Question DRIVER_POWER_STATE_FAILURE BSOD

[Barty1884]

Hi all,

Yesterday and today, upon first boot/log in I'm met with the a BSOD with the above description.

Using DriverView I determined my NIC driver was a bit out of date, so have updated that now. Unfortunately, if yesterday was anything to go by, I can't replicate the BSOD on demand, so not sure if it's worked or not.

Can anybody decipher the DMP file for me? Hopefully it gives more of an indication....

DMP fIle: https://drive.google.com/file/d/14w2iOWieTy3V7wAM4DeZR-OZNQeTjSZm/view?usp=sharing

Thanks

 

[Colif]

unless you turned fast startup off (like I suggested in discord), you should be able to replicate it just by turning pc off and restarting, as that is same action as you go through at start of new day. PC with fast startup on isn't off when you shut it down, its in a hybrid hibernate state, Its that fact that messes with older drivers that assume PC was off when you start them up again.

I have sent link to gardenman already

 

[onespeedbiker]

The Dump file indicated problem with RAM and/or overheating. First you should check you chassis for a build up of dust, with special attention to the PSU and chassis intake After that run sfc/ scannow and then chkdsk /r at an Administrator level command prompt. If that doesn't solve the problem, you might have a RAM mismatch, meaning your memory has not been paired or one of your RAM sticks is failing.

 

[Barty1884]

unless you turned fast startup off (like I suggested in discord), you should be able to replicate it just by turning pc off and restarting, as that is same action as you go through at start of new day. PC with fast startup on isn't off when you shut it down, its in a hybrid hibernate state, Its that fact that messes with older drivers that assume PC was off when you start them up again.

I have sent link to gardenman already

You would think, right? But no, reboots do not replicate the issue.

The Dump file indicated problem with RAM and/or overheating. First you should check you chassis for a build up of dust, with special attention to the PSU and chassis intake After that run sfc/ scannow and then chkdsk /r at an Administrator level command prompt. If that doesn't solve the problem, you might have a RAM mismatch, meaning your memory has not been paired or one of your RAM sticks is failing.

System is clean, temperatures are totally fine. System is not under load when it occurs, nor can I replicate when under load.
Prime95 is stable, haven't ran MemTest in a while to verify the RAM is still ok, but typically RAM is defective from the outset, or fine for decades under normal circumstances. RAM is a matched kit.

Surely the BSOD is suggesting a driver issue conflicting with the power plans?

 

[axe0axe0]

The Dump file indicated problem with RAM and/or overheating. First you should check you chassis for a build up of dust, with special attention to the PSU and chassis intake After that run sfc/ scannow and then chkdsk /r at an Administrator level command prompt. If that doesn't solve the problem, you might have a RAM mismatch, meaning your memory has not been paired or one of your RAM sticks is failing.

May I ask how you found potential problems with the RAM? Because I'm not seeing it at the moment.

It most definitely is not overheating, the current temperature is 303 kelvin which is around 30C or 86F.

ThermalInfo @ 0xffff9a8bbf64d910
  Stamp:         0x00000006  Constant1:  0x00000000  Constant2:   0x00000000
  Period:        0x00000000  ActiveCnt:  0x00000000  MinThrottle: 0x00000000
  OverThrottle:  0x00000000
  Current Temperature:                   0x00000bd6 (303.0K)
  Passive TripPoint Temperature:         0x00000000 (0.0K)
  ThermalStandby TripPoint Temperature:  0x00000000 (0.0K)
  Hibernate TripPoint Temperature:       0x00000000 (0.0K)
  Critical TripPoint Temperature:        0x00000f52 (392.2K)

0x9F with p1 = 0x3 is an issue with a power IRP
Looking into the IRP:

Irp is active with 3 stacks 2 is current (= 0xffff9a8bca314708)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = ffff9a8bca314610
ThreadListEntry.Blink = ffff9a8bca314610
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 = ffff9a8bca314668
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffff8013943fd60
Tail.Overlay.ListEntry.Blink = fffff8013943fd60
Tail.Overlay.CurrentStackLocation = ffff9a8bca314708
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffff9a8bbe820aa0 00000000 00000000-00000000    
           \Driver\nvvhci
            Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9a8bc7da0de0 00000000 fffff8013916d2f0-ffff9a8bcd2fa790 Success Error Cancel pending
           \Driver\xusb22    nt!PopRequestCompletion
            Args: 00051100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff9a8bcd2fa790    

            Args: 00000000 00000000 00000000 00000000

It looks like xusb22 is where the problem started which is an Xbox 360 controller driver.

 

[onespeedbiker]

My bad, I was reading the wrong dump file.

 

[Barty1884]

0x9F with p1 = 0x3 is an issue with a power IRP

It looks like xusb22 is where the problem started which is an Xbox 360 controller driver.

Thanks for this! That would make a whole lot of sense.
I have an XBox One controller, where the wireless adapter doesn't work consistently.... So I've used it wired AND have since started using my Nvidia Shield controller in place of it.

Double-checking now, the XBOne controller shows up as such in Device Manager, but the Shield controller shows as an XBox 360.... so issue likely sits with the Shield controller.

 

[gardenman]

It looks like I'm a little late. I'd listen to what axe says first, but here's the dump info that I got in case you want to look through it: https://pste.eu/p/fZof.html

File information:	MEMORY.DMP (Jul 19 2019 - 09:43:12)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 22 Hour(s), 12 Min(s), and 39 Sec(s)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

 

[Colif]

in some threads I used to wish I got 1 person who could analyse dump files to answer, this one you got 3.

Talk about spoilt