ASUS P5W DH - Problems + Fixes Thread

yes, i have tried it with just the raptor running vista and one seagate only. i've tried the seagate on each of the other SATA spots (blacks and oranges) and still the same thing.
i had them running as individual storage drives on my windows xp (1 on each black adapter) until i switched to AHCI and put vista on this computer.
apparently the ez-backup mirrored my drives too somewhere in me mixing the adapters to make this work, because when i hooked them up to the jmicron the 2 drives (that previously had completely different things backed up on them) became 2 copies of 1 drive. (unfortunately it mirrored my drive of movies/crap and i lost my otehr drive of documents, mp3s, programs :( )

with both vista and xp the windows bar scrolls 11 times. i have an e6600 on p5w-dh with 2xraptor x in raid 0 powered by corsair hx620. i have tried all the diferent bios's to no avail. sometimes and i never know how i remove a drive say and it boots in a second, but not always. jmicron is disabled. running a 500gb sata drive on ich7 with the raid + 2x pata dvd on ide channel. i have tried almost everything apart from changing opticals to cable select as i suspect it's a random i/0 problem. is anyone else finding that whatever boot and drive configs they use windows boots real slow. hope someone has the answer.

Quote:

---

Originally Posted by Alfieg

with both vista and xp the windows bar scrolls 11 times. i have an e6600 on p5w-dh with 2xraptor x in raid 0 powered by corsair hx620. i have tried all the diferent bios's to no avail. sometimes and i never know how i remove a drive say and it boots in a second, but not always. jmicron is disabled. running a 500gb sata drive on ich7 with the raid + 2x pata dvd on ide channel. i have tried almost everything apart from changing opticals to cable select as i suspect it's a random i/0 problem. is anyone else finding that whatever boot and drive configs they use windows boots real slow. hope someone has the answer.

---

In device manager disable everything you don't use, and if you're only using 1 ide drive on a channel, click properties and instead of Auto Detection, change them to Not Installed so on boot it doesn't search for ide drives. Also in bios change the ide options to Not Installed for unused ports.

Quote:

---

Originally Posted by iadstudio

One question though, what happens if I put too much graphite on the resistor?

---

You can always remove it with a rubber/napkin [ lol ] /etc

Haven't located the "supposed to be" new BIOS yet.
In our dreams we're seeing tRFC, tREF & tRD coming with it, but hey!
Get your @ss back in reality :D

I want my mits on 1901 bios...

Hi, me too, and, geez, I'd settle being able to get into their forum, haven't had access for days. Anyone else the same?
ChrisC

But P5B's can do about 500FSB with 1066strap (vmodded) . P5W can't do 480+ even vmodded .

Quote:

---

Originally Posted by gritty

Just got the P5W DH and in process of installing it. Saw on a previous post that there is a problem with updating Win XP if you have a Creative X-FI installed. Has this problem been resolved with the later (latest) BIOS flashes or what?

Also, MB manual states that the board does not recognize a SATA drive untill XP SP1 is installed. Does this mean you have to istall Windows on an IDE drive first and then to use a SATA drive for boot drive you clone the IDE drive to a SATA drive?

Any other quirks or tricks I need to know?

Thanks for any help.

---

Hi. I actually bought and installed my x-fi after I had my system up and running, and didn't have any problems. You will surely want to download the latest driver off Creative's site, and use at least bios 1707 (unless we get this new 1901 with 1333fsb and its stable).

What the manual means regarding SATA is that you will have to use a slipstreamed copy of Windows with SP2 to avoid having issues. I'm not sure whether or not anyone had any problems with the vanilla XP, but when I did my load, I used a slipstreamed copy with all patches back to 11/2006. No problems!

For quirks and tricks, spend a week and go through the thread. :eek:

Quote:

---

Originally Posted by BenchZowner

Haven't located the "supposed to be" new BIOS yet.
In our dreams we're seeing tRFC, tREF & tRD coming with it, but hey!
Get your @ss back in reality :D

---

And not to mention open multipliers for the X/QX CPU's... Sigh... Probably time to get back to the reality... :D

Quote:

---

Originally Posted by bellx1

i have an issue with the setup im trying to run. the issue is that i have 2 seagate 120gb drives i want to use as storage, but vista ultimate see's them as one combined drive that is unreadable and unallocated and in disk management all the options to format/partition/etc are greyed out. whne i look at the properties it has the disk labeled the same way i had them about a year ago when they were raided together! is there something i need to change to get them to be seen as individiual drives? i have tried every combo of things i can think of, its drivin me nuts lol

right now i have AHCI selected in bios. on the red adapter is my raptor 150gb with vista, on the black next to the red is a wd 500gb backup drive. on the next black is a 120gb seagate, and on the ezraid 1 is the other seagate 120gb. i have removed both jumpers from the ezraid currently, but have tried this in all the jumper configs trying to get SOMETHING to let me access the drives. the only thing that would let me get on the drives is using the jmicron, but i can only see the one drive on jmicron and not the 2nd drive on either the black or orange connectors when i do this. the raptor and wd 500gb always show up just as they should.

is this because i have ahci enabled? does something in the mbr (i dont even know what that is really lol) of the seagates need changed?

help please:eek:

---

^-- When you create arrays, yes, it does write to the MBR and tags the disk with the type of array that it's assigned to.

If you can, set your BIOS to RAID, not AHCI, and from the Intel Disk Config that comes up when you POST, delete the drives from whatever array they're showing. You can run Non-Member disks in RAID mode and have them be JBOD just fine, with full AHCI/NCQ support.

Also be sure you have the latest version of the Intel Storage Matrix drivers inside windows. You didn't mention if you did or not, but it's important.

Lastly, if you still can't get it to work and modify the drives, download a copy of SystemRescueCD, and use gparted when you boot into the linux. You can manipulate all drives/filesystems from here, but you may have to know some linux to get around.

Best of luck!

Quote:

---

Originally Posted by Rob Halford

And not to mention open multipliers for the X/QX CPU's... Sigh... Probably time to get back to the reality... :D

---

Hey Rob, I noticed your 3dmark06 score. Wicked man. Could you give the breakdown of the CPU/GPU/Shader scores (or whatever it is when you look at detail on their webpage).

I know our 8800gtx's are being bottlenecked by the CPU, but I find it hard to believe by *that* much. My e6600 (@3.5ghz) + 8800gtx is just over 11,200 in 3dmark06. If the CPU helps to hit a 19,000, I'm going to have to catch a deal on one and fleabay my melon crap cpu. I need better performance in Vanguard! :D

Quote:

---

Originally Posted by nickfd

Hey Rob, I noticed your 3dmark06 score. Wicked man. Could you give the breakdown of the CPU/GPU/Shader scores (or whatever it is when you look at detail on their webpage).

I know our 8800gtx's are being bottlenecked by the CPU, but I find it hard to believe by *that* much. My e6600 (@3.5ghz) + 8800gtx is just over 11,200 in 3dmark06. If the CPU helps to hit a 19,000, I'm going to have to catch a deal on one and fleabay my melon crap cpu. I need better performance in Vanguard! :D

---

Hi Nickfd,

Score achieved with EVGA 680, 8800 GTX (SLi) @ 690/2100 and QX 6700 @ 3.943, all cooled with an Overklokk built Waterchiller for CPU and GPU's. However, got bored with the EVGA MOBO and bought P5W DH Deluxe which overklokk modified according to the recipe on first page. He also rebuilt the waterchiller into a singel stager phase as well as I got hold of a better sample QX6700. Present CPU runs 3dMark06 @ 4.5 which gives a CPU score of 6.400 or thereabout. (CPU tested 3dMark06 stabile over 5.1 GHz on LN2... :D) Just waiting for those R600 cards in crossfire now so that I can pass 21.500... :p:

You can find the breakdown at the following link: http://service.futuremark.com/orb/pr...ojectId=657558

Where is that 1901 BIOS ???????

Quote:

---

Originally Posted by Rob Halford

And not to mention open multipliers for the X/QX CPU's... Sigh... Probably time to get back to the reality... :D

---

You can use any of the previously released BIOS versions to use the upwards multipliers with X/QX CPUs.
If you've flashed to 1707 or any newer version, you need to flash back by performing a full eeprom flash.

More details here :)

Quote:

---

Originally Posted by nickfd

^-- When you create arrays, yes, it does write to the MBR and tags the disk with the type of array that it's assigned to.

If you can, set your BIOS to RAID, not AHCI, and from the Intel Disk Config that comes up when you POST, delete the drives from whatever array they're showing. You can run Non-Member disks in RAID mode and have them be JBOD just fine, with full AHCI/NCQ support.

Also be sure you have the latest version of the Intel Storage Matrix drivers inside windows. You didn't mention if you did or not, but it's important.

Lastly, if you still can't get it to work and modify the drives, download a copy of SystemRescueCD, and use gparted when you boot into the linux. You can manipulate all drives/filesystems from here, but you may have to know some linux to get around.

Best of luck!

---

thanks! that was exactly it. this actually occurred to me on the drive to school today that i had never reset the drives from the raid array back to non-raid status. i disconnected all drives, placed the seagates on sata 1 and 3, changed bios to raid, entered the intel manager with ctrl+I, reset them, put bios back to AHCI and my raptor back to sata 1, wd500gb to sata3, seagate to sata 4 and seagate to ez-backup 1 and now it shows just as it should with each seagate being an individual drive. :banana: somtimes, im such a tard lol

Quote:

---

Originally Posted by BenchZowner

You can use any of the previously released BIOS versions to use the upwards multipliers with X/QX CPUs.
If you've flashed to 1707 or any newer version, you need to flash back by performing a full eeprom flash.

More details here :)

---

Thx,

Tried all new BIOS's but no open multiplier for my QX6700 after 1601. I normally use Asus EZ-Flash utility (within BIOS) to upgrade BIOS but BIOS 1601 - for some reason - does not allow this procedure. Yes there is a f*** up somewhere. Consequently, I have to use the Windows Update Utility to upgrade BIOS and everytime I pray (yes, just like we pray to our Lord Jesus) that the newer BIOS will allow me to flash back to 1601 (using EZ-Flash utility) if I find that the new BIOS does not have open multiplier for the QX6700... Our soules and gratitude to ASUS... May the Lord be mercyful... :slapass:

Quote:

---

Originally Posted by Rob Halford

Thx,

Tried all new BIOS's but no open multiplier for my QX6700 after 1601. I normally use Asus EZ-Flash utility (within BIOS) to upgrade BIOS but BIOS 1601 - for some reason - does not allow this procedure. Yes there is a f*** up somewhere. Consequently, I have to use the Windows Update Utility to upgrade BIOS and everytime I pray (yes, just like we pray to our Lord Jesus) that the newer BIOS will allow me to flash back to 1601 (using EZ-Flash utility) if I find that the new BIOS does not have open multiplier for the QX6700... Our soules and gratitude to ASUS... May the Lord be mercyful... :slapass:

---

You should be able to flashback to 1601 using the AFUDOS utility.
If you're more like...me ( no FDD around since...2004 I think :D ) you can use a bootable flash cd ( bootdisk.com for ISO image AFAIR ).
I don't remember the full flash switch for AFUDOS atm.

Nick, thank you for the reply. Been reading forum for a few weeks already. That is where I came up with my questions, hoping that there were some fixes, especially in BIOS from Asus so I would not have to do anything special. I may have missed some things as there is an awful lot of stuff here. Sure is a lot harder making a new computer than a few years ago when all you had to do was install the parts and load the OS.

g'day...

Well I've tried but can't find any retailer who sells any E6700s that's a better sample than mine (I'm after a week 32+), but to make matters worse this week the pc has been going skitty!

Essentially repeated BSODs in XP reporting some kernel exception, then I got a different one with IRQL_NOT_LESS_OR_EQUAL error. I've had the latter exception before (on a P4C800-E when o/cing), but I've not had the sinister sounding kernel errors before. I've checked with the windows debugging tools and ALL of the bsods appear to be related specifically to kernel processes which again I've not seen before (on the P4C it was always a random process/driver). Now to me it seems that my windows kernel could somehow have been corrupted (no idea how), yet when I turn my RAM speed down from 875MHz to 700MHz, the problem appears to go away (I found this by originally going back to stock CPU speed and working my way up).

This all seems a bit odd, seen as I've been running the machine on stable settings for months - does anybody recognize this apparent hardware degredation? I do remember "degredation" of sorts being mentioned in this post, but that was relating to FSB. I'm planning to install XP again on a seperate drive and testing, but I think that the RAM speed solution shows that the mobo is goosed, but no idea why!

Anybody got ideas?

Cheers :)

Quote:

---

Originally Posted by Seb R

g'day...

Well I've tried but can't find any retailer who sells any E6700s that's a better sample than mine (I'm after a week 32+), but to make matters worse this week the pc has been going skitty!

Essentially repeated BSODs in XP reporting some kernel exception, then I got a different one with IRQL_NOT_LESS_OR_EQUAL error. I've had the latter exception before (on a P4C800-E when o/cing), but I've not had the sinister sounding kernel errors before. I've checked with the windows debugging tools and ALL of the bsods appear to be related specifically to kernel processes which again I've not seen before (on the P4C it was always a random process/driver). Now to me it seems that my windows kernel could somehow have been corrupted (no idea how), yet when I turn my RAM speed down from 875MHz to 700MHz, the problem appears to go away (I found this by originally going back to stock CPU speed and working my way up).

This all seems a bit odd, seen as I've been running the machine on stable settings for months - does anybody recognize this apparent hardware degredation? I do remember "degredation" of sorts being mentioned in this post, but that was relating to FSB. I'm planning to install XP again on a seperate drive and testing, but I think that the RAM speed solution shows that the mobo is goosed, but no idea why!

Anybody got ideas?

Cheers :)

---

Sounds a lot like my problems. I have the same basic setup as you, corsair pc2 8500C5, e6700 and p5w. I had to pull my memory back to 1:1 at 760mhz and the problem went away. I managed to get a 2:3 memory ratio stable for months (1020 4-4-4-10) and then one day after installing some new led fans the system went heywire!

I pulled the fans off the mobo and have them directly into the PSU and it seemed to pacify the issue. Could I have hastened the deterioration of the board due to over volting the memory and fans?

I've since done a pencil mod to calm down the vdroop and squeezed 50mhz more out but my memory will no longer run stable at anything more than 4:5 and even that is a stretch some times. I also can't boot anything over 382fsb so I think the board has been tapped out. When I have more time I'll play with the memory more but I don't have time to right now. I have a sinking suspicion that this memory really suffers when it's been given 2.4v to achieve lower latencies or it could be the memory slot on the mobo. When memtest showed the memory failing it was always the same slot.

Sound familiar?

Quote:

---

Originally Posted by Seb R

...when I turn my RAM speed down from 875MHz to 700MHz, the problem appears to go away...

---

And that's too bad because I found the extra bandwidth (as long as you can maintain low latencys) really helps. It might be time for us to bite the bullet and invest in some CL3 pc2 6400. CL2 at 700mhz would rock!!!

Right now I think I have hit a wall. I am at 3.6ghz @ 1.5375volts in bios. Temps are at 57ºC at load. I try and run 3.8ghz @ 1.65volts and it gets to the point where normally that windows screen would come up where the blue bar goes across the bottom of your screen a couple times, but it just sits there at a black screen. I do have an A chip also. Any ideas? Also if I want to run my ram faster and in bios it lets me choose from 800mhz next is 1000mhz, what if I want like 850 or 900? Can I do that and how?

Where is info how to do this pencil vdroop mod?

Hi. I have a weird problem with my P5W DH Deluxe, bios 1602. The rest of my setup: E6600 @3.2GHz (8*400), Zalman CNPS9500 LED, 2x1GB Kingston Value 800MHz DDR2, ASUS GF 7950GT 512MB, 2x300GB Seagate 7200.8 @RAID0, SB Audigy 2, Corsair 520W PSU.

When I first set up my rig, I tested it both at default speed and overclocked @3.2 (8*400). For testing I used several hours of 3DMark, Orthos Prime (x2), games, video encoding etc.
It worked perfectly @400*8 for about two months, temps were ok (and still are), never above 62 C under full load.

Now I'm experiencing lockups, usually after about 5-10 minutes under full load, and I have to hit the reset button. After that, the mobo usually won’t boot so I have to turn it off and back on again. It then says something like “overclock failed, enter setup”. If I just try the previous settings in bios (just hit F10 and save) it almost always locks up again, however if I reset the multiplier to 9 (default) it boots at 3.6GHz!!! at the same voltage, and I enter bios setup again, lower the multi to 8, it then boots and works normaly at 3.2 GHz. Until the next time it locks up.

I’ve tried upping voltages without success (temps are not too high, I also tried running with case open), so I’m guessing it has to do something with the multiplier, because it runs normally @ 9x and lower FSB.
It’s like it locks up just because multilpier has been changed from the default value (like the mobo doesn’t “like” that), however I haven’t seen anyone else having such a problem. I must say again, it used to work normally before, at same voltages, temps, settings.

Any ideas?

Thanks.

p.s. would you recommend the latest bios 1707?