*** Official ASUS P5W DH Thread ***

[iamdw]

Originally posted by: renozi
Write Recovery Time is defaulted @ 4 is in the manual.

If I might add, try bumping up the vcore. I doubt you need it since your C2D is probably a more recent week than my week 24 (L624A573). Otherwise I don't know why you can't run at a higher FSB. ?_?

I can't find where it says 4, all i see is 5-5-5-15-2. I gave 4 a try though but no luck. Also tried raising the VCore to 1.45 over the previous 1.4 setting. Should i be going higher?

 

[hofan41]

nvm

 

[phile]

Originally posted by: mp6951md
Hello everyone, I'm new to the forum and I'm doing my first build with my brother using this motherboard. I just wanted to make sure that my cpu cooler and power supply will be adequate.

My cpu cooler is the Zalman CNPS 9700LED: Does this fit easily or will I need to make any mods to the cooler?

My power supply is the Thermaltake TR2 W0070RUC 430W: I know its a little on the weak side but I'm only going to have a single ATI x1900 video card and I don't think I'll do any significant overclocking. Is this enough power or do I need somthing stronger?

Appreciate the input.

Welcome to AT. Your PSU should be plenty fine.

-phil

 

[QuietRiot]

Originally posted by: iamdw
Another issue for me is that when i play Battlefield 2142 i will eventually get a hard reset after a bit with the below settings and a CPU Freq above 327 (yes even 328 hard resets).

I would try upping the MCH. My E6300 was stuck at 350 and by going to 1.65 v it allows it to go higher.

-----

After weeks of breaking my head over the temps of my rig (it was idlying in the high 50's/low 60's), I started lowering the voltages and I'm using the lowest allowed voltage on BIOS 1602 = 1.2250 v (@ 333 CPU freq). Now it idle's in the high 40's, low 50's. I get Tuniq Tower today so I try once more to reseat the heatsink and organize the inside of my rig to improve airflow. The goal is to have it in the low 30's.

Temps acquired using Core Temp.

 

[msmith7305]

Phil-

I'm sure you know the answer to this!

Why does every indication I have show my ethernet connection as 100 Mbps? I would have thought with a gigabit controller it would be higher?

I am connected to Time Warner's cable modem for the internet.

Thanks

 

[phile]

Originally posted by: msmith7305
Phil-

I'm sure you know the answer to this!

Why does every indication I have show my ethernet connection as 100 Mbps? I would have thought with a gigabit controller it would be higher?

I am connected to Time Warner's cable modem for the internet.

Thanks

The 100 mbps refers to the connection-type of your ISP, not the theoretical bandwidth capabilities of your ethernet controller. To put things into their proper perspective, your actual downstream limit with Time Warner is about 7 mbps (7000 kbps) - nowhere near their 100 mbps capacity.

You can test your connection here:
http://www.speakeasy.net/speedtest/

-phil

 

[phile]

Originally posted by: iamdw
Hey guys, I'm having trouble getting my setup up to where i think it should be able to overclock to as well as others with similar specs have been able to get.

If i follow the settings from this site to reach 3.6GHz, I cannot even get a POST.

Before upgrading to the latest 3dMark06 patch i was able to complete test without fail at the settings below (until most recent patch where a get a consistent sys.lock even at stock BIOS settings, but that is a different issue). Orthos as well as MemTest86 also run without error.

Another issue for me is that when i play Battlefield 2142 i will eventually get a hard reset after a bit with the below settings and a CPU Freq above 327 (yes even 328 hard resets).

So i guess what i'm asking is if there is anything noticeable with the settings below that may be at fault? Perhaps something in my system specs in my siggy? I've followed a few guides and thread suggestions hear and elsewhere but am unable to get beyond my current 3.27GHz CPU freq with stability.

At this point i suspect it is probably RAM related as I see a few threads of PC2-8500 memory being incompatible or at issue with this board. At POST with my current setting i'm seeing PC2-7100, but as others have noted, it is common to have inaccurate POST readings.



CPU : Intel Core 2 Duo e6700
DDR2 : Corsair TWIN2X2048 8500 C5D Dominator 1Gx2
Bios : 1602
VGA : ATI x1900 XT Crossfire/x1900 XT (dual) 512MB
HDD : Western Digi 300GB IDE 7200
PSU : PC Power & Cooling TC 850 SSI 850W
OS : XP SP2 Latest patches, etc..
OVERCLOCK (MHz) = 3270

BIOS SETTINGS

JumperFree Configuration

AI Overclocking set to MANUAL

CPU Frequency : 327
DRAMM Frequency : 981

Performance Mode : Standard
PCI Express Frequency : 100
PCI Clock Sync Mode : 33.33

Memory Voltage : 2.20
CPU Vcore Voltage : 1.4000
FSB Termination V : 1.40
MCH Chipset V : 1.55
ICH Chipset V : 1.05
--------------------------------------------------------

CPU Configuration

Modify Ratio Support Disabled
Microcode Update : Enabled
Max CPUID Value Limit : Disabled
Execute Disable Function : Disabled
Enhanced C1 Control : Disabled
CPU Internal Thermal Control : Disabled
Virtualization Technology : Enabled
Intel SpeedStep Technology : Disabled
--------------------------------------------------------

Advanced Chipset Settings (DDR2)

Configure DRAM Timing By SPD : Set to MANUAL and set to Mem specs
DRAM CAS Latency : 5
DRAM RAS Precharge : 5
DRAM RAS To CAS Delay : 5
DRAM RAS Activate to Precharge Delay : 15
DRAM Write Recovery Time : 2

DRAM ECC Mode : Disabled
Hyper Path 3 : Disabled
DRAM Throttling Threshold : Disabled
Memory Remap Feature: Disabled

Per Buffer Length : Auto
Link Latency : Auto
PEG Root Control : Auto
PEG Link Mode : Auto
Slot Power : Auto



Any suggestions/tips could be greatly appreciated..

- dDub

I briefly skimmed youir posts and the few replies. It looks like your mem and the P5WDH are not playing nice. Have you tried enabling SPD timings for the overclocks that fail with manual timings? Also, have you done any memtest86 diagnostics on the mem, with the machine running at stock configuration? You're wasting your time with all this troubleshooting if you have a bad stick.

Memtest:
http://www.memtest.org

I would also note that PC8500 memory is not officially supported by the P5WDH. PC6400 is the fastest support memory. Your mem might be unstable when using certain dividers that cause no problems with slower mem.

Here's a little table with the memory dividers used for various memory speeds, with FSB at stock.

FSB - EFFECTIVE - REAL - DIVIDER
266MHz - PC4200 (DDR2-533) - 266MHz - 1:1
266MHz - PC5300 (DDR2-667) - 333MHz - 4:5
266MHz - PC6400 (DDR2-800) - 400MHz - 2:3
266MHz - PC8500 (DDR2-1066) - 533MHz - 1:2

Personally, I have had no problems running configurations using the first 3 dividers. 1:2, however, I have never tried. That would be quite the overclock for my PC6400 kit. It may be that you just need to find the right mem speed (and thus, memory divider) for whatever overclock you're aiming for.

With your mem, and a target FSB of 360, here are the options for mem speed, at those dividers I illustrated above:

FSB - EFFECTIVE - REAL - DIVIDER
360MHz - DDR2-720 - 360MHz - 1:1 (extreme memory underclock)
360MHz - DDR2-900 - 450MHz - 4:5 (moderate memory underclock)
360MHz - DDR2-1080 - 540MHz - 2:3 (very slight memory overclock)
360MHz - DDR2-1440 - 720MHz - 1:2 (extreme memory overclock)

I would try the middle two options. For the third option, try upping the mem voltage +.1 from the spec.

Again, this is all may be resolved by running SPD timings, instead of setting them manually.

-phil

 

[Whirlwind]

I have had no trouble with my set up at all....everything is rock solid.

I have the set -up in my sig. I have not OC yet, but am thinking of just a small, mild overclock.

Could someone tell me what I need as far as programs to monitor heat and stress test programs...or do I really need them for small or mild OC?

