BSOD driver_power_state_failure when reboot on fresh Windows 10

Hi.

I have driver_power_state_failure issue on my desktop PC (see my specs) which has been running Windows 7 for 4 years without issues, and it also boots Linux Live CDs, USBs and Windows 8 PE from USB without any issues.

I install Windows 10 Pro 64 bit (without activating it yet) just fine, it boots, then it automatically updates its drivers and what not. Then later I do restart after installing some software (I have tried also clean Windows install & reboot without installing anything myself). Then it sits on Restaring screen for 5-10 minutes without any HDD activity (HDD led does not light up) and then shows the BSOD with driver_power_state_failure. It also shows that it is collecting some information.

Then I hard reset it, and it starts booting into diagnostic mode, reports that there's nothing to be fixed and offers to restart. I agree.
And then it just hangs on the Windows logo screen with rotating dots without any hard disk activity at all. I wait for 10-20 minutes and then just hard reboot. No improvement. The system is unbootable.
I tried adding legacy boot menu option from bcdedit in the repair tools and boot to Safe mode - does not boot. Enable boot logging - nothing.
I booted my PC with Linux live cd and inspected the Windows 10 drive for BSOD minidumps - nothing, no Minidump folder. I managed to collect only evtx files from logs.

Darn, Microsoft, why they don't show any clues in the BSOD about the driver which caused the issue?

The only way to install Windows 10 without getting this problem is to disable network. Then after first boot, Windows does not install additional drivers (Device Manager shows some question marks and Basic video driver). It reboots just fine.

My guess is that there is some driver coming from Windows Update causing the issue, but I have no idea how to catch it because there is no additional info in BSOD screen and there is no Minidump, and the BSOD happens only once after installing. On next reboot it just hangs. So I'll have to reinstall Windows (or restore from image) every time I want to reproduce the BSOD....

Do you, guys, have any ideas how to find the buggy driver? Currently I have a clean Windows 10 installed as secondary system and I disabled networking, so it is not yet corrupted with bad drivers. How do I proceed and install them one by one and prevent Windows itself from installing them from Microsoft servers? How to catch the minidump which for some reason is missing?

Thanks for the idea.

I have used HDTune recently to scan my both drives for bad blocks in full scan mode (it took hours). I have Samsung EVO 840 120GB and Seagate 1TB. No errors found.


Now I managed to collect Windows Event Viewer files from my last failed install attempt of Windows 10 and attached them:
Attachment 45865

In System.evtx there are lots of errors:

Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware.

but I have seen them also on my Windows 7 and still it has been working rock solid for years.

I have updated my specs. The SystemInfo tool tried to fill Sound Card section with more info but the browser input field cropped it, and I also could not add missing parts manually. maxlength="100" surely is not enough to enumerate all audio devices in that field...

Thanks for the hint of disabling automatic driver installation, I will try that immediately with disconnected Internet. Also, it seems, Windows 10 has System Restore disabled by default. I'll enable it, and also create a full copy using Paragon Free, and do my best to enable minidumps, and then I'll install drivers one by one until it crashes again, after that hopefully I'll be able to retrieve the dump file.

I reproduced the issue again on a clean Windows install. But before that I cleaned System, Application event logs.

In system recovery settings I disabled automatic restarts and set dump to Small memory dump (256KB) with path %systemRoot%\Minidump and also verified that "Write an event to the system log" is checked.

Then I let Windows to update drivers automatically. After Windows installed everything, I clicked AMD Check for updates button, but it showed that I have the latest version. So, even if AMD drivers are the cause of the issue, I might have no options to fix them.

And the bad news: after I restarted my PC and got the BSOD and booted to my old Windows 7, there is no folder Windows\Minidump on my Windows 10 installation partition (I was careful not to confuse it with my working Windows 7 partition). I even ran full search for *.dmp - nothing. Again, I copied .evtx files and looked into System, but there are only 55 events, and none of them seem to be related to the BSOD.

My guess is that the BSOD happens so late during restart process that some important subsystems might already be shut down, therefore Windows cannot even log the event.

But when the crash happens, I see that Windows is counting percents from 0 to 100% - obviously, it is collecting something but I'm not sure if it is writing the data to disk.

Attached is the new archived package with events collected only during restart and also photo of the BSOD and some screen captures from AMD Catalyst installed automatically by Windows:

Attachment 45912

Not sure, what more can I do to retrieve minidumps. At least now I have captured a restore point and also a full partition image, so I can reliably reproduce the crash.

My current Win10 partition has 20.2 GB free.