X370 Taichi, Goes Blank; Code '00'

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

 Ivan_83 wrote:

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

So a simple PSU power cycle or press of the Reset button is enough to reset internal CPU registers? Or that somehow resets/initializes the watchdog? You said both of those things would fix the "00" POST code and POST failure.

What is producing all the error messages for the "drivers" you don't have? They seem to be internal UEFI/BIOS code? Wait, you are using FreeBSD 11 x64.

You have dismissed using FreeBSD 11 x64 as irrelevant, simply because someone reported a similar issue. AMD states only Windows 10 officially supports Ryzen. ASRock states only Windows 10 is supported for the X370 Taichi. Have you verified Ryzen support on FreeBSD 11 x64? If that is possible.

Have you modified the UEFI/BIOS file yourself?