Personally I think its a POS but the fact here is that Bios on this board has never properly supported the stupid thing and its one of the Key components to the new Platform and it would be nice to be able to use it to monitor your system without it taking it down for no good reason.
SuperMicro X8SAX
Xeon 5620
12GB - Crucial ECC DDR3 1333
Intel 520 180GB Cherryville
Areca 1231ML ~ 2~ 250GB Seagate ES.2 ~ Raid 0 ~ 4~ Hitachi 5K3000 2TB ~ Raid 6 ~
I think it's due to the mobo uses slam vid mode. That means the CPU VID set via MSR registers are not used. The CPU VID in the registers stays at 1.25V.
Now AOD starts reads 1.25V CPU VID and tries to apply an appropriate CPU voltage.
If posted the MSR registers at page ~#24 here.
where is the driver disk for the latest bios Raid Rom
Latest Raid Driver Package from DFI is
790FX-RAID-F6
Includes SIL and SB600 drivers and is recommended for raid bios version above 3.1.
The SB600 drivers are from 08/2007.
"Angels on the sideline, Puzzled and amused.
Why did Father give these humans free will?
Now they’re all confused."
9850(JAAFB AA 0810BPAW), DFI 790FX M2RS(3/05 Bios), G.SKILL 2 x 2GB 1T-5-5-5-15, OCZ 600, MINI NINJA, WD SE16 AAKS 320, HIS3850, bluegears b-Enspirer, Vista 64
Well i'm ocing now.
Got 3,2 at 1,375V in bios bus it not stable and gives an rounding error at 4 min. Other voltage setting have a minor increase. Mem is @ stock.
I will be wokring on this. I want 3,2Ghz....
Another thing. when i shut Vista down it restarts it self and boots up to vista startscreen. i looked to the connectors and the are ok connected and working. anyone having the same problems.
@ final8ty look on:
http://us.dfi.com.tw/Support/Downloa...FLAG=A&SITE=US
F6 is the latest and works ok
Spider >>>> Dragon system:
Antec P182
Antec TruePower Quattro, 850Watt
ASUS CROSSHAIR III
Corsair H50 PnP
AMD 955BE
Corsair CMD8GX3M4A1600C8 4x2GB
WD Raptor, 3x36 GB RAID 0
Sapphire HD4890 CF
Vista Home Premium 64bit, NL
Logitech G15.2 & G9
koekerwauz: two possible reasons: you get an bsod during shutdown which you do not see because of the os is set to restart at errors (default with home versions)
or you have set some wol- or other wake-up settings in bios.
i had this problem with my cfx and only way to get rid of was using the other lan-port..
1. ASUS Sabertooth 990fx | FX 8320 || 2. DFI DK 790FXB-M3H5 | X4 810
8GB Samsung 30nm DDR3-2000 9-10-10-28 || 4GB PSC DDR3-1333 6-7-6-21
Corsair TX750W | Sapphire 6970 2GB || BeQuiet PurePower 450w | HD 4850
EK Supreme | AC aquagratix | Laing Pro | MoRa 2 || Aircooled
Hi oese I have finaly been able to do that test with half en round multipliers,
ddr 1042 @ multi 10 clock 2610mhz gives:
8560mhz read
with ddr1000 @ multi 11.5 = 2998mhz gives
9091 read
So I guese G2 brisbanes are not sensitive for half multi problems!
As you can see higher trfc have solved my oc problems 308+mhz htt is no problem any longer since I use 3oh6 settings for this ram! Thank you very very much for that!
@ all has any one noticed if changing from k8 to k10 does lower the squeeling noices of the bord? the lower vcore of phenom does it help reducing this sound? Or is this noice related to the changing memory speeds on k8 when changing multi?
greetz
AMD Athlon II 620 @ 2.6ghz (@ 1.15v)
DFI AM2RD790 2x 2GB
OCZ OCZ2P10004GK@500mhz 2.1V
Seasonic s2 430watt
Sapphire HD 3450 - Samsung F1 750GB
Scythe NINJA
Windows XP 32/Vista 64 Prof
You should not be getting any noise periodI have had a 6400+BE in this board and the Phenom is new past few days and I have had 2 boards and neither one of them made any kind of noise under load or due to RAM MHZ Or voltage change
![]()
SuperMicro X8SAX
Xeon 5620
12GB - Crucial ECC DDR3 1333
Intel 520 180GB Cherryville
Areca 1231ML ~ 2~ 250GB Seagate ES.2 ~ Raid 0 ~ 4~ Hitachi 5K3000 2TB ~ Raid 6 ~
@ DPeter: Nice, thank you... It would have been horrible if brisbanes which often come with half multipliers would show this behaviour.. and Phenoms have half multipliers often too...
1. ASUS Sabertooth 990fx | FX 8320 || 2. DFI DK 790FXB-M3H5 | X4 810
8GB Samsung 30nm DDR3-2000 9-10-10-28 || 4GB PSC DDR3-1333 6-7-6-21
Corsair TX750W | Sapphire 6970 2GB || BeQuiet PurePower 450w | HD 4850
EK Supreme | AC aquagratix | Laing Pro | MoRa 2 || Aircooled
It's true you "shouldn't" get any sound from the board although it happens quite often on any component when stressed more.
I had both an X800Pro ViVi @ XT PE and a X1800XT @ XT PE which made noise underload only. Also my previous DFI nF4 Ultra-D board made noise, Epox 'somthing' made noise and this one does as well.
As you said, it shouldn't however it's not a sign of dieing hardware or anything. So if you can live with it just leave it be.
Synaptic Overflow
CPU:
-Intel Core i7 920 3841A522
--CPU: 4200Mhz| Vcore: +120mV| Uncore: 3200Mhz| VTT: +100mV| Turbo: On| HT: Off
---CPU block: EK Supreme Acetal| Radiator: TCF X-Changer 480mm
Motherboard:
-Foxconn Bloodrage P06
--Blck: 200Mhz| QPI: 3600Mhz
Graphics:
-Sapphire Radeon HD 4870X2
--GPU: 750Mhz| GDDR: 900Mhz
RAM:
-3x 2GB Mushkin XP3-12800
--Mhz: 800Mhz| Vdimm: 1.65V| Timings: 7-8-7-20-1T
Storage:
-3Ware 9650SE-2LP RAID controller
--2x Western Digital 74GB Raptor RAID 0
PSU:
-Enermax Revolution 85+ 1250W
OS:
-Windows Vista Business x64
ORDERED: Sapphire HD 5970 OC
LOOKING FOR: 2x G.Skill Falcon II 128GB SSD, Windows 7
Last edited by Koekerwauz_NL; 03-30-2008 at 07:55 AM.
Spider >>>> Dragon system:
Antec P182
Antec TruePower Quattro, 850Watt
ASUS CROSSHAIR III
Corsair H50 PnP
AMD 955BE
Corsair CMD8GX3M4A1600C8 4x2GB
WD Raptor, 3x36 GB RAID 0
Sapphire HD4890 CF
Vista Home Premium 64bit, NL
Logitech G15.2 & G9
G.Skill SPD have support for Weak Mode, when BIOS have that option I enable it, I just use NORMAL to cut some variables when debugging, a non boot situation. All RFC's can be set to 75nm, about gains didn't bench WEAK/NORMAL, I'm still fighting to level this board at same MSI/ASUS OC level, to start real benching. (I'm tempted to flash M3A32 bios in this board, with some mods).
I'm running Prime ATM:
Yea, changing tabs or set Turbo mode, got video corruption (color stripes all over) mouse sometimes move sometimes don't.
Welcome,bw to low, SP1 it's not TBL fix killer but also general performance killer, I will be back to non SP1 soon.
I will not argue with that, but the fact is, if I touch the HS heatpipes near CPU when at full load I bearly feel it warm, if I touch PWM HS then I feel it more hot.![]()
How can I know the real temp, by software? All progs I have, show me aprox same results. Please check Thumbnail, thx.
I'm alergic to the Dark side.![]()
Real temps are not possible with software with AMD Phenom.
Check the new AOD they were supposed to calibrate the readings better (?)
The 1.4V+Phenom temp statement I made a long time ago in MSI thread because of details from AMD.
Tcontrol works by reading "too low" when it's below a "certain temperature point" but then "too high" when above that same "certain temperature point". The temperature point looking at documents seems to be near 55C real Tcase.
So;
Before that value you'll have temp. values given back that are -<54 while the real temp is higher.
After that value you'll have temp. values given back that are >55- while the real temp is lower.
Hence, the temp. feedback is designed to read lower than ambient and even negative values on air cooling.![]()
If you have enough air moving on the HSF, it will feel cold to the touch. Only the direct base will feel heat near to the real temperature. Also metal feels cold to human touch if you're hands are above its temperature, its a relative thing. Just be careful, your load temps will be high, very high, on air at 1.4v.![]()
Ok, so if I got it, 55C its the "breaking" point, Tcase(real temp)<55 Tcontrol read low temps. So my readings are "low" Tcontrol=CPU 57C; Cores 48C full load, can I make an logical conclusion that my Tcase<55C?Tcontrol works by reading "too low" when it's below a "certain temperature point" but then "too high" when above that same "certain temperature point". The temperature point looking at documents seems to be near 55C real Tcase.
As you can see some posts before I got photos from my system running, the white fan is at 110CFM and blow air over PWM HS, and i feel the difference between PWM/CPU, I know is far from be accurate reading, but reflects the software reading difference values, in bios CPU temp reads 28 and PWM 45.
Only the MSI runned fine 2750 @1.3v.
Well, I have some temp probes cables, and still have an K7M board with pins to connect, so if I put the probe between CPU and the socket (I have one able to insert there, just don't know here), can I read Real temp in the K7M system?
THX
I noticed that my board has a high pitch squealing noise too and it seems to be coming from the PWM area. I don't know if this is normal or not but everything seems to be working fine so far.
OK...... Was able to finally get the OC working on this thingonly problem is that for some reason I am baffled to why the computer wont Boot with Ram at 1066 set in Bios
is it the Ram or is it me? My Ram does over 1200MHZ
Thats a factguess its me
or does some Ram just not get detected when set to 1066 max value in Bios? Also from what I see my board responds better to being set through FID/DID not by CPU Multi
any words of wisdom on the 1066 Ram setting in Genie Bios and why my PC wont boot with it set on that?
Modest OC
@ 2420MHZ @ 220 Bus Speed X11 Multi HT Link Frequency @1980mhz NB Frequency @ 2200mhz / Ganged Mode all at stock Voltage![]()
Cmon fellas help a brother out and lay some info on me![]()
SuperMicro X8SAX
Xeon 5620
12GB - Crucial ECC DDR3 1333
Intel 520 180GB Cherryville
Areca 1231ML ~ 2~ 250GB Seagate ES.2 ~ Raid 0 ~ 4~ Hitachi 5K3000 2TB ~ Raid 6 ~
That's a guess by me and that's only Tcase (center of IHS). Tjunction (internal diode) temp. is higher. But yeah 55C seems very close to what it is. The diodes in k10h also have an errata where they read too low temps.
You just have to use common sense and basic physics knowledge to discern whats correct and not; 1.4V/155W on a 1.23V/95W TDP chip is going to be very high load temps. In the 70-75C region Tjunction with a TRUE and 2x 105CFM Deltas, 20C ambients, which is not far from the throttling temp.![]()
Brother, you'll need to read quite a lot for Phenom, it 'aint that simple as X2/C2. Spend some useful time now and quit messing around![]()
Achim and aGeoM should know all there is to it without you needing any other material.
Drop your NB to 6x and the MEM to 667 mode, blast coolers on full then try oc'ing Phenom.![]()
I have massive trouble with it even with the BE5000 in my board. It does not like the M2R near as I can tell. Actually, I haven't found a board that it works well with yet. I had an Asus M3A32, it worked poorly with that (actually, it reset the board by itself constantly).
I'm typing this on a Gigabyte 780G board, and it works poorly there too (even with the new version specifically FOR the 780G). It registers voltage and temps incorrectly, doesn't baseline most settings at all, and is generally faulty.
If I run it, and I have Everest running at the same time, clock speeds start bouncing around in Everest. AOD is pretty lame.....![]()
ok, I give up. I was lucky not melting the board when I did 2900Mhz @1.53v
![]()
KTE, OCing in my point of view, isn't lowering nothing, more CPU/NB/HT/MEM MHz @ the most stable configs, finding the balance (G spot) it's my gold, for 24/7 use and smooth as silk gaming. When targeting some hwbot's scores then I clock someting down to achive it. For me Phenom in some way isn't different from X2 or K6-2, only have more variables to play.
That's why I'm a litlle frustraded with DFI compared with ASUS/MSI, she's cold like Artic waters, maybe that's why I'm getting so low temps.![]()
![]()
So your ram is not yet supported. KTE mentioned some time go that modules without 1066 JEDEC mode need to be prepared by the bios developers in a more manual way.
Nevermind 4-5-5-16 are the best timings i could choose in the bios in that mode, unfortunatel i could not yet reach a 300MHz ref HT.![]()
I tried it the FID/DID way here first and it did not boot with a 13x multi using the cpu clock multiplicator worked, so I thought it's the better way.
Seems sometimes the DID's and FID's are not set to proper defaults.
What made you boot finaly, 800 mode or FID/DID?
There ya go, 2.2GHz for the NB is abit high for stock (1.25V).
Bookmarks