Random game crashing.

[Stephen sofka]

PC specs:
CPU
Intel Core i7-13700KF 3.4 GHz 16-Core Processor
CPU Cooler
Cooler Master MasterLiquid ML280 Mirror Liquid CPU Cooler
Motherboard
MSI MAG B660 TOMAHAWK WIFI DDR4 ATX LGA1700 Motherboard
Memory
TEAMGROUP T-Force Vulcan Z 32 GB (4 x 16 GB) DDR4-3200 CL16 Memory
Storage
Seagate Barracuda Compute 8 TB 3.5" 5400 RPM Internal Hard Drive
Storage
Western Digital Blue SA510 1 TB M.2-2280 SATA Solid State Drive
Video Card
Zotac GAMING AMP GeForce RTX 4080 SUPER 16 GB Video Card
Case
Lian Li O11 Dynamic Mini ATX Mid Tower Case w/750 W Power Supply
Power Supply
Thermaltake Toughpower SFX 850 W 80+ Platinum Certified Fully Modular SFX Power Supply
Operating System
Microsoft Windows 10 Pro OEM - DVD 64-bit

For about 5 months Ive been runing into crashing problem with games. I have replaced my RAM, PSU, Storage, and RMA'd 2 graphics cards to get a functioning one.

I've ran RAMtest64, several benchmarks to test the gpu, reinstalled Windows, clean installed the games that crash, clean installed graphics drivers with ddu. Im at my whits end. When the different games crash they don't create .dmp files or crash reports, or at least i cant find any in the windows folder for em or using AppCrashView v1.35 Copyright (c) 2009 - 2018 Nir Sofer.
I don't understand why they are crashing, the games are Rust, Dota2, Magic the gathering, Heretics fork, Overwatch 2, Marvel Rivals.
I would LOVE some help or ideas to try and find what is making these games unstable.
At this point I'm open to a reward if someone can help.

[axxi]

Did you update the BIOS to a version that fixed the Intel instability issues? Did you have instability issues (out of video memory crashes) before?

[KnoT]

Well you replaced everything but the CPU and those are known to degrade, updated bios see if that helps (probably not) and then look in to extended RMA for intel 13/14 gen CPU's

[problemsolver]

4 hours ago, Stephen sofka said:

PC specs:
CPU
Intel Core i7-13700KF 3.4 GHz 16-Core Processor
CPU Cooler
Cooler Master MasterLiquid ML280 Mirror Liquid CPU Cooler
Motherboard
MSI MAG B660 TOMAHAWK WIFI DDR4 ATX LGA1700 Motherboard
Memory
TEAMGROUP T-Force Vulcan Z 32 GB (4 x 16 GB) DDR4-3200 CL16 Memory
Storage
Seagate Barracuda Compute 8 TB 3.5" 5400 RPM Internal Hard Drive
Storage
Western Digital Blue SA510 1 TB M.2-2280 SATA Solid State Drive
Video Card
Zotac GAMING AMP GeForce RTX 4080 SUPER 16 GB Video Card
Case
Lian Li O11 Dynamic Mini ATX Mid Tower Case w/750 W Power Supply
Power Supply
Thermaltake Toughpower SFX 850 W 80+ Platinum Certified Fully Modular SFX Power Supply
Operating System
Microsoft Windows 10 Pro OEM - DVD 64-bit

For about 5 months Ive been runing into crashing problem with games. I have replaced my RAM, PSU, Storage, and RMA'd 2 graphics cards to get a functioning one.

I've ran RAMtest64, several benchmarks to test the gpu, reinstalled Windows, clean installed the games that crash, clean installed graphics drivers with ddu. Im at my whits end. When the different games crash they don't create .dmp files or crash reports, or at least i cant find any in the windows folder for em or using AppCrashView v1.35 Copyright (c) 2009 - 2018 Nir Sofer.
I don't understand why they are crashing, the games are Rust, Dota2, Magic the gathering, Heretics fork, Overwatch 2, Marvel Rivals.
I would LOVE some help or ideas to try and find what is making these games unstable.
At this point I'm open to a reward if someone can help.

It's the CPU. There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent - The Verge
You'll need to RMA it. Even if updating the UEFI (BIOS) stopped the crashing, I would still RMA it because it's permanently damaged and it's life is shortened.
Update your UEFI (BIOS) when you get the new CPU so that this doesn't happen to it.

[Stephen sofka]

19 hours ago, problemsolver said:

It's the CPU. There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent - The Verge
You'll need to RMA it. Even if updating the UEFI (BIOS) stopped the crashing, I would still RMA it because it's permanently damaged and it's life is shortened.
Update your UEFI (BIOS) when you get the new CPU so that this doesn't happen to it.

 

On 12/30/2024 at 8:17 PM, KnoT said:

Well you replaced everything but the CPU and those are known to degrade, updated bios see if that helps (probably not) and then look in to extended RMA for intel 13/14 gen CPU's

 

On 12/30/2024 at 8:16 PM, axxi said:

Did you update the BIOS to a version that fixed the Intel instability issues? Did you have instability issues (out of video memory crashes) before?

I have updated the bios once when I build the pc about a year ago. I will try to RMA the CPU, how did you come to that conclusion? process of elimination? I was laboring under what might be the misconception that CPU issues would cause general stability issues rather than what seem to be graphically intensive applications to just outright quit.
Also I have had only one game make a crash report, it is at follows.
"
Version=1
EventType=APPCRASH
EventTime=133800615840830027
ReportType=2
Consent=1
UploadTime=133800615843840026
ReportStatus=268435456
ReportIdentifier=b8e9d432-afc9-490e-9230-0669a54c36a4
IntegratorReportIdentifier=84dcaabf-967d-4358-8388-a4a9937517af
Wow64Host=34404
NsAppName=RotMG Exalt.exe
AppSessionGuid=00005910-0001-0030-de83-056bf15adb01
TargetAppId=W:000653999852e4dcda0b598af290caed2b1800000904!0000ac509792aa9ee681e5255ba10bdc9b6ad9bd59de!RotMG Exalt.exe
TargetAppVer=2023//09//13:01:22:40!af693!RotMG Exalt.exe
BootId=4294967295
TargetAsId=1148
UserImpactVector=271593744
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=b13ce0b759a72b301ddf19b0a00c635c
Response.BucketTable=4
Response.LegacyBucketId=2152467393296491356
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=RotMG Exalt.exe
Sig[1].Name=Application Version
Sig[1].Value=2022.3.10.14226
Sig[2].Name=Application Timestamp
Sig[2].Value=65010ee0
Sig[3].Name=Fault Module Name
Sig[3].Value=UnityPlayer.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=2022.3.10.14226
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=65011305
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000074cc3e
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19045.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=f4dc
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=f4dcd24604dfad0213d2b5008a28b5ba
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0eee
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0eee5a39a743e0a0e8224c9adcd08766
UI[2]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\RotMG Exalt.exe
LoadedModule[0]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\RotMG Exalt.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[4]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\UnityPlayer.dll
LoadedModule[5]=C:\Windows\System32\USER32.dll
LoadedModule[6]=C:\Windows\System32\win32u.dll
LoadedModule[7]=C:\Windows\System32\GDI32.dll
LoadedModule[8]=C:\Windows\System32\gdi32full.dll
LoadedModule[9]=C:\Windows\System32\msvcp_win.dll
LoadedModule[10]=C:\Windows\System32\ucrtbase.dll
LoadedModule[11]=C:\Windows\System32\ole32.dll
LoadedModule[12]=C:\Windows\System32\RPCRT4.dll
LoadedModule[13]=C:\Windows\System32\combase.dll
LoadedModule[14]=C:\Windows\System32\SHLWAPI.dll
LoadedModule[15]=C:\Windows\System32\msvcrt.dll
LoadedModule[16]=C:\Windows\System32\SETUPAPI.dll
LoadedModule[17]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[18]=C:\Windows\System32\cfgmgr32.dll
LoadedModule[19]=C:\Windows\System32\bcrypt.dll
LoadedModule[20]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[21]=C:\Windows\System32\sechost.dll
LoadedModule[22]=C:\Windows\System32\SHELL32.dll
LoadedModule[23]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[24]=C:\Windows\System32\IMM32.dll
LoadedModule[25]=C:\Windows\System32\CRYPT32.dll
LoadedModule[26]=C:\Windows\System32\WS2_32.dll
LoadedModule[27]=C:\Windows\SYSTEM32\OPENGL32.dll
LoadedModule[28]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[29]=C:\Windows\SYSTEM32\WINHTTP.dll
LoadedModule[30]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[31]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[32]=C:\Windows\SYSTEM32\GLU32.dll
LoadedModule[33]=C:\Program Files (x86)\Steam\gameoverlayrenderer64.dll
LoadedModule[34]=C:\Windows\System32\PSAPI.DLL
LoadedModule[35]=C:\Windows\system32\apphelp.dll
LoadedModule[36]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[37]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[38]=C:\Windows\system32\uxtheme.dll
LoadedModule[39]=C:\Windows\System32\shcore.dll
LoadedModule[40]=C:\Windows\SYSTEM32\windows.storage.dll
LoadedModule[41]=C:\Windows\SYSTEM32\Wldp.dll
LoadedModule[42]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[43]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\GameAssembly.dll
LoadedModule[44]=C:\Windows\SYSTEM32\dbghelp.dll
LoadedModule[45]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[46]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\baselib.dll
LoadedModule[47]=C:\Windows\System32\clbcatq.dll
LoadedModule[48]=C:\Windows\System32\CoreMessaging.dll
LoadedModule[49]=C:\Windows\System32\MSCTF.dll
LoadedModule[50]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[51]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[52]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9425e4c3b1ac1c47\nvldumdx.dll
LoadedModule[53]=C:\Windows\SYSTEM32\msasn1.dll
LoadedModule[54]=C:\Windows\SYSTEM32\cryptnet.dll
LoadedModule[55]=C:\Windows\SYSTEM32\cryptbase.dll
LoadedModule[56]=C:\Windows\SYSTEM32\drvstore.dll
LoadedModule[57]=C:\Windows\SYSTEM32\devobj.dll
LoadedModule[58]=C:\Windows\System32\wintrust.dll
LoadedModule[59]=C:\Windows\System32\imagehlp.dll
LoadedModule[60]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[61]=C:\Windows\system32\rsaenh.dll
LoadedModule[62]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9425e4c3b1ac1c47\nvgpucomp64.dll
LoadedModule[63]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9425e4c3b1ac1c47\nvwgf2umx.dll
LoadedModule[64]=C:\Windows\SYSTEM32\powrprof.dll
LoadedModule[65]=C:\Windows\SYSTEM32\UMPDC.dll
LoadedModule[66]=C:\Windows\system32\nvspcap64.dll
LoadedModule[67]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[68]=C:\Windows\SYSTEM32\dxcore.dll
LoadedModule[69]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9425e4c3b1ac1c47\nvppex.dll
LoadedModule[70]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[71]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[72]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[73]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[74]=C:\Windows\SYSTEM32\amsi.dll
LoadedModule[75]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[76]=C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.24090.11-0\MpOav.dll
LoadedModule[77]=C:\Windows\System32\MMDevApi.dll
LoadedModule[78]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[79]=C:\Windows\SYSTEM32\resourcepolicyclient.dll
LoadedModule[80]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\RotMG Exalt_Data\Plugins\x86_64\lib_burst_generated.dll
LoadedModule[81]=C:\Windows\SYSTEM32\xinput1_3.dll
LoadedModule[82]=C:\Windows\SYSTEM32\dcomp.dll
LoadedModule[83]=C:\Windows\SYSTEM32\textinputframework.dll
LoadedModule[84]=C:\Windows\SYSTEM32\CoreUIComponents.dll
LoadedModule[85]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[86]=C:\Windows\System32\NSI.dll
LoadedModule[87]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[88]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[89]=C:\Windows\system32\mswsock.dll
LoadedModule[90]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[91]=C:\Windows\System32\rasadhlp.dll
LoadedModule[92]=C:\Windows\System32\Windows.UI.dll
LoadedModule[93]=C:\Windows\System32\InputHost.dll
LoadedModule[94]=C:\Windows\System32\WindowManagementAPI.dll
LoadedModule[95]=C:\Windows\SYSTEM32\twinapi.appcore.dll
LoadedModule[96]=C:\Windows\System32\PROPSYS.dll
LoadedModule[97]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[98]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[99]=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\RotMG Exalt_Data\Plugins\x86_64\steam_api64.dll
LoadedModule[100]=C:\Program Files (x86)\Steam\steamclient64.dll
LoadedModule[101]=C:\Program Files (x86)\Steam\tier0_s64.dll
LoadedModule[102]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[103]=C:\Program Files (x86)\Steam\vstdlib_s64.dll
LoadedModule[104]=C:\Windows\SYSTEM32\SSPICLI.DLL
LoadedModule[105]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[106]=C:\Windows\system32\napinsp.dll
LoadedModule[107]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[108]=C:\Windows\system32\wshbth.dll
LoadedModule[109]=C:\Windows\system32\NLAapi.dll
LoadedModule[110]=C:\Windows\System32\winrnr.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19045
OsInfo[3].Key=ubr
OsInfo[3].Value=5247
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=222998136
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.3636.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=65391
OsInfo[19].Key=svolsz
OsInfo[19].Value=930
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.5247.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=MD:283BAEF,ME:3037091,FX:132CC947,ME:3038C64,FX:1335985C,ME:3038CEC,FX:133BD387,MD:3039059,MD:30390AF
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=RotMG Exalt.exe
AppPath=C:\Users\lilso\Documents\RealmOfTheMadGod\Production\RotMG Exalt.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=75B147DF8099ED47A2C83A0BE7181F93
MetadataHash=855889519
"

