X370 Taichi Bios 4.xx -20℃

[Monster]

x370 taichi
bios 4.xx
1~8 cpu Appropriate temperature
9~16 cpu temp -20℃
core temp Version 1.11

bios 3.xx 1~16 cpu Appropriate temperature
core temp Version 1.11

[The Coolest]

Is this a new problem after the BIOS update or was it always there?
I have had a similar report recently about a 1600X. Can you post a System Information screenshot where it's scrolled to the bottom? (Tools --> System Information)

[Monster]

Bugs after BIOS update 4.xx

3.xx normal

[The Coolest]

Thanks, I'll look into it.

[The Coolest]

Could you please post a register dump? (Tools menu)
That may help point me in the right direction.

[Monster]

Bios Ver.3.xx dump

http://www.mediafire.com/file/sijma67qi ... p-Dump.txt

How to upload dump.txt?

[The Coolest]

Thanks.

Below the post text box, you have Options and Upload attachment, you can use that to upload a file.

[Monster]

Taichi Bios Ver3.xx dump txt

[Monster]

Core Temp Ver 1.12
Core Temp Ver 1.11
-20℃
Bios Ver 4.xx

[The Coolest]

It seems to be a problem with Core Temp not having access to the registers it needs from the 2nd CCX.
I'll look into adding a workaround for this problem into the next release.

[SebastianDI]

Hello from Germany. Maybe i can help. I have exactly the same temp status as the guy who posted this stuff. So i do not need to send a snapshot of my screen.
And i found out, why - nothing on the mobo is damaged. I have an MSI Carbon X370 Gaming Pro motherboard. Ryzen 1800X Prozzi on it. Latest BIOS on the mobo.
The situation states as followed:
I have 2 Soundcards to test. When i plug the soundcard called Creative Sound Blaster X-Fi Titanium HD into the first PCI-Express slot of the motherboard, all is running fine with the temp sensors there.
When i use the soundcard called ASUS Xonar Essence STX II in this slot, the temp sensor is slightly mad running (4 cores stay on -20°C), exactly as the user upper here this thread wrote it down.

I know that this is not a hardware damage thing. Maybe it has to do something with an IRQ problem, because the temp-sensor on the mo-board uses the same IRQ like the ASUS Xonar Soundcard uses? Every slot tried out, the card stays on IRQ32 (ASUS XONAR).

Just a thought. And if so, can this situation get solved by a BIOS update for the mobo? Thanks in advance, i only got member here to mention it - and to help a little.

Greetz from Germany,
DI

Aunt edith:
My System specs as followed:
Zotac Geforce GTX 1080TI AMP Core Edition (IRQ 54) and factory overclocked
AMD Ryzen Processor 1800X not overclocked, runs at AMD specs
Latest AMD chipset drivers installed
Motherboard MSI Carbon X370 Gaming Pro (BIOS Version 1.H0)
Ram DIMM3: G Skill Aegis F4-3000C16-8GISB DIMM4: G Skill Aegis F4-3000C16-8GISB
OS Version 10.0.17134.285 (Win10 RS4)

and lots of hardware surrounding me to test stuff.

[The Coolest]

It's my gut feeling that this problem has to do with something different.
It seems that the 4 cores on the 2nd CCX can't access the PCI device to read the temperature data out of it.
Perhaps it has something to do with BIOS (microcode?) security fixes for Meltdown and Spectre vulnerabilities.

[thedust]

Im using a PC with AMD Ryzen 1600X CPU. It s working good before, but after attached a Wifi PCI card, it show wrong temperature on 3 cores like below

[Freeze]

Hi!

After Windows 10 upgraded from build 18305 into build 18309, CoreTemp v1.12.1 no longer displays correct temp for all my CPU cores. Cores 1-4 are normal, but rest of them are way off too high.

Motherboard: Asus Prime X370 Pro
BIOS: 4024 (second newest, the one manufactuirer claims is a newer one is not recognized by BIOS update software )
CPU: AMD Ryzen 5 1600X

Screenshot:

[The Coolest]

@Freeze

It looks like a similar issue to the thread I moved your post to.
I haven't been able to figure out exactly what causes this problem, but I have a few theories.
Sadly there's no ETA on a fix for this yet. This will take some in depth rework to fix properly.

[Freeze]

@The Coolest

It's fixed now. Installing new Windows build 18312 fixed the error.
Thankfully, also the newest Windows beta and your new build 1.13.1 seem to get along just fine.

[spio017]

I have been looking for a fix for this problem as well. I recently did a reformat of my machine and now I'm seeing the same results. I am running on an X370 Gaming Pro Carbon motherboard with an R7 1800X on stock clocks. This only started happening after flashing the BIOS and doing a fresh format. I have attempted both the 7A32v1K and 7A32v1L BIOS versions with same results. I am thinking this is likely OS related though since the last post said this was fixed after a feature update. I am on Win 10 1809.