**Unified** DFI LanParty UT 790FX-M2R-M2RS / Phenom /Data Base Thread**

[Oese]

lol @ that p-2 thing

but... nb IS working.. you can measure it...

[Lastviking]

w00ps, a few corrections in first post;

I only have P-0 to P-3, not P-4

P-3 result was a BSOD, so I think P-2 is the best.

Running for 20 minutes already,. had to increase Vcore 1.4875V for 3.7Ghz. Makes sense according to my results on air, namely '+0.15V'.

If this passes the 1h OCCT test Ill try and go higher with more Volts. Im quite happy the BSOD's I got with all previous testing were most likely meaning nothing because of P-state mess up. Although 1.4875Vcore for 3.7Ghz ain't super, nor bad though, I might be able to hit 4Ghz with 1.55Vcore...

With 1.4875Vcore, 1.2Vnb (if it's actually working) and 3.7Ghz CPU, 2Ghz NB my CPU temp is 36C

Im happy to say there's a bit more hope for this board again, on the otherhand Ive got to say BIOS is even worse than expected because, as I noted before, P-states shouldnt have any effect on OC'ing

[EDIT
WTF, I set 1.4875Vcore, it ran for at least 30 minutes which Im sure about but just as I checked it BSOD'd anyway with P-state 2 Everytime I get the same Machine Check Exception error as well. I set my NB back to 1.8Ghz incase Vnb ain't being applied after all.

EDIT 2
Ehm... Im starting to wonder if it might be caused due to my own mess, namely I didnt do a re-install of my OS's after I changed from 790FXB-M2RSH to 790FX-M2R and set my PCI-e and PCI cards into different slots than on my M2RSH. For example, I get 5 Found New Hardware pop-ups after boot...

The P0-P3 thing is wierd...but dont do like me and feed the hungry 1066 mems with only 1.95v... it looks like they need 2.08v

Try to fix the another mess first , first check memmory with memtest, and after that go to the cpu thing... have you tryied ACCisabled/Auto/Fixed?

One more thing can you check one thing for me....i did something stupid this day and changed to singel core instead of auto..so i can have messed up something in windows(nvm looks good now haha)

[Rammsteiner]

The P0-P3 thing is wierd...but dont do like me and feed the hungry 1066 mems with only 1.95v... it looks like they need 2.08v

Try to fix the another mess first , first check memmory with memtest, and after that go to the cpu thing... have you tryied ACCisabled/Auto/Fixed?

One more thing can you check one thing for me....i did something stupid this day and changed to singel core instead of auto..so i can have messed up something in windows(nvm looks good now haha)

I always set Vdimm higher right from the start, always around 2.1Vdimm or so.

I cant use ACC since this board is with SB600.

I suspected the memory system however that wouldnt make sense since Ive ran Memtest already. Not very long, but if there would have been serious damage you would find out very soon when starting Memtest.

Ill do a fresh Vista install without anything else, just OCCT and Memtest. What exactly do you mean with 'changed to single core instead of auto'?

[pershoot]

I always set Vdimm higher right from the start, always around 2.1Vdimm or so.

I cant use ACC since this board is with SB600.

I suspected the memory system however that wouldnt make sense since Ive ran Memtest already. Not very long, but if there would have been serious damage you would find out very soon when starting Memtest.

Ill do a fresh Vista install without anything else, just OCCT and Memtest. What exactly do you mean with 'changed to single core instead of auto'?

lower your vdimm and only apply if needed. that could surely be contributing to the issues (it does for me). vcore too (not as much since your on water, but some chips get unstable with more then needed voltage).

[Rammsteiner]

lower your vdimm and only apply if needed. that could surely be contributing to the issues (it does for me). vcore too (not as much since your on water, but some chips get unstable with more then needed voltage).

Might give it a try but well, it's listed as 2.1~1.15Vdimm

Just reinstalled Vista, then Memtest and OCCT 3.0.0.0 Running 4 instances of Memtest of 900MB each, will let it go over night, that should rule out any memory issues

[Smartidiot89]

Text

LastViking reported the same thing, he gained stability through changing P-state

[Rammsteiner]

Sooner than later Im going to use this board as a frisbee

It just wont run stable at 3.7Ghz! And it was sure as hell stable on the 790FXB, un ing believable. Tried different P-states, Vcore upto 1.4875, lowering Vdimm, using higher NB clocks etc. And it wasnt the memory, ran 125% coverage with 4 instances of Memtest, each 900MB.

This is getting retarded. Ill try and see if this board maybe has some preference for low multipliers or so, as far as a motherboard could have that, I dont know.

[pershoot]

installed speedfan for the hell of it and ran it. system froze at scanning ISA bus. cpu did not clock the same afterwards (even a cmos clear did not help). had to do the ol killcmos -> flash -> killcmos -> flash to get it back.

fan on nb w./ velcro is helpin lots. reduced amount of heat gettin to rads internally. man can i hear the intake fan (after cleaning out) and chipset fan slightly. ah well, ill get used to it.

3.82GHZ on fxb-m2rsh. had to increase vdimm slightly to get it to pass after 6.5hrs (i was hoping it wouldn't be CPU-NB volts that needed to go up, and so far don't need to, so thats good..).

http://img128.imageshack.us/img128/7...phenomii3w.jpg

[Rammsteiner]

Oh...

Somehow my CPU has a wall right at 3.7Ghz 3.7 or over it just doesnt work (thus far).

I ran 15x246 for 3.5h at 1.5V, then I set 15x248 and it restarted in 5 minutes. Now I set 1.55V, if it will still BSOD/restart Im afraid Ive just some retarded batch

It's running a few minutes longer thus far, so maybe there's hope PWM's do get hot though, in the 60's. I dont know what DFI did with PWM cooling but it ain't doing its job very well

[pershoot]

Oh...

Somehow my CPU has a wall right at 3.7Ghz 3.7 or over it just doesnt work (thus far).

I ran 15x246 for 3.5h at 1.5V, then I set 15x248 and it restarted in 5 minutes. Now I set 1.55V, if it will still BSOD/restart Im afraid Ive just some retarded batch

It's running a few minutes longer thus far, so maybe there's hope PWM's do get hot though, in the 60's. I dont know what DFI did with PWM cooling but it ain't doing its job very well

i had the same pwm toasty issue on the m2r. on this fxb, the pwm stays nice and cool.

[Brother Esau]

Danger Den Torture Rack
LanParty JR 790GX 1/21/2009 Bios
940 BE
Danger Den Custom Water


CRAP!!!!!!!!! Forgot to change screen resolution ...........any way its 3.8ghz @ 1.44v

[mcmeat51]

M2RS BETA BIOS

well just flashed to the 02/02 lates beta bios and after a VERY preliminary test, it seems MILES better than the A01 version, (may be becuase I usb flashed this time instead of winflash)

but the bios layout seems better and NB multi acrually works.

so far ive had a much better and stable OCing with it.

[Oese]

@ brother esau: nice

[Rammsteiner]

Oh lol, my this motherboard is rather funny... in a bad way though.

Im slowly boosting up HTT with stock multiplier. Last night I actuall;y had it stable running 15x248, needed 1.55V though. Changed to 15x251, restarted in 10 minutes.

This morning I set 1.575V and it was still going after 40 minutes.

This is on 26/12 beta though, since you guys had issues with 16/01 and 21/01 I didnt try those yet, but could it be that either of those BIOS's has a better OCíng or do I just have a crappy batch

Weird thing is that the PWM temp seems to be different everytime, always too high IMO but well. Ill keep this board for a while though however I do not plan to get a DFI board soon again with all those BIOS issues and bad cooling solutions.

Maybe a Crosshair II. Sapphire released a new motherboard too, but think it's for AM3. It's a 790GX board with some epic amount of MOSFETs, looks a bit like Jetway's 790GX board. I dont mind squeaking PWM's as long as the cooling is allright

[Russ_64]

@pershoot - how did you set your CPU-NB volts - mine is at 1E (is there a way to see volts?) - I tried at 1F but was still not stable with NB @ 2.2 and HT @ 2.0 I matched your other settings but was not stable at 3.7 - passed OCCT at 3.6 (Itried up to +125mV)

As Folding was causing system freeze / crash I have backed down to CPU@3.4 +75mV/NB@2.0/HT@1.8

[Rammsteiner]

I think Im getting closer to the problem but there could be various issues;
1) Board/CPU doesnt like high HTT's and/or HTT's around certain speeds (with my Athlon X2 64 it refused to work at 266/267Mhz but over and below it would)
2) Board doesnt like too high multipliers
3) Board has an issue around Vdimm (testing now).

I succesfully ran 15x248 with RAM at DDR533. I set 13x286 and it was quite stable AFAIK. I set RAM at DDR800 and 2.16Vdimm and it all turns black after a while. 18.5x200 never really worked either And yes, the RAM does work at that speed. It's running for 30 minutes now with high Vdimm, but well, anything can happen in the next hour

I requested a RMA an hour ago and asking if I could replace it with an other board, awaiting response. That's for my 790FXB-M2RS with the blown MOSFET btw.

Ill also RMA all the other stuff and just sell them.

[pershoot]

@pershoot - how did you set your CPU-NB volts - mine is at 1E (is there a way to see volts?) - I tried at 1F but was still not stable with NB @ 2.2 and HT @ 2.0 I matched your other settings but was not stable at 3.7 - passed OCCT at 3.6 (Itried up to +125mV)

As Folding was causing system freeze / crash I have backed down to CPU@3.4 +75mV/NB@2.0/HT@1.8

backwards from 1e goes up in value and forwards goes down in value. please refer to the table that has been posted in this thread two or three pages back.

you shouldnt use my values as they will be different for your parts.

[bldegle2]

Rammsteiner,

RE: P states, following your postings and figuring the 790fx-M2R is about the same except for the SB600, I set the P state to P2 in the bios since that was the setting that worked best for you, there seems to be a change in the way the unit runs/reacts (better).....will test further and see what is.....

Interesting stuffs, wonder if it affects the PWM reaction????

Laterzzzzz...............

[Rammsteiner]

WTF

Can anyone with a stable OC try and set a Vdimm of say 2.16V? If your RAM supports that of course, and test for stability again?

Either my PhII doesnt like high Vdimm or my board is just messed up, which might explain why I just got a mail from the store where I send my 9950BE for RMA to saying it ain't broken (memory problems, wouldnt read certain DIMMs etc)

Annoying annoying

[Russ_64]

backwards from 1e goes up in value and forwards goes down in value. please refer to the table that has been posted in this thread two or three pages back.

you shouldnt use my values as they will be different for your parts.

Thanks mate, we actually have similar rigs so I used your settings to get some idea of what to play with and what to leave well alone

[pershoot]

Thanks mate, we actually have similar rigs so I used your settings to get some idea of what to play with and what to leave well alone

cool. i see your on 1/20. this bios limited my clocks. flash to 1/16. you should be more stable at higher clocks.

[Russ_64]

Well, as a rule I hate going back to an older version if the current one works - anyway we can still hope for a new beta sometime this week :-)

Q1 - have you tried P2 or just P1?
Q2 - do you think ramping up NB and HT is necessary (I ask becuase some do it and some don't)?

[pershoot]

Well, as a rule I hate going back to an older version if the current one works - anyway we can still hope for a new beta sometime this week :-)

Q1 - have you tried P2 or just P1?
Q2 - do you think ramping up NB and HT is necessary (I ask becuase some do it and some don't)?

1 - i have been on p-1 since i popped the cpu in; when it first landed in my hands. this is the most stable for me (i have tried them all). i have also advised others early on in other threads to play with this setting. the pII brings forth more p-states. i thought it was related to cool and quiet (which i have disabled), so not sure why this works in adding stability. ah well, whetever works, hehe.
2 - NB yea to get down the latencies. If you ramp up NB, HT likes to be at the same speed for most stability, in my experience. I think leaving HT at default (1.8) as well should also be stable with a higher NB.

good luck

[bldegle2]

Rammsteiner,

RE: ram voltage, I have been running 2.3 to 2.4 with my Adata stuffs, no problems, 2.3 is default for 1066 runnings, all four slots, added a .1 just in case.

P2 state still seems to be better....

laterzzzz...................

[pershoot]

installed speedfan for the hell of it and ran it. system froze at scanning ISA bus. cpu did not clock the same afterwards (even a cmos clear did not help). had to do the ol killcmos -> flash -> killcmos -> flash to get it back.

fan on nb w./ velcro is helpin lots. reduced amount of heat gettin to rads internally. man can i hear the intake fan (after cleaning out) and chipset fan slightly. ah well, ill get used to it.

3.82GHZ on fxb-m2rsh. had to increase vdimm slightly to get it to pass after 6.5hrs (i was hoping it wouldn't be CPU-NB volts that needed to go up, and so far don't need to, so thats good..).

3.84 looked good when i left my apartment for work (was 3 hours in to occt). 3.86 no go (increasing vdimm to the next level made pc bounce itself during the night while stressing). 3.9 failed in about ~5 mins of stress at this voltage level, so for sure there is clock room left in this gem of a cpu that i have. maybe ill burn the hell out of it when im ready to upgrade next year, hehe.

i had something strange happen...

i was burning a dvd this morning and must have built up a slight static electricity charge from walking over the area rug in the other room and having my coat on. i went to go open the front panel a lil bit more to check on dvd, and felt a slight shock. video went out for about a half a second (then came back), and dvd failed to burn (i reburned and it went fine) and occt was still going strong. hopefully i didnt ruin any components from that one incident. i gotta remember to always ground myself prior to touching the pc!