New Build Crashing Games - Help Required

Associate
Joined
11 Jan 2021
Posts
12
Hello,

Long time forum lurker but first time PC builder so please reply in somewhat layman's terms, I'll dump a lot of info here not all of it will be relevant but I let those who are more experienced than myself be the judge of what is/isn't relevant.

PC Spec
CPU - AMD 5800X
GPU - 6800XT (sapphire nitro+)
Mobo - MSI x570 Tomahawk
Ram - 4 x 8gb Corsair Vengeance Pro 3600mhzRGB (set to 3600 in bios using XMP)
CPU Cooler - Corsair H115i AIO (240mm)
PSU - Corsair CX750f rgb
Storage - Corsair MP600 1tb m.2

Software
Mobo - Bios is the latest with the exception of a Beta (7C84v14)
GPU - Latest according to AMD Radeon/Adrenaline software (20.12.02)
Chipset - Latest according to AMD Radeon/Adrenaline software

Amd Radeon itself is one before latest as the latest is an optional, I have tried both

Crashing
Idle/low load - downloading games browsing internet or listening to music, no issue's
In Game - 3 different character of crashes

- While playing troy total war I experienced two BSOD crashes and restarts "SYSTEM SERVICE EXEPTION"
- While playing any game <5mins boot to desktop this is a regular crash,
- I have since changed my GPU to rage mode in Radeon this gave me circa 10mins of play until game froze but didn't boot to desktop, used task manager to close

AMD Radeon software does potentially give a big clue? seen the following message a few times "Default Radeon WattMan settings have been restored due to an unexpected system failure"


Games - (1440p)
Troy Total War
COD Cold War
AC Valhalla

Things to try

- Single ram stick non XMP - Tried
- Reduce game graphics - Tried
- Beta Bios?
- Optional Radeon update - Tried
- Reinstall windows - done tbc
- GPU power, add additional cable - done
- CPU power currently has the 8pin and 4 pin, is there a correct side of the 4 pin that should be used ?


In summary lots of things to try but I'm essentially learning on the job is there anything else you can think of that might be a teething issue I'm missing?
 
Last edited:
Try setting the core voltage to override mode 1.3v and CPU clock to 4.5ghz fixed and see if this stops the bsods.
 
Yes
If your unsure how, if you Google overclocking guide' and the name of your motherboard it will show you where that setting is. Even tho your not overclocking
Will do, I was hoping to not have to "OC" my system and just use it a default settings, but as its unstable I'm open to trying to fix it this way so have some more learning to do,
 
Will do, I was hoping to not have to "OC" my system and just use it a default settings, but as its unstable I'm open to trying to fix it this way so have some more learning to do,

Raising the voltage isn't overclocking.

Sounds more like a driver or GPU issue to me. I was just telling you how to find were to change the vcore

I would try a different driver. Find a older one.
 
Last edited:
Will do, I was hoping to not have to "OC" my system and just use it a default settings, but as its unstable I'm open to trying to fix it this way so have some more learning to do,
It's more underclocking the system since at stock it will boost to 4.85. If a 4.5ghz all core clock is stable then this will show if the CPU is unstable at stock settings.
 
It's more underclocking the system since at stock it will boost to 4.85. If a 4.5ghz all core clock is stable then this will show if the CPU is unstable at stock settings.
I chose my words badly, I meant any general tinkering,

I tried the 1.3v with no success, I did not lock the frequency as I wasn't sure how to, I now have seen an msi video that explains it so I can try again later
Ive also now tried to disable Precision Boost (PBO) and C-State with no improvement

In my last attempt I had the Radeon metrics up and noticed CPU utilization is fairly low (30%) would this point back to more of a gpu error?
 
"Default Radeon WattMan settings have been restored due to an unexpected system failure"
i get this every now and again i just put it down to crappy radeon software, i know when the graphic drivers have crashed because the fans ramp up.
 
Hi - and welcome to this side of the forums!

As everything is brand new it should run out of the box and the most likely culprit is a driver glitch - possibly corrupted when installing or changing processor. I suggest you do not mess about with tinkering to try and "fix" things just go-ahead and do a fresh install of windows with all of your hardware plugged in and running at stock speeds. If you have any problems thereafter you will likely be looking for a broken component and we'll worry about that if or when it happens.

Good luck.
 
Hi - and welcome to this side of the forums!

As everything is brand new it should run out of the box and the most likely culprit is a driver glitch - possibly corrupted when installing or changing processor. I suggest you do not mess about with tinkering to try and "fix" things just go-ahead and do a fresh install of windows with all of your hardware plugged in and running at stock speeds. If you have any problems thereafter you will likely be looking for a broken component and we'll worry about that if or when it happens.

Good luck.
Understood,

Doing this now, thank you
 
Assuming you've tried all other suggestions, I'm going to point fingers at the memory. The only 3600MHz Corsair kit I can find tested by MSI for the motherboard is CMK16GX4M2B3600C18 ver4.31 and that is only up to 2 DIMMs. Officially that means your config is unsupported by MSI. It's unlikely as memory support has improved greatly since Zen 1, it's still a possibility.

Remove all but 1 stick, run it at 2133 and see if the errors occur again under the same scenarios.

The Wattman error is likely just drivers, PITA, but something we live with (I get a driver crash daily with my 5700 XT).
 
Assuming you've tried all other suggestions, I'm going to point fingers at the memory. The only 3600MHz Corsair kit I can find tested by MSI for the motherboard is CMK16GX4M2B3600C18 ver4.31 and that is only up to 2 DIMMs. Officially that means your config is unsupported by MSI. It's unlikely as memory support has improved greatly since Zen 1, it's still a possibility.

Remove all but 1 stick, run it at 2133 and see if the errors occur again under the same scenarios.

The Wattman error is likely just drivers, PITA, but something we live with (I get a driver crash daily with my 5700 XT).

Not yet tried anything with Ram, for info my ram is CMW16GX4M2D3600C18,


I have just reset with a fresh windows install, as per the post above yours, I am downloading Assasins Creed now, I have not downloaded any other software at this point I was thinking to go straight in to the game to see what happens, unless any one can advise against this? (download will take a couple of hours so I have time)
 
Not yet tried anything with Ram, for info my ram is CMW16GX4M2D3600C18,


I have just reset with a fresh windows install, as per the post above yours, I am downloading Assasins Creed now, I have not downloaded any other software at this point I was thinking to go straight in to the game to see what happens, unless any one can advise against this? (download will take a couple of hours so I have time)

Are you also running the hardware at stock settings, or the same and before the fresh install (so the only difference is the installation)?
 
Are you also running the hardware at stock settings, or the same and before the fresh install (so the only difference is the installation)?
I need to go back to bios and turn the ram back to 2133 that should be only thing that is currently "not stock" once the download is complete ill shutdown, remove all but one stick and do that all in one go
 
Update:

Fresh windows install
Windows updates installed
Ubisoft Connect and AC vallhala installed
1 Ram Stick, (second slot from CPU)
Set to 2133 in Bios

No other software installed or downloaded at this point,

Result - Game crash after 5-6 minutes and boots to desktop allows me to report bug via ubisoft prompt,

I then took a look in Event viewer/windows logs/sysyem right about the time it crashed there is a warning "Display driver amdkmdag stopped responding and has successfully recovered" unfortunatly i hadnt checked this location prior to windows reinstall, but It felt like a softer crash as it was to desktop not a full restart. im cautiously optimistic this is a step in the right direction and we should now start to point at the GPU driver?
 
Last edited:
Back
Top Bottom