F5F Stay Refreshed Software PC Gaming Issue with PC random reboots?

Issue with PC random reboots?

Issue with PC random reboots?

E
EnderSponge_
Member
225
05-10-2020, 08:53 PM
#1
My configuration includes:
-Rogstrix x570e gaming
-Ryzen 9 5900x
-RTX 3080 OC version (Factory "OC" – no changes made)
-32 GB RAM @ 3200RPM

While playing Hogwarts Legacy, the system began to restart repeatedly. It was unusual since it had happened only once before, but each reboot brought me back to the BIOS, trapping me in a loop. I had to perform a cold reboot several times to escape.

I investigated and noticed Hogwarts Legacy has many issues. I suspected the driver might be corrupted, so I reinstalled it. After that, I switched to Ghostwire Tokyo without any problems. However, today I was testing Fallout 4 with the latest modlist, paused the game, took my dog to the vet, and returned after a few hours when the computer had rebooted again.

I checked the Event Viewer, but the only critical message was "Kernel-power," which didn’t provide any useful information. This situation is puzzling because I had been using the machine from 7am to 1am, playing Ghostwire from 6pm to 1am every week, and never experienced any issues. It’s hard to understand what might be causing this if you have any advice.
E
EnderSponge_
05-10-2020, 08:53 PM #1

My configuration includes:
-Rogstrix x570e gaming
-Ryzen 9 5900x
-RTX 3080 OC version (Factory "OC" – no changes made)
-32 GB RAM @ 3200RPM

While playing Hogwarts Legacy, the system began to restart repeatedly. It was unusual since it had happened only once before, but each reboot brought me back to the BIOS, trapping me in a loop. I had to perform a cold reboot several times to escape.

I investigated and noticed Hogwarts Legacy has many issues. I suspected the driver might be corrupted, so I reinstalled it. After that, I switched to Ghostwire Tokyo without any problems. However, today I was testing Fallout 4 with the latest modlist, paused the game, took my dog to the vet, and returned after a few hours when the computer had rebooted again.

I checked the Event Viewer, but the only critical message was "Kernel-power," which didn’t provide any useful information. This situation is puzzling because I had been using the machine from 7am to 1am, playing Ghostwire from 6pm to 1am every week, and never experienced any issues. It’s hard to understand what might be causing this if you have any advice.

K
Killerman1834
Posting Freak
885
05-11-2020, 01:43 PM
#2
What is the model number and make of your PSU? How outdated is the PSU? Typically, reboot issues are linked to a defective or failing power supply, although other factors may be involved. Are you seeing error message 41 in the Kernel Power window? If so, this could indicate an underpowered or faulty power supply problem. Additionally, consider re-seating your RAM and graphics card on the motherboard. You might also try running CHKDSK and SFC commands to inspect your hard drive and Windows system files.
K
Killerman1834
05-11-2020, 01:43 PM #2

What is the model number and make of your PSU? How outdated is the PSU? Typically, reboot issues are linked to a defective or failing power supply, although other factors may be involved. Are you seeing error message 41 in the Kernel Power window? If so, this could indicate an underpowered or faulty power supply problem. Additionally, consider re-seating your RAM and graphics card on the motherboard. You might also try running CHKDSK and SFC commands to inspect your hard drive and Windows system files.

G
Guiguixd11
Member
58
05-12-2020, 09:22 PM
#3
The event number is 41, the PSU is more than two years old, and the system runs at 750w. DISM and SFC were executed, and both reported no issues. CHKDSK indicated a repair was needed for the final section, which resulted in the following outcomes:

System file inspection on C disk revealed an NTFS file system. A disk check has been arranged. Windows will now perform the disk verification.

First stage: Analyzing basic file structure...
1,120,000 records were examined. File checks passed.
Duration of verification: 8.81 seconds.
16,799 large files processed. Verification time for orphaned records: 10.33 milliseconds.
No bad files found. Verification time for bad records: 4.45 milliseconds.

Second stage: Reviewing file name connections...
23,849 reparse entries handled. 1,428,894 index records verified.
Verification time: 22.57 seconds. No files unindexed.
Reconnection time for orphaned files: 1.45 seconds. All lost and found items recovered.
Recovery time from orphaned to lost and found: 35.87 milliseconds.

