Freeze and reboot - no BSOD

acbendc · Jun 6, 2022

Hi All !

First thanks for your forum and for the help you provide !

I deal with freeze and reboot during gaming sessions since several months ... sometimes after a few minutes, sometimes after several hours.
I have no errors or BSOD on screen, just freeze and after a few seconds reboot.

In the event viewer I have each time a Kernel 41 (63) critical error.

Windows version : 21H2 build 22000.708

=> PSU, graphic card and RAM have been changed. PSU because I thought it was the issue, Graphic card and RAM for upgrade (RAM is a second identical kit, I have already tried either the old one, the new one and the 2 kits together, same issue with freeze and reboot).

I have made several full new proper install (full wipe) with drivers from asus website or automatic update from Windows Update. Try on Windows 10 and Windows 11, no change ... BIOS is up to date.

I don't know where to look anymore ....

You will find enclosed the V2 log collector extraction, hope it will be helpful !

If you have any idea or question don't hesistate !!!!

Ben

glasskuter · Jun 6, 2022

@zbook

glasskuter · Jun 7, 2022

Welcome to the forum Ben. That is an impressive setup you are running. I guess @zbook missed my tag so I'll try to tag him again so he can analyze your logs. Are you overclocking?

acbendc · Jun 8, 2022

Hello Glasskuter !

Thank you :)

No overclocking at all (for the moment !)

zbook · Jun 8, 2022

There were no BSOD so the thread was moved to the general forum.

The logs were in a foreign language and could not be scanned or 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 10

How to Change Display Language in Windows 10

www.tenforums.com

There was one live kernel event seen in the log files.

The live kernel event bugcheck was 1A1 = WIN32K_CALLOUT_WATCHDOG_LIVEDUMP

It was a one time event in the logs.

The computer can be monitored:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using

When it comes to hidden gems in Windows, nothing beats the Reliability monitor tool, hidden behind a link inside of another tool that you don't use either.

www.howtogeek.com

This script will tune up the computer and modify crash settings so that if they occur they are less likely to be missed:

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

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

Code:

Signature du problème :
P1 : 1a1
P2 : ffffb6868eb15040
P3 : 0
P4 : 0
P5 : 0
P6 : 10_0_22000
P7 : 0_0
P8 : 256_1
P9 :
P10 :

Fichiers joints :
\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20220602-0225.dmp
\\?\C:\Windows\SystemTemp\WER-68998343-0.sysdata.xml
\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog-20220602-0225.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b66275b9-69b8-4ed0-9e1b-d3fb5a4ad30f.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b869e05-65e9-4f5a-871c-f65650a68778.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20b24e7c-b7a2-4b81-851f-534325dab7a4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.343f28ed-5b89-436b-b8d8-64d5bc87b471.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a1_215d81a22b3dd4cb1df4d305e7f3af6bc536a1a_00000000_a1d8428b-98dd-4c03-99e8-2d0222b693d0

Code:

02/06/2022 05:43    Windows Error Reporting    Détecteur d'erreurs , type 0&#x000d;&#x000a;Nom d’événement : LiveKernelEvent&#x000d;&#x000a;Réponse : Non disponible&#x000d;&#x000a;ID de CAB : 0&#x000d;&#x000a;&#x000d;&#x000a;Signature du problème : &#x000d;&#x000a;P1 : 1a1&#x000d;&#x000a;P2 : ffffb6868eb15040&#x000d;&#x000a;P3 : 0&#x000d;&#x000a;P4 : 0&#x000d;&#x000a;P5 : 0&#x000d;&#x000a;P6 : 10_0_22000&#x000d;&#x000a;P7 : 0_0&#x000d;&#x000a;P8 : 256_1&#x000d;&#x000a;P9 : &#x000d;&#x000a;P10 : &#x000d;&#x000a;&#x000d;&#x000a;Fichiers joints :&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER-68998343-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b66275b9-69b8-4ed0-9e1b-d3fb5a4ad30f.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b869e05-65e9-4f5a-871c-f65650a68778.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20b24e7c-b7a2-4b81-851f-534325dab7a4.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.343f28ed-5b89-436b-b8d8-64d5bc87b471.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;Ces fichiers sont peut-être disponibles ici :&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_215d81a22b3dd4cb1df4d305e7f3af6bc536a1a_00000000_cab_a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;&#x000d;&#x000a;Symbole d’analyse : &#x000d;&#x000a;Nouvelle recherche de la solution : 0&#x000d;&#x000a;ID de rapport : a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;Statut du rapport : 2049&#x000d;&#x000a;Récipient avec hachage : &#x000d;&#x000a;GUID CAB :0
02/06/2022 05:43    Windows Error Reporting    Détecteur d'erreurs , type 0&#x000d;&#x000a;Nom d’événement : LiveKernelEvent&#x000d;&#x000a;Réponse : Non disponible&#x000d;&#x000a;ID de CAB : 0&#x000d;&#x000a;&#x000d;&#x000a;Signature du problème : &#x000d;&#x000a;P1 : 1a1&#x000d;&#x000a;P2 : ffffb6868eb15040&#x000d;&#x000a;P3 : 0&#x000d;&#x000a;P4 : 0&#x000d;&#x000a;P5 : 0&#x000d;&#x000a;P6 : 10_0_22000&#x000d;&#x000a;P7 : 0_0&#x000d;&#x000a;P8 : 256_1&#x000d;&#x000a;P9 : &#x000d;&#x000a;P10 : &#x000d;&#x000a;&#x000d;&#x000a;Fichiers joints :&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER-68998343-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b66275b9-69b8-4ed0-9e1b-d3fb5a4ad30f.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b869e05-65e9-4f5a-871c-f65650a68778.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20b24e7c-b7a2-4b81-851f-534325dab7a4.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.343f28ed-5b89-436b-b8d8-64d5bc87b471.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;Ces fichiers sont peut-être disponibles ici :&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a1_215d81a22b3dd4cb1df4d305e7f3af6bc536a1a_00000000_a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;&#x000d;&#x000a;Symbole d’analyse : &#x000d;&#x000a;Nouvelle recherche de la solution : 0&#x000d;&#x000a;ID de rapport : a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;Statut du rapport : 4&#x000d;&#x000a;Récipient avec hachage : &#x000d;&#x000a;GUID CAB :0

acbendc · Jun 8, 2022

Hi! thanks again !

I have switched my system to english, launch again the log collector and the script too :)
you will find attached the results !

zbook · Jun 8, 2022

The tuneup plus results were good.

Today is 06/08/22 and the logs indicated a fresh installation on 06/01/2022.
So there was approximately one week of data.

There were no BSOD.
The live kernel event 1A1 was reported in the earlier post.

The Intel CPU: i7-11700KF supports DDR4 RAM speeds up to 3200 MHz.

At the time that the log collector ran the RAM speed was 3600 MHz..

During the troubleshooting please make sure that there is no overclocking.
Turn off XMP.

Intel® Core™ i7-11700KF Processor (16M Cache, up to 5.00 GHz) - Product Specifications | Intel

Intel® Core™ i7-11700KF Processor (16M Cache, up to 5.00 GHz) quick reference with specifications, features, and technologies.

www.intel.com

Uninstall: MSI Afterburner

Uninstall or uninstall and reinstall: CORSAIR iCUE 4 Software

Monitored the computer using reliability monitor.

If you have to manually power off the computer record the day and time.

acbendc · Jun 9, 2022

I had a new reboot yesterday night. I made new logs attached if it can helps !

I will also try without Msi Afterburner.

I have already tryed without Corsair Icue but same issue ....

zbook · Jun 9, 2022

During the log collection the RAM speed was recorded at 2000 MHz.

