This error code indicates a blue screen or crash related to constant issues.
This error code indicates a blue screen or crash related to constant issues.
System:
MSI MAG Z790 Tomahawk WIFI DDR4
Core i9 13900K, custom watercooled, not overclocked
2 x 3600 DDR 4 32GB RAM
MSI RTX 4090 Suprim, added to the watercooling loop
BeQuiet Dark Pro 12 1500W
Latest Ghost Spectre Windows 11 build, all latest drivers.
watercooling loop: 280 x 25mm RAD, 360 x 30mm RAD, 2 pumps, AlphaCool CPU block, Byski GPU block
Computer started acting wonky last week, getting worse as time went on, the dreaded c0000005 error. Tested the RAM with MEMTest86 (USB boot version), and tested fine. Decided to reformat. Got the latest Spectre build, went to MSI and got the "latest" BIOS. Flashed the BIOS and tried to install Windows. Kept crashing, but after a few attempts I got it to work. Went back to gaming and seemed okay for a while, then crashed again last night. Kept getting c0000005 errors showing up in the Event Viewer. Tested the RAM again and again, tested fine. I tried running the Windows RAM tester, but I was not by the computer when it restarted and the log was not listed in the Event Viewer when I did get Windows open again.
I decided to roll back the BIOS because the older one was at least more stable than the new one. MSI had changed the BIOS and ME flash tool that they had posted (7D91v1A and ME_16.1.30.2264 were downloaded on the first, and now taken down. 7D91v1B and ME_16.1.30.2330 are now in it's place. And, yes, I did download the right ones the first time). Before and after flashing the BIOS and updated the ME, I've been trying to run Cinebench for checking stability. Single core seems to work, but if I try multicore, it crashes and directs me to the bug report (since it's downloaded from the M$ store, it's not where it states. Luckily I found a thread online that tells where to find it.
There's no report in the Event Viewer, but I was able to open up the dmp file with WinDbg. I don't know what most of it means, but I do see the c0000005 error showing up again. I know that's usually RAM, which is why I have been testing it over and over, but it keeps coming up fine.
EDIT: I had a side note saying my temps were bad. I worked to see if there was any air stuck in the system and repasted the CPU block. Temps are under control, but Cinebench is still crashing with the same error.
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 499
Key : Analysis.Elapsed.mSec
Value: 1483
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 2
Key : Analysis.IO.Write.Mb
Value: 3
Key : Analysis.Init.CPU.mSec
Value: 139
Key : Analysis.Init.Elapsed.mSec
Value: 23993
Key : Analysis.Memory.CommitPeak.Mb
Value: 433
Key : Failure.Bucket
Value: INVALID_POINTER_READ_c0000005_c4dplugin.xdl64!Unknown
Key : Failure.Hash
Value: {be3d2427-eba4-4fed-89a5-f274a3051014}
Key : Timeline.OS.Boot.DeltaSec
Value: 476
Key : Timeline.Process.Start.DeltaSec
Value: 427
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
Key : WER.Process.Version
Value: 23.2.0.0
FILE_IN_CAB: minidump.dmp
CONTEXT: (.ecxr)
rax=3fe4ac5317840b16 rbx=0000000000000000 rcx=3fe9f43eff838bc9
rdx=3fd44df2ac26d0f3 rsi=0000000fb301d830 rdi=3fe4ac5317840b16
rip=00007ffd11757101 rsp=0000000fb301cda0 rbp=bff0000000000000
r8=3ff0000000000000 r9=3ff0000000000000 r10=3ff0000000000000
r11=00000000000000a3 r12=3fe4ac5317840b16 r13=3fe4ac5317840b16
r14=0000000000003480 r15=0000000fb301d830
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
c4dplugin+0x9f7101:
00007ffd`11757101 4d890424 mov qword ptr [r12],r8 ds:3fe4ac53`17840b16=????????????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffd11757101 (c4dplugin+0x00000000009f7101)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
PROCESS_NAME: Cinebench.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:
0000000f`b301cda0 00007ffc`fc856c06 : 00000000`00000000 3f745bb9`50f71480 3ff00000`00000000 00000000`00000000 : c4dplugin+0x9f7101
0000000f`b301ce60 00007ffc`fc85438f : 80000000`00000000 00000000`00000000 0000000f`b301cfc0 0000000f`b301cff0 : sla+0xc6c06
0000000f`b301cf30 00007ffc`fc7fb1ec : 3ff00000`00000000 00000000`00000000 406382cd`76a6bfe1 00000000`00000000 : sla+0xc438f
0000000f`b301d030 00007ffd`11757840 : 00000000`00000000 00000000`00000000 00000000`00000000 3ff00000`00000000 : sla+0x6b1ec
0000000f`b301d1f0 00007ffd`1123f244 : c047648d`00000000 40512e2c`ea6798cc 3ff00000`00000000 3ff00000`00000000 : c4dplugin+0x9f7840
0000000f`b301d370 00007ffd`118b8120 : 42ed9d01`42ed9d01 42ed9d01`42ed9d01 42ed9d01`42ed9d01 42ed9d01`42ed9d01 : c4dplugin+0x4df244
0000000f`b301da80 00007ffd`118d62fa : 3f293a96`3a161d0e 00000000`00000000 4001a9f6`e1aef085 00000000`00000000 : c4dplugin+0xb58120
0000000f`b301dee0 00007ffd`119be95f : 00000000`00000000 3fe11bc5`40000000 3fa75b97`80000000 00000000`00000000 : c4dplugin+0xb762fa
0000000f`b301e410 00007ffd`119c63e1 : 3f847ae1`47ae1485 bfbc28f5`c28f5c31 3ff35c28`f5c28f5d 00000000`00000000 : c4dplugin+0xc5e95f
0000000f`b301ea50 00007ffd`118d8427 : 00000000`00000000 00000000`00000000 00000000`00000000 3fc1eec7`035dca0f : c4dplugin+0xc663e1
0000000f`b301ec50 00007ffd`118dc7fa : 3ff00000`00000000 00000157`467c9728 00000000`00000000 00000000`00000000 : c4dplugin+0xb78427
0000000f`b301f180 00007ffd`118d34db : bfc486f3`e6bf7804 bfd36352`a912a65e 3ff00000`00000000 c075f0b6`084c0e1e : c4dplugin+0xb7c7fa
0000000f`b301f4b0 00007ffd`118d300c : 406160bf`ffda391c 4025ee76`c2b06073 c075f0b6`084c0e1e 406160bf`ffda391c : c4dplugin+0xb734db
0000000f`b301f650 00007ffd`118d1b8e : 00000010`00000000 00000157`00000000 00000157`4edb3900 00000000`00000000 : c4dplugin+0xb7300c
0000000f`b301f7f0 00007ffd`118cd87a : 00000157`00000000 00000000`00000010 00000157`25ffda38 00000157`25ff1108 : c4dplugin+0xb71b8e
0000000f`b301fa20 00007ffd`118692bc : 00000000`00000000 00000000`ffffffff 00000157`6e3020c0 00000000`00000000 : c4dplugin+0xb6d87a
0000000f`b301fbf0 00007ff7`32775740 : 00000000`00000000 00000000`00000000 00000000`000002ff 00000157`25ff1940 : c4dplugin+0xb092bc
0000000f`b301fc20 00007ff7`3277534c : 00000157`25ff1000 ffffffff`fffffffe 00000000`00000680 00000000`00001f80 : Cinebench_exe!MaxonDebugDumpThreadProfile+0x58bd40
0000000f`b301fca0 00007ff7`3277ddb3 : 00000157`7d9d3080 ffffffff`fffffffe 00000000`00000000 00007ffd`4958372b : Cinebench_exe!MaxonDebugDumpThreadProfile+0x58b94c
0000000f`b301fd20 00007ffd`49ab1503 : 00000157`6fe822d0 00000000`00000000 00000000`00000000 00000000`00000000 : Cinebench_exe!MaxonDebugDumpThreadProfile+0x5943b3
0000000f`b301fda0 00007ffd`4a31257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<void (__cdecl*)(void *),0>+0x93
0000000f`b301fdd0 00007ffd`4c0caa58 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1d
0000000f`b301fe00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28
SYMBOL_NAME: c4dplugin+9f7101
MODULE_NAME: c4dplugin
IMAGE_NAME: c4dplugin.xdl64
STACK_COMMAND: ~57s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_c4dplugin.xdl64!Unknown
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {be3d2427-eba4-4fed-89a5-f274a3051014}
Followup: MachineOwner
---------
verify the cpu socket on the motherboard for bent pins
examine the HSRD drives for any errors
tell me how you installed Windows, specifically using the latest version of the media creation tool from Microsoft?
has the system been overclocked? is XMP enabled?
Some answers were already provided. There was no need for overclocking, XMP RAM, or extensive testing of the RAM, and it's currently running Ghost Spectre Windows 11. I've been attempting to test the m.2 drive, but it consistently failed on that system. When I connected it to my son's computer this morning, the first attempt failed immediately, though the second succeeded. Check Disk passed, but the process was very quick, suggesting a short test rather than a thorough one. I'm planning to search for a tool capable of conducting a longer evaluation.
If the M.2 failed on two systems, perhaps it’s that issue. How did you verify it? Using which tool? Checking with the manufacturer’s software. Sorry, I wasn’t sure what Spectre was until now. Consider installing Windows 11 via the original media creation utility from Microsoft. Disable XMP to see if it runs at 3200MHz during testing.
It's a WD Black SN850 1TB. My gaming setup was experiencing frequent crashes, so that wasn't surprising. I attempted to use WD Dashboard, but it kept failing on my gaming rig. I also tried running the SMART long test in the BIOS, which also failed.
I tested it on my son's system. The SMART test in the BIOS failed immediately, but after a retry it worked correctly. I accessed Windows through his account and ran the Windows error checking tool from the properties menu, which also confirmed everything was fine. After downloading WD Dashboard, it functioned properly.
During these tests, I removed the CPU and inspected all the pins, thinking something might be wrong since I hadn't handled that in months. Everything on the CPU and socket appeared normal.
I restored the BIOS to its previous version. When I booted into Windows and tried installing the GPU drivers, it started the process but stopped early. After reformatting the drive again, everything installed correctly, including the GPU drivers. However, when I ran Cinebench, it crashed immediately once more.
Turning off XMP settings suggests the RAM was at 2133, according to JEDEC standards. I plan to test it with that setting, but I'm not convinced it's the issue—whether it's the RAM or the M.2 slot.
Yep. It simply crashed when using the RAM at 2133.
Do you have additional DDR4 memory on hand? It would be a good idea to consider it, especially since you haven't mentioned testing it from other devices in this one. Also, could you clarify what the 'Latest Ghost Spectre Windows 11 build' refers to?
Ghost Spectre is a simplified version of Windows 11. It removes all unnecessary features, tracking data, and prevents updates. Tom has written an article about it some time ago, together with Tiny11.
I planned to test my son's RAM. It's included in a quad setup; I have two units, he has two. However, I'm not sure if it's the RAM itself. I've set it up to 4000 Gear 1, which I kept for months, and it still works fine. Additionally, I increased the CPU core voltage to 1.4V and ran Cenebench. Even though it was running, it stopped responding. I'm considering going back to the BIOS settings but have already tested the RAM extensively—it's definitely not the issue. I was expecting it to be a m.2 module because that would be a simple fix. Now it seems to be affecting the CPU or motherboard.
Update: I re-flashed the BIOS to the older version. Keeping the RAM at 4000, Cenebench crashed again. Adjusting the CPU voltage by +0.150V resolved the issue. It still shows thermal throttling but doesn't crash. It continues to leave a problem with either the CPU or motherboard. I'm going to go to sleep now.
started recently without testing much.
with auto mode enabled, temperatures stayed near 75°C during heavy use, but the system would shut down. The RTX 4090 hit around 55°C, with a hotspot at 65°C.
after adding +150V, it reached 100°C fast and throttled off. GPU wasn’t under stress.
added: Tested with +0.05V – it held for about 5 minutes before failure. Peak reached 100°C without throttling. Running now at +0.04V.
just completed testing at +0.04V. Reached 100°C on a few cores, but no throttling. Under load, those cores run at roughly 5.4GHz.
So, this issue still keeps me frustrated, and I'm stuck on finding a solution.
I'm just going through the details, a bit faster now. Would a GPU ever trigger an error code like c0000005? Or is that always related to RAM or the system? The CPU seems to be the problem (more info below), but I'm dealing with other issues and wondering if I should send in returns for the CPU or the motherboard.
I've tried swapping the RAM, and it's still the same. I've tested the RAM multiple times without any problems. Now I've replaced the CPU; I bought a 12700K to use while I handle the RMA of the 13900K, but it seems to have its own issues. I'm having trouble getting Intel's third-party support to resolve anything.
I ran OCCT and all tests—CPU, RAM, GPU, VRAM—everything passed (especially with the new 12700K).
To give you an example, I played Elden Ring at 11,520x2160 (using a NVidia Surround and an EyeFinity RX7900XTX). The game would freeze roughly every minute. It wasn't smooth at first, but it got worse over time. I attributed it to the CPU since I was also dealing with problems with the 13900K, and the 13900K failed Intel's own diagnostics. But it still works with the new 12700K. I haven't run any RAM tests or attempted a system crash since my last post a few weeks back. I've been trying to get Intel to process the RMA, but it's been really stressful for my mental health.
I moved on to Immortals: Fenyx Rising and I'm fine with that. From a graphics standpoint, it has a high polygon count, but not high-resolution textures, so it's putting more strain on the GPU rather than the VRAM. All benchmarks are normal.
While I was writing this, my system would occasionally pause—especially when I was downloading Far Cry 6 for testing.