BSODs about once per day; help?

[nietzescher]

Hello,

I recently installed Windows 7 Home Premium on a machine I built myself. I've been having BSODs maybe once every other day; some occur when the machine is under heavy load (Crysis at max settings, etc.), some when the machine is idle. I'm not yet convinced that all the BSODs have a common cause.

Attached is a .rar of the three minidump files I have right now (I had more, but attempted a reformat/reinstall of Windows 7 to try to fix the issues). If anyone could give me some clue as to what might be causing these problems, I would be very appreciative.

Note that the dump that happened on June 19th, 2010 happened during Fallout 3; this one seems to indicate a memory problem. The other two happened while the system was idle, and my extremely uninformed opinion is that they had something to do with networking.

System Specs:

Mobo: ASUS P7P55D-E Pro
Processor: Intel Core i7 2.8 GHz quad-core
4GB RAM
HD: Western Digital 1TB Caviar
Video: ATI Radeon HD 5870
Corsair 750W power supply

 

[CarlTR6]

All three dmps point to hardware issues.

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 18, 0, 0}

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

Followup: MachineOwner

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000018
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iTunes.exe

STACK_TEXT:  
fffff880`068bef68 fffff800`0282cb6e : 00000000`0000001a 00000000`00041287 00000000`00000018 00000000`00000000 : nt!KeBugCheckEx
fffff880`068bef70 fffff800`0287e6ee : 00000000`00000000 fffffa80`0588b000 fffffa80`04e14700 fffffa80`056b3060 : nt! ?? ::FNODOBFM::`string'+0x42be5
fffff880`068bf0d0 fffff800`02986c7f : fffffa80`0588b000 fffffa80`05545330 fffff8a0`07df15f8 fffffa80`0554f0b0 : nt!KiPageFault+0x16e
fffff880`068bf260 fffff800`0282418b : 00000003`00000000 00000000`00004ea7 fffffa80`02220840 fffff880`068bf498 : nt!MiLogPageAccess+0x10f
fffff880`068bf2b0 fffff800`02b98155 : fffff980`036eb000 fffff8a0`0b293b30 00000000`00000001 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2bf28
fffff880`068bf590 fffff800`02899447 : 00000000`012c0000 fffffa80`03cc7df0 00000000`00000000 00000000`01300000 : nt!CcUnmapVacb+0x5d
fffff880`068bf5d0 fffff800`0289f285 : fffffa80`0436fc01 00000000`00b00000 fffffa80`0436fac0 00000000`01300001 : nt!CcUnmapVacbArray+0x1b7
fffff880`068bf660 fffff800`02b9e8d2 : 00000000`00b00000 00000000`01300000 fffff880`068bf730 fffff880`068bf7c0 : nt!CcGetVirtualAddress+0x2c5
fffff880`068bf6f0 fffff880`0129dc48 : fffff880`00000000 00000000`00000005 fffffa80`06803d60 fffffa80`00100001 : nt!CcCopyRead+0x132
fffff880`068bf7b0 fffff880`0104c0c8 : fffffa80`04d22b70 fffffa80`06803cf8 fffffa80`00000000 fffffa80`04d22b01 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`068bf980 fffff880`0104fc2a : fffff880`068bfa50 00000000`0d290003 00000000`0d290000 fffffa80`04d22b00 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`068bf9e0 fffff880`0106d5f0 : fffffa80`04d22b70 00000000`00000000 fffff880`068bfb40 00000000`00100000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`068bfa20 fffff800`02b9f239 : fffffa80`04d22b70 fffff880`00000002 fffffa80`03d08200 fffffa80`04d22b70 : fltmgr!FltpFastIoRead+0x1d0
fffff880`068bfac0 fffff800`0287f853 : 00000000`00009015 00000000`00001160 00000000`00000000 00000000`0927d9ac : nt!NtReadFile+0x417
fffff880`068bfbb0 00000000`74c62dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0821ebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c62dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42be5
fffff800`0282cb6e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42be5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42be5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42be5

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa807a4103a0, 2, 0, fffff88005473d22}

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

Followup: MachineOwner

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa807a4103a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88005473d22, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb90e0
 fffffa807a4103a0 

CURRENT_IRQL:  2

FAULTING_IP: 
MpNWMon+2d22
fffff880`05473d22 48395910        cmp     qword ptr [rcx+10h],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`03369928 fffff800`02a80b69 : 00000000`0000000a fffffa80`7a4103a0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03369930 fffff800`02a7f7e0 : 00000001`0078001f fffffa80`056c6aa0 00000000`00000000 96658701`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03369a70 fffff880`05473d22 : fffffa80`03ceeb60 fffffa80`06b28c01 fffffa80`06b28c01 fffffa80`056c6aa0 : nt!KiPageFault+0x260
fffff880`03369c00 fffffa80`03ceeb60 : fffffa80`06b28c01 fffffa80`06b28c01 fffffa80`056c6aa0 fffffa80`06b28c01 : MpNWMon+0x2d22
fffff880`03369c08 fffffa80`06b28c01 : fffffa80`06b28c01 fffffa80`056c6aa0 fffffa80`06b28c01 fffff880`0547c35a : 0xfffffa80`03ceeb60
fffff880`03369c10 fffffa80`06b28c01 : fffffa80`056c6aa0 fffffa80`06b28c01 fffff880`0547c35a fffffa80`04124370 : 0xfffffa80`06b28c01
fffff880`03369c18 fffffa80`056c6aa0 : fffffa80`06b28c01 fffff880`0547c35a fffffa80`04124370 fffff880`03369c50 : 0xfffffa80`06b28c01
fffff880`03369c20 fffffa80`06b28c01 : fffff880`0547c35a fffffa80`04124370 fffff880`03369c50 fffff880`03369c88 : 0xfffffa80`056c6aa0
fffff880`03369c28 fffff880`0547c35a : fffffa80`04124370 fffff880`03369c50 fffff880`03369c88 fffff880`017159b9 : 0xfffffa80`06b28c01
fffff880`03369c30 fffffa80`04124370 : fffff880`03369c50 fffff880`03369c88 fffff880`017159b9 fffff880`00000070 : MpNWMon+0xb35a
fffff880`03369c38 fffff880`03369c50 : fffff880`03369c88 fffff880`017159b9 fffff880`00000070 fffffa80`04124388 : 0xfffffa80`04124370
fffff880`03369c40 fffff880`03369c88 : fffff880`017159b9 fffff880`00000070 fffffa80`04124388 fffffa80`0687b401 : 0xfffff880`03369c50
fffff880`03369c48 fffff880`017159b9 : fffff880`00000070 fffffa80`04124388 fffffa80`0687b401 00000000`00000000 : 0xfffff880`03369c88
fffff880`03369c50 fffff800`02d7e827 : fffffa80`06aabda0 fffffa80`00000000 fffffa80`04d2c940 fffffa80`03ceeb60 : NETIO!WfpSysTimerPassiveCallback+0x59
fffff880`03369c80 fffff800`02a8e861 : fffff800`02c26500 fffff800`02d7e804 fffffa80`03ceeb60 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`03369cb0 fffff800`02d26a86 : cd8b4500`00008024 fffffa80`03ceeb60 00000000`00000080 fffffa80`03c71890 : nt!ExpWorkerThread+0x111
fffff880`03369d40 fffff800`02a5fb06 : fffff880`03167180 fffffa80`03ceeb60 fffff880`031720c0 3b410000`43d215ff : nt!PspSystemThreadStartup+0x5a
fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`033693c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MpNWMon+2d22
fffff880`05473d22 48395910        cmp     qword ptr [rcx+10h],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  MpNWMon+2d22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MpNWMon

IMAGE_NAME:  MpNWMon.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b0756e6

FAILURE_BUCKET_ID:  X64_0xD1_MpNWMon+2d22

BUCKET_ID:  X64_0xD1_MpNWMon+2d22

Followup: MachineOwner


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {40, c, 1, fffff80002af5300}

Probably caused by : memory_corruption

Followup: memory_corruption


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf90e0
 0000000000000040 

CURRENT_IRQL:  c

FAULTING_IP: 
nt!KeFlushTb+d0
fffff800`02af5300 48895c4b38      mov     qword ptr [rbx+rcx*2+38h],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`033e7728 fffff800`02ac0b69 : 00000000`0000000a 00000000`00000040 00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx
fffff880`033e7730 fffff800`02abf7e0 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`033e7870 fffff800`02af5300 : fffffa80`0595cbb0 fffff800`02ad4aa9 00000000`00000000 fffff800`02ad60c9 : nt!KiPageFault+0x260
fffff880`033e7a00 fffff800`02b7457e : fffffa80`03d01040 00000000`00000002 00000000`00095788 00000000`00000002 : nt!KeFlushTb+0xd0
fffff880`033e7a80 fffff800`02ad64c0 : fffffa80`03d01040 fffff880`033e7ba0 00000000`00000000 00000000`00000000 : nt!MiAttachSession+0xbe
fffff880`033e7ab0 fffff800`02ad584c : 00000000`00000000 fffff880`033e7ba0 00000000`00000001 fffff880`033e7bb0 : nt!MiAttachAndLockWorkingSet+0x100
fffff880`033e7ae0 fffff800`02ad5de2 : 00000000`0000acd2 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt!MiProcessWorkingSets+0x18c
fffff880`033e7b80 fffff800`02ad606f : 00000000`00000008 fffff880`033e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`033e7bd0 fffff800`02d66a86 : fffffa80`03d01040 00000000`00000080 fffffa80`03c71890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`033e7d40 fffff800`02a9fb06 : fffff880`009b1180 fffffa80`03d01040 fffff880`009bc0c0 01caf484`20da96fa : nt!PspSystemThreadStartup+0x5a
fffff880`033e7d80 00000000`00000000 : fffff880`033e8000 fffff880`033e2000 fffff880`033e7710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff80002af5303-fffff80002af533b)
fffff80002af5300  48  89  5c *4b  38  48  8d  05  bc  f9  fd *0b  45  33  c9  48 H.\K8H......E3.H
fffff80002af5310  89  44  24 *1e  48  8b  cf  48  89  6c  24 *9d  48  89  5c  24 .D$.H..H.l$.H.\$
fffff80002af5320  20  e8  2a *dd  fd  ff  44  0f  b6  de  45 *f4  22  c3  4c  8d  .*...D...E.".L.
fffff80002af5330  5c  24  70 *8c  8b  5b  10  49  8b  6b  18 *14  8b  73  20  49 \$p..[.I.k...s I

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption

Looking at your drivers, I found sptd.sys. Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use the driver, sptd.sys, that is notorious for causing BSODs. . Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

After you have done this and reboot, let your system run and see if you get a new BSOD. If you do, please attach it in your next post and we will look further.

 

[nietzescher]

Thanks for the fast response! I have removed sptd.sys, and I'll post again if I get another BSOD.

I was thinking of letting memtest run overnight, just to make sure my RAM is (probably) not the issue. If no memory issues are detected, I'll let my computer run normally and wait for another BSOD. If there's any reason I shouldn't do this, please let me know.

 

[CarlTR6]

You are very welcome.

Either way is fine. Personally, I would bet that sptd.sys is the problem. But you can certainly run memtest over night. It will not hurt anything to do so. Let us know the results if you run it.

 

[jcgriff2]

Be sure to update your Realtek Ethernet driver as well -

[FONT=lucida console]Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)[/FONT]

Realtek driver downloads --> Realtek

Regards. . .

jcgriff2

.

 

[CarlTR6]

Do follow JC's advice.

 

[nietzescher]

Realtek driver has been updated. Thanks, JC!

I forgot to run memtest last night... If/when I get another BSOD, I'll do that, I suppose.

 

[CarlTR6]

Glad you updated the Realtek driver and very glad you have not had another BSOD. Do post back and let us know whether or not you get another BSOD in the next day or so. I am hoping we can mark the thread as solved!

 

[nietzescher]

Well, for the first time in a long time (possibly ever), my computer was able to remain stable for 24 hours, with no reboots (voluntary or otherwise).

If we can make it to this time tomorrow without a crash, I think we can mark this thread as solved. In the meantime, I'll post if I have any disasters. Thanks for your help, Carl and JC!

 

[CarlTR6]

You are very welcome! We are pleased that we are able to help. Do post tomorrow and let us know. You can request that the thread be marked as solved as solved by clicking on the red triangle in the upper right corner of your post and asking the moderators to mark the thread as solved.

 

[nietzescher]

Two days without a BSOD! USA wins their group! It's been a good week so far, and I think we're done here. Massive thanks again for your help, guys.

 

[CarlTR6]

Glad to hear it. And it a good day for the USA, too!!

I am glad we were able to help. I hope you will be blue screen free! Thanks for reporting back.