F5F Stay Refreshed Hardware Desktop The computer restarts unexpectedly during gameplay.

The computer restarts unexpectedly during gameplay.

The computer restarts unexpectedly during gameplay.

D
DazzlingWinter
Junior Member
15
12-17-2023, 08:15 PM
#1
I assembled a PC four years ago and it functioned well for a couple of years. Occasionally, it would crash with a BSOD while running games like Minecraft, Sekiro, R6, and CS2. After trying various fixes, I switched to a new Windows installation. Now the problem persists but instead of a crash, the system just powers off and restarts. The issue might be linked to a PSU protection feature. Here’s the component list: https://ca.pcpartpicker.com/list/7Bhw74. Updated: Replacing the PSU resolved it.
D
DazzlingWinter
12-17-2023, 08:15 PM #1

I assembled a PC four years ago and it functioned well for a couple of years. Occasionally, it would crash with a BSOD while running games like Minecraft, Sekiro, R6, and CS2. After trying various fixes, I switched to a new Windows installation. Now the problem persists but instead of a crash, the system just powers off and restarts. The issue might be linked to a PSU protection feature. Here’s the component list: https://ca.pcpartpicker.com/list/7Bhw74. Updated: Replacing the PSU resolved it.

J
josephn619
Member
76
12-18-2023, 03:03 PM
#2
Hi. Possible causes include heat, bad RAM, or the power supply. RAM is straightforward to test—run memtest 86 and repeat at least once. Heat is another factor; monitor temperatures using CPUID's Hardware Monitor. The PSU is trickier—defer checking until later.
J
josephn619
12-18-2023, 03:03 PM #2

Hi. Possible causes include heat, bad RAM, or the power supply. RAM is straightforward to test—run memtest 86 and repeat at least once. Heat is another factor; monitor temperatures using CPUID's Hardware Monitor. The PSU is trickier—defer checking until later.

G
gioquadro011
Junior Member
36
12-18-2023, 05:57 PM
#3
No, I haven't seen any BSOD error codes.
G
gioquadro011
12-18-2023, 05:57 PM #3

No, I haven't seen any BSOD error codes.

P
PsychoFel
Member
69
12-19-2023, 01:21 PM
#4
Can't get started with memtest consistently. Most attempts end in a black screen or the Asus setup screen, but I can't access the BIOS. I don't have the crash codes from previous crashes, though now I see "CRITICAL PROCESS DIED" and "KERNAL DATA INPAGE ERROR" when launching Windows.
P
PsychoFel
12-19-2023, 01:21 PM #4

Can't get started with memtest consistently. Most attempts end in a black screen or the Asus setup screen, but I can't access the BIOS. I don't have the crash codes from previous crashes, though now I see "CRITICAL PROCESS DIED" and "KERNAL DATA INPAGE ERROR" when launching Windows.

D
DRGNdragsYT
Senior Member
723
12-21-2023, 03:43 PM
#5
Critical_Process_Died suggests a memory issue in kernel files, usually due to damaged files. It often points to storage problems rather than just a file error. This crash typically appears alongside storage concerns. Kernel_Data_Inpage_Error indicates corruption in the page file, which is a strong warning about bad storage. Re-seat the M.2 drive if needed, as improper installation is common after moving the PC. With multiple drives, the OS drive is usually affected, but memory errors can still occur. You're seeing corrupted page file entries and the page file behaves like extra RAM, which may cause memory faults. Storage issues can lead to these errors. We can identify the drive hosting the page file—usually the OS drive—to confirm if it's the source of the problem. If you have only one drive, this step isn't required. Run the command in PowerShell: Get-CimInstance -ClassName Win32_PageFileUsage -Property * To see the location; if it shows C:\pagefile.sys, the root is likely the problematic drive.
D
DRGNdragsYT
12-21-2023, 03:43 PM #5

Critical_Process_Died suggests a memory issue in kernel files, usually due to damaged files. It often points to storage problems rather than just a file error. This crash typically appears alongside storage concerns. Kernel_Data_Inpage_Error indicates corruption in the page file, which is a strong warning about bad storage. Re-seat the M.2 drive if needed, as improper installation is common after moving the PC. With multiple drives, the OS drive is usually affected, but memory errors can still occur. You're seeing corrupted page file entries and the page file behaves like extra RAM, which may cause memory faults. Storage issues can lead to these errors. We can identify the drive hosting the page file—usually the OS drive—to confirm if it's the source of the problem. If you have only one drive, this step isn't required. Run the command in PowerShell: Get-CimInstance -ClassName Win32_PageFileUsage -Property * To see the location; if it shows C:\pagefile.sys, the root is likely the problematic drive.

T
tyoshi1
Junior Member
48
12-21-2023, 04:24 PM
#6
You have just two external drives, but the system reports it's on the C drive after the command runs. After reinserting both M.2 drives, the BSODs disappeared, yet the device still powers off during gameplay. You were able to view these error messages.
T
tyoshi1
12-21-2023, 04:24 PM #6

You have just two external drives, but the system reports it's on the C drive after the command runs. After reinserting both M.2 drives, the BSODs disappeared, yet the device still powers off during gameplay. You were able to view these error messages.

C
captainalpha9
Member
200
12-23-2023, 02:51 PM
#7
The pak file issues in CS2 stem from file corruption, while other problems relate to memory faults. You could have experienced major file damage if drives weren't correctly connected, possibly requiring a full reinstall or even OS replacement. This shouldn’t lead to crashes. To verify hardware issues, open Event Viewer → Windows Logs → System, navigate to the right and look for "Filter Current Log." Click the dropdown under Event Sources and choose "WHEA-logger." Highlight any WHEA events, then right-click and save them. Submit the .evtx file here.
C
captainalpha9
12-23-2023, 02:51 PM #7

The pak file issues in CS2 stem from file corruption, while other problems relate to memory faults. You could have experienced major file damage if drives weren't correctly connected, possibly requiring a full reinstall or even OS replacement. This shouldn’t lead to crashes. To verify hardware issues, open Event Viewer → Windows Logs → System, navigate to the right and look for "Filter Current Log." Click the dropdown under Event Sources and choose "WHEA-logger." Highlight any WHEA events, then right-click and save them. Submit the .evtx file here.

I
iPeque
Member
227
12-23-2023, 07:23 PM
#8
It looks like you're unsure about WHEA events and whether to reinstall Windows. Consider checking your system status or contacting support for guidance.
I
iPeque
12-23-2023, 07:23 PM #8

It looks like you're unsure about WHEA events and whether to reinstall Windows. Consider checking your system status or contacting support for guidance.

N
nanaki1324
Junior Member
17
12-24-2023, 11:33 PM
#9
It seems worth trying, though the ongoing shutdowns concern me. I dislike suggesting someone has two problems at once when it's improbable, but I can't see a link between them. The only idea I have is that the storage was incorrectly placed and the shutdowns are unrelated to that matter.
N
nanaki1324
12-24-2023, 11:33 PM #9

It seems worth trying, though the ongoing shutdowns concern me. I dislike suggesting someone has two problems at once when it's improbable, but I can't see a link between them. The only idea I have is that the storage was incorrectly placed and the shutdowns are unrelated to that matter.

L
lorda7medo
Member
53
12-25-2023, 02:39 AM
#10
Check your memory speed. If you're having trouble starting memtest 86, consider disabling secure boot.
L
lorda7medo
12-25-2023, 02:39 AM #10

Check your memory speed. If you're having trouble starting memtest 86, consider disabling secure boot.