F5F Stay Refreshed Hardware Desktop Random System Crashes While Running Adobe Software (Doesn't Happen While Gaming or Doing Other Work)

Random System Crashes While Running Adobe Software (Doesn't Happen While Gaming or Doing Other Work)

Random System Crashes While Running Adobe Software (Doesn't Happen While Gaming or Doing Other Work)

Pages (2): Previous 1 2
K
Kynedee
Posting Freak
784
07-20-2025, 09:22 PM
#11
The listed occurrences and the corresponding screenshot reference Event1336.evtx, Event1451.evtx, Event1456.evtx, and Event1458.evtx.
K
Kynedee
07-20-2025, 09:22 PM #11

The listed occurrences and the corresponding screenshot reference Event1336.evtx, Event1451.evtx, Event1456.evtx, and Event1458.evtx.

I
isaac17gamer
Member
73
07-20-2025, 09:22 PM
#12
The shutdowns are arranged based on the CPU, which explains the WHEA event you see. Decoding these events is a bit more difficult than interpreting standard BSOD messages because the RawData section (the error packet) is quite extensive and requires manual processing. The CPU can initiate a shutdown if it detects a critical problem that prevents timely OS notification and results in a BSOD. The CPU keeps track of itself and PCIe devices. On the general event page, you’ll find details about which CPU component identified the issue, not the specific cause. From these logs, it seems the CPU is responsible. If you’re experimenting with overclocking or undervolting, remove that unit. This includes XMP/DOCP/EXPO settings exceeding the officially supported limits set by the CPU manufacturer. I’m unsure if you still have the 5800X mentioned in an earlier post—it has a maximum officially supported memory speed of 3200MT/s. If you still own that CPU or continue using AMD, check your BIOS and ensure Precision Boost Overdrive (PBO) is turned off. PBO can overclock the CPU when there’s enough thermal margin; this isn’t the same as regular Turbo.
I
isaac17gamer
07-20-2025, 09:22 PM #12

The shutdowns are arranged based on the CPU, which explains the WHEA event you see. Decoding these events is a bit more difficult than interpreting standard BSOD messages because the RawData section (the error packet) is quite extensive and requires manual processing. The CPU can initiate a shutdown if it detects a critical problem that prevents timely OS notification and results in a BSOD. The CPU keeps track of itself and PCIe devices. On the general event page, you’ll find details about which CPU component identified the issue, not the specific cause. From these logs, it seems the CPU is responsible. If you’re experimenting with overclocking or undervolting, remove that unit. This includes XMP/DOCP/EXPO settings exceeding the officially supported limits set by the CPU manufacturer. I’m unsure if you still have the 5800X mentioned in an earlier post—it has a maximum officially supported memory speed of 3200MT/s. If you still own that CPU or continue using AMD, check your BIOS and ensure Precision Boost Overdrive (PBO) is turned off. PBO can overclock the CPU when there’s enough thermal margin; this isn’t the same as regular Turbo.

A
AllanDC_
Junior Member
30
07-20-2025, 09:22 PM
#13
The CMOS battery reset didn’t resolve the issue—it failed again after roughly 4-5 hours of use. I believe I’ve resolved it. I performed a complete PC reset and updated the BIOS (just behind the latest version). The system has run smoothly for the past two days, with no problems during my 12-14 hour work sessions in Premiere Pro and Photoshop. If stability continues for a week, I’ll post on the forum to mark it as solved. It could have been an Adobe or BIOS glitch, but I’m glad it’s working now!
A
AllanDC_
07-20-2025, 09:22 PM #13

The CMOS battery reset didn’t resolve the issue—it failed again after roughly 4-5 hours of use. I believe I’ve resolved it. I performed a complete PC reset and updated the BIOS (just behind the latest version). The system has run smoothly for the past two days, with no problems during my 12-14 hour work sessions in Premiere Pro and Photoshop. If stability continues for a week, I’ll post on the forum to mark it as solved. It could have been an Adobe or BIOS glitch, but I’m glad it’s working now!

Pages (2): Previous 1 2