Another BSOD to analyse...

canoemoose · Sep 14, 2010

Hi all,
I've just finished building a new machine and installed Windows 7 Ultimate 64 bit. I keep getting BSODs at seemingly random intervals - the machine will sometimes run all morning fine and then suffer bluescreens within minutes of rebooting. They seem to be related to heavy network traffic, although when I spent a morning downloading applications etc I had no problems

You'll find my dump files and health report attached.

Hardware:

Gigabyte GA-H55M-S2
Intel i5 750 2.66GHz
2x 2GB DDR3 1333MHz OCZ Gold RAM
500GB Seagate Barracuda
NVIDIA 9500GT

As I had a spare XP license and an upgrade license for Windows 7 is available with student discount, I installed XP first and then did a "clean install" upgrade to Windows 7.

I've run memtest86 for 12 hours (about 20 passes) and it reported one error of 1 bit on the 4th pass only.

I hope someone can help as I'm now stuck!

EDIT: Attachment didn't work. Fixed now!

canoemoose · Sep 14, 2010

Edited attachments onto OP, this post to bump thread.

Jonathan_King · Sep 14, 2010

Welcome to SF!

I suspect you are on to something when you suspect network. Avast is blamed by one dump, your Realtek drivers by another.

Please remove Avast with this tool: http://files.avast.com/files/eng/aswclear5.exe

Replace it with MSE: http://www.microsoft.com/security_essentials

If the problem persists, please follow the BSOD Posting Instructions again.

