ASUS P5W DH - Problems + Fixes Thread

Printable View

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

10-19-2006, 08:55 AM
mikepaul

Quote:

Originally Posted by Falkentyne

Two quiet clicks....that sounds like a hard drive head dying...could be wrong, though....(a head dying and freezing can cause the entire system to freeze).

Is the HDD LED light on when this happens?

Can't say if the HD light was on more than normal: the case is on its side with the access opening up, so the light faces away from me.

The boot drive is 'new', a RMA replacement WD 160GB that was fortunately around when I overheated and killed my old drive while defragmenting, and it hasn't had any problems that have been brought to my attention. It now lives in an Antec HD cooler at maybe 34C per the LED display. The WD 80GB data drive has seen better days, since I've had to reformat three partitions recently to get around Ghost 10 not being able to back them up. One of the partitions is where I keep the swapfile and it has needed a CHKDSK a few times due to these crashes and also what seemed like normal shutdowns. I guess the click sound could be coming from that general area, since it's almost the same level in the case as the PSU.

I can keep this idea in mind if having the non-boot (but swapfile) drive act funny can cause these kind of crashes, and put a new drive on the shopping list. Would moving the swapfile back to the C: drive for a while limit the impact crash-wise of any head issues on this secondary drive? One day, when I have 8GB of RAM and a version of Windows that can use it, I want to do away with the swapfile anyway...
10-19-2006, 09:43 AM
pee4

Quote:

Originally Posted by topboy

Does anyone have issues with this board on a reboot where it fails to initizalise the usb controller and hangs. I then press reset switch and it slow boots and throws a weird config disk entry in the raid list of disks on the ICH raid screen.

Config is 3 Raptors on raid 0

System not overclocked

Help appreciated

Topboy

I get that rubbish too sometimes. It stalls for a moment when trying to find IDE4 then it displays that junk (--------------) in the Intel RAID section. I've got 2 Raptors in Raid 0. I don't know what happens if the PC actually boots, because when I see it I normally reset the PC because it worries me that it might corrupt the data on my hard drives if I let it boot.
10-19-2006, 10:06 AM
deadlock7

Quote:

Originally Posted by pee4

I get that rubbish too sometimes. It stalls for a moment when trying to find IDE4 then it displays that junk (--------------) in the Intel RAID section. I've got 2 Raptors in Raid 0. I don't know what happens if the PC actually boots, because when I see it I normally reset the PC because it worries me that it might corrupt the data on my hard drives if I let it boot.

Same here..:(
10-19-2006, 11:05 AM
lawrywild

I just let it boot when it happens, it does nothing, don't worry about it
10-19-2006, 01:10 PM
Leeghoofd

can't even boot 410 fsb on this vcore thou, but it's rock stable at 400, ran orthos for 24 hours and other benchies fine, ran a few hours of fear and bf2 also and works fine

Max FSB I got with 1405 was 445 and with 1502 now it's less :( But the reboot seems different. Thoush stil noa added mem timings like with P5B Bios

it definitely needs that voltage, just think it's a bit too much for that clock. also temps are high... around 65 at max load ...and that's with a scythe infinity and some as5 (possibly bad contact?)

I need to put 1.4125 or 1.4250, the latter gives me less choppyness in games but the rig is rockstable on 1.4125 ( real just below 1.4 volts in bios) but he games tend to lag so I give the cpu some more voltage. I think you better reseat the cooler. In Orthos (so Dual prime) I get 52-50°c in Coretemp with my Ultra 120, The previous Zalman was 4-5 degrees hotter than the Thermalright. Everest Home gives for the CPU under load 44°C which is fine for me and the rig runs like this 24/7

These are my settings here in the link :

http://users.pandora.be/OAP/ALT.doc

Also here's a piccie of the cooling setup, I removed the covers of the bridges, a small old CPU fan on the northbridge and a beefy 120mm fan giving some cool air to my X2 card and the southbridge

http://users.pandora.be/OAP/Ultra120.jpg
10-19-2006, 01:25 PM
Richard Dower

You Asus guys have too many hits!, 165,000...us Gigabyte folks are launching a campaign to beat y'all.

:-)
10-19-2006, 01:43 PM
v_parrello

Memory subtimings

Hi guys!

Is in the new 1502 bios anything concerning memory subtimings (tRD, tRFC)configuration?

Somebody did try it? And what about memory divider? Are They working better with this new bios?

Thanks in advance
10-19-2006, 03:42 PM
lawrywild

Quote:

Originally Posted by v_parrello

Hi guys!

Is in the new 1502 bios anything concerning memory subtimings (tRD, tRFC)configuration?

Somebody did try it? And what about memory divider? Are They working better with this new bios?

Thanks in advance

Apparently not :(
10-19-2006, 03:43 PM
lawrywild

Quote:

Originally Posted by Richard Dower

You Asus guys have too many hits!, 165,000...us Gigabyte folks are launching a campaign to beat y'all.

:-)

haha.. you can try :D
10-19-2006, 07:55 PM
Pjoeloe

I thought it might come in handy to pass this url : it`s the newest version of the Asus update utilty v 7.07.06 to update the bios of all asus boards in windows xp without leaving windows xp :

http://drivers.softpedia.com/get/Oth...ty-70706.shtml
10-19-2006, 09:00 PM
Liquid3D

something to make you laugh

I finally get around to testing my Conroe 6400 and P5W DH, I install the board and the stock cooler as usual to test temps on stock, and then go to power-up the system and nothing?

So I check all connections blah blah, and try the obvious removing the conroe and installing a Pentium 930, still the system won't power-up?

So I pull the board out of the case set it up on the box on Anti-static bag to elinimate Case grounding problems etc. as an option. I use a jumper to power up the board and it works! So I pop the front off the NZXT Zero case to see where the short might be in the wiring and it's fine? Then I realize I was freaking trying to power on the system using the DAM Reset button Doh!!!!

I've decided to remove the "savant" from my nickname Idiot-Savant. Anyway I rei-install Conroe she boots but it says 6300 running at 1.60GHz? So I raised the FSB to 333 as I thought this was supposed to be the Conroe's FSB speed anyway and this raise the memory to ddr2-1000 ehifch it is, and the chip to it's dfeault speed of 2.13GHz> Then the system won't boot? When the BIOS (0801) comes up again (at 1.60GHz) I notice the CPU temp is 65C? I try lowering the Vcore which was on Auto but I figure maybe there's something wrong, and this does nothing. Now I know with stock cooling 65C is insane since my room is at 18C and the case is open and near an open patio door letting cold air in. SO 65C is impossible. Well not with a Pentium 930 and a stock cooler overclocked but on a Conroe running under it's speed? PLAESE HELP

Does the bIOS 0801 report CPU temps wrong?

I'm sure I seated the cooler correctly although to be honest I hate these freaking new pop-pins they drive me nuts because they just don't work right half the time. You push two pin across from each other so one side doesn't seat unevenly and what happens only one goes in anyway. Anyway I need help or a handgun..... :(
10-20-2006, 04:21 AM
phile

The BIOS will correctly report which CPU you have, regardless of the operating speed. So, if it's reporting that you have a E6300, that's exactly what you have. Stock FSB for conroe is 266. Your temps suggest that the cooler is NOT properly secured to the mobo. I would suggest removing and reseating the CPU (Take the opportunity to read the fine print on the heatspreader, which tells you the default operating frequency. This will help you determine what chip you have.) and reinstalling the HSF.

-phil
10-20-2006, 05:20 AM
irenic

my new asus p5w dh deluxe straight out of the box manage to run my E6400 @ 3.2ghz with vcore @ default, vfsb up 1 notch, vmch @ 1.65, vdimm @ 1.9.

orthos stable @ 6hrs, but i'm using stock intel hsf. Coretemp reported core temp @ 80c .. :D
10-20-2006, 05:58 AM
Jimbo

Quote:

Originally Posted by irenic

my new asus p5w dh deluxe straight out of the box manage to run my E6400 @ 3.2ghz with vcore @ default, vfsb up 1 notch, vmch @ 1.65, vdimm @ 1.9.

orthos stable @ 6hrs, but i'm using stock intel hsf. Coretemp reported core temp @ 80c .. :D

80c? :eek:

I thought mine was bad at 60c load, at 3ghz.

Well screw it then, Im going back to 3ghz. :D
10-20-2006, 06:40 AM
irenic

i dunno how accurate it was.. my room temp was at 24c and my GTO also cooled down to 35c .. i touched intel hsf and i could feel the cold. but coretemp showed 80c.

my cpu is ok, not concave bcoz last time with big typhoon VX, even at 1.5vcore temp never goes above 65c.
10-20-2006, 06:41 AM
phile

Quote:

Originally Posted by Jimbo

80c? :eek:

I thought mine was bad at 60c load, at 3ghz.

Well screw it then, Im going back to 3ghz. :D

Core temps of ~60C at load (TaT, Orthos Small FFTs) are well within the safe zone. I would certainly be very much uncomfortable with 80C, though.

-phil
10-20-2006, 07:10 AM
Nunyabiz

Quote:

Originally Posted by Liquid3D

I've decided to remove the "savant" from my nickname Idiot-Savant. Anyway I rei-install Conroe she boots but it says 6300 running at 1.60GHz? So I raised the FSB to 333 as I thought this was supposed to be the Conroe's FSB speed anyway and this raise the memory to ddr2-1000 ehifch it is, and the chip to it's dfeault speed of 2.13GHz> Then the system won't boot? When the BIOS (0801) comes up again (at 1.60GHz) I notice the CPU temp is 65C? I try lowering the Vcore which was on Auto but I figure maybe there's something wrong, and this does nothing. Now I know with stock cooling 65C is insane since my room is at 18C and the case is open and near an open patio door letting cold air in. SO 65C is impossible. Well not with a Pentium 930 and a stock cooler overclocked but on a Conroe running under it's speed? PLAESE HELP:(

Where did it say 1.6 GHZ? If in windows it could be the cpu throttling down to save power. If when you set the FSB to 333, you left vcore on auto, the board will possibly set the vcore very high, thusly given you high temps. And if you try and read the vcore with cpuid it will read low.....

Just a bunch of maybes.....
10-20-2006, 09:51 AM
mikepaul

Quote:

Originally Posted by Falkentyne

Two quiet clicks....that sounds like a hard drive head dying...could be wrong, though....(a head dying and freezing can cause the entire system to freeze).

That sound could also be from a hard drive starved for power.

When I had another failure to boot due to no hard drives found, I checked and noticed the plug into the slave drive (the one with recent troubles) wasn't on solidly. Sure, I had shoved it on until it clicked, but it still rattled like the pins inside weren't attached solidly. Another plug had already proven to be unreliable so it's not like I wasn't warned.

So I demoted that plug to powering a fan and put another one on the HD, then still moved the swapfile to C:, and the machine ran all night. I may still splurge for another PSU with attachable cables so I can cut back on splitters. Meanwhile I may need to figure out if they sell kits to rebuild these plugs. This was the PSU I got via RMA when the first one seemed bad.

Thanks...
10-20-2006, 10:43 AM
pee4

Quote:

Originally Posted by lawrywild

I just let it boot when it happens, it does nothing, don't worry about it

That's good to know. Thanks.
10-20-2006, 11:20 AM
lawrywild

Np, afaik it's supposed to show up every once in a while.
10-20-2006, 02:00 PM
Mxtra

I have a big problem. The second core on my 6600 stops working after I leave my pc on for a while. When I reboot, it goes back to normal. It'll then work fine for a few hours or maybe several days straight, but eventually it happens again. I'll run something multithreaded and the first core will be maxed out and the second core will be virtually unused. I tried a fresh install with xp pro and home and same problem with both. I ran Othos the last time it happened and got the following error message: Affinity Mask: Process: 0x1 Sys: 0x3. Anyone have any ideas on what's going on?
10-20-2006, 02:20 PM
Mxtra

I just found a post about someone wanting to use just one core and doing this: run,msconfig,boot.ini tab,boot.ini advanced options, /numproc (set to number of cores to 1). So I did that but set it to 2 to see if it helps. It was blank by default. Hopefully, this'll do the trick. For some reason, I'm not that hopeful that it will.
10-20-2006, 02:29 PM
Tallman

Quote:

Originally Posted by Richard Dower

You Asus guys have too many hits!, 165,000...us Gigabyte folks are launching a campaign to beat y'all.

:-)

LOL, keep posting in this thread please and see if you beat this one.
10-20-2006, 02:47 PM
revenant

MXtra - sounds like a bad cpu maybe?? you could try a full socket reseat.. blow the socket off when the cpu is out also.. good luck!
10-20-2006, 04:37 PM
Tallman

Quote:

Originally Posted by virtualrain

Please let me know if you find any improvements or issues! Thanks again Tallman!

Well, I tried 1305, and for me at least, 1402 is better. More stable.
With 1305, when I boot at 390 fsb, I cannot bench and it shuts down after about 30 seconds with 1.7 vcore.

Same vcore and fsb of 390 with 1402 and I can bench and stays running.
So it is 1402 for me all the way.

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