Then I'm going to conclude it's a BIOS setting or the motherboard at this point. I'm not there to really test it so I can't be sure.
Out of curiosity, do you have an option to disable onboard video in the CPU? Also, monkey with BIOS settings saving different profiles.
Edit-
From your manual here.
Make sure BIOS is using default settings and auto settings.
For testing:
Turn off hyper-threading.
Chose two cores instead of four cores in the CPU via the BIOS setting.
Turn off Execute Disable Bit.
Turn off the Adjacent Cache Line Prefetch.
Disable the Intel C-State.
Have no idea what the CFG Lock is, but try turning it off/on for testing.
Disable the EIST.
Disable Intel Turbo Boost.
Disconnect all peripherals except mouse and keyboard.
Thanks for taking time to help me.
Before testing all this I have news on my side, a bit of "improvment". I'll explain, maybe it will help you narrowing the problem.
So when I previously tried old Nvidia drivers, I took them from the Nvidia Advanced Driver Search which only show the last 20 driver versions, which, when I tried, only got back to 2021. None of those I tried improved the stability.
Yesterday I found that the GPU ROG page proposed far more versions... back to 2016. So I gave it a shot.
I downloaded the oldest one, ver. 368.39, uninstalled the previous with DDU and installed only the graphic driver.
The game started, and I played for 3 hours without seeing a crash. But it still crashed once, when I was afk. The crash log is still the same, but the .dmp is a bit different, it gives a NULL_CLASS_PTR_WRITE_c0000005_nvwgf2umx.dll.
Yesterday I was playing with only a single RAM stick. Today I put the second one back in, and it crashed quicker. Twice in an hour. Coincidence or linked ? Can't say, but I just removed the second stick and I'll retry. Also, the new .dmp gives another message : PRIVILEGED_INSTRUCTION_c0000096_nvwgf2umx.dll.
I hope it gives more information on the problem. If not, I'll try everything you proposed.
Thanks
- - - Updated - - -
The session with a single stick gave the same stats as yesterday : only one crash over a span of 3 hours. Seems fishy.
Look on your RAM sticks, are they ALL the same version numbers character for character?
I had an issue with crashing games and despite all of my RAM being the same, one stick, just one had a different serial number and it seems like it was that one stick of RAM. I pulled it (I'm now on 12 GB instead of 16) and the crash issue went away.
Again, they are ALL the same RAM. Just the serial number is different.
I had originally bought two sticks then latter two more. Thus the one stick that was different via the serial number only.
It was interesting for me though because with that one stick along side the other three, Memtest86 spat out errors. I don't recall seeing that before. But it did it this time. Removing all sticks except the odd numbered serial number stick and testing that one stick in Memtest86 had no errors.
My conclusion is that there's something different with that one stick versus the other sticks and thus had compatibility issues working together.
RAM is a huge thing when it comes to computer oddities since all the data that is processed goes through RAM. Game crashes, browser crashes, etc can be RAM related.
Is your RAM listed on your motherboard's QVL? Go to the motherboard manufacturer under support.
"I indeed tried to OC it when I built my PC 6 years ago, by curiosity, but reseted it to default settings. I checked those settings various times during my troubleshootings because removing the OCs is always advised. Is there something I missed here ?"
Exactly ... What you are missing is that the MOBO is 6 years old and used for gaming with Overclocking. That reduces the life/endurance of a MOBO and that is where 90% of the electronic components and indeed functionality is.
MOBOs are difficult to test because of the immense functionality involved, so I would come to a conclusion of the MOBO going out of spec in some respect.
That essentially means a new MOBO. The SSD/HDD and RAM modules, Graphic Card are in themselves probably just fine but they are reliant on the MOBO electronics to function correctly.
The fact that you now have no overclocking now and still have problems means the damage has been done in previous years to that MOBO.
My comments were largely to get the info from you, which you have supplied.
Thanks you both.
Yes, the sticks were bought as a pack and have the same version number. And the production numbers (I guess ?) follow each others.
Yes
So, for the BIOS settings:
- Initiate Graphic Adaptater was correctly on PEG.
- I changed PCI Express protocol from Auto to Gen3.
- Legacy + UEFI was already set. I tried UEFI and enabling WHQL support but OS wouldn't boot, so reseted to Legacy + UEFI.
- I'm currently trying with the CPU settings you listed, except Hyper-threading and Execute Disable Bit that couln't been found despite being specified in the MB manual.
Also, I'll share what I observed with different GPU drivers :
I tried another game when the oldest available driver was installed (368.39) and a popup warned that this driver was too old and know for having reliability issues. They recommended the version 441.20. The closest version on the GPU page was 441.87, but when I tried it RocketLeague wouldn't start. So from this one I tried several until both games started (417.71 and 416.33 wouldn't let RocketLeague start). So for the moment I'm set with the version 398.36 wich allows both games to run. But they still both crashed a few times (drasticly less than before, nonetheless). This was before I applied CPU BIOS changes. I didn't played long enough since those changes to make a conclusion.
What I was trying to say is I only tried overclocking for a few hours 6 years ago. Maybe it was enough to do damages. I agree that the MOBO seems to be the source of the problem.
I'm looking for a new one (with new CPU because of socket evolution).
You are playing multiplayer games which have anti cheat. The anti cheat is causing the crashing when you play multiplayer games.
Also when you close a multiplayer game then the anti cheat can still be running in the background so it can mess up what you do next.
Uninstall all the multiplayer games that crash, restart the pc, play offline games that have no anti cheat and see what happens.
That's probably because your CPU doesn't have hyper threading and I think the execute disable bit is either CPU or chipset specific. I guess I should have known that before posting it as a test to try.I'm currently trying with the CPU settings you listed, except Hyper-threading and Execute Disable Bit that couln't been found despite being specified in the MB manual.
About the anti-cheat idea. That sounds prudent, but for the anti-cheat code to be so abrasive like that on one's computer makes you think this anti-cheat code crap is just that - crap! If that's what the issue is though... Who really knows. This is a very peculiar issue. Especially since everything it seems has been tried to no availability.
I've heard of some very bad business with that anti-cheat program crap and the privacy invasion. It existed in the days of Punk Buster. It's funny because Punk Buster was by my estimation only 60% good at doing what it should do and 99% good at pisses you off for one reason or another due to Punk Buster being a stupid "punk."
Even today the game hacks just for Call Of Duty ( a huge recycled franchise IMO) are MASSIVELY out of control like you wouldn't believe. I play with a couple damn, DAMN good COD players and they know a cheat was activated almost immediately. They're like a wolf that can smell it with the slight bit of lag or how the player plays. I'm not that good like that though. But it goes to show you all the effort in trying to prevent cheating while at the same time raping your computer and your privacy is BS.
Unfortunately I have some single player games which also crashed (Cities Skyline, Outer Wilds, Disco Elysium, Hades...).
But, I think you found a fix Simpilot ! As since I modified the CPU settings in the BIOS no crashes occured (played around 7 hours on 3 different games that always crashed before).
As reminder, I disabled Adjacent Cache Line Prefetch, Intel C-State, EIST and Intel Turbo Boost.
I'll wait a few days with this setup to ensure that those past hours weren't just lucky ones.
Then I'll start by reinstalling the second RAM stick, and maybe try a newer GPU driver.
And if among the 4 disabled settings some of them might be interesting to reactivate, I'll try one by one. Else I'll let them like this.
Regarding the MB and CPU upgrade, I'll wait while this setup still holds.
Thanks a lot for your time and your help, again ! I'll update the thread in the following days with my progression.
as i said if you immediately play a single player game after a multiplayer game then the anti cheat of the multiplayer game can still be active so it can make the single player game crash
restart the pc to force close the anti cheat, directly play a single player game and see if it crashes. if multiple single player games crashed and you didnt play a multiplayer game before them then something else is causing the problem
please directly play pure single player games that have no anti cheat after you restart the pc and let me know what happens. dont play a multiplayer game in single player mode because the anti cheat is still there
Quote
