Random restarts without any visible BSOD

pcu123 · Aug 23, 2022

My Windows randomly restarts every several days (like 2-3 times a week). There is no BSOD, the screen just turns black and the PC restarts.
I disabled automatic restart after BSOD but this didn't change anything. There is no dump, I don't see any errors in the eventlog.

I am attaching the V2 Log Collector output. Any help really appreciated.

zbook · Aug 23, 2022

The logs were in another language and could not be read.

Please modify the default language to English so that the logs can be scanned and read.

Add, Remove, and Change Display Language in Windows 10

How to Add or Remove Language Packs and Change Display Language in Windows 10

www.tenforums.com

Change Display Language in Windows 11 Tutorial

This tutorial will show you how to change the display language for your account in Windows 11. Installing the language pack of an added language will add the language to your list of Windows display languages. The display language you select changes the default language used by Windows...

www.elevenforum.com

1) Move the page file from D: to C:
Then reboot.

2) Run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

https://www.elevenforum.com/attachments/tuneup_plus_log-bat.36285/

Post a share link into this thread using one drive, drop box, or google drive.

3) After performing the above steps post images or share links displaying these settings:
a) Startup and recovery system failure
b) Virtual memory / page file

4) For any new BSOD post a new V2 share link into the newest post.

pcu123 · Aug 24, 2022

Page file moved to C:.

Tuneup_plus_log output:

Code:

 Microsoft Windows 11 Pro  Version 21H2 (OS Build 22000.856)
  
==================================================================

    Started on Wed 08/24/2022 at  9:56:40.14 
    
        [SFC /ScanNow] 
    
Beginning system scan.  This process will take some time.

Results: 
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on Wed 08/24/2022 at  9:59:16.63 

        [DISM /online /cleanup-image /ScanHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.22000.653

Image Version: 10.0.22000.856 
 
No component store corruption detected.

The operation completed successfully. 
 
==================================================================

    Started on Wed 08/24/2022 at 10:00:38.60 

        [DISM /online /cleanup-image /RestoreHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.22000.653

Image Version: 10.0.22000.856 
 
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 Wed 08/24/2022 at 10:01:31.92 

        [ChkDsk /Scan]  
 
The type of the file system is NTFS.
Volume label is System.
 
Stage 1: Examining basic file system structure ... 
1346304 file records processed.                                                        
File verification completed.
Phase duration (File record verification): 12.93 seconds.
21032 large file records processed.                                   
Phase duration (Orphan file record recovery): 9.59 milliseconds.
0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.04 milliseconds.
 
Stage 2: Examining file name linkage ... 
476 reparse records processed.                                      
1873424 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 54.64 seconds.
0 unindexed files scanned.                                        
Phase duration (Orphan reconnection): 20.12 seconds.
0 unindexed files recovered to lost and found.                    
Phase duration (Orphan recovery to lost and found): 0.10 milliseconds.
476 reparse records processed.                                      
Phase duration (Reparse point and Object ID verification): 4.39 milliseconds.
 
Stage 3: Examining security descriptors ... 
Security descriptor verification completed.
Phase duration (Security descriptor verification): 43.84 milliseconds.
263561 data files processed.                                           
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
36116344 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 127.22 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
499780686 KB total disk space. 
380204772 KB in 934863 files.
602800 KB in 263562 indexes.
0 KB in bad sectors.
1472318 KB in use by the system.
65536 KB occupied by the log file.
117500796 KB available on disk.
 
4096 bytes in each allocation unit. 
124945171 total allocation units on disk.
29375199 allocation units available on disk.
Total duration: 1.46 minutes (87896 ms).
 
==================================================================
 
    Started on Wed 08/24/2022 at 10:03:07.71 
 
AutoReboot   
 
FALSE       
 
==================================================================
 
        [Set AutoReboot = False] 
 
Updating property(s) of '\\LEGION\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
1              
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\LEGION\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
DebugInfoType   
 
7              
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=32768
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20220824094710.784059+120
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
FALSE                     
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\LEGION\ROOT\CIMV2:Win32_ComputerSystem.Name="LEGION"'
Property(s) update successful.
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

    Finished on Wed 08/24/2022 at 10:03:09.16
    It took 6 minutes and 29 seconds to complete the operations.

Startup and recovery system failure:

Virtual memory / page file:

And an English version of V2 logs attached.

zbook · Aug 24, 2022

The logs reported no BSOD.

The logs reported approximately 6 unexpected shutdowns and restarts.

There were live kernel events related to the video card or video card drivers.

The BIOS is out of date.

The opening post did not report hangs and freezes and reported random restarts.

Random restarts without BSOD are most often related to power problems.

With this being a laptop you may need to contact Lenovo or a local computer store for troubleshooting.

The Video card drivers could be replaced with the drivers displayed on the Lenovo website to see if it makes any difference.

The thread can be moved to the general forum as there were no BSOD.

1) Upgrade the BIOS: FSCN20WW > FSCN25WW

BIOS Update for Windows 10 (64-bit) - Legion 5-15ARH05H, Legion 5-17ARH05H, Legion 5P-15ARH05H - Lenovo Support US

pcsupport.lenovo.com

2) Run the Lenovo automatic driver update:

laptops and netbooks :: legion series :: legion 5 15arh05h :: 82b1contentdetail - Lenovo Support US

pcsupport.lenovo.com

Report any updates.

3) Run:
https://www.tenforums.com/attachmen...collect_logs_from_event_viewer-2021-09-14.bat

Post a share link into this thread using one drive, drop box, or google drive.

4) Run the Lenovo Custom hardware diagnostics > (click view all) (check all boxes)

laptops and netbooks :: legion series :: legion 5 15arh05h :: 82b1 - Lenovo Support US

pcsupport.lenovo.com

Post images or share links displaying the tests performed with results into this thread.

pcu123 · Aug 25, 2022

1) I knew there was a BIOS update but I didn't do it because the previous update hadn't run well. The first boot after BIOS install there was a Windows chime but the screen was black. I had much trouble restoring the correct behavior (even created the support request but they weren't very helpful), the funny thing was that when connecting the laptop to the external screen via HDMI cable I could see the picture on the external screen. The final solution was to go to the troubleshooting mode of Windows 11 and boot into BIOS. After that the laptop screen was functioning correctly…
And so I did an update today and the same story – no picture on laptop screen, attaching external screen via HDMI, booting into BIOS, job done.

2) Nothing found.

4) Everything passed.

I think it makes no sense to run 3) now. I will wait to the next unexpected restart and collect all logs again (and post here).

Regarding the video drivers – I used to have AMD drivers but Windows Update still proposed me an update for it. So I removed the AMD software and I am using the Windows Update version of the driver.
For Nvidia – I am using drivers from Nvidia website. I am sure the Lenovo version of their drivers is mostly outdated. And they don't even have a version for Windows 11. They don't seem to care about Windows 11 for this model, there are only Windows software available, not drivers at all.

Anixx · Aug 30, 2022

I also have random restarts without a BSOD (2 times today), both on this system (Lenovo) and on my older system, Samsung.

pcu123 · Nov 3, 2022

The restarts were gone and it lasted for two months… Now it strikes again.

I put the logs collected after the recent restart:

V2 logs
Tuneup Plus logs
Event Logs

into: Temp

@zbook: Could you please take a look?

zbook · Nov 3, 2022

The logs were in a foreign language and could not be scanned.

Please use English as the default language so that the log files can be read.

pcu123 · Nov 3, 2022

I use English, I set it some days ago when the restarts came back:

UPDATE: I found some old event logs in Polish and this make sense. But since they're old I don't think they are that important.
If you see Polish in any other logs, let me know where.

zbook · Nov 4, 2022

The event text logs are often fixed until there is a clean install.

Today is 11/4/2022 and these are examples of the most recent entries in the event viewer text files:

Code:

Event[8198]
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2022-11-03T17:08:08.1750000Z
  Event ID: 1
  Task: N/A
  Level: Informacje
  Opcode: Informacje
  Keyword: Time
  User: S-1-5-21-344720674-3962062576-3258858526-1001
  User Name: LEGION\root
  Computer: Legion
  Description:
Czas systemowy zosta│ zmieniony na ?2022?-?11?-?03T16:08:08.175576600Z z ?2022?-?11?-?03T16:08:08.175576600Z.
Rˇ┐nica czasu: 0 ms

Przyczyna zmiany: System time adjusted to the new time zone.
Proces: '\Device\HarddiskVolume3\Windows\System32\wbem\WmiPrvSE.exe' (10052 PID).

czas RTC: ?2022?-?11?-?03T17:08:08.175576600Z
Bie┐╣cy odchylenie strefy czasowej: -60
czas RTC to CZAS UTC: false
Czas systemowy by│ oparty na czasie RTC: false

