Archived from groups: microsoft.public.windowsxp.general (
More info?)
notme wrote:
> I tried several things from that site already. Tried a few more...
> The machine will not boot to safe mode.
> Attempting to reinstall Windows results in the same error. (STOP 0x000000D1)
> Docmem says the memory is fine. I switched the 512MB strip for a 1GB strip
> (both PC333) and reran docmem, all OK.
> I removed the EIDE CD drive and installed a floppy to boot from.
> I copied the atapi.sys file from another XP Pro machine, but I get 'invalid
> directory' when trying to cd\windows\system32\drivers\ to copy it over. The
> directory is visible in the DOS window, just not accessible. Maybe the HDD
> is corrupted, but even trying to do a repair install fails.
> The only addin cards are a modem and a SB LIve card.
> The video, USB and NIC are onboard.
> If anyone has more suggestions, please post them!
> TIA
> "Will Denny" <willdenny@mvps.org> wrote in message
> news:uyTmKDilFHA.1968@TK2MSFTNGP14.phx.gbl...
>
>>Hi
>>
>>Please try the following link to Jim Eshelman's web page - left hand
>>column
>>(0A)
>>
>>http://aumha.org/win5/kbestop.htm
>>
>>--
>>
>>Will Denny
>>MS-MVP Windows Shell/User
>>Please reply to the News Groups
>>
>>
>>"NotMe" <Dewmealso@aol.com> wrote in message
>>news:OKksIAilFHA.3552@TK2MSFTNGP10.phx.gbl...
>>
>>>I have a C2.7/512MB/XP Pro SP2 system I built last year.
>>>It worked fine until yesterday.
>>>While in use, it blue screened and started a continous boot/reboot cycle.
>>>Occasionally, it will actually stop on the BSOD with the error and lists
>>>atapi.sys as the culprit every time.
>>>I tried a repair install. It loads all the files then reboots to continue
>>>the install, again the same error.
>>>I am currently building a boot CD with Doc Mem to test the RAM, any other
>>>ideas?
>>>TIA
>>>--
>>>For evil to prosper requires only that good men remain silent!
>>>
>>
>>
>
>
I had this problem develop suddenly as well and then it seem to get
better but then came back stronger and faster! Im the end after endless
searching I came to the opinion that it was because I had installed or
modified a driver or hardware that was disagreeing with windows. I
checked the IRQ list in device manager and although I had several items
that shared the same IRQ none of them seemed to be marked with a yellow
! mark. I ran the driver verifier and after rebooting it showed me the
problem. In ignorance I deleted the file thinking that windows will
reinstall it when I rebooted. Boy was i wrong I got another BSOD and
then when I attempted to sort THAT out I got a BSOD on reboot that would
even let me boot in safe mode let alone normal!!
I tried many things, like using the restore(or is it repair) console in
xp but that didn't work either. In the end I had to do a clean reinstall
of windows and decided to reformat my drive at the same time. I then
installed all my HDD and other devices one by one and made sure I had
the latest drivers for each one. That was a LONG Friday I can tell you!
Fingers crossed - I havnt had a problem since Friday!
If you want my advice think carefully which device or driver you
installed before the problem first started and then go back and either
to a rollback (in the case of the driver) or a clean uninstall, reboot
and install (in the case of the hardware). Make sure you do a system
restore before this just in case and also make sure EVERYTHING is uptodate.
Hope this helps and works out better for you.
Zankhna
Facebook
Twitter
Instagram