random BSODs and freezes (suspecting RAM)

Hi :)

I am experiencing random BSODs and freezes with my machine since the beggining (few months of usage). Sometimes it happens only a few seconds after reboot, sometimes after many hours of work - totally unpredictable. Machine is very 'clean' - no internet, only music production, totally controled environment.

Intel Core I7 - 960
RAM DDR Kingston 12 Gb
HDD WD 1tb
Power supply Corsair 650w

I've done memory test few times. Only once it showed some memory errors - next time I ran test they are gone. So I really suspect RAM.

I am sending you a couple of dump files - please, look at them, i hope you'll find the reason for crashes.

Many thanks in advance !

spd.jpg memory.jpg
View attachment minidump.zip

Welcome. Your memory is set wrong in the bios. Go to bios. Load the Optimized Defaults. Save. Then post a new memory tab.

BTW, excellent first post. Well prepared, which makes life easy for me.

(You're having 0x124 hardware errors right now because of it.)


Also update J-Micron SATA driver:

jraid jraid.sys Wed May 27 01:39:35 2009


Thank you, what was QUICK !!!

I'll go in the studio later today and setup everything as you said.
Then I'll send you a new memory tab back.

Thanks again !


I didn't find 'load optimized defaults' in my BIOS - only 'Load setup defaults' (Phoenix BIOS).
I've selected this option, but memory tab information is still the same.

Funny is, that i didn't have any BSOD for two days, no matter how hard i try, eh.

Any other ideas, what should I do. Does latest bios versions have 'load optimized defaults' option ?


Last edited:
Hi :)

Can you give me any hints, how to setup memory correctly (what is wrong with the memory tab)?

btw. did you look at the dumpfile - is there something else to take care ?


667 MHz with 9-9-9-24 timings needed to be set manually in the bios, then saved.

memory.jpg spd.jpg

667 MHz with 9-9-9-24 timings needed to be set manually in the bios, then saved.
Ok, I will try that !

Funny thing - i have another machine with 6 GB of GEIL ram (same motherboard P6T and I7 - 920). I have absolutely no BSOD-s there. It's much more loaded machine than other, problematic one.

I am sending you screenshots of this normal working machine. I think that BIOS memory settings are the same, as I can see. Still no problems here.

Can you check these screenshots ! Thanks !!!

btw. If I set memory as you suggested also on non-problematic machine, can i make it faster working ? Or should I leave it as it is?


I'm helping you here with a machine that is non-functional. Please don't push your luck.

I'm helping you here with a machine that is non-functional. Please don't push your luck.
Ok, understood :)

I will try this new memory setings on the non-functional machine, only - i'll keep you informed !!!

Many thanks.

Here we go again ...

Timings corrected to 9-9-9-24

Screenshots provided.

Now very rare crash/freeze produces dmpfile, which I am sending to you.

Thanks !

SPD-corrected.jpg memory-corrected.jpg View attachment dumpfile.zip

Still not right, must be 667 MHz with 9-9-9-24 while yours is currently set 534Mhz. : )

My BIOS 'DRAM frequency' (set to auto) has only options from 800-2133 MHz.
How can I set it to 667 MHz?

Am I looking to the right option ?


CPU-Z shows it is a 667 Mhz RAM. Could you give the link to your RAM kit where I can verify its specs?

I'll talk to someone at the computer shop on monday - hope they'll give me exact data about RAM - i will let you know about it.

Still, strange thing is that my nonproblematic machine (Geil RAM) and problematic machine (Kingston RAM) are showing the same frequency to the CPU-Z (534 MHz).

I'll do some more tests with Memtest overnight !


Still, strange thing is that my nonproblematic machine (Geil RAM) and problematic machine (Kingston RAM) are showing the same frequency to the CPU-Z (534 MHz).
The thing is CPU-Z sometimes detects certain RAM sticks wrong, so to have it absolutely positive verify the specs - frequency, timings, voltage. You can find this info on the RAM package/web site/sometimes written on the RAM stick itself.

The thing is CPU-Z sometimes detects certain RAM sticks wrong, so to have it absolutely positive verify the specs - frequency, timings, voltage. You can find this info on the RAM package/web site/sometimes written on the RAM stick itself.
Ok, I will do my best !

Wish you a happy new year :)


Ok, I will do my best !

Wish you a happy new year :)


Thank you Sir, have great holidays as well.

Yes, verify that the RAM is set right in the BIOS. Set the frequency, the voltage, and the timings manually, of course provided you know the specs exactly. Btw, your latest crash dump shows stop 0x124 - which means a fatal uncorrectable hardware error has occured, so let's hope the right RAM settings will fix it.


A fatal hardware error has occurred
Stack - nt nt nt nt nt
Probably caused by : hardware

You did not update all drivers which TorrentG listed for you on Page 1 of this thread:

jraid.sys Wed May 27 01:39:35 2009
JMicron JMB36X RAID Driver

tdrpm251.sys Fri Jul 31 09:59:53 2009

Even with the RAM settings right, you should update those drivers as they are old for Windows 7 and sooner or later will be bugging out.

Crash Dumps:

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

Loading Dump File [F:\a\Minidump\D M P\DMP\123010-13447-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03090e50
Debug session time: Thu Dec 30 13:00:09.663 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:06.772
Loading Kernel Symbols
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800b0b7038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner

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

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.
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800b0b7038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

BUGCHECK_STR:  0x124_GenuineIntel





fffff880`035626f0 fffff800`0310da79 : fffffa80`0b0b7010 fffffa80`09d78040 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03562c10 fffff800`02fef5a7 : fffffa80`0b0b7010 fffff800`030685f8 fffffa80`09d78040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03562c40 fffff800`02f57b85 : fffff800`030ca360 fffff880`01279a18 00000000`00000000 fffffa80`09d78040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03562c80 fffff800`02ed0861 : fffff880`01238800 fffff800`02f57b60 fffffa80`09d78040 9c5c9c5c`b902b902 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03562cb0 fffff800`03168a86 : 5ec05ec0`71427142 fffffa80`09d78040 00000000`00000080 fffffa80`09d5c040 : nt!ExpWorkerThread+0x111
fffff880`03562d40 fffff800`02ea1b06 : fffff880`0336a180 fffffa80`09d78040 fffff880`033750c0 27b827b8`a6e8a6e8 : nt!PspSystemThreadStartup+0x5a
fffff880`03562d80 00000000`00000000 : fffff880`03563000 fffff880`0355d000 fffff880`039cf590 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware



BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner


start             end                 module name
fffff880`00f23000 fffff880`00f7a000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`010bc000 fffff880`010c7000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00e63000 fffff880`00e6c000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00dac000 fffff880`00dd6000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01850000 fffff880`01880000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d34000 fffff880`00d92000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01185000 fffff880`011f8000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01880000 fffff880`0188e000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0183a000 fffff880`01850000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0189a000 fffff880`018a3000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0188e000 fffff880`0189a000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`019ed000 fffff880`01a00000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01113000 fffff880`01127000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010c7000 fffff880`01113000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013ea000 fffff880`013f4000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01800000 fffff880`0183a000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02e0a000 fffff800`02e53000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`019e4000 fffff880`019ed000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`00dd6000 fffff880`00df3000   jraid    jraid.sys    Wed May 27 01:39:35 2009 (4A1CD217)
fffff800`00baa000 fffff800`00bb4000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`013bf000 fffff880`013d9000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00cdc000 fffff880`00d20000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00d92000 fffff880`00dac000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f83000 fffff880`00f8d000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01127000 fffff880`01185000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01bea000 fffff880`01bfc000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014dd000 fffff880`015cf000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02e53000 fffff800`0342f000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`0121c000 fffff880`013bf000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00fcd000 fffff880`00fe2000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f8d000 fffff880`00fc0000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00cc0000 fffff880`00cd0000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013d9000 fffff880`013ea000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00d20000 fffff880`00d34000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01a00000 fffff880`01a3a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0108d000 fffff880`010bc000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`01bab000 fffff880`01bea000   snapman  snapman.sys  Tue Sep 08 03:57:04 2009 (4AA60E50)
fffff880`01ba3000 fffff880`01bab000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`01a3d000 fffff880`01ba3000   tdrpm251 tdrpm251.sys Fri Jul 31 09:59:53 2009 (4A72F8D9)
fffff880`018a3000 fffff880`01988000   timntr   timntr.sys   Mon Aug 17 03:16:13 2009 (4A8903BD)
fffff880`00fc0000 fffff880`00fcd000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01988000 fffff880`01998000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00fe2000 fffff880`00ff7000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01998000 fffff880`019e4000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e70000 fffff880`00f14000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f14000 fffff880`00f23000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f7a000 fffff880`00f83000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list

Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.