BSOD after Sleep

Caledon Ken · 20 May 2022

Windows 10 V21H2, 19044.1706

I am experiencing random BSOD's when my machine awakens from sleep. (Say four or five hours but can be longer, like overnight)

I install a new Samsung M.2 970 1 TB on April 6th, 2022.

My first BSOD was May 1, 2022, then May 3, 2022.

At than time I uninstalled Samsung Magician, since two updates ago I was getting failed to initialized occasionally, and I uninstalled a new version of iCue. I ran SFC /scannow and it found and fixed corrupt files.

Things were looking good until today. I woke up machine May 20, 2022 and it BSOD. I had installed the latest version of Samsung Magician on May 13th and those failed to initialize errors appear to be gone. Firmware on all drives up to date.

My BIOS is up to date, V2701. My display drivers are up to date according to Intel's support tool.

I'll leave it at that unless you have questions.

I ran the V2 Collector, link to zip file.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Appreciate any help that can be offered.

zbook · 21 May 2022

Hi Caledon Ken,

Windows Error Reporting (WER) reported BSOD starting 04/06/2022.

That was also the day that you reported in the opening post for the Samsung drive installation.
Other than that I've not seen a cause and effect.

All of the BSOD recorded were bugcheck A0: internal power error

Please perform the following steps:

1) Run:

https://www.tenforums.com/attachment...p_plus_log.bat

Post a share link displaying the commands with results.

2) Open administrative command prompt and type or copy and paste:

msdt.exe -id DeviceDiagnostic
msdt.exe -id PowerDiagnostic
powercfg -h off

For each Windows troubleshooter click view detailed information > post images or share links of the results

3) Make sure that Samsung Magician is up to date:
Samsung Magician Software Download | Samsung Semiconductor Global

Run update software / firmware

For any new BSOD post a new V2 into the newest post.

Code:

Event[2998]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-05-03T08:21:11.0930000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description: 
Windows failed to resume from hibernate with error status 0xC0000001.

Code:

Event[2389]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-05-01T13:50:39.0910000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description: 
Windows failed to resume from hibernate with error status 0xC0000001.

Caledon Ken · 22 May 2022

Thanks zbook.

The first BSOD was the very first boot after installing the new M.2 on April 6/2022. At that time I was using Fast Startup and had made some SATA port changes. The very first boot failed. I restarted and everything was good. I ignored that BSOD.

I have hibernation shut off, I ran that command but will run again.

Code:

Microsoft Windows 10 Pro  Version 21H2 (OS Build 19044.1706)  ==================================================================    
Started on 2022-05-22 at 22:34:16.86             

[SFC /ScanNow]     

Beginning system scan.  This process will take some time.Results:  

Windows Resource Protection did not find any integrity violations. 

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

Started on 2022-05-22 at 22:36:08.02         

[DISM /online /cleanup-image /ScanHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.19041.844Image Version: 10.0.19044.1706  

No component store corruption detected.The operation completed successfully. 

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

Started on 2022-05-22 at 22:40:57.10         [DISM /online /cleanup-image /RestoreHealth] 

Deployment Image Servicing and Management tool

Version: 10.0.19041.844Image Version: 10.0.19044.1706  

The restore operation completed successfully.

The operation completed successfully. 

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

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations. 

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

Started on 2022-05-22 at 23:02:11.91         

[ChkDsk /Scan]   

The type of the file system is NTFS. 

Stage 1: Examining basic file system structure ... 

790528 file records processed.                                                        
File verification completed.
Phase duration (File record verification): 10.30 seconds.
11790 large file records processed.                                   
Phase duration (Orphan file record recovery): 0.00 milliseconds.0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.04 milliseconds. 

Stage 2: Examining file name linkage ... 
332 reparse records processed.                                      
1105104 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 18.59 seconds.
0 unindexed files scanned.                                        
Phase duration (Orphan reconnection): 2.67 seconds.
0 unindexed files recovered to lost and found.                    
Phase duration (Orphan recovery to lost and found): 0.09 milliseconds.
332 reparse records processed.                                      
Phase duration (Reparse point and Object ID verification): 3.09 milliseconds. 

Stage 3: Examining security descriptors ... 
Security descriptor verification completed.
Phase duration (Security descriptor verification): 37.17 milliseconds.
157289 data files processed.                                           
Phase duration (Data attribute verification): 0.08 milliseconds.
CHKDSK is verifying Usn Journal...39946536 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 149.89 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required. 

262193151 KB total disk space. 
90493700 KB in 497791 files.
329276 KB in 157290 indexes.
0 KB in bad sectors.
911615 KB in use by the system.
65536 KB occupied by the log file.
170458560 KB available on disk. 

4096 bytes in each allocation unit. 
65548287 total allocation units on disk.
42614640 allocation units available on disk.
Total duration: 31.77 seconds (31778 ms).

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

Started on 2022-05-22 at 23:02:50.27

  AutoReboot    

FALSE        

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

[Set AutoReboot = False]  

Updating property(s) of '\\XCODE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk4\\Partition4"'

Property(s) update successful.

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

AutoReboot    

FALSE        

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

DebugInfoType    

3               

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

[Set DebugInfoType = 7]

Updating property(s) of '\\XCODE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk4\\Partition4"'

Property(s) update successful.

================================================================== 
DebugInfoType    

7               
==================================================================        

[WMIC PageFile list]
AllocatedBaseSize=2048
CurrentUsage=42
Description=C:\pagefile.sys
InstallDate=20191118134714.836390-300
Name=C:\pagefile.sys
PeakUsage=48
Status=TempPageFile=FALSE 

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

AutomaticManagedPagefile    

FALSE                      

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

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\XCODE\ROOT\CIMV2:Win32_ComputerSystem.Name="XCODE"'

Property(s) update successful.

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

AutomaticManagedPagefile    TRUE                       ==================================================================        

[BcdEdit /enum {badmemory}]

RAM Defects-----------

identifier              {badmemory} 

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

Finished on 2022-05-22 at 23:02:52.28    

It took 28 minutes and 36 seconds to complete the operations.

Caledon Ken · 22 May 2022

zbook it looks like you reset my pagefile

changed a debug level to 7

and were checking on a BCD entry.

Please explain and how will debug level be reset and if you could why the BCD check.

I'll work on the other commands.

Caledon Ken · 22 May 2022

So output from command to set hibernate to off

Link to diagnostics.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Looks like it changed my sleep time and shut off screen saver. Both not a fix.

I restored my settings, turn high performance back on. These settings have been used for years and I know of no reason they would cause wake BSOD. MS says I'm using to much energy.

zbook · 22 May 2022

Tuneup plus results were all good.
The settings are now optimal for BSOD troubleshooting.
When 3 is chosen it often creates mini dumps instead of memory dumps.
When 7 is chosen it typically creates both mini and memory dumps.

The windows troubleshooters were ran to see if there were any other problems.
Resetting your preferences is fine.

The BCD entry that you're referring to is the badmemory?
This is a diagnostic command as is regularly seen when running the command bcdedit /enum all
This made no modifications and again was only diagnostic.
Sometimes Windows will display bad memory regions.
It quickens the troubleshooting when looking for malfunctioning RAM.
So it was written into the script.

If there is a new BSOD then post a new V2.

Turning off hibernation may fix the problem with the A0 bugcheck.

If there are other types of bugchecks they can be debugged and memory dumps if available can be debugged as needed.

If there are no BSOD for a week then turn hibernation back on as needed.
The longer the duration with hibernation off with no BSOD the better the testing period.

Caledon Ken · 22 May 2022

Thanks. Hibernation has been off for weeks. I ran that command after the second BSOD.

Since I shut it off my UPS software has been asking me to enable so I know it is off.

I did run windows memory checker weeks ago, nothing found.

I did not run the extensive Memtest86.

I should have mention Samsung is the latest. I confirmed. Still I have it disable, it does not start with Windows. All SSD's have latest firmware according to Samsung.

I will run V2 if I get BSOD. So intermittent makes it hard to diagnose.

Thank you for helping.

zbook · 22 May 2022

This bugcheck was A0 = internal power error
Hibernation is high on the list for a fix especially with the fail errors in the event viewer.
If not, then Windows Driver Verifier (WDV) can be run to make sure misbehaving drivers if present are found.
Alternatively if there are no BSOD for a week then that will complete the troubleshooting monitoring period.

Caledon Ken · 23 May 2022

Last time it went 17 days with no BSOD's.

I do have a full memory dump from the first occurrence.

I'll look into driver verifier

zbook · 23 May 2022

This is a link for Windows driver verifier:

Enable and Disable Driver Verifier in Windows 10

Learn the methods to turn off the tool in safe mode using the commands:

verifier /reset

or

verifier /bootmode resetonbootfail

Start with the 3 customized tests in the TF link.
If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

verifier /querysettings

Post a share link into this thread.

If there are no performance problems or very slow boot using 3 customized tests the number of customized tests will be increased to stress test non-Windows drivers.

Plan to run the tool in background for 48 hours while using the computer with the understand that during this period there may or may not be performance problems or unexpected shutdowns and restarts.