Windows 7: BSOD multiple stop codes seams to happen at random times

jmoser · 10 Sep 2012

I built my computer and I've been getting BSOD's at seemingly random times with a total of probably 5 or 6 different stop codes.

The codes I've managed to see have been 0A, 1E, 7E, 3b and a few I didn't manage to get a look at because i hadn't set my computer to not automatically restart.

I've done multiple scans such as memtest and I've done stress tests on my CPU and GPU. I have also replaced my motherboard and have wiped my hard drive and re-installed windows 7.

I'm pretty sure it's not hardware but I'm not ruling anything out.

I've spent countless hours struggling to figure this out on my own and I've given up because this is over my head.

I attached a zip file with hopefully all the information needed.Attachment 231162

**koolkat77** · 10 Sep 2012

Welcome

There seems to be no zip file attached. Could you please attach it again?

jmoser · 10 Sep 2012

sorry about that its on there now

**koolkat77** · 11 Sep 2012

Thanks

If you have McAfee installed, please uninstall and use MSE

Microsoft Security Essentials - Free Antivirus for Windows McAfee is a known cause of BSODs. Reboot.

Run the system file checker for repairing any damaged windows files

SFC /SCANNOW Command - System File Checker (3 times as well as reboots required)

Uninstall and reinstall your Marvell9x11 drivers (Install latest drivers if there are any)

To make sure that hard drive is good run disk check following this tutorial

Disk Check then Hard drive scan usings
SeaTools

SeaTools | Seagate both long and short tests.

Take your time and post back results

jmoser · 11 Sep 2012

Ok so I've never has McAfee always MSE. I ran the system file checker multiple times with no issues. I uninstalled my Marvell drivers and can't figure out how to reinstall them. I did the disk check which came out clean. When i tried to use SeaTools it told me it couldn't detect my hard drive.

**koolkat77** · 11 Sep 2012

Lets enable driver verifier to rule out buggy drivers

Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Quote: Originally Posted by Capt.Jack Sparrow

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

jmoser · 11 Sep 2012

Alright I have it running now I just wait until a BSOD happens then how do I tell what driver was faulty?

**koolkat77** · 11 Sep 2012

Yup. Operate your computer you normally do, let it stress. If you get blue screens, post them like you did earlier.

jmoser · 11 Sep 2012

Alright here it is hopefully this will be of use.

**koolkat77** · 11 Sep 2012

If you are overclocking any hardware, please stop.

o Download and install |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download
o Reboot the computer in Safe Mode from Advanced Boot Options
o Boot into your computer normally now. Go to your video cards manufacturing website or use option 2 auto detect Drivers - Download NVIDIA Drivers and install the latest drivers for your graphic card.

Once done do a Video Card - Stress Test with Furmark
Video Card - Stress Test with Furmark

Use Speccy to monitor your temp during this test

Post back results

Code:

..............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff87fd4e408a8, 0, fffff8800f495674, 5}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+6b674 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff87fd4e408a8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800f495674, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b7100
 fffff87fd4e408a8 

FAULTING_IP: 
nvlddmkm+6b674
fffff880`0f495674 80bc249803000000 cmp     byte ptr [rsp+398h],0

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ae40380 -- (.trap 0xfffff8800ae40380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f495674 rsp=fffff8800ae40510 rbp=fffff98022c24ff0
 r8=0000000000000008  r9=00000000000000c5 r10=0000000100000000
r11=fffff8800ae404e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x6b674:
fffff880`0f495674 80bc249803000000 cmp     byte ptr [rsp+398h],0 ss:0018:fffff880`0ae408a8=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e2ef0f to fffff80002e881c0

STACK_TEXT:  
fffff880`0ae40218 fffff800`02e2ef0f : 00000000`00000050 fffff87f`d4e408a8 00000000`00000000 fffff880`0ae40380 : nt!KeBugCheckEx
fffff880`0ae40220 fffff800`02e862ee : 00000000`00000000 fffff87f`d4e408a8 fffffa80`0aa50b00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43d51
fffff880`0ae40380 fffff880`0f495674 : 00000000`00000000 fffff980`22c24ff0 fffff880`0ae40920 fffff880`00000700 : nt!KiPageFault+0x16e
fffff880`0ae40510 00000000`00000000 : fffff980`22c24ff0 fffff880`0ae40920 fffff880`00000700 00000000`00000000 : nvlddmkm+0x6b674


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+6b674
fffff880`0f495674 80bc249803000000 cmp     byte ptr [rsp+398h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+6b674

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fb20748

FAILURE_BUCKET_ID:  X64_0x50_VRF_nvlddmkm+6b674

BUCKET_ID:  X64_0x50_VRF_nvlddmkm+6b674

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff87fd4e408a8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800f495674, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  fffff87fd4e408a8 

FAULTING_IP: 
nvlddmkm+6b674
fffff880`0f495674 80bc249803000000 cmp     byte ptr [rsp+398h],0

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ae40380 -- (.trap 0xfffff8800ae40380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f495674 rsp=fffff8800ae40510 rbp=fffff98022c24ff0
 r8=0000000000000008  r9=00000000000000c5 r10=0000000100000000
r11=fffff8800ae404e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x6b674:
fffff880`0f495674 80bc249803000000 cmp     byte ptr [rsp+398h],0 ss:0018:fffff880`0ae408a8=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e2ef0f to fffff80002e881c0

STACK_TEXT:  
fffff880`0ae40218 fffff800`02e2ef0f : 00000000`00000050 fffff87f`d4e408a8 00000000`00000000 fffff880`0ae40380 : nt!KeBugCheckEx
fffff880`0ae40220 fffff800`02e862ee : 00000000`00000000 fffff87f`d4e408a8 fffffa80`0aa50b00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43d51
fffff880`0ae40380 fffff880`0f495674 : 00000000`00000000 fffff980`22c24ff0 fffff880`0ae40920 fffff880`00000700 : nt!KiPageFault+0x16e
fffff880`0ae40510 00000000`00000000 : fffff980`22c24ff0 fffff880`0ae40920 fffff880`00000700 00000000`00000000 : nvlddmkm+0x6b674


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+6b674
fffff880`0f495674 80bc249803000000 cmp     byte ptr [rsp+398h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+6b674

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fb20748

FAILURE_BUCKET_ID:  X64_0x50_VRF_nvlddmkm+6b674

BUCKET_ID:  X64_0x50_VRF_nvlddmkm+6b674

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f42a000 fffff880`101ec000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 15 13:35:36 2012 (4FB20748)
    CheckSum:         00DA5E91
    ImageSize:        00DC2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Windows 7: BSOD multiple stop codes seams to happen at random times

BSOD multiple stop codes seams to happen at random times problems?