well if a device doesnt get the V it needs it compensates by using more A.

The overheating problem occured again and this time I was able to test the voltage rails as OCZ wished... the good news is, the voltages were almost exactly their correct values. Bad news, something else besides the PSU must be causing the voltage on the mobo to be too low, causing the CPU to overheat... voltage regulators went bad, maybe? It appears my next step is to contact DFI :( . I'm rather hoping to get this resolved and everything working well in about 2 weeks time when I get out of school for the summer :p

checked if the caps are round and fine ?

EDIT:
you do know many temp sensors on motherboards are a joke ?
amd have measured up over 30 celsius wrong on an asus board and all other boards they had tested was more or less off.

is the heatsink hot ?
reapplied AS5 ?

I looked around at the caps, none appear to be blown as far as I can see, and I doubt the temp sensors are off by almost 30C. Also I'm not using AS5, just whatever came with the stock AMD HS.

Although the problem may have occurred at system startup a few times in the past, I haven't been able to get it to occur at startup when I've tried. After doing a bit more testing, I have found another way to reliably duplicate the problem. If I put the computer on standby, then try to bring it back up, the overheating problem occurs every time. Further evidence that this is a hardware issue, and not just SmartGuardian reporting incorrect values, is that the first few times I attempted to bring up the system from standby, the whole computer shut down. When I went into the BIOS and upped the CPU shutdown temperature from 60C to 65C, the system shutdown ceased occurring and I was able to bring the computer back from standby into Windows, where SmartGuardian reported temps of ~59C. Since the shutdown is controlled by the BIOS, not SmartGuardian, it appears that the BIOS is seeing the high temps too. And so the plot thickens...

Have you got cool and quiet disabled in BIOS? And CPU thermal throttling turned off?

You don't have wake-on enabled or anything like that do you?

If I put the computer on standby, then try to bring it back up, the overheating problem occurs every time. Further evidence that this is a hardware issue, and not just SmartGuardian reporting incorrect values, is that the first few times I attempted to bring up the system from standby,

seen many strange things happen when using standby mode so i still believe its a software issue.

i know you dont have a msi motherboard but if you go to their forum and make a search on standby you will se many different problems.
monitors not starting mice and keyboard doesnt work
cd's stop working networkproblems... the list can be made very long.

Cool and Quiet is disabled, as are the power on for mouse and keyboard. CPU thermal throttling is enabled at 50%... I thought this is for overheat prevention? Come to think of it, thermal throttling is probably what my mobo is doing, to prevent further overheating. If my temps hit 60C with it on, how high would they go without it?? I don't really want to know.

It *could* be a software problem relating to standby, but still, standby SHOULD work. It is preferred over shutting down the comp all the time to save on the power, wear and tear that the system goes through on startup, etc. If for some reason my system is incapable of using standby correctly, then somebody screwed up the design somewhere.

Also btw I have 2 Windows installations on this system, both of which exhibit the exact same overheat behavior on startup. Therefore it is at least not a probem with a particular installation of Windows.

From Angry_Games on DFI Street:

actually if you check the real temps, I think you'll see that only the temp sensors are reporting incorrectly resuming from standby...the actual temps are not getting that high.

This is a known issue (resuming from standby and having temps show about 20C too high).

There is no fix for this.

There is nothing wrong with your motherboard.

The DFI Lanparty series motherboards are built purely for overclocking, and because of such a design, certain features on 'vanilla' boards don't always work correctly anymore (resume from standby and hibernate are two features that usually take a hit along with Cool & Quiet).


You are free to RMA your board as many times as you want, but you will find that each and every board will do the same thing upon resume from Standby.


The only real answer is just shut the computer down when not using it, or just have the monitor turn off after 15 minutes or whatever and leave the rig running.

So, it is a software reporting issue after all. Guess I'm good to go on overclocking, as long as I stay away from standby. As I said, not a good design, but meh maybe I can live with it as long as it's not actually damaging the CPU.

Thanks for the help everyone :worship: :worship:

why not get a third party temp sensor for the cpu instead of using the builtin ?

third party is often much more accurate.

That is a possibility... could you recommend a good model?