Windows 10: New PC, Bluescreens with "DRIVER POWER STATE FAILURE"

Hello,

Just finished building a brand new PC and I am experiencing occasional Blue Screens which seem to occur within a few minutes after I start the PC. After I crash and restart I don't seem to have any issues, but this is happening every 2-3 days.

So far I have tried all the following without any luck:
1. Run SFC/scannow 3 times, nothing found/fixed
2. Run CHKDSK on OS drive, no issues
3. Check device manager for any issues (yellow exclamation marks), none found
4. All suggestions at this tomshardware link.
5. Check system events for critical errors. I have found some but do not understand them. Here is an image of some right before and after one of the blue screens:
Attachment 152095

PC specs:
Windows 10 Pro 64 Bit
AMD R5-1600 (Currently at stock)
Scythe Fuma
AMD RX 570 Sapphire Nitro 8GB (stock) (Latest Driver: 17.8.2)
G.Skill RipJaws 2X8GB DDR4 3200 (Currently at 2133 & 15-15-15-36 1T)
Asrock AB350M Pro 4 Micro ATX Motherboard
MydigitalSSD BPX 240GB M.2 SSD (OS Drive)
2X Seagate Barracuda 1TB 2.5" 5400 RPM HDD's in RAID 1 via RAIDXpert 2
Bitfenix Prodigy M Cobalt
EVGA Supernova 550 G3

I have attached the latest minidump from the blue screen, and have more if they are needed.
Attachment 152102
Attachment 152097

Any help is greatly appreciated.

:)

 

Windows 10 Bluescreen

my blue screen and stop code driver power state failure

 

Error 0xdead039e BSOD

My Lenovo Yoga 2 Pro also produces this bluescreen error on a Windows 10 Home Version 1511 system. But it started with a bluescreen "Driver Power State Failure". I then updated a couple of drivers in the device manager (amongst which Intel(R) HD Graphics
Family to version 10.18.15.4279 and Realtek High Definition Audio to version 6.0.1.7548). Now I got this 0xdead039e error. Unfortunately, I have no idea whether this might be related to the driver update(s) I made.

 

See posting instructions: BSOD - Posting Instructions - Windows 10 Forums

 

Fixed, my bad!! *Redface

 

Hi Ocman76 .

There were no mini dump files collected by our DM log collector.
The event logs display many bsod with bugchecks.
1) How were you able to find and save the mini dump file?
2) Was it accidentally deleted?
3) Were you using Ccleaner or any other method that could delete dmp files?
4) Had you recently ran disk clean up?


5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /restorehealth
8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

9) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

10) Find a replacement driver for rcraid.sys: AMD-RAID Controller
Download Drivers
Updating a driver: https://answers.microsoft.com/en-us/...=1436753520149

11) open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours so plan to run overnight.

12) post the chkdsk results from file explorer using the information in this link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

13) Run HDTune:
HD Tune website

to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark including the following:
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

14) Using file explorer > this PC > local C drive > right upper corner search > look for:
%SystemRoot%\MEMORY.DMP
or
C:\Windows\MEMORY.DMP
Using one drive or drop box post a share link into the thread.

15) Run Sea tools for windows on your drive using SMART, short and long generic tests:

How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/




Windows Trusted Platform Module Management Step-by-Step Guide



Code: rcraid rcraid rcraid Kernel Boot Running OK TRUE FALSE 0 483,328 0 2016-11-08 7:49:48 AM C:\WINDOWS\system32\drivers\rcraid.sys[/quote] Code: Name AMD-RAID Controller [storport]Manufacturer Advanced Micro Devices, Inc. Status OK PNP Device ID {54CB850D-A731-8590-0628-1992592BD448}\RCBOTTOM\5&C2D70D1&0&196607 Driver c:\windows\system32\drivers\rcraid.sys (8.1.0.26, 514.38 KB (526,728 bytes), 2017-07-30 6:30 PM)[/quote] Code: Name AMD-RAID Controller [storport]Manufacturer Advanced Micro Devices, Inc. Status OK PNP Device ID {54CB850D-A731-8590-0628-1992592BD448}\RCBOTTOM\5&2316737C&0&131071 Driver c:\windows\system32\drivers\rcraid.sys (8.1.0.26, 514.38 KB (526,728 bytes), 2017-07-30 6:30 PM)[/quote] Code: rcraid rcraid c:\windows\system32\drivers\rcraid.sys Kernel Driver Yes Boot Running OK Severe No Yes[/quote]

