ASUS P5W DH - Problems + Fixes Thread

Quote:

---

Originally Posted by Severance

hey guys i need help. this is my first post so im not very experienced. I have read all 80+ pages and have tried everything but still cant get over 360fsb.
x6800
p5wdh mb
corsair 5400pro with those lights on them.I have already fried my new corsair8500c5 trying to get them to run at 1066. Can somebody just post a link of all bios settings i need to set to get over 360fsb please...would help me alot thanx

---

I just wanted to ask how did the 8500 "fry" what gave you this indiator? Did you test the memory in another system before RMAing it? I have the feeling you RMA'd the memory and then someone told you to clear CMOS which means you sent back a perfectly good kit of memory.

This is not meant as an insult or accusation just a question. SPD is not ideal but unfortunately it may nbe the way the BIOS was written with Corsair in mind as the memory maker. Of course if you have PC2-5400 you can't really overclock when you consider your working off a 1066FSB (or you have to start with 266FSB not 200FSB) so the Memory Divisor must be 266FSB x 2.5 = 675 (665 actually) so this would be a motherboard which would have benefitted from divisors displayed as they are instead of displaying the memory speed, such as 400, 533, 567, 800 etc.

Now if you take 266 x 4 = 1066 x 8 = 8500 (PC2-8500) now we need someone with more timne better at math then me to figure out where many end-users are making mistakes with their settings? I know I can't run my system at 425FSB or even 400FSB without dropping the memory divisor to 675MHz.

ok nowu got my attention lol. luckily i have not sent them back yet. Heres how it happend. I installed a water cooling kit. went to boot up it wouldent. I think then we reset cmos. still wouldent boot. Then we tried other ram and it booted. tried the corsair again it would boot only with 1 stick but not the other. left the 1 stick at the comp shop came home booted using the 1 stick but it would hang trying to get into hardware monitor. took it out put in pair of corsair 5400 sticks and all is good. So what did i do? jump the gun?

Quote:

---

Originally Posted by Liquid3D

I just wanted to ask how did the 8500 "fry" whayt gave you this indocator? Did you test the memory in another system before RMAing it? I have the feeling you RMA'd the memory and then someone told you to clear CMOS which means you sent back a perfectly good kit of memory.

This is not meant as an insuklt or accusation just a question. SPD is not ideal but unfortunately it may nbe the way the BIOS was written with Corsair in mind as the memory maker. Of course if you have PC2-5400 you can't really overclock when you consider your working off a 1066FSB (or you have to start with 266FSB not 200FSB) so the Memory Divisor must be 266FSB x 2.5 = 675 (665 actually) so this would be a motherboard which would have benefitted from divisors displayed as they are instead of displaying the memory speed, such as 400, 533, 567, 800 etc.

Now if you take 266 x 4 = 1066 x 8 = 8500 (PC2-8500) now we need someone with more timne better at math then me to figure out where many end-users are making mistakes with their settings? I know I can't run my system at 425FSB or even 400FSB without dropping the memory divisor to 675MHz.

---

Is it me or does it seem many people have issue with Corsair Ram and this board. I have noticed this more than a few times while reading on the Asus P5w, in various threads.

About two weeks ago another guy had one dead stick and went through power supplies etc until he checked the RAM- found the Corsair was the culprit 1 dead stick, same error you reported first post Sererance overvolting vdimm error bla-bla-bla.

I run 1:1 400 x 9 4-4-4 12-4 no issues with G.skill, but you have a E6800 right?
sparx
Edit: here is that guy's post I mention in the text above, back about 10 pages right here on this very thread: http://www.xtremesystems.org/forums/...110193&page=76 (see thickfog)

x6800....

Quote:

---

Originally Posted by Sparx

Is it me or does it seem many people have issue with Corsair Ram and this board. I have noticed this more than a few times while reading on the Asus P5w, in various threads.

