Associate
- Joined
- 22 Apr 2021
- Posts
- 17
Ayup,
I'm after a bit of advice on a recent Ryzen 5800x purchase from Overclockers.
This replaced an existing 3700x in an MSI Pro-a X570 board with 16 gig of cas18 3600 ram (with an AMD-specific XMP profile), an 850watt PSU, Noctua DH15 cooler and RTX 3080 and various other bits and bobs including a Valve Index.
The system's been solid and stable for ages with the 3700x. Since putting the 5800x in I just can't get the thing to be stable when gaming. It's rock solid doing regular Windows stuff, it always boots and runs brilliantly. But in *some* games (specifically, Automobilista 2, Project Cars 2 and Assetto Corsa Competizione) it'll blue-screen after anything from 5 minutes to an hour. The error is logged in the event log as a "bugcheck 0x00000124" which I believe is a generic hardware fault error code. There are no other errors in the event log (no on-going WHEA errors or anything, just this BSOD).
I can run CPU benchmarks like Prime95 without errors for ages. The CPU will boost to around 4600 all core and 4820 single core when benching, with temps topping out at about 80 when running all core prime85 small tests. Temps in gaming are much lower (in the low 60s). But as I'm a VR player I never actually get to see the temps at the point when it BSODs because I have the goggles on. I also ran the Windows memory diagnostic (no errors).
I've been through some fairly standard trouble shooting steps - set the ram back to default, updated drivers (chipset & GPU), tried 3 different BIOSes (the latest 2 beta bioses and the last 'official' bios). I've also tried with PBO disabled in BIOS and lower TDC, EDC and PPT limits (80, 120 and 120 respectively) but nothing seems to make any difference - it'll run for a while in these games but eventually BSOD with this same bugcheck error.
Is there anything I've missed here? I'm not really sure what to do - should I start the RMA process? It feels like it may be a faulty chip, given that the 3700x has been running like a champ with not a single crash or hiccup for more than a year, but I appreciate that demonstrating that it's definitely the chip will be a challenge
I'm after a bit of advice on a recent Ryzen 5800x purchase from Overclockers.
This replaced an existing 3700x in an MSI Pro-a X570 board with 16 gig of cas18 3600 ram (with an AMD-specific XMP profile), an 850watt PSU, Noctua DH15 cooler and RTX 3080 and various other bits and bobs including a Valve Index.
The system's been solid and stable for ages with the 3700x. Since putting the 5800x in I just can't get the thing to be stable when gaming. It's rock solid doing regular Windows stuff, it always boots and runs brilliantly. But in *some* games (specifically, Automobilista 2, Project Cars 2 and Assetto Corsa Competizione) it'll blue-screen after anything from 5 minutes to an hour. The error is logged in the event log as a "bugcheck 0x00000124" which I believe is a generic hardware fault error code. There are no other errors in the event log (no on-going WHEA errors or anything, just this BSOD).
I can run CPU benchmarks like Prime95 without errors for ages. The CPU will boost to around 4600 all core and 4820 single core when benching, with temps topping out at about 80 when running all core prime85 small tests. Temps in gaming are much lower (in the low 60s). But as I'm a VR player I never actually get to see the temps at the point when it BSODs because I have the goggles on. I also ran the Windows memory diagnostic (no errors).
I've been through some fairly standard trouble shooting steps - set the ram back to default, updated drivers (chipset & GPU), tried 3 different BIOSes (the latest 2 beta bioses and the last 'official' bios). I've also tried with PBO disabled in BIOS and lower TDC, EDC and PPT limits (80, 120 and 120 respectively) but nothing seems to make any difference - it'll run for a while in these games but eventually BSOD with this same bugcheck error.
Is there anything I've missed here? I'm not really sure what to do - should I start the RMA process? It feels like it may be a faulty chip, given that the 3700x has been running like a champ with not a single crash or hiccup for more than a year, but I appreciate that demonstrating that it's definitely the chip will be a challenge