...Summary of the Dumps:

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 09:26:52.187 2010 (UTC - 4:00)
System Uptime: 0 days 1:50:12.639
BugCheck 3B, {c0000005, fffff88005b87a82, fffff88006cf29a0, 0}
Probably caused by : aswMonFlt.sys ( aswMonFlt+4a82 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 07:27:27.853 2010 (UTC - 4:00)
System Uptime: 0 days 1:10:35.304
BugCheck D1, {40000018, 2, 0, fffff8800165fee3}
*** 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+16a6c )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 14:58:59.873 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:32.324
BugCheck 3D, {fffff88002f1adc0, 0, 0, fffff88003d9ef15}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchDdiNotifyInterrupt+3d )
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 14:45:45.549 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:24.000
BugCheck FC, {fffff88005b14684, 8000000116daf121, fffff80000b9c0d0, 0}
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_StartIo+262 )
BUGCHECK_STR:  0xFC
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 10 06:34:26.004 2010 (UTC - 4:00)
System Uptime: 0 days 1:40:47.456
BugCheck 3B, {c000001d, fffff880040653c3, fffff88009d7a940, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DMMVIDPNSOURCE::DMMVIDPNSOURCE+257 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WinSAT.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

canoemoose · Sep 14, 2010

I've removed Avast, however, it now bluescreens when completing the final stages of MSE installation - every time. I've unplugged the network cable for now and am posting this from my Linux box.

More memory dumps etc attached - including the ones posted before.

Jonathan_King · Sep 14, 2010

Uninstall your Realtek network adapter drivers, as they are blamed by your last dump, and seem to have some error in msinfo32.

Install these ones: Realtek

...Summary of the Dumps:

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 13:33:01.304 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.756
BugCheck F4, {3, fffffa8005d914c0, fffffa8005d917a0, fffff80002d7e5d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 13:26:52.764 2010 (UTC - 4:00)
System Uptime: 0 days 3:57:44.841
BugCheck D1, {245c8944, 2, 0, fffff88003e15141}
*** 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+15141 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

canoemoose · Sep 15, 2010

The installer for the drivers you linked to caused a bluescreen, so I downloaded the drivers only and installed them through Device Manager. MSE has now installed successfully.
Memory dump from installer bluescreen attached.

Is it worth running Driver Verifier to see if anything shows up?

Jonathan_King · Sep 15, 2010

Let's wait and see if the bluescreens continue. If they do, enable driver verifier.

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2 (3).zip\Windows_NT6_BSOD_jcgriff2\091510-20280-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Wed Sep 15 04:23:58.101 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:10.553
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff8a003445290, dde000008af46963, fffff8800514a710, 2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42497 )

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

2: kd> KiBugCheckDriver
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for speedfan.sys
*** ERROR: Module load completed but symbols could not be loaded for speedfan.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** WARNING: Unable to verify timestamp for HECIx64.sys
*** ERROR: Module load completed but symbols could not be loaded for HECIx64.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for nvBridge.kmd
*** ERROR: Module load completed but symbols could not be loaded for nvBridge.kmd
*** WARNING: Unable to verify checksum for cdd.dll
Couldn't resolve error at 'iBugCheckDriver'
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a003445290, Virtual address for the attempted execute.
Arg2: dde000008af46963, PTE contents.
Arg3: fffff8800514a710, (reserved)
Arg4: 0000000000000002, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800514a710 -- (.trap 0xfffff8800514a710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c1b3aa10 rbx=0000000000000000 rcx=fffff900c1b3aa78
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a003445290 rsp=fffff8800514a8a8 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffffa800515ea00
r11=fffff900c1afe1c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff8a0`03445290 0202            add     al,byte ptr [rdx] ds:52a0:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0bbcf to fffff80002a8b740

STACK_TEXT:  
fffff880`0514a5a8 fffff800`02b0bbcf : 00000000`000000fc fffff8a0`03445290 dde00000`8af46963 fffff880`0514a710 : nt!KeBugCheckEx
fffff880`0514a5b0 fffff800`02a8982e : 00000000`00000008 00000000`0000031c fffffa80`058fe200 fffffa80`058fe3f0 : nt! ?? ::FNODOBFM::`string'+0x42497
fffff880`0514a710 fffff8a0`03445290 : 00000000`00000000 fffffa80`04469b00 00000000`00000003 fffff900`c01df850 : nt!KiPageFault+0x16e
fffff880`0514a8a8 00000000`00000000 : fffffa80`04469b00 00000000`00000003 fffff900`c01df850 fffff960`000b41d0 : 0xfffff8a0`03445290


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42497
fffff800`02b0bbcf cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42497

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+42497

BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+42497

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

canoemoose · Sep 15, 2010

Well, updating the Realtek drivers seems to have solved the problem - it's been running all day and I've been using it with no problems.
If it does crash again I'll post again with the dumps for you.

Thanks for your help!!

Jonathan_King · Sep 15, 2010

Good, thanks for the report!

Keep us posted if anything new turns up.

canoemoose · Sep 17, 2010

Unfortunately, I return...

I was attempting to install Adobe Reader but launching the installer caused another bluescreen, blaming dxgmms1.sys - something to do with DirectX I think.

I rebooted, and the installer ran fine, but I thought I'd just post the dump here in case there's something else going on I'm unaware of.

Jonathan_King · Sep 17, 2010

Do you have another graphics card you can test out? I almost suspect bad video RAM.

If not, I suggest returning the card back to the place you bought it, and get a new one.

It may also pay to do a RAM test. See this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

...Summary of the Dumps:

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 17 10:56:00.863 2010 (UTC - 4:00)
System Uptime: 0 days 6:23:20.314
BugCheck 50, {fffffa8045cb1350, 1, fffff88004178ad9, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCaptureProcessName+69 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

canoemoose · Sep 17, 2010

I've already run Memtest86+ - see my OP for the results.

The only other PCI-e video card I've got is an ATI Radeon HD5770 - it needs its own power connection, the PSU in the new machine hasn't got one/it's all zip tied tidily away somewhere.
The 9500GT I've got in here is the only non-new component - it's about a year old and was previously in my other desktop. I upgraded to the aforementioned HD5770 and decide to use the then spare 9500GT in this otherwise new build.
Meh. I'm tempted to not do anything and see if the problem happens again. Is there any way of doing the equivalent of a Memtest86 on video RAM?

Jonathan_King · Sep 17, 2010

Sure, you can try Furmark: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Another thing you can try is reseating the video card, and blowing out the PCIe slot with a can of air.

canoemoose · Sep 19, 2010

Unfortunately I return.

The machine bluescreened again just now. I was just browsing the Internet. Is this the same issue as before or something else? Memory dumps attached.

The Furmark test ran fine; I quit it when the temperature levelled out.

Jonathan_King · Sep 19, 2010

I'd really like to see that other video card tested out. Any chance you could crack open that bunch of power cables?

...Summary of the Dumps:

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 06:31:56.461 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:28.912
BugCheck 3B, {c0000005, fffff96000092a4c, fffff88005bd6850, 0}
Probably caused by : win32k.sys ( win32k!bDetermineAlphaBlendFunction+2b4 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

canoemoose · Jan 10, 2011

Hi again.
Having now had some more time, I'm now continuing the troubleshooting.
The previous graphics card died, so has been replaced with a brand new one, no improvements. The PSU has also been swapped out for a slightly more powerful one, with no effect.
I'm going to run Memtest86+ again overnight, but in the meantime I've attached memory dumps going all the way back to my OP.

Jonathan_King · Jan 10, 2011

Hello again,

I see several possible causes, just from the dumps dated November and later.

First, your original theory of a network issue is not eliminated from this batch of dumps. Rt64win7.sys and NETIO.SYS are blamed by two dumps, which are your Realtek Ethernet and Windows networking drivers, respectively. Chrome.exe was the top process in another dump. Try installing these updated drivers:
Realtek

The next cause is your Hauppauge TV card drivers. Try installing newer ones from here: Hauppauge Computer Works : Support

Code:

HCW71364.sys    Fri Jan 15 15:20:45 2010 (4B50CE1D)

If you can't find newer ones, remove the device.

Do run the memory test again. One thing I missed the last time around was that error that was detected; any errors are unacceptable, and should be dealt with.

Beside the Memtest86 test, run Prime95. Run both the Blend and Small FFTs tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Also test your hard drive, with SeaTools.

Finally, let me ask, when did you replace the graphics card? Was it before or after November 5?

...Summary of the dumps:

Code:

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 16:15:10.548 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:06.000
Probably caused by : usbehci.sys ( usbehci!EHCI_NotifyTransferQueueState+6d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_usbehci!EHCI_NotifyTransferQueueState+6d
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 15:59:02.447 2011 (UTC - 5:00)
System Uptime: 0 days 0:07:41.524
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 15:12:20.994 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:48.446
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 15:06:58.836 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:15.913
Probably caused by : usbehci.sys ( usbehci!EHCI_RefAsyncIdle+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_usbehci!EHCI_RefAsyncIdle+56
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan  8 06:30:33.597 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:26.674
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : hardware ( spsys+37345 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  sppsvc.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_spsys.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan  5 05:32:27.535 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:03.002
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+a7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeliverApc+a7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan  3 15:09:18.341 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:50.824
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!EngCopyBits+12e4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!EngCopyBits+12e4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan  3 14:57:19.085 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:26.178
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+122 )
BUGCHECK_STR:  0xc2_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_99_Ntfs!NtfsFullDeleteLcb+122
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 09:00:45.551 2011 (UTC - 5:00)
System Uptime: 0 days 1:17:49.034
*** WARNING: Unable to verify timestamp for HCW71364.sys
*** ERROR: Module load completed but symbols could not be loaded for HCW71364.sys
Probably caused by : HCW71364.sys ( HCW71364+2bdf0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_HCW71364+2bdf0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 07:42:08.907 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:38.000
Probably caused by : hardware ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 07:37:46.539 2011 (UTC - 5:00)
System Uptime: 0 days 1:17:20.022
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSelectContextFromThisPriority+80 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiSelectContextFromThisPriority+80
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan  2 06:19:17.517 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:50.000
Probably caused by : hardware ( usbehci!EHCI_DecPendingTransfer+3b )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_usbehci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 20 11:28:16.786 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:12.253
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+119cf8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 14:22:11.548 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:43.000
Probably caused by : hardware ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+443 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 14 15:55:43.523 2010 (UTC - 5:00)
System Uptime: 0 days 0:21:13.600
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 20 15:35:26.908 2010 (UTC - 5:00)
System Uptime: 1 days 0:11:48.359
*** WARNING: Unable to verify timestamp for HCW71364.sys
*** ERROR: Module load completed but symbols could not be loaded for HCW71364.sys
Probably caused by : HCW71364.sys ( HCW71364+2c4fd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_HCW71364+2c4fd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 15:22:58.303 2010 (UTC - 5:00)
System Uptime: 2 days 23:54:51.755
Probably caused by : ntkrnlmp.exe ( nt!PopFindPowerSettingConfiguration+37 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!PopFindPowerSettingConfiguration+37
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 15:24:14.194 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:31.646
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
BUGCHECK_STR:  0xc0000102
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xc0000102_nt!ExpSystemErrorHandler2+5e1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 15:20:03.903 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:37.355
Probably caused by : hardware ( win32k!GreOffsetRgn+9 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 16:32:42.311 2010 (UTC - 5:00)
System Uptime: 0 days 0:11:32.762
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+3e2303 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+3e2303
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 16:20:31.898 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:49.349
Probably caused by : win32k.sys ( win32k!EvaluateSpline+25a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_win32k!EvaluateSpline+25a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 10 15:05:27.552 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:44.004
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 10 13:39:07.583 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:09.035
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : hardware ( Rt64win7+14786 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_Rt64win7.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 15:29:58.100 2010 (UTC - 5:00)
System Uptime: 0 days 0:09:08.552
Probably caused by : nvlddmkm.sys ( nvlddmkm+58e7c3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+58e7c3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  1 16:16:50.027 2010 (UTC - 5:00)
System Uptime: 0 days 1:14:14.478
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

canoemoose · Jan 11, 2011

Hi,
Memtest reported 66 errors over 20 passes of the whole lot of RAM, so I'm now trying each stick in each channel in order to (hopefully) pinpoint the problem.

I've already tested the hard drive with SeaTools - it's fine.

The graphics card was replaced with a temporary one on 30/12/10, and replaced again with a permanent replacement on 8/1/11.

I'll let you know when I've pinpointed the RAM problem.

Jonathan_King · Jan 11, 2011

That sounds good.

Remember, modern boards usually run in dual or even triple channel configurations. If you need to RMA one stick, RMA the whole kit, to make sure you don't have problems down the road from now.

canoemoose · Jan 11, 2011

After a day of Memtest'ing, I've pinpointed the fault to one memory module. I've raised an RMA request with OCZ and am awaiting developments.

Another BSOD to analyse...

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer