Hello everyone,
Hope everyone is safe and well during these times
First, I apologise for my very lengthy first post.
My issue is the title of this thread. My question is, how do I further identify the issue? Currently I think I have narrowed it down between the Motherboard, GPU, or the RAM. However, due to so many inconsistencies, I can’t pinpoint the issue.
I will appreciate any other suggestions and will test them out as well.
Below are information of my build, a background of the build, temperatures, what games I have tried and tools, the tests I did, the tests I still intend to try, and their results.
1. Build
My current build:
This desktop was first built at the end of July. Probably overkill for 1080p gaming but wanted a minimum 60fps for Godfall, Assassin's Creed: Valhalla and Cyberpunk 2077 at the highest graphical setting...
For the first few months, no issues at all. Everything went well. I never tinkered with anything and let Radeon and ASUS do it’s own thing - I used “D.O.C.P. Profile #1” and “Optimal” in the “EzSetup” at the BIOS and "Default" for Radeon.
However, early September, problems started to happen. Games would crash with no warning until I check my Event Viewer and Radeon Software. In “Event Viewer”, I get the “Kernal-Power” issue and in the “Radeon Software”, I get the “Default Radeon WattMan settings has been restored due to unexpected system failure”. I have done numerous fixes but they always come creeping back.
I don’t know if the fault lies with Radeon (as I am always with nVidia), and because of the current pandemic, I can’t get my mates to test it on their systems. When idle, watching TV, listening to music, or downloading, I get zero issues.
All hardware and software are all up to date.
3. Temperatures and Utilisation
Based on videos and forums, the following results seem to be normal for my chosen parts.
Games played before September:
So the culprit (maybe): Motherboard’s PCIe socket is faulty or GPU is faulty
Games played after September till Cyberpunk 2077 came out:
So the culprit (maybe): Motherboard’s RAM socket is faulty or RAM is faulty
Overall it could be:
Tests I’ve done to try and solve the issue in September:
Tests I’ve done to try and solve the issue in December is exactly the same as September, however, with a set of additional new tests:
Edit 2 (22/12/2020): Updated the tests done in December
Hope everyone is safe and well during these times

First, I apologise for my very lengthy first post.
My issue is the title of this thread. My question is, how do I further identify the issue? Currently I think I have narrowed it down between the Motherboard, GPU, or the RAM. However, due to so many inconsistencies, I can’t pinpoint the issue.
I will appreciate any other suggestions and will test them out as well.
Below are information of my build, a background of the build, temperatures, what games I have tried and tools, the tests I did, the tests I still intend to try, and their results.
1. Build
My current build:
- AMD Ryzen 7 3800X
- BIOS on “Optimal”
- Performance automated by ASUS - went to 4.2GHz @ 1.37V. Sometimes even at maximum! Which is 4.5GHz but didn't note down the voltage (but less that 1.5V)
- Corsair H100i RGB PLATINUM
- Asus PRIME B450M-K
- Corsair Vengeance RGB Pro 16GB (2x 8GB) DDR4-3200 CL16
- BIOS runs it at 3200MHz (16-18-18-36 @ 1.35V)
- Crucial 525GB MX300 SATA M.2 SSD
- Western Digital Blue 1TB 2.5" SSD
- PowerColor Radeon RX 5700XT 8GB Red Dragon
- “Default” setting on the “Radeon Software” (performance automated by Radeon - can't remember how high it went. Around 2000MHz I think)
- Corsair Crystal 280X RGB
- Corsair RMx 650W (80+ Gold)
- Asus TUF GAMING VG249Q (via DisplayPoint)
- Windows 10 Pro
This desktop was first built at the end of July. Probably overkill for 1080p gaming but wanted a minimum 60fps for Godfall, Assassin's Creed: Valhalla and Cyberpunk 2077 at the highest graphical setting...
For the first few months, no issues at all. Everything went well. I never tinkered with anything and let Radeon and ASUS do it’s own thing - I used “D.O.C.P. Profile #1” and “Optimal” in the “EzSetup” at the BIOS and "Default" for Radeon.
However, early September, problems started to happen. Games would crash with no warning until I check my Event Viewer and Radeon Software. In “Event Viewer”, I get the “Kernal-Power” issue and in the “Radeon Software”, I get the “Default Radeon WattMan settings has been restored due to unexpected system failure”. I have done numerous fixes but they always come creeping back.
I don’t know if the fault lies with Radeon (as I am always with nVidia), and because of the current pandemic, I can’t get my mates to test it on their systems. When idle, watching TV, listening to music, or downloading, I get zero issues.
All hardware and software are all up to date.
3. Temperatures and Utilisation
Based on videos and forums, the following results seem to be normal for my chosen parts.
- CPU
- Temperatures:
- Minimum (idle): 30°C
- Maximum: 75°C
- Utilisation:
- Not quite sure. I am pretty sure it doesn't go above 90%. Cyberpunk 2077 doesn't go over 50%
- Temperatures:
- GPU
- Temperatures:
- Minimum (idle): 50°C
- Maximum: 80°C and 100°C (junction)
- Utilisation:
- Pretty much between 95 to 100%
- Temperatures:
- RAM
- Temperatures:
- Minimum (idle): 42°C
- Maximum: need to check
- Utilisation:
- I think it's between 50 to 60%
- Temperatures:
Games played before September:
- 3DMark: Crashes at the first test - within a few seconds to 5 minutes
- Divinity: Original Sin 2: restarts computer after an hour of gaming or less
- League of Legends: freezes and resumes but no crashing - detrimental when team fights occur
- Path of Exile: I don’t think it crashed once
- Tom Clancy's Rainbow Six Siege: restarts computer after approximately 2 hours of gaming or less
So the culprit (maybe): Motherboard’s PCIe socket is faulty or GPU is faulty
Games played after September till Cyberpunk 2077 came out:
- 3DMark: no issues
- Assassin’s Creed: Valhalla: no issues
- Cyberpunk 2077: crashes vary from seconds to several hours. Also, I experienced my first crash to the desktop and sent the error reports to AMD/Radeon and CD Projekt.
- Godfall: no issues
- Path of Exile: no issues
- Warzone: no issues
So the culprit (maybe): Motherboard’s RAM socket is faulty or RAM is faulty
Overall it could be:
- Motherboard sockets are bad (since it is a cheap ol’ thing)
- Bad luck with faulty GPU and/or RAM
- Cyberpunk 2077 strains my computer badly
Tests I’ve done to try and solve the issue in September:
- Test 1: Turned off fast boot
- Test 2:
- RAM back at base 2133MHz and CPU controlled by ASUS
- For the GPU, on the “Radeon Software”, I left it at “Automatic”
- Test 3: Same as Test 2 but for the GPU, I left it at “Undervolt”
- Test 4: Same as Test 2 but for the GPU, I left it at “Overclock”
- Test 5: Reseating GPU and RAM, making sure all cables are plugged in and not loose, reseating and applying new thermal for
- Test 6: Try the original PSU cables (I bought premium Corsair cables to rule them out)
- Test 7: Try onboard GPU
- Test 8: Unplug all unnecessary devices (only the keyboard & mouse connected)
- Test 9: Try each RAM individually and different sockets individually
- Test 10: Reinstalling drivers
- Test 11: Remove my Lego stand to stop the GPU drooping down
- Test 1 to 10: Issue still occurs
- Test 11: Issue is gone. Concluded that the Lego was too high and it must be the motherboard with a bad PCIe socket or the GPU had a bad connection because of the Lego.
Tests I’ve done to try and solve the issue in December is exactly the same as September, however, with a set of additional new tests:
- Test 12: Using two dedicated 6+2 PCIe cables instead of one splitting into two 6+2 cable ends
- Test 13: Tried setting RAM at 3200MHz @ 16-18-18-36 1.2V
- Test 14: I've seen people saying to try MemTest86, so will need to try that
- Test 15: Try other games and see if the issue persists (when RAM is back at 3200MHz @ 16-18-18-36 1.35V)
- Test 16: Prevent ASUS from overclocking the CPU as well - as default it’s all automatic. However, I'm not exactly sure how to do this yet as I thought resetting back to default settings meant turning it off.
- Test 1 to 15: Issue still occurs. Other games do not cause the same issue as Cyberpunk 2077.
Edit 2 (22/12/2020): Updated the tests done in December
Last edited: