So what you guys are saying is I should hold off a bit longer pulling the trigger on a 940????
So what you guys are saying is I should hold off a bit longer pulling the trigger on a 940????
I wasn't aware you had asked for counsel on CPU Purchase:confused:
I been reading cause I want a 940, and I want to run it on my M2R.
Perhaps I should hold off for a while yet......
Unless you think it would be fine...
The CPU is fine in the Board my only concern is current state of Bios:shakes:
I'm using 1.16.09 Bios atm.
oh and btw my chip numbers are:
HDZ940 XCJ4DGI
CACVC AC 0849APAW 9072241L80280
oh and since I re-seated the stock DFI NB/SB/chip cooler and applied Arctic Cooling MX-2 temps are down 5 Celsius
Do I have to have the 1/16 to runa P2 or can I keep the current one, I realize it will report unknown CPU, but is there other stuff that it needs or helps anything???
Currently have 6/12 installed....
Even the 12/1 official has PhenomII support...
running 3.9 gig again with my M2R, improved the chiller loop, got lower temps with higher volts, I say go for it, put the phenom in and start playing...
still a few more parts coming for even lower temps...damit, i am going to hit 4gig one way or the other......
laterzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Has anyone good CPU-Z shots or Screenshots with this board and Phenom II near 4GHz?
when AMD reached 6.5ghz at that overclock event, i watched the video and it was done on a M2RS DFI board..... then I think I saw another one at 6.7ghz with a gigabyte board, and then I believe I saw 6.xghz on an ASUS board.
I understand that they are using dry ice / liquid nitrogen / liquid helium, but what I was wanting to get at is isn't the M2RS bios very similar to the M2R bios or am I mistaken?
So far the BIOS is good except for one thing which is; increasing NB voltage. Changing it in the PWM settings does absolutely nothing it is as if that setting is being ignored (but still saved). I have tried all the way up to 1.5v but its still only 1.175v booted which limits me to around 2150mhz NB, after that I can't boot or will get horribly unstable. So I found a solution using these HEX codes, which ofcourse didn't work for me.
HEX = Volts HEX = Volts
00 = 1.5500 14 = 1.3000
01 = 1.5375 15 = 1.2875
02 = 1.5250 16 = 1.2750
03 = 1.5125 17 = 1.2625
04 = 1.5000 18 = 1.2500
05 = 1.4875 19 = 1.2375
06 = 1.4750 1A = 1.2250
07 = 1.4625 1B = 1.2125
08 = 1.4500 1C = 1.2000
09 = 1.4375 1D = 1.1875
0A = 1.4250 1E = 1.1750
0B = 1.4125 1F = 1.1625
0C = 1.4000 20 = 1.1500
0D = 1.3875 21 = 1.1375
0E = 1.3750 22 = 1.1250
0F = 1.3625 23 = 1.1125
10 = 1.3500 24 = 1.1000
11 = 1.3375 25 = 1.0875
12 = 1.3250 26 = 1.0750
13 = 1.3125 27 = 1.0625
1. Enters Advanced Mode and enters new HEX Code (stock is 1E - 1.175v).
2. Computer shutdown, followed by computer turnon and all fans running at 100%.
3. Only way to solve it is Clear CMOS.
4. I come back to BIOS and now the HEX code is set at 00(1.55v). Save and Exit which will result in 2. again.
5. Now I need to remove the MB battery in order to reset my NB-VID back to 1E.
And this is where I am. I have tried with several HEX codes, but none seems to work as i get the same result all over. I am using the latest BETA Bios on DFI's webpage 1/20/2009.
Am I doing something horribly wrong when applying these codes, cause it seems to work with others who use the same board as me (in signature).
Same on the MR2, the CPU NB volts don't change.
Hmm.. The funny thing is people have been able to change it on my motherboard the M2RSH with changing the HEX code, but as you can see it starts acting up. Hope DFI pulls out some new bios soon then :/Quote:
Originally Posted by Final8ty
Is it possible they could add the CPU-NB vcore options to the BIOS? AOD isn't good. It keeps resetting the voltage of CPU to default when I install the latest version.
The setting is there, it can be changed, but it won't do anything when booted it will stay at stock. Re-start and go back to BIOS and your setting is still there.Quote:
Originally Posted by panzerchaos47
As i said, awesome board love it, but of all things that has to be epic fail is that single setting in BIOS:mad:
Oh I meant for M2RS with SB600. Sorry I forgot to add that.
BIOs stays the same but in the OS when I install AOD. CPU would change back to default voltage and cause the system to be unstable. Same with memory voltage.
??? they do! i can even measure that...Quote:
Originally Posted by Final8ty
I was just about to post that it must change as i have been doing some testing even tho AOD & K10STAT says its at default & my NB overclock would become unstable when i lowed it in the bios.Quote:
Originally Posted by Oese
So its a screwed up reading & trying to change the cpu NB volts in AOD will screw up the CPU volts & it put mine down to 1.23 volts.
Its was not a problem with phenom 1 so its either a problem with just the bios giving out the wrong reading & address on phenom2 or just a problem with the latest bios.
I can be bothered to stick in a phenom 1 to see if its down to the latest bios or the phenom 2 side of the bios only.
i know the readout does not work somehow, not on k10stat nor on everest, dont care about aod... with the pI everest was also only reading the default value...
the NB multiplier absolutely works upward/downward with a 940 on fxb-m2rsh. with a 920, you wont get upwards adjustment and will need to raise HTT. downwards should work fine.Quote:
Originally Posted by Smartidiot89
Yepp I know. But i refered to changing HEX codes in order to increase the NB voltage:confused:Quote:
Originally Posted by pershoot
that absolutely works too, otherwise i wouldn't be on 2.6GHZ NB;)Quote:
Originally Posted by Smartidiot89
I can barely go above 2100mhz stable, as whenever I insert a HEX code and save/exit it goes loco and a clear-cmos won't even help as the HEX code will go too 00 (1.55v) and when I save/exit after that I need to remove my motherboard battery in order to restore it :PQuote:
Originally Posted by pershoot
So yeah, I am stuck at 1.175v
You got a Phenom II 940BE maybe its diffrent with Phenom II 920?Quote:
Originally Posted by pershoot
ya thats a tough one, since your locked upward. please load optimised defaults, try lowering your multiplier and ram divider, clock up a bit, lower your HT, and then try again on the NB..Quote:
Originally Posted by Smartidiot89
good luck:)