TheFlyingWallaby

I did a quick thread search but was not able to find any useful info, so here goes. I just finished my X2 rig (in my sig) and started testing. I opened Coretemp and...and...9c core0, 11c core1, no Tjunction. Alright, this has happened before. Usually MBM screwing around assigning sensors to the wrong locations. I go through, erase anything MBM related (including Reg entries), and reboot. Same thing, temps impossibly low. :***: In BIOS, a little better, 20c CPU, 44c chipset, 33c system. Looks like the chipset sensor is OK. I have installed, uninstalled, and reconfigured every monitoring program I could think of. Even the DFI software was inaccurate. My only thought is that there are still some Gigabyte drivers left over from my old board that are screwing things up. I've done a decent search, but have not found any though. If anyone has ideas, that would be a big help. Also, if anyone knows where to view all the drivers installed on the system (to see if I missed any) that would also be a big help.

__________________
The Flying Wallaby strikes again!

TheFlyingWallaby

Also getting bad readings in Everest (sorry for posting again, edit button disappeared)

__________________
The Flying Wallaby strikes again!

JacKz5o

Temps are ridiculously high for me.. My PWM was idling at 56C today in the 90F weather.

TheFlyingWallaby

Thats nice, but it does not help me at all.

__________________
The Flying Wallaby strikes again!

Syrillian

Have you considered re-flashing the BIOS? Perhaps it is the culprit.

Does DFI provide any bundled software that includes a system monitoring utility (i.e. Asus' PC Probe)?

How about SpeedFan, have you tried that?

I realise that the aforementioned programs are not all that accurate (and sometimes downright loony), but setting a general trend may lend some insight.

__________________
Silentium ~ Arcane Arts

Semper Fidelis

"Illegitimi non carborundum"

TheFlyingWallaby

I have tried all the monitoring programs I know. The general trend is some sensor (somehow assigned to CPU) reads between 9c and 15c, one sensor (assigned to chipset) reads high 40's-low 50's, and one sensor (system) reads mid 30's. The SMART readings off the hard drives in speedfan are pretty much the same as they always have been. Coretemp reports no Tcasemax, which leads me to believe that the sensor itself is fine, only that it is not assigned to display as Tcasemax. This happened before (different system) and it turned out that MBM5 had reassigned everything incorrectly. FYI, that never got sorted out either. I would rather not flash the BIOS, as I just got the board today, and I strongly believe the problem is in driver conflicts, not the board itself.

__________________
The Flying Wallaby strikes again!

an51r

I really think, as syrillian mentioned, that your bios are the culprit as AMD has just switched to the 65nm process alot of boards where not equipped to accurately run the new process. I would consider it strongly and if you have doubts search the DFI website and forums or just read what the newer bios revisions fixed.

__________________
"All the true things I am about to tell you are shameless lies"
Kurt Vonnegut

Syrillian

... perhaps this will help...

View a Complete List of Drivers

Another popular and useful command line tool is driverquery. Intermediate users and network administrators can use this command to view a list of all installed device drivers and their properties. Driverquery command parameters can be added that allow the information to be output in a table, a list, or using comma separated values, all of which can be used to save the information for later use. There's even a command to output only information about signed device drivers.

To see a complete list of the device drivers on a computer:

• At a command prompt, type driverquery, and then press Enter.


To format the information in a table:

• At a command prompt, type driverquery /fo:table, and then press Enter.


To format the information in a list:

• At a command prompt, type driverquery /fo:list, and then press Enter.


To format the information using comma-separated values:

• At a command prompt, type driverquery /fo:csv, and then press Enter.


To view only signed device drivers:

• At a command prompt, type driverquery /si. Figure 3 shows an example of signed driver information presented in a list.

-Windows Support

__________________
Silentium ~ Arcane Arts

Semper Fidelis

"Illegitimi non carborundum"

TheFlyingWallaby

I just flashed the BIOS and still nothing. I'm really running out of ideas, but I'm starting to get the feeling that the only way to fix things is a Windows reinstall, seeing as it was software that screwed things up.

__________________
The Flying Wallaby strikes again!

Syrillian

...

Did you try taking a look at the installed drivers in the command line interface?

...you may be right: fresh install.

Did you re-flash the BIOS to the same version, or did you try other compatible versions?

__________________
Silentium ~ Arcane Arts

Semper Fidelis

"Illegitimi non carborundum"