|
X370 Taichi, Goes Blank; Code '00' |
Post Reply 
|
Page <1 2345> |
| Author | |
Ivan_83 
Newbie 
Joined: 22 May 2017 Status: Offline Points: 85 |
 Post Options
 Thanks(0)
 Quote Reply
 Posted: 23 May 2017 at 1:46am |
|
I have no overclock.
I try 1,35V for CPU, this don't help. I try mem at 2133 and 1,35V - don't help too (for corsair and for Samsung. Samsung start and work OK at 2966 1,35V, 18-18-18-18-36). I have no crashes on high CPU load (prime95 = mprime - 2 hours - OK), most crashes happen on intensive video output (video playback, paint remote desktop). May be this is some how connected with network activity (like packet of death on some vendor + intel network chip), but some times I transfer many data and crashes not happen. Most video that I playback from network share. I will try to use different network card after next reboot. |
|
 |
|
|
Atan87
Newbie
Joined: 01 May 2017 Status: Offline Points: 25 |
Post Options
Thanks(0)
Quote Reply
Posted: 23 May 2017 at 12:49am |
|
|
|
Ivan_83
Newbie
Joined: 22 May 2017 Status: Offline Points: 85 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2017 at 9:54pm |
|
Screen goes black and I get "00" on the Dr Debug display, that happen when the PC is running after a while.
System can work up to 2-6 day before that happen. I unable to reproduce this by any actions in OS/software. As I remember, '00' happen most times on video playback. Last time I was working with xfreerdp with remote computer. No sound, no music, no video playback. May this not connected, but 1-2 days before boot loop code '00', video playback with tearing. Last time was no tearing on video playback, may be because I set Vsoc = 1.0V and SOC load line calibration = 3. On my first link another taichi user get '00' on windows setup, music playback and playing game. It may be quit difficult to RMA: 14 days are left and local reseller may take mobo for tests and because '00' code difficult to reproduce it can deny RMA or I will wait for long time for approve. ======== I suggest that boot loop instead reboot happen because some internal CPU registers or devices (inside CPU) contain incorrect values. (May be some one forget set msr registers to protect some internal/system registers/mem regions during bios init, then OS try to use it - some CPU critical data may be damaged, then system try start but bios initial code does not init this part at all or fail to init.) May be something wrong with watchdog inside CPU. Is it possible that BIOS programmers forget init watchdog on BIOS start, it initialized by some random crap and after 2-6 day it fire reboot? (Me and man with linux have no driver that reinit watchdog. User from first link and topic starter may be not setup all drivers for all devices and windows dont re init watch dog to. One of my theory.) I try load watch dog driver but get: amdsbwd0: <AMD FCH Rev 41h+ Watchdog Timer> at iomem 0xfed80b00-0xfed80b03,0xfed80b04-0xfed80b07 on isa0 amdsbwd0: watchdog hardware is disabled device_attach: amdsbwd0 attach returned 6 I cant patch driver because I have no BIOS and Kernel Developer's Guide for AMD 17h, I request it and waiting: https://community.amd.com/thread/213584 Also I have no drivers for: none0@pci0:0:0:2: class=0x080600 card=0x14511022 chip=0x14511022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' class = base peripheral subclass = IOMMU cap 0f[40] = unknown cap 05[64] = MSI supports 4 messages, 64 bit cap 08[74] = HT MSI fixed address window enabled at 0xfee00000 none1@pci0:0:20:0: class=0x0c0500 card=0xffff1849 chip=0x790b1022 rev=0x59 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'FCH SMBus Controller' class = serial bus subclass = SMBus none2@pci0:17:0:0: class=0x130000 card=0x145a1022 chip=0x145a1022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' cap 09[48] = vendor (length 8) cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 10[64] = PCI-Express 2 endpoint max data 256(256) RO NS link x16(x16) speed 8.0(8.0) ASPM disabled(L0s/L1) ecap 000b[100] = Vendor 1 ID 1 ecap 0019[270] = PCIe Sec 1 lane errors 0 none3@pci0:17:0:2: class=0x108000 card=0x14561022 chip=0x14561022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' class = encrypt/decrypt bar [18] = type Memory, range 32, base 0xfe600000, size 1048576, enabled bar [24] = type Memory, range 32, base 0xfe700000, size 8192, enabled cap 09[48] = vendor (length 8) cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 10[64] = PCI-Express 2 endpoint max data 256(256) RO NS link x16(x16) speed 8.0(8.0) ASPM disabled(L0s/L1) cap 05[a0] = MSI supports 2 messages, 64 bit cap 11[c0] = MSI-X supports 2 messages Table in map 0x24[0x0], PBA in map 0x24[0x1000] ecap 000b[100] = Vendor 1 ID 1 none4@pci0:18:0:0: class=0x130000 card=0x14551022 chip=0x14551022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' cap 09[48] = vendor (length 8) cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 10[64] = PCI-Express 2 endpoint max data 256(256) RO NS link x16(x16) speed 8.0(8.0) ASPM disabled(L0s/L1) ecap 000b[100] = Vendor 1 ID 1 ecap 0019[270] = PCIe Sec 1 lane errors 0 Edited by Ivan_83 - 22 May 2017 at 10:53pm |
|
|
|
|
parsec
Moderator Group 
Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2017 at 9:02pm |
Thank you, now I understand what is happening much better. The only thing I'm not sure about is when the screen goes black and you get "00" on the Dr Debug display. Does that happen when the PC is running after a while? Or does it happen when you first power on the PC? This is a very strange problem. Since you used a different PSU, memory, SSD, and video card, they should not be the problem. If the only thing that would fix it (temporarily) would be to power off - on the PSU, then I would say it was something wrong with the mother board. But if pressing the Reset button also lets the PC work fine afterwards, that does not make sense, given the "00" code. But I can't think of any other reason why the PC should act this way. I have a different ASRock Ryzen board and CPU, and I have never had this problem. You can try replacing the board, that is all that is left to do besides a different CPU. |
|
|
|
|
|
|
Ivan_83
Newbie
Joined: 22 May 2017 Status: Offline Points: 85 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2017 at 4:01pm |
|
1. After power on PC start OK.
Then it works OK 2-6 days. Then screen goes black and Dr.Debug show '00'. If I press reset button or power off-on PSU - PC start OK and I continue work next 2-6 days. 2. '00' code does not happen after power on or reset button, so system start/work OK and I can update BIOS, boot to OS...etc... I have no alternative CPU and MOBO for AM4. (for next few weeks) All (at most) other hardware have alternative that I try. 3. Samsung memory come after Gigabyte mobo RMA. I think CPU is OK, because: - CPU start and work OK up to 2-6 days (even if I run prime95 (mprime) few hours) - there is other peoples with x370 taichi with same problem - Gigabyte only overheat VRM and stop work until temperature goes normal, this should not damage CPU, IMHO. ====== I build test machine with 1700X, Corsair mem and gigabyte mobo. Gigabyte mobo overheat in test time. I RMA gigabyte mobo and get taichi mobo. I test taichi for overheat - test passed, no other issues found (but I do not test long uptime) and then I move 1700x, taichi and Corsair mem to my work system (replace 775 mobo+CPU+ddr3 that work OK while 5+ years). All was OK next few days then screen goes black and I see '00' error code. I press reset and system rebooted, I continue work... Samsung memory come, I remove Corsair and try work only with samsung - not help with '00'. I try replace PSU, video card, tune bios - not help. Intel SSD come and replace SP S60 SSD. I continue playing with bios settings...without success. So I continue press reset every 2-6 days to continue. |
|
|
|
|
parsec
Moderator Group
Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2017 at 9:53am |
|
Your description is very confusing, I don't know what the current status of the PC is at all. First you said this: 2-6 days uptime and then black screen and boot loop with code: '00' Dr Debug code of "00" means a bad CPU. The board won't POST or do anything, because the CPU is not working for some reason, or is dead. That means the PC will not start at all, you cannot get into the UEFI/BIOS, nothing on the screen at all, so the PC cannot be used. Next you said: First I update to 1.60 from FreeDOS. 2.00, 2.20, 2.30 from bios flash tool - not help. So after you had the "00" POST code and a black screen dead PC, you were able to start the PC and boot into a DOS bootable USB flash drive to update to 1.60? You said you used Instant Flash to try three UEFI/BIOS versions? How can you do that if you get a "00" POST code and the PC does not work at all? Sorry I don't understand how this is possible. After this, you said you tried alternate hardware to try to fix the "00" problem, that you then listed. That is different hardware, a new 1700X, new memory, new mother board? This alternate hardware has the same "00" problem? I'm sorry but I don't understand what you did, or if you used new hardware or something else. Finally you said: 1700X and Corsair CMK16GX4M2B3466C16 works before with Gigabyte gamming 3 but there was VRM overheat problem and I cant be 100% sure that CPU and mem OK, because no tests with long uptimes done. You are not sure if the CPU and memory you used in a Gigabyte board was not damaged before you put it in the X370 Taichi board. With the possibility of the CPU or memory being damaged on the old board, and since I do not understand the sequence of events of what you did with the X370 Taichi board, I can't suggest anything. Is the "00" POST code the only code you get on the Dr Debug display? Please describe what happened since you first used the Taichi board with the CPU and memory from the other Ryzen build. Please try to make your description better, I described what I don't understand in my comments above. |
|
|
|
|
|
|
|
Ivan_83
Newbie
Joined: 22 May 2017 Status: Offline Points: 85 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2017 at 7:36am |
|
I have same problem.
2-6 days uptime and then black screen and boot loop with code: '00' Video: https://www.dropbox.com/sh/uyj88uj1k9wa8cg/AAClalavS1r8bp_12PB9f-Tka/Crash%20Loop.mp4?dl=0 (by NewRigTime from link 1) Also other peoples too: 1. http://www.tomshardware.co.uk/answers/id-3383713/asrock-x370-taichi-amd-ryzen-1800x-post-build-crashing-issues-error-codes.html (He was on this forum but after RMA taichi and get Fatality pro) 2. https://www.servethehome.com/amd-ryzen-with-ubuntu-here-is-what-you-have-to-do-to-fix-constant-crashes/#comment-460405 3. https://forums.overclockers.co.uk/threads/the-asrock-thread-support-feedback-etc.18760683/page-26#post-30785355 Also '00' code happen on: ASRock X370 GAMING k4 1. https://www.hardwareluxx.de/community/f139/amd-ryzen-zen-summit-ridge-socket-am4-oc-thread-1159257-28.html#post25475030 2. https://translate.google.com/translate?hl=en&sl=ja&tl=en&u=http%3A%2F%2Fanago.2ch.sc%2Ftest%2Fread.cgi%2Fjisaku%2F1489712334%2F (use find, sorry no post direct link) May be this connected some how with taichi. ===================================== First I update to 1.60 from FreeDOS. 2.00, 2.20, 2.30 from bios flash tool - not help. My config and alternate h/w that I try to use to fix '00' boot loop: CPU: 1700X (no overclock, try 1.2, 1,35 V, load line calibration 3) MOBO: x370 taichi with removed wifi/Bluetooth adapter (radio in bios on/off - no affect to '00') MEM: Corsair CMK16GX4M2B3466C16 (2x8 Gb) and Samsung M378A2K43BB1-CPB (1x16 Gb) (try 1x8 Gb @ 2133 1.35V, try 1x16 Gb @ 2133 1.35V, memtest from boot flash show that all modules OK, now 2+1=32Gb @ 1,35v 16-18-18-18-36) PSU: corsair RM550x / FSP 600-80GLN VIDEO: Asus GT610 / Asus GT730 / Radeon HD6450 HDD: ssd SP S60 (60 GB) / INTEL SSDSC2BW120H6 120 Gb + HDD SAMSUNG HD204UI 2Tb (sata2, never try without it) ODD: ASUS DRW-1814BLT 1.14, it connected but not used (sata1, never try without it) 3,5 card reader USB 3.0 SEMA (Samsung) (never try without it) OS: FreeBSD 11 x64, but this not relevant, users have same problem with linux and windows. New H/W that works only with X370 taichi: - Samsung M378A2K43BB1-CPB - corsair RM550x - Asus GT730 - INTEL SSDSC2BW120H6 120 Gb 1700X and Corsair CMK16GX4M2B3466C16 works before with Gigabyte gamming 3 but there was VRM overheat problem and I cant be 100% sure that CPU and mem OK, because no tests with long uptimes done. I try load defaults, tune various bios settings - wont help. Try on/off: iommu, svm, c6, cool-n-quiet..... Try Vsoc 1.0V and SOC load line calibration = 3... What I can do/try before RMA? (I have two weeks+- to be your tester) Please help! Edited by Ivan_83 - 22 May 2017 at 7:47am |
|
|
|
|
mgrandy@hotmail.co.u
Newbie
Joined: 20 Feb 2016 Location: uk Status: Offline Points: 65 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 Mar 2017 at 3:32am |
|
ok because you cannot get in to windows try wiping the hdd on another pc windows 10 is usually a nightmare to remove once put on start from a clean everything and go from there or try entering safe mode usually spamming all f5-10 works although i think its f8 for safe mode it should default to stock windows settings
personally what i done was use a windows 7 disk to wipe the hdd as it uses an older utilty then reinstalled windows 10 may also work for you. this way you no dyam sure windows 10 has had nothing to do with wiping the drive and keeping any of your old settings here what im getting so far bios settings run fine along with dos and updated fine so theres no issue with your cpu or board. along with the cpu as it manage to complete the full flash no "00" code right? so in this case i would remove windows 10 as it seems its still trying to load your UEFI settings for the clocks. make sure they are fully removed Edited by mgrandy@hotmail.co.u - 13 Mar 2017 at 4:12am |
|
|
fx 9370 asrock, fatal1ty 970 performance 3.1, NZXT phantom f-atx, AeroCool Integrator 850W, Corsair Hydro Series H100
|
|
|
|
|
Hectic
Newbie
Joined: 12 Mar 2017 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 Mar 2017 at 3:28am |
|
OK, yeah I was doing the DOS update wrong. I was in the right directory, I just wasn't actually typing in the name of file to execute properly. I was typing in the FULL name like you see it in Windows i.e. "X370TC154.exe" when instead I should (and did) type "X370TC1~.exe" like the way it shows it in DOS when I looked at the directory. It executed, updated the bios no problem. Thing is, THE PROBLEM IS STILL HAPPENING!!! Tried to install Windows, as soon as it gives that little progress bar on the bottom saying "Readying Windows Files" (or whatever it says), the screen goes black and I get the flashing '00's!
The bios are updated, everything is back to their defaults in there, everything is plugged in and working properly...I don't get it, I'm at my wits end! I already set up the RMA's to Newegg and will await a new processor and go for the Gigabyte MB. Just have to wait a week or 2. I've used an ASRock MB before and it was pretty solid as I remember it, but this experience has just soured me on trusting them.
|
|
|
|
|
mgrandy@hotmail.co.u
Newbie
Joined: 20 Feb 2016 Location: uk Status: Offline Points: 65 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 Mar 2017 at 2:36am |
|
yes you are not even locating the file in dos that is why it is cumming up with invalid command
are you in the right directory? can you access your drive ?try to cd(change directory) to the drive letter using mdos commands before trying to run the file. after you enter the command to load you will/should be presented with a UI of sorts like an old fashioned windows screen from there it will ask you. are you sure you want to flash and have read the terms and conditions etc which drive would you like to flash. ill do a guide in next few days with screens to follow soon as my psu comes dont want to risk my fatal1ty 970 on a 500w psu im pushing it as is. any new boards will take time for bios files usually the mdos version is out first hears a link to a guide on the giga byte http://www.gigabyte.com/webpage/20/images/flashbios_dos.pdf skip to section 4 page 10 read the note and go from there. see the flash utility (UI) im taking about just underneath Warning when you get to the UI and if it stops at any point while performing the flash, leave it!!! if it takes 20 mins or 1 hour still leave it. usually when it finds a bad section of memory it will stop for awhile this is normal just wait it is very rare for a flash to fail unless powered off or loss of power or to much bad memory. been new you wont have this issue. all memory blocks will be checked at the factory before shipping if a certain amount fail they would not release the board. let me know how ya get on "Yes, I've been able to keep the bios/settings open indefinitely" leads me to believe the problem is with windows 10 pushing clocks or doing something it aint ment too Edited by mgrandy@hotmail.co.u - 13 Mar 2017 at 2:58am |
|
|
fx 9370 asrock, fatal1ty 970 performance 3.1, NZXT phantom f-atx, AeroCool Integrator 850W, Corsair Hydro Series H100
|
|
|
|
|
Post Reply
|
Page <1 2345> |
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
Ivan_83 wrote: