ASUS P5W DH - Problems + Fixes Thread

[MarcusTaz]

Did a quick Google and found this article about "loose/bent pin" chassis intrusion jumper:
http://blogs.ittoolbox.com/windows/a...n-system-15608

If the jumper is not "loose" and verified it's over the correct pins: (see attached pic)
- unplug AC power
- CAREFULLY double-check intrusion jumper and pins for "tightness"
- check PCB mounting for odd shorts
- disconnect all USB devices, especially powered HUBs (in case of a "sneak-circuit" supplying +5sbvdc to intrusion circuit)
- clear BIOS with jumper (10sec)
- connect only keyboard and USB port if needed for flashdrive, else floppy
- reconnect AC power and pray

If all fails, guess its time to request replacement BIOS chip from ASUS Support?

Best of luck to you!

EDIT: just found more stuff using Google "ASUS intrusion" search term
http://www.digit-life.com/forum/0003/000387.html

clipped from above thread:
Dr Fat Chick - Junior Member
I had this problem with my brand new A7v333 and fixed it successfully:
If you look on the Asus web site you can find the fix tucked away in a faq - it suggests removing the existing jumper, rebooting (yes, you'll get the error but now correctly because the chassis alert pins are bare).
Now jump the pins with a NEW jumper cap (should ship with the board) and....huzzah!! immediate boot....at least that fixed mine.
It's still a bit worrying that this problem crops up on so many Asus boards though.

Nice find man hope this helps him out...

[lawrywild]

Can someone post how to flash using AFUDOS211 and Lawrywilds 2004 bios..
I have not flashed using dos in many years..
I kmow I have to put AFUDOS211 on usb key then put bios on aswell..
Then what?
reboot then do what to get it to flash properly?
Thanks

Have you made the usb drive bootable?

This is my favourite guide: http://www.weethet.nl/english/hardwa...omusbstick.php

Once you made it bootable, put afudos.exe and 2004.rom on the drive.

In bios change the usb drive in usb configuration to "FORCED FDD"

Then save changes, tap f8 on POST and select to boot from usb drive.

Once dos is loaded, type:

afudos /i2004.rom /p /b /n /c /reboot

note the i after the /

[Polynikes]

Hi guys, I've been playing with my OC settings now that I have my watercooling kit installed, but I've been hampered by this damn 360 FSB wall. I've tried putting my RAM on SPD settings, but that doesn't help. (Strangely, when I tried the SPD setting at a lower FSB speed that worked, it didn't boot at SPD, but at the speed that was selected right beneath the FSB setting.) So, anyways, I've turned off all the extra memory options, the CPU options, etc. I've gotten my system to boot and run two Orthos instances for 10 minutes with no problems at FSB 350, RAM at 875mhz 4-4-4-12 with 1.325 vcore and 1.65mch, but upping the voltages to get higher FSB aren't working at all. I've tried doing all the things I could find in this thread and elsewhere, but nothing has helped. All I want is 400 FSB. That's it. I'm not trying to break records, I just want to run 1:1 with tighter RAM timings at DDR2-800. I'm using the 2004 BIOS, by the way. Was I a lucky winner in the "let's see who gets a poor overclocker" sweepstakes?

I miss the days when heat was your only enemy. Just throw good enough cooling at it and it'll go. Not anymore it seems.

[bichi]

Asus P5W DH Help
Im removed wrong jumper and now... Chassis Intruded !
Fatal Error... System Halted!

Two more possible "intrusion detected" solutions:
- not specific to P5WDH, but worth a try
- from ASUS FAQs

Server will show Chassis intruded! Fatal error message:

Server will show Chassis intruded! Fatal error message
The error message will appear due to chassis intrusion sensor detects the server chassis has been opened. When user encountered this issue, they can eliminate the error message by following the steps below:

1. Shut down the system, close the top or sider cover properly and secure the screws of the cover if available.

2. Power on the system and the error message will show again. Please press the Reset button on front panel.

2. The error message will show persistently after system restarts. Please press the Reset button on front panel again

3. Upon restarting for 2nd time, the error message will be eliminated and the server will boot properly then.

*************

System goes directly to BIOS utility with error message:

Due to the fact that system detects chassis is opening during boot up, if you would like to disable this function, please refer to the user manual to find out the location of chassis alarm lead (4-1 pin). This lead is designed for hassis with intrusion detection feature. Please power off the system and use a jumper cap to short the pins labeled "Chassis Signal" and "Ground".

After power on for the first time, the system will go to BIOS utility directly and warn user with message stating "chassis opened" previously. Please go to [Exit] menu and select [Exit Saving Changes]. After reboot, the system will enter boot sequence successfully.

By the way, you also can also choose to close the chassis so the message won't show after second reboot.

*****************

ASUS SUPPORT
Search Terms: intrusion, answer
http://support.asus.com/faq/faq.aspx?SLanguage=en-us

[simri]

Not even now this work

Im can not RMA for that reason i placed AS5 on NB and SB and removed the asus label on NB,SB and Silicon Image SI4723.

[WeldZilla]

simri it sounds like you have managed to corrupt your bios chip. Call Asus and ask for the bios department and they will send you a new one 502-995-0883.
With this board there is no need to pull the jumper!!! if you OC to far and it won't move just hold down the power on switch til it goes off, when things stop spinning hit it again . you will get an over clock error and it will tell you to hit F1 to boot .This will take you back to the bios to try again. Again there is no need to pull the JUMPER. In the future make sure of what you are removing before you remove it! I have built 13 systems on these boards they have all been perfect!!!
Don't try to tell me I just happen to get 13 great boards and 13 great cpus and hell even 13 sets of great memory. It isn't luck. Too many of you overthink this. It is not rocket science. (which is not really hard either)
Too many of you know too little and should just leave the damn side covers alone. If there were a shred of decency in this world this miserable thread would be deleted. People don't search it, they just want to re-ask the same ?'s for god knows how many times. very few really want to research and understand anything most just want some killer OC and they want it now!!! I have been running these boards for over a year now. Starting back
with a Presler 950es which was great cuz it would just kick the hell out of an FX-60 so it made my day. Then I moved to the e6400, again it was just unreal fast but, this board works best with the 6600 and higher due to the need for higher multipliers to work with. These boards have been great to me.

WZ

[MarcusTaz]

Hi guys, I've been playing with my OC settings now that I have my watercooling kit installed, but I've been hampered by this damn 360 FSB wall. I've tried putting my RAM on SPD settings, but that doesn't help. (Strangely, when I tried the SPD setting at a lower FSB speed that worked, it didn't boot at SPD, but at the speed that was selected right beneath the FSB setting.) So, anyways, I've turned off all the extra memory options, the CPU options, etc. I've gotten my system to boot and run two Orthos instances for 10 minutes with no problems at FSB 350, RAM at 875mhz 4-4-4-12 with 1.325 vcore and 1.65mch, but upping the voltages to get higher FSB aren't working at all. I've tried doing all the things I could find in this thread and elsewhere, but nothing has helped. All I want is 400 FSB. That's it. I'm not trying to break records, I just want to run 1:1 with tighter RAM timings at DDR2-800. I'm using the 2004 BIOS, by the way. Was I a lucky winner in the "let's see who gets a poor overclocker" sweepstakes?

I miss the days when heat was your only enemy. Just throw good enough cooling at it and it'll go. Not anymore it seems.

Hey bro try lowering your memory by 1 click. I run mine @ 378FSB but if i put my mem above 800mhz then it is unstable even with higher voltage. See if that works...

[Polynikes]

See, this is the kind of stuff I see that gets me pissed off:

http://forums.vr-zone.com/showpost.p...80&postcount=2

I lowered my RAM to 720mhz and upped my FSB to 365, yay, but I'm afraid putting my RAM up to 800 is gonna mess things up. All I want is 8 or 9x400 on the lowest vcore possible. That guy did it at 1.3! Why would my RAM be holding me back? It's frickin' Dominator 8500, easily capable of DDR2-800 at 4-4-4 timings!

[MarcusTaz]

you are not really losing that much, try my bios settings, they are a few pages back. Just run the FSB @ 395 to give you 3.5GHZ and leave your mem where it is @, one click below 800... The bios should still say you are at PC-6400 at boot....

[Polynikes]

So far I can't get past 375, though my RAM is at 750 with 4-4-4-12 timings. In order to do it I had to set my vcore to 1.45. I'll look at your BIOS settings to see what you did. This isn't too bad, really, I just wish my parts would OC as well as others'. I mean, 9x400 at 1.3x? That's nuts. I guess we'll see how stable this OC is when Orthos has had its way. Thanks for the help.

[MacClipper]

In BIOS 1901 EIST/C1E is not linked with Vcore.

Wow, is that the only BIOS versions which is unlinked? Don't remember seeing any mention of this in the FAQ or any other posts in this thread either.

[gwolfman]

Hi guys, I've been playing with my OC settings now that I have my watercooling kit installed, but I've been hampered by this damn 360 FSB wall. I've tried putting my RAM on SPD settings, but that doesn't help. (Strangely, when I tried the SPD setting at a lower FSB speed that worked, it didn't boot at SPD, but at the speed that was selected right beneath the FSB setting.) So, anyways, I've turned off all the extra memory options, the CPU options, etc. I've gotten my system to boot and run two Orthos instances for 10 minutes with no problems at FSB 350, RAM at 875mhz 4-4-4-12 with 1.325 vcore and 1.65mch, but upping the voltages to get higher FSB aren't working at all. I've tried doing all the things I could find in this thread and elsewhere, but nothing has helped. All I want is 400 FSB. That's it. I'm not trying to break records, I just want to run 1:1 with tighter RAM timings at DDR2-800. I'm using the 2004 BIOS, by the way. Was I a lucky winner in the "let's see who gets a poor overclocker" sweepstakes?

I miss the days when heat was your only enemy. Just throw good enough cooling at it and it'll go. Not anymore it seems.

I'm in the same boat as you, I can't seem to get past 375-380. Shouldn't my CPU (E6600) be able to go at least 400 * 9?

[gwolfman]

See, this is the kind of stuff I see that gets me pissed off:

http://forums.vr-zone.com/showpost.p...80&postcount=2

I lowered my RAM to 720mhz and upped my FSB to 365, yay, but I'm afraid putting my RAM up to 800 is gonna mess things up. All I want is 8 or 9x400 on the lowest vcore possible. That guy did it at 1.3! Why would my RAM be holding me back? It's frickin' Dominator 8500, easily capable of DDR2-800 at 4-4-4 timings!

That makes me mad too, why can't my setup run close to that?

[Polynikes]

I guess it's just a matter of luck. Could be the board, your CPU, maybe your RAM. Some people have had crazy good luck, others have not. :\

[gwolfman]

So far I can't get past 375, though my RAM is at 750 with 4-4-4-12 timings. In order to do it I had to set my vcore to 1.45. I'll look at your BIOS settings to see what you did. This isn't too bad, really, I just wish my parts would OC as well as others'. I mean, 9x400 at 1.3x? That's nuts. I guess we'll see how stable this OC is when Orthos has had its way. Thanks for the help.

Hey, me too, I'm stuck there. Have any luck getting past it? I'll post BIOS settings soon with system specs. Maybe tomorrow night.

[MarcusTaz]

My Vcore is bumped to 1.5 in my bios, just bump the vcore up and keep and eye on temps. I have no mods on this board at all, it is bone stock and that goes for cooling too just my cpu is water cooled. So even though I have vcore set to 1.5 now it reads 1.45-1.47 under Everest.. bump that Vcore and leave the MCH @ 1.65 no more no less and set the term voltage to 1.4 no higer no less

[X7007]

Does someone have problems with Overclocking to some limit, lets say from 266 to 280 it works good, but when you try 290 Vista sometimes shows black screen on welcome screen. its like instead of opening pretty, it shows black when only the password box shows first and than everything becomes visible.

i have no idea what the problem is, i tired voltages , timings. very very anoying, its like something is wrong, and prime 95 25.24 passed blend 6hr.

[Chrysalis]

Seems my stuttering video is related to page faults and a windows registry tweak setting system pages to the maximum possible number just about removes the stuttering even with speedstep enabled, havent tested this alongside ahci/raid yet but will as soon as possible on dual boot.

How do I get the Lawrywilds 2004 bios? and what is different on it? thanks.

--edit-- I see added to 1st post in this thread.

[Potato Salad]

Have you made the usb drive bootable?

This is my favourite guide: http://www.weethet.nl/english/hardwa...omusbstick.php

Once you made it bootable, put afudos.exe and 2004.rom on the drive.

In bios change the usb drive in usb configuration to "FORCED FDD"

Then save changes, tap f8 on POST and select to boot from usb drive.

Once dos is loaded, type:

afudos /i2004.rom /p /b /n /c /reboot

note the i after the /

Thanks alot for the guide..
I'll give it a shot later.

[Polynikes]

Hey, me too, I'm stuck there. Have any luck getting past it? I'll post BIOS settings soon with system specs. Maybe tomorrow night.

Here's a few screenshots of my setup. This is the best I've gotten out of it. So far, it's passed two instances of Orthos (RAM and CPU tests) for about 15 minutes, a 32M superpi, two full runs of 3DMark06 (just the gaming benches, not the other stuff) and I played Counter-Strike: Source with 11 bots for about an hour with all the settings maxed. It's pretty stable, at least for what I do with it. I'll probably do more rigorous testing in the future. Here's the screens:

Bios1
Bios2
Bios3
CPUZ + Temp
http://valid.x86-secret.com/show_oc.php?id=229340

Hope this helps. Keep in mind, your machine may boot slower, so wait an extra 30 seconds or so before shutting it off to try again. See below.

Is there any way to "fix" the stall when booting when you've overclocked a lot? My machine takes an extra 15 to 20 seconds to get to the POST beep. I'm glad I waited, otherwise I would've never known this thing was actually capable of booting at these speeds.

[roger_h99.nor]

@Polynikes,
Pretty similar rig, even got the same psu! (look sig.)

You should get a lot more out of that x6800. Tried higher multiplier? (got the same stepping also )
Mine oc easy above 4G on this board, mind if you have 1.85Vmch avalible..

Think fsb 370 was about max with a 1.65Vmch revison board I had earlier.

btw, your biossettings looks ok by me.

http://valid.x86-secret.com/show_oc.php?id=131012

[Polynikes]

I haven't tried a higher multiplier, I'm more interested in 400FSB. I'm curious if it can handle 10 or 11, perhaps I'll mess with it later. I'd also rather not push too much voltage through my NB since I have stock cooling and just finished installing my watercooling kit. The idea of taking it all apart and removing the mobo to put new TIM/reseat and/or install a different cooling solution sounds depressing. :P What voltage settings (all of them) are you using to get it to 410 there? How far is it safe to go with the mch on stock cooling? I do have the 250mm fan on the side of my case blowing directly on the mobo and NB, is that enough to keep it relatively cool? My radiator's two 120mm fans are in the front of the case blowing at full speed (~78 CFM each) towards the mobo as well.

[aledsav1]

Was hoping to find a concise list of bios settings in this thread but so large!!! any ideas where i can find list. Iv just got a p5w and have managed to get to 3.7 with e6750 though not orthos stable so really need settings have updated to latest bios anyone with any suggestions ta

[roger_h99.nor]

Assembly /deassebly is half the fun

My voltage was pretty much maxed out, unless Vcore at 1,58V (1.55V DMM measured) to reach 4G.

I agree - you should be a bit careful with Vmch with stock cooling on it, at least you should change the termal paste on it if haven't already.

My 24/7 (rock stable) is 11 x 325 (water on NB) at Vcore 1.50V set i bios (real 1.48V). Coretemp about 55 C under full load. Probably stable at about 3,8 - 3,9, but haven't tested yet.

@aledsav1,
Take a look at Polynikes settings, they are a good start.

[Polynikes]

Look at my post above for bios screenshots that will probably help. vMCH is going to need to be raised a bit to help, and depending on how far you want to go, your vcore will, too.

Wow, I was running at 333*10 for the longest time at stock voltage and it was rock solid. My load temp on water wouldn't go past 48 C. Does the extra multi really make that big a difference for you?

Someday when I'm feeling more adventurous and want more out of my system, I'll probably change my NB cooling. Maybe I'll integrate it into my loop, maybe not.