Code: BugCheck 9F, {3, ffff8e00af81e060, ffffba805fab78f0, ffff8e00ae6af010} *** WARNING: Unable to verify timestamp for rcraid.sys *** ERROR: Module load completed but symbols could not be loaded for rcraid.sys Probably caused by : rcraid.sys[/quote]
Code: 2017-08-01 5:49 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff80e951c5d39 P4: ffff9a81a4675ec8 P5: ffff9a81a4675710 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\073117-5875-01.dmp \\?\C:\Windows\Temp\WER-6609-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2172.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_9a2e3d34a61e37a6f348bb57c4332f621a78da8_00000000_cab_1f0c4cc8 Analysis symbol: Rechecking for solution: 0 Report Id: 750eaa8a-4e5b-4e96-99b7-b0978fb1a483 Report Status: 2049 Hashed bucket:2017-08-01 5:48 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff80e951c5d39 P4: ffff9a81a4675ec8 P5: ffff9a81a4675710 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\073117-5875-01.dmp \\?\C:\Windows\Temp\WER-6609-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2172.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_9a2e3d34a61e37a6f348bb57c4332f621a78da8_00000000_02c82172 Analysis symbol: Rechecking for solution: 0 Report Id: 750eaa8a-4e5b-4e96-99b7-b0978fb1a483 Report Status: 4 Hashed bucket:2017-08-23 11:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff80046d41f060 P4: ffffe401d8b378f0 P5: ffff80046cf6f010 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082317-18171-01.dmp \\?\C:\Windows\Temp\WER-20406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57B5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_19f8e05fa46abb5875e64b3d8d5639d03ea09bf7_00000000_cab_1838597a Analysis symbol: Rechecking for solution: 0 Report Id: c7813a44-8df0-4be8-b3a6-5f7a3ef8dc1d Report Status: 2049 Hashed bucket:2017-08-23 11:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff80046d41f060 P4: ffffe401d8b378f0 P5: ffff80046cf6f010 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082317-18171-01.dmp \\?\C:\Windows\Temp\WER-20406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57B5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_19f8e05fa46abb5875e64b3d8d5639d03ea09bf7_00000000_038057e4 Analysis symbol: Rechecking for solution: 0 Report Id: c7813a44-8df0-4be8-b3a6-5f7a3ef8dc1d Report Status: 4 Hashed bucket:2017-08-16 11:37 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff8a86c9a1e060 P4: ffffb581fce2d8f0 P5: ffff8a86ce1e5630 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081617-10515-01.dmp \\?\C:\Windows\Temp\WER-12343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38E2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38F3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_c198f78ac19413fcc5ea91343cfb888a2b22d119_00000000_cab_15a4398e Analysis symbol: Rechecking for solution: 0 Report Id: ee49ea46-9fe0-4d00-8e08-0589f890fff9 Report Status: 2049 Hashed bucket:2017-08-16 11:37 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff8a86c9a1e060 P4: ffffb581fce2d8f0 P5: ffff8a86ce1e5630 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081617-10515-01.dmp \\?\C:\Windows\Temp\WER-12343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38E2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38F3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_c198f78ac19413fcc5ea91343cfb888a2b22d119_00000000_035038f2 Analysis symbol: Rechecking for solution: 0 Report Id: ee49ea46-9fe0-4d00-8e08-0589f890fff9 Report Status: 4 Hashed bucket:2017-09-05 9:45 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff8e00af81e060 P4: ffffba805fab78f0 P5: ffff8e00ae6af010 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090517-18015-01.dmp \\?\C:\Windows\Temp\WER-20031-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5880.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER589F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58B0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_f9e263eb1ba34d391b88c7a4c05819c3b91f50_00000000_cab_20645bac Analysis symbol: Rechecking for solution: 0 Report Id: b1df83c6-9f90-4d8a-b59b-95b1a1708329 Report Status: 2049 Hashed bucket:2017-09-05 9:45 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff8e00af81e060 P4: ffffba805fab78f0 P5: ffff8e00ae6af010 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090517-18015-01.dmp \\?\C:\Windows\Temp\WER-20031-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5880.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER589F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58B0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_f9e263eb1ba34d391b88c7a4c05819c3b91f50_00000000_038c58af Analysis symbol: Rechecking for solution: 0 Report Id: b1df83c6-9f90-4d8a-b59b-95b1a1708329 Report Status: 4 Hashed bucket:2017-08-17 6:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff9d043750f060 P4: fffff80092c5b8f0 P5: ffff9d043c95dc10 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081617-10500-01.dmp \\?\C:\Windows\Temp\WER-12343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3884.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38B4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_e66534b43c63a3395d4970cfb3c38a4946887cbc_00000000_cab_15a43930 Analysis symbol: Rechecking for solution: 0 Report Id: 07878c89-fb79-4a42-8823-6e3714d8e505 Report Status: 2049 Hashed bucket:2017-08-17 6:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff9d043750f060 P4: fffff80092c5b8f0 P5: ffff9d043c95dc10 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081617-10500-01.dmp \\?\C:\Windows\Temp\WER-12343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3884.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38B4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_e66534b43c63a3395d4970cfb3c38a4946887cbc_00000000_034c38b3 Analysis symbol: Rechecking for solution: 0 Report Id: 07878c89-fb79-4a42-8823-6e3714d8e505 Report Status: 4 Hashed bucket:2017-08-15 11:22 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb388d4f9c640 P4: ffffc4013eaad8f0 P5: ffffb388daf3c010 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081517-9359-01.dmp \\?\C:\Windows\Temp\WER-11234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44F8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4546.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4557.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_4a8467f1da96c43252122dd5457efb52e96eb74_00000000_cab_035045e2 Analysis symbol: Rechecking for solution: 0 Report Id: 9b87572d-6707-4a90-959a-34f91fa92dd6 Report Status: 2049 Hashed bucket:2017-08-15 11:22 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb388d4f9c640 P4: ffffc4013eaad8f0 P5: ffffb388daf3c010 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081517-9359-01.dmp \\?\C:\Windows\Temp\WER-11234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44F8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4546.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4557.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_4a8467f1da96c43252122dd5457efb52e96eb74_00000000_035c4556 Analysis symbol: Rechecking for solution: 0 Report Id: 9b87572d-6707-4a90-959a-34f91fa92dd6 Report Status: 4 Hashed bucket:2017-08-23 12:19 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb38d949e8060 P4: fffff8029287b8f0 P5: ffffb38d9993d610 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082217-7812-01.dmp \\?\C:\Windows\Temp\WER-9625-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DB7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DD6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DE7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_58af9c6182811fb37adf7bb186341d08945b949_00000000_cab_13803018 Analysis symbol: Rechecking for solution: 0 Report Id: 74d8d08d-b0ab-463b-b284-bb3ed89a4c41 Report Status: 2049 Hashed bucket:2017-08-23 12:19 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb38d949e8060 P4: fffff8029287b8f0 P5: ffffb38d9993d610 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082217-7812-01.dmp \\?\C:\Windows\Temp\WER-9625-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DB7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DD6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DE7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_58af9c6182811fb37adf7bb186341d08945b949_00000000_03602de6 Analysis symbol: Rechecking for solution: 0 Report Id: 74d8d08d-b0ab-463b-b284-bb3ed89a4c41 Report Status: 4 Hashed bucket:2017-08-18 6:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb603d561f060 P4: ffff8e81047378f0 P5: ffffb603dbc17260 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081717-8843-01.dmp \\?\C:\Windows\Temp\WER-10671-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER320C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER322B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER323C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_8fd823aefe393742dd0c6566283dc765984b_00000000_cab_14a8341f Analysis symbol: Rechecking for solution: 0 Report Id: 9aa840ad-4ff2-45d5-b7ab-3758435aa708 Report Status: 2049 Hashed bucket:2017-08-18 6:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb603d561f060 P4: ffff8e81047378f0 P5: ffffb603dbc17260 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081717-8843-01.dmp \\?\C:\Windows\Temp\WER-10671-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER320C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER322B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER323C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_8fd823aefe393742dd0c6566283dc765984b_00000000_033c324b Analysis symbol: Rechecking for solution: 0 Report Id: 9aa840ad-4ff2-45d5-b7ab-3758435aa708 Report Status: 4 Hashed bucket:2017-08-26 7:34 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffda860f21e060 P4: ffffc5012b1f88f0 P5: ffffda861272e980 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082617-18078-01.dmp \\?\C:\Windows\Temp\WER-20156-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5812.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5832.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5842.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_6892f62afade65b886656b605a72c7484fae6693_00000000_cab_12485a16 Analysis symbol: Rechecking for solution: 0 Report Id: 472a6c0e-0b9b-42fd-a4c7-0db160281bcb Report Status: 2049 Hashed bucket:2017-08-26 7:34 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffda860f21e060 P4: ffffc5012b1f88f0 P5: ffffda861272e980 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082617-18078-01.dmp \\?\C:\Windows\Temp\WER-20156-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5812.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5832.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5842.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_6892f62afade65b886656b605a72c7484fae6693_00000000_037c5841 Analysis symbol: Rechecking for solution: 0 Report Id: 472a6c0e-0b9b-42fd-a4c7-0db160281bcb Report Status: 4 Hashed bucket:2017-09-04 9:41 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffe68ff8fb6060 P4: ffffac81413f78f0 P5: ffffe68ffc147960 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090417-9562-01.dmp \\?\C:\Windows\Temp\WER-11687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3827.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3836.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3847.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_6a9accee58fd1e4a827667e99bc21eaff96936_00000000_cab_04fc3d66 Analysis symbol: Rechecking for solution: 0 Report Id: 7da23b10-d5f3-433a-aaeb-af0ab4ea88ce Report Status: 2049 Hashed bucket:2017-09-04 9:41 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffe68ff8fb6060 P4: ffffac81413f78f0 P5: ffffe68ffc147960 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090417-9562-01.dmp \\?\C:\Windows\Temp\WER-11687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3827.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3836.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3847.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_6a9accee58fd1e4a827667e99bc21eaff96936_00000000_037c3846 Analysis symbol: Rechecking for solution: 0 Report Id: 7da23b10-d5f3-433a-aaeb-af0ab4ea88ce Report Status: 4 Hashed bucket:[/quote]
Code: Event[4319]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-08-24T17:07:59.680 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Quentin-Custom-Built-Desktop-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume7.(A device which does not exist was specified.)[/quote] Code: Event[1283]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-07-30T17:48:02.734 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3O3V6DT Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[4302]: Log Name: System Source: Microsoft-Windows-BitLocker-Driver Date: 2017-08-24T17:07:55.062 Event ID: 24680 Task: N/A Level: Error Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: Bootmgr failed to unseal VMK using the TPM[/quote] Code: Event[4320]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-08-24T17:07:59.681 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Quentin-Custom-Built-Desktop-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume7.[/quote] Code: Event[4326]: Log Name: System Source: NTFS Date: 2017-08-24T17:08:00.507 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[/quote] Code: Event[4327]: Log Name: System Source: NTFS Date: 2017-08-24T17:08:00.507 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: {Delayed Write Failed} Windows was unable to save all the data for the file \$Extend\$UsnJrnl:$J:$DATA. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[/quote] Code: Event[4328]: Log Name: System Source: Application Popup Date: 2017-08-24T17:08:00.513 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Quentin-Custom-Built-Desktop-PC Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ffc464b1718 0x7ffc464b1718 0x7ffc464b1718 0x7ffc464b1718[/quote] Code: Event[4356]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-08-26T12:31:29.431 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Quentin-Custom-Built-Desktop-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume8.[/quote] Code: Event[4363]: Log Name: System Source: NTFS Date: 2017-08-26T12:31:30.642 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[/quote] Code: Event[4314]: Log Name: System Source: Disk Date: 2017-08-24T17:07:58.648 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation. Event[4315]: Log Name: System Source: Disk Date: 2017-08-24T17:07:58.648 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation. Event[4316]: Log Name: System Source: Disk Date: 2017-08-24T17:07:58.648 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation. Event[4317]: Log Name: System Source: Disk Date: 2017-08-24T17:07:58.648 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation. Event[4318]: Log Name: System Source: Disk Date: 2017-08-24T17:07:58.648 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.[/quote] Code: Event[4725]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-05T14:44:58.365 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8e00af81e060, 0xffffba805fab78f0, 0xffff8e00ae6af010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b1df83c6-9f90-4d8a-b59b-95b1a1708329.[/quote] Code: Event[4511]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-04T14:41:38.012 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe68ff8fb6060, 0xffffac81413f78f0, 0xffffe68ffc147960). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7da23b10-d5f3-433a-aaeb-af0ab4ea88ce.[/quote] Code: Event[4414]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-26T12:34:49.476 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffda860f21e060, 0xffffc5012b1f88f0, 0xffffda861272e980). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 472a6c0e-0b9b-42fd-a4c7-0db160281bcb.[/quote] Code: Event[4251]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-23T16:52:36.730 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff80046d41f060, 0xffffe401d8b378f0, 0xffff80046cf6f010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c7813a44-8df0-4be8-b3a6-5f7a3ef8dc1d.[/quote] Code: Event[3991]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-22T17:19:16.959 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffb38d949e8060, 0xfffff8029287b8f0, 0xffffb38d9993d610). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 74d8d08d-b0ab-463b-b284-bb3ed89a4c41.[/quote] Code: Event[3091]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-17T23:35:42.042 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffb603d561f060, 0xffff8e81047378f0, 0xffffb603dbc17260). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 9aa840ad-4ff2-45d5-b7ab-3758435aa708.[/quote] Code: Event[2805]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-16T23:17:03.715 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff9d043750f060, 0xfffff80092c5b8f0, 0xffff9d043c95dc10). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 07878c89-fb79-4a42-8823-6e3714d8e505.[/quote] Code: Event[2712]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-16T16:36:58.717 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8a86c9a1e060, 0xffffb581fce2d8f0, 0xffff8a86ce1e5630). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: ee49ea46-9fe0-4d00-8e08-0589f890fff9.[/quote] Code: Event[2529]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-15T16:22:01.470 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Quentin-Custom-Built-Desktop-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffb388d4f9c640, 0xffffc4013eaad8f0, 0xffffb388daf3c010). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 9b87572d-6707-4a90-959a-34f91fa92dd6.[/quote]

 

