F5F Stay Refreshed Hardware Desktop Numerous app crashes are recorded in the event log.

Numerous app crashes are recorded in the event log.

Numerous app crashes are recorded in the event log.

2
2anivb
Member
61
10-19-2022, 09:35 PM
#1
I observed some unusual patterns over the past weeks. My monitors didn't shut down after 15 minutes of inactivity as usual, the AMD control panel would unexpectedly stay open and sharp when left, the hourglass cursor moved quickly, and other odd things happened. Most times, besides these minor issues, I didn’t see any crashes. I also have a brand new Windows 11 install on a different NVMe drive showing the same behavior—only a fresh setup with just a browser and drivers installed. I ran an OCCT CPU+RAM test using AVX2 without problems except for high CPU temperatures. Someone might suggest next steps! Recent updates: I upgraded the MSI BIOS to the latest version due to the CPU concern. I applied Intel defaults and set XMP, otherwise everything stayed the same. Hardware: 2x 1TB NVMe with separate Windows 11 copies. CPU: Z690-a with 32GB DDR5-5600 RAM at 13600k. MSI Z690-a w/32GB DDR5-5600 13600k. Here are three random incidents (id 1001): Fault bucket, type 0 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1 explorer.exe P2 10.0.22621.4169 P3 df363a33 P4 c44a P5 33554432 Fault bucket, type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1 AcroCEF.exe P2 24.3.20112.0 P3 66db57b7 P4 KERNELBASE.dll P5 10.0.22621.4111 P6 03c619d0 Fault bucket, type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1 IAStorDataMgrSvc.exe P2 13.0.3.1001 P3 533de83f P4 IAStorUtil P5 13.0.3.1001 P6 533de824 P7 2e System.NullReferenceException P8 None More Details
2
2anivb
10-19-2022, 09:35 PM #1

I observed some unusual patterns over the past weeks. My monitors didn't shut down after 15 minutes of inactivity as usual, the AMD control panel would unexpectedly stay open and sharp when left, the hourglass cursor moved quickly, and other odd things happened. Most times, besides these minor issues, I didn’t see any crashes. I also have a brand new Windows 11 install on a different NVMe drive showing the same behavior—only a fresh setup with just a browser and drivers installed. I ran an OCCT CPU+RAM test using AVX2 without problems except for high CPU temperatures. Someone might suggest next steps! Recent updates: I upgraded the MSI BIOS to the latest version due to the CPU concern. I applied Intel defaults and set XMP, otherwise everything stayed the same. Hardware: 2x 1TB NVMe with separate Windows 11 copies. CPU: Z690-a with 32GB DDR5-5600 RAM at 13600k. MSI Z690-a w/32GB DDR5-5600 13600k. Here are three random incidents (id 1001): Fault bucket, type 0 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1 explorer.exe P2 10.0.22621.4169 P3 df363a33 P4 c44a P5 33554432 Fault bucket, type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1 AcroCEF.exe P2 24.3.20112.0 P3 66db57b7 P4 KERNELBASE.dll P5 10.0.22621.4111 P6 03c619d0 Fault bucket, type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1 IAStorDataMgrSvc.exe P2 13.0.3.1001 P3 533de83f P4 IAStorUtil P5 13.0.3.1001 P6 533de824 P7 2e System.NullReferenceException P8 None More Details

S
Skyllful
Member
57
10-20-2022, 02:53 AM
#2
Consider trying DDU. If that doesn’t work, switch to an AMD CPU (seriously) or consider removing your Intel CPU—otherwise you might not have any other options. Just a note: those codes are just information, not actual error signals. It’s odd they keep repeating, but it could point to a faulty processor. Replacing it seems like the most straightforward fix unless you have another solution.
S
Skyllful
10-20-2022, 02:53 AM #2

Consider trying DDU. If that doesn’t work, switch to an AMD CPU (seriously) or consider removing your Intel CPU—otherwise you might not have any other options. Just a note: those codes are just information, not actual error signals. It’s odd they keep repeating, but it could point to a faulty processor. Replacing it seems like the most straightforward fix unless you have another solution.