*segment faults*
>>61909482
S O P A
>>61909482
http://phoronix.com/scan.php?page=news_item&px=Ryzen-Segv-Response
>>61909534
POO
>>61909482
Superglueâ„¢
>>61909544
>Ryzen customers believe to be affected by the problem can contact AMD Customer Care. Some of those who have contacted customer care about the segmentation faults have in turn been affected by thermal, power, or other problems,
Oh amd, never change.
>>61909482
*dereferences your pointer*
>>61909534
U M A
>>61909549
Fuck off
>>61911671
the designated street beckons
>>61909482
MUH WOODSCREWS
MUH 1.7%
MUH JEW SEMEN
MUH 100 DEGREES CELSIUS
>>61911698
MUH FERMI HOUSEFIRES
MUH 3.5GB
>>61911698
>amdrone in PTSD after vega release
It was already fixed though. Only early batches were affected, and it was probably because the default SOC voltage was too low for them (a common problem I saw in regards to stability during the launch in OCN).
>>61911698
MUH NETBURST NUCLEAR FIRE
MUH FDIV BUG
MUH 1.15Ghz PIII FIASCO
Throwing some old ammo to fight the shills.
>Intel is so desesperate that they started seeing amd as competition
lmao
>>61911716
>it was probably because the default SOC voltage was too low
I can second this. My Ryzen had a default SOC of 0.8V or something like that. Cranking that up to 1.175V fixes literally everything about OCing the CPU and RAM.
now rocking it at 3.9ghz while RAMs work at 3200mhz CL14 1.375V