Third stage: Analyzing security descriptors...
Removed 160 unused index entries from index SII of file 0x9.
Cleaned up 160 unused index entries from index SDH of file 0x9.
Eliminated 160 unused security descriptors.
CHKDSK is compacting the security descriptor stream.
Security descriptor check finished in 49.75 milliseconds.

Fourth stage: Searching for bad clusters in user files...
1,119,884 files processed. File data verified.
Recovery time for user files: 18.90 minutes.

Fifth stage: Identifying bad and free clusters...
38,199,216 free clusters found. Free space check complete.
Recovery time for free space: 17.27 seconds.

Windows corrected file system issues. No further actions needed.

Disk usage summary:
- Total disk space: 975,937,535 KB
- Files: 821,469,388 KB across 674,892 files
- Indexes: 414,896 KB in 154,451 indexes
- Bad sectors: 0 KB
- System use: 1,125,638 KB
- Log file: 6,5536 KB
- Allocation units: 243,984,383 total
- Total time: 19.74 minutes (1,184,866 ms)

Additional notes:
Internal information recorded at various stages.
G
Guiguixd11
05-12-2020, 09:22 PM #3

The event number is 41, the PSU is more than two years old, and the system runs at 750w. DISM and SFC were executed, and both reported no issues. CHKDSK indicated a repair was needed for the final section, which resulted in the following outcomes:

System file inspection on C disk revealed an NTFS file system. A disk check has been arranged. Windows will now perform the disk verification.

First stage: Analyzing basic file structure...
1,120,000 records were examined. File checks passed.
Duration of verification: 8.81 seconds.
16,799 large files processed. Verification time for orphaned records: 10.33 milliseconds.
No bad files found. Verification time for bad records: 4.45 milliseconds.

Second stage: Reviewing file name connections...
23,849 reparse entries handled. 1,428,894 index records verified.
Verification time: 22.57 seconds. No files unindexed.
Reconnection time for orphaned files: 1.45 seconds. All lost and found items recovered.
Recovery time from orphaned to lost and found: 35.87 milliseconds.

Third stage: Analyzing security descriptors...
Removed 160 unused index entries from index SII of file 0x9.
Cleaned up 160 unused index entries from index SDH of file 0x9.
Eliminated 160 unused security descriptors.
CHKDSK is compacting the security descriptor stream.
Security descriptor check finished in 49.75 milliseconds.

Fourth stage: Searching for bad clusters in user files...
1,119,884 files processed. File data verified.
Recovery time for user files: 18.90 minutes.

Fifth stage: Identifying bad and free clusters...
38,199,216 free clusters found. Free space check complete.
Recovery time for free space: 17.27 seconds.

Windows corrected file system issues. No further actions needed.

Disk usage summary:
- Total disk space: 975,937,535 KB
- Files: 821,469,388 KB across 674,892 files
- Indexes: 414,896 KB in 154,451 indexes
- Bad sectors: 0 KB
- System use: 1,125,638 KB
- Log file: 6,5536 KB
- Allocation units: 243,984,383 total
- Total time: 19.74 minutes (1,184,866 ms)

Additional notes:
Internal information recorded at various stages.

A
Aragone
Member
224
05-12-2020, 10:11 PM
#4
We must first identify the exact model number and brand of the power supply unit. Look at the label on its side for this information.
A
Aragone
05-12-2020, 10:11 PM #4

We must first identify the exact model number and brand of the power supply unit. Look at the label on its side for this information.

X
xVeryn1337
Member
229
05-12-2020, 10:25 PM
#5
Sorry, I misread, this is the correct link
XPG CORE REACTOR Modular Power Supply
www.xpg.com
X
xVeryn1337
05-12-2020, 10:25 PM #5

Sorry, I misread, this is the correct link
XPG CORE REACTOR Modular Power Supply
www.xpg.com

G
gonzilla03
Junior Member
34
05-13-2020, 05:28 AM
#6
The PSU seems to be OKAY. I don't think there might an issue using this SKU. Some other thing might be causing random reboots. but doesn,and the more modern RM750.
G
gonzilla03
05-13-2020, 05:28 AM #6

The PSU seems to be OKAY. I don't think there might an issue using this SKU. Some other thing might be causing random reboots. but doesn,and the more modern RM750.