Occasional ntoskrnl BSOD

I've been battling this one since I built this system in late October. Since then, the machine suffers a BSOD, approximately once every two days; although it has gone as long as nine days in between.

There is no obvious theme to what the machine is doing when the crash occurs. It has crashed at idle, in graphics intensive games, and while simply browsing the internet.

I've done what I feel I can, and now must seek your assistance.

The machine is running Windows 7 x64 Pro.

I began by using WhoCrashed 2.10 to analyze the minidumps after the first BSOD.

Sadly, all 22 dumps I've collected list ntoskrnl.exe as the cause, although for varying reasons; including 'CRITICAL STRUCTURE CORRUPTION' and 'KMODE EXCEPTION NOT HANDLED'.

I have run Memtest86+ to completion, with my RAM modules in their current positions.
I have NOT run Memtest86+ on the modules individually.

I have reinstalled several drivers, and I believe them all to be current.

I have attached my latest three minidumps.

The single most recent dump was created while 'verifer.exe' was active, monitoring all non-Microsoft drivers on the system; and running all tests except 'Low Resource Simulation'.

Oddly, after activating the driver verifier, it took a full nine days, and several reboots to actually suffer a BSOD; as opposed to the common two day interval.

I have never installed Alcohol 120% or Daemon Tools on the system.
It was running AVG for a time, but I replaced it with MSE a number of weeks ago.

Thank you for your time.


Last edited:

Ram is set wrong. Load Optimized Defaults in bios, save.

Update Realtek lan driver:

2: kd> lmvm rt64win7
start end module name
fffff880`0406a000 fffff880`040a8000 Rt64win7 T (no symbols)
Loaded symbol image file: Rt64win7.sys
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Image name: Rt64win7.sys
Timestamp: Thu Jul 30 07:58:43 2009 (4A718AF3)
CheckSum: 000460F2
ImageSize: 0003E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


Thank you for the quick response.

Updated the Realtek drivers from 7.00 to 7.34 successfully.

Attempted to alter the RAM settings, however it seems that all settings are already in the 'Auto' mode. There is no universal, 'load optimized defaults' that I can find.

When accessing the memory settings, I'm presented with a list of 30 or so timing items, that I can configure manually, or leave in the automatic mode. I've always left them automatic.

It does seem to me that the timings could be a bit tighter than where the defaults have placed them, but I'm more interested in stability at this point.

Perhaps if you could be more specific as to which RAM settings should be altered?

Thanks again.

I've suffered another BSOD after updating the Realtek drivers. I've attached the minidump in the event it might be helpful.

I'm imagining that all there is left to try is to adjust the RAM timings, but I'm not exactly sure in what way they should be changed. Should I underclock the RAM and see if the system stabilizes?

I've also noticed, in my BIOS browsing that the CPU idles around 47 C... which seems a bit high to me, but considering that I'm using the stock cooler, I don't know if I can complain.

Thanks again.


After doing a little more research, I have disabled CPU Spread Spectrum on my motherboard.

My Memory tab now shows:
NB Frequency - 2000.1 MHz
DRAM Frequency - 666.7 MHz

Other timings are the same.

I have no idea if this was necessary, as I am not overclocking the system, but I am running out of ideas, and growing frustrated.

Lol, that's why I don't rely much on the verifier, disable it by the way ASAP to stop it crashing you non-stop:

BugCheck 1E, {ffffffffc0000005, fffff80000b9a5b0, 0, 0}

The network driver is good and latest:
Rt64win7.sys Tue Nov 30 01:01:28 2010

The only driver I'd ask you to update is VIA audio:
viahduaa.sys Thu Sep 17 07:04:15 2009


RAM - it's not set right in the bios, and moreover CPU-Z doesn't detect it right. So I ask you to give link to your memory sticks specs. You can see them on the RAM package if you have it. Then set them right. Loading bios with the optimized defaults can help.

Crash Dumps

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

