<<Crash>>Access violation (0xc0000005)

Repeated crashes with this error code. Did some digging. I have ruled out hardware issues with 6 days of different debuggers and reinstalling just about every driver I have.

Here’s some of the highlights from the console logs

Here’s the crash line <>Access violation (0xc0000005) in build 5e8c95198fe9360418e0fe53a08916a496fa0c5f
accessing address 000000000000FF8A from 00007FFCF31CFB93<>
<>
{00007ffd082f0000, 001f8000, b5ced1c6, ccc0e361-20f4-24be-044d-e630c3bd80c4, 00000001, ntdll.pdb}
{00007ffd070d0000, 000bf000, 73bb7c6b, 4379f432-e88d-e285-3ee4-e11356d45532, 00000001, kernel32.pdb}
{00007ffcf3010000, 0368a000, 63583522, 7eb4630d-7087-43fb-b317-36f64c30132f, 00000001, C:\dvs\p4\build\sw\rel\gpu_drv\r525\r526_25\drivers\wgf2um_out\wddm2_amd64_release\nvwgf2umx.pdb}
Interestingly I run Intel. Could someone tell me why is it calling amd libraries?

This line also repeats every few minutes or so. Could it be a symptom?
error: [Unit] Unit: ‘#ID[ac4edce5274f2d78]’ has still childs attached to it, please unlink them before destroying the unit
child 0: ‘#ID[60aacb675ed8aef1]’
Unit Id changes the child id doesn’t.

1 Like

Same thing happened again and caught the logs this time!
GUID: 84a47430-2b9e-41ab-aaf5-6a499490bf1b
Log File:
Info Type:


It appears to be calling AMD libraries because, as a TLDR, it relates to CPU architecture and instruction sets. The 64-bit version of the x86 instruction set was designed by AMD, called x86_64, or sometimes amd64.

This is most certainly driver-related. The last couple of updates from NVIDIA have been particularly problematic, so I can only recommend rolling back to an older version right now.

1 Like

Allright. Thank you for the info!! I’ll be sure to try this next!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.