The file is not present, I just checked and Ccleaner had a default option checked deleting it... *Banghead

Looks like I will have to wait for another crash.

 

Hi Ocman76,

A 9f bugcheck means that the kernel sent a I/O request packet (IRP) to a driver, ordering it to change power states. The problem is that the kernel did not receive a response in a reasonable amount of time (I believe it's over 100 seconds).

The first parameter is 3, meaning that a device is blocking that IRP from completing.

After looking into the specific IRP that was blocked and the device that is blocking it, the AMD Raid controller for your motherboard, rcraid.sys, appears to be the culprit.

I would suggest that you update to the latest release of the AMD Chipset Drivers.

The driver in question:
Code: Name AMD-RAID Controller [storport] Manufacturer Advanced Micro Devices, Inc. Status OK PNP Device ID {54CB850D-A731-8590-0628-1992592BD448}\RCBOTTOM\5&C2D70D1&0&196607 Driver c:\windows\system32\drivers\rcraid.sys (8.1.0.26, 514.38 KB (526,728 bytes), 2017-07-30 6:30 PM)[/quote] The device object:
Code: Device object (ffff8e00af81e060) is for: Cannot read info offset from nt!ObpInfoMaskToOffset \Driver\rcraid DriverObject ffff8e00af9cfac0 Current Irp 00000000 RefCount 0 Type 00000007 Flags 00001050 SecurityDescriptor ffffe488b68b9b30 DevExt ffff8e00af81e1b0 DevObjExt ffff8e00af81ec30 DevNode ffff8e00ace86090 ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT Characteristics (0x00000180) FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) ffff8e00b079b060 \Driver\Disk Device queue is not busy.[/quote] The IRP that was blocked:
Code: Irp is active with 4 stacks 2 is current (= 0xffff8e00ae6af128) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)] 0 0 ffff8e00af81e060 00000000 fffff80bd6757020-ffff8e00b079b5a0 \Driver\rcraid CLASSPNP!ClasspPowerUpCompletion Args: 00000000 00000000 00000000 00000002 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff8e00b079b060 00000000 fffff80bd59c4050-00000000 Success Error Cancel pending \Driver\Disk partmgr!PmPowerCompletion Args: 00051100 00000001 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff8e00b01cb9f0 00000000 fffff803cd94aeb0-ffff8e00b458f8e0 Success Error Cancel pending \Driver\partmgr nt!PopRequestCompletion Args: 00051100 00000001 00000001 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffff8e00b458f8e0 Args: 00000000 00000000 00000000 00000000[/quote]

 

