I totally did not know that but makes sense now that I think about it. QC codes are surprisingly hardy so it would probably decode properly after using an upscaler.
I bough the last week a Ryzen 1700 in pccomponentes (Spain)
with Ubuntu 17.10 Beta 2
i compile Python 3.6 (the kill-ryzen dosent work (fail mount ramdisk) )
12 times whithout segmentation fault (only other warnings) problem using this:
first do ./configure
#!/bin/bash
export LANG=C
if [ $# -ge 1 ] ; then
CONCURRENCY=$1
else
CONCURRENCY=16
fi
for ((i=0;12;i++)) ; do
echo 'Start test $i'
if make -j$CONCURRENCY >/dev/null 2>>log.txt ; then
echo "$i: $(date): OK" >>log.txt
else
echo "$i: $(date): NG" >>log.txt
fi
dmesg >dmesg.txt
make clean >/dev/null 2>>log.txt
done
My CPU is 1717SUS
DMI: Gigabyte Technology Co., Ltd. AB350M-Gaming 3/AB350M-Gaming 3-CF, BIOS F7a 09/15/2017
model : 1
model name : AMD Ryzen 7 1700 Eight-Core Processor
stepping : 1
microcode : 0x8001129
Just use a live distro from USB. Manjaro XFCE runs perfectly fine these days and I just needed to build blender to trigger the segfault. Also ubuntu 17.10 is out so that might be another option for a live stick.
Now we can see the error more clearly.
Iām starting my RMA. Waiting for their respects.
I wanted to know who did it, if it was necessary to send the CPU before receiving the new copy. I can not stop.
In my case, they said they would send the replacement after verifying the defective CPU was shipped, but it took several weeks before I got mine back (to be fair this about the time Irma happened, and they shipped it from Canada. The place they had me send the defective CPU to was in Miami).
Their customer service seems pretty decent, I would at least ask if they will do an advanced RMA.
Also, in your first email, to speed up the process, go ahead and include this info (it may take a day or two for them to reply in my experience):
Processor model
Make and model of motherboard
Motherboard BIOS version
Make and model of RAM
Make and model of power supply
CPU VCORE, SOC and RAM voltages (screenshot/picture of BIOS settings preferred)
Picture of the interior of the case, to rule out heating issues
This is the correct advice. Thanks for posting that for others.
In my case it was also shipped out of Canada at the same time as Irma was happening.
On the box the source address read āATi Technologies LLCā of all things
Just as a heads upā¦ Amazon is still selling impacted CPUās. Ordered an 1800x same day shipping (couldnāt resist the new $350 price, received an 1800X UA1721PGT with segfault issuesā¦
model : 1
model name : AMD Ryzen 7 1700 Eight-Core Processor
stepping : 1
microcode : 0x8001129
EDIT:
oh ya and
dmesg | grep -e 'DMI.*BIOSā
gave me this.
[ 0.000000] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.10 08/25/2017
Hmmn, now that I think about it. When I got my ryzen 1700 I was rendering unreal editor 4. It would crash and shut down the editor at random timesā¦ It did it in my windows boot a couple timesā¦ I actually used that as a test frame to set, voltage to clock speed. I thought I was clocking too much. And now I wonder.
Thatās a difficult to debug & noisy test case.
Because Unreal ED can be buggy at the best of times and introduces too many variable that one canāt control for.
As updateā¦ Returned the CPU to Amazon and ordered a replacement from Newegg. Exact same production facility and date codeā¦ It seems as though AMD is trying to offload these old production chips to some of the bigger retailers.
Wish Iād known this before I ordered yesterday, heh.
I got my 1700 today and itās a Week 19 chip. So close, yet so far. As predicted, Amazon said they canāt really do anything other than let me play the Replacement Game, so Iāll see if AMD can help me out before playing that game.
But have you tested it to confirm the segfault bug?
Donāt just return it because of the manufacture date. I have seen 2 Ryzen 7ās and one Ryzen 5 now which are early chips without the bug. So its not always a 100% sure thing.
Iād rather not open it up and deal with it since I already have a āworkingā 1600 up and running in my server. Iād rather let AMD test and return if itās fine. No point in downtime if Iād just have to put the 1600 back in anyway.
Edit: āworkingā in quotes because the 1600 actually has faulty L3 cacheā¦but thatās another story!