Is it possible my new 5950x system hardware has already degraded?

Ok i just finished 7 hours of memtest, at 64gb i only had time to get 1 pass, but yeah no errors.
Running aida64 cache benchmark yeilds instant whea in event log with whatever setting i try. The WHEA errors are just a lot more rare when i set the cpu to a static multipiler.

What i notice is that whenever i set the cpu to static multipiler the CPU VCORE also becomes pretty much static, sitting around 1.1v all the time.
Without a static multipiler and core boost of the algoritm seems to still "take care" of the vcore voltage but it never goes to 1.5v, with core boosts of it maxes out at 1.032v.

The thing is, the minimum voltage is what makes me think this is the issue, the minimum voltage for vcore is 0.192v? This sounds like it could be the issue, the "algoritm" chokes the cpu from power and it generates these issues in the eventlog, should i set the vcore to 1.2v?

p9M8k26.png

I also found this video: https://www.youtube.com/watch?v=tobzYO5pSJs where the guy explains his cpu was working at first, then suddenly nothing works, it went so far for him that his cpu won't even post windows anymore, he swaps the cpu with an old one and everything works fine, so chances are these 5950x are prone to break as these issues seem very common at this point.

It blows my mind that all the reviewers NEVER talked about this, yet whenever the cpus come out all hell breaks loose, is it safe to say that every single reviewer in the world gets a special type of hardware sent to them and whenever the masses get to buy the hardware we get something else? I just can't seem to understand how this goes under the radar, it's a massive issue and no one with a following is talking about it?

Anyways if you have any ideas what i can try next i'm all ears, i'm thinking once again i may have to RMA my cpu.
 
I just found out my ryzen 2600 is compatable with the motherboard (x570 aorus extreme), i have this in my backup server. Is it worth it to disassemble it just to try the stuff with another cpu? I don't know if i want to, the backup server is operating daily for my important files, i may as well just buy another cheap cpu tbh
 
pc-guy said:
What are the volts doing? As I said I don’t trust motherboard’s auto volts and also PLL is important.
Click to expand...

I have not touched PLL i have to look and see if i can find it in the bios somewhere, what should i be setting it at?

I am right now running with:
set vdram to 1.4
Vsoc to 1.05
V IOD and V ccd to 1.0v
V DDP to 0.95.

At 2666mhz/1333FLCK and before i even get into windows the eventviewer fills up with WHEA errors, no difference with or without these voltage settings, no difference if i have memory in xmp 3600mhz/1800flck or this slow stuff.
 
iraffe2 said:
I have not touched PLL i have to look and see if i can find it in the bios somewhere, what should i be setting it at?

I am right now running with:
set vdram to 1.4
Vsoc to 1.05
V IOD and V ccd to 1.0v
V DDP to 0.95.

At 2666mhz/1333FLCK and before i even get into windows the eventviewer fills up with WHEA errors, no difference with or without these voltage settings, no difference if i have memory in xmp 3600mhz/1800flck or this slow stuff.
Click to expand...
PLL should in the digipower menu. Usually found in the same area where you set core volts and core multipliers but it is a sub menu. It should be set it L2/3 probably on auto atm.

also enable Gear Down Mode as you are running 4x16GB.
 
So added to my voltages above:
VORE manually set to 1.2v
CPU Vore Loadline Calibration > TURBO
Vcore SOC Loadline Calibration > TURBO
CPU VCORE Protetion > 400MV (max)
CPU VCORE SOC Protetion > 400MV (Max)
PWM Phase Control > Extreme Performance (Max)

Running everything at stock, 3400mhz, no core boosts enabled, memory at default 2666mhz loose timings no XMP and flck 1333.

Full of WHEA errors.

Literally none of these voltages make any difference to anything, voltages do get higher tho, now cpu is idling at 1.2v so i know these settings have effect, memory is at 1.416 v, but considering it doesn't make a single difference it seems stupid to continue to play around with voltages, its clearly not the problem.
 
pc-guy said:
PLL should in the digipower menu. Usually found in the same area where you set core volts and core multipliers but it is a sub menu. It should be set it L2/3 probably on auto atm.

also enable Gear Down Mode as you are running 4x16GB.
Click to expand...

Can't for the life of me find this PLL thing anywhere in the bios, perhaps its called something else?

I think we have something finally, Gear down mode Enabled in 3 different places in bios, running AIDA64 benchmark right now and it previously instantly resulted in whea errors, now i actually have none, so i believe you found the issue.

How Gear down mode changed must have been when i tried bios f31 and then went back to f30, gear down mode has always been set to auto but i guess auto changed somehow?
 
GDM auto means it is off potentially by default. Anyway have a google for PLL for your motherboard. I only really know my way around MSI and ASUS bios. I avoid ASRock and Gigabyte boards - the former is too basic the latter is too buggy and unreliable.

ASUS got terrible customer services. So I won’t be getting ASUS products anytime soon. It’s a shame cos I like their boards. Better features and cheaper than MSI.
 
MrRockliffe said:
A note on your PSU - I wouldn’t be confident that it’s enough to handle the sudden current spikes that the 3xxx series exhibits under load. If you find your PSU switching off under sustained GPU and CPU load you’ll know the issue :)
Click to expand...

Really? what kind of PSU would you recommend?
 
