Prev: Gigabyte mobo ?
Next: Connecting a UFS harddisk
From: philo on 7 Nov 2009 11:52
Sarge� wrote:
> 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
>
>


I'd start out by resetting the bios to defaults
From: philo on 8 Nov 2009 01:03
Sarge� wrote:
> On Sat, 07 Nov 2009 10:52:16 -0600, philo <philo(a)privacy.invalid>
> wrote:
>
>> Sarge� wrote:
>>> 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
>>>
>>>
>>
>> I'd start out by resetting the bios to defaults
>
>
> Nope, no go.



All I can think of would be to run a RAM test
and HD diagnostic
From: philo on 8 Nov 2009 11:55
Sarge� wrote:
> On Sun, 08 Nov 2009 00:03:03 -0600, philo <philo(a)privacy.net> wrote:
>
>> Sarge� wrote:
>>> On Sat, 07 Nov 2009 10:52:16 -0600, philo <philo(a)privacy.invalid>
>>> wrote:
>>>
>>>> Sarge� wrote:
>>>>> 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
>>>>>
>>>>>
>>>> I'd start out by resetting the bios to defaults
>>>
>>> Nope, no go.
>>
>>
>> All I can think of would be to run a RAM test
>> and HD diagnostic
>
> I ran the mem test off the Win7 CD with no errors found. Would the HD
> affect the Post ?



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 ...
From: kony on 8 Nov 2009 17:00
On Sun, 08 Nov 2009 10:55:58 -0600, philo
<philo(a)privacy.invalid> wrote:


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

Run memtest86+ overnight, at least several hours.



>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

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.
From: kony on 11 Nov 2009 16:08
On Mon, 09 Nov 2009 19:44:40 -0400, Sarge�
<sarge(a)dontbother.com> wrote:


>>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.
>
>
>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.

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.
 | 
Pages: 1
Prev: Gigabyte mobo ?
Next: Connecting a UFS harddisk