Sunde Oct 6, 2024 @ 9:35pm
intel pc constant crashing in CS2
Constant crashing please help -- intel pc
Hi there, for the past month my game has been relentlessly crashing. Time frame varies , I may get through 1 match or 2 and it can be as short as a few rounds.

Although Ive had different errors one constant is this error
INVALID_POINTER_READ_c0000005_scenesystem.dll!Unknown
found in the dumps folder.

Specs:
i9 13900 KS
RTX 4090
64GB Corsair dominator ram
asus rog maximus Z90APEX
Samsung 980 PRO 2TB
Windows 11 pro
all watercooled

So far:
verified game integrity
reinstalled cs
deleted numerous programs including norton
running on 1 stick of ram
unticked and ticked
-disable fullscreen optimisations
-run this program in administrator
-run this program in compatibility mode
In bios
-updated bios
-disabled hyperthreading
-reset to factory settings

other errors ive had:
nvgpucomp64.dll!Unknown
panorama.dll!Unknown
scenesystem.dll!Unknown
nvwgf2umx.dll!Unknown
materialsystem2.dll
rendersystemdx11.dll
crashhandler64.dll
tier0.dll!Unknown

although i think ive worked through these errors and so far its just
scenesystem.dll

I am not very tech cluey so if Im not making sense please forgive.
Any help in the matter would be greatly appreciated
< >
Showing 1-14 of 14 comments
Bad 💀 Motha Oct 6, 2024 @ 10:17pm 
You do realize you own one of the CPUs now known for higher then normal failure rates?
mtono Oct 6, 2024 @ 10:20pm 
Originally posted by Bad 💀 Motha:
You do realize you own one of the CPUs now known for higher then normal failure rates?
thumbs up!
Sunde Oct 6, 2024 @ 10:41pm 
Its only cs2 that crashes. No other games crash, i run more intensive games and have no issues
Bad 💀 Motha Oct 6, 2024 @ 10:47pm 
Try wiping GPU Drivers using DDU app in Safe Mode. Then reboot and install the latest GPU Driver fresh, reboot when done.

That error can often be associated with Visual C Runtimes.
Try uninstalling all of those off your system. Reboot, and then download and install them all again via > https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one (extract the contents, then run the BAT file to automate the installers); when done reboot and then manually click "Check for Updates" in your OS' Windows Updates section.
Set-115689 Oct 6, 2024 @ 11:46pm 
Since you have an effected cpu update bios and install microcode 0x12b. Set bios to intel defaults and enable/select an xmp ram profile. See if that helps at all?
Last edited by Set-115689; Oct 6, 2024 @ 11:47pm
Set-115689 Oct 6, 2024 @ 11:55pm 
Might be an issue with a recent update:

Recent update caused the crash issue. below is the way how to fix it, hope Valve can fix it soon in next update.

Find the cs2.exe, normally under this folder: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64

RMB the exe file, click the "compatibility" , enable the checkbox for "Run this program in compatibility mode for 'windows8'"
I have tested over 10 times, the crash issue was gone after this change.

Can try verifying game files

There's apparently youtube videos.

Can search cs2 forum for crashing
Bad 💀 Motha Oct 7, 2024 @ 12:02am 
How do they keep breaking stuff like this? People said that was some kind of a fix for the Rockstar Launcher as well, very odd. These companies must have a bunch of monkeys for coders. Doesn't seem logical to have to select the Win7 or Win8 compatibility when all these launchers and games were already working fine before under Win10. Now on Win11 this can be hit/miss; especially if you updated to 24H2.
_I_ Oct 7, 2024 @ 2:30am 
update bios
get the correct drivers from the mobo mfg site

post a cpuz validation link
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here

psu brand/model/age?
Last edited by _I_; Oct 7, 2024 @ 2:30am
skOsH♥ Oct 7, 2024 @ 4:52am 
Check for bios updates and chipset driver updates, LAN driver, audio drivers....etc.

Definitely run 16gbx2 on an xmp profile
Adjust timings on them after setting xmp. Just *barely*. I'm talking about lowering the cl# by 1, the next two values by 2 each, and the refresh tRC = 2+2. Otherwise if these timings are not measured out properly, it can lead to ram running sporadically or being unstable. So a good timing would be something like 32 - 36 - 36 - 72. 36+36=72. Having the middle two timings add up to the total tRC timing

Use process lasso to whip your cpu into allocating as much computational power to cs2 as possible whilst keeping it stable. Cs2 needs dx12 in source 2 to take advantage of more than a few cores of a cpu. Process lasso is literally the only solution I have found for now..

Put steam.exe at "memory priority set by registry". Allocate cpu cores and set affinity to groups of 2, starting with core 1 if you're amd, core 0 if Intel.


So an Intel user would be setting cpu priority and affinity to core/threads 0,1,2,4,5,8. Amd users would set it to core1,2,5,6,9,10

Cs2.exe in process lasso should be set to high or extra high priority (one level below real-time priority)

Set I/O as normal

Check cpu-z, make sure the timings and frequency is where it should be at. Also useful to check the frequency of the cpu clock.

Cs2 is not optimized. It's still just only over a year after the beta was released to everyone.

For some reason, I am completely convinced that to entirely eliminate your stuttering or bad performance, is after maxing out your cpu and have it be stable and not overheat, and make sure your gpu is not bottlenecked ( it should reach maybe 60%), you *need* to lower those four latencies that are listed on the ddr5 xmp timings. If you have a good kit of ram, you can get slightly faster timings and still have it on xmp with minimal loss to frequency clock

Ram does the job of juggling all the temporary files, specific information on frame pacing and times, it will hold onto net code information for the packets you're buffering, etc. Think of the timings as how a juggler paces the objects they are juggling. If the timings are not optimized, things get messy....especially in a game like cs2 which runs at high fps. If a juggler doesn't have good timing, they will drop their items they're juggling

If the timings are too slow, you will experience bad 0.1% and 1% fps lows, as well as a lot of stuttering

Find an option that's not vsync that helps with frame timings and placement....without limiting frames. Preferably async for nvidia.

Turn off the UI option to see teammate weapons and utility loadouts through walls.

Limit your fps value to 10fps below your slowest 0.1% and 1.0% fps lows for the value of the in game menu fps limit

Put the fps_max at 0

Lower settings to bilinear/trilinear for texture filtering, and 2x msaa instead of 4x

If running nvidia, use launch options -dx12, -high, -novid, -nojoy

In windows, disable fullscreen optimizations, and also disable high dpi scaling.

If all this doesn't work, delete temporary files, delete the dx11 shader cache, uninstall, and then reinstall the same. That fixed nearly all my performance issues
Last edited by skOsH♥; Oct 7, 2024 @ 4:55am
Sunde Oct 7, 2024 @ 10:32am 
Thank you for the assistance guys
I ran tests on the CPU using Intel diagnostics and it came out fine
Bios is already to date and back to defaults
Caping my CPU at 5 GHz has seemed to fixed things for now
Have already tried rmbing the CS2. .exe
Forgive me that i didn't already mention as I've already done so many things.

Understood cs is not optimised yet but also sad as the game is 1 year old.
Set-115689 Oct 7, 2024 @ 10:59am 
Intel diagnostic test isn't great. Likely need to run other tests.

If the ram is overclocked manually try using xmp settings or run the ram at default speeds for testing.
Illusion of Progress Oct 7, 2024 @ 12:04pm 
Originally posted by Sunde:
Caping my CPU at 5 GHz has seemed to fixed things for now
Limiting the clock speed is one of the things known to increase stability for Raptor Lake CPUs with the stability/degradation issue. I would look further in that direction if I were you; the Intel Processor Diagnostic tool is way too generic and won't catch this. If you have games with shader compilation, those tend to be good tests. They like to throw an error to the extent of being unable to allocate rendering resources due to a lack of memory or some such, which sounds like a GPU/VRAM thing but it's because the CPU got unstable while compiling shaders.

Something else to try is with RAM at default/JEDEC speeds. That's basically troubleshooting 101 when you start having stability issues.
Bad 💀 Motha Oct 7, 2024 @ 3:22pm 
Run Intel Burn Test for about 30 mins and see how it does. But yea most likely it's that particular game
Last edited by Bad 💀 Motha; Oct 7, 2024 @ 3:22pm
Set-115689 Oct 7, 2024 @ 9:03pm 
Maybe cap the voltage in the bios in case the cpu spikes during the tests??? No idea. Don't want to wreck stuff that isn't broken.

https://www.youtube.com/watch?v=P7Eyv5d2Rq8
Last edited by Set-115689; Oct 7, 2024 @ 9:05pm
< >
Showing 1-14 of 14 comments
Per page: 1530 50

Date Posted: Oct 6, 2024 @ 9:35pm
Posts: 14