ASUS P5W DH Deluxe BIOS Screens 56k Warning

[Airjarhead]

Hey Guys,
In the past I've always searched for Guides to help me set up my BIOS screens since the manuals are never any help (what the hell is "Microcode Updation"). Anyway I just got an Asus P5W DH Deluxe and couldn't find any guides except FCG's great guide for the P5B Deluxe here:
http://www.xtremesystems.org/forums/...d.php?t=115217

I have just passed 11 hours of Orthos and 20 passes of memtest with the settings in the screenshots below
What did I change to go from failure (less than a minute of Orthos) to succes? I plugged my case fans directly into the PSU molex connectors vice the motherboard 3 pin connectors. I know I've heard that tip before, but thought it was over-rated.

If any of you salty dogs know of tried and true settings, (or have good reasons for other settings) let me know. Then as I correct the setting I will post the corrected BIOS screen and this could end up as a guide for dumb-asses like me :P

1


2


3


4


5


6


7


8


9


10


11


12

[BigRigDriver]

Asus sux arse big time!!!

[Airjarhead]

Thanks for the constructive criticism

I was just surfing around...and came up with a few things I haven't thought of:

I have my RAM in the Orange slots. Should I try the black

I'm running the 1602 BIOS as recommended in the probs & fixes thread. Is the E4300 supported in this BIOS?

Thanks

[barrymaldon]

enable by spd as some ram will not run with this disabled at even there defualt timings (my OCZ plat's wouldn't). Also make sure you've got speed step etc disabled

[Thasp]

Anything over 330 FSB didn't work unless I used the lowest ram divider on that board.. lots of bad memories trying to get the p5wdh to do anything I wanted it to.

[crazyea]

These are my e6600 stable settings. You can try and apply to your situation.

JUMPER FREE Page

AI Overclocking: Manual
CPU Freq: 400 <---- Try 333
DRAM Freq: 800 <---- Try 666

Perf Mode: Auto
PCIe: Auto
PCI: Auto

Mem V: 2.0 <---- With SPD on Manual you may need more Volts here.
CPU V: 1.3875
FSB V: 1.40
MCH V: 1.55
ICH V: Auto

CPU CONFIG Page

Modify Ratio: Enabled <----Disable this
Multi: 8 <----With above disabled mutli will be 9
Microcode Update: Enabled
Max CPUID: Disabled
Execute Disable: Disabled
CPU Thermal Control: Auto
C1E: Disabled
Virtualization: Disabled
EIST/Speedstep: Disabled

CHIPSET Page

Configure by SPD: Enabled <---- If you get stable try custom settings
ECC: Disabled
Hyperpath: Auto
DRAM Throttle: Auto

All Other Settings on this page: Auto

[crazyea]

BTW, I am using the 1901 Bios.

[Airjarhead]

Thanks Crazy. I'll try those suggestions.

[Bail_w]

Vcore: 1.45v (start dropping once you get it stable)
FSB: 1.45v
Vmch : 1.65 ( i use 1.85v for 430FSB stable if i drop it, it will crash immediatly)
Vich : 1.205v

[barrymaldon]

don't use 1901 for the love of god, the p5w-dh is good for alot more than what your currently getting so there is another issue somewhere. Mine will do 455fsb boot into windows.

[lawrywild]

1901 is fine for a lot of people including myself

anyway, try:

vFSB to 1.2v
vMCH keep to Auto
Performance mode to Turbo
Slot power to Heavier
Pci-e to 105
Pci to 33mhz
Link Latency to normal
Modify rato to disabled

[QuietRiot]

Performance mode to Turbo
Slot power to Heavier
Pci-e to 105
Link Latency to normal

Is there a good in-depth guide for the P5W DH - I'm interested in knowing more about each individual BIOS settings.

[Airjarhead]

Is there a good in-depth guide for the P5W DH - I'm interested in knowing more about each individual BIOS settings.

I haven't found one, that's why I made this post - in the hopes of creating one.

Thanks for the post Lawry - I will put those in and change the pics

An update on me - I have just passed 11 hours of Orthos and 20 passes of memtest with the settings in the screenshots above
What did I change to go from failure (less than a minute of Orthos) to succes? I plugged my case fans directly into the PSU molex connectors vice the motherboard 3 pin connectors. I know I've heard that tip before, but thought it was over-rated.

Thanks for the suggestions. If anyone has any more (like Lawrywild) with good reasoning/experience I will put it in my BIOS and change the respective screenshot to try and make this a guide.

Thanks Again

[Airjarhead]

Well I updated the BIOS to 1901. Seems OK.
There is one more question I had looking under the Main>My Hard Drive section
there is an option for
"32Bit Data Transfer" After a clear CMOS it was set to disable, and I have never changed it.
Do you recommend enabling it?
I think it is supposed to be for IDE drives, do you think it will help SATA drives?
Would it hurt to change the setting after the OS has been installed (like AHCI/IDE modes)

Thanks

[Airjarhead]

Here is what Adrian's Rojak Pot says about 32bit data transfer:

32-bit Disk Access

Options : Enabled, Disabled

32-bit Disk Access is a misnomer because it doesn't really allow 32-bit access to the hard disk. What it actually does is set the IDE controller to combine two 16-bit reads from the hard disk into a single 32-bit double word transfer to the processor. This makes more efficient use of the PCI bus as fewer transactions are needed for the transfer of a particular amount of data.

However, according to a Microsoft article about Enhanced IDE operation under WinNT 4.0, 32-bit disk access can cause data corruption under WinNT in some cases. Microsoft recommends that WinNT 4.0 users disable 32-bit Disk Access.

On the other hand, Lord Mike asked someone in the know and he was told that the data corruption issue was taken very seriously at Microsoft and that it had been corrected through Service Pack 2. Although he couldn't get an official statement from Microsoft, it's probably safe enough to enable IDE HDD Block Mode if you are running WinNT, just as long as you upgrade to Service Pack 2.

If disabled, data transfers from the IDE controller to the processor will then occur only in 16-bits. This degrades performance, of course, so you should enable it if possible. Disable it only if you face the possibility of data corruption.

You can also find more information on the WinNT issue above in our Speed Demonz' guide on IDE Block Mode!


Sounds to me like it is only for IDE and could possibly give corruption.
What do you think about my original questions?