F5F Stay Refreshed Hardware Desktop Question: Computer crashes cause a restart, and following the restart the PC becomes frozen?

Question: Computer crashes cause a restart, and following the restart the PC becomes frozen?

Question: Computer crashes cause a restart, and following the restart the PC becomes frozen?

X
xXSuperNovaXx
Posting Freak
811
12-25-2023, 12:31 AM
#1
Hey everyone.
I've been having a problem with my computer lately, but it only happens in one new game (Arknights Endfield).
The problem is this: while playing, I suddenly experience a crash, which forces me to restart the system. After rebooting, the computer becomes unresponsive. According to Event Viewer, it seems like a forced reboot occurs, but it always fails. I have to restart it again using the power button.
My PC details:
Mobo: B550-A PRO (MS-7C56)
CPU: Ryzen 7 5800X 8-core, 3801 MHz, 8 cores, 16 logical processors
GPU: AMD Radeon RX 7800 XT
RAM: 32GB
OS: Windows 11
I've tried updating drivers, BIOS, reinstalling everything—but nothing fixed it. I'm concerned about the health of my PC.
Attached are screenshots from Event Viewer showing some errors around the crash time.
X
xXSuperNovaXx
12-25-2023, 12:31 AM #1

Hey everyone.
I've been having a problem with my computer lately, but it only happens in one new game (Arknights Endfield).
The problem is this: while playing, I suddenly experience a crash, which forces me to restart the system. After rebooting, the computer becomes unresponsive. According to Event Viewer, it seems like a forced reboot occurs, but it always fails. I have to restart it again using the power button.
My PC details:
Mobo: B550-A PRO (MS-7C56)
CPU: Ryzen 7 5800X 8-core, 3801 MHz, 8 cores, 16 logical processors
GPU: AMD Radeon RX 7800 XT
RAM: 32GB
OS: Windows 11
I've tried updating drivers, BIOS, reinstalling everything—but nothing fixed it. I'm concerned about the health of my PC.
Attached are screenshots from Event Viewer showing some errors around the crash time.

D
dianarose32129
Senior Member
570
12-25-2023, 09:07 AM
#2
Another method to employ is Reliability History/Monitor. It is more user-friendly than Event Viewer and the timeline view might show trends. Review the details – it could be useful or not.
= = = =
D
dianarose32129
12-25-2023, 09:07 AM #2

Another method to employ is Reliability History/Monitor. It is more user-friendly than Event Viewer and the timeline view might show trends. Review the details – it could be useful or not.
= = = =

X
xX_PVPMill_Xx
Member
86
12-26-2023, 02:11 AM
#3
Reliability History displays only the errors pointing to improper shutdowns in Windows. It doesn’t reveal the root cause. I can provide screenshots if required. For uninstalling, it has already been attempted.
X
xX_PVPMill_Xx
12-26-2023, 02:11 AM #3

Reliability History displays only the errors pointing to improper shutdowns in Windows. It doesn’t reveal the root cause. I can provide screenshots if required. For uninstalling, it has already been attempted.

C
ChaaBoyHD
Junior Member
9
12-27-2023, 03:30 PM
#4
Improper shutdowns typically indicate that the system experienced a complete power loss or a failure in one or more parts from Windows' perspective. A frequent reason involves a malfunctioning or deteriorating PSU. PSUs deliver three distinct voltages (3.3, 5, 12) to different system components, and any issue with one voltage can disrupt operations. Additional factors might include user mistakes, forced shutdowns during crashes or hangs, or power-related incidents such as losing the mains supply or experiencing electrostatic discharge or sparks. Windows needs time to perform necessary "housekeeping" tasks when it receives the appropriate signals for shutdown. This process usually includes saving volatile data, closing files, and completing updates before final shutdown. If this step isn't completed correctly, it can lead to file corruption and further complications.

= = = =

Begin with a physical inspection of the system:
Make sure, as usual should be done, that all critical data is safely backed up away from the affected system.
Power down, unplug, open the case.
Remove dust and debris.
Check that all connectors, cards, RAM, jumpers, and case connections are securely installed.
Use a bright flashlight to look for signs of damage: exposed conductors, bent or pinched wires, melting, corrosion, burnt or blackened spots, loose or missing screws, scratches, sagging brackets, swollen parts...
Assess whether the issue persists, lessens, or changes.
If not, proceed to test the PSU with a multimeter or replace it with a known working unit if testing isn't feasible.
C
ChaaBoyHD
12-27-2023, 03:30 PM #4

Improper shutdowns typically indicate that the system experienced a complete power loss or a failure in one or more parts from Windows' perspective. A frequent reason involves a malfunctioning or deteriorating PSU. PSUs deliver three distinct voltages (3.3, 5, 12) to different system components, and any issue with one voltage can disrupt operations. Additional factors might include user mistakes, forced shutdowns during crashes or hangs, or power-related incidents such as losing the mains supply or experiencing electrostatic discharge or sparks. Windows needs time to perform necessary "housekeeping" tasks when it receives the appropriate signals for shutdown. This process usually includes saving volatile data, closing files, and completing updates before final shutdown. If this step isn't completed correctly, it can lead to file corruption and further complications.

= = = =

Begin with a physical inspection of the system:
Make sure, as usual should be done, that all critical data is safely backed up away from the affected system.
Power down, unplug, open the case.
Remove dust and debris.
Check that all connectors, cards, RAM, jumpers, and case connections are securely installed.
Use a bright flashlight to look for signs of damage: exposed conductors, bent or pinched wires, melting, corrosion, burnt or blackened spots, loose or missing screws, scratches, sagging brackets, swollen parts...
Assess whether the issue persists, lessens, or changes.
If not, proceed to test the PSU with a multimeter or replace it with a known working unit if testing isn't feasible.