[SOLVED] Windows 11 Sleep BSOD

Status
Not open for further replies.

roieco

Reputable
Dec 4, 2020
128
1
4,595
hi there,

my system is as specified in my signature.
i've been using sleep often with Windows 10 with no issue.

ever since I've upgraded to Windows 11, I've noticed two new phenomena:
  1. it takes windows significantly more time to go into sleep
  2. sometimes, usually after i've been using the pc for some time, the monitors would turn of, and after a long time the computer would turn off completely (with an invisible BSOD, as the monitors are off)
Code:
==================================================

Dump File         : 102421-6234-01.dmp

Crash Time        : 24/10/2021 15:48:21

Bug Check String  :

Bug Check Code    : 0x00000133

Parameter 1       : 00000000[ICODE]00000001

Parameter 2       : 00000000[/ICODE]00001e00

Parameter 3       : fffff807[ICODE]71505330

Parameter 4       : 00000000[/ICODE]00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+415590

File Description  :

Product Name      :

Company           :

File Version      :

Processor         : x64

Crash Address     : ntoskrnl.exe+415590

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\102421-6234-01.dmp

Processors Count  : 16

Major Version     : 15

Minor Version     : 22000

Dump File Size    : 6,807,620

Dump File Time    : 24/10/2021 16:35:36

==================================================



any help would be appreciated.
 
Some hardware did not respond to the sleep request and after 2 minutes the windows watchdog timer called a bug check. For this case, your best bet is to look in the windows event log to see if you can find a entry to tell you what the device is. You could also guess and just go to your motherboard vendors website and update drivers like the blue tooth driver /wifi driver. (often a failure point)
 

roieco

Reputable
Dec 4, 2020
128
1
4,595
Some hardware did not respond to the sleep request and after 2 minutes the windows watchdog timer called a bug check. For this case, your best bet is to look in the windows event log to see if you can find a entry to tell you what the device is. You could also guess and just go to your motherboard vendors website and update drivers like the blue tooth driver /wifi driver. (often a failure point)

Looked atevent viewer, no clue there. Also the wifi and bt are on latest driver version
I will try to turn off devices and report.
 

Colif

Win 11 Master
Moderator
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

hardly ever saw DPC errors before the last few months... hmm
often caused by audio drivers, but thats not always. Seen them caused by LAN drivers or even the actual CPU in one case.
 

Endre

Reputable
hi there,

my system is as specified in my signature.
i've been using sleep often with Windows 10 with no issue.

ever since I've upgraded to Windows 11, I've noticed two new phenomena:
  1. it takes windows significantly more time to go into sleep
  2. sometimes, usually after i've been using the pc for some time, the monitors would turn of, and after a long time the computer would turn off completely (with an invisible BSOD, as the monitors are off)
Code:
==================================================

Dump File         : 102421-6234-01.dmp

Crash Time        : 24/10/2021 15:48:21

Bug Check String  :

Bug Check Code    : 0x00000133

Parameter 1       : 00000000[ICODE]00000001

Parameter 2       : 00000000[/ICODE]00001e00

Parameter 3       : fffff807[ICODE]71505330

Parameter 4       : 00000000[/ICODE]00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+415590

File Description  :

Product Name      :

Company           :

File Version      :

Processor         : x64

Crash Address     : ntoskrnl.exe+415590

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\102421-6234-01.dmp

Processors Count  : 16

Major Version     : 15

Minor Version     : 22000

Dump File Size    : 6,807,620

Dump File Time    : 24/10/2021 16:35:36

==================================================



any help would be appreciated.

Hello!

Did you install Win11 clean, or was it an update from Win10?

If it was an update from Win10, then you should try re-installing Win11 clean (format partition C at setup).

I hope this helps...
 

roieco

Reputable
Dec 4, 2020
128
1
4,595
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
hardly ever saw DPC errors before the last few months... hmm
often caused by audio drivers, but thats not always. Seen them caused by LAN drivers or even the actual CPU in one case.

hey all!

thank you for your responses.
  1. here is a link to the minidumps: https://we.tl/t-n7aOMPyAa1
  2. it is an upgrade from win10
  3. i tried disabling my wifi and lan - didnt help
  4. i notice that it happens more after the computer was in use for some time - if i just turn it on it goes to sleep fine most of the times
 

roieco

Reputable
Dec 4, 2020
128
1
4,595
Okay the issue is now resolved.
The problem was with the definition of one of the bitlocker enabled storage drives, which didnt turn off whe the computer went into sleep and didnt respond to config changes.

At the end I did a re install of windows 11 (preserving progs, data and config) and that resolved the problem.
 
Last edited:
Status
Not open for further replies.