Event[8199]
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2022-11-03T17:09:25.9360000Z
  Event ID: 10016
  Task: N/A
  Level: Ostrze┐enia
  Opcode: Informacje
  Keyword: Klasyczny
  User: S-1-5-21-344720674-3962062576-3258858526-1001
  User Name: LEGION\root
  Computer: Legion
  Description:
Zgodnie z ustawieniami uprawnienia w│aťciwe dla aplikacji nie jest udzielane uprawnienie Lokalny Aktywacja do aplikacji serwera COM z identyfikatorem klasy CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 i identyfikatorem aplikacji APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 u┐ytkownikowi LEGION\root o identyfikatorze zabezpiecze˝ SID (S-1-5-21-344720674-3962062576-3258858526-1001) z adresu LocalHost (u┐ycie LRPC) dzia│aj╣cemu w kontenerze aplikacji o identyfikatorze SID Niedostŕpny (Niedostŕpny). To uprawnienie zabezpiecze˝ mo┐na modyfikowaŠ przy u┐yciu narzŕdzia administracyjnego Us│ugi sk│adowe.

Event[8200]
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2022-11-03T17:09:26.1110000Z
  Event ID: 10016
  Task: N/A
  Level: Ostrze┐enia
  Opcode: Informacje
  Keyword: Klasyczny
  User: S-1-5-21-344720674-3962062576-3258858526-1001
  User Name: LEGION\root
  Computer: Legion
  Description:
Zgodnie z ustawieniami uprawnienia w│aťciwe dla aplikacji nie jest udzielane uprawnienie Lokalny Aktywacja do aplikacji serwera COM z identyfikatorem klasy CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 i identyfikatorem aplikacji APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 u┐ytkownikowi LEGION\root o identyfikatorze zabezpiecze˝ SID (S-1-5-21-344720674-3962062576-3258858526-1001) z adresu LocalHost (u┐ycie LRPC) dzia│aj╣cemu w kontenerze aplikacji o identyfikatorze SID Niedostŕpny (Niedostŕpny). To uprawnienie zabezpiecze˝ mo┐na modyfikowaŠ przy u┐yciu narzŕdzia administracyjnego Us│ugi sk│adowe.

Event[8201]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-11-03T17:11:01.5360000Z
  Event ID: 566
  Task: N/A
  Level: Informacje
  Opcode: Informacje
  Keyword: N/A
  User: S-1-5-18
  User Name: ZARZąDZANIE NT\SYSTEM
  Computer: Legion
  Description:
Sesja systemowa zosta│a przeniesiona z 1 do 3.

Przyczyna InputHid

BootId: 22

All of the event viewer files will remain in a foreign language until the next clean install.
The files cannot be scanned using English words.
The unexpected shutdowns though were able to be verified.

For frequent unexpected shutdowns and restarts in a laptop you can place the computer into safe mode with networking and see if the unexpected shutdowns restarts disappear or continue.

meimeiriver · Nov 4, 2022

Sponteneous reboots, without a BSOD, are often PSU related (unstable and/or undervolting of some sort). There was exactly 1 time a nVidia driver version caused an undervolting of the card, which also led to a reboot (this only lasted for 1 day, as, contrary to popular belief, they're not crazy at nVidIa, and they promptly fixed it).

Try and boot, and then start a CPU/GPU stress test. If your computer starts spontaneously rebooting at that moment, then you have your likely culprit.

pcu123 · Nov 4, 2022

meimeiriver said:
Sponteneous reboots, without a BSOD, are often PSU related (unstable and/or undervolting of some sort). There was exactly 1 time a nVidia driver version caused an undervolting of the card, which also led to a reboot (this only lasted for 1 day, as, contrary to popular belief, they're not crazy at nVidIa, and they prompty fixed it).

I was also suspecting a graphic card driver. Some time ago in certain moments when something on screen has to be changed a screen started to blink and the graphics "refreshed". Some time later at the same moments instead of a screen refresh, I got an unexpected restart.

Now it happens from time to time when I try to change the volume (but it displays OCD so it still can be a graphics problem).

meimeiriver said:
Try and boot, and then start a CPU/GPU stress test. If your computer starts spontaneously rebooting at that moment, then you have your likely culprit.

I did a full Lenovo Diagnostics (lasting for several hours), including CPU test. Everything was reported as doing fine…