Games crashing back to desktop (no BSOD) frequently and randomly

Hey all. I could really use some help here, I'm on the verge of giving up and selling my PC for parts probably. In 2022 I built a PC, only my second build, and I just continue to have crashing issues. I posted on this before but kind of gave up on it... here is that thread if interested (https://www.bleepingcomputer.com/forums/t/767979/games-crashing-back-to-desktop-randomly/?view=getnewpost). I copied and pasted some of the below from there.

So my PC can be running fine, and I can be playing games for 4 hours plus no issue, then all of a sudden my games will start crashing to the desktop. So no BSOD, just crashing to the desktop. I keep restarting my PC, and eventually it will start working again, but usually when this happens my games will crash 4 or 5 times, usually about a minute in to start up. Sometimes no matter how many times I try I can't get past a minute in. Then sometimes I get further into games and get yet another random crash to the desktop, then it just keeps happening. It does, on occasion, do a full crash and shut off the computer and it restarts, but much more frequently it crashed to desktop.

It's becoming much more frequent now and is super frustrating to have spent all this time and money to just get aggravated trying to play a game. I dont know if it's a GPU issue, I thought it was RAM but that doesnt seem to be the case, im just a bit lost on what to do. So I would really appreciate any and all advice. I am not super technical, but know an ok amount I guess just as background.

I attached the sysnative file, and here is the link to my speccy.... speccy.piriform.com/results/wf6IcTDfr4oFCVbgWsPBLhQ . I also attached a JPG of the what the windows crash files look like along with a PDF of the who crashed report.

In case any more info is needed I provided more background below. Really appreciate any guidance on this one!!

Here is what I have tried so far

• Buying and installing new RAM from the QVL.

• Ran the windows memory diagnostic app to see if it picked up anything (came back clean)

• Doing a clean driver install through NVIDIA

• Used driver fix to make sure all my drivers are up to date

• I still monitor my temps with AIDA extreme, it's not due to heat