[Stephen sofka]

Plugging the crash report into CHATGPT, which I have defaulted to when trying to understand crash reports says this. 
"

This crash report indicates that the game RotMG Exalt.exe (part of Realm of the Mad God) has crashed due to an issue involving the UnityPlayer.dll module. Let's break it down:

Key Elements in the Crash Report:

1. Application Info:

   • App Name: RotMG Exalt.exe
   • App Version: 2022.3.10.14226 (This is the version of the RotMG Exalt client that was running)
   • App Timestamp: 65010ee0 (Time when the application was built)

2. Fault Module:

   • Fault Module Name: UnityPlayer.dll
   • Fault Module Version: 2022.3.10.14226 (This corresponds to the Unity version used by the game)
   • Fault Module Timestamp: 65011305

   This is crucial. The error is tied to UnityPlayer.dll, a core Unity engine component responsible for rendering and handling various aspects of a Unity-based game. UnityPlayer.dll often crashes due to issues like memory access errors, missing or corrupted files, or incompatible hardware or drivers.

3. Exception Code:

   • Exception Code: c0000005 (Access violation)
   • Exception Offset: 000000000074cc3e (The specific location in the code where the error occurred)

   The exception code c0000005 is an access violation, which typically happens when the program tries to read or write to a memory location that it shouldn't. This could be caused by:

   • Outdated or corrupted game files.
   • A bug in the Unity engine.
   • Insufficient system resources (memory, GPU, etc.).
   • Hardware or driver issues.