so gear down mode definitely made it better but i still cannot run my old spec of
3600cl16/1800 my guess is that any of these 40+ memory tweak settings that previously were auto, and is still auto was modified by one or another bios update and that's what causing the issue, one would hope the xmp profile would set those but it doesn't from what i can tell.... any idea what more mem setting that is really important? I read something about ProcOCT what shoult that setting be?

EDIT:

Not sure what to tell you guys, gear down mode fixed the problem, so i started doing some work, and suddenly all the whea errors are back, i didn't change anything lol, ok i officially give up on this rigg, ill just wait until it completely fails so i can rma the thing, wtf is this garbage, its either the trash gigabyte bioses making changes as we go, or the cpu is broken or a little of both, it seems to be far to finicky to be worth spending anymore time on as nothing makes sense anymore
 
Last edited:
It seems many people with 5950x and 5900x cpus are suffering these problems with gigabyte and asus motherboards. Though some report the latest 3003 bios fixes these issues. OC.net has a long thread about this issue. People just seeing crashes to desktop while idle. Indeed quite frustrating esp since reviewers NEVER mentioned this. Some people tried EVERY gigabyte bios with no change. The only thing that works so far is turning off Fmax or dialing back the cpu. Fortunately, if you use your machine for gaming at high resolutions, the bottleneck is the gpu so you wont really see an adverse effect dialing down the cpu till this issue is resolved. Your hardware is top notch and your psu is even good enough for a 3090 so the only thing you can do is rma the cpu if you dont want to wait till gigabyte addresses the bios.
 
If it was me I'd RMA, there's something strange going on with some of these CPUs.

I had a 5950x with the exact same issues directly swapped with a 100% stable 3900x. Like you, the only way to make it stable was disabling core performance boost. Swapped out for another 5950x and no issues since, same bios same everything.
 
Look just get your system into windows and set things as I explained and do those tests. You have 64GB ram there is no way you could have ran memtest86 on 3200 MHz and 3400MHz and 3600MHz and tested 3600MHz at XMP timings in 24hrs let alone Aida64 test. So you are running your system with errors in ram.

i have 32GB ram each memtest86 4 pass tests takes 5hrs so yours will take a lot longer. Don’t take any short cuts just do it properly otherwise you are in a world of hurt.

I cant freaking stress this more. Test and freaking test your damn ram. Like it is the last thing that works. Memtest86 the crap out of it. 4 passes and be freaking damn patient and at the end of it you will be rewarded for your efforts.
 
Last edited:
Not sure what to tell you guys, gear down mode fixed the problem, so i started doing some work, and suddenly all the whea errors are back, i didn't change anything lol, ok i officially give up on this rigg, ill just wait until it completely fails so i can rma the thing, wtf is this garbage, its either the trash gigabyte bioses making changes as we go, or the cpu is broken or a little of both, it seems to be far to finicky to be worth spending anymore time on as nothing makes sense anymore
pc-guy said:
Look just get your system into windows and set things as I explained and do those tests. You have 64GB ram there is no way you could have ran memtest86 on 3200 MHz and 3400MHz and 3600MHz and tested 3600MHz at XMP timings in 24hrs let alone Aida64 test. So you are running your system with errors in ram.

i have 32GB ram each memtest86 4 pass tests takes 5hrs so yours will take a lot longer. Don’t take any short cuts just do it properly otherwise you are in a world of hurt.

I cant freaking stress this more. Test and freaking test your damn ram. Like it is the last thing that works. Memtest86 the crap out of it. 4 passes and be freaking damn patient and at the end of it you will be rewarded for your efforts.
Click to expand...

Hmm i ran 2 passes of memtest86, i looked and it took around 4hours to make 1 pass, what would be wrong? I am now running memtest86 at 3600mhz/1800flck timing 16-18-18-36 with no stability issues, i chose to ignore those whea errors and suddenly they just went away out of nowhere. Again my WHEA error are ID 10,11 which doesn't seem to have any stability impact on the system and it's probably just a random luck i didn't see them earlier as they came from nowhere and now has disappeared out of nowhere.

Is there any special setting in memtest86 that i need to configure? I've just made it on a usb stick and once you boot on it the tests starts automatically so i haven't touched anything. It does seem strange that 64gb of ram would make 1 pass in 4 hours if it takes your 32gb 5 hours to make 1 pass.
 
No special settings just let the test run through 4passes.

If it all goes through then it is fine. You can move on from it.

is your windows a fresh install?

each pass on my 32GB is 1hr and 45min 4 passes is exactly 7hrs. I leave it overnight.
 
pc-guy said:
No special settings just let the test run through 4passes.

If it all goes through then it is fine. You can move on from it.

is your windows a fresh install?

each pass on my 32GB is 1hr and 45min 4 passes is exactly 7hrs. I leave it overnight.
Click to expand...
Oh i read your original post wrong, yeah that seems about the same, i ran memtest tonight at 3600mhz 16-18-18-19-36/1800flck for around 8.5 hours and it had made 2 passes no errors.

I am ignoring the WHEA errors for now, they are coming and going at complete random, right now i don't have them anymore and im back at 3600mhz/1800flck. They have never lead to my system crashing either so i believe WHEA ID 10 and 11 is not nearly as bad at 19 which seem to lead to hard crashing and reboots.
 
Check chipset drivers and make sure all your drivers are upto date.

if viable do a windows reset.

also post in the windows section of the forum to see if anyone got any idea what these WHEA errors are and if they mean anything.

good luck.
 
You must log in or register to reply here.
Back
Top Bottom