Frequent crashes 13700k, Faulty CPU?

Zanmorian · ‎03-19-2024

Hello and a good day,

I'd like to share my two month long journey figuring out what is wrong with my PC.

I'll start at the very beginning.

I bought the CPU and MB around January 2023 and it worked fine. Around two months ago I began to see a few game crashes, and also a BSOD. Upon loading back in and checking out task manager I saw the PC was only detecting 1 out of 2 RAM sticks. I relocated one and then the PC saw 2 sticks again. But I kept having game crashes and also app crashes by now (Discord and Firefox mostly). In windows event viewer I saw "Exception code: 0xc0000005" and "Faulting module name: nvwgf2umx.dll" mentioned in most of the errors.

After a bit of googling I:

Reinstalled my nvidia drivers. (Also using DDU)

Installed older versions of the Nvidia driver.

Checked my system for outdated drivers.

Disabled XMP.

Updated my bios to the latest version.

Reset my CMOS multiple times.

Reset Windows.

Used Memtest to check for faulty RAM. I tested both sticks at the same time, no errors. I tested them both one at a time. No errors.

I stress tested my GPU with the Heaven benchmark and the 3DMark Benchmark multiple times, both passed everytime.

I stress tested my CPU using the Intel Diagnostics tool and CPU-Z. On both the CPU passes.

I removed one RAM stick and with that the problem subsided.

So I figured that even though I tested the RAM it had to be faulty. I ordered a set of 2 new RAM sticks. Exactly the same RAM as the old ones.

I installed them with the RAM stick on which the system was working. So I had 3 RAM installed.

The crashes started to appear again!

I removed the last old RAM stick, so only the 2 new ones now. Still crashes. I left only 1 RAM stick, the problems went away again. I used memtest again to check the new RAM sticks, also no errors.

The system worked on every RAM stick as long as there was only one. Didn't matter which slot on the MB. Though not always on slot B2.

By now I figured it had to be the MB. I also by this point suspected the CPU's memory controller. But read that in these cases it's almost always the MB, not the CPU.

So I ordered a new MB and new RAM to go with it. (just to be sure, and with this I also wanted to upgrade to DDR5)

The: "ASrock Z790 PG Lightning" and "Corsair DDR5 Vengance 2x32GB"

During installation I checked the CPU for damage, but it looked normal.

But the crashes remained...

I did another complete reinstall of my nvidia drivers. But it only seemed to be getting worse now.

Upon starting certain games like Dying light 2 the PC just froze. I did another bunch of tests focused on the CPU now.

With Prime95 the PC immediatly froze upon start of the test.

The Intel Diagnostics tool failed at the prime number part of the test.

But then. When looking through the ASrock Bios. I changed a setting.

They call it: Vcore compensation. It's on "Auto" by default. And can be changed to Levels 1-5.

After changing it to level 1 the crashes and freezes went away. Except for one game, Old World. The Intel Diagnostics tool also passes when using that setting.

When trying to turn on XMP or setting a custom RAM frequency the problems reappear. And when using the benchmark in CPU-Z I get a BSOD.

Because I also saw some weird readings using HWinfo (like the +5v rail reading as only 1.6v and the +12v rail going to 11.72 under load) and the Vcore difference fix(?) together with my PSU being old I ordered a new one. Just maybe this was a PSU problem.

It was not.

So now after 2 months and replacing almost all my hardware all fingers point towards a kind of faulty CPU in my eyes. Though I don't understand why the system is relatively stable when changing the Vcore setting.

Is this a faulty CPU or something else? And if it's something else, what can it be?

Attached I have a few examples of the crashes and a SSU report.

Hopefully we can figure something out.

Thank you in advance,

- Zanmorian

Zanmorian · ‎03-19-2024

Here are the attachments

vmovups · ‎03-19-2024

Can you go in the file explorer and search *.dmp in your C: drive? Then upload the Helldivers 2 and Discord/Firefox crash dumps to the thread so Intel can investigate.

Another thing, does Helldivers 2 crash during shader compilation or startup only? both at startup and ingame? seemingly always after doing a specific action but still randomly?

If yes to any of these questions it's possible you're affected by the epidemic of 13 and 14 gen Intel CPUs going defective.

Another thing you can try is having the two sticks in, with XMP but you reduce the core frequencies or play with the power plan set to power saving.

The fact you're still getting crashes despite confirming the PSU, Motherboard and RAM aren't causing it makes me believe the CPU is the root cause of the crashes.

Zanmorian · ‎03-19-2024

Hi, thank you for the input.

The crashes in Helldivers 2 (and any game really) can vary from immediatly on launch to a few minutes in game to around 30 minutes ingame. Old World on the other hand only crashes during the AI's turn(turn based game) even with the Vcore change.

And yes, the fact that I kind of singled out the CPU does point all fingers to it. It's just weird that it kind of works with the Vcore change.

I have a few mini dump files. But it won't let me upload them. Gives this error: The attachment's escapefromtarkov.exe.12792.dmp content type (application/octet-stream) does not match its file extension and has been removed.

I guess I can just copy them here:

*** WARNING: Unable to verify checksum for OldWorld.exe

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 405

    Key  : Analysis.Elapsed.mSec
    Value: 864

    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: 124

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3184

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 127

    Key  : Failure.Bucket
    Value: SOFTWARE_NX_FAULT_c0000005_OldWorld.exe!unknown_error_in_process

    Key  : Failure.Hash
    Value: {bea16f79-07c3-5018-267e-40083fb69151}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 15504

    Key  : Timeline.Process.Start.DeltaSec
    Value: 570

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 2021.3.34.9831


FILE_IN_CAB:  OldWorld.exe.16180.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)rax=00000047d345e000 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000000074d1 rsi=0000000000000003 rdi=000001f7256e80f0
rip=00000047d345dff0 rsp=00000047d345dfb0 rbp=00000047d345f440
 r8=000000000000001d  r9=00007ff9f53165c0 r10=000001f6ac313be0
r11=00007ff9f4dcf5f0 r12=000001f7256e80f0 r13=0000000000000009
r14=0000000000000000 r15=000001f7256e80f0
iopl=0         nv up ei pl nz ac po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010214
00000047`d345dff0 002f            add     byte ptr [rdi],ch ds:000001f7`256e80f0=??
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)ExceptionAddress: 00000047d345dff0
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000008
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 00000047d345dff0
Attempt to execute non-executable address 00000047d345dff0

PROCESS_NAME:  OldWorld.exe

EXECUTE_ADDRESS: 47d345dff0

FAILED_INSTRUCTION_ADDRESS: 
+0
00000047`d345dff0 002f            add     byte ptr [rdi],ch

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:  00000047d345dff0

IP_ON_STACK: 
+0
00000047`d345dff0 002f            add     byte ptr [rdi],ch

FRAME_ONE_INVALID: 1

STACK_TEXT:  
00000047`d345dfb0 00000047`d345df80     : 00000000`00000000 00000000`00000003 000001f7`25884180 000001f7`256e80f0 : 0x00000047`d345dff0
00000047`d345dfb8 00000000`00000000     : 00000000`00000003 000001f7`25884180 000001f7`256e80f0 00000000`00000009 : 0x00000047`d345df80


SYMBOL_NAME:  OldWorld.exe!unknown_error_in_process

MODULE_NAME: OldWorld

IMAGE_NAME:  OldWorld.exe

STACK_COMMAND:  ~126s; .ecxr ; kb

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_c0000005_OldWorld.exe!unknown_error_in_process

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  2021.3.34.9831

FAILURE_ID_HASH:  {bea16f79-07c3-5018-267e-40083fb69151}

Followup:     MachineOwner

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 796

    Key  : Analysis.Elapsed.mSec
    Value: 796

    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: 140

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2350

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 207

    Key  : Failure.Bucket
    Value: INVALID_POINTER_READ_c0000005_nvwgf2umx.dll!Unknown

    Key  : Failure.Hash
    Value: {7b367f86-064a-2e05-5dc0-760739d560ad}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 56510

    Key  : Timeline.Process.Start.DeltaSec
    Value: 2872

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 1.8.17201.0


FILE_IN_CAB:  helldivers2.exe.22024.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)rax=00007ffdb9126020 rbx=00007ffdbbe53b48 rcx=00007ffdbbe53b48
rdx=0000000210397950 rsi=0000000000000000 rdi=4800e2b3bde8204f
rip=00007ffdb935e389 rsp=000000007f5fd5b0 rbp=0000000000000000
 r8=00000002103e2fa8  r9=0000000000000002 r10=00000001672b0000
r11=0000000000000000 r12=00000000ffffffff r13=0000000210397950
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvwgf2umx!NVENCODEAPI_Thunk+0x13dee9:
00007ffd`b935e389 f6473802        test    byte ptr [rdi+38h],2 ds:4800e2b3`bde82087=??
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)ExceptionAddress: 00007ffdb935e389 (nvwgf2umx!NVENCODEAPI_Thunk+0x000000000013dee9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

PROCESS_NAME:  helldivers2.exe

READ_ADDRESS:  ffffffffffffffff 

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:  ffffffffffffffff

STACK_TEXT:  
00000000`7f5fd5b0 00007ffd`b975f65f     : 00000000`00000000 00000002`103e2f18 00000000`00000000 00030202`f95fe800 : nvwgf2umx!NVENCODEAPI_Thunk+0x13dee9
00000000`7f5fd630 00007ffd`b92ede79     : 00000002`103e2f70 00000002`103e2f80 00000002`103e1d00 00000000`00000000 : nvwgf2umx!OpenAdapter10+0xf7fff
00000000`7f5fd6a0 00007ffd`b976381b     : 00000000`00000000 00000000`00000000 00000001`6cb0be10 00000000`00000000 : nvwgf2umx!NVENCODEAPI_Thunk+0xcd9d9
00000000`7f5fda00 00007ffd`b97327fc     : 00000002`10397950 00000002`9b16e520 00000000`00000010 00000003`84247530 : nvwgf2umx!OpenAdapter10+0xfc1bb
00000000`7f5fda30 00007ffd`b97f2039     : 00000003`84247530 00000001`603bd3f0 00000000`00000000 00000001`60470c40 : nvwgf2umx!OpenAdapter10+0xcb19c
00000000`7f5fda80 00007ffd`94abad37     : 00000002`a40009c0 00000003`84246ec0 00000003`32241ac0 00000000`00000000 : nvwgf2umx!OpenAdapter12+0x9009
00000000`7f5fdad0 00000001`4065cda9     : 00000002`44a129b0 00000001`604371b0 00000003`31aa3358 00000000`7f5fdc10 : D3D12Core!CGraphicsCommandList::SetPipelineState_VariadicHelper<void (__cdecl*)(ID3D12PipelineState * __ptr64),1,1,0,0>::Variadic_Thk+0x87
00000000`7f5fdb10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : helldivers2+0x65cda9


SYMBOL_NAME:  nvwgf2umx+13dee9

MODULE_NAME: nvwgf2umx

IMAGE_NAME:  nvwgf2umx.dll

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~14s; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_nvwgf2umx.dll!Unknown

BUCKET_ID_MODPRIVATE: 1

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  31.0.15.5152

FAILURE_ID_HASH:  {7b367f86-064a-2e05-5dc0-760739d560ad}

Followup:     MachineOwner

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 406

    Key  : Analysis.Elapsed.mSec
    Value: 736

    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: 140

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3112

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 251

    Key  : Failure.Bucket
    Value: INVALID_POINTER_WRITE_c0000005_nvgpucomp64.dll!Unknown

    Key  : Failure.Hash
    Value: {96e9e540-a005-8606-46d0-e0f084bedb9a}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 51314

    Key  : Timeline.Process.Start.DeltaSec
    Value: 6

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 0.14.1.29197


FILE_IN_CAB:  EscapeFromTarkov.exe.12792.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=ffffffff97ce97a0 rbx=0000008d0180ca10 rcx=0000000000000054
rdx=00000000000002ad rsi=0000019e97d48e10 rdi=0000000000000006
rip=00007ffdc254ec8b rsp=0000008d0180c9a0 rbp=0000000000000000
 r8=0000000000000001  r9=00000000000002ad r10=0000000000002000
r11=0000000000000002 r12=0000019e97d9dcb0 r13=0000000000000001
r14=0000019e97cdfb58 r15=0000019e9b53be60
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nvgpucomp64!destroyFinalizer+0xcff14b:
00007ffd`c254ec8b 89548304        mov     dword ptr [rbx+rax*4+4],edx ds:0000008b`60bb2894=????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffdc254ec8b (nvgpucomp64!destroyFinalizer+0x0000000000cff14b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000008b60bb2894
Attempt to write to address 0000008b60bb2894

PROCESS_NAME:  EscapeFromTarkov.exe

WRITE_ADDRESS:  0000008b60bb2894 

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:  0000000000000001

EXCEPTION_PARAMETER2:  0000008b60bb2894

STACK_TEXT:  
0000008d`0180c9a0 00007ffd`c2499aa4     : 0000019e`97ce97a0 0000019e`97cdf7c0 0000019e`97d9dc40 00000000`00000000 : nvgpucomp64!destroyFinalizer+0xcff14b
0000008d`0180ca10 00007ffd`c2493a07     : 0000019e`00000001 0000019e`00000002 0000019e`97d9dc40 0000019e`9b51ff88 : nvgpucomp64!destroyFinalizer+0xc49f64
0000008d`0180eb20 00007ffd`c23897b6     : 0000019e`97ce97a0 0000019e`97d9dd90 0000019e`97ce97a0 0000019e`97d9dd90 : nvgpucomp64!destroyFinalizer+0xc43ec7
0000008d`0180ee80 00007ffd`c2497b0d     : 0000019e`00000000 0000019e`00000010 0000019e`97ce97a0 0000019e`0000003e : nvgpucomp64!destroyFinalizer+0xb39c76
0000008d`0180efc0 00007ffd`c2379a50     : 00000000`50300000 00000000`0000006f 00000000`000000eb 00000000`000008f6 : nvgpucomp64!destroyFinalizer+0xc47fcd
0000008d`0180f010 00007ffd`c2379b37     : 00007ffd`c2f6d67c 0000008d`0180f1a0 0000008d`0180f210 00007ffd`c2c17c80 : nvgpucomp64!destroyFinalizer+0xb29f10
0000008d`0180f0a0 00007ffd`c21dc6c9     : 0000019e`97ccb3a0 0000019e`97ce4068 0000019e`97cdf7c0 00000000`0000ff98 : nvgpucomp64!destroyFinalizer+0xb29ff7
0000008d`0180f1d0 00007ffd`c21dc795     : 0000019e`0008001f 0000019e`97cdf7c0 0000019e`97cdf7c0 0000008d`0180f460 : nvgpucomp64!destroyFinalizer+0x98cb89
0000008d`0180f2b0 00007ffd`c1c68890     : 0000008d`0180f458 0000008d`0180f458 0000019e`9d40e5b0 0000019e`9d40e5b0 : nvgpucomp64!destroyFinalizer+0x98cc55
0000008d`0180f2e0 00007ffd`c1c692d5     : 0000019e`97cd4210 0000008d`0180f440 0000019e`97cd40b0 00000000`00000000 : nvgpucomp64!destroyFinalizer+0x418d50
0000008d`0180f340 00007ffd`c1c556a8     : 00000000`00000000 0000008d`0180f7c0 00000000`00000041 0000019e`96568738 : nvgpucomp64!destroyFinalizer+0x419795
0000008d`0180f660 00007ffd`c1c55840     : 00000000`00000000 00000000`00000000 00000000`00000000 0000019e`957038d0 : nvgpucomp64!destroyFinalizer+0x405b68
0000008d`0180f6a0 00007ffd`b9129191     : b1131387`433b8e29 0000019e`a4efde08 00000000`00000000 00007ffd`b9f5f902 : nvgpucomp64!destroyFinalizer+0x405d00
0000008d`0180f6d0 00007ffd`b9932a90     : 00000000`00000000 b1131387`433b8e29 00000000`00000000 dfa17adb`58f0c8a1 : nvwgf2umx+0x89191
0000008d`0180f740 00007ffd`b94a61c5     : 00000000`00000000 00000000`00000000 0000008d`0180f810 0000008d`0180f879 : nvwgf2umx!OpenAdapter12+0x149a60
0000008d`0180f7c0 00007ffd`b93b9897     : 0000019e`2748ed00 0000019e`a4efda80 0000019e`a4efda80 00007ffd`b947aa2e : nvwgf2umx!NVAPI_Thunk+0x1393f5
0000008d`0180f8c0 00007ffd`b935d389     : 0000019e`2748ed00 00000000`00000000 0000019e`a4efda80 00000000`00000000 : nvwgf2umx!NVAPI_Thunk+0x4cac7
0000008d`0180f960 00007ffd`b915b190     : 0000019e`9a5199a0 00000000`00000000 0000008d`0180fa90 00000000`00000000 : nvwgf2umx!NVENCODEAPI_Thunk+0x13cee9
0000008d`0180f990 00007ffd`b9990923     : 00000000`00000000 0000019e`9a5168b0 0000019e`274db440 00000000`00000000 : nvwgf2umx!NVAPI_DirectMethods+0x29a70
0000008d`0180fc70 00007ffd`b9990648     : 00000000`00000000 0000019e`274db440 00000000`00000000 0000019e`27601300 : nvwgf2umx!NVDEV_Thunk+0x3ac63
0000008d`0180fd80 00007ffd`b99be413     : 0000019e`96e64a90 00000000`fffffff0 0000019e`96cd6d60 00000000`00000000 : nvwgf2umx!NVDEV_Thunk+0x3a988
0000008d`0180fe30 00007ffd`b99be30f     : 00000000`00000000 0000019e`479b9970 00000000`00000000 00000000`00000000 : nvwgf2umx!NVDEV_Thunk+0x68753
0000008d`0180fe80 00007ffd`b9f6687e     : 0000019e`479b9970 00000000`00000000 00000000`00000000 00000000`00000000 : nvwgf2umx!NVDEV_Thunk+0x6864f
0000008d`0180feb0 00007ffd`d1a47344     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvwgf2umx!NVDEV_Thunk+0x610bbe
0000008d`0180fee0 00007ffd`d2a426b1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
0000008d`0180ff10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


SYMBOL_NAME:  nvgpucomp64+cff14b

MODULE_NAME: nvgpucomp64

IMAGE_NAME:  nvgpucomp64.dll

STACK_COMMAND:  ~86s; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_WRITE_c0000005_nvgpucomp64.dll!Unknown

BUCKET_ID_MODPRIVATE: 1

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  31.0.15.5152

FAILURE_ID_HASH:  {96e9e540-a005-8606-46d0-e0f084bedb9a}

Followup:     MachineOwner

vmovups · ‎03-19-2024

The Helldivers 2 crash dump indicates the CPU tried to write to 0xFFFFFFFFFFFFFFFF(garbage address) despite the instruction and register content making that impossible at a first glance, in the Old World crash the CPU jumped to the stack for some reason(you didn't get hacked and no normal code does this), the Tarkov crash could be a bug, difficult to say. If you want to upload crash dumps compressing them in a single .zip file could work?

From having compared the crash dumps to mine it somewhat matches what I had on my 14900K, you also had crashes when playing turn based games, i did too.(for me it was always when pressing a key that would advance the game by a turn.)

This is just my opinion but i'd recommend getting a replacement, see what Intel says if they respond but they may ask you to RMA the chip to them after getting it to crash in Intel's own stress test software.

Zanmorian · ‎03-20-2024

Thank you for your insight on those minidumps. I don't have the expertise to really decipher them myself.

From other logs that I looked at they vary a bit in what address it tries to write to, but it looks like it's all the same error pattern to me.

It looks like there are a lot of people by now that have problems with their 13th and 14th gen chips.

I'd like for Intel to respond and see what they have to say. But it looks like an RMA.

NormanS_Intel · ‎03-22-2024

Hi Zanmorian,

I appreciate your effort in detailing the troubleshooting steps you've undertaken. It's evident that you've invested considerable time and energy into resolving the issue, and I recognize that this can be quite taxing. I have sent a private email regarding this matter. Please take a moment to review it at your earliest convenience.

Thank you.

Best regards,

Norman S.

Intel Customer Support Engineer

onlyjuan · ‎03-22-2024

Hi! I'm having the exact same situation, also using a 13700k in my build. Started about a month ago and have tried every recommended or even vaguely mentioned solution in the forums. Have tried everything you have except swapping hardware. Games crash to desktop seemingly at random times, Event Viewer shows Faulting module name: nvwgf2umx.dll with Exception code: 0xc0000005.

Have tried everything you have except swapping hardware. Waiting on new RAM sticks, will try swapping GPU.

Specs:

i7-13700k

ROG Maximus Z790 Hero MoBo

RTX 4070Ti

Kingston 4800 DDR5

750W Corsair PSU

2TB Kingston NVME

I don't know where to go from here asides from trying the new RAM and testing out my old GPU. If you pinpoint the issue please do tell!

I've attached the most recent crash dump files since I just clean installed Windows for the 2nd time, I have no experience reading these files.

I'll try any suggestions!

Zanmorian · ‎03-23-2024

Hi Onlyjuan,

It really sucks, I know. And it can be very frustrating trying to figure this out.

By trying everything, did you also mean changing Vcore settings in the bios?

Looks like you have an Asus MB. Maybe this article can help you out.

https://www.radgametools.com/oodleintel.htm

onlyjuan · ‎03-25-2024

Apologies, I have not tried changing Vcore settings yet. Started troulbeshooting CPU after seeing your post. Did a little more research on CPU issues and found 13th gen has been having known issues. A solution posted several times, with some replies saying it worked, was disabling Turbo Boost on BIOS so I tried that first.

As of disabling Turbo Boost, I have only crashed once in about 6 hours of testing in 2 different games (I would normally crash seemingly randomly before the 30-40 min mark).

Will keep on testing with Turbo Boost off, if it maintains stability I guess the issue would most definetly lie in the CPU?

Have you tried turning Turbo Boost off?

NormanS_Intel · ‎03-25-2024

Hello Zanmorian,

I'm reaching out to inquire whether you've had an opportunity to look over the information I sent through email. Thank you for your attention to this matter.

Additionally, @onlyjuan, I notice you're encountering a similar issue. For more tailored and effective assistance, it would be beneficial to initiate a new thread. This way, we can engage in a direct and focused dialogue to address your concerns. Thank you for your cooperation.

Best regards,

Norman S.

Intel Customer Support Engineer