4. Loaded Modules: These are the libraries and files that were loaded into memory when the game ran. Among the notable ones:

   • UnityPlayer.dll (Unity engine)
   • GameAssembly.dll (specific to RotMG Exalt)
   • Steam-related DLLs (indicating the game is running through Steam)

5. System Information:

   • OS Version: Windows 10, version 10.0.19045
   • RAM: 65391 MB (sufficient memory)
   • Graphics Driver: The crash report includes specific NVIDIA libraries, indicating an NVIDIA GPU is in use. The drivers could play a role in the issue if outdated.

Potential Causes of the Crash:

1. Unity Engine Bug: The game uses Unity, and the issue might be due to a bug in the Unity engine itself. It could be related to a specific version of Unity (2022.3.10), which might have compatibility issues with the game or your system.

2. Access Violation (c0000005): This type of crash often happens due to memory issues like:

   • Corrupted files: If any of the game files (especially UnityPlayer.dll) are corrupted, it could trigger this crash. Verifying the integrity of the game files (especially if using a platform like Steam) might help.
   • Outdated drivers: If the graphics drivers or other critical system drivers are outdated, they can conflict with the Unity engine and cause access violations. Ensure that the GPU drivers are up to date.
   • Hardware issues: In rare cases, a failing RAM or graphics card can cause access violations.

3. Steam Overlay or Modifications: The loaded module list includes steam_api64.dll and other Steam-related libraries. Sometimes, the Steam overlay or specific mods can cause instability. Try disabling the Steam overlay or verifying the game without any third-party mods.

4. Out of Memory or Resource Issues: Although the system has sufficient RAM, other factors like CPU usage or GPU memory could cause issues, especially with graphics-heavy games like RotMG.

Steps to Resolve the Crash:

1. Verify Game Files: If you're using a platform like Steam, verify the integrity of the game files to ensure nothing is corrupted.

2. Update Graphics Drivers: Ensure your NVIDIA graphics drivers are up to date. You can visit the NVIDIA website or use a tool like GeForce Experience to check for updates.

3. Check for Game or Unity Updates: If there’s a newer version of RotMG Exalt or Unity, try updating to see if the issue persists.

4. Disable Steam Overlay: Try disabling the Steam overlay to rule out conflicts with it.

5. Run as Administrator: Sometimes, running the game as an administrator can resolve permission-related issues.

6. Reinstall the Game: If verifying the game files doesn't help, consider reinstalling the game to fix any potential corruption in the installation.

By following these steps, you may be able to resolve the issue or at least narrow down the root cause. If the issue persists, you may need to contact the game's support team for further troubleshooting."

[KnoT]

@Stephen sofka 

 

[problemsolver]

On 12/31/2024 at 8:34 PM, Stephen sofka said:

I have updated the bios once when I build the pc about a year ago. I will try to RMA the CPU, how did you come to that conclusion? process of elimination? I was laboring under what might be the misconception that CPU issues would cause general stability issues rather than what seem to be graphically intensive applications to just outright quit.

Extensive experience in how they fail and that they all will  fail if the UEFI wasn't updated with the latest update from... 2 months ago. So, if you've used the PC for a year, then you're 100% guaranteed to have a bad CPU at this point. Because Intel wasn't able to fix it until October/November of 2024 (when the motherboard manufactures released the updates).

 

There's nothing you could've done. Don't worry though, just update your UEFI with the latest version and you should be fine for the replacement CPU. Again, you can try updating now. I've seen it 'fix' a few that are unstable... but the damage is already done, hence my recommendation to replace it regardless.

Also, be warned, updating (with your current bad CPU) poses the risk of rendering the PC unusable due to the new microcode limiting voltages and your chip--already being damaged--may need more voltage just to run.