ASUS P5W DH - Problems + Fixes Thread

Printable View

Show 100 post(s) from this thread on one page

08-12-2006, 09:41 AM
matt1

Sorted now :D
08-12-2006, 11:53 AM
Counter CS

Quote:

Originally Posted by zbogorgon

can anybody help me with vdroop ?
what resistence of 50k VR is best?

Where is the place to do it ?
08-12-2006, 12:35 PM
mion

Quote:

Originally Posted by zbogorgon

can anybody help me with vdroop ?
what resistence of 50k VR is best?

I don't know what I am doing right now anyways. I used intel 805 and played with resistance and didn't have much effect. Finally I decided to go with zero to see what happens. Zero gets vcore as close as possible to the one set in bios but that's for 805
08-12-2006, 01:11 PM
[G.N.U.]Fragman

i dont understand why coretemp should be the right temp and not asus probe...it is the same probe they are measuring....just getting different results..and coretemp always insanely hihg....
08-12-2006, 01:58 PM
lawrywild

Quote:

Originally Posted by [G.N.U.]Fragman

i dont understand why coretemp should be the right temp and not asus probe...it is the same probe they are measuring....just getting different results..and coretemp always insanely hihg....

No p5wdh is reading a thermal probe under the cpu itself, on the motherboard
08-12-2006, 04:07 PM
yike99

asus p5w dh + e6600 usb keyboard problem.

System has been running fine at 3.3ghz but now when i am playing a game the usb keyboard disconnects and reconnects and it takes like 30sec to reinitialize. any ideas?
08-12-2006, 08:15 PM
Falkentyne

Quote:

Originally Posted by OBR

99% of "Problems" posted here are not really bugs or somethings, BUT only total amateurism of users ... This thred is only chaotic bunch of stupidity ...not serious "Fixes thred"
I have no serious problem with this MoBo, my E6600 runs @430FSB, and i have RAID0, Firewire ... everything OK, only ONE problem i have - crappy memory dividers ...so far ...

Prove it, please.

Thank you. You couldn't.

Please don't crap this thread k thx.
08-13-2006, 12:26 AM
hot_fifty

my E6600 will not be stable over 376-380FSB... but I have SPI 1m at 402FSB... What can I do to improve... Enabled SPD timings doesnt help and 1,6vmch does not... Maybe better cooling on NB? I have a 120mm 1200RPM on it
08-13-2006, 12:45 AM
alpha0ne

Quote:

Originally Posted by yike99

System has been running fine at 3.3ghz but now when i am playing a game the usb keyboard disconnects and reconnects and it takes like 30sec to reinitialize. any ideas?

Set ICH chipset to 1.20V :)
08-13-2006, 01:03 AM
hot_fifty

I want to be stable on 400FSB.. please help:_D
08-13-2006, 02:52 AM
Jimbo

I have just upgraded my bios from 701 to 1101 and now PC probe talks even more rubbish. It says my cpu is at somthing like 256c then goes back down to 30c. It says my cpu rpm is dodgy and my case temp is high.

I say this program is not very good at monitoring the P5W DH.

Interestingly I had no problems with it apart from system temp on bios version 701.
08-13-2006, 04:18 AM
hot_fifty

hmm that 256 is not bios related i think... But is there any improvment.. stability or overclock on 1101.. try everest ultimate edition and core temp to see temps
08-13-2006, 05:09 AM
Mykou

Quote:

Originally Posted by hot_fifty

hmm that 256 is not bios related i think... But is there any improvment.. stability or overclock on 1101.. try everest ultimate edition and core temp to see temps

with 1101 I can now boot with DDR 6400@1050 mhz 4-4-3-12 for benches

I'm still stable under prime with less Vcore 1.51 v@3.5 ghz ( 1.47v with pc probe 2 ( 3 hours blend test now and temp cpu is 56° :D ) but I replace NB heatsink yesterday maybe this could explain it too

I got 256° temps spikes too , but I noticed it comes when I run Cpu-z , strange but I don't mind really :)

Finally fine with this 1101 , and it works with ES...:toast:
08-13-2006, 06:11 AM
davefr

I did some characterization of FSB vs Vcore with all other factors being equal.

