ASUS P5W DH - Problems + Fixes Thread

[SS_The_Demon]

Does the board still boot correctly if you clear the CMOS with the jumper (after unplugging or turning off the power supply switch?).

I don't know, why wouldn't it? Should I try this? If so, for what reason, since the board seem to be working fine now (@333FSB that is)

EDIT:update, I downloaded SetFSB, made 100% sure i chose the right clock generator, booted into BIOS and set FSB termination voltage to 1.5 and vmch to 1.85 but let the FSB stay at 333. Strangely enough, it didn't POST, WTH????

Rebooted, set FSB termination to 1.4 and vmch to 1.75, this time it booted, and I got it up to 360FSB using SetFSB. Choosing 370 didn't go too well, as soon as I hit "get FSB" it froze. Sitting @ 333FSB yet again, frustrated as hell. And to think that some guys have been able to get 380FSB at 1.65V vmch as their 24/7 setting, is even more frustrating. But what about flashing BIOS? Using 1602 currently btw.

And to think that it didn't even POST when the only thing I changed was the vmch and fsbtv. I'm thinking that the board has some kind of overvoltage protection as well. And when POSTing the computer seems to imply this as well with the already familiar "overclocking failed or overvoltage failed". Isn't there anyone here who can tell me what I'm doing wrong?

[Aerics]

Aerics Try to set memory timings to SPD, our board likes it more and overclocks then higher.

I trayed it an changed the FSB again to 360. My system crashed after 2 min. I change the voltage to 1,65V and 1,4V and the vcore to 1,5V, but the system crasehd again after 6min.

I don`t figure out what the problem is.

And is it normal that i can`t chose obove 1.65V for the northbridge? Is this a Bios problem?

[G40RoCkEt]

I trayed it an changed the FSB again to 360. My system crashed after 2 min. I change the voltage to 1,65V and 1,4V and the vcore to 1,5V, but the system crasehd again after 6min.

I don`t figure out what the problem is.

And is it normal that i can`t chose obove 1.65V for the northbridge? Is this a Bios problem?

If you have a P5W DH with Revision 1.02g is normal.

The maximum is 1.65v for this revision.

(you can see the revision number near to the first orange dimm socket)

Btw, anyone already try config wifi in w7?

I cannot share my internet to my laptop with WIFI. (In XP and Vista i have no problem).

Already disable windows firewall, antivirus, update the wifi driver to the last in Realtek website.. still no have internet in laptop..

[Falkentyne]

@SS_The_Demon:

I faintly recall something about 1.5 vFSB not working correctly on some board versions, like it setting too LOW of a FSB or something else. It was way back in the thread, though. If 1.4v fsb worked but 1.5vfsb didnt, at the same other settings, then that's why.

I also know that vFSB is somehow indirectly linked to vmch...like, setting 1.3 vfsb and 1.75 vmch actually gives 1.82 vmch (tested by someone else with a multimeter). 1.4 vfsb+1.85 vmch gave 1.96 vmch....(it was something like that....)...it takes ages to find the chart tho (only found it once).

It was like a .05 mch boost for every step in vfsb...

[SS_The_Demon]

@SS_The_Demon:

I also know that vFSB is somehow indirectly linked to vmch...like, setting 1.3 vfsb and 1.75 vmch actually gives 1.82 vmch (tested by someone else with a multimeter). 1.4 vfsb+1.85 vmch gave 1.96 vmch....(it was something like that....)...it takes ages to find the chart tho (only found it once).

It was like a .05 mch boost for every step in vfsb...

Now that you mention it, I faintly recall that I've read something like that myself a long time ago. But anyway, I tried several options to get it to boot at 360FSB, but no luck except I got that weird screen 2 or 3 times that I told you about earlier. A few times i got lucky and made it past POST and could even see the XP loading screen, but after that either it rebooted or just gave me a BSOD. BTW, got an interesting question here...

Why is it that sometimes when I try to boot at 360FSB or more, I get an "Intel CPU µCode error"? Tried using 1.35vcore and as low as 1.25vcore but it doesn't seem to matter.

Getting annoyed with this mobo, and I really could use some higher clocks on the CPU. @ 2.4GHz my 3dmark06 scores is as follows:

4933 Shader Model 2
6162 SM3/HDR
2113 CPU

11076 Total

And @ 2.4 stock my memory runs @ 800, which gives me higher scores than 1:1 (533MHz). Now, with the CPU @ 3GHz (25% OC) and the memory @ 667 I get the following:

6072 SM2 = 23% increase
6959 SM3/HDR = 13% increase
2624 CPU = 24% increase

13324 Total = 20% increase

Running the GPU benchmark in Crysis show the same trend, with the minimum fps being 19.62 and 23.27 for 2.4 and 3GHz respectively. That's an increase of 18.6% right there, proving that my CPU, which was the 3rd fastest desktop CPU in mid 2006 btw, is actually bottlenecking my GTX260

Gaming is the most demanding thing I do on the computer, and I play alot. So you can only imagine the frustration when you know you have a CPU which can do 3.6 on only 1.3vcore, but is being held back by the mobo. Does it help oc'ing if you remove the wlan card? Do you have to remove the mobo from the case in order to remove the card?

ANY AND ALL SUGGESTIONS are very welcome at this point, there must be something I've missed, seeing other pushing past 400FSB for 24/7 use as I already said. I'm gonna stop whining now btw...

[Supa Chiney]

Quote:
Originally Posted by Falkentyne View Post
Remove one stick of memory and see if the problem goes away. Or switch the remaining stick. Memory that is dying (like micron D9's) will cause this to happen.

Raise the memory voltage to 2.1v .....does the problem go away then?

this sticks are brand new, i did that when i first installed them, i forgot to mention that this problem started when i added a pair of the same type i had before (on my sig) but those were different version, so i though that was the problem, that's why i bought the new ram.

I cold booted twice this morning without issues will, report back in a couple days or later if problem stops/continues

is it safe to run them at 2.1v even if they are rated to run at 1.8v ?

the only way around i found to "fix" the problem is to switch the PSU everytime i'm gonna shutdown and it boots everytime i turn it on

[Falkentyne]

People have hit over 400 FSB with E8x00 cpu's, but they were all using the 1.04g board. And only the 1.04g works correctly with proper vcore settings on e8x00 cpu's; I know 1.02 is limited to auto and 1.45+v, and 1.03 I'm not sure.

You do have to remember that the B2 stepping E6x00 and X6x00's were pretty much limited to between 3.4 to 3.8 ghz on air, and 3.8 ghz often took over 1.5v to get there. If you boot and suddenly get a CPU ucode error during an overclock, its always caused by (1) insufficient vcore, (2) unstable RAM (most likely), (3) unstable northbridge (almost as likely, and can cause very similar symptoms as 2).

I think most E6x00 cpu's could do 3.6 ghz at 1.5v or more.
The B2 steppings were a dog though. The G0 steppings could do 3.8 or even 4 ghz with enough voltage.

[marzliak]

People have hit over 400 FSB with E8x00 cpu's, but they were all using the 1.04g board. And only the 1.04g works correctly with proper vcore settings on e8x00 cpu's; I know 1.02 is limited to auto and 1.45+v, and 1.03 I'm not sure.
.

Confirmed, i´m using a 1.02 edition. Bios 2901.

Vcore auto only @ e7400 and normal for my old E6600.

Any ideas?

[DJBamby]

Clear CMOS.
Sett Vcore in BIOS - 1.700V - real 1.28V
My Е6600@3,6 (400х9)_1.500V in bios
My E7200@3,8Ghz (400x9.5)_1.700 in bios

[PaVi90]

Clear CMOS.
Sett Vcore in BIOS - 1.700V - real 1.28V
My Е6600@3,6 (400х9)_1.500V in bios
My E7200@3,8Ghz (400x9.5)_1.700 in bios

Uh? Are you saying that there is a Vdrop of more than 0,4V?

[DJBamby]

Bios-1,700V , Full load - 1,256V

[roger_h99.nor]

This vdroop can't be right..
The P5W DH usually have a droop around 0.04V.

Maybe your board is faulty in some way?

[G40RoCkEt]

This vdroop can't be right..
The P5W DH usually have a droop around 0.04V.

Maybe your board is faulty in some way?

Thoose vdrops numbers was wrong..

Do a good clear cmos to check this out or try another CPU-Z version.

In my E8600 when i select 1.40v (minimal) in my bios, in CPU-z report's me between 1.37-1.39v..

So the difference isn't SO HIGHHHHH..

[SS_The_Demon]

People have hit over 400 FSB with E8x00 cpu's, but they were all using the 1.04g board. And only the 1.04g works correctly with proper vcore settings on e8x00 cpu's; I know 1.02 is limited to auto and 1.45+v, and 1.03 I'm not sure.

Well I can inform you that I can select a vcore as low as 1.225V in BIOS, the board is a 1.03G. So 1.03G revisions are good for 45nm CPUs right?

You do have to remember that the B2 stepping E6x00 and X6x00's were pretty much limited to between 3.4 to 3.8 ghz on air, and 3.8 ghz often took over 1.5v to get there. If you boot and suddenly get a CPU ucode error during an overclock, its always caused by (1) insufficient vcore, (2) unstable RAM (most likely), (3) unstable northbridge (almost as likely, and can cause very similar symptoms as 2).

I think most E6x00 cpu's could do 3.6 ghz at 1.5v or more.
The B2 steppings were a dog though. The G0 steppings could do 3.8 or even 4 ghz with enough voltage.

Well, like I said, when I ran 3.6GHz I only selected 1.3vcore in BIOS and it ran Orthos for several hours without problems. And I didn't get the µCode error then, plus when I got it now it didn't seem to make any difference no matter what the vcore, at least 1.35V didn't. However, last time I reached 3.6GHz I used 2 Corsair 1GB sticks rated 800MHz 4-4-4-12 @ 2.1V. But now I use 2x2GB Corsair 800MHz 5-5-5-18 @ 1.8V. But those are only a few months old, and I am running them below their max specified speed and timings, but still using 1.8V.

So I'm definately thinking it's the motherboard (northbridge). But I'm still gonna try and go higher whenever I feel like I'm in the mood. But it's so annoying. There are still some combinations of settings in BIOS that I haven't tried.

[SS_The_Demon]

Bios-1,700V , Full load - 1,256V

Whoa, whoa, WHOA! You might wanna lower the vcore on that thing before you fry it, 45nm CPUs are only rated at 1.3625V for safe 24/7 use, and 1.45V for benching Heck it's even beyond the benching voltage for their 65nm CPUs which is 1.6V so take it easy alright

Look at a post I made earlier, CPU-Z showed something like 1.2xxV, but I had 1.45 selected in BIOS. Like G40RoCkEt said, update CPU-Z to the newest and see if it still shows the same value. Better still, check in BIOS. Even better, check with a multimeter.

[DJBamby]

Rev. 1.02G



Bug ???

Look my best FSB with this mainbord- 450Mhz http://img241.imageshack.us/img241/5...4053mhzuc6.jpg

[G40RoCkEt]

I think that the people talk here is about this Vcore.. :

[DJBamby]

Sorry for my bad english.......

Auto = 1.040V
1.400V=0,0992V
1.700V=1.27V (for my best overclock)

Test all Bios, clear CMOS. Never readout Vcore more 1,27V with Е7200 and E7300. E6600 working good!
My be revision is old for this CPU

[u-ultima]

the only way around i found to "fix" the problem is to switch the PSU everytime i'm gonna shutdown and it boots everytime i turn it on

i got this problem after trying to update my asus p5w dh bios using asus update,and it some how failed after that i had to turn off and turn on a few times to get me through the windows boot screen.now i have left it on 24x7, i m afraid that my hard disks may get damaged due to the power off on thing all the time to see the post screen.

[SS_The_Demon]

Sorry for my bad english.......

Auto = 1.040V
1.400V=0,0992V
1.700V=1.27V (for my best overclock)

Test all Bios, clear CMOS. Never readout Vcore more 1,27V with Е7200 and E7300. E6600 working good!
My be revision is old for this CPU

But don't look at the voltage shown in BIOS! Look at the screenshot G40RoCkEt posted. That's the place where you adjust your vcore, and you shouldn't have to use 1.7V for that CPU, you will fry it. Ignore the 1.272V you see in the picture you posted, apperently your motherboard doesn't support that CPU, so it shows the wrong value. Try setting your vcore to 1.45V, if it works then try 1.3625V and if that works as well, try to go lower step by step, and after every decrease in vcore boot into Windows and stress the CPU to see if it's stable.

You cannot possibly need that much voltage, it will only DESTROY your CPU!!! For your information, 65nm CPUs like my E6600 need higher voltages than 45nm CPUs to run at the same speed, and I only needed 1.3V to reach 3600 MHz with my E6600.
Just trying to warn you

[Yolanda]

If it's a real 1.7V then CPU will be very hot under any work, it's easy to check.

[DJBamby]

Hey, I'm not a newbie, but because of my bad english I asked a friend of mine to translate everything about the problem with the E7000 CPU...
Need to clarify something... that major vdroop happens only when I put an E7000 CPU in the socket... with all other CPUs it's OK... the Vcore setting is correct and everybody are happy... only when I put E7200/E7300 CPU in the socket, that big vcore difference between real setting and the readout happens...



Bios 1.400V



can there be a problem with the readout - wrong readout, but the setting is OK... like i'm setting 1.7V Vcore, it reads 1.27V, but actually it's 1.7V?

something more... check out the picture:



With 1.7V setting, you can see the real readout on the voltmeter... any suggestions?
I have this board since 2006 and thus far i've installed more than 30 CPUs to test out... that very problem with the Vcore happens only with the E7000....

[BobyTT]

hey DJBamby , nice to see that you start to post at XS also.

[roger_h99.nor]

This is not droop at all - droop is the fall in vcore from idle to load.

Since I don't own a E7000 - is it possible to boot this cpu at 0.86?!

You may consider checking your reading with a second DMM - no offense, but it looks kinda cheap to me

[SS_The_Demon]

This is not droop at all - droop is the fall in vcore from idle to load.

You may consider checking your reading with a second DMM - no offense, but it looks kinda cheap to me

Are you sure about the vdroop thing? That vdroop is the difference in the voltage between idle and load?

Agreed on the second statement though, try changing voltmeter or at least, change the battery as it shows the low battery symbol. I have noticed that on at least some meters they can show some very obscure voltages when the battery is low.

DJBamby: - The last screen you posted, this one:

http://img508.imageshack.us/img508/1889/bios1700v.jpg

Did you remember to save and reboot here, so that 1.7V is actually applied? 0.58V difference between the setting and the multimeter sounds really odd. Have you tried lower the vcore as I suggested? If so, what happens, does it boot/POST?

EDIT: Have you tried more than one E7000 series CPUs? What BIOS are you using?