Windows 11 Crashes in Sleep Mode

New Contributor



I have a new Dell Inspiron 15 that came with Windows 11.

I've noticed that if I let Windows 11 install all its updates, at some point it will always crash when I leave it idle in Sleep or Hibernation modes. I don't know which update exactly causes this. I ran Dell Updates to get the latest drivers, but that doesn't seem to help.

I already reset the PC to its factory setup three times and I'm frustrated with this. Anyway, here is the Error and Critical log messages I find in the Event Viewer:


"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000006, 0xffff9b8a2d9d8a40, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3ef4dbc1-5685-4270-8782-43a16abb1335."



"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."


Any idea what could be the reason behind this?



4 Replies
During update installation, it shouldn't go to sleep and Windows will prevent it. So check and make sure you have latest driver and firmware update for your device.
Open start and search for feedback and open the Feedback Hub app and report this issue.
Try disable Sleep and Hibernate and download and install all updates and restart your PC and turn them on and see if the problem persist?

It does go into sleep, or it looks like it does, so please don't say it doesn't.  If you don't know, it's ok to remain silent.  This is a VERY annoying issue with windows 11!


Thank you!



best response confirmed by YasmineRK (New Contributor)
Issue is closed. The problem was the preinstalled Windows image . So I cleaned all partitions and installed a new Windows disk image. I haven't encountered the problem since then.
You misunderstood my comment, when I mentioned it shouldn't go to sleep , I mean this is the expected result and when you are seeing different result, there is something wrong with your system. I am telling this to explain this is NOT a Windows bug but rather issue with your system. Then I shared you some solutions like updating firmware and drivers which I believe you ignore them. However, glad the problem have been fixed.