About two weeks ago another guy had one dead stick and went through power supplies etc until he checked the RAM- found the Corsair was the culprit 1 dead stick, same error you reported first post Sererance overvolting vdimm error bla-bla-bla.

I run 1:1 400 x 9 4-4-4 12-4 no issues with G.skill, but you have a E6800 right?
sparx
Edit: here is that guy's post I mention in the text above, back about 10 pages right here on this very thread: http://www.xtremesystems.org/forums/...110193&page=76 (see thickfog)

---

for your guys information, i never had problem setting the mem manually and i manage to hit 430 fsb with both my E6400 week 28 and my E6600 week 29.

my ram is Mushkin EM2 DDR2 800 with green heatspreader. the rated timing is sux, 800mhz @ 5-5-5-12 but this ram is great as i manage to oc stable until 1088mhz :D

Quote:

---

Originally Posted by Severance

x6800....

---

Ok so you are at 2.9 stock.
Corsair RAM seems to have issues.

it does seem that way. just tried lower multiplier lower ram ratio..cpu running at 2.3 ram at 533 fsb at 370. shes a no go. By running ram that low have i counted out the mem timing theory at 370? or am i just an idiot?

Quote:

---

Originally Posted by Sparx

Ok so you are at 2.9 stock.
Corsair RAM seems to have issues.

---

to tellu guys the truth..i dont know why im trying to run fsb so high anyways cus anything over 340fsb and my crossfire dies anyways. I need to uninstall drivers reinstall them and sometimes it works sometimes not. when it does work if i go above 340fsb crossfire dies again. what i mean by die is...in games there are artifacts when i disable 1 vid card all is good but with both running its messed up

running my e6600 at 3.0ghz, rams at 1ghz - spd. g-skill 2x1gb "hz" ram

Just was wondering... my timings according to cpu-z are:

frequency: 500.2mhz
fsb:dram : 2:3
CAS# Latency: 5.0clocks
RAS# to CAS# Delay Latency: 6 clocks
RAS# Precharge: 6 clocks
Cycle Time (Tras) 18 clocks
Bank Cycle Time (Trc) 21 clocks

System is stable, bf2 works fine for couple hours as does games like fsx, havent checked orthos but i imagine it is...

Would it be advisible to make the timings tighter? Or would there be no real performance boost from it, and also if if would be advisible to make the timings tighter what would the bios settings be?

Thanks.

Timmaah
You should be able to run 4-4-4-12-4 with that RAM. I am using 2.05 volts on my ram btw.

Try it and test with Orthos it will act up within 3 hours if there is an issue.
Also run 3d05 and check the performace with your settings then run it again to test with new settings and compare.
Sandra (test program) also can be used to test performance.

Using a CD with only the ROM file loaded did not work for that ezflash thing under tools in the BIOS, I will try putting onto CD what it wants me to put onto a floppy. Unless it's one of those things where you give the program your floppy drive letter and it makes the floppy for you. :(

Quote:

---

Originally Posted by Sparx

Timmaah
You should be able to run 4-4-4-12-4 with that RAM. I am using 2.05 volts on my ram btw.

Try it and test with Orthos it will act up within 3 hours if there is an issue.
Also run 3d05 and check the performace with your settings then run it again to test with new settings and compare.
Sandra (test program) also can be used to test performance.

---

Just curious Sparx why do you suggest 3d05 to check for stability and not 06 or another program??

Quote:

---

Originally Posted by Thasp

Using a CD with only the ROM file loaded did not work for that ezflash thing under tools in the BIOS, I will try putting onto CD what it wants me to put onto a floppy. Unless it's one of those things where you give the program your floppy drive letter and it makes the floppy for you. :(

---

when i flashed it with the cd method on the NF4 board, i think i had to put the flash tool file with the bios, and select that drive as priority boot in order to run it. You didnt try the usb mp3 player flash method? Someone said it works for them, just do a manual cmos reset when your done.

Quote:

---

Originally Posted by Severance

to tellu guys the truth..i dont know why im trying to run fsb so high anyways cus anything over 340fsb and my crossfire dies anyways. I need to uninstall drivers reinstall them and sometimes it works sometimes not. when it does work if i go above 340fsb crossfire dies again. what i mean by die is...in games there are artifacts when i disable 1 vid card all is good but with both running its messed up

---

What? I never had this problem back when I had X1900 CF Setup and my current one. Also, I currently have the mem in my (Corsair) working fine.

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

Quote:

---

Originally Posted by Severance

to tellu guys the truth..i dont know why im trying to run fsb so high anyways cus anything over 340fsb and my crossfire dies anyways. I need to uninstall drivers reinstall them and sometimes it works sometimes not. when it does work if i go above 340fsb crossfire dies again. what i mean by die is...in games there are artifacts when i disable 1 vid card all is good but with both running its messed up

---

hard set the pci-e frequency to 100mhz and pci-e sync to 33.3mhz.. that should help. after doing that my CF setup was good to go up to 400mhz on the fsb.

I believe you should always reset bios after flashing..
Right after flashing on reboot, load setup defaults, then when it reboots, go back in bios then change what you need to..:)

Hi,

My Rig :
E6700, Asus P5W DH Deluxe, Corsair 2GB XMS2-8500C5, Tuniq Tower

Having some OC problems with these settings with BIOS 1506 :

CPU Frequency: 350MHz
DRAM Frequency: DDR2 700MHz (1:1)
Performance Mode: Standard
PCI Express Frequency: 100
PCI Clock Synchronization Mode: 33.33
Memory Voltage: 2.20V
CPU Vcore Voltage: 1.4V
FSB Termination: 1.4
MCH Chipset Voltage: Auto
ICH Chipset Voltage: AUTO
Digital Home Mode: Disabled

Under Advanced Chipset:

DRAM Timings by SPD: Manual (per RAM specs 5-5-5-15)
DRAM ECC Mode: Disabled
Hyper Path 3: Disabled
DRAM Throttling Threshold: Auto
*All PEG Settings AUTO*

Under advanced CPU settings:

Microcode Updation: Enabled
Everything else: Disabled

I have every device Disabled that I don't need eg. RAID controller, Serial Port etc etc

Problem is that with these setting I run Prime95 or Orthos and it immedietely gives me errors.

Any idea's what mistakes I've made ?

Cheers

raise your Vcore to say 1.475 ( then any voltage higher that temps allow you as you overclock higher, keep an eye on temperatures)
MCH to 1.65
ICH to 2.0
dram throttling-disabled

make sure all the qfan and anything to do with fan settings are disabled also

Quote:

---

Originally Posted by Potato Salad

Just curious Sparx why do you suggest 3d05 to check for stability and not 06 or another program??

---

3D06 is great too, I have been lazy not downloading 3d06. :D

Jaap74set Pcie to 105

sparx

well i used memset and set it to 5-5-5-12 expecting the pc to freeze, i cant find the trc value though in memset 3.0. Pc didnt freeze so im pleasantly surprised, even though the tras is 26 and not 10 :|

When my corsair c5 was alive i was able to get it to 510mhz stable with 4449 timings but not 1066 55515 as for the crossfire... dont know why im having problems getting over 340fsb. im using asus 1950s.

Quote:

---

Originally Posted by nicepun

What? I never had this problem back when I had X1900 CF Setup and my current one. Also, I currently have the mem in my (Corsair) working fine.

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

---

Hey guys... upgraded to the new 1602 BIOS and now can't increase the multiplier of my x6800 to 13. Anyone else notice this?

In 1503 I have the multiplier=13 for 3.46ghz, ram at DDR2-1067 for PC-8500 - very fast.

Not sure if they added something that I am missing or not ...

Hi,
Ive errors in memtest x86, while running test 7:

Test 7 [Random number sequence]

This test writes a series of random numbers into memory. By resetting the seed for the random number the same sequence of number can be created for a reference. The initial pattern is checked and then complemented and checked again on the next pass. However, unlike the moving inversions test writing and checking can only be done in the forward direction.

My cfg:
* Intel duo 2 e6400: 400x6
* DDR2 PC6400C4 Corsair 2x512

It only happens when running in DUAL CHANNEL !!

I dont know what to do, please help me. I tried to disable all features in bios but with no effect.

What is better: run in dual channel or fsb2ram 1:1 ?

/edit

Tested with 300x8 and ram at 800mhz, works fine.

Quote:

---

Originally Posted by tompl

Hi,
Ive errors in memtest x86, while running test 7:

Test 7 [Random number sequence]

This test writes a series of random numbers into memory. By resetting the seed for the random number the same sequence of number can be created for a reference. The initial pattern is checked and then complemented and checked again on the next pass. However, unlike the moving inversions test writing and checking can only be done in the forward direction.

My cfg:
* Intel duo 2 e6400: 400x6
* DDR2 PC6400C4 Corsair 2x512

It only happens when running in DUAL CHANNEL !!

I dont know what to do, please help me. I tried to disable all features in bios but with no effect.

What is better: run in dual channel or fsb2ram 1:1 ?

/edit

Tested with 300x7 and ram at 800mhz, works fine.

---

Try putting your RAM in the other two dual channel slots. Sometimes those slots can be picky.

Hey guys, it's been awhile since I've overclocked, but like many others, I found this thread to be very helpful.

I don't know if this problem is strange or not, but my settings are as follows:

CPU Frequency: 400MHz (e6600)
DRAM Frequency: DDR2 800MHz (1:1) - G.skill
Performance Mode: Standard
PCI Express Frequency: 101
PCI Clock Synchronization Mode: 33.33
Memory Voltage: 2.15V
CPU Vcore Voltage: 1.61V (1.58 reported by asus probe)
FSB Termination: 1.2
MCH Chipset Voltage: 1.65
ICH Chipset Voltage: AUTO
Digital Home Mode: Disabled

Under Advanced Chipset:

DRAM Timings by SPD: Manual (per RAM specs 4-4-4-12)
DRAM ECC Mode: Disabled
Hyper Path 3: Disabled
DRAM Throttling Threshold: Disabled
*All PEG Settings AUTO*

So I'm running dual prime 95 with the custom settings - max FFT at 900, and memory usage at 1790kb for both. I made this mistake as I really meant to put 900kb for memory usage on both instances of prime 95. It's strange that with the settings like this, I can run 18hours+ of this and everything is fine. However, when I left the max FFT to default at 4096, and memory usage at 900kb, 1 instance of prime will crash within minutes. Can anyone explain why this is?


Am I at the limit with my cpu? I've tried all voltage settings from 1.56 -> 1.61 and it seems like 1.61 (1.58 in asus probe) has allowed me to run dual prime 95 at 400fsb, but with the above problem. This chip was able to run at least 370fsb at 1.4v. Seems like too high of a jump in vcore to hit 400fsb. Heat doesn't seem to be a problem as I'm running a watercooling setup (cpu doesnt hit over 40C) as well as an active cooler on the nb (nb doesnt hit over 50c). I've tried everything including changing bios to 1602, reverted back to 1503 now. I've changed VMCH to 1.8+ and vdimm set to SPD/manual at 2.2 vdimm, FSB termination to 1.3, swapped memory slots, etc and nothing seems to help except the vcore increase.

One last thing to note: I'm able to run 3dmark loop at 400fsb w/ 1.56v(1.52-1.53v) for 24+ hours and memtest86 for 24+ hours without any problems. I'm also able to play bf2102 and company of heroes for hours without any problems as well.

Thanks in advance for the help.

Edit: It's the chip, set the multiplier at 8 and runs 400mhz w/o any probs.