Cyberpunk 2077 Freeze and crash with xid 69 error after moving ingame with gtx 1070ti. is it a hardware problem?

i have a zotac gtx 1070ti and an intel i7-8700k with an ASUS ROG STRIX Z390-F GAMING motherboard.

this only happens in cyberpunk. i can start a corpo save but after moving a bit it crashes and a streetkid save freezes immediatly. the game also crashes at the intro when fsr is on with the same error. when i disable glcache i can move around for a few more seconds.

things i tried:
i ran memtest for a night and got zero errors after 6 passes.(not sure if its enough)
i changed my ram configs to motherboard auto and default xmp.
i reseated both ram and gpu into other slots.
i tried 535*, 545* and vulkan beta drivers.

if this isn’t a problem with the drivers what would be the best way to test for hardware problems?
log:
nvidia-bug-report.log.gz (568.8 KB)

UPDATE: i used a vm and it didn’t crash. so it has to be a driver error. (or maybe a misconfigured system? im not too sure)
what should i do?

Unfortunately, Xid 69 is rather unspecific, can be really everything from hardware to software. Only thing I noticed is on every boot, kcminit crashes in the nvidia driver compiling shaders. A bit puzzling, what does kcminit start graphics related? Please check, maybe this leaves the gpu in a dirty state having influence on cyberpunk.

the only soution i could find for it was to downgrade glibc and lib32-glibc to 2.38-3 which fixed the error in kcminit but i still crash in cyberpunk with the same error.

new log:
nvidia-bug-report.log.gz (559.1 KB)

So that was a red herring. How did you set up the VM where it worked, gpu passthrough to Windows VM on KVM?

i used single gpu passthrough from this guide:
(Home · Wiki · Risingprism / Single GPU Passthrough · GitLab)
because i didnt want to dualboot windows to see if the problem was my hardwear. i use qemu kvm.

i made a new vm with a fresh install of endeavouros and i got the same error so at least it’s consistant.

there has been no reply here for a while. is there anything i can do, anyone i can contact? or is this unfixable?

Difficult, since you seem to be the only one with that specific error in that game. To have someone at nvidia look at it, it must be reproducable. Also Xid 69 is an internal gpu error which doesn’t make things easier. Usually, I’d say the gpu is breaking but OTOH, this doesn’t reproduce on Windows or in general Linux usage.
Is this only occuring in Cyberpunk or are also other games/applications affected? To check the gpu for subtile errors, you might want to run gpu-burn for 10 minutes.

yes it’s only in cyberpunk. and i ran gpu-burn for 10 minutes and there was no error. should i run it for longer?

I don’t think doing a longer gpu-burn run will change the results. You could rather use cuda-gpumemtest to check for video memory defects though I also don’t think that will yield anything, would rather result in Xids 8,13,31.
Maybe try setting “Prefer Maximum Performance” in nvidia-settings to check if performance level switching has some influence.

that setting has always been on maximum performance. i have also tried seting the option to adaptive and downclocking using nvidia-smi to change power usage and it doesn’t work.
(i also ran gpu-burn for an hour and you were right it didn’t change the result)

I’ve been checking protondb and there are only few reports for Pascal based gpus. There might be an issue for those combined with proton-8, switching to proton-7 fixed that, though. What are you using to run CP2077?

i use lutris. i tried proton 7, 8, experimental, wine-ge, wine staging, wine tgk and none of them work

Since it runs for some seconds longer when glcache is disabled, I guess shader compilation defers it. Already tried running with lowest settings, all extras disabled?

yes. and what makes it crash faster is turning on fsr.

Checking with VK3D, FSR in CP2077 seems to be a general issue, unrelated to gpu vendor. So not really helping.

the problem was with vkd3d.
after tweaking the game a bit more it turned out that with vkd3d v2.6 the game runs without crashing. i’m going to report this problem to the vkd3d github. thanks for helping generix :).

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