BSOD - All the time - In game and out

[xAnimalistic]

I've had this problem since I bought this system a year ago. But recently it started happening all the time.

I reformatted and reinstalled windows. Updated my graphics driver to 304.79 and still had the problem. Rolled back the driver. Still had the issue. This zip is from after I rolled back.

Thanks for your knowledge!

 

[FredeGail]

Hello Animalistic and welcome to Sevenforums.

* Since when did you start having these errors?
* Have you installed anything recently? (drivers, hardware or software for instance)
* What's your temperatures just before a crash?

Updating System Specs will give us a better sight of
how your system is put together. It's simply done.

§ Download Speccy
§ |User CP (top of the page)| |Edit System Spec|
§ COPY & PASTE section to section
§ Include Laptop, Desktop information
§ End with |Save Changes|​

´´´´´´´´

BSOD Analyse

Graphics Driver

You had some arguments in your bugcheck code that involves a blocked IRP request. Blocked IRP requests are like some I/O plugin and plugout extensions. Your Nvidia Graphics Driver was involved in this one. Here's all the junk.

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007f8da10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: [COLOR=Red]fffffa800c6a0260, The blocked IRP[/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
0: kd> !irp fffffa800c6a0260 1
Irp is active with 4 stacks 2 is current (= 0xfffffa800c6a0378)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800c6a0280
ThreadListEntry.Blink = fffffa800c6a0280
IoStatus.Status = 00000000
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800c6a02d8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffff80002c34b00
Tail.Overlay.ListEntry.Blink = fffff80002c34b00
Tail.Overlay.CurrentStackLocation = fffffa800c6a0378
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
[COLOR=Orange]>[ 16, 2]   0 e1 fffffa8008066630 00000000 fffff8800f562524-fffffa800ade28b0 Success Error Cancel pending[/COLOR]
          [COLOR=Red] \Driver\ACPI    nvlddmkm[/COLOR]
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 [COLOR=Blue]fffffa800a3e8480[/COLOR] 00000000 00000000-00000000    pending
          [COLOR=Red] \Driver\nvlddmkm
            Args: 00000000 00000001 00000001 00000000[/COLOR]
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80071b98d0    

            Args: 00000000 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
0: kd> !devobj fffffa800a3e8480
Device object (fffffa800a3e8480) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800a3e8450
 \Driver\nvlddmkm DriverObject fffffa8009d873d0
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
DevExt fffffa800a3e85d0 DevObjExt fffffa800a3e8f88 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8008066630 \Driver\ACPI
Device queue is not busy.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
0: kd> !devobj fffffa800a3e8480
Device object (fffffa800a3e8480) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800a3e8450
 \Driver\nvlddmkm DriverObject fffffa8009d873d0
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
DevExt fffffa800a3e85d0 DevObjExt fffffa800a3e8f88 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8008066630 \Driver\ACPI
Device queue is not busy.
0: kd> !drvobj fffffa8009d873d0
fffff80002c34fb0: Unable to get value of ObpRootDirectoryObject
fffff80002c34fb0: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa8009d873d0) is for:
 \Driver\nvlddmkm
Driver Extension List: (id , addr)

Device Object list:
fffffa800b803470: Could not read device object

I recommend you to run a Clean Install of the Graphics Card driver, as it's showing blocked requests in cases like this.

Different culprits pointed towards your NVIDIA Graphics Driver. Driver Sweeper will ensure that you'd have a clean install at the end of the procedure, and by that no leftover files that'd bork the system.

* Make your way to Nvidia Drivers - Download NVIDIA Drivers and download the latest driver for your card, save it to your desktop for instance.
* Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
* Download Driver Sweeper
* Get to safe mode (without network) and search for Driver Sweeper in your rb:
* Select all the Nvidia components and analyse them
* Clean them, head into Windows without internet and install the driver you downloaded previously

**************************Thu Aug 30 06:00:36.568 2012 (UTC + 2:00)**************************
BugCheck 9F, {3, fffffa8007f8da10, fffff80000b9c3d8, fffffa800c6a0260}
Probably caused by : pci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug 30 05:31:23.194 2012 (UTC + 2:00)**************************
BugCheck 9F, {3, fffffa8007f6ea10, fffff800043ae3d8, fffffa8007a1fbd0}
Probably caused by : pci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug 30 04:07:40.537 2012 (UTC + 2:00)**************************
BugCheck 9F, {3, fffffa8007f6ea10, fffff80000b9c3d8, fffffa800ba5b290}
Probably caused by : pci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug 30 03:56:25.069 2012 (UTC + 2:00)**************************
BugCheck 9F, {3, fffffa8009834a10, fffff80000b9c3d8, fffffa800c499a10}
Probably caused by : pci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug 30 03:45:08.693 2012 (UTC + 2:00)**************************
BugCheck 9F, {3, fffffa8007f8ca10, fffff800043a13d8, fffffa800ace8a60}
Probably caused by : pci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Best Regards,
Frederik.

 

[Poimetheus]

Also, it wouldn't hurt to uninstall the driver; and then let Windows auto re-install it.

 

[FredeGail]

The one Windows install is older than one of the Nvidia ones. As long as the Nvidia released ones are digitally signed & WHQL, there's no problem. But yes, it's worth a try.

Best Regards,
Frederik.

 

[Poimetheus]

Agreed. However, the latest release isn't necessarily the most stable.

 

[Vir Gnarus]

Nvidia drivers are involved, but there's no IoStatus for this particular IRP to express an issue that would've caused it to hold up. When that happens, I've found that often it's because some external factor we're not seeing here is holding up this particular IRP, such as a resource being handled by something else that this Nvidia driver is waiting on. Regardless, good job on looking at the held IRP.

As for my personal recommendation, outside what's already been provided, Driver Verifier should be turned on and have it catch a couple more crashes then send to us the new crashdumps. We might have better luck with those. If not, a kernel dump will be necessary for this case.

Though one thing that concerns me is that the person stated they have had this problem since they first bought their PC. There may very well be an underlying hardware failure here that we're not aware of that has been around since initial purchase and is now only starting to flare up.

 

[Poimetheus]

Nvidia drivers are involved, but there's no IoStatus for this particular IRP to express an issue that would've caused it to hold up. When that happens, I've found that often it's because some external factor we're not seeing here is holding up this particular IRP, such as a resource being handled by something else that this Nvidia driver is waiting on. Regardless, good job on looking at the held IRP.

As for my personal recommendation, outside what's already been provided, Driver Verifier should be turned on and have it catch a couple more crashes then send to us the new crashdumps. We might have better luck with those. If not, a kernel dump will be necessary for this case.

Though one thing that concerns me is that the person stated they have had this problem since they first bought their PC. There may very well be an underlying hardware failure here that we're not aware of that has been around since initial purchase and is now only starting to flare up.

This is very true. My Sager/Clevo BSOD'd right out of the box when I had it. I'm a system tech with a lot of resources at my job. Nothing worked to fix it... minus swapping the card.

 

[Vir Gnarus]

Yah, unfortunately most people will not return it or ask for replacement, and instead deal with the occasional problem until it festers and starts getting to a point where it's intolerable. Worst of all, often when that happens the warranty has already been expired or damage has already been done that could've been avoided. If any instability is exhibited from a brand new computer, it's always best to point blame at bad hardware first.

 

[Poimetheus]

Everything aside, a new computer should work right out of the box.