Repeated system crashes
Repeated system crashes
NightmanGX
01-22-2023, 09:11 AM #1Hey there, I'm feeling really puzzled. Whenever I attempt to play Counter-Strike 2, my machine freezes with a Blue Screen of Death. I've attached the dump screenshots. It keeps happening, with errors scattered everywhere: "PAGE ERRORS," "System Service Exceptions," and the most frequent is "KMODE EXCEPTION NOT HANDLED." The twist? Other games work fine, so it looks like a CS2-specific issue. I've tried everything I can think of—reinstalled the verified game cache, updated drivers (including a clean DDU install for Nvidia), ran the SFC tool, replaced RAM twice, adjusted page file settings, reset BIOS, and even swapped out all motherboard parts. Just to be sure, this only occurs in CS2. I've listed my system details (Windows 11, Asus B550, Ryzen 5800x, 32GB RAM, RTX 4060ti GPU, etc.) for reference. Anyone else experienced these BSODs in CS2? Any suggestions could really help! Thanks a lot!
Here are the dumps: DUMPS: https://files.catbox.moe/n6eknl.dmp https://files.catbox.moe/kn2cpt.dmp https://files.catbox.moe/5yhaia.dmp https://files.catbox.moe/k0dylo.dmp https://files.catbox.moe/upzabs.dmp LOOKING FOR THE SOLUTION? I may have found the solution already. Although maybe not quite: I'm still testing. I was reinstalling everything including iCUE to manage the RGB lighting and noticed that I cannot change the lighting on my motherboard with iCUE. So I Googled and found Asus Amore Crate to Control the RGB Lighting. I always taught it was bloatware so I never looked at it And the moment it was installed it prompted.me to update like 3 drivers for Bluetooth and THE ASUS CHIPSET DRIVER FROM 4.0 SOMETHING to 5.03 - The change log I found included some fixes for bluescreens!!! The bad news is: It doesn't name the Bluescreens there that Im experiencing! Still updated it of course and it seems to at least help with the problem somehow. So I ran CS2 now for some time and no Bluescreens happend so far for like 1 hour. The ridiculous part about this: Asus doesn't seem to make.this CHIPSET DRIVER available on their website to download. They only seem to offer it through their shit ass software. I'm still testing. Maybe I had a lucky gaming session so far or the problem was fixed in the most random style possible. Ending my suffering. If another blue screen appears I'm going to write ✍ again..if I don't: It may have fixed it.
Done Both. XMP (or in ASUS's case "DOCP") is off! Temperatures are fine. Here is a video of my BIOS settings: (THE RAM SPEED IS FALSE I KNOW. This video was recorded BEFORE the RAM was changed. Otherwise it remained the same Here are the dumps: DUMPS: https://files.catbox.moe/n6eknl.dmp https://files.catbox.moe/kn2cpt.dmp https://files.catbox.moe/5yhaia.dmp https://files.catbox.moe/k0dylo.dmp https://files.catbox.moe/upzabs.dmp LOOKING FOR THE SOLUTION? I may have found the solution already. Although maybe not quite: I'm still testing. I was reinstalling everything including iCUE to manage the RGB lighting and noticed that I cannot change the lighting on my motherboard with iCUE. So I Googled and found Asus Amore Crate to Control the RGB Lighting. I always taught it was bloatware so I never looked at it And the moment it was installed it prompted.me to update like 3 drivers for Bluetooth and THE ASUS CHIPSET DRIVER FROM 4.0 SOMETHING to 5.03 - The change log I found included some fixes for bluescreens!!! The bad news is: It doesn't name the Bluescreens there that Im experiencing! Still updated it of course and it seems to at least help with the problem somehow. So I ran CS2 now for some time and no Bluescreens happend so far for like 1 hour. The ridiculous part about this: Asus doesn't seem to make.this CHIPSET DRIVER available on their website to download. They only seem to offer it through their shit ass software. I'm still testing. Maybe I had a lucky gaming session so far or the problem was fixed in the most random style possible. Ending my suffering. If another blue screen appears I'm going to write ✍ again..if I don't: It may have fixed it.