- Joined
- Nov 24, 2022
- Messages
- 361 (0.39/day)
Is it possible to find out the real cause that a computer restart from the logfiles? I only see codes and no specific information.
-
Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
Windows 10 find the restarts faults from the logbook.
- Thread starter Oldschool297
- Start date
- Joined
- Jul 25, 2006
- Messages
- 14,105 (2.05/day)
- Location
- Nebraska, USA
| System Name | Brightworks Systems BWS-6 E-IV |
|---|---|
| Processor | Intel Core i5-6600 @ 3.9GHz |
| Motherboard | Gigabyte GA-Z170-HD3 Rev 1.0 |
| Cooling | Quality Fractal Design Define R4 case, 2 x FD 140mm fans, CM Hyper 212 EVO HSF |
| Memory | 32GB (4 x 8GB) DDR4 3000 Corsair Vengeance |
| Video Card(s) | EVGA GEForce GTX 1050Ti 4Gb GDDR5 |
| Storage | Samsung 850 Pro 256GB SSD, Samsung 860 Evo 500GB SSD |
| Display(s) | Samsung S24E650BW LED x 2 |
| Case | Fractal Design Define R4 |
| Power Supply | EVGA Supernova 550W G2 Gold |
| Mouse | Logitech M190 |
| Keyboard | Microsoft Wireless Comfort 5050 |
| Software | W10 Pro 64-bit |
Sadly, often not. And much of the reason for that is because the fault occurs and triggers the reboot/shutdown/freeze so quickly, the OS does not have time write an entry in the logs, even if it knows exactly what happened. So, typically, at best, those entries, if any, are just hints of what might have caused it.
- Joined
- Nov 16, 2023
- Messages
- 2,488 (4.36/day)
- Location
- Nowhere
| System Name | I don't name my rig |
|---|---|
| Processor | 14700K |
| Motherboard | Asus TUF Z790 |
| Cooling | Air/water/DryIce |
| Memory | DDR5 G.Skill Z5 RGB 6000mhz C36 |
| Video Card(s) | RTX 4070 Super |
| Storage | 980 Pro |
| Display(s) | 1080P 144hz |
| Case | Open bench |
| Audio Device(s) | Some Old Sherwood stereo and old cabinet speakers |
| Power Supply | Corsair 1050w HX series |
| Mouse | Razor Mamba Tournament Edition |
| Keyboard | Logitech G910 |
| VR HMD | Quest 2 |
| Software | Windows |
| Benchmark Scores | Max Freq 13700K 6.7ghz DryIce Max Freq 14700K 7.0ghz DryIce Max all time Freq FX-8300 7685mhz LN2 |
You can have a look at Event Viewer in windows. Sometimes it helps get you in the right direction. When open, click Windows logs and from the drop down click system. Find the time date corresponding with the crash/restart/hang.
Good Luck!
Use Event Viewer (eventvwr.msc) to check for logs around the time of the restart:
Navigate to Windows Logs → System
Look for these Event IDs:
6006 – Event log service stopped (shutdown)
6005 – Event log service started (startup)
6008 – Unexpected shutdown
41 (Kernel-Power) – System rebooted without clean shutdown (power loss, BSOD, crash)
Tip: Filter by Event IDs: 41, 6008, 6006, 6005 for quick analysis.
Navigate to Windows Logs → System
Look for these Event IDs:
6006 – Event log service stopped (shutdown)
6005 – Event log service started (startup)
6008 – Unexpected shutdown
41 (Kernel-Power) – System rebooted without clean shutdown (power loss, BSOD, crash)
Tip: Filter by Event IDs: 41, 6008, 6006, 6005 for quick analysis.
- Joined
- Jul 25, 2006
- Messages
- 14,105 (2.05/day)
- Location
- Nebraska, USA
| System Name | Brightworks Systems BWS-6 E-IV |
|---|---|
| Processor | Intel Core i5-6600 @ 3.9GHz |
| Motherboard | Gigabyte GA-Z170-HD3 Rev 1.0 |
| Cooling | Quality Fractal Design Define R4 case, 2 x FD 140mm fans, CM Hyper 212 EVO HSF |
| Memory | 32GB (4 x 8GB) DDR4 3000 Corsair Vengeance |
| Video Card(s) | EVGA GEForce GTX 1050Ti 4Gb GDDR5 |
| Storage | Samsung 850 Pro 256GB SSD, Samsung 860 Evo 500GB SSD |
| Display(s) | Samsung S24E650BW LED x 2 |
| Case | Fractal Design Define R4 |
| Power Supply | EVGA Supernova 550W G2 Gold |
| Mouse | Logitech M190 |
| Keyboard | Microsoft Wireless Comfort 5050 |
| Software | W10 Pro 64-bit |
I may be mistaken but pretty sure when Oldschool297 asked about more detailed information from the logfiles, he was referring to those entries in the logs viewed through Event Viewer. As I noted, they rarely indicated exactly what device, what driver, or what setting was the actual culprit.
- Joined
- Aug 19, 2024
- Messages
- 766 (2.60/day)
- Location
- Texas, USA
| System Name | Obliterator |
|---|---|
| Processor | Ryzen 7 7700x PBO |
| Motherboard | ASRock x670e Steel Legend |
| Cooling | Noctua NH-D15 G2 LBC |
| Memory | G.skill Trident Z5 Neo 6000@CL30 |
| Video Card(s) | ASRock rx7900 GRE Steel Legend |
| Storage | 2 x 2TB Samsung 990 pro nmve ssd 2 X 4TB Samsung 870 evo sata ssd 1 X 18TB WD Gold sata hdd |
| Display(s) | LG 27GN750-B |
| Case | Fractal Torrent |
| Audio Device(s) | Klipsch promedia heritage 2.1 |
| Power Supply | FSP Hydro TI 1000w |
| Mouse | SteelSeries Prime+ |
| Keyboard | Lenovo SK-8825 (L) |
| Software | Windows 10 Enterprise LTSC 21H2 / Windows 11 Enterprise LTSC 24H2 with multiple flavors of VM |
Whocrashed and Bluescreenview can be useful for these purposes.......but these, as has been stated, require that there are proper crash dumps.