Loading Dump File [C:\Documents and Settings\XPMUser\My Documents\122910-14515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Documents and Settings\XPMUser\My Documents\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Wed Dec 29 17:10:44.154 2010 (UTC - 5:00)
System Uptime: 1 days 0:50:12.046
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80000b9a5b0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1586b )

Followup: MachineOwner

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

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80000b9a5b0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

fffff800`00b9a5b0 c8b4b900        enter   0B9B4h,0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR:  0x1E_c0000005





EXCEPTION_RECORD:  fffff80000b9b4c8 -- (.exr 0xfffff80000b9b4c8)
ExceptionAddress: fffff88002b945ba (afd!AfdCloseConnection+0x000000000000009a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9b570 -- (.trap 0xfffff80000b9b570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=001301000003afd8
rdx=0000000000130100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002b945ba rsp=fffff80000b9b700 rbp=fffffa800676b380
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8005878f40
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
fffff880`02b945ba 488b01          mov     rax,qword ptr [rcx] ds:0004:00130100`0003afd8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b61bdb to fffff80002acf740

fffff800`00b9b700 fffff880`02b95cab : fffffa80`04cdad30 00000000`00000010 00000000`80000000 fffff800`02c57c40 : afd!AfdCloseConnection+0x9a
fffff800`00b9b740 fffff880`0166ca77 : fffff800`00b9bb60 fffff800`00b9bb60 fffffa80`04d43888 fffffa80`04c6a630 : afd!AfdCommonRestartDisconnect+0x3b
fffff800`00b9b790 fffff880`0166bd97 : fffffa80`04c6a630 fffffa80`04c6a630 fffffa80`04c6a630 00000000`00000010 : tcpip!TcpDisconnectTcbComplete+0x67
fffff800`00b9b840 fffff880`0166a1ad : 00000000`00000000 fffff800`00b9bb60 00000000`bc384279 00000000`00000001 : tcpip!TcpFinAcknowledged+0x137
fffff800`00b9b8d0 fffff880`01677334 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpTcbCarefulDatagram+0x43d
fffff800`00b9ba80 fffff880`0167b86a : fffffa80`059d5f00 fffffa80`03b10900 fffffa80`05874901 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff800`00b9bc30 fffff880`0167b3b7 : fffff880`04f6cae2 fffffa80`059c7000 00000000`00000000 fffff880`0165e600 : tcpip!TcpMatchReceive+0x1fa
fffff800`00b9bd80 fffff880`0165d6c7 : fffffa80`059c7000 fffffa80`058a9820 fffffa80`059d27df 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177
fffff800`00b9be30 fffff880`0165d799 : fffff800`00b9bfb0 fffff880`0176b9a0 fffff800`00b9bfc0 fffffa80`03b109e0 : tcpip!IppDeliverListToProtocol+0x97
fffff800`00b9bef0 fffff880`0165dc90 : fffffa80`05953e70 00000000`00000000 00000000`0007c0c8 fffff800`00b9bfb0 : tcpip!IppProcessDeliverList+0x59
fffff800`00b9bf60 fffff880`0165cb21 : 00000000`00000004 fffffa80`059c7000 fffff880`0176b9a0 00000000`05f6f601 : tcpip!IppReceiveHeaderBatch+0x231
fffff800`00b9c040 fffff880`0165b592 : fffffa80`05fd4d80 00000000`00000000 fffffa80`05f6f601 fffff800`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff800`00b9c240 fffff880`01674e5a : fffffa80`05f6f610 fffff800`00b9c370 fffffa80`05f6f610 fffff800`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff800`00b9c320 fffff800`02adee5a : fffff980`04828e20 fffff800`00b97000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff800`00b9c370 fffff880`01674882 : fffff880`01674d80 fffff800`00b9c480 fffff800`00b9c102 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff800`00b9c450 fffff880`0152d0eb : fffff980`096c88d0 00000000`00000000 fffffa80`05cbb1a0 fffff800`02cddb7c : tcpip!FlReceiveNetBufferListChain+0xb2
fffff800`00b9c4c0 fffff880`014f6fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff800`00b9c530 fffff880`01470ef1 : fffffa80`05cbb1a0 00000000`00000002 00000000`00000001 fffff980`033eaf90 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff800`00b9c9b0 fffff880`0409f86b : fffffa80`05e1f000 fffff980`033eaf90 fffffa80`05e1f600 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff800`00b9ca00 fffffa80`05e1f000 : fffff980`033eaf90 fffffa80`05e1f600 00000000`00000000 fffff800`00000001 : Rt64win7+0x1586b
fffff800`00b9ca08 fffff980`033eaf90 : fffffa80`05e1f600 00000000`00000000 fffff800`00000001 fffffa80`03af5b90 : 0xfffffa80`05e1f000
fffff800`00b9ca10 fffffa80`05e1f600 : 00000000`00000000 fffff800`00000001 fffffa80`03af5b90 00000000`00002000 : 0xfffff980`033eaf90
fffff800`00b9ca18 00000000`00000000 : fffff800`00000001 fffffa80`03af5b90 00000000`00002000 00000000`00000001 : 0xfffffa80`05e1f600

