Is there any CPU diagnostic check for Ryzen 5 3600?

[☄️⁧⁧Sneakydude555]

Intel has one, i used it for my Xeon x5675. soo does AMD have any?

[KeplersConjecture]

As far as I know the closest thing AMD has is its Ryzen Master System and older AMD System Monitor

https://www.amd.com/en/technologies/ryzen-master
https://www.amd.com/en/support/kb/faq/gpu-100


Neither are comparable to Intel's and are really more for overclocking than proper diagnostic work.

[☄️⁧⁧Sneakydude555]

KeplersConjecture님이 먼저 게시:

As far as I know the closest thing AMD has is its Ryzen Master System and older AMD System Monitor

https://www.amd.com/en/technologies/ryzen-master
https://www.amd.com/en/support/kb/faq/gpu-100


Neither are comparable to Intel's and are really more for overclocking than proper diagnostic work.

This is a bit worry some for me but thanks.

[KeplersConjecture]

NightMAREZ_VVV님이 먼저 게시:

KeplersConjecture님이 먼저 게시:

As far as I know the closest thing AMD has is its Ryzen Master System and older AMD System Monitor

https://www.amd.com/en/technologies/ryzen-master
https://www.amd.com/en/support/kb/faq/gpu-100


Neither are comparable to Intel's and are really more for overclocking than proper diagnostic work.

This is a bit worry some for me but thanks.

AMD has been notorious over the years for its bad driver support. Just one of those things unfortunately.

[☄️⁧⁧Sneakydude555]

KeplersConjecture님이 먼저 게시:

NightMAREZ_VVV님이 먼저 게시:

This is a bit worry some for me but thanks.

AMD has been notorious over the years for its bad driver support. Just one of those things unfortunately.

yep i really had a bunch of driver problems with my RX 470. thank God i have a 1660 now.

Guess i have to rely on the bios to make sure that the CPU is working fine. I plan to not overclock this cpu really. I just want to make sure my CPU is working fine after benchmarking stuff and in general usage

[r.linder]

KeplersConjecture님이 먼저 게시:

NightMAREZ_VVV님이 먼저 게시:

This is a bit worry some for me but thanks.

AMD has been notorious over the years for its bad driver support. Just one of those things unfortunately.

That's really only for GPUs. Their chipset drivers are usually fine.

Funny how nobody talked about the issues that Comet Lake had when it launched earlier this year because Intel rushed it into production to try to get a lead on AMD. NVIDIA's had their fair share of issues too, which I saw with my 2080, but people seem to act like AMD is the only one with problems.

NightMAREZ_VVV님이 먼저 게시:

KeplersConjecture님이 먼저 게시:

AMD has been notorious over the years for its bad driver support. Just one of those things unfortunately.

yep i really had a bunch of driver problems with my RX 470. thank God i have a 1660 now.

Guess i have to rely on the bios to make sure that the CPU is working fine. I plan to not overclock this cpu really. I just want to make sure my CPU is working fine after benchmarking stuff and in general usage

If there's no glaring issues, then it works. No reason to worry.

There's no point in manual overclocking a Ryzen 3000 CPU, they're pretty much pushed to the max out of the box. The more cores the chip has, the worse the OC potential, evident by the fact that most 3900Xs struggle to overclock beyond 4.2 all core, while most 3100s and 3300Xs can go beyond that because there's considerably less cores to work with.

Also, UserBenchmark's test can be somewhat useful for seeing if everything in your system is working poorly, normally, or optimally.

[☄️⁧⁧Sneakydude555]

Escorve님이 먼저 게시:

KeplersConjecture님이 먼저 게시:

AMD has been notorious over the years for its bad driver support. Just one of those things unfortunately.

That's really only for GPUs. Their chipset drivers are usually fine.

Funny how nobody talked about the issues that Comet Lake had when it launched earlier this year because Intel rushed it into production to try to get a lead on AMD. NVIDIA's had their fair share of issues too, which I saw with my 2080, but people seem to act like AMD is the only one with problems.

NightMAREZ_VVV님이 먼저 게시:

yep i really had a bunch of driver problems with my RX 470. thank God i have a 1660 now.

Guess i have to rely on the bios to make sure that the CPU is working fine. I plan to not overclock this cpu really. I just want to make sure my CPU is working fine after benchmarking stuff and in general usage

If there's no glaring issues, then it works. No reason to worry.

There's no point in manual overclocking a Ryzen 3000 CPU, they're pretty much pushed to the max out of the box. The more cores the chip has, the worse the OC potential, evident by the fact that most 3900Xs struggle to overclock beyond 4.2 all core, while most 3100s and 3300Xs can go beyond that because there's considerably less cores to work with.

Also, UserBenchmark's test can be somewhat useful for seeing if everything in your system is working poorly, normally, or optimally.

Ah okay thanks. I figured overclocking a 3600 isnt worth it. I acutally did use userbenchmark before when i first built this PC, the results said i could XMP my hyper x 16gb 2666mhz ram. I honestly didnt really care since it said everything was performing well. Ill redo the userbenchmark test, i didnt really thought of as system check

[r.linder]

NightMAREZ_VVV님이 먼저 게시:

Escorve님이 먼저 게시:

That's really only for GPUs. Their chipset drivers are usually fine.

Funny how nobody talked about the issues that Comet Lake had when it launched earlier this year because Intel rushed it into production to try to get a lead on AMD. NVIDIA's had their fair share of issues too, which I saw with my 2080, but people seem to act like AMD is the only one with problems.


