Windows 10: Windows Fast Boot BSOD

I have seeing multiple BSOD related to Fastboot. I've disable the FastBoot option but that did not made much difference. I had windows 10 originally with this issue and updating to Win11 did not fix the issue.WinDbg shows the following:RIVER_IRQL_NOT_LESS_OR_EQUAL d1 An attempt was made to access a pageable or completely invalid address at an interrupt request level IRQL that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000010, memory referenced Arg2: 0000000000000002, IRQL Arg3:

:)

 

ughhh! BSOD on boot

I guess my computer BSOD on boot right before getting to windows. not sure what the problem is though, everything is stable.

It gave me a list of two files in windows that could have caused the problems

 

BSOD DRIVER_POWER_STATE_FAILURE randomly after cold boot/sleep

For the past month I have been getting random BSOD's all with driver power state failure. They happen randomly, usually within the first 5-10 minutes of cold booting or waking my computer. Steps I have taken to attempt to fix the problem:

1. Reinstalled GPU drivers/ tried old drivers
2. Fresh installed Windows 1803, still happened, then fresh installed 1709
3. Disabled Fast Boot

None of these things fixed the issue, any help would be much appreciated at pinpointing the issue. Thanks

 

laptop doesnt boot automatically

This is what happened.

1. Did a repair install and later disabled hibertnate in CMD.
2. Enabled legacy option ROM in BIOS.
3. After a few times startup ( i used the system in such mode for 5 days), changed boot option back to default.
4. Vola!! It boots automatically to win10 without any keypress. Tested it with many starts to confirm the same.
5. Re-enabled hibernate option using CMD and later selected Fast Startup.
6. System booted normally, without the need for any keypress.

I do not know exactly whether such steps resolved the problem or what else happened, hence cannot suggest above steps.

Many thanks to all members who helped to troubleshoot problems.