I started with FSB = 330 and went to 380 and gradually brought up Vcore until the point that my system went from unstable to stable. I plotted this and determined the slope of the curve.

I found that for every 4 mV Vcore increase you could get about 1 Mhz increase in stable FSB speed. In other words 330 FSB was the best I could do at 1.3 Vcore. However at 1.5 Vcore I could get to 380 FSB and remain stable. The Vcore vs FSB curve was almost a straight line. Although I didn't try it, it looks like approx. 1.6 Vcore would be required to get to 400 FSB.

I suspect that the slope is the same for most E6600's but obviously the starting points could be shifted depending on the specific device.

For my system I settled on a conservative 366 FSB = 3.3 Ghz at 1.475. I'm affraid to go >1.5 Vcore.

E6600
P5W DH
PCI=33
PCIE = 101
MCH, ICH, Mem = Auto
HP3 disabled
08-13-2006, 06:22 AM
mion

Quote:

Originally Posted by davefr

I did some characterization of FSB vs Vcore with all other factors being equal.

I started with FSB = 330 and went to 380 and gradually brought up Vcore until the point that my system went from unstable to stable. I plotted this and determined the slope of the curve.

I found that for every 4 mV Vcore increase you could get about 1 Mhz increase in stable FSB speed. In other words 330 FSB was the best I could do at 1.3 Vcore. However at 1.5 Vcore I could get to 380 FSB and remain stable. The Vcore vs FSB curve was almost a straight line. Although I didn't try it, it looks like approx. 1.6 Vcore would be required to get to 400 FSB.

I suspect that the slope is the same for most E6600's but obviously the starting points could be shifted depending on the specific device.

For my system I settled on a conservative 366 FSB = 3.3 Ghz at 1.475. I'm affraid to go >1.5 Vcore.

E6600
P5W DH
PCI=33
PCIE = 101
MCH, ICH, Mem = Auto
HP3 disabled

Did you try uping mch?
08-13-2006, 06:33 AM
unclean

Quote:

Originally Posted by Falkentyne

Prove it, please.

Thank you. You couldn't.

Please don't crap this thread k thx.

Reading through the thread is evidence enough, most of these are just silly non-MB related issues to do with user inexperience/ineptitude, and most of those that aren't have been answered multiple times.

If anything, this thread shows that there are only a couple of _real_ issues with the board and has made me more confident to get one :)
08-13-2006, 11:13 AM
Brahmzy

