XP SP2 RC2 loading problem

[Thantos]

Hi, I just installed the SP2 RC2 for win xp and after doing so on reboot I recieve a blue screen stating that windows was unable to restart... I tried to restart and I get the same thing again even when I try to load into safemode... One interesting thing is that as I try to load into safe mode 2 dll's ask if I want to skip loading them before it blue screens.

While installing SP2 I had an error regarding atapi.sys which I fixed by renaming it... Not sure if this is the cause...

Specs:

P4 1.8 ghz

Symantec corp antivirus 8

Internet security firewall

Does any one know how I can fix this? Or perhaps how to rollback or uninstall sp2 via dos?

Any help would be appreciated thx!

[Heathen]

Boot into safe mode and when it comes up with a YES or NO option... hit no and do a system restore. I had the same problem when I tried to load SP2

[Thantos]

Thanks for the reply.. Ummm it doesn't even make it to that message before it blue screens

[Heathen]

You mean it crashes in safe mode?

[Thantos]

Well when it tries to enter safe mode it crashes and when it tries to load windows in normal mode it crashes.. The only difference in safe mode is that the does loading of dlls occurs but afterwhich it crashes immediately before it can switch from dos to windows

[Nick Sheldon]

sfc /scannow run this in command prompt.

It will check your system files, and probably ask you for your cd if they are corrupted.

Hopefully it will flag your atapi.sys

[Thantos]

cool, I will try that.. However will I have to have a slip streamed sp2 windows xp cd fro that to work?

[Thantos]

I just checked the error message again and it is as follows..

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE

The Stop 0x7B message indicates that Windows XP Professional has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.

Interpreting the Message

This Stop message has four parameters:

The address of a Unicode string data structure representing the Advanced Reduced Instruction Set Computing (RISC) Computing (ARC) specification name of the device at which you attempted startup.

Pointer to ARC name string in memory.

This value is 0x00000000 (zero).

This value is 0x00000000 (zero).

The first parameter typically contains two separate pieces of data. For example, if the parameter is 0x00800020, 0x0020 is the actual length of the Unicode string and 0x0080 is the maximum ARC name string length. The next parameter contains the address of the buffer. This address is in system space, so the high-order bit is set.

If the file system is unable to mount the boot device or simply does not recognize the data on the boot device as a file system structure, the following parameter definition applies:

The address of the device object that could not be mounted.

Error code value or 0x00000000 (zero).

This value is 0x00000000 (zero).

This value is 0x00000000 (zero).

The value of the first parameter determines whether the parameter is a pointer to an ARC name string (ARC names are a generic method of identifying devices within the ARC environment) or a device object, because a Unicode string never has an odd number of bytes, and a device object always has a Type code of 0003.

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

Disks or storage controllers that are failing, defective, or improperly configured.

Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.

Resolving the Problem

The following suggestions are specific to Stop 0x7B errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.

Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured. For more information about the Boot.ini file, see "Troubleshooting Startup" in this book.

Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP Professional setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.

Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.

Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this appendix.

For more information about Stop 0x7B messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000007B, 0x7B, and Txtsetup.oem.

Now the questions is how would I fix this?

[felixml]

one of my office PCs did something very similar, reinstalled XP, faster then trying to find what is wrong...

[dougkinzinger]

You've got either some funky hardware or some funky drivers.

Yes, I too would likely reinstall XP to solve.

[Thantos]

so install win xp over the exisiting? (I haven't backed up all my files yet because I don't have a large enough hd to transfer them to.. or I would have formatted...

@Yakkob how do I operate teh sfc /scannow command because when I tried it in COmmand and also in the recovery console it says that it is an unknown command...

[dougkinzinger]

Yakkbob did not read your problem correctly. He thought you could actually get into Windows.

You can, yes, install over the existing installation by booting off the XP CD. That is what I would do if I hadn't backed up my stuff.

[Thantos]

THX I guess I have no choice but to do that

[mikey1001]

I think your problem might have something to do with programs like Daemon Tools or Alcohol 120%. Do you have any of those installed or running at bootup? If you do, you had to get rid of them before applying SP2.

[Thantos]

Ok I've reinstalled XP however now I am unable to access my software such as MS office to backup the address book etc.. Does anyone know how I can back it up?

As well, since I had a password on my old user account I am unable to access it..

is there any way to import the old user into the new windows or perhaps decrypt the folder (which is located in Doc and Settings)

[cuzabis]

I too have got this error and have found a few different ways around

UNINSTALL alcohol and/or daemon tools or any thing else that uses virtual drives on your comp

some people need to disable IDE DMA Bus-Mastering go to http://support.microsoft.com/default.aspx?...kb;EN-US;158873

(this error is posted at http://support.microsoft.com/default.aspx?...&NoWebContent=1

Some need to rename the Atapi.SYS file to something like Atapi.SY_ or something

(renaming did not work for me)

For some all you need to do is install it in Safe Mode

I havent tried all these methods yet, I still experience the error and have had to restore my computer back to Sept 1 5 times already

Skipping file didnt work, renaming file didnt work...this attempt I Have alcohol uninstalled AND im going to install in Safe Mode, I will post again to let you know if I have solved the problem

It took me 3 days to find all these solutions for the Atapi.sys error with SP2

I hope y findings help others

[cuzabis]

no luck still have the error, im going to need to reboot windows ive tried everything but the DMA Bus thing because I do not want to play around with the registries