Another BSOD to analyse...

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!

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:

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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

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:

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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

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
---------

Good, thanks for the report!

Keep us posted if anything new turns up.