This was pretty much my experience with my retail E6600 on the DS3 as well. Unfortunately, it looks like when I get my P5W DH Monday, I will be no better off with it than I was the DS3. :( So much for 975X being better for the 9x+ chips.

Quote:

Originally Posted by davefr

I did some characterization of FSB vs Vcore with all other factors being equal.

I started with FSB = 330 and went to 380 and gradually brought up Vcore until the point that my system went from unstable to stable. I plotted this and determined the slope of the curve.

I found that for every 4 mV Vcore increase you could get about 1 Mhz increase in stable FSB speed. In other words 330 FSB was the best I could do at 1.3 Vcore. However at 1.5 Vcore I could get to 380 FSB and remain stable. The Vcore vs FSB curve was almost a straight line. Although I didn't try it, it looks like approx. 1.6 Vcore would be required to get to 400 FSB.

I suspect that the slope is the same for most E6600's but obviously the starting points could be shifted depending on the specific device.

For my system I settled on a conservative 366 FSB = 3.3 Ghz at 1.475. I'm affraid to go >1.5 Vcore.

E6600
P5W DH
PCI=33
PCIE = 101
MCH, ICH, Mem = Auto
HP3 disabled
08-13-2006, 12:00 PM
lawrywild

btw for me, my asus p5w undervolts by .05v so I'm fine running 1.55v in the bios for around 3.35 or something..

if you don't have a dmm then buy one..
08-13-2006, 12:04 PM
John600rr

I found that I needed the following voltages to get the following clocks:

1.40 = 333FSB Stable = 3000mhz
1.50 = 350FSB Stable = 3150mhz
1.55 =370FSB Stable = 3333mhz
1.65 = 400FSB stable for dual prime 32m, but crashes dual SP2004 and BF2

This is with everything else on Auto (Vmch, Vich, Vfsb, RAM, etc). Hyperpath disabled, etc.

Even trying to run 375fsb with 1.6Vcore and MAX MCH, ICH, FSB, makes to different at all. The only setting that helps my OC stabalize is Cvore.

Maybe my CPU has reached its limit. It runs about 30c idle/42c load even at 1.55vcore though. But I think it's the board.

I would recommend no one else buys this board until Asus releases a proper BIOS (or maybe another revision). You can find higher OCs and more stability with other boards for much less.

This will also put pressure on ASUS to release a better BIOS and help the rest of us out.
08-13-2006, 12:08 PM
lawrywild

Quote:

Originally Posted by John600rr

1.50 = 350FSB Stable = 3150mhz
1.55 =370FSB Stable = 3333mhz

wtf, no way lol :stick:
08-13-2006, 12:30 PM
fornowagain

Quote:

Originally Posted by John600rr

I would recommend no one else buys this board until Asus releases a proper BIOS (or maybe another revision). You can find higher OCs and more stability with other boards for much less.

This will also put pressure on ASUS to release a better BIOS and help the rest of us out.

Yeah that's going to happen:poke:

I don't need anything like those voltages and I'm quite happy with mine thanks.
08-13-2006, 04:25 PM
davefr

Quote:

Originally Posted by mion

Did you try uping mch?

Yes, I chose a point where I was on the threshold of unstable to stable and played around with mch. It didn't make any meaningful difference.
08-13-2006, 07:36 PM
noobzed

mine is fully stable at 400 x 9, 6600ES Step5

vcore in bios 1,55
vfsb 1,5
vmch 1,5

bios 801

2xsp2004
2xtoast
1xsuperpi 32m
1xprime95
1x3dmark2001 loop

during 1 night ( 8h ), no crash, temp is 51 for cpu, 60°c chipset in full
08-14-2006, 02:37 AM
hot_fifty

Quote:

Originally Posted by noobzed

mine is fully stable at 400 x 9, 6600ES Step5

vcore in bios 1,55
vfsb 1,5
vmch 1,5

bios 801

2xsp2004
2xtoast
1xsuperpi 32m
1xprime95
1x3dmark2001 loop

during 1 night ( 8h ), no crash, temp is 51 for cpu, 60°c chipset in full

On air, water or SS
08-14-2006, 02:59 AM
simonmaltby

FSB WALL TESTING RESULTS AND A CONCLUSION

I did some work last night regarding FSB wall on this board....

P5W DH deluxe with Bios 1101
E6700 OEM Step 6 B2
2GB OCZ 6400 Plat 4,5,4,15

Results:
I have been having real issues at 380FSB and Above. I tried out an E6600 and that worked up to 400FSB, but no higher.

Another post of the foum put me onto crystal http://crystalmark.info/download/index-e.html which lets you change the multi in windows on this board.

So I tried the E6700 at 9x and 8x to see what happened.
The only Bios setting that helped at all was to set the ram to SPD - no voltage changes let me go higher than 379FSB. With SPD on i could do 410FSB before it would go no further. I should point out that SPD sets my ram at 5,6,6,20 - miles out from what it should be.... this got me thinking...

Next I booted with SPD settings and used memset http://rv.page.cegetel.net.perso.cegetel.net/MemSet.zip to see all the ram settings. I took a screen shot and saved the memset settings.

Then I rebooted changing back to manual RAM settings in the bios 4,4,5,15

When in windows I opened memset and changed all the settings apart from 4,4,5,15 to be the same as the screen shot at SPD.

I was then able to go right up to 440FSB before i suffered any issues.

Summary:
1. FSB Wall at 380FSB with manual Ram settings in Bios
2. FSB Wall at 400FSB with SPD ram settings in Bios
3. FSB Wall at 440FSB with manual Ram settings in Bios but changed to match SPD in windows with memset.

Conclusion:
Asus need to provide access to far more RAM settings in the Bios. This might well be the cause of the FSB wall and would explain why different people get the wall at different points... down to when the RAM fails due to its settings.

Show 100 post(s) from this thread on one page