Page 1 of 1

Phenom II X4 955 BE - AMD 790FX - Windows 7 RC - No Temp.

Posted: Mon Jun 01, 2009 10:06 am
by CoreTemp-User264
I have built a new system with the following components

AMD Phenom II X4 955 BE Processor
Gigabyte MA790FXT-UD5P Motherboard
8G DDR3 RAM
Windows 7 RC x64

CoreTemp 99.5.20 reports 0? in the temperature reading. I also noticed that the AMD overdirve software reports a temperature of -255 degrees.

Happy to help with any testing.

Posted: Tue Jun 02, 2009 10:35 pm
by The Coolest
It seems to be a BIOS issue, as some users have started to experience similar issues. The fact the AMD's software also exhibits similar behavior means that this is not a software problem.
Try to update your BIOS to the latest one and see if that helps.

Posted: Tue Jun 09, 2009 7:30 am
by CoreTemp-User273
I have an AMD Phenom II X2 on a Gigabyte board (GA-MA790XT-UD4P) that is having the same issue. It also registers the processor at 800 MHz until I do something. CPUZ shows it at 3.1 ghz, no throttling. CUPID hardware monitor says its 50c at all times for both cores, but has 3 odd "temps" called TMPIN0 TMPIN2 and TMPIN2 that look like system and CPU temps.

With Prime95 going (for awhile now), here is what I am seeing:

Temperatures
TMPIN0 - 52C
TMPIN1 - 61C
TMPIN2 - 52C

AMD Phenom II Black Edition
Temperatures
COre #0 - 50C
Core #1 - 50C

I don't think the Hardware monitor is working right either. I set my motherboard alarm to 60C, and it goes off after a little while of Prime95, so my temps at load must be around 60C. Not the greatest, need a better fan.

Also, if I unlock all 4 cores, Core Temp goes crazy. It tells me I have 4 12GHz processors when the CPU's are under load. My 60C alarm goes off instantly when I Prime95 it. My motherboard temp gauge (in BIOS) says its 50C with all 4 unlocked, so no nuclear meltdown is happening.

No Prime95 errors as of yet. System seems stable with Windows 7 running. I also have the newest BIOS that Gigabyte has released for my board. It allowed my processor to be identified, was unknown before the BIOS update.