What is the easiest thing for me too do to get a mild OC?

I think my current temps are good
CPU 30 Idle Load35
MB 49 Idle Load 55

Can i do this and still have a really stable mobo?

 

[iamdw]

Originally posted by: phile
I briefly skimmed youir posts and the few replies. It looks like your mem and the P5WDH are not playing nice. Have you tried enabling SPD timings for the overclocks that fail with manual timings? Also, have you done any memtest86 diagnostics on the mem, with the machine running at stock configuration? You're wasting your time with all this troubleshooting if you have a bad stick.

Memtest:
http://www.memtest.org

I would also note that PC8500 memory is not officially supported by the P5WDH. PC6400 is the fastest support memory. Your mem might be unstable when using certain dividers that cause no problems with slower mem.

Here's a little table with the memory dividers used for various memory speeds, with FSB at stock.

FSB - EFFECTIVE - REAL - DIVIDER
266MHz - PC4200 (DDR2-533) - 266MHz - 1:1
266MHz - PC5300 (DDR2-667) - 333MHz - 4:5
266MHz - PC6400 (DDR2-800) - 400MHz - 2:3
266MHz - PC8500 (DDR2-1066) - 533MHz - 1:2

Personally, I have had no problems running configurations using the first 3 dividers. 1:2, however, I have never tried. That would be quite the overclock for my PC6400 kit. It may be that you just need to find the right mem speed (and thus, memory divider) for whatever overclock you're aiming for.

With your mem, and a target FSB of 360, here are the options for mem speed, at those dividers I illustrated above:

FSB - EFFECTIVE - REAL - DIVIDER
360MHz - DDR2-720 - 360MHz - 1:1 (extreme memory underclock)
360MHz - DDR2-900 - 450MHz - 4:5 (moderate memory underclock)
360MHz - DDR2-1080 - 540MHz - 2:3 (very slight memory overclock)
360MHz - DDR2-1440 - 720MHz - 1:2 (extreme memory overclock)

I would try the middle two options. For the third option, try upping the mem voltage +.1 from the spec.

Again, this is all may be resolved by running SPD timings, instead of setting them manually.

-phil

Phil,

Thanks for the suggestions. I 've done the usual testing with Memtest and such and my RAM appears to be ok.

I wound testing the first three dividers - none of which were successful... argh.

- 2:3 would not allow a POST
- 4:5/1:1 would POST but eventually rebooted at random. Strange though, 4:5 seemed to allow a longer time until reboot whereas 1:1 would reboot within a minute or so of login.

I guess the problem, as you mentioned, must be the issue with 8500 memory and the current BIOS incompatibility. I've see others with the same types of troubles as i am having with the P5W and 8500 mem. Guess i'll just have to stick with my moderate OC speed until the BIOS is better able to support my memory.

Thanks for the help,

- dDub

[EDIT: forgot to mention that i did tried with SPD timings but the results were the same]

 

[touchstone1]

Hi guys,

OK, it's Tearing My Hair Out time. After a couple of months using the EZ-Backup raid system, with a lot of problems (drive read errors, several array rebuilds etc.), I'm trying to use the ICH7R instead, but I can't get as far as Windows XP installation...

I've got a pair of Western Digital SATA-II drives (250GB), connected to SATA1 and SATA3. I'm running 1602 BIOS, and have configured SATA mode to RAID with the BOOT ROM enabled. I've built a RAID-1 array using the Intel (Ctrl-I) interface, and set up a floppy with the latest Intel ICH7R RAID driver. I use the F6 'load drivers' switch in Windows XP setup and choose the "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)". Setup continues until it says 'Setup is starting Windows' and then I get a blue-screen STOP error, every time.

I would have thought that this meant I had selected the wrong driver, but 'Desktop ICH7R/DH' is the right one, isn't it?

Any help would be greatly appreciated!!

 

[QuietRiot]

Funny you should post this. Back on page 14, you gave me comfort when you said that the EZ-Backup was working fine while I was struggling with my ICH7R setup. I wanted because I wanted to get the ICH7R working and, after manually modifying my hair outline, I figured it out. Simple answer: get the latest drivers from Intel.

