GSkill DDR3 ram zum 3.mal defekt

[hulkhardy1]

Im zweiten Bild schallte mal den zweiten Eintrag DDR3 Timimg Items auf manuell und trage die Werte von Hand ein also von oben nach unten, 9-9-9-25 und 1T/2T Command Timing auf 2T steht nämlich nach deinem CPU-Z Screenshot auf 1T also umschallten, die restlichen Werte kannst du so lassen wie sie eingestellt sind.

 

[Painkiller]

Gestern isser endlich angekommen....
Hab mir ein neues Netzteil geholt (Corsair HX850) und gleich mal alles wieder verbaut. Bis jetzt hatte er keine abstürze. Hab win7-64bit installiert,alle Treiber,Battleforge gezogen,Stalker Benchmark laufen gelassen, WinRAR Bench 45min laufen lassen und keine Absturz. Das zirpen ist jetzt auch nicht mehr zu hören. Nur unter Last bei Dragon Age aber ich denke das kommt von der Graka weil das war schon immer und ist auch bei weitem nicht so laut. Ich hoffe mal das es wirklich nur das Netzteil war. Das Toughpower hat ja noch Garantie laut deren Homepage.

Jo das "zirpen" nennt sich Spulenfiepen...^^ xD
Is ganz normal hat meine GTX285 auch....

Freut mich für dich, das alles wieder geht...
btw. lass mal 3DMark06 drüberlaufen, nur zur Sicherheit....

 

[Sidhi]

Danke , ich habs so gemacht wie du gesagt hast hulkhardy1.
jetzt steht auch in cpu-z 2T drinnen. Muss jetz mal ein bisschen beobachten wie es läuft,
ich hoffe es ist vorbei.
vielen dank erstmal ich melde mich nachts wieder wie alles läuft.

 

[hulkhardy1]

Ja, alles klar sag bescheit aber ich denke es lag an der Commandrate (Timing). Wenn noch Fehler auftreten, kannst ja mal memtest laufen lassen wenn der keine Fehler meldet kannst du davon ausgehen das dein Ram stabiel läuft.

 

[Sidhi]

offenbar war diese kleinigkeit mein problem, windows test zeigt nix an memtest nach 4 std auch nix, zum glück hab ich noch hier gefragt bevor ich sie zurückgeschickt hätte.
vielen dank hulkhardy1

 

[hulkhardy1]

Na super freud mich doch das es bei dir wieder läuft, ich kenn das ja auch, mann baut was neues ein und nix geht mehr. god luck!

 

[Stahlmann]

Lol....also.....
Das Netzteil war es auch nicht. Gestern Abend (mein PC lief 1 Tag lang gar nicht) schalt ich meinen PC ein freu mich auf ne Runde Dragon Age lauf weg während dem booten und als ich wieder an PC komm BSOD -.- non paged area dingens und wieder die tollten 0x00000.... Fehler. Memtest CD rein,Neustart und wieder tausende Fehler. Dann Resetet,Bios nachgeschaut, nix geändert,neustart,alles läuft super Prime läuft stundenland,Memtest zeigt auch nach dem 4x keine Fehler (Jeweils nur paar Minuten nur zum kontrollieren,Fehler kamen wenn dann immer sofort). Hab mein altes Netzteil wieder drangehängt und das neue geht wieder zurück. Das alte fiept zwar kostet aber nix...Also ich weiss jetzt echt nicht mehr weiter.

 

[hulkhardy1]

Das ist jetzt ein anderer Fehler! Das liegt am Kaltstart da haben manche Ram Probleme mit da hilft meistens die Spannung etwas anzuheben, um o.1 oder 0.2 Volt.

 

[Stahlmann]

auf dich ist verlass
ok ich hab den ram dann jetzt mal auf 1,6v laufen und das neue netzteil wieder verbaut...das spulienfiepen vom alten war einfach nicht auszuhalten.
mal schauen wie es jetzt läuft. ich meld mich dann wieder beim nächsten bsod und memtest-rekordfehlerlauf ^^

 

[Stahlmann]

nach einer schönen woche voller spielspaß heute wieder mal das böse erwachen
eingeschaltet und noch im Win7 Ladebildschirm wo das Logo so herfliegt hatte ich einen bunten Streifen 1sec lang und schon kam der BSOD mit dem fehler irql_not_less_or_equal 0x0000000a
Hab dann nachgeforscht und gelesen es könnten TreiberProbleme sein und hab dann versucht den abgesicherten Modus zu starten. Ging aber auch nicht. Dann nachm 5. Versuch kam dann der Fehler Stop c000021a und nochmal ein anderer den ich mir aber nicht notiert habe. Memtest brachte in 20sec 6000fehler... Achja mir ist auch aufgefallen das meine 2. Festplatte immer so komisch gesurrt hat und dann in Ruhezustand oder so gefallen ist mit nem knacksen. So wie wenn man ne externe ne Weile nicht benutzt und die anspringt. Hab die Platte dann abgehängt und dann hat er gebootet. Die Platte hat aber erst 1 Jahr aufm Buckel oder so. Und wurde ja eigentlich komplett mit HDTune gecheckt ohne fehler....

 

[Stahlmann]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030910-20625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: '"'
Symbol search path is: "srv*c:\cache*http://msdl.microsoft.com/download/symbols;"
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Tue Mar 9 16:00:44.359 2010 (GMT+1)
System Uptime: 0 days 0:00:11.359
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.............................................
Loading User Symbols
Loading unloaded module list
..
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004e71028, be000000, 800400}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004e71028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002a1b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff800`04151a98 fffff800`0300a903 : 00000000`00000124 00000000`00000000 fffffa80`04e71028 00000000`be000000 : nt+0x71f00
fffff800`04151aa0 00000000`00000124 : 00000000`00000000 fffffa80`04e71028 00000000`be000000 00000000`00800400 : hal+0x12903
fffff800`04151aa8 00000000`00000000 : fffffa80`04e71028 00000000`be000000 00000000`00800400 fffffa80`04b9bbd0 : 0x124


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

0: kd> lmvm hardware
start end module name

 

[Blechdesigner]

Hat hier schonmal einer auf den SATA-Kontroller vom Board selbst getippt? Wenn nicht mach ich das einfach mal.

 

[Stahlmann]

kann ich den irgendwie testen?

 

[Wolf78]

G.Skill und Kingston sind meine 2 Lieblingsmarken, von denen hat mich bisher kein einziger Riegel enttäuscht.

Da kann ich Dir nur zustimmen G.Skill sind nicht zu schlagen. Meine haben zwar fast 200 Eus gekostet ,aber es hat sich gelohnt machen ohne zu zucken 2000 Mhz mit . Siehe hier G.Skill PI 2x2GB DDR3 PC3-12800 Review

 

[Stahlmann]

Jetzt hab ich ja schon das 3. Kit ich glaub nicht mehr das es der Ram sein kann...

 

[Blechdesigner]

Also am Speicher kann's wirklich nicht liegen, wenn man so Google überfliegt liest man mehr von Treiberproblemen als von Hardware-Schäden.

Und den Kontroller könntest du nur mit einem anderen Board so wirklich testen (ob's halt die Fehlerquelle ist und selbiger ne Make hat)