0x0000000A DC will not boot up!

[Guest]

We were doing some re-routing of power cables this past weekend so we had to
shut all of our servers down for about an hour. Of course the first server
(DC) we power up we get this Stop error:
Stop: 0x0000000A (0x000004E7, 0x0000001C, 0x00000000, 0x8042B857)
IRQ_NOT_LESS_OR_EQUL
*** ADDRESS 8042B857 BASE AT 80400000, DATESTAMP 403D35E2 - NTOSKRNL.EXE
I have searched these forums and google for helpfull info but all of the
info I have found pertain to doing things while the OS is running. We can
not get past the BSOD. We can not even invoke F8 to try "Last known good".
Is there a way to recover from this or should I get
out the Windows CD and start reinstalling? By reinstalling and running
DCPROMO I should be back up and running with no problems right? Any help
would be greatly appreciated!
Thanks,
Adam

 

[S.J.Haribabu]

Hi,

Solution -1
===========
The cause was probably incompatible hardware. Install the hard drive into
another system. Check whether WIndows boot up properly and works fine.

Solution -2
=========

Update the system BIOS to the most current version.

CAUTION - Try this solution at last, sometimes the system may not boot if
the BIOS is not properly loaded.


Solution - 3
==========

Searched and found the following articles. The reason there may more than
one possibilities for this error. But I believe it could wrong device
driver. please look in to the web links and try this solutions.

When using the ActiveSync 3.1 software on a USB connection

Apparently some conflict between the onboard (in this case, unused) Symbios
SCSI controller

DIsable the service or device driver which you think it may cause the
problem. Go thru this article on how to do
http://support.microsoft.com/kb/244905/EN-US/
Mainly try to stop the anti virus software. Use recovery console for do the
same.

I hope the above posting might be helpful for you.

Thanks,
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Well I was able to run CHKDSK /F and if seams to have fixed some errors. I
want to thank all of you for your responses. I have a lot of good
information for future failures now!