Getting BSOD randomly

z3r010 · 25 Dec 2012

Bah, I only spotted this page lol

clicky · 25 Dec 2012

One last bump before I go to bed

koolkat77 · 25 Dec 2012

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffffa800891b060, 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+1b39c9 )

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: fffffa800891b060
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF8000462CFB0

LAST_CONTROL_TRANSFER:  from fffff8000312780a to fffff800030d0fc0

STACK_TEXT:  
fffff800`04626ff8 fffff800`0312780a : 00000000`000000c4 00000000`00000091 00000000`00000002 fffffa80`0891b060 : nt!KeBugCheckEx
fffff800`04627000 fffff800`0316ccd5 : fffffa80`07fdb000 00000000`00040120 fffff800`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4874
fffff800`04627040 fffff800`0318aded : fffff880`0aaab000 fffff880`0aab4000 00000000`00000000 fffff800`0462cd10 : nt!RtlEnoughStackSpaceForStackCapture+0x15
fffff800`04627070 fffff800`0318bc8b : 00000000`00000001 fffff800`046270f0 00000000`00000000 fffff800`0462cd10 : nt!RtlWalkFrameChain+0x4d
fffff800`046270a0 fffff880`081db9c9 : 00000000`00000000 fffff800`04627130 fffffa80`0665e000 00000000`00040120 : nt!RtlCaptureStackBackTrace+0x4b
fffff800`046270d0 00000000`00000000 : fffff800`04627130 fffffa80`0665e000 00000000`00040120 fffff800`04627150 : nvlddmkm+0x1b39c9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1b39c9
fffff880`081db9c9 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nvlddmkm+1b39c9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

FAILURE_BUCKET_ID:  X64_0xc4_91_nvlddmkm+1b39c9

BUCKET_ID:  X64_0xc4_91_nvlddmkm+1b39c9

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`08028000 fffff880`08b49000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 01 09:24:02 2012 (50B97852)
    CheckSum:         00B0A675
    ImageSize:        00B21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Crashes seem to be happening on your Nvidia Drivers.
Are you overclocking any hardware?
Try going back to a last known stable NVIDIA driver version.

Perform these tests:
Video Card - Stress Test with Furmark

Video Card - Stress Test with Furmark

Monitor your temps with Speccy during these tests

Does you motherboard have onboard VGA? Does it crash there as well?

clicky · 26 Dec 2012

Hey, thank you for your help koolkat77.

I thought that this issue might be related to a bad nvidia driver or a faulty GPU since these green dots appear every time before a BSOD. My GPU is the MSI 560 Ti OC version so don't know if that's the problem. I did try a stress test for 10 minutes and the temps seems to be somewhere around 79-81.

As for the onboard VGA, yes, it does have an onboard VGA, but it never crashed not even once, so don't really know what's causing this. I however did reinstall a new nvidia driver and hopefully this will fix the problem and if it didn't, then maybe it's time to get a new GPU.

koolkat77 · 26 Dec 2012

To be sure the GPU is at fault itself,

Test it on another computer.
Test another monitor.
Test another GPU on your computer.
Make sure the fans/power supply is working properly/not failing.

Good luck.