Please uninstall these software:

CORSAIR iCUE 4 Software
MSI Afterburner 4.6.4

The Corsair software continues to cause application errors.

The last recorded live kernel event was: Date: 2022-06-02T07:43:25.4360000Z

Using reliability monitor > monitor the computer for unexpected shutdowns and restarts
If you manually power off the computer then comment into the thread.

I'll sign off so other members can continue the troubleshooting.
If there are BSOD then let me know and I'll troubleshoot the BSOD.

Code:

Event[2779]
  Log Name: System
  Source: EventLog
  Date: 2022-06-08T23:36:19.2470000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-7KQ8MSN
  Description:
The previous system shutdown at 23:34:46 on ?08/?06/?2022 was unexpected.

Code:

Event[2789]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-06-08T23:36:14.2000000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

acbendc · Jun 9, 2022

Ok I uninstalled MSI afterburner and ICUE.
I also fixed the RAM to 3600Mhz in the bios and run successfully a memory test provided by windows.

let's try again .... I will let you know !

acbendc · Jun 14, 2022

acbendc said:
Ok I uninstalled MSI afterburner and ICUE.
I also fixed the RAM to 3600Mhz in the bios and run successfully a memory test provided by windows.

let's try again .... I will let you know !

I had a new crash :crys:

still the kernel power 41 (63)

Here are the logs if you can help me !

zbook · Jun 14, 2022

There were no BSOD.

Windows fast startup failed.

Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 11 Tutorial

This tutorial will show you how to turn on or off fast startup in Windows 11. There are three startup modes in Windows: Cold (traditional) Wake-from-hibernation Fast Starting with Windows 8.x, the default shutdown and restart scenario has been updated and named fast startup. Fast startup...

www.elevenforum.com

Use the computer for a few weeks and if there is a problem then open a new thread.

Follow the trends using reliability monitor:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using

When it comes to hidden gems in Windows, nothing beats the Reliability monitor tool, hidden behind a link inside of another tool that you don't use either.

www.howtogeek.com

Code:

Event[4003]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-06-14T19:12:32.7590000Z
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
Windows failed fast startup with error status 0xC00000D4.

Code:

Event[4015]
  Log Name: System
  Source: EventLog
  Date: 2022-06-14T19:12:39.9000000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-7KQ8MSN
  Description:
The previous system shutdown at 12:57:56 on ?14/?06/?2022 was unexpected.

Code:

Event[4025]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-06-14T19:12:35.0290000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[2779]
  Log Name: System
  Source: EventLog
  Date: 2022-06-08T23:36:19.2470000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-7KQ8MSN
  Description:
The previous system shutdown at 23:34:46 on ?08/?06/?2022 was unexpected.

Code:

Event[2789]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-06-08T23:36:14.2000000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

acbendc · Jun 15, 2022

Thank you.
I turned off fast boot. I will let you know if it's better !

acbendc · Jun 25, 2022

Hello!

unfortunately I got a new crash. only 1 within 7 days but the issue is still present.

you will find enclosed the logs if you can help.

thank you !

zbook · Jun 25, 2022

Today is 06/25/2022.

When was the crash?

Was it a BSOD, a Windows crash without BSOD, or an application crash?

acbendc · Jun 25, 2022

Crash was the 06/22.
no BSOD, just a freeze, then black screen and reboot. no error message ...

zbook · Jun 25, 2022

The log collector collected no mini dump files and did not record any memory dumps.

The logs reported the last unexpected shutdown and restart on 06/22/2022.

The live kernel event with bugcheck 1A1 was on 06/02/2022.

So continue monitoring the computer.

If there are continued unexpected shutdowns and restarts without BSOD or live kernel events then stress test or swap hardware.
For example PSU.

The entries in the log collector can appear the same way during manual poweroffs.
So if there is a hang or freeze and manual power off please comment into this thread.

Code:

02/06/2022 05:43    Windows Error Reporting    Fault bucket , type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Non disponible&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1a1&#x000d;&#x000a;P2: ffffb6868eb15040&#x000d;&#x000a;P3: 0&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER-68998343-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b66275b9-69b8-4ed0-9e1b-d3fb5a4ad30f.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b869e05-65e9-4f5a-871c-f65650a68778.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20b24e7c-b7a2-4b81-851f-534325dab7a4.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.343f28ed-5b89-436b-b8d8-64d5bc87b471.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_215d81a22b3dd4cb1df4d305e7f3af6bc536a1a_00000000_cab_a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0

02/06/2022 05:43    Windows Error Reporting    Fault bucket , type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Non disponible&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1a1&#x000d;&#x000a;P2: ffffb6868eb15040&#x000d;&#x000a;P3: 0&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER-68998343-0.sysdata.xml&#x000d;&#x000a;\\?\C:\Windows\LiveKernelReports\PoW32kWatchdog-20220602-0225.dmp&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b66275b9-69b8-4ed0-9e1b-d3fb5a4ad30f.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b869e05-65e9-4f5a-871c-f65650a68778.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20b24e7c-b7a2-4b81-851f-534325dab7a4.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.343f28ed-5b89-436b-b8d8-64d5bc87b471.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a1_215d81a22b3dd4cb1df4d305e7f3af6bc536a1a_00000000_a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: a1d8428b-98dd-4c03-99e8-2d0222b693d0&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0

Code:

Event[6347]

  Log Name: System
  Source: EventLog
  Date: 2022-06-22T22:08:10.2450000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-7KQ8MSN
  Description:
The previous system shutdown at 22:06:34 on ?22/?06/?2022 was unexpected.

Code:

Event[6357]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-06-22T22:08:05.3420000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

acbendc · Jun 25, 2022

Thank you.
I have already swap with a new PSU.

I will continue monitoring the computer and let you know.

acbendc · Jun 28, 2022

Got 2 new crashes without BSOD... Could it be a motherboard issue ? or a CPU issue ?

zbook · Jun 28, 2022

Please compare the installed RAM to the Qualified Vendor List (QVL) and report your findings.

The installed RAM modules (F4-3600C15-8GTZ ) were not seen on the QVL.

For testing purposes install RAM that is on the QVL.

ROG STRIX Z590-F GAMING WIFI

ROG Strix Z590-F Gaming WiFi motherboard features boosted power delivery, an optimized cooling design, PCIe® 4.0, WiFi 6E, AI controls and cyberpunk-inspired aesthetics.

rog.asus.com

Monitor for unexpected shutdowns and restarts using reliability monitor:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using

When it comes to hidden gems in Windows, nothing beats the Reliability monitor tool, hidden behind a link inside of another tool that you don't use either.

www.howtogeek.com

Code:

Event[8493]
  Log Name: System
  Source: EventLog
  Date: 2022-06-28T18:27:17.8720000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-7KQ8MSN
  Description:
The previous system shutdown at 18:25:33 on ?28/?06/?2022 was unexpected.

Code:

Event[8162]
  Log Name: System
  Source: EventLog
  Date: 2022-06-27T23:30:58.8240000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-7KQ8MSN
  Description:
The previous system shutdown at 23:29:49 on ?27/?06/?2022 was unexpected.

Code:

Event[8172]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-06-27T23:30:54.2180000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[8503]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-06-28T18:27:13.2680000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORITE NT\SystÞme
  Computer: DESKTOP-7KQ8MSN
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[7616]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2022-06-27T19:13:25.8310000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: AUTORITE NT\SERVICE LOCAL
  Computer: DESKTOP-7KQ8MSN
  Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Code:

Event[7724]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2022-06-27T19:23:30.7500000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: AUTORITE NT\SERVICE LOCAL
  Computer: DESKTOP-7KQ8MSN
  Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.