Why does System and NB temps show as 0C?
I think this might be why my fans go full pelt all the time instead of being "smart"..
Printable View
Why does System and NB temps show as 0C?
I think this might be why my fans go full pelt all the time instead of being "smart"..
Mine shows the same, i don't really use the program as because of things like this it's not much use :down:
Hi
I canot get the Aegis pannel to work, its says unknown MB when I start it. It is the new from Foxcon download
Even the new ini file with no luck
Foxconn Blackops G28
Q9650 @ 3.9Ghz (410x9,5) v1.3
2x1GB CellShock DDR3-1800 (7-6-6-21, v1.86)
Two separate WC loops
D-Tek Fusion v1 on cpu
and stock+copper top on nb (thanks a lot shamino)
nb v1.47
I love this board and is not ready to show alle my settings yet
Have you tried a different version of the Aegis Panel?Quote:
Originally Posted by tinus
hey guys,
sorry about the inconvinience...
could you post some more details?
are you on xp or vista?
what version of aegis are you using?
what bios are you using?
what exactly doesnt work for you?
oh and do you have the smbus driver and chipset driver installed?
Latest version of the Aegis Panel (1.0.2.32) from the Quantum Force website - http://www.quantum-force.net/downloa...Panel10232.zip - does work with the Blackops.
For some reason LiveUpdate doesn't download this new version.
If you have the old version installed, seems to have to uninstall the old one first, reboot, then install this or it won't work, and you have to install it to it's default location in C:\Program Files.
tinus - try going to c:\program files\FOXCONN\Aegis Panel and running FXAppLoader.exe
that's where your shortcut should point.. if you have installed it elsewhere, uninstall -> reboot -> reinstall to default location then it should work.
gungero - same result with 10214, 10215 and 10232
negev - have done it no change
Latest version of the Aegis Panel (1.0.2.32)
XP
Foxconn Blackops G28
Q9650 @ 3.9Ghz (410x9,5) v1.3
2x1GB CellShock DDR3-1800 (7-6-6-21, v1.86)
Two separate WC loops
D-Tek Fusion v1 on cpu
and stock+copper top on nb (thanks a lot shamino)
nb v1.47
I love this board and is not ready to show alle my settings yet
I think I had to reinstall it a couple of times before it worked, make sure you uninstall it, completely remove the directory and reboot before you reinstall.
If you still can't get it working try extracting this into your program files dir:
www.dontbeshy.net/AegisPanel.zip
Yo, I just got blackops last night and got it up and running.
Same this with Aegis reading (or, not reading) wrong temps on NB and System. Aegis is really inconvenient, especially volt tweaking.
But i have the worse problem of horrible vdroop. i set target cpu voltage to 1.4 in BIOS and cpuz reads 0.88 at idle and 0.95 at load...i'm pretty dissappointed with this board so far.
I don't think cpuz reports the voltage correctly, it definitely doesn't report my memory configuration correctly. In any case, there is a vdroop compensation option in the bios (use at your own risk).
it was always reliable in my other x48 chipset, and the temps i get in realtemp support what cpuz is telling me. i idle at 30-34 and load around 40.
have you been able to clock any higher than 3.2? because i was able to do that right out of the box, no volt changes. But my chip did 3.8 on my gigabyte x48 mobo. So...uh...yah.
Mine needs 0.2v extra vcore to reach 3.2, I've tried several times to push it higher but always got lockups no matter now much voltage i blasted through the nb, vtt, vcore etc. I've now discovered that it was the ram, for some reason my Geil ram doesn't like running at it's rated timings even at 2N.
I will try to push harder again when I have time, now that I know it's the ram that was holding it back. It'll probably want super-lame timings to reach 1800MHz though :(
Quote:
Originally Posted by negev
Done with no luck, but I got a hint - there is some driver install incluted
and it's maybee interferience with somthing in my set up (an old monitor program or other driver) I will keep om tying.
Don't go by cpu-z for the vcore either, it shows me as 0.9v :rolleyes:
I wouldn't recommend going by software like this for your voltage settings, just use the BIOS.
Always take my voltages with Multimeter
vcore v1.3
nb v1.47
ram v1.86
I have a dream, a correct software based reading tool ;)
Hi! All
just back from i34 and was talking to the foxconn people there
the latest version of Aegis Panel is 1.0.2.32 http://www.quantum-force.net/downloa...Panel10232.zip and for the temp readings to work correctly you need bios version p05
p05 is bios version g28 + a few extra updates
it is available here http://www.foxconnchannel.com/support/downloads.aspx
i have flashed to p05 and have no issues with it - This is the bios they were using for the new E8600 and all their overclocking with LN2
best regards
flanr
Thanks a lot flanrQuote:
Originally Posted by flanr
The Aegis panel needs a public bios, ok never got into my mind
:rofl:
P05 is really later than G28?
I thought G28 was the hardcore beta bios that all the overclockers were using ;)
According to Foxliveupdate program G28 is the newest, and P05 is old. However Flanr said P05 is newer in another thread so i flashed it last night.
No change in Aegis panel or cpu-z readings.
@ negev
if you're having trouble getting above 400fsb try bumping the vdimm up a notch. for some reason my FSB seems entirely dependent on vdimm; i can only post at a higher speed when i increase it.
Thanks for the tip, ill give it a shot if i ever get my raid controller to stop lagging like a drunk :banana::banana::banana::banana::banana:.
It's been pissing me off for two days now, im now on my 2nd reinstall of windows but I think ive cracked it this time.
To anyone reading this DO NOT under any circumstances update your chipset or raid drivers with the latest ones from Intel, only use the ones from foxconn or you'll have major problems!
man, i really hope this board is eventually worth the hassle...before nehalem comes out.
Well after flashing P05 i've had the return of the dreaded Random Post Code 52 Hang phenomenon, which i've not had since i was on a previous public bios (p02). It's meant to be some memory related error however i get it even on settings which are 9hr prime stable, and then i just turn the comp off and on and it will boot fine. Until the next time i try to restart, when it will do it again.
Flashing back to G28!
I get the same thing with code 54.
let me know if flashing back to G28 fixes it.