PC components (speccy link http://speccy.piriform.com/results/PzwGYMRc4m1WubtkfVwLwlT )

• AMD Ryzen 7 5800x

• Nvidia Geforce RTX 3060 TI - Asus

• ASRock B550 Phantom Gaming-ITX/ax Mini ITX AM4 Motherboard

• OLOy Blade RGB 32GB (2 x 16GB) 288-Pin DDR4 SDRAM DDR4 3600 - Am now using TEAMGROUP T-Force Delta RGB DDR4 32GB (2x16GB) 3600MHz (PC4-28800) CL18 Desktop Gaming Memory Module Ram Black - TF3D432G3600HC18JDC01

• MSI SPATIUM Series M.2 2280 1TB PCI-Express 4.0 x4, NVMe 1.3 3D NAND Internal Solid State Drive (SSD) M470

• NZXT H1 case with included PSU (650w)

Hi, Welcome Back.

Please only post attachments that are asked for. Thanks.

Do not know (yet) if mentioned this but should ask questions instead of just buying stuff.   Again the wrong Ram is installed.

Max  Ram Speed for the  AMD Ryzen 7 5800x : Up to 3200MT/s as per Chip Spec Page.

https://www.amd.com/en/products/cpu/amd-ryzen-7-5800x

Does not matter what is on the QVL, you match the Ram Speed to the Chip then you look for that speed on the QVL.

Would also be looking for possibly a little slower if there is as once use XMP you're above specs.

So : TEAMGROUP-UD4-3600 is again to fast for the Chip and you can not use XMP ever.   Note : by running the wrong speed Ram you can cause damage to the Chip and void a warranty that is now over.

Note : Once you have a particular issue with Ram you will always have issues.  It is the Beast within that now decides what it will do.

So your ram should be set in BIOS on your M/B  as per your Manual to below 3200 so that you can use XMP (equivalent as now interchangeable)

As well set the ram Timings and lock it in somewhere in SPD. 

I do not read manuals but you should.        

So now I have spelled this out clearly you may want to carry this knowledge into the future for every CHIP you buy look up the Specs so can find Max Ram Speed.

Note : Reviews of Chips are great but you may not want to buy the chip if max ram speed is 1600 or 2333 or. 

You are not alone in not knowing this stuff.

Will look at stuff later but The BSOD Kernal Expert will look late this date or early next and will say same thing am sure.

Who Crashed does not come close to the Program and Knowledge that is used to figure out a Crash Dump.

Lock the Ram speed in.  Somewhere in your BIOS to below 3200 or @ 3200. 

Enter the Ram Timings  22-22-22-52  to get better stability and performance.

Edited by Pkshadow, 28 March 2024 - 04:12 PM.

Do not allow Microsoft Update to Update your Video Card Drivers ever.  

https://www.tenforums.com/tutorials/146562-prevent-windows-update-updating-specific-device-driver.html

&

https://www.windowscentral.com/how-roll-back-device-driver-windows-10 /11

Use the Makers Drivers. As well use M/B Drivers.

If you have done a Clean Install of Windows disconnect from the internet, then install your already Downloaded Chipset Driver then SATA Driver followed by the lesser drivers.  Reboots after each.

They tell Device Manager who and what they are.

So in DxDiagx86 it shows (under the Heading : Diagnostics as to what is crashing) this does not mean they are the cause of the crash.

So : Fault bucket LKD_0x141_Tdr:C_AppFault_IMAGE_nvlddmkm.sys_Ampere, type 0

&

Fault bucket 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_nvlddmkm!LDDM_SubmitCommand, type 0

Shows that the Video Card is Crashing.

Download your Newest Driver for your Card from here : https://www.techspot.com/downloads/drivers/essentials/nvidia-geforce/

Run DDU as per instructions : https://www.guru3d.com/download/display-driver-uninstaller-download/ then install the drivers with internet connect OFF so that MS does not install a driver. Never take MS Driver.

Will look further.

Edited by Pkshadow, 28 March 2024 - 04:19 PM.

The Microsoft Store is a Integral Part of Updating Windows 11.

Open the Store and go down the Left side to Library and install only what you use.

Anything that is gaming related in there, game bar, Xbox if use it all etc notepad, powershell (should uninstall old version so there is not 2 on the system) Version: 5.1.22000.1 as current version is 7.

Edited by Pkshadow, 28 March 2024 - 04:18 PM.

Usual suspects for random crashing: first, RAM is suspect. Run Memtest on each stick one at a time.

If all prove good, check that RAM is ok for your board and CPU (per PKshadow's advice above).

Always check CPU and box temps; if you ONLY crash in games, then stress is suspect: overheating of CPU or GPU is common. I'm sure you know about cleaning dust in the CPU heatsink and boxl, etc.

Dump 6875 : VIDEO_SCHEDULER_INTERNAL_ERROR (119)  So with any luck this should be fixed with drivers.  Note : it could also be hardware.

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE    This on the other hand will not be.  Test Ram as per above.  

Run test on 1 stick of ram at a time. Do the max 4 passes with free version then repeat another 4 passes on same stick.

Then test the other stick.  Report back as to passed or failed.

Note : continued crashing with out fixing the issue will corrupt ram.       You fix things as it happens and you do not wait.

Will have @ubuysa BSOD Kernel Expert  determine what is going on as is the Expert.

Edited by Pkshadow, 28 March 2024 - 04:34 PM.

Lock the Ram speed in.  Somewhere in your BIOS to below 3200 or @ 3200. 

 

Enter the Ram Timings  22-22-22-52  to get better stability and performance.

Thank you much for taking the time, really appreciate you walking me through this. I just tried updating these settings, unfortunately it crashed during the first game I tried playing but will keep trying it out. I also see you have me other prescriptions to walk through so i will be trying all of that tonight or tomorrow and will report back. Thank you again.

If possible do asap as should be done before midnight Pacific Time so you have the info in there for the BSOD Expert to review.

Welcome.

The graphic card is defective or the card's settings are wrong.

Just a guess.

Sorry I couldnt get through all the steps tonight... but I did do as suggested and prevented windows from updating or installing drivers. Did the clean windows 11 install, did the driver installs, adjusted the RAM in the bios to under 3200 and set the RAM timings to 22-22-22-52. I haven't tested a game yet but I will tomorrow. 

I will then to the memtest on the RAM sticks and report back. I downloaded it and have it on a USB ready to go.

Ya well Doing a fresh install may work out for you with the ram down graded.

Did not say to stop Windows from Updating Windows.  Just not the drivers as your Support Page has what you need as well NVIDIA has the Drivers for the GPU.

Chipset needs to always be installed.  Even when ancient so the right info is in there.  Would always make sure you have your drivers for a emergency issue.

Note : have 1 more year or so left of updates from Asrock.

Ok, do not need to do anything but test the ram if you have issues.

If it has a BSOD upload the dump files.

Edited by Pkshadow, 28 March 2024 - 11:49 PM.

From the dumps, which are all very similar, this looks most likely to be a RAM problem. The key to that diagnosis are chkimg failures in every dump, four for dxgkrnl.sys (a DirectX kernel driver) and one for pci.sys (the root PCI driver). All four dumps failing dxgkrnl.sys have identical chkimg failures, here's one as an example...

CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgkrnl
    fffff80224cb3c15-fffff80224cb3c18  4 bytes - dxgkrnl!DxgNotifyDpcCB+95
    [ 77 70 06 00:67 2b 8a 6d ]
    fffff80224cb5b3a-fffff80224cb5b3d  4 bytes - dxgkrnl!DxgNotifyInterruptCB+aa (+0x1f25)
    [ 52 51 06 00:42 0c 8a 6d ]
    fffff80224cba508-fffff80224cba50b  4 bytes - dxgkrnl!CCompositionFrameCollection::AddCompositionFrame+38 (+0x49ce)
    [ 84 07 06 00:74 c2 89 6d ]
    fffff80224cc9362-fffff80224cc9365  4 bytes - dxgkrnl!DpReadDeviceSpace+92 (+0xee5a)
    [ 2a 19 05 00:1a d4 88 6d ]
    fffff80224cd3f92-fffff80224cd3f95  4 bytes - dxgkrnl!DpWriteDeviceSpace+92 (+0xac30)
    [ fa 6c 04 00:ea 27 88 6d ]
    fffff80225046e3c-fffff80225046e3f  4 bytes - dxgkrnl!DxgDestroyContextAllocationCB+ac
    [ 50 3e cd ff:40 f9 50 6d ]
    fffff8022505b7ee - dxgkrnl!DpGetDeviceInformation+ae (+0x149b2)
    [ f8:fc ]
25 errors : !dxgkrnl (fffff80224cb3c15-fffff8022505b7ee)

The chkimg feature compares the in-memory copy of a module with a known good copy from the Microsoft libraries, if there are any differences you see this error. In almost every case the cause is bad RAM, so that's where I suggest you start - as already suggested.

No memory testing software can prove that your RAM is good and since you have two 16GB RAM sticks I would suggest that you remove one stick and run on just one for a day or several. Then swap RAM sticks. You'll soon see whether it's stable on one but not on the other.

Edited by ubuysa, 29 March 2024 - 05:33 AM.