Question Blue Screen - Driver Power State failure

Toggle sidebar Toggle sidebar
R

risky

Oct 29, 2019
15
0
10
Hey everybody,

I have an issue which I am sadly not able to solve on my own. I get random blue screens, where my computer restarts and then works normal again.
The Error message is: Driver Power State Failure
In the event log the error these are the details:

- <Event xmlns=" ">

- <System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>41</EventID>

<Version>6</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2019-10-29T18:09:00.805641100Z" />

<EventRecordID>6165</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>DESKTOP-4KF8V2A</Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>

<Data Name="BugcheckCode">159</Data>

<Data Name="BugcheckParameter1">0x3</Data>

<Data Name="BugcheckParameter2">0xffffde8d7c494060</Data>

<Data Name="BugcheckParameter3">0xffff8d88e38618b0</Data>

<Data Name="BugcheckParameter4">0xffffde8d7c5c98a0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">0</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">false</Data>

<Data Name="CheckpointStatus">0</Data>

</EventData>

</Event>

I would greatly appreciate any help!

System conf:
AMD Ryzen 5 1500x
Prime B350-Plus
NVIDIA GeForce GTX 1050TI
16 GB RAM (need to check which exactly)
1 SSD (takeMS SSD UTX-PO318 240GB)
3 HDD (2x 2TB, 1x 1TB)
be quiet! Pure Power 11 500W 80+ Gold
 
Last edited:
Sort by date Sort by votes
R

risky

Oct 29, 2019
15
0
10
Maybe some further interesting information
Bios Version/Date = American Megatrends Inc. 4011, 19.04.2018
SMBIOS-Version = 3.1
starting-device = \Device\HarddiskVolume2
Win10 Pro Version 10.0.18362 Build 18362

If you need the error dump, let me know
 
Upvote 0 Downvote
A

axe0axe0

Honorable
Jun 5, 2017
986
37
11,590
The reason I asked all dumps is, you posted a different bugcheck than you mentioned (0x154) for which the parameters are wrong. I simply wanted to check they're all 0x9F crashes because if they weren't things would have changed.

It looks like each crash is caused by the AMD SATA drivers.
I checked the support page of your motherboard and the oldest version is about 2 years newer from the one you have installed.
Where did you get the AMD SATA drivers from?

I would suggest updating your AMD SATA drivers from ASUS.
Code: 
0: kd> lmvm amd_sata
Browse full module list
start             end                 module name
fffff802`54970000 fffff802`5498d000   amd_sata T (no symbols)           
    Loaded symbol image file: amd_sata.sys
    Image path: \SystemRoot\System32\drivers\amd_sata.sys
    Image name: amd_sata.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Mar 19 07:43:08 2015 (550A6FFC)
    CheckSum:         00021C22
    ImageSize:        0001D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
Upvote 0 Downvote
FlaryBartender

FlaryBartender

Nov 1, 2019
45
5
35
Me as a brother of an IT guy i can tell you 3 thing. BSOD is because of RAM, GPU or CPU. In rare cases it could be newly installed drivers/updates to OS or overheating. Ruzen CPU and RAM i think should be OK. The problem could be with your GPU! Try to do something w/no gpu attached to mobo!
Check the CPU temps! OR try using PC with one RAM card at a time! This is all what i can suggest to you at this point.
 
Upvote 0 Downvote
A

axe0axe0

Honorable
Jun 5, 2017
986
37
11,590
I'm sorry to say this, but I strongly disagree with your post. As someone who has been looking into BSOD crashes for the last few years I can tell you that drivers are by far more often the cause of BSOD than hardware. When it comes to hardware, the hard drive is the number 1 cause mostly identified with events from eventviewer, but it is second after drivers.

With 0x9F crashes, it is not uncommon for display drivers to cause crashes, but that's still drivers. If it were to be the actual GPU causing issues, commonly crashes wherein the bugcheck code states something like 'video' occurs.

RAM is actually one of the least potential causes, I have seen RAM cause the problem in less than a couple dozen situations out of hundreds.

The CPU, although by some possibly considered as the last part that should be tested, is actually one that I have seen causing so many more crashes than the RAM. In particular with the whea uncorrectable error (0x124) or machine check exception (0x9C) the CPU has been commonly a good potential cause.

Regarding the GPU itself, I didn't see anything related to dxgkrnl indicating the GPU was somehow involved. Of course, with a minidump one can only really look into the thread that called the bugcheck, some related registers, and with a bit of luck some other interesting things such as memory objects/addresses, but still dxgkrnl I should have seen in the blocked IRP or in the stack to at least be considered.
 
Upvote 0 Downvote
R

risky

Oct 29, 2019
15
0
10
axe0axe0 said:
The reason I asked all dumps is, you posted a different bugcheck than you mentioned (0x154) for which the parameters are wrong. I simply wanted to check they're all 0x9F crashes because if they weren't things would have changed.

It looks like each crash is caused by the AMD SATA drivers.
I checked the support page of your motherboard and the oldest version is about 2 years newer from the one you have installed.
Where did you get the AMD SATA drivers from?

I would suggest updating your AMD SATA drivers from ASUS.
Code: 
0: kd> lmvm amd_sata
Browse full module list
start             end                 module name
fffff802`54970000 fffff802`5498d000   amd_sata T (no symbols)          
    Loaded symbol image file: amd_sata.sys
    Image path: \SystemRoot\System32\drivers\amd_sata.sys
    Image name: amd_sata.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Mar 19 07:43:08 2015 (550A6FFC)
    CheckSum:         00021C22
    ImageSize:        0001D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Click to expand...
First of all thanks a lot for your response! I greatly appreciate your help.
Nevertheless, I tried downloading the driver from the asus homepage (link to the download file)

When I install it, this error pops up
https://gofile.io/?c=JIj67i

What am I doing wrong? I feel sttupid right now - is it only for raid users?
When I go over the device manager, the system cant find an update on its own.

I will also try to update the other drivers!

Thanks again
 
Upvote 0 Downvote
A

axe0axe0

Honorable
Jun 5, 2017
986
37
11,590
I didn't read the description of the AMD SATA driver downloads correctly.
The AMD SATA drivers are for RAID, but that means that the drivers that you should update are in the chipset driver downloads.

I wouldn't suggest using device manager, the chance that it actually updates drivers is pretty slim.
 
Upvote 0 Downvote
A

axe0axe0

Honorable
Jun 5, 2017
986
37
11,590
Cancel the msinfo pop-up, not the script itself. Let the Sysnative tool continue and upload what it collects.

When msinfo takes a long time, it's commonly due to bad maintenance, a slow pc or a pc that's in a bad shape which isn't due to bad maintenance.
Most often it's either a pc that's in a bad shape or a slow pc, the latter wouldn't be surprising though because msinfo provides a lot of information.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom