ASUS P5WDG2 WS Pro+Retail Box E6300 @ FSB 470+

Printable View

Show 100 post(s) from this thread on one page

09-03-2006, 10:01 PM
SLi_dog

Quote:

Originally Posted by Anemone

When is the P5W64 due?

This one?

http://www.asus.com/products.aspx?l1...41&modelmenu=1
09-03-2006, 10:45 PM
Simon

Quote:

Originally Posted by faith4

wats that program in ur picture called ? it shows vcore,cpu,mb and other things. http://www.iamxtreme.net/andre/WSPRO-473.JPG

CPU-Z!

http://www.cpuid.com/cpuz.php
09-03-2006, 10:46 PM
Vengure

I want that Mobo drools .... I wish ASUS would give ur more DDR vdm to play with sigh.
09-04-2006, 12:43 AM
Durzel

Can anyone tell me whether this board has the same strange shutdown behaviour as the P5W-DH? (i.e. when you reset it or make changes in CMOS instead of resetting it cold boots?)
09-04-2006, 12:54 AM
apfubar

Quote:

Originally Posted by Durzel

Can anyone tell me whether this board has the same strange shutdown behaviour as the P5W-DH? (i.e. when you reset it or make changes in CMOS instead of resetting it cold boots?)

It does appear to have the same behavious, but I am not 100% sure, how can you tell?

cheers,
AP
09-04-2006, 01:29 AM
Durzel

Quote:

Originally Posted by apfubar

It does appear to have the same behavious, but I am not 100% sure, how can you tell?

cheers,
AP

When you reset the PC in Windows (Start Menu -> Restart) does it actually power off completely and then come back on a couple of seconds later? Or do the fans etc stay on like a normal reset? The P5W-DH also does this if you make any change in the BIOS and save it.
09-04-2006, 05:16 AM
fishingeek

Yes it shuts down on restart and bios changes.

Geek
09-04-2006, 06:36 AM
Natalia

Quote:

Originally Posted by fhpchris

I would only use these dividers:
1:1
4:5
2:3

at 1.5v core bios I could easily prime @ 3100 mhz(~345fsb) and passed a dual 1m @ 3300 mhz(~367 fsb)

at 1.6v core bios I could easily prime at 3600(~400fsb) and dual 32m @ 3700(412 fsb)

Make sure your ram isnt walling and you are not using the overclocked dividers.(the dividers that overclock your northbridge-- like 712 divider @ 266 fsb)

Whenever I leave my computer off for a while and come back and turn it on, the boot fails. (i.e. all I get is a black screen, no source to the monitor) When I turn the computer on and off, I get a slow initialization of the BIOS, and when I try to go into the BIOS it takes a while. It also shows a message that the overclock failed. Once I am in , all I have to do is save and exit (no changes) and reboot. Then enter the BIOS again, change the Boot priority to my RAID (the only option that resets during this ordeal) and I am good to go. Once I do this I can restart all I want, it only makes me do this when it is off for over an hour.

Is this Ram related?

VCore: 1.35v
E6600 FSB: 370
G.Skill DDR2-800 RAM: 925 @ 2.25V
4-4-4-8

I have run Orthos all night long before with no errors, and run a memory tester to 300% without errors.
09-04-2006, 06:40 AM
pcdoc1

Give vcore a small bump and see if the problem goes away...
09-04-2006, 07:27 AM
Natalia

Reason I ask about it being memory, is I got the same issue when ever I tried any settings with the memory at 987 MHz.
09-04-2006, 07:32 AM
pcdoc1

Have you tried loosening timings a bit...
09-04-2006, 08:12 AM
Raja@ASUS

Natalia, it may be an idea to come down to the 1:1 memory speed (533). And run at Cas 3-3-3-8 if your ram can handle that latency, the bandwidth will be the same due to the reduced latency.

I have experimented with this on the DFI board, which I have running 370-380 fsb, it has the same issues as yours at over 900 mhz, no loss of perceived performance either, at the lower cas and divider , slightly higher stability too.

regards
Raja
09-04-2006, 08:28 AM
orion23

Quote:

Originally Posted by raju

Natalia, it may be an idea to come down to the 1:1 memory speed (533). And run at Cas 3-3-3-8 if your ram can handle that latency, the bandwidth will be the same due to the reduced latency.

I have experimented with this on the DFI board, which I have running 370-380 fsb, it has the same issues as yours at over 900 mhz, no loss of perceived performance either, at the lower cas and divider , slightly higher stability too.

regards
Raja

Yeah, why not try running the memory 1:1 which is still below the rated 800mhz the G.skill supports. Just downclock it and don't even bother about the timings yet. See what happens!

Also, make sure that the battery is all the way IN!
09-04-2006, 09:15 AM
linflas

Quote:

Originally Posted by Natalia

Whenever I leave my computer off for a while and come back and turn it on, the boot fails. (i.e. all I get is a black screen, no source to the monitor) When I turn the computer on and off, I get a slow initialization of the BIOS, and when I try to go into the BIOS it takes a while. It also shows a message that the overclock failed. Once I am in , all I have to do is save and exit (no changes) and reboot. Then enter the BIOS again, change the Boot priority to my RAID (the only option that resets during this ordeal) and I am good to go. Once I do this I can restart all I want, it only makes me do this when it is off for over an hour.

Is this Ram related?

VCore: 1.35v
E6600 FSB: 370
G.Skill DDR2-800 RAM: 925 @ 2.25V
4-4-4-8

I have run Orthos all night long before with no errors, and run a memory tester to 300% without errors.

I think raju is right, I have the same memory, and this board does not like doing anything other than 1:1 on the memory we have.

If your cooling is OK, try 1.45 vCore in Bios, FSB @ 400, memory at 4-4-4-12-4 delay of 7, memory strap of 1:1 i.e. ddr2 800, vdimm 2.2, mch @1.6-1.7, and try your rig, and see if that works better.
09-04-2006, 09:51 AM
Anemone

Quote:

This one?

http://www.asus.com/products.aspx?l1...41&modelmenu=1

Thank you :) Yep!
09-04-2006, 12:14 PM
xgman

The easiset way to tell is give it a little more vcore. I find this more than anything else will get you more stability and a little higher o/c. If that doesn't work, then look elsewhere. The conore is very sensitive to needing just a bit more voltage albeit at the cost of more heat.
09-04-2006, 08:21 PM
SLi_dog

Quote:

Originally Posted by fishingeek

Yes it shuts down on restart and bios changes.

Geek

I'm still getting used to that :stick:

Quote:

Originally Posted by xgman

The easiset way to tell is give it a little more vcore. I find this more than anything else will get you more stability and a little higher o/c. If that doesn't work, then look elsewhere. The conore is very sensitive to needing just a bit more voltage albeit at the cost of more heat.

For me a slow boot up usually occurs with not enough vCore.

Quote:

Originally Posted by Vengure

I want that Mobo drools .... I wish ASUS would give ur more DDR vdm to play with sigh.

I'd love some more vCore too :banana:
09-05-2006, 08:11 AM
Raja@ASUS

There's an offer going on at Ocxtreme forums, (you need to be a member to see)

http://www.ocxtreme.org/forumenus/showthread.php?t=2511

he offers vmods too, at a very good price for members (cost only no labour charge). I've ordered mine, just waiting patiently now...

regards
Raja
09-05-2006, 10:26 AM
Durzel

Anyone noticed that this board has the same USB header as the P5W-DH for the wireless module? You could add wireless quite easily to this board :)
09-11-2006, 11:29 PM
camouflage

:rolleyes: So again back to the BIOS - is there a benefit changing to the 0004 or should I stay with the 07/20/2006 ??? :confused:

And how does it work to save the current BIOS with the ASUS UPDATE program?

Each time I try it gives me no BIOS file to save...... :stick:

This is what I got so far - seems that this board doesn't like high FSB async... :

http://img205.imageshack.us/img205/7475/sp1m3208vi2.jpg

The chip ran 3.6 with 1.49 Vcore on air at the guy I bought it from but I think I have to do some testing sync for higher speed.

But the most fvcked up thing is the cold boot bug in BIOS after leaving it - never had a board acting like this ?!?!?!
09-12-2006, 04:01 AM
Dumo

470ish FSB attainable with this board...

http://img123.imageshack.us/img123/4...shot007uj2.jpg

http://img165.imageshack.us/img165/9...shot009iy8.jpg
09-12-2006, 04:30 AM
MrBean

Quote:

Originally Posted by Natalia

Whenever I leave my computer off for a while and come back and turn it on, the boot fails. (i.e. all I get is a black screen, no source to the monitor) When I turn the computer on and off, I get a slow initialization of the BIOS, and when I try to go into the BIOS it takes a while. It also shows a message that the overclock failed. Once I am in , all I have to do is save and exit (no changes) and reboot. Then enter the BIOS again, change the Boot priority to my RAID (the only option that resets during this ordeal) and I am good to go. Once I do this I can restart all I want, it only makes me do this when it is off for over an hour.

Is this Ram related?

I have exactly same setup as you, and my memory is sitting at 667 strap, with 370 fsb, so mem running around 925mHz, only diff is my timings, which I have 5-5-5-16 for stability, and 24/7 operations.

Vmem at only 2.10volts, and vcore 1.40 (measured at chokes)

You can try and up vmem to around 2.35, which should give you more/better stability, but probably a better (for your hardware) longterm solution would be to cut down on latencies a little, and keep 1:1 ratio.

Conroe loves bandwidth, and most applications will appreciate higher bandwidth over latencies.

You can test yourself with SuperPI, run with 1:1, very tight timings, and then set strap to 667 (20% mem overclock over fsb) and increase latencies to 5-5-5-15 or there abouts, and test again.

At least with my testing I needed somewhat higher overclock on fsb 1:1 to reach same SuperPI results with memory running fsb:ram 4:5

Keep us posted of your results - and if you find a solution to your problem.

Kind regards,
MrBean.
09-12-2006, 10:25 AM
lkraven

Quote:

Originally Posted by Natalia

Whenever I leave my computer off for a while and come back and turn it on, the boot fails. (i.e. all I get is a black screen, no source to the monitor) When I turn the computer on and off, I get a slow initialization of the BIOS, and when I try to go into the BIOS it takes a while. It also shows a message that the overclock failed. Once I am in , all I have to do is save and exit (no changes) and reboot. Then enter the BIOS again, change the Boot priority to my RAID (the only option that resets during this ordeal) and I am good to go. Once I do this I can restart all I want, it only makes me do this when it is off for over an hour.

Is this Ram related?

Natalia,

I have a P5W-DH and I have this EXACT same issue. It's been driving me nuts, and I have no idea how to go about resolving it. System is prime and orthos stable, and memory runs like a champ, but, if, like you, I leave the machine for awhile, I come back and turn it on it's black on my screen-- sometimes it can take a few reboots.

I am running a modest overclock at:

E6600 @ 3.20ghz
356FSB
Corsair Memory (rated at DDR800 @ 4-4-4-12)
1.475 vCore
2.1 vDimm

I believe I have run it at a 1:1 divider and have the same problem. When I do get it to reboot, it is VERY slow, and it the Intel Raid does not recognize my Raid array (sees it as gibberish). After I go into the Bios and reboot, the Raid is recognized, and it's back to normal.

I also notice this quite a bit when the machine has been allowed to go on Standby. When it comes back, sometimes, it is okay, and sometimes, it freezes with no display (and hard drive lights on).

I have a 7950GX2-- do you have the same adapter, Natalia?

It's very very annoying-- so annoying I was going to ditch my P5W-DH and buy the P5WDG2, but I guess that plan is not going to get me anywhere either!

If you or anyone find a solution, I would LOVE to know what it is.
09-12-2006, 10:28 AM
Raja@ASUS

is there a pcie reset option? Try enabling it..
09-12-2006, 10:36 AM
Durzel

Quote:

Originally Posted by fhpchris

Asus probe turns the comp off once it hits 65c, just use core temp! :)

I don't think Asus Probe turns the computer off, does it? If you're overclocked and the PC just switches off it's because it's overclocked too high/not cooled enough.

Show 100 post(s) from this thread on one page