Please modify Ccleaner so that the box for windows > system > memory dumps is un-checked

 

I have already changed this. I see you have posted a large amount of troubleshooting steps, I will start working through them when I have the time and will post back when I can. Thank you for the suggestions!

 

I just installed, thanks for the link. Will let you know if I still experience crashes after this.

 

For the RAID.
Please indicate information about
1) hardware vs software, RAID configuration, etc.
2) whether you had been able to run software tests on the drive while in RAID
3) in case HD tune is unable to test the drive while in RAID are you able to temporarily turn off RAID?
4) In case you are not able to temporarily turn off RAID finding software to test all drives is the goal.
So try HD Sentinel, Sea Tools for Windows (already a step above), HDD scan, etc.
It may not be whether the drives are in or not in RAID but the controller may block the testing.
So see what works by trial and error so that there are tests on all drives.

 

Here are the troubleshooting steps I have been able to get through so far:

1. CMD prompt results:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

2. Windows fast startup had already been disabled by me.
3. I have updated to the latest RAID driver.
4. Chkdsk file attached: Attachment 152253

No crashes recently... I wonder if updating the RAID driver helped?

 

I have not crashed since installing the latest release of the AMD Chipset Drivers.

Seems to me like the problem has been solved, if it reappears I will return to this thread. Thanks for the help everyone *Smile

 

Your welcome.
What progress did you make in testing the drive?