Windows 10: Random reboots after bug checks

After a fresh install of Windows 10 Education 10.0.19045 Build 19045 I encountered random BSOD. Tried multiple attempts to figure out the problem. Attempted Driver Verifier but it crashed my system and I had to reinstall! Still having the same issue. Drivers seem to be up to date. Thought it was Chrome when playing audio or video, but the problem occurred in MS Edge, too, even after reinstalling Chrome. When I attempt to access minidumps it tells me I don't have permission even though I am the administrator on the computer. I had to change permissions manually to even load it into debug

:)

 

Random Reboots

I've had, as the title suggests, random reboots for the length of the time since I've built my computer (2 years roughly) and they're completely inexplicable.

It happens under no load, high load, watching movies, listening to music, playing games, browsing the web, sitting by itself in the room when the my sleeping monitor is even saying WTF?!

There aren't any Events to view other than the usual 0xC*D event when the service just shrugs at me.

Any thoughts or suggestions? Maybe someone has had the same problem before and it was just a loose molex connection? I'm baffled.

 

Reboots possibly due to Bug Check

Update - I am marking this thread as Solved since my computer has stopped rebooting in the middle of the night. I am not sure what the cause was or why the reboots stopped. I did uninstall and reinstall the Intel iGPU driver and have since updated the driver to v30.0.101.1994 which was released on May 14, 2022.

Based on review of Event Viewer, I thought the reboots may have been caused by a Bug Check event but MrPepka suggested it was the Intel UHD 630 graphics driver. I assume he determined this by reviewing the DMP files I provided.

Thank you MrPepka

 

Win random reboot from bug check.

MSI GT75 8RF, W10 keeps rebooting from Bug Check.
What is wrong and how do I fix it?

Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffa80d42c69800, 0xffffc980ea89f7d0, 0xffffa80db1405840). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: ca728076-d30a-40ee-b154-fb936eb76e2c.

Memory.dmp is 2.71 GB! ... How do I get this fixed?

**UPDATE**
DL 'Who Crashed v6.01'
Will post back with results.



Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 2018-08-27 6:29:19 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082718-30593-01.dmp
This was probably caused by the following module: Unknown (0xFFFFA80DB1405840)
Bugcheck code: 0x9F (0x3, 0xFFFFA80D42C69800, 0xFFFFC980EA89F7D0, 0xFFFFA80DB1405840)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_POWER_STATE_FAILURE

There are 4 of these, all the same
+1 ...

On Sat 2018-08-18 7:19:33 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081818-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x9F (0x3, 0xFFFFD404D4E6F800, 0xFFFFE48BAA6BF7D0, 0xFFFFD404D7318C10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion
5 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


**************************************************************************************************** ***********************************************

I have a BIOS update for this new notebook that isn't installed.
I think this has to do with the notebook not sleeping, and /or the power button on long press not shutting down the notebook.
Will do the bios update and report back if it happens again.

Got something to add, please post it.