P5WD2-E system "hang" after memory size

Hello!

I built a PC based on the ASUS P5WD2-E board. Lately, the computer at
bootup appears to hang at the memory size display, and before the drive
preipherals are detected and listed. This lasts for an indeterminable
amount of time. However, the PC still responds to keypresses that are
used to enter the CMOS setup screen, and the boot device screen. I warm
boot it and the problem goes away.

What do you think is causing this problem?

I suspect the memory. But I am using Corsair PC6400 CL4 memory, which
has been tested. I can run an overnight test if that will make a
difference.

Thank you!

Bob Graham

PS: My last board, a P5WD2 Premium, had a malfunctioning memory
subsystem. So I purchased my current board. I wonder if this series of
ASUS board has a history of onboard memory subsystem problems.

In article 1152214877.940981.275320
@k73g2000cwa.googlegroups.com, says...
Hello!

I built a PC based on the ASUS P5WD2-E board. Lately, the computer at
bootup appears to hang at the memory size display, and before the drive
preipherals are detected and listed. This lasts for an indeterminable
amount of time. However, the PC still responds to keypresses that are
used to enter the CMOS setup screen, and the boot device screen. I warm
boot it and the problem goes away.


I have same issue with the P5LD2 del. Several years ago the
problem was called the cold boot problem. Never was a solution
..Does it never cold boot or just take forever ?

It sounds like the problem is that it is waiting for the hard drive to
acknowledge it is ready. If it was a memory fault, you should get some
info to that effect. Because you can get to the CMOS it appears it
completed the memory test just fine.

Ken wrote:
It sounds like the problem is that it is waiting for the hard drive to
acknowledge it is ready. If it was a memory fault, you should get some
info to that effect. Because you can get to the CMOS it appears it
completed the memory test just fine.

Good point. However, the memory test during POST is not comprehensive.
Also I have seen memory problems turn up in the functionality of an
operation without any reported memory errors, like the copying of
files.

Sometimes it waits forever during the cold boot, but I think it
eventually boots. I get impatient and hit the reset button. I have a
RAID 0 setup between two 150G Western Digital 7200 rpm drives. I am
using the Intel RAID controller. Maybe it is a problem with the RAID
configuration?

The memory subsystem problem I talked about made any type of plugged in
memory return errors during testing with a standalone bootable memory
test program. I changed the board and the problem went away, after I
returned three sets of memory.

Thanks for your help!

Bob Graham

CeeBee wrote:
wrote in alt.comp.periphs.mainboard.asus:

I suspect the memory. But I am using Corsair PC6400 CL4 memory, which
has been tested. I can run an overnight test if that will make a
difference.

Do you mean that you tested it with a hardware tester or software tester or
that the manufacturer claims it has been tested?

If so, try http://www.simmtester.com/PAGE/products/doc/docinfo.asp and let
it run for a few hours.

--
CeeBee

*** The Cookie Has Spoken ***

I used a softwaare tester from Microsoft. I will look at your link.

Bob Graham

troop wrote:
In article 1152214877.940981.275320
@k73g2000cwa.googlegroups.com, says...

I have same issue with the P5LD2 del. Several years ago the
problem was called the cold boot problem. Never was a solution
.Does it never cold boot or just take forever ?

Interesting. I looked through the ASUS forums and found an applicable
item. It appears that the system will seem to hang (take forever) if
any of the three or more pronged fan sockets are used that monitors fan
speed. I think I will try this out. But then I do not want to give up
the ability for my BIOS to control the CPU fan speed.

Bob Graham

"Bob Graham" wrote in message
ups.com...

troop wrote:
In article 1152214877.940981.275320
@k73g2000cwa.googlegroups.com, says...

I have same issue with the P5LD2 del. Several years ago the
problem was called the cold boot problem. Never was a solution
.Does it never cold boot or just take forever ?

Interesting. I looked through the ASUS forums and found an applicable
item. It appears that the system will seem to hang (take forever) if
any of the three or more pronged fan sockets are used that monitors fan
speed. I think I will try this out. But then I do not want to give up
the ability for my BIOS to control the CPU fan speed.

Wow. I have been following this thread because I have the same problem and
the above entry kicked me into gear. My problem started happening right
after I bought a new fan for the case side. Instead of a two element
connector (like the original fan) it had three so I connected it to the
motherboard three pronged connector instead of the case's two pronger. I
can't wait to get home to test this as the long boot-up time is annoying as
hell.

BTW: Since my case also has a thermostat to control the fan I really don't
need the BIOS to control it, but I am not sure which of the three fan wires
I need for the two pronged case connector. I can make my own connector but
would like to make sure I get the correct wires connected G.

Thanks for the clue,
Don Freeman
--
Ever had one of those days where you just felt like:
http://cosmoslair.com/BadDay.html ?
(Eating the elephant outside the box, one paradigm at a time)

Don Freeman wrote:

[snip]

BTW: Since my case also has a thermostat to control the fan I really don't
need the BIOS to control it, but I am not sure which of the three fan wires
I need for the two pronged case connector. I can make my own connector but
would like to make sure I get the correct wires connected G.


There is a molex to fan power cable converter that you can purchase.
Thanks for the comfirmation. Please post back if unplugging the fan
connector solves this problem.

Bob Graham

True about the memory post not being that thorough but I thought you
said you had done added testing. You could swap or remove and try
individual modules.

You might try changing the boot order in the bios and put the CD ahead
of the Raid. If it comes up with the any key boot cd message quicker
that'd be an indicator. It also might pause the booting long enough for
the drive to stabalize. If the SATAs are set to high speed you could
also back that down as an experiment.

I have had older drives exhibit similar characteristics. An aging
bearing was the culprit. Just could spin up quick enough for the system
and a reboot would get it going. They finally got noisy and proved the
idea.

True about the memory post not being that thorough but I thought you
said you had done added testing. You could swap or remove and try
individual modules.

You might try changing the boot order in the bios and put the CD ahead
of the Raid. If it comes up with the any key boot cd message quicker
that'd be an indicator. It also might pause the booting long enough for
the drive to stabalize. If the SATAs are set to high speed you could
also back that down as an experiment.

I have had older drives exhibit similar characteristics. An aging
bearing was the culprit. Just could spin up quick enough for the system
and a reboot would get it going. They finally got noisy and proved the
idea.