ASUS P5W DH - Problems + Fixes Thread

[secretworld]

i run 355 24/7 and i'm going higher when i get better cooling...
what i don't understand is how all you guys are having problems above a certain point... do you have the pci-e locked?

Yes PCIe fixed @100 (and PCI @ 33) and nothing helps. No voltages, no relaxing ram timings. Seems like like one part is overheating and producing errors but all temps are really low.

[Random Murderer]

Yes PCIe fixed @100 (and PCI @ 33) and nothing helps. No voltages, no relaxing ram timings. Seems like like one part is overheating and producing errors but all temps are really low.

do you have hyperpath 3 disabled?

[SkyYYZ]

Hey Psitech,

Try setting the voltage to auto... my E8400 is running smooth. And make sure your RAM voltage is set correctly and to Auto timings (by SPD I think is what I selected.) Computer uses stock speeds and RAM is 1:1 using different timings than factory. If you get Windows to boot then you can try different OC settings if you want.

My 8800GT was running at half clock until I finally reinstalled Windows as a last resort. All was fine after that... machine is running sweet. Going to attempt overclock to 3.6GHz soon using stock cooling, which apparently E8400 does without effort or extra voltage.

Keep us updated. BTW I'm using Bios 2602.

Jay

I tried my E8400 again last night with bios 2602 and got the exact same results as I did with 2504. It would boot with no problem at all but reboot just after loading windows. I put my e6600 back in and all is well.

Do you guys think it has anything to do with the revision of the board? I don't remember the exact revision of mine but it only goes to 1.65 for the NB. The chip information reported is accurate, but when loading all bios defaults and then looking at the reported cpu voltage in the bios it reads at 1.75. The lowest voltage available for me to choose is 1.375 and I know that this is WAY off.

Any ideas?

[Psitech]

Hey Psitech,

Try setting the voltage to auto... my E8400 is running smooth. And make sure your RAM voltage is set correctly and to Auto timings (by SPD I think is what I selected.) Computer uses stock speeds and RAM is 1:1 using different timings than factory. If you get Windows to boot then you can try different OC settings if you want.

My 8800GT was running at half clock until I finally reinstalled Windows as a last resort. All was fine after that... machine is running sweet. Going to attempt overclock to 3.6GHz soon using stock cooling, which apparently E8400 does without effort or extra voltage.

Keep us updated. BTW I'm using Bios 2602.

Jay

It looks as if the E8400 isn't going to work with my P5W. I've literally tried everything at this point. I've tried different voltages for mem, cpu, mch, it didn't matter. I've tried every possible thing I can think of. I did a full cmos reset and even did a long cmos reset and that didn't even help.

The thing that still bothers me is that it seemed to be defaulting to the correct default voltage (1.18) after I did the cmos reset, but the lowest voltage available to me was still 1.375. What made it more weird is when I set the cpu volts to 1.375, the bios hardware monitor showed 0.98. I could crank the voltage and it would barely move in the hardware monitor status. As a last result I set the cpu voltage to 1.65 just to see what it would read as the actual voltage and it was just 1.23v in the bios monitor section. Something is majorly screwed. I don't know if it's my board or the processor.

No matter what I tried in the bios, it would either reboot before loading into windows or reboot seconds after loading windows. I even tried taking 2 sticks of ram out and that didn't help either.

The thing that REALLY sux now is I have my E6600 back in and I can't change the cpu voltage from "auto". I've even got speedstep and c1e turned off. This board is really pissing me off now. Sux that I've got to wait a couple of weeks till I can get a P35 board.

Update: I figured out the cpu voltage problem with my E6600. I had to do another full cmos reset to get any voltage other than "auto" after putting the e6600 back in. This makes me feel a bit better. I may give it this board one last shot tomorrow with the e8400. If it doesn't work after that I'll give up and wait for my P35.

[rvltion909]

Im just about done here. I've tried configuring all the settings and performing all the tests I've read about and my results have been the same...

ERROR/CRASH

My most recent configuration was:

FSB 333
Vcore 2.2625
RAM: DDR2 667 1:1 5-5-5-15 2.0V
Hyperpath 3 disabled
PCI-e set to 100
PCI Clock Synchronization 33:33


I initially thought my problems might have been stemming from my RAM so I ran memtest for 12hrs with no errors.

I then began running the Prime 95 tests. I first ran the combination tests which had temps around the high 50's. It ran for about 8hrs then produced an error report.

I bumped up Vcore and ran again...an error after a couple hours.

I changed vcore to auto and ran the small fft test. The temps were hung at about high 50's/low 60's. It shut down at around the 1hr mark.

My most recent was running small fft test in Prime95 with 2.2625 Vcore, Hyper 3 disabled and all the same settings mentioned above.

I got a shutdown in a little over an hour. The temps were around mid-high 60's


Im grasping at straws here guys. Does an end-all solution exist for my set up? Im just about ready to give up on over clocking here. Its a brand new q6600. I see posts from people who are running stable at well above 333 here and Im wondering what the hell Im doing wrong and if the 25% increase is even worth it at this point.

Like I said before, I run this PC for strictly DAW purposes and this has been the most unproductive, creativity-killing waste of time.

t_ski, Larry-is it worth trying for 333 or higher anymore or has this board been a waste of $ in re: to over clocking?

[Random Murderer]

Im just about done here. I've tried configuring all the settings and performing all the tests I've read about and my results have been the same...

ERROR/CRASH

My most recent configuration was:

FSB 333
Vcore 2.2625
RAM: DDR2 667 1:1 5-5-5-15 2.0V
Hyperpath 3 disabled
PCI-e set to 100
PCI Clock Synchronization 33:33


I initially thought my problems might have been stemming from my RAM so I ran memtest for 12hrs with no errors.

I then began running the Prime 95 tests. I first ran the combination tests which had temps around the high 50's. It ran for about 8hrs then produced an error report.

I bumped up Vcore and ran again...an error after a couple hours.

I changed vcore to auto and ran the small fft test. The temps were hung at about high 50's/low 60's. It shut down at around the 1hr mark.

My most recent was running small fft test in Prime95 with 2.2625 Vcore, Hyper 3 disabled and all the same settings mentioned above.

I got a shutdown in a little over an hour. The temps were around mid-high 60's


Im grasping at straws here guys. Does an end-all solution exist for my set up? Im just about ready to give up on over clocking here. Its a brand new q6600. I see posts from people who are running stable at well above 333 here and Im wondering what the hell Im doing wrong and if the 25% increase is even worth it at this point.

Like I said before, I run this PC for strictly DAW purposes and this has been the most unproductive, creativity-killing waste of time.

t_ski, Larry-is it worth trying for 333 or higher anymore or has this board been a waste of $ in re: to over clocking?

what are your fsb termination voltages and mch voltage? set your mch voltage to 1.65. fsb just ratchet up in single notches until it's stable.

[secretworld]

do you have hyperpath 3 disabled?

yes disabled, with hyperpath 290 is the highest FSB I can get.

[Lurker246]

i run 355 24/7 and i'm going higher when i get better cooling...
what i don't understand is how all you guys are having problems above a certain point... do you have the pci-e locked?

Isn't it a limitation with the 975x chipset and Quads? For the most part anywhere between 333 - 360 could be stable, it seems to be a lottery what you'll be able to reach and keep stable with a quad.

I've only seen I think 1 guy that has managed to get it above 360 stable and that was with a completely watercooled mobo- NB,CPU,mosfets...etc.

The highest I was able to reach was 360 X 9 3.2Ghz (I've got 6 x 120mm fans on it) but the onboard audio would completely freak out and almost pop your ear drums with a high pitched whine before it died.

[Donseba]

when i start the pc the detection of usb devices is too much, it´s normal ?

[Random Murderer]

Isn't it a limitation with the 975x chipset and Quads? For the most part anywhere between 333 - 360 could be stable, it seems to be a lottery what you'll be able to reach and keep stable with a quad.

I've only seen I think 1 guy that has managed to get it above 360 stable and that was with a completely watercooled mobo- NB,CPU,mosfets...etc.

The highest I was able to reach was 360 X 9 3.2Ghz (I've got 6 x 120mm fans on it) but the onboard audio would completely freak out and almost pop your ear drums with a high pitched whine before it died.

i don't know, the only problems i've experienced have been heat, and only pertaining to the cpu itself. maybe because i'm on a b3 i'm not experiencing what you guys are?

[rvltion909]

what are your fsb termination voltages and mch voltage? set your mch voltage to 1.65. fsb just ratchet up in single notches until it's stable.

FSB term is set to auto. Just set the mch to 1.65 and have been stressing with Prime 95 (small fft) for almost 3hrs. No errors yet. Temps are at about 58-60.

What's the difference between FSB term. and Vcore voltage?

BTW during these failed stress tests...the next time I try to boot up it plays dead. I'll have to switch the PSU off and when I boot up again it posts the "failed" overclock msg in the BIOS (anyone else get this? is it normal?)

[Random Murderer]

FSB term is set to auto. Just set the mch to 1.65 and have been stressing with Prime 95 (small fft) for almost 3hrs. No errors yet. Temps are at about 58-60.

What's the difference between FSB term. and Vcore voltage?

VCore is the voltage being supplied to the processor itself.
FSB Termination:

source -> line -> component -> short line -> termination

the "lines" in this case are signal traces. works a lot like a SCSI bus. high speed switching operations can cause reflections on the line (in essence, this is resonant noise caused from high-speed switching on the lines as the memory controller gates on and off to place data on the bus, nothing more than rising and falling voltages). clearly enough, the faster the signal switches (higher frequency memory) the more noise.

termination resistors, used in passive termination environments, are exactly matched to the target frequency for operation based largely on trace length, ESR (equivalent series resistance) and the over capactive/inductive nature of the circuit, as well as some other things well out of the scope of this post. problem is that this is often matched for a specific frequency...which as we know is not so cool for overclockers. enter the active termination system. this actually uses a voltage bias to set final line resistance value so that the user can tune for better operation when overclocking.

this method of tuning is largely trial and error as you have no way of know the specification of the circuit or have any idea of the calculations need to find the "perfect" value. so anway, the answer is, strangely enough, whatever works best.

hope this helps.

FCG

[Nu-B]

Hey, sorry to just jump in with my P5w issue, but I thought you guys would
have some ideas or pointers.
Hopefully my system specs will show up below.....

I've just put together my system, I have never OC'ed before, hence my handle
of "Nu-B". The computer runs fine, steady as a rock. Using Intel TAT, it appears my E6600 cores are running at 57/55 at idle, and 65/59 at 5 minutes
of 100% cpu activity. Which is WAY too hot for my tastes. I've tried Speedfan
to increase the stock CPU cooler fan (pwm) from its slow 1600 rpm, but no-go.
I've enabled/disabled the AIQuiet(?) in the BIOS, and done the same with the
Q-fan control. Changed the specs all around in Speedfan, to no avail.
CPU fan just rotates at 1600, no changes. Any ideas?

If I have to, I'd drive the CPU fan off the PSU with a potentiometer, but I'd
prefer not to.

[rvltion909]

I had a similar problem. What is your OC config?

I've never used the stock cooler but the problem I had with my Freezer Pro with similar temps was due to an improper mount.

Those bastards are a "bich" to get in there just right. I had to take the board out to actually see that is wasnt mounted right...at all. You might not have to and if anybody has any tips on mounting them correctly the first time... without taking the board out or breakin the flippn CPU Im all ears

Im always scared Im going to put too much pressure on it, slip and knock off one of the batteries or something. I got some good advice from somebody here who spotted the sign right away. Check you mount.

BTW guys, Im at 12+hrs stress testing with Prime95 with no errors (longest its ever gone!) Im going to try to run the full 24hrs. Looks like the MCH voltage may have been the culprit.

The advice of a Random Murderer has never been so useful.

[JacKz5o]

The FSB won't go too high

[next-jin]

Hey guys I'm having a hell of a time getting anything meaningful out of my board. Here is my setup.

e6750 w/Zalman 9700
P5W DH Deluxe
2 Gb PC 1066
8800GTX
2x Raptors in Raid 0

for some reason I cannot get this thing to post over any adjustments what so ever,

What is the basic settings config for a solid overclock I could expect with this setup?

Hyperpath 3 Disabled
MCH voltages etc?

[w2richwood]

do some reading from first page on lots of good infor.
Rich

[rvltion909]

yup, Im done-spoke to soon

after the 14+hr run I got a reboot. Bumped it down to 2.8 Mhz and it posted fine. I threw my DAW test at it (8-audio tracks, 8 cpu intensive vst/midi tracks and loads of effects). It got pushed to about 55% CPU use and high 50's in temps.

Shut it down, moved it back to my room and tried to boot back up 3 hrs later. Nope, wont post. I cant even load defaults to boot. If Im able to boot up and load defaults anytime in the near future...thats where I'll stay.


Im setting a $100 limit on my next board and it wont be ASUS. Im pretty sure I've covered all the bases and addressed all the variables here and its not happening.

[Random Murderer]

yup, Im done-spoke to soon

after the 14+hr run I got a reboot. Bumped it down to 2.8 Mhz and it posted fine. I threw my DAW test at it (8-audio tracks, 8 cpu intensive vst/midi tracks and loads of effects). It got pushed to about 55% CPU use and high 50's in temps.

Shut it down, moved it back to my room and tried to boot back up 3 hrs later. Nope, wont post. I cant even load defaults to boot. If Im able to boot up and load defaults anytime in the near future...thats where I'll stay.


Im setting a $100 limit on my next board and it wont be ASUS. Im pretty sure I've covered all the bases and addressed all the variables here and its not happening.

you think maybe it has something to do with your room?

[w2richwood]

well asus boards are stable as a rock i have a hard time buying anything else its that board needs rma or one of your other parts are bad. or something your doing or not doing so what ever makes you happy go for it but ive had many asus for years a happy as can be and will stay with them tell something proofs better
Rich

[MacClipper]

Seems no one has posted a E2160 in this thread so far so here goes. Finally demoted the P5W from main rig so bought a cheap cpu for it and running at Auto Vcore - one of my main dislikes about this mobo's BIOS since I prefer to have EIST/C1E active. Using XP90c, AC Ryan 120mm fan and Kingston VR D9DCL sticks (2.0V), Prime95 stable >2hrs. Couldn't even reach 9 x 333FSB with OCCT stability at Auto Vcore, pity!

[P5WDHdeluxe]

i can't see in bios any option, if our cpu reach a specific temp.(i.e over 70c) our system to be shut down... how can i configure this one?

anything on that?

[Falkentyne]

Isn't it a limitation with the 975x chipset and Quads? For the most part anywhere between 333 - 360 could be stable, it seems to be a lottery what you'll be able to reach and keep stable with a quad.

I've only seen I think 1 guy that has managed to get it above 360 stable and that was with a completely watercooled mobo- NB,CPU,mosfets...etc.

The highest I was able to reach was 360 X 9 3.2Ghz (I've got 6 x 120mm fans on it) but the onboard audio would completely freak out and almost pop your ear drums with a high pitched whine before it died.

I got 370 stable on my Qx9650. Using x-fi though. 380 fsb wasn't prime stable at 1.3875v and I didn't try to go any higher on the vcore. 400 fsb didn't post. The same frequency was stable at much lower vcore at 333 fsb/higher multi. This was at 4-4-4-12 timings and 1.65 mch.

[next-jin]

Ok I cannot get this thing to boot into windows with the following settings. It will POST but will not get to the windows logon, it'll just remain black.

CPU Freq: 400
DRAM Freq: 800
Performance Mode: Auto
PCI-E Freq: 100
PCI Clock Sync: 33.33
Memory Volt: 2.2 (as per rating @ 1066)
Vcore: 1.4
FSB Volt: 1.3
MCH: 1.65
ICH: Auto
Memory Timings: 5-5-5-15-5
Hyperpath 3: Disabled
DRAM Throttiling: Auto

I am using Raid from the chipset and not the JMicron controller
I am using the onboard soundcard
BIOS: 2301

System:

e6750 w/9700 AS5
P5W DH Dlx
8800GTX
2x Raptors Raid 0
1 IDE 500Gb
PC Power and Cooling 750w Silencer

With everything at stock (I cannot overclock) my temps are:

Idle -
CPU 95f
NB 110f

Full load -
CPU 51c
NB ?

I shouldnt be hitting a FSB wall because I am not using the SPD settings and disabled Hyperpath 3.

Any suggestions?

[Lurker246]

I got 370 stable on my Qx9650. Using x-fi though. 380 fsb wasn't prime stable at 1.3875v and I didn't try to go any higher on the vcore. 400 fsb didn't post. The same frequency was stable at much lower vcore at 333 fsb/higher multi. This was at 4-4-4-12 timings and 1.65 mch.

370 on a Quad is excellent well done

I've got an old Audigy lying about but it sounds like crap in vista so I've left it residing in my old rig. If you've ever heard the high pitch whine from the on board you just know it's not healthy and the first time I heard it I thought it was an air raid siren, then realised it was the pc audio and promptly ripped the plug out of the wall socket in a panic!

My system did boot at 400 fsb on Lawry's G0 BIOS, 400 X 8 (1.85 mch, Auto SPD, 1:1)- even made it as far as windows but crapped out after login.

333 X 9 is steady as a rock for me though and I'm more than happy with it.