Pc crashing after gaming

Associate
Joined
15 Feb 2024
Posts
2
Location
England
Hello,

Currently, I am experiencing that when I play intensive games, my PC just randomly shuts off after about half an hour of gameplay. Previously, I have been getting Nvidia OpenGL logs"
DrvSetContext failed functionality indeterminant" and were experiencing these logs for a while. I thought this was the cause of the shutdowns but I managed to fix it after doing a DDU on my GPU and CPU. I stopped getting any OpenGl logs after this. I have still tried to fix the issue surrounding the 'Nvlddmkm' issue though as a lot of people have similar issues. I have tried changing my PCIE gen, changing the Nvlddmkm permissions in the system 32 folder, turning off DOCP overclocking for my RAM, switching the RAM, reseating my GPU, changing the CMOS battery, doing a DDU uninstall, running a memtest but nothing. I am sure there are other fixes I have done but forgotten. What is strange is that my system does not shut off during any stress test, just during the more demanding games. Strangely I have also been getting VSS logs in event viewer:" Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.]" but these logs do not match up with the time the system shutdowns occur. I'm starting to think that this is now a hardware issue as I have tried everything I can. Any suggestions would be welcome though.

Specs:

Ryzen 7800X3D
RTX 4090
32Gb DDR5 ram 6000mhz
Asus TUF B650 Plus Wifi
Corsair 1000W PSU
 
Does your system get abit toasty? Try playing with with the case door off and play, see if the system behaves differently? Maybe some transient power spike?
 
Hello,

Currently, I am experiencing that when I play intensive games, my PC just randomly shuts off after about half an hour of gameplay. Previously, I have been getting Nvidia OpenGL logs"
DrvSetContext failed functionality indeterminant" and were experiencing these logs for a while. I thought this was the cause of the shutdowns but I managed to fix it after doing a DDU on my GPU and CPU. I stopped getting any OpenGl logs after this. I have still tried to fix the issue surrounding the 'Nvlddmkm' issue though as a lot of people have similar issues. I have tried changing my PCIE gen, changing the Nvlddmkm permissions in the system 32 folder, turning off DOCP overclocking for my RAM, switching the RAM, reseating my GPU, changing the CMOS battery, doing a DDU uninstall, running a memtest but nothing. I am sure there are other fixes I have done but forgotten. What is strange is that my system does not shut off during any stress test, just during the more demanding games. Strangely I have also been getting VSS logs in event viewer:" Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.]" but these logs do not match up with the time the system shutdowns occur. I'm starting to think that this is now a hardware issue as I have tried everything I can. Any suggestions would be welcome though.

Specs:

Ryzen 7800X3D
RTX 4090
32Gb DDR5 ram 6000mhz
Asus TUF B650 Plus Wifi
Corsair 1000W PSU

When you say youve been doing stress tests, which ones ? which game ?, does it use AVX instructions.

I recently sent back a CPU because even at stock it wouldnt pass Core Cycler SSE Huge on the 3D cores within about 15 mins, so I didnt have to run it for long to find out, and would crash the system with Prime on Large FFTs AVX2, I know it wasnt my ram as that was tested, the system previously passed everything I threw at it with my last CPU, so the only thing it could have been was the CPU.
 
Last edited:
My cpu temps can get a bit hot but I think it’s within operable ranges. I’ll try but not so sure it’ll work.

sometimes when diagnosing an issue I try to look for changes in behaviour when a easy change can be made, to rule things out. For instance if it goes from 30mins to 2hrs before crashing it may be a airflow/thermal issue etc or nothing changes then you move on to something else.
 
Back
Top Bottom