I'm having a really weird specific issue with my new Ryzen

>>61265310
Intel CPUs don't have this problem. Just saying.

File: bandicam 2017-07-07 16-07-45-273.jpg (477KB, 2342x1441px) Image search: [Google]

477KB, 2342x1441px

Windows sees that I've set the multiplier manually, but CPU-z says my multiplier is 15.5, and if I run any test, it is definitely clocked down that low.

File: bandicam 2017-07-07 16-54-11-175.jpg (111KB, 413x414px) Image search: [Google]

111KB, 413x414px

I seem to have made some progress, though whats happening is still kind of beyond me. I lowered the CPU voltage to 1.3v flat, and the CPU is telling me the correct multiplier now, whereas I was putting it at 1.36v in an attempt to try seeing if I could get a stable 3.9 and then start dropping the vcore until I started crashing, instead it just dropped my multiplier without giving me a reason.

File: intelBugList.png (66KB, 1274x537px) Image search: [Google]

66KB, 1274x537px

>>61265397
I don't understand what you're saying.

File: vvbure.png (595KB, 773x823px) Image search: [Google]

595KB, 773x823px

>>61265397
What are you saying?

File: NoComPrendooo.png (635KB, 662x685px) Image search: [Google]

635KB, 662x685px

>>61265397
whats happening ing ing ing ing ing

It appears to be something about the jump from 1.3250v to 1.3375v (it forces me to do .0125v jumps at a time) causing the multiplier issue, but with 10 minutes of running prime95 at 1.3250v @ 3.9ghz i appear stable, 3.95ghz crashed immediately, i guess msi fucked something up after the new AGESA(?) update that's doing something if you try to go over 1.33v on their b350 arctic tomahawk?

>>61265310
>MSI tomahawk arctic b350
found your problem
get an asrock board

>>61266579
Shit advice. MSI's B350 boards are better than ASCock's, especially in terms of VRM quality.

This prob had something to do with ryzen p states

>>61265940
>>61265972
>Lib
>Free
Boohoo your poorfag shit doesnt work
>>61266579
asrock b350 pro has no SoC voltage or LLC settings.

Try hwmon to check the clocks

>>61266925
>blames the software for the cpu bug

lol, good one

>>61265402
>>61265310
Same issue here on my Ryzen 1600X with a msi x370 pro sli i read that it's a bug in the BIOS and will/should be fixed in future BIOS updates

>>61266803
>msi
>good VRMs
i kek'd

>>61265397
http://www.overclock.net/t/1561131/5960x-dead

Killing your cpu is better right

>>61267331
It's a matter of fact that MSI's B350 boards have the best VRM setup.

https://www.youtube.com/watch?v=ZGrxhf_xZWI

No amount of you shitposting will change that.

>>61265310
>>61265908
>>61266173

OP here, I went to the forums and asked about it and was told it is currently an issue in the latest release, sadly there aren't any beta bios's above the version currently available so either I lose the ability to run my ram above 2666 and have the chance to try and see if the extra voltage gets me to 4ghz, or i sit tight on my 3.9ghz and 3600mhz ram speed and hope the next update resolves the voltage issue.

>>61265310
I have the same issue with my MSI x370 SLI plus. Some other manufacturer boards even have this 1.55 GHz issue. The only way I could fix it was reverting to the SLI plus V1.31 BIOS (it is the 1.0.0.4 AGESA update, so I'd try your 1.0.0.4 update specific BIOS) It's a shame since the newest 1.34 BIOS allows me XMP 3200 MHz RAM no problem at all, but with the v1.31 all I can get is 2667 at 14, 14, 14, 30 CL timings. Some people have reported that using offset vcore gets rid of the issue but my board doesn't allow offset vcore.