Random BSODs

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c9f24e, fffff8800f3ccab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSignalSynchronizationObject+4e )

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

You may try "0x0000003B" Stop error when you run certain applications in Windows 7 or in Windows Server 2008 R2

If applying it does not change change the situation, .........

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002cde1bc, fffff88003d327e8, fffff88003d32040}

Probably caused by : memory_corruption ( nt!MiSegmentDelete+a1 )

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

This crash dump is not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results, with the subsequent crash dumps, if any.

Yes, it is needed, coz the two crash dumps are not providing any information.

Two will be enough :)

Here are the reports of the two crashes. From the first one ....

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffff80002e5fcc0, 0}

*** 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+1b804a )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80002e5fcc0
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

LAST_CONTROL_TRANSFER:  from fffff80002d3580a to fffff80002cdefc0

STACK_TEXT:  
fffff800`00b97008 fffff800`02d3580a : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`02e5fcc0 : nt!KeBugCheckEx
fffff800`00b97010 fffff800`02d7acd5 : 00000000`00000000 fffffa80`0848f290 00000000`00000003 fffff800`02d09bcb : nt! ?? ::FNODOBFM::`string'+0x4874
fffff800`00b97050 fffff800`02d98ded : fffff800`00b97000 fffff800`00b9d000 00000000`00000003 fffff800`02d09e20 : nt!RtlEnoughStackSpaceForStackCapture+0x15
fffff800`00b97080 fffff800`02d99c8b : 00000000`00000005 fffffa80`0848f320 00000000`00000000 fffff880`0604d04a : nt!RtlWalkFrameChain+0x4d
fffff800`00b970b0 fffff800`0317215f : fffffa80`0848f318 00000000`00000080 00000000`00002710 00000000`4d52564e : nt!RtlCaptureStackBackTrace+0x4b
fffff800`00b970e0 fffff800`03176365 : 00000000`00000000 00000000`00000258 00000000`00000080 00000000`00002710 : nt!ViFaultsTracesLog+0x5f
fffff800`00b97110 fffff800`03176629 : 00000000`00000001 00000000`00000080 00000000`00000001 fffff800`03175082 : nt!VfFaultsInjectResourceFailure+0xe5
fffff800`00b97140 fffff800`03176af6 : 00000000`4d52564e 00000000`00000080 00000000`00000040 00000000`00000080 : nt!VfFaultsInjectPoolAllocationFailure+0x169
fffff800`00b97190 fffff800`03176f0d : 00000000`00000001 fffff800`00b97270 00000000`4d52564e 00000000`00000000 : nt!VeAllocatePoolWithTagPriority+0xe6
fffff800`00b97200 fffff880`0604d04a : fffff800`00b97270 fffff880`0602880c fffff800`00b972d0 fffff880`0607596a : nt!VerifierExAllocatePoolWithTag+0x1d
fffff800`00b97240 fffff800`00b97270 : fffff880`0602880c fffff800`00b972d0 fffff880`0607596a 00000000`00000000 : nvlddmkm+0x1b804a
fffff800`00b97248 fffff880`0602880c : fffff800`00b972d0 fffff880`0607596a 00000000`00000000 fffff800`00000002 : 0xfffff800`00b97270
fffff800`00b97250 fffff800`00b972d0 : fffff880`0607596a 00000000`00000000 fffff800`00000002 fffff800`00b972d0 : nvlddmkm+0x19380c
fffff800`00b97258 fffff880`0607596a : 00000000`00000000 fffff800`00000002 fffff800`00b972d0 fffff880`0604d110 : 0xfffff800`00b972d0
fffff800`00b97260 00000000`00000000 : fffff800`00000002 fffff800`00b972d0 fffff880`0604d110 fffff800`00b97338 : nvlddmkm+0x1e096a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1b804a
fffff880`0604d04a ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  nvlddmkm+1b804a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50de9218

FAILURE_BUCKET_ID:  X64_0xc4_91_VRF_nvlddmkm+1b804a

BUCKET_ID:  X64_0xc4_91_VRF_nvlddmkm+1b804a

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05e95000 fffff880`06933000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 12:17:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This particular version (the latest one) is buggy. Uninstall it and apply a known stable earlier version.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search for nVidia elements in Control Panel > Program and features, uninstall them all, one by one.
  * Uninstall the Display Driver the last.
  ** If you use nVidia Chipset, dont uninstall the chipset drivers.
• Then follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

And, from the other one ....

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a12d010, fffff88005426580, ffffffffc0000001, 3}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f580 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a12d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005426580, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

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


FAULTING_IP: 
igdkmd64+f580
fffff880`05426580 48894c2408      mov     qword ptr [rsp+8],rcx

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0939c848 fffff880`052cd004 : 00000000`00000116 fffffa80`0a12d010 fffff880`05426580 ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`0939c850 fffff880`052a0569 : fffff880`05426580 fffffa80`0dec3000 00000000`00000000 fffffa80`0de0a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0939c890 fffff880`052ccdb1 : fffffa80`0a12d010 fffffa80`0a12d010 fffffa80`0a12d010 fffffa80`0de0a410 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`0939c8d0 fffff880`05374fbf : fffffa80`0a12d010 00000000`00000000 00000000`00000000 fffffa80`0de0a410 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`0939c900 fffff880`0539ed7c : fffffa80`00000000 00000000`00007b16 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0939c9e0 fffff880`0539d463 : 00000000`00000102 00000000`00000000 00000000`00007b16 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`0939ca10 fffff880`053702e6 : ffffffff`ff676980 fffffa80`0de0a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0939cab0 fffff880`0539d022 : 00000000`00000000 fffffa80`0d9f0010 00000000`00000080 fffffa80`0de0a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0939cbc0 fffff800`02f6fe5a : 00000000`02d6dcd5 fffffa80`0decab50 fffffa80`084bfb30 fffffa80`0decab50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0939cc00 fffff800`02cc9d26 : fffff880`038a5180 fffffa80`0decab50 fffff880`038b00c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0939cc40 00000000`00000000 : fffff880`0939d000 fffff880`09397000 fffff880`0939bbe0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd64+f580
fffff880`05426580 48894c2408      mov     qword ptr [rsp+8],rcx

SYMBOL_NAME:  igdkmd64+f580

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50c92472

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys

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

4: kd> lmvm igdkmd64
start             end                 module name
fffff880`05417000 fffff880`059321a0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Dec 13 06:12:26 2012 (50C92472)
    CheckSum:         0051BB58
    ImageSize:        0051B1A0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

For it, follow STOP 0x116: VIDEO_TDR_ERROR troubleshooting.

wisecraker1 said:

Is it possible that all the crashes are video driver related?

Not possible, but fact.

4 BSOD's in about an hour.
Followed all the steps for 306.23 installation. Then re-installed it as well after the first crash just to be sure.
As usual, after all BSOD's I ran sfc/scannow to make sure system files are OK.


EDIT:
On boot I get an error message with something along the lines of: Failed to initialize DirextX 9.