Question I'm not sure if I should replace my motherboard for new CPU?

[zkfltmxkf]

I've recently bought a 5800x3D for my PC. Currently I have a Gigabyte x570 Aorus Elite with Ryzen 3600.

The problem is some years ago when I updated my bios it had this problem where though the update went fine, when it booted into windows everything it rendered on my screen was terribly deformed (?) like it was zigzagish static kinda like white noise with shapes (just based on the colors I could tell it was on windows log in screen) and it was unresponsive for an hour at which point I decided to force it off. Since then it'd occasionally hang on boot screen, sometimes the RGB on motherboard will stay on even when the system is turned off and seems to be reproduced in scenarios like power outage. However, it's never bricked or had any other noticeable problems.

I'm not sure if this is an indicator that I should replace my motherboard to use with the new CPU, as most of things seem to work relatively fine without any problems. So far the 3600 has had no problem and isn't fried so I'm prone to thinking that whatever problems it might have doesn't affect the cpu, but I also don't want any risk of frying my new cpu due to faulty motherboard.

What do you guys think?

 

[drea.drechsler]

I've recently bought a 5800x3D for my PC. Currently I have a Gigabyte x570 Aorus Elite with Ryzen 3600.

The problem is some years ago when I updated my bios it had this problem where though the update went fine, when it booted into windows everything it rendered on my screen was terribly deformed (?) like it was zigzagish static kinda like white noise with shapes (just based on the colors I could tell it was on windows log in screen) and it was unresponsive for an hour at which point I decided to force it off. Since then it'd occasionally hang on boot screen, sometimes the RGB on motherboard will stay on even when the system is turned off and seems to be reproduced in scenarios like power outage. However, it's never bricked or had any other noticeable problems.

I'm not sure if this is an indicator that I should replace my motherboard to use with the new CPU, as most of things seem to work relatively fine without any problems. So far the 3600 has had no problem and isn't fried so I'm prone to thinking that whatever problems it might have doesn't affect the cpu, but I also don't want any risk of frying my new cpu due to faulty motherboard.

What do you guys think?

First a question: what BIOS rev are you currently running? For the 5800X3d you will need it to be the latest, which is a good idea even for the 3600. You don't have to update to it yet although it wouldn't hurt.

There's no good reason to change motherboard for the new CPU unless it's defective but the problems you describe sound more like GPU driver corruption. To resolve these issues I'd start with resetting CMOS, then boot into Windows and run SFC /SCANNOW from a command prompt with admin rights. Then uninstall the GPU drivers and run DDU to clean them up and re-install the latest version for your GPU.

Once you've got the system running smoothly, then update BIOS to the latest (for compatibility with the new CPU) and swap out the CPU for the 5800X3d. After swapping the CPU reset CMOS again before booting up into Windows.

 

[zkfltmxkf]

First a question: what BIOS rev are you currently running? For the 5800X3d you will need it to be the latest, which is a good idea even for the 3600. You don't have to update to it yet although it wouldn't hurt.

There's no good reason to change motherboard for the new CPU unless it's defective but the problems you describe sound more like GPU driver corruption. To resolve these issues I'd start with resetting CMOS, then boot into Windows and run SFC /SCANNOW from a command prompt with admin rights. Then uninstall the GPU drivers and run DDU to clean them up and re-install the latest version for your GPU.

Once you've got the system running smoothly, then update BIOS to the latest (for compatibility with the new CPU) and swap out the CPU for the 5800X3d. After swapping the CPU reset CMOS again before booting up into Windows.

I'm not sure of the exact version, however I have updated the bios earlier this year. Although I was already planning to update it before installing the new cpu.

Yea, it just that problems I have sounds like a motherboard issue. It only started happening after a bios update and the rendering issue has not happened ever since right after the bios update. It's only sometimes it still hangs on booting screen, and RGB sometimes doesn't turn off. These at the least the seems like a problem that'd be bios related if not motherboard as a whole seeing the problem with RGB(that comes as part of the motherboard).

Though I haven't tried messing with CMOS, once I nut up to installing 5800x3d on this motherboard, I'll definitely give the method a try. Until then I'd probably want a clearer answer on whether if it's even safe to put a new cpu on this motherboard lol.

Ty for the reply.

 

[drea.drechsler]

...It only started happening after a bios update and the rendering issue has not happened ever since right after the bios update. It's only sometimes it still hangs on booting screen, and RGB sometimes doesn't turn off. These at the least the seems like a problem that'd be bios related if not motherboard as a whole seeing the problem with RGB(that comes as part of the motherboard).

Though I haven't tried messing with CMOS, ...

You're not really describing anything that could be definitively considered a defect on the motherboard. As I understand it, most people have problems with RGB even when it's working right so I can't say that's a reason. I don't use it...in fact turn it off on my Asus board.

If you never reset CMOS after installing the 3600...and after updating BIOS...that could easily be the source of your problems. It's not hard to do, actually quite safe. One way is to remove the coin cell battery for a few minutes. The simplest way is to short the two pins with a screwdriver tip. Just be sure to turn it off and remove the power cord from the wall outlet before you open up the case and you'll be perfectly safe even if you accidentally short the wrong two pins.

You should run also "SFC /scannow" any time you start having strange Windows problems. It may not fix the problem even if it does find system file corruption but it can do no harm and takes only a couple minutes.

Uninstalling GPU drivers and cleaning up with DDU takes a bit longer, but it's surprising how many people are suffering through corrupted drivers and didn't know it.

 

[zkfltmxkf]

You're not really describing anything that could be definitively considered a defect on the motherboard. As I understand it, most people have problems with RGB even when it's working right so I can't say that's a reason. I don't use it...in fact turn it off on my Asus board.

If you never reset CMOS after installing the 3600...and after updating BIOS...that could easily be the source of your problems. It's not hard to do, actually quite safe. One way is to remove the coin cell battery for a few minutes. The simplest way is to short the two pins with a screwdriver tip. Just be sure to turn it off and remove the power cord from the wall outlet before you open up the case and you'll be perfectly safe even if you accidentally short the wrong two pins.

You should run also "SFC /scannow" any time you start having strange Windows problems. It may not fix the problem even if it does find system file corruption but it can do no harm and takes only a couple minutes.

Uninstalling GPU drivers and cleaning up with DDU takes a bit longer, but it's surprising how many people are suffering through corrupted drivers and didn't know it.

Well, the motherboard was new with new 3600 at the time. I don't mean to be contrary to your point, it's just that for me it just seems like in the sequence of events where, I update my bios, PC becomes unresponsive with rendering issues, holding the power button wouldn't even shut it off and I had to unplug the power, then it proceeded to developed these problems of hanging on boot screen / rgb, it just SEEMS like a motherboard issue because it only happened after what it seems to be a corrupted bios update. But I suppose bios issues doesn't have to equal motherboard issues. Though it was clearly not a windows problem and never had one so far.

I have NEVER tried resetting CMOS even though it's been recommended before so I'll give it a go.

 

[CountMike]

Well, the motherboard was new with new 3600 at the time. I don't mean to be contrary to your point, it's just that for me it just seems like in the sequence of events where, I update my bios, PC becomes unresponsive with rendering issues, holding the power button wouldn't even shut it off and I had to unplug the power, then it proceeded to developed these problems of hanging on boot screen / rgb, it just SEEMS like a motherboard issue because it only happened after what it seems to be a corrupted bios update. But I suppose bios issues doesn't have to equal motherboard issues. Though it was clearly not a windows problem and never had one so far.

I have NEVER tried resetting CMOS even though it's been recommended before so I'll give it a go.
PS,
Power should be right off while doing CMOS reset or it will not "catch".

It's a good idea. practically mandatory to reset CMOS to factory defaults for any major component change, that gives it a chance to run thru whole P.O.S.T. sequence and get acquainted with it and make default settings accordingly. Most if not all modern parts are "Plug&Play" having own kind of BIOS containing data relevant to that part.
When updating BIOS version CMOS should also be cleared first as well as after although most updates do that anyway.
Modern BIOS/UEFI also have 2 stages of CMOS clearing, one by using a button or posts on the MB which clears only changes made to BIOS/UEFI and second stage when battery is also removed for few seconds and that also resets time and some other settings.