STACK_COMMAND:  .trap 0xfffff80000b9b570 ; kb

fffff880`0409f86b ??              ???


SYMBOL_NAME:  Rt64win7+1586b

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  Rt64win7.sys


FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_Rt64win7+1586b

BUCKET_ID:  X64_0x1E_c0000005_VRF_Rt64win7+1586b

Followup: MachineOwner


start             end                 module name
fffff880`00f52000 fffff880`00fa9000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02b52000 fffff880`02bdc000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`041a8000 fffff880`041be000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03db3000 fffff880`03dc8000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00c00000 fffff880`00c0b000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`083e7000 fffff880`083f2000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00dc4000 fffff880`00dcd000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00dcd000 fffff880`00df7000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`043bc000 fffff880`043dc000   AtihdW76 AtihdW76.sys Thu Jul 15 08:46:49 2010 (4C3F0339)
fffff880`04605000 fffff880`04dfa000   atikmdag atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1)
fffff880`03e58000 fffff880`03ea3000   atikmpag atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF)
fffff960`008f0000 fffff960`00951000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`02a61000 fffff880`02a68000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03d7c000 fffff880`03d8d000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`03910000 fffff880`0392e000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`007d0000 fffff960`007f7000   cdd      cdd.dll      unavailable (00000000)
fffff880`063db000 fffff880`063f8000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`02a01000 fffff880`02a2b000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cea000 fffff880`00daa000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01000000 fffff880`01030000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c8c000 fffff880`00cea000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`012f0000 fffff880`01363000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04198000 fffff880`041a8000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`043dc000 fffff880`043ea000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03cdb000 fffff880`03d5e000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`03d5e000 fffff880`03d7c000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03ccc000 fffff880`03cdb000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`013ca000 fffff880`013e0000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0423d000 fffff880`0425f000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`043f6000 fffff880`043ff000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`043ea000 fffff880`043f6000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`03e33000 fffff880`03e46000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`063cf000 fffff880`063db000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`03ea3000 fffff880`03f97000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`03f97000 fffff880`03fdd000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`00c57000 fffff880`00c6b000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00c0b000 fffff880`00c57000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01374000 fffff880`0137e000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0123a000 fffff880`01274000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02a16000 fffff800`02a5f000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`03e00000 fffff880`03e24000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`08200000 fffff880`08219000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`042c6000 fffff880`042ce080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`083f2000 fffff880`08400000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`03848000 fffff880`03910000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01462000 fffff880`0146b000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04162000 fffff880`04180000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04180000 fffff880`0418f000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bd0000 fffff800`00bda000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`042f8000 fffff880`0433b000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`012d6000 fffff880`012f0000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015c1000 fffff880`015ec000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0425f000 fffff880`04264200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`03de9000 fffff880`03dfe000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03fdd000 fffff880`04000000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c6b000 fffff880`00c78000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`04291000 fffff880`0429f000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`03e24000 fffff880`03e33000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`08219000 fffff880`08226000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00daa000 fffff880`00dc4000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02a2b000 fffff880`02a58000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`039e4000 fffff880`039f4000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`0392e000 fffff880`03946000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03946000 fffff880`03973000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`03973000 fffff880`039c1000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`039c1000 fffff880`039e4000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`02ac6000 fffff880`02ad1000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fb2000 fffff880`00fbc000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01278000 fffff880`012d6000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03cc1000 fffff880`03ccc000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015ec000 fffff880`015fe000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0146f000 fffff880`01561000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`041e2000 fffff880`041ee000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04000000 fffff880`0402f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`043a7000 fffff880`043bc000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03c26000 fffff880`03c35000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02b0d000 fffff880`02b52000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01561000 fffff880`015c1000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02ad1000 fffff880`02ae2000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03cb5000 fffff880`03cc1000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a5f000 fffff800`0303b000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01041000 fffff880`011e4000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02a58000 fffff880`02a61000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`03c00000 fffff880`03c26000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00fbc000 fffff880`00fef000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e86000 fffff880`00e8d000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e8d000 fffff880`00e9d000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01363000 fffff880`01374000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`07edf000 fffff880`07f85000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`042dc000 fffff880`042ec000   point64  point64.sys  Tue Jun 29 04:54:31 2010 (4C29B4C7)
fffff880`04200000 fffff880`0423d000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c78000 fffff880`00c8c000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`041be000 fffff880`041e2000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0402f000 fffff880`0404a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0404a000 fffff880`0406b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0406b000 fffff880`04085000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03c64000 fffff880`03cb5000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`041ee000 fffff880`041f9000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`02aab000 fffff880`02ab4000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02ab4000 fffff880`02abd000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02abd000 fffff880`02ac6000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01200000 fffff880`0123a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02be5000 fffff880`02bfd000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0408a000 fffff880`040f0000   Rt64win7 Rt64win7.sys Tue Nov 30 01:01:28 2010 (4CF49338)
fffff880`07f85000 fffff880`07f90000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`0145a000 fffff880`01462000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`082af000 fffff880`08345000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07e00000 fffff880`07e67000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`07f90000 fffff880`07fbd000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`041f9000 fffff880`041fa480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`07fbd000 fffff880`07fcf000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`02b00000 fffff880`02b0d000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02ae2000 fffff880`02b00000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03c50000 fffff880`03c64000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`004f0000 fffff960`004fa000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03d8d000 fffff880`03db3000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`0433b000 fffff880`0434d000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`06200000 fffff880`0621d000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`0621d000 fffff880`0621ef00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04151000 fffff880`04162000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0434d000 fffff880`043a7000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`040f0000 fffff880`040fb000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`040fb000 fffff880`04151000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`0621f000 fffff880`0622b000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
fffff880`04265000 fffff880`04276000   usbscan  usbscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
fffff880`04276000 fffff880`04291000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00fef000 fffff880`00ffc000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02a68000 fffff880`02a76000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`06230000 fffff880`063cf000   viahduaa viahduaa.sys Thu Sep 17 07:04:15 2009 (4AB217AF)
fffff880`02a76000 fffff880`02a9b000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0144a000 fffff880`0145a000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00e15000 fffff880`00e2a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e2a000 fffff880`00e86000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`0137e000 fffff880`013ca000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03c35000 fffff880`03c50000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02a9b000 fffff880`02aab000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e9f000 fffff880`00f43000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f43000 fffff880`00f52000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02bdc000 fffff880`02be5000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00060000 fffff960`00370000   win32k   win32k.sys   unavailable (00000000)
fffff880`0418f000 fffff880`04198000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00fa9000 fffff880`00fb2000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`03dc8000 fffff880`03de9000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`08345000 fffff880`08376000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`042ad000 fffff880`042c6000   HIDCLASS.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00019000
fffff880`0429f000 fffff880`042ad000   hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`042cf000 fffff880`042dc000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`08376000 fffff880`083e7000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`013e0000 fffff880`013ee000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`013ee000 fffff880`013fa000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`01030000 fffff880`01039000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`011e4000 fffff880`011f7000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

I have upgraded my VIA HD Audio driver.
From: 6.01.7500 Dated: 9/17/2009
To: 6.01.8700 Dated: 8/4/2010

I have altered some of my RAM timings using the information from this datasheet:

It shows my proper memory timings to be 9-9-9-24.

This is my motherboard:
ASRock > Products > M3A770DE

My BIOS doesn't have a "Load Optimized Defaults".
I can "Load Defaults", but that simply returns it to the factory settings, which is "Auto" for everything. Obviously, the "Auto" mode is not setting my RAM timings correctly, so I have set them manually.

My New Memory Settings Are:

Memory Clock: 667 MHz DDR3_1333
Memory Controller Mode: Unganged
Power Down Enable: Disabled
Bank Interleaving: Auto
Channel Interleaving: HASH 2

CL: 9
tRCD: 9
tRP: 9
tRAS: 24
tRTP: 5 (Auto)
tRRD: 4 (Auto)
tWTR: 5 (Auto)
tWR: 10 (Auto)
tRC: 33 (Auto) <---{This seems correct, as tRP+tRAS = 33}
tRWTWB: 9 (Auto)
tRWTTO: 8 (Auto)
tWRRD: 2 (Auto)
tWRWR: 3 (Auto)
tRDRD: 4 (Auto)
tRFC0: 110 (Auto)
tRFC1: 110 (Auto)

CHA ADDR/CMD Delay: 22/64 (Auto)
CHA ADDR/CMD Setup: 1 (Auto)
CHA CS/ODT Delay: 0 (Auto)
CHA CS/ODT Setup: 1/2 (Auto)
CHB ADDR/CMD Delay: 22/64 (Auto)
CHB ADDR/CMD Setup: 1 (Auto)
CHB CS/ODT Delay: 0 (Auto)
CHB CS/ODT Setup: 1/2 (Auto)

CHA CKE Drive: 1.50x (Auto)
CHA CS/ODT Drive: 1.50x (Auto)
CHA ADDR/CMD Driver: 1.50x (Auto)
CHA CLK Drive: 1.50x (Auto)
CHA DATA Drive: 1.00x (Auto)
CHA DQS Drive: 1.00x (Auto)
CHA Processor ODT: 60 ohms (Auto)
CHB CKE Drive: 1.50x (Auto)
CHB CS/ODT Drive: 1.50x (Auto)
CHB ADDR/CMD Driver: 1.50x (Auto)
CHB CLK Drive: 1.50x (Auto)
CHB DATA Drive: 1.00x (Auto)
CHB DQS Drive: 1.00x (Auto)
CHB Processor ODT: 60 ohms (Auto)

While I don't know much/anything about the settings I left in the "Auto" state, one thing I wonder about is how the system functioned while tRP was 12 and tRAS was 30. When that was the case, tRC should have been 42... not 33. It was my understanding that having tRC be less than tRP+tRAS was a sure-fire way of preventing a clean boot. Odd.

Nonetheless, I completed another sweep of Memtest86+ last night (before changing the settings). It completed 10 passes in 9.5 hours. Though, with how occasional my problem is, I still can't rule out my RAM. I will run it again tonight.

Also, I have left Driver Verifier running for the time being. It hasn't caused any additional instability. The crashes still average about once per day, usually at very annoying times.

Thank you for the continued support.

Your screenshot above shows you have it 665Mhz 9-12-12-30.

The pdf shows it's meant to be DDR3-1333 9-9-9-24 at 1.5V. If this is your RAM set it this way as shown.

Sorry, I suppose I should have updated my screenshot after making the timing adjustments. It has been corrected.

Ran Memtest86+ last night with the 9-9-9-24 timings. No problems found in 11 passes.

Sorry, I suppose I should have updated my screenshot after making the timing adjustments. It has been corrected.

Ran Memtest86+ last night with the 9-9-9-24 timings. No problems found in 11 passes.

Yes, your updated screenshots indeed show you have it the right way now 9-9-9-24, and there's your reward - 11 passes without errors. Well done, enjoy the holidays now. : )

I wish I had your optimism. The system managed to get through 10 passes with the incorrect RAM timings. Eleven passes with the correct timings doesn't leave me sated.

I just can't trust the system at this point... it ate two months worth of accounting when it crashed during a save operation... (should have had a more recent backup, I know) It also corrupted LibreOffice by crashing during the install operation.

I sincerely hope that either the RAM timings or the updated audio drivers solved the problem.
I'm disabling the driver verifier until the next crash, so that data won't be in the next minidump.

I'll post back when/if it crashes again...

Thank you again for your assistance. You lead me down some avenues I wouldn't have considered otherwise.

The system managed to get through 10 passes with the incorrect RAM timings.
Oh yes, it's a well known fact memtest does not necessarily find errors when RAM is set wrong. Sometimes it finds sometimes it doesn't.

Eleven passes with the correct timings doesn't leave me sated.
Still the news is good if the memtest detects no errors, means you have a chance to do without replacing the RAM. So there's probably some grounds for the optimism. Let's hope. : )

Oh yes, it's a well known fact memtest does not necessarily find errors when RAM is set wrong. Sometimes it finds sometimes it doesn't.

Still the news is good if the memtest detects no errors, means you have a chance to do without replacing the RAM. So there's probably some grounds for the optimism. Let's hope. : )
I didn't know that Memtest wouldn't necessarily detect off-timing errors.

Thank you. :)

Lol, memtest does not always right away detect defective RAM either, even if it's set right and is indeed defective. It takes sometimes to test sticks separately and in different slots.


I didn't know that Memtest wouldn't necessarily detect off-timing errors.

Thank you. :)
to quote since windows 95 Microsoft have stated about memory testing programs
Defective memory chips may not be detected by memory checking tools. Some memory checking programs are not adequate tests because they do not test RAM in the same way that Windows uses RAM. Most memory checkers use read/write cycles when scanning memory. Since Windows is executing code from memory, it uses execute cycles. Execute cycles are different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.

Well, after a week of delightful, crash-free stability, I got up this morning to see something a little odd.

In the past, when the system BSOD'd while I was gone/asleep, I'd usually wake it from sleep, and see the "Windows has recovered from..." message; meaning it had crashed and rebooted itself. Not this time.

This time, I walked into the room and my monitor was in the 'active' state. Essentially, the system was frozen at a black screen. It wouldn't respond to the power button, so a reset was in order. Upon reboot, I found a brand-new minidump waiting for me.

Fine, whatever... off to work.

I come home for lunch, the situation was repeated. Another black screen, another minidump.

Okay... that's enough of this BS. Time for the big guns. People overclock their systems, and verify their stability all the time, right?

So I loaded Prime95. The machine has never run that hot before.

Prime95 runs for 3 hours, 6 minutes. (The usual stability runs are 16+ hours aren't they?)
Thread #3 kicks out the following:
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
So... I'm guessing we can rule out software, and say that I definitely have a hardware problem.

Now what? Am I correct in assuming that it now has to be either motherboard or memory? Could it still be the timings?

Should I take one stick out, run Prime? Then, if it passes, try the other stick? If it fails, try a different slot? Essentially, am I at the point where I need to determine the hardware failure point by process of elimination, or is there another avenue I should attempt first?

Thank you all again.

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Yes, this means hardware.

Am I correct in assuming that it now has to be either motherboard or memory? Could it still be the timings?
If you've set them right (loaded bios defaults), it's not the timings.

Should I take one stick out, run Prime? Then, if it passes, try the other stick? If it fails, try a different slot?
I need to determine the hardware failure point by process of elimination, or is there another avenue I should attempt first?
This is the most difficult part, yes you can try that but watch the temps don't let them go past the critical. Stop the test if the CPU reaches or exceeds 70 Celcius Degrees. Cause that way the errors may pop up due to overheating and the testing becomes senseless.

Prime95 - if you do FFT this puts stress primarily on the CPU. Blend tests memory too. You may wanna do both to see if you get different results, hopefully to find out if this is likely your RAM faulty.


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