K today in the P5Q Dlx topic we had an issue that users couldn't downgrade to an earlier bios... I proposed to try out a hot flash in which I succeeded ( for those unaware the P5Q Dlx and co have 2 bios chips) so I downflashed from 1611 to 1406... reset bios to defaults, rebooted and then shut down and popped the battery for half an hour to make sure everything got thoroughly wiped... I rebooted and wanted to verify if everything was working correctly... gamed on the rig for a few hours all looked stable, then again a quick temp check etc...
When I opened Realtemp I noticed a strange anomaly in the temps under load... my quad has always been pretty close in the cores, yet now I got a 7°C difference... I openend coretemp : same temp difference there and ow shocka a VID of 1.125... where did the latter come from ? it has always been a VID 1.250 with this QX on 4 different mobo's...
Look at the screens they tell a zillion words :
CHIP 1 with the 1611 to 1406 downflash ( reflashed it trice now wiuth EZ FLASH and AFUDOS and popped battery each time)
CHIP 2 with 1406 bios ( have also reflashed it today, was 0803 before)
So if someone has an explenation what has exactly happened here : a bad flash like most will suspect ( rig works perfectly passes 15 IBT passes, gamed upon,...) reflashed trice, popped battery etc... and no I'm not a NOOB : all settings are 100% identical
I 've told a few times that on some mobo's the cores on some of my CPU's were stuck. Yet on another mobo they worked perfectly ( same type of mobo )
Again this experience confirms that a bios can bork readouts of 45nm way more than some know... VID seems to be able to change with biosses etc
EDIT : reflashed the borked chip with KODA's utility all is same again as chip 2 Yet it remains fascinating to me that a bad flash can evoke this sort of behaviour on monitoring programs
Saaya yupp, I agree
Reply With Quote
Bookmarks