If there's no glaring issues, then it works. No reason to worry.

There's no point in manual overclocking a Ryzen 3000 CPU, they're pretty much pushed to the max out of the box. The more cores the chip has, the worse the OC potential, evident by the fact that most 3900Xs struggle to overclock beyond 4.2 all core, while most 3100s and 3300Xs can go beyond that because there's considerably less cores to work with.

Also, UserBenchmark's test can be somewhat useful for seeing if everything in your system is working poorly, normally, or optimally.

Ah okay thanks. I figured overclocking a 3600 isnt worth it. I acutally did use userbenchmark before when i first built this PC, the results said i could XMP my hyper x 16gb 2666mhz ram. I honestly didnt really care since it said everything was performing well. Ill redo the userbenchmark test, i didnt really thought of as system check :SisterRam:

It kind of is a system check because it compares your score to other systems of the same specs.

Also, you should have 3200 MHz (CL14 or CL16 it doesn't really matter much) RAM because of the infinity fabric. It can make quite a difference in some cases.

[☄️⁧⁧Sneakydude555]

Escorve님이 먼저 게시:

NightMAREZ_VVV님이 먼저 게시:

Ah okay thanks. I figured overclocking a 3600 isnt worth it. I acutally did use userbenchmark before when i first built this PC, the results said i could XMP my hyper x 16gb 2666mhz ram. I honestly didnt really care since it said everything was performing well. Ill redo the userbenchmark test, i didnt really thought of as system check

It kind of is a system check because it compares your score to other systems of the same specs.

Also, you should have 3200 MHz (CL14 or CL16 it doesn't really matter much) RAM because of the infinity fabric. It can make quite a difference in some cases.

https://www.amazon.com/G-SKILL-TridentZ-DDR43200MHz-escritorio-F4-3200C16D-16GTZR/dp/B01MTDEYHU/ref=sr_1_10?dchild=1&keywords=16gb+ddr4+3200&link_code=qs&qid=1594633046&sourceid=Mozilla-search&sr=8-10&tag=mozilla-20

will this be fine?

[r.linder]

NightMAREZ_VVV님이 먼저 게시:

Escorve님이 먼저 게시:

It kind of is a system check because it compares your score to other systems of the same specs.

Also, you should have 3200 MHz (CL14 or CL16 it doesn't really matter much) RAM because of the infinity fabric. It can make quite a difference in some cases.

https://www.amazon.com/G-SKILL-TridentZ-DDR43200MHz-escritorio-F4-3200C16D-16GTZR/dp/B01MTDEYHU/ref=sr_1_10?dchild=1&keywords=16gb+ddr4+3200&link_code=qs&qid=1594633046&sourceid=Mozilla-search&sr=8-10&tag=mozilla-20

will this be fine? :Ksha_VII:

Yes, I've used that kit before.

[Bad 💀 Motha]

Prime95, PCMark, AIDA64, IntelBurnTest

Yes use all of them.

[Memes]

Escorve님이 먼저 게시:

NightMAREZ_VVV님이 먼저 게시:

https://www.amazon.com/G-SKILL-TridentZ-DDR43200MHz-escritorio-F4-3200C16D-16GTZR/dp/B01MTDEYHU/ref=sr_1_10?dchild=1&keywords=16gb+ddr4+3200&link_code=qs&qid=1594633046&sourceid=Mozilla-search&sr=8-10&tag=mozilla-20

will this be fine? :Ksha_VII:

Yes, I've used that kit before.

I'm gonna use the Ryzen 3600 for one of my build so should I go with the Corsair Vengeance LPX 3600mhz C18 or just go with the GSkill 3200mhz C16. Using 2x8GB of course

[r.linder]

Memes님이 먼저 게시:

Escorve님이 먼저 게시:

Yes, I've used that kit before.

I'm gonna use the Ryzen 3600 for one of my build so should I go with the Corsair Vengeance LPX 3600mhz C18 or just go with the GSkill 3200mhz C16. Using 2x8GB of course

3200 CL16 and 3600 CL18 have the same memory access speed, so there's not much of a difference aside from price.
Anything above 3200 yields little to no benefit in games. 3200 CL14 is 1~3% better than 3200 CL16, similar case with 3600 CL16.

Additionally, a lot of budget motherboards struggle to run 3600 CL16, or even anything above 3200 MHz in general. First generation AM4 often struggle even with 3200 MHz, with B350 even having issues with 3000 in some cases.

[Bad 💀 Motha]

Most boards won't support 3600 RAM. Better to look at GSKILL TridentZ 3200 CL14

3200mhz is fine on B450/X470
If you have B350/X370, stick to 3000mhz

[☄️⁧⁧Sneakydude555]

Bad 💀 Motha님이 먼저 게시:

Prime95, PCMark, AIDA64, IntelBurnTest

Yes use all of them.

isnt prime 95 dangerous to use though?

[r.linder]

NightMAREZ_VVV님이 먼저 게시:

Bad 💀 Motha님이 먼저 게시:

Prime95, PCMark, AIDA64, IntelBurnTest

Yes use all of them.

isnt prime 95 dangerous to use though?

No.
The CPU will force a shutdown if it gets hot enough to prevent damage to the CPU.
However, dangerous levels of LLC in BIOS can result in overshooting voltage to dangerous levels above 1.5v that can kill the CPU, but that's more user error messing with LLC settings than anything.