Longer answer: I was never able to get it to work correctly with F6 - it wouldn't blue-screen, but it would get stuck. I ended up creating a slipstreamed version of my WinXP CD including those Intel drivers and it worked.

To create a slipstreamed Windows CD I used nLite (www.nliteos.com).

 

[msmith7305]

Originally posted by: phile

Originally posted by: msmith7305
Phil-

I'm sure you know the answer to this!

Why does every indication I have show my ethernet connection as 100 Mbps? I would have thought with a gigabit controller it would be higher?

I am connected to Time Warner's cable modem for the internet.

Thanks

The 100 mbps refers to the connection-type of your ISP, not the theoretical bandwidth capabilities of your ethernet controller. To put things into their proper perspective, your actual downstream limit with Time Warner is about 7 mbps (7000 kbps) - nowhere near their 100 mbps capacity.

You can test your connection here:
http://www.speakeasy.net/speedtest/

-phil

Phil-

Thanks for the response. Guess the gigabit lan thing is more hype than anything.

In a previous reply, you said to disable serial port if not needed. I can't find where in BIOS to do this.

Also, I noticed on my old computer that the PS/2 optical mouse's light is on even when the system is not powered up. On this one, the mouse light doesn't come on until boot up. What causes this?

Thanks

 

[SkyYYZ]

Off topic, but holy crap! I just did the Speakeasy test... I had no idea my download speeds were increased by my ISP (Rogers Cable Systems):

Atlanta, GA test -

Last Result:
Download Speed: 2132 kbps (266.5 KB/sec transfer rate)
Upload Speed: 693 kbps (86.6 KB/sec transfer rate)

New York City, NY test -

Last Result:
Download Speed: 3350 kbps (418.8 KB/sec transfer rate)
Upload Speed: 767 kbps (95.9 KB/sec transfer rate)

Washington, DC test -

Last Result:
Download Speed: 3955 kbps (494.4 KB/sec transfer rate)
Upload Speed: 775 kbps (96.9 KB/sec transfer rate)

Sweet!

 

[touchstone1]

Originally posted by: QuietRiot
Funny you should post this. Back on page 14, you gave me comfort when you said that the EZ-Backup was working fine while I was struggling with my ICH7R setup. I wanted because I wanted to get the ICH7R working and, after manually modifying my hair outline, I figured it out. Simple answer: get the latest drivers from Intel.

Longer answer: I was never able to get it to work correctly with F6 - it wouldn't blue-screen, but it would get stuck. I ended up creating a slipstreamed version of my WinXP CD including those Intel drivers and it worked.

To create a slipstreamed Windows CD I used nLite (www.nliteos.com).

Hi QuietRiot,

Well, I tried the slipstreamed CD approach, using the latest Intel drivers (specifically, just the ICH7R RAID driver) and nLite, and I still get the bluscreen/STOP error when Setup tries to start Windows. BTW, the STOP error is 0x24, which Technet says "indicates that a problem occurred within Ntfs.sys"...

I know the HDs are OK, because I've been using them for the last few months; the only problems I've had were related to the EzBackup array needing a rebuild every week or two.

So, I might have to give up the idea of using a RAID array, chiz chiz.

Unless anyone has any ideas?

 

[touchstone1]

Possible stupid question: after creating the RAID 1 array using the Intel ROM interface, should the disks be formatted or cleared somehow? Or does the Intel array creation 'clear' the previous data from the drives?

 

[DutchBBQ]

Download LATEST bios & drivers prior setting up your system

Downloading and installing latest BIOS & Drivers helps reducing installation problems and instability of your system. While the idea is dead obvious--the problem is that we don't do the obvious. Don't use the drivers on the accompanied ASUS CD of your P5W HD Deluxe motherboard!!
For your convenience, I've listed here the links where to get the LATEST of them:

http://vip.asus.com/forum/view.aspx?id=...l=P5W+DH+Deluxe&page=1&SLanguage=en-us

 

