Games Crashing to Desktop After Playing for a Bit - 0xc0000005 error
I have a Powerspec G468 PC that has worked great for the past several years for gaming. I updated the OS from Windows 10 to Windows 11 sometime last year. The past few months, I have started noticing games crashing to desktop after a random amount of time. At first I thought it was just RDR2, but then it started happening with other steam games I was playing. When looking at the crash dumps for the individual games, it references a 0xc0000005 error. It only seems to happen when playing games. Games that I have had crash recently:
- RDR2
- BG3
- RE Village
I have tried a lot of different fixes listed online, and nothing has seemed to work so far. I have tried:
- Uninstalling GPU drivers with DDU and doing a clean install
- Running sfc /scannow
- Running chkdsk /f /r C:
- Running Windows Memory Diagnostic to check RAM
- Scanning for malware
- Uninstalling 3rd party antivirus software (ESET)
- Disabling Windows Defender
- Performing a clean boot
None of these have resulted in a consistent fix. I am starting to get to my wits end trying to figure this out. It's frustrating to have games constantly crash on an expensive gaming PC. Here is an example WinDbg crash dump analysis from a recent RDR2:
******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify checksum for USER32.dll *** WARNING: Unable to verify checksum for ole32.dll *** WARNING: Unable to verify checksum for nvwgf2umx.dll *** WARNING: Unable to verify checksum for twinapi.appcore.dll KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 31 Key : Analysis.Elapsed.mSec Value: 1531 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 15 Key : Analysis.Init.Elapsed.mSec Value: 18497 Key : Analysis.Memory.CommitPeak.Mb Value: 295 Key : Failure.Bucket Value: INVALID_POINTER_READ_c0000005_RDR2.exe!Unknown Key : Failure.Hash Value: {b74c0c48-83bc-bfb4-70e3-8ada6dd51a70} Key : Timeline.Process.Start.DeltaSec Value: 4866 Key : WER.Process.Version Value: 1.0.1491.18 FILE_IN_CAB: 5e7fbdc3-8c0c-403c-a4ab-7063e5a268e8.dmp NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 CONTEXT: (.ecxr) rax=00000000ffffffff rbx=000000000000fc00 rcx=000000000000fc00 rdx=000002def84e7c01 rsi=000000000000fc00 rdi=000002de9d1e8d00 rip=00007ff6833411c3 rsp=000000e5072df830 rbp=000000e5072dfa00 r8=0000000000000006 r9=000002e6378b2af0 r10=000000e5072df410 r11=000000e5072df840 r12=0000000000000000 r13=00000000ffffff00 r14=0000000000000250 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0033 ss=0000 ds=0000 es=0000 fs=0053 gs=002b efl=00010206 RDR2+0x6311c3: 00007ff6`833411c3 3a9199000000 cmp dl,byte ptr [rcx+99h] ds:00000000`0000fc99=?? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff6833411c3 (RDR2+0x00000000006311c3) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 000000000000fc99 Attempt to read from address 000000000000fc99 PROCESS_NAME: RDR2.exe READ_ADDRESS: 000000000000fc99 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 000000000000fc99 STACK_TEXT: 000000e5`072df830 00007ff6`8334080c : 00000000`00000000 00000000`0000fc00 000002de`9d1e8d00 00007ff6`0fff1a3e : RDR2+0x6311c3 000000e5`072df8e0 00007ff6`833416ae : 00000000`00000001 000000e5`072dfaa8 00000000`00000000 00000000`00000001 : RDR2+0x63080c 000000e5`072df960 00007ff6`858a007d : 000000e5`072dfab8 00000000`00000004 00000000`00000000 000002e4`00449500 : RDR2+0x6316ae 000000e5`072df990 00007ff6`8326400f : 00000000`00000001 00000000`00000000 0000ffff`00000003 000000e5`00000002 : RDR2+0x2b9007d 000000e5`072dfa60 00007ff6`8588363c : 000002de`0000001b 00007ff6`8381e200 00000000`00000000 000000e5`00000000 : RDR2+0x55400f 000000e5`072dfb40 00007ff6`832659e0 : 00000000`00020009 00000000`00000004 00000000`00000007 00007ff6`88818a60 : RDR2+0x2b7363c 000000e5`072dfbc0 00007ff6`83290e2f : 000002de`84e6c320 00000000`00000000 00007ff6`00000012 0000ffff`ffffffff : RDR2+0x5559e0 000000e5`072dfc40 00007ff6`85a18b5f : 0000ffff`ffffffff 00000000`00000000 00000000`00000000 000002de`826e06f0 : RDR2+0x580e2f 000000e5`072dfc90 00007ff6`8529e60f : 00007ff6`8805a6b0 00000000`00000000 00007ff6`00000000 00000000`00000000 : RDR2+0x2d08b5f 000000e5`072dfce0 00007ffb`bd41257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : RDR2+0x258e60f 000000e5`072dfd60 00007ffb`beb6aa78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x1d 000000e5`072dfd90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28 SYMBOL_NAME: RDR2+6311c3 MODULE_NAME: RDR2 IMAGE_NAME: RDR2.exe STACK_COMMAND: ~86s; .ecxr ; kb FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_RDR2.exe!Unknown OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 1.0.1491.18 FAILURE_ID_HASH: {b74c0c48-83bc-bfb4-70e3-8ada6dd51a70} Followup: MachineOwner
I haven't done anything custom with drivers or overclocking/underclocking. Everything is running on the default settings that came on the PC. I do have a few peripherals attached to my PC, but I don't think those would be causing the issue:
- Focusrite Scarlet Solo
- Steam Deck
I appreciate any help that you guys can give me. I feel like I've run out of options to try listed based on Google search.
Comments
-
What's in the event viewer log under Custom Views - Administrative Events at the time of the crash?
-
@PowerSpec_MikeW That's one of the frustrating things. Most of the time, it doesn't seem like there's a particularly related error there in the Event Viewer. I get an Autopilot.dll WIL error frequently around the time of crashing, but I don't think it's really related since it does that super frequently. I also get this error on my Windows laptop, and it doesn't crash playing the same games. Here's the error I am referencing:
-
Lets try this. Open elevated command prompt and type:
- net user /add Test
- net localgroup administrators /add Test
Creates a local administrator user. Then sign out and into the new account. If you game on this new local account, do the game still crash?
-
@PowerSpec_MikeW I will definitely try this and report back. The thought would be that this is fixing what exactly? Some sort of permissions issue with the game folders? My default account is already listed as an administrator, so I'm just curious what this would potentially resolve
-
Would confirm those autopilot warnings are significant. If we take Windows Hello out of the equation, that shouldn't be an issue.
-
@PowerSpec_MikeW I started getting the autopilot warnings on the local admin user before even trying to run any games. Would that be expected?
-
No, that's strange. Has this system ever been attached to a corporate network for job and enrolled in InTune?
-
@PowerSpec_MikeW no. it's never been connected to a corporate network or enrolled in InTune. Purely for recreational use. As I mentioned, I also see this error pervasively on my new gaming laptop that i have connected to the same Microsoft account. I have not been experiencing any of these crashing issues on that computer
-
Understood, we need to rule it out. On the 'Test' account go into services.msc. Disable the Microsoft Automatic Sign-in Assistant service. Verify the error stops then try some games and see if it's stable.
-
@PowerSpec_MikeW Sounds good. I went to the test account and disabled the Microsoft Account Sign-in Assistant service. I'm no longer seeing the autopilot.dll error. However I did see a few things pop up in the Event Viewer shortly afterwards:
^don't know if this could be related to your question above, but it seemed interesting. I also saw the following several errors, although I'm not sure if these have any relevance either:
I'll try playing some games to see if I get further crashes
-
Doesn't look promising with those Nvidia driver crashes already appearing. NoCat is a wireless authentication portal. Let me know. If this still crashes, we'll know to troubleshoot the GPU/driver next.
-
@PowerSpec_MikeW No crashes when I played last night, but I wasn't playing for too long, so that's not a particularly great test. I'll try again today. Are there any programs that I should try running to stress test my hardware while I'm working on my other computer today, or do you think playing the games that crashed and waiting to see if they crash is the best approach
-
OCCT is pretty solid. https://www.ocbase.com/
-
@PowerSpec_MikeW is there any particular test you would recommend running from OCCT? Seems like there are a ton of different options. I currently have it running the "Platinum Stability Certificate" system test. Seemed like that should cover all the hardware
-
GPU Standard and Adaptive to start.
-
@PowerSpec_MikeW the system stability certificate test passed without any errors. It won't let me post a link to it here, but this is the path after the ocbase.com base url: stabilityCertificate/6527411774380361dc545cba
The test locked up my computer all day. I'll try playing some games tomorrow again to see if I get any crashes
-
That'll be the real test. Let me know how it goes.
-
@PowerSpec_MikeW just got a crash from RDR2 on the test account. No corresponding event in the Administrative Events tab of the Event Viewer. Same 0xc0000005 error code:
******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify checksum for RDR2.exe *** WARNING: Unable to verify checksum for KERNEL32.DLL *** WARNING: Unable to verify checksum for USER32.dll *** WARNING: Unable to verify checksum for ole32.dll *** WARNING: Unable to verify checksum for twinapi.appcore.dll KEY_VALUES_STRING: 1 Key : AV.Fault Value: Execute Key : Analysis.CPU.mSec Value: 171 Key : Analysis.Elapsed.mSec Value: 7037 Key : Analysis.IO.Other.Mb Value: 7 Key : Analysis.IO.Read.Mb Value: 21 Key : Analysis.IO.Write.Mb Value: 51 Key : Analysis.Init.CPU.mSec Value: 61 Key : Analysis.Init.Elapsed.mSec Value: 6127 Key : Analysis.Memory.CommitPeak.Mb Value: 180 Key : Failure.Bucket Value: SOFTWARE_NX_FAULT_c0000005_RDR2.exe!Unknown Key : Failure.Hash Value: {7cec1f1e-1ef5-76ce-1407-f7e86460e7ca} Key : Timeline.Process.Start.DeltaSec Value: 2608 Key : WER.Process.Version Value: 1.0.1491.18 FILE_IN_CAB: 8efaa412-5f3f-4e7a-bcb9-c29855b95104.dmp NTGLOBALFLAG: 0 CONTEXT: (.ecxr) rax=00007ff63b4e6ed8 rbx=0000000000000000 rcx=0000021c660701b0 rdx=0000021c660701b0 rsi=000002139d977c40 rdi=0000021c660701b0 rip=0000001400000010 rsp=000000b1b8bff688 rbp=000000b1b8bff760 r8=000002139d977c40 r9=0000021929f65910 r10=0000021b1ed85760 r11=000000b1b8bff760 r12=0000000000000000 r13=00007ff63dceb040 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl nz na pe nc cs=0033 ss=0000 ds=0000 es=0000 fs=0053 gs=002b efl=00010202 00000014`00000010 ?? ??? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 0000001400000010 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 0000001400000010 Attempt to execute non-executable address 0000001400000010 PROCESS_NAME: RDR2.exe EXECUTE_ADDRESS: 1400000010 FAILED_INSTRUCTION_ADDRESS: +0 00000014`00000010 ?? ??? ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 0000001400000010 IP_ON_HEAP: 0000001400000010 IP_IN_FREE_BLOCK: 1400000010 STACK_TEXT: 000000b1`b8bff688 00007ff6`3a1c86d2 : 0000021b`ec081bc0 000000b1`b8bff700 00007ff6`3dceb060 00000000`00000000 : 0x00000014`00000010 000000b1`b8bff690 00007ff6`3b3336ad : 0000021c`66070101 00000000`00000000 00000000`00000000 00000000`00000000 : RDR2+0x20a86d2 000000b1`b8bff6c0 00007ff6`3b321a2d : 0000021c`660701b0 000000b1`b8bff760 00007ff6`3dceb080 00007ff6`3b32fe02 : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x3937bd 000000b1`b8bff6f0 00007ff6`3b32fa95 : 00000000`00000000 00007ff6`3dceb080 00000213`9d977c40 00000000`00000001 : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x381b3d 000000b1`b8bff770 00007ff6`3b0ea584 : 00000213`9d977c40 00000000`00000001 00007ff6`3dceb040 00000000`00000000 : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x38fba5 000000b1`b8bff7a0 00007ff6`3b0eaae6 : 00000213`9d977c40 00007ff6`3dc00f00 00000000`00000004 00000000`00000001 : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x14a694 000000b1`b8bff7d0 00007ff6`3b0eac2e : 00000000`00000000 00007ff6`3dc00f00 00000213`803a13b0 00000000`00000000 : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x14abf6 000000b1`b8bff890 00007ff6`3b0eafe1 : 00000000`00000000 00000213`803a13b0 00007ff6`3d46cb60 00000000`fffffff0 : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x14ad3e 000000b1`b8bff8c0 00007ff6`3a6ad11a : 00000000`00000000 00000213`803a13b0 00000213`00000000 00000000`0000086c : RDR2!NVSDK_NGX_VULKAN_Shutdown+0x14b0f1 000000b1`b8bff8f0 00007ff6`3a6ae60f : 00000000`00000000 00000000`000008b8 00007ff6`3d46a340 00000000`00000000 : RDR2+0x258d11a 000000b1`b8bffb50 00007fff`919b257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : RDR2+0x258e60f 000000b1`b8bffbd0 00007fff`92ccaa78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x1d 000000b1`b8bffc00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28 STACK_COMMAND: ~2s; .ecxr ; kb SYMBOL_NAME: rdr2+20a86d2 MODULE_NAME: RDR2 IMAGE_NAME: RDR2.exe FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_RDR2.exe!Unknown OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 1.0.1491.18 FAILURE_ID_HASH: {7cec1f1e-1ef5-76ce-1407-f7e86460e7ca} Followup: MachineOwner ---------
A little hard to know if it's just an issue related to this game or not. There are a lot of complaints online about it being buggy. I'll try a different one tomorrow to test, but I'm guessing I'll probably get another crash at some point
-
I believe you will. Lets try a clean reinstall with DDU: https://www.wagnardsoft.com/forums/viewtopic.php?t=4699
Please run that and clean all Nvidia drivers, then we'll install the latest driver and see if the issue persists.
-
@PowerSpec_MikeW I just finished a clean uninstall with DDU and reinstalled the latest driver that I had predownloaded to my desktop. I avoided installing the GEForce Experience app this time as I read that it can cause some issues. Should I reinstall the NVIDIA Control Panel or no?
-
Nvidia control panel will automatically download from the Microsoft Store.
-
@PowerSpec_MikeW just had another crash. this time on the new Lords of the Fallen Game:
******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* KEY_VALUES_STRING: 1 Key : AV.Fault Value: Execute Key : Analysis.CPU.mSec Value: 390 Key : Analysis.Elapsed.mSec Value: 625 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 2 Key : Analysis.Init.CPU.mSec Value: 30 Key : Analysis.Init.Elapsed.mSec Value: 5986 Key : Analysis.Memory.CommitPeak.Mb Value: 255 Key : Failure.Bucket Value: SOFTWARE_NX_FAULT_CODE_c0000005_LOTF2-Win64-Shipping.exe!Unknown Key : Failure.Hash Value: {5bf7abe7-39eb-12d4-1d14-e94a475e2d28} Key : Timeline.Process.Start.DeltaSec Value: 1347 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 Key : WER.Process.Version Value: 5.1.1.0 FILE_IN_CAB: UEMinidump.dmp CONTEXT: (.ecxr) rax=00007ff711410c38 rbx=0000021108444288 rcx=0000021261a1a180 rdx=0000002d1087f540 rsi=00000211e92b4e80 rdi=000002113f07de48 rip=00007ff711412038 rsp=0000002d1087f508 rbp=0000000000001ddf r8=0000021132340000 r9=00007ff7127fb700 r10=000002125e11cf28 r11=0000002d1087f598 r12=0000000000000000 r13=0000000000000012 r14=0000000000000016 r15=0000000000002001 iopl=0 nv up ei pl nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206 LOTF2_Win64_Shipping!D3D12SDKVersion+0x1233764: 00007ff7`11412038 4c ??? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff711412038 (LOTF2_Win64_Shipping!D3D12SDKVersion+0x0000000001233764) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 00007ff711412038 Attempt to execute non-executable address 00007ff711412038 PROCESS_NAME: LOTF2-Win64-Shipping.exe EXECUTE_ADDRESS: 7ff711412038 FAILED_INSTRUCTION_ADDRESS: LOTF2_Win64_Shipping!D3D12SDKVersion+1233764 00007ff7`11412038 4c ??? ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 00007ff711412038 STACK_TEXT: 0000002d`1087f508 00007ff7`0dc73d26 : 0000a382`e1d7fd98 00000210`fbf20141 00000211`08444288 00000000`00001dde : LOTF2_Win64_Shipping!D3D12SDKVersion+0x1233764 0000002d`1087f510 00007ff7`0dc71d7d : 00000211`08444201 0000002d`00000012 00000000`00001001 00000000`00004000 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x1ef8fc6 0000002d`1087f5a0 00007ff7`0b419132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x1ef701d 0000002d`1087f5e0 00007ff7`0b41c844 : 00000213`09e6f518 0000002d`1087f700 00000000`00000000 00000000`00000000 : LOTF2_Win64_Shipping!AK::SoundEngine::StopProfilerCapture+0x1f8562 0000002d`1087f6e0 00007ff7`0cfcbf85 : 00000213`09e6f518 00000210`fc72db70 00000213`09e6f518 00007ff7`0cfcad1b : LOTF2_Win64_Shipping!AK::SoundEngine::StopProfilerCapture+0x1fbc74 0000002d`1087f710 00007ff7`0cfc2571 : 00000000`00000000 00000000`00000000 00007ff7`12a20f80 00007ff7`0cfdb2cd : LOTF2_Win64_Shipping!ffxGetVkImageView+0x1251225 0000002d`1087f790 00007ff7`0cfdbee3 : 00000000`00000000 0000002d`1087f840 00000000`00000035 00007ff7`12a20f80 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x1247811 0000002d`1087f7e0 00007ff7`0cfc78a0 : 00007ff7`0cfc7880 00000000`00000000 00000210`8b2ff000 00000210`00000551 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x1261183 0000002d`1087f950 00007ff7`0d02cc64 : 00000210`885e0c80 00000000`00000000 00000000`00000000 00000000`00000000 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x124cb40 0000002d`1087f990 00007ff7`0d1304d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x12b1f04 0000002d`1087f9c0 00007ff7`0d12b011 : 00000210`885e0c80 00000000`00000000 00000000`00000000 00000000`00000000 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x13b5777 0000002d`1087f9f0 00007ffd`3495257d : 00000210`885e0c80 00000000`00000000 00000000`00000000 00000000`00000000 : LOTF2_Win64_Shipping!ffxGetVkImageView+0x13b02b1 0000002d`1087fa30 00007ffd`35f6aa78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1d 0000002d`1087fa60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28 SYMBOL_NAME: LOTF2_Win64_Shipping+1233764 MODULE_NAME: LOTF2_Win64_Shipping IMAGE_NAME: LOTF2-Win64-Shipping.exe STACK_COMMAND: ~19s; .ecxr ; kb FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_CODE_c0000005_LOTF2-Win64-Shipping.exe!Unknown OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 5.1.1.0 FAILURE_ID_HASH: {5bf7abe7-39eb-12d4-1d14-e94a475e2d28} Followup: MachineOwner
^this was the only thing i could see in the event viewer around the time of the crash
-
Just an access violation, pretty generic CTD. How long were you playing when this happened?
Lets try this. Go into the BIOS with 'Del' on startup and on the AI Tweaker Menu, set AI Overclock Tuner to Auto. Save and exit ( F10 ). Then game some more and see what we've got.
-
@PowerSpec_MikeW I had been playing for about an hour before it crashed the first time. Then it crashed several times in relatively quick succession during a boss fight. I'll try changing that BIOS setting next weekend when I get home. Hopefully that will help
-
@PowerSpec_MikeW making that change in the BIOS seems to have fixed the issue. I haven't had any crashes in the new LOTF or BG3 since I changed that setting last weekend. What would this suggest was the issue?
-
We disabled XMP. Dropped your memory from 3600 to the JEDEC 2133 speed. It would appear the memory has become unstable over the life of the system. Could be a failing stick, could just be the effects of capacitor aging which we can tweak around. So with memory issues you want to know if the errors are coming from the stick on the IMC and Memtest86 is really good at uncovering this based on which of the tests fail.
I would first create a bootable memtest86 drive here: https://www.memtest86.com/
Then set it back to XMP II and run the tests overnight, it will take several hours for four full passes. Let me know the results. Switch it back to Auto when you're done and stay on Auto for now. We don't want the memory instability to damage your OS.
Categories
- All Categories
- 1 The Blog
- 1 What's Trending
- 7.4K The Community
- 3K General Discussion
- 102 New Members
- 789 Consumer Tech
- 197 Prebuilt PCs and Laptops
- 154 Software
- 30 Audio/Visual
- 50 Networking & Security
- 4 Home Automation
- 5 Digital Photography
- 12 Content Creators
- 28 Hobby Boards & Projects
- 75 3D Printing
- 83 Retro Arcade/Gaming
- 60 All Other Tech
- 287 PowerSpec
- 2.5K Store Information and Policy
- 140 Off Topic
- 40 Community Ideas & Feedback
- 596 Your Completed Builds
- 3.6K Build-Your-Own PC
- 2.6K Help Choosing Parts
- 303 Graphics Cards
- 324 CPUs, Memory, and Motherboards
- 134 Cases and Power Supplies
- 50 Air and Liquid Cooling
- 46 Monitors and Displays
- 88 Peripherals
- 57 All Other Parts
- 62 Featured Categories
We love seeing what our customers build
Submit photos and a description of your PC to our build showcase
Submit NowLooking for a little inspiration?
See other custom PC builds and get some ideas for what can be done
View Build ShowcaseSAME DAY CUSTOM BUILD SERVICE
If You Can Dream it, We Can Build it.
Services starting at $149.99