Solved Driver Power State Failure, ntoskrnl.exe?

[Slartybart]

Ok, great, and good news about best behavoir.
I think yo're saying that things are better, but I want to be sure.

But mon ami, you can be of more help
Did you download / install the driver from my link, reinstall the driver you downloaded before, or use the Nvidia detect?

Did another BSOD occur or are you in the clear for the moment? You attached a diag and describe sluggishness before a BSOD.

Is what you describe something that occurred in the past or is this a new BSOD?

Thanks for the feedback,
Bill
.

What enabled you to update the Nvidia drivers this time? Did you follow the excellent instructions in essenbe's post?
....

I didn't know this post existed. Whatever caused the nvidia driver installer to not recognize the fact that there was a 460M either fixed itself, or this was the correct installer this time. I can't say for certain. Wish I could be of more help.

Also, BSOD. Computer was on its best behavior. Subsequent operations following the BSOD were very slow, sluggish, like it wasn't operating at 100%. Diag attached.

EDIT: I did notice that this particular driver installer replaced the previous versions it was trying to install, so in my instance, the issue of needing to go back and uninstall the previous drivers was nonexistent.

 

[Palladion]

Ok, great, and good news about best behavoir.
I think yo're saying that things are better, but I want to be sure.

But mon ami, you can be of more help
Did you download / install the driver from my link, reinstall the driver you downloaded before, or use the Nvidia detect?

Did another BSOD occur or are you in the clear for the moment? You attached a diag and describe sluggishness before a BSOD.

Is what you describe something that occurred in the past or is this a new BSOD?

Thanks for the feedback,
Bill
.

What enabled you to update the Nvidia drivers this time? Did you follow the excellent instructions in essenbe's post?
....

I didn't know this post existed. Whatever caused the nvidia driver installer to not recognize the fact that there was a 460M either fixed itself, or this was the correct installer this time. I can't say for certain. Wish I could be of more help.

Also, BSOD. Computer was on its best behavior. Subsequent operations following the BSOD were very slow, sluggish, like it wasn't operating at 100%. Diag attached.

EDIT: I did notice that this particular driver installer replaced the previous versions it was trying to install, so in my instance, the issue of needing to go back and uninstall the previous drivers was nonexistent.

Ah, of course. I used the link you provided in the aforementioned post. Worked perfectly. Don't know why the one from earlier in this thread didn't pull through.

And yes, this is a BSOD that occurred today, after the updating of drivers, just a few hours ago as I started a Starcraft 2 match to sort of impromptu stress test my card, since the game seemed to instigate a crash more than anything else.

The drivers for my video card may not have been the solution, but again, thanks to everyone for your help so far. It's been invaluable.

 

[Slartybart]

Thanks for the clarification. I'm not a dump expert by any means, so I'll fire up the bat signal.

Yeah, don't know why the driver worked the 2nd time - not important though.

Bill
.

 

[Palladion]

This.

 

[carwiz]

Uninstall the Intel Management Engine Interface. It's using the same IRQ as your display controller. This is not needed unless you rely on an IT department to maintain your PC. It's a system eating hog that runs all the time. Be sure to re-boot after the uninstall.

If the BSOD 9f continues, uninstall the Daemon tools and see if your problem goes away. It's also hooked to your display.

 

[Palladion]

Done.

 

[Palladion]

Still having problems. Any clues?

 

[carwiz]

Attach the utility output so we can see the latest.

 

[Palladion]

That's... this thing?

 

[Palladion]

Relevant.

http://i46.tinypic.com/xn9ftu.png

EDIT: In typical fashion, a length of slower performance concluded with a BSOD, this time with the computer completely in idle on the desktop, something that has never happened before. This occurred minutes after this initial posting, and after the re-installation and updating of my graphics card drivers. Also, I remember, distinctly, performing a clean install of the graphics card drivers. All of them. I double checked tonight, and my driver versions were quite out of date. After installing the drivers again, my machine seems more on the edge of BSOD than ever.

 

[carwiz]

The MSINFO file is not populated.

Follow these instruction: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Check your installed programs/features and see if Intel Management Engine Interface has been re-installed by Windows automatic updates. If it has, Un-install it and change your update options to Let Me Decide. When it comes back as an update, right click it and select Hide. Do NOT let this software install again. It may also show up in Windows driver updates.

 

[Palladion]

I have read them. I don't know why MSINFO file was not populated. Did the same thing I had several times before. I will try again.

Also, Intel Management Engine Interface is not listed on my installed programs/features.

 

[carwiz]

It looks like the Nvidia drivers you have loaded are not compatable with the motherboard/BIOS. Appearently, you can not use the standard Nvidia drivers from their site. You should be downloading drivers from Dell. I can't remember back but did you check for a BIOS update? The warning below, in red, indicates the driver may not be a valid release.

System Manufacturer: Alienware
System Model: M17xR3
BIOS Version/Date: Alienware A12, 8/20/2012

Also...
MEI is still installed as a system driver and it still appears in memory and the IRQ table.

DRIVER_POWER_STATE_FAILURE (9f)
[COLOR=red]*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[/COLOR]A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800dfd3a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800f6e0260, The blocked IRP
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f48000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
STACK_TEXT:  
fffff800`00b9c388 fffff800`030ff992 : 00000000`0000009f 00000000`00000003 fffffa80`0dfd3a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`0309a94c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`0309a7e6 : fffff880`00f112b0 00000000`00009fc2 00000000`00000000 fffff880`0402f7dd : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0309a6ce : 00000001`7c4a3290 fffff800`00b9cb18 00000000`00009fc2 fffff800`0320fac8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`0309a4b7 : 00000000`4a25a6c2 00000000`00009fc2 00000000`4a25a602 00000000`000000c2 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0308794a : fffff800`0320be80 fffff800`03219cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
Followup: MachineOwner
---------
0: kd> !irp fffffa800f6e0260 1
Irp is active with 4 stacks 2 is current (= 0xfffffa800f6e0378)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800f6e0280
ThreadListEntry.Blink = fffffa800f6e0280
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 = fffffa800f6e02d8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffff80003240b00
Tail.Overlay.ListEntry.Blink = fffff80003240b00
Tail.Overlay.CurrentStackLocation = fffffa800f6e0378
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=red]>[ 16, 2]   0 e1 fffffa800e0c71d0 00000000 fffff880065ae084-fffffa80110a27c0 Success Error Cancel pending
        \Driver\ACPI nvlddmkm
   Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa800f694040 00000000 fffff8000307b750-fffffa8011382c80 Success Error Cancel pending
        \Driver\nvlddmkm nt!IopUnloadSafeCompletion
[/COLOR]   Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800fed08a0    
   Args: 00000000 00000000 00000000 00000000

 

[Palladion]

That's wild. Let me look into it, thanks. Sounds promising.

 

[Palladion]

Going to mark this one as solved. Have not yet had a BSOD since the... proper, drivers were installed for my video card. Thanks everyone.