[QuietRiot]

Nice post, DutchBBQ.

Touchstone, I'm not sure technically, but I'd format just for the cleanness of it.

Does anyone around here know if the provided infrared (IR) dongle works only with the remote? I was trying to connect my mobile through it, but WinXP won't even recognize when I connect the dongle. Maybe it's just a receiver..?

 

[touchstone1]

Continuing the saga...

I've 'formatted' the drives using Western Digital's Data Lifeguard Tools, and now I get a Stop 0x7B (lost access to the system partition or boot volume). There is a known, unresolved problem with XP (KB307099) where this can happen after the text portion of Setup (which is exactly where I get it), when F6 is used, if the 'Repartition' option is on during an unattended setup. Well, my setup isn't unattended, but it sounds too similar to be a total coincidence. I'll check the nLite setup and see if I can change the (presumably hidden) Repartition option.

 

[CRChickadee]

touchstone:

"I've 'formatted' the drives using Western Digital's Data Lifeguard Tools, and now I get a Stop 0x7B (lost access to the system partition or boot volume). There is a known, unresolved problem with XP (KB307099) where this can happen after the text portion of Setup (which is exactly where I get it), when F6 is used, if the 'Repartition' option is on during an unattended setup. Well, my setup isn't unattended, but it sounds too similar to be a total coincidence. I'll check the nLite setup and see if I can change the (presumably hidden) Repartition option."

Personally I'd just let the OS install process format the drive. I've used WD drives also, and for me this has avoided the LifeGuard issues/WD issues.

 

[CRChickadee]

If you intend on using Vista 64 RTM with an ATI card, make sure you use the recent release of the ATI Vista beta drivers, put out yesterday.

The previous release would often currupt the boot system following play in games. So far it's been about 2 hours and several re-boots with the new release. The previous release usually would not get past 20 minutes following a game and and then a failed re-boot, necessitating a re-mirroring back the system.

 

[CRChickadee]

Potential Photoshop CS2 users with Vista 64. Though the launch takes about the same time as it would in XP-Pro, the 'processing", for me, has been about 300% faster, e.g. 35 seconds to auto complete a full mask in Vista 64 in a hi-res photo, -vs- 1:30 in XP Pro.

It's nice to see the memory useage assistance with a 64 bit system.

 

[Austin2k]

Originally posted by: touchstone
Possible stupid question: after creating the RAID 1 array using the Intel ROM interface, should the disks be formatted or cleared somehow? Or does the Intel array creation 'clear' the previous data from the drives?

Let the OS do the formatting after you have installed the ICH7R driver at the beginning of the XP install.

Cheers from Austin, Texas.

 

[Austin2k]

Originally posted by: CRChickadee
Potential Photoshop CS2 users with Vista 64. Though the launch takes about the same time as it would in XP-Pro, the 'processing", for me, has been about 300% faster, e.g. 35 seconds to auto complete a full mask in Vista 64 in a hi-res photo, -vs- 1:30 in XP Pro.

It's nice to see the memory useage assistance with a 64 bit system.

Do you have the new memory optimization for 64-bit enabled in BIOS?

 

[msmith7305]

This is something that is bugging me a lot.

Why does the "gigabit" ethernet controller only have 100Mbps full duplex as the highest setting when looking at the properties page in device manager?

I know my cable won't get me that speed, I'm just not understanding why the option to set the controller for 1000Mbps doesn't seem to be there.

Could someone please help this idiot out?

Thanks

 

[touchstone1]

Re: getting ICH7R RAID working

Thanks for the 'when to format' responses ... so far, I'm still stuck trying to get the ICH7R driver loaded during setup, either using F6 or slipstreamed CDs. My next step is to try adding ALL the drivers from the 32-bit Intel 'floppy' to a streamlined CD, instead of just the ICH7R RAID driver.

One interesting thing I've found is that the Intel user guide mentions that a 0x7B error may be expected if the RAID mode is changed after OS installation. Again, this appears relevant, but since the drives are formatted and don't include an OS yet, maybe not.

Maybe I should just go and buy a tape drive 8-(