2) P3 pin 6 - P3 pin 7 12 VDC (check both relay and display board) If one the above voltages not present check connection to P3 connector. MS were no help there.Īnother in windows running fine but no real load. 1) P3 pin 4 - P3 pin 5 5 VDC (check both relay and display board). One PCIE card (DVICO DUAL DIGITAL PCIE) is not even detected by this M/B. NOTE: all BIOS defaults, no overclocking, RAM (GSKILL RipjawsV 2666 but tried the others too). Since the proddate is post 1725 I shouldn’t be seeing the kill ryzen issues according to all the advice I’ve seen posted. Lots of building Qt will make this happen too. When it starts the M/B NIC starts behaving badly. This is indicative of the RETIQ issue mentioned I believe. These don’t happen much until things are under load. I notice I get more lines like Sep 14 08:02:50 kernel: usb 1-5: dvb_usb_af9015: command failed=2 I also run mythtv on this server which does a lot of IO to PCIE and USB for DVB EIT scanning. These fail with either traps or segfault (varies). 4 others progressively fail and is stable to 2h at 11 threads running under kill-ryzen. Kill-ryzen.sh fails first time after approx 82s.
Make: *** Error 2ĭMI: Micro-Star International Co., Ltd MS-7A34/B350 PC MATE(MS-7A34), BIOS A.60 Make: Leaving directory '/mnt/ramdisk/workdir/buildloop.d/loop-15' yesĬonfigure: error: uint64_t or int64_t not found I’m not certain what caused the first gp fault, but all the consecutive build failures where due to this: checking for unsigned long long int. Aug 08 12:57:24 jupiter kernel: perf: interrupt took too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 79800 amdcommunity, UA1725SUS, SEGV OK, RMA ReplacementĪfter about 3 hours I got this: Aug 08 12:51:13 jupiter kernel: traps: as general protection ip:7f10bcd4428a sp:7ffd14de3248 error:0 in libc-2.25.so amdcommunity, UA1725SUS, R7-1700, SEGV OK, RMA Replacement Reported By, Build Date, Type, Status, Notes
Update (25th August 2017) Google Sheets doc of affected & RMA chip UA numbers RYZEN SEGV DATA Week 6 of 2017 means it was produced anywhere between February 6 to February 12.
The first being the year the CPU was produced =(2017) and the week = (Week 6). The Batch number consists of the UA and then a two part number of 2 digits each. The text you see is explained as follows: SKU: YD1700BBM88AE Note This requires taking off your CPU cooler, I currently don’t know of another way to gain this information.
This is a short guide on how to read your CPU’s batch number. Model name : AMD Ryzen 7 1700X Eight-Core ProcessorĮdit Reading your production date/batch number Here’s my example: ASRock X370 Gaming K4, BIOS P3.00 How to get BIOS Version dmesg | grep -e 'DMI.*BIOS' How to get your CPU version and microcode grep 'stepping\|model\|microcode' /proc/cpuinfo | head -4 Post the output of following command below and state your Motherboard and BIOS version: Since not everyone has a Reddit account, I’m recreating this post here: