Post Troubleshooting help

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View


Need a little help finding out why my box takes about 1 to 2 minutes
to move past the Main Processor line during the Post.  It seems to
stall right after ID'ing the processor.  A minute or two later the Mem
test starts and everything boots normally.  Once in the OS, seems fine
while using it but if left on overnight ... it will not respond to
mouse clicks (ie ...  double clicking on an icon will bring up the
busy cursor and that's where it will stay until I do a hard reset).
Other sporadic annoyances such as cursor jumping and jerky page
scrolling in fire fox have been happening also.

No new hardware/software has been added and power settings are set at
always on.  This wasn't a gradual build up either, just one day
everything started happening.  So far I have swapped out the Power
Supply, memory, Video card and HD and even tried the Monitor...lol.  I
believe its obviously the Motherboard or Processor but would like to
think I have missed something here.

Any ideas?

Sys build

Asus M2N32-SLI Deluxe (latest posted BIOS) (reflashed today)
AMD Athlon 64 X2 (6400+)
4 Gigs Corsair Memory
Geforce 8800 GTS
Booting from a WD Raptor



Re: Post Troubleshooting help



Sarge® wrote:
Quoted text here. Click to load it


I'd start out by resetting the bios to defaults

Re: Post Troubleshooting help



wrote:

Quoted text here. Click to load it


Nope, no go.

Re: Post Troubleshooting help



Sarge® wrote:
Quoted text here. Click to load it



All I can think of would be to run a RAM test
and HD diagnostic

Re: Post Troubleshooting help




Quoted text here. Click to load it

I ran the mem test off the Win7 CD with no errors found.  Would the HD
affect the Post ?

Re: Post Troubleshooting help



Sarge® wrote:
Quoted text here. Click to load it



I've had flaky HD's cause a machine hesitate prior to posting...

can't hurt the check it.

Just go the the HD mfg's website and they will have a free diagnostic
utility.


Also: You can try just disconnecting the drive and see how fast the
machine posts...then goes to the "no OS" error


Finally...check the bios to see if maybe instead of having all channels
set to AUTO, you *might* have one set to some non-existent device ...

Re: Post Troubleshooting help



On Sun, 08 Nov 2009 10:55:58 -0600, philo


Quoted text here. Click to load it

Run memtest86+ overnight, at least several hours.



Quoted text here. Click to load it

Good idea, and it might be possible that the SATA connector
on the board or the cable itself is flaky, try another
connector and cable.  It does seem like it could be an
intermittent or failing hard drive issue, he might also
check Windows Event Viewer to see if anything related is
logged.

Re: Post Troubleshooting help




Quoted text here. Click to load it


Looked at the event logs.  A bunch of Critical's from when I had to
force a shut down. However the seems to be a controller problem under
event ID 11 happening around the same times.

"The driver detected a controller error on \Device\Harddisk5\DR5."

The number of the Harddisk and DR change every now and then but the
times are pretty close.  I would assume that the Sata controller is
pooched ?  All my drives are Sata.

Re: Post Troubleshooting help



On Mon, 09 Nov 2009 19:44:40 -0400, Sarge®


Quoted text here. Click to load it

That is usually a sign the hard drive, not the controller is
failing, but it could also be something as simple as a bad
connection at the drive or board, the cable loose, faulty
cable, etc.

Re: Post Troubleshooting help <---- Solved




Quoted text here. Click to load it


Apparently in my obsession with routing cables, I missed the cable
coming from my multi card reader and it was plugged in the whole time.
Once I unplugged it, everything worked again.  I would have never in a
million years figured that a card reader would affect the post ....
but it did.  Thanks to Philio and kony for your suggestions and help.

Re: Post Troubleshooting help <---- Solved



On Wed, 11 Nov 2009 22:55:47 -0400, Sarge®

Quoted text here. Click to load it


I had the same problem with an Abit IP35-E board... took me
about a year to figure it out (wasn't trying all that time,
coincidence just lead to the discovery eventually).

Re: Post Troubleshooting help <---- Solved



Sarge® wrote:
Quoted text here. Click to load it
<snip>

Quoted text here. Click to load it



Thanks for posting back...

I've seen USB devices do that

Re: Post Troubleshooting help



wrote:

Quoted text here. Click to load it

Well ... I ran the HD test in both quick and advanced with no errors.
Disconnected everything with the same result and even took the battery
out of the Mb and reversed it for 30 secs. Made sure any empty slot
was disabled in the BIOS. I think we pretty much covered everything
Philo


Site Timeline