Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD 0x0000007E and atapi.sys error


  • Please log in to reply

#1
stezie

stezie

    New Member

  • Member
  • Pip
  • 1 posts
Using Windows Xp I had to power down due to a frozen screen. When I re-booted I got the BSOD with the following errors:

Stop: 0x0000007E (0xf75663c0, 0xF7A24528, 0xF7A24224)

atapi.sys - addressF75663c0 base at 7550000, date stamp 41107b4d.

I can't boot up using safe mode or last know configuration as it returns to the BSOD. The only options that work are F2 start up and F12 boot options.

Can someone give me step by step instructions on how to resolve this
  • 0

Advertisements


#2
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
If you have Windows CD...(if you don't have Windows CD, scroll down)

1. Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD.
2. Once you have booted from CD, do NOT select the option that states: Press F2 to initiate the Automated System Recovery (ASR) tool.
You’re going to proceed until you see the following screen, at which point you will press the “R” key to enter the recovery console:

Posted Image

3. After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (typically number “1″).
Select the installation number, and hit Enter.
If there is an administrator password for the administrator account, enter it and hit Enter (if asked for the password, and you don't know it, you're out of luck).
You will be greeted with this screen, which indicates a recovery console at the ready:

Posted Image

4. There are eight commands you must enter in sequence to repair your problem..
NOTE. Make sure, you press Enter after each command. Make sure, all commands are exact, including "spaces".
These commands are as follows:

CD..
ATTRIB -H C:\boot.ini
ATTRIB -S C:\boot.ini
ATTRIB -R C:\boot.ini
del boot.ini
BOOTCFG /Rebuild


Note about the above command.
BOOTCFG /REBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors.
It is very important that you do one or both of the following two things:
A.) Every Windows XP owner must use /FASTDETECT as OS Load Option when the rebuild process is finalizing.
B.) If you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option.
For the Enter Load Identifier portion of this command, you should enter the name of the operating system you have installed.
If, for example, you are using Windows XP Home, you could type Microsoft Windows XP Home Edition for the identifier (it's not crucial, however what the name is, as long, as it's meaningful).
Here is your computer screen:

Posted Image

5. Following command verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, it’s still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit:

CHKDSK /R

6. This last command writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are Sure you want to write a new bootsector to the partition C: ? just hit “Y”, then Enter to confirm your decision:

FIXBOOT

7. It’s time to reboot your PC by typing
EXIT
and pressing Enter.

With any luck, your PC will boot successfully into Windows XP as if your various DLL, Hive, EXE and NTLDR errors never existed.



If you don't have Windows CD...
Download Windows Recovery Console: http://www.thecomput...om/files/rc.iso
Download, and install free Imgburn: http://www.imgburn.c...hp?act=download
Using Imgburn, burn rc.iso to a CD.
Boot to the CD...let it finish loading.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Then, follow instructions from Step #3 above.
  • 0

#3
ezink

ezink

    New Member

  • Member
  • Pip
  • 1 posts
Broni,

Why is your solution supposed to work to fix this problem.

I had the same problem about a month ago.... Went searching online for a solution. I came across your solution a tried it. It did not work. Tried it again.. Still did not work.

Tried other ideas I came across online.. nothing worked.

I finally gave up and broke down and did a Windows Install Repair with SP2 and then reinstalling sp3.

That worked, but their has to be an easier way.

Now, here I am today. Same dang problem.

I start up the computer. Windows XP starts to load, shows the Window Xp sceen, then goes to BSOD with message:
stop: 0X0000007E, (0XC0000005, 0XF74B07C0, 0XF789E528, 0XF789E224)
atapi.sys - address F74B07C0 base at F749A000, Date stamp 4802539d

So, I don't understand why your boot.ini fix should work, when Windows already begins to start, but then stops..

Plus, since I cannot get to my C-drive windows installation, on reboot, I use the same boot.ini to select another installation of XP on another drive, from which I am typing from now, and searching for a solution to the problem of getting into my main XP installation.. All my installed programs are on the C drive, this is just a backup that I never really use..


So...

1.) Do you have any other solution that would work to fix the problem..
and

2.) Would turning off the switch at the back of the computer lead to this problem?

I normally, shut down my computer using the windows start button to turn off the computer and let it at that, without turning off the power supply switch.

Earlier today, I shut off the computer using the windows start button. After the computer turned off, I then turned off the power supply switch on the back of the computer. When I returned home later and started up the computer is when I then ran into the BSOD with error message: stop: 0X0000007E, with atapi.sys listed.

It seems to me, that when I had the same problem a month ago, that it was the same scenario... I shut down the computer using windows start button, but then turned off the power supply switch.

Could turning off the power supply switch be causing any problem?
  • 0

#4
Diana Mon

Diana Mon

    New Member

  • Member
  • Pip
  • 1 posts
Hi,
I got the same error and after reading a lot of forums I got the solution:

0x0000007E (0xf75663c0, 0xF7A24528, 0xF7A24224)
atapi.sys - addressF75663c0 base at 7550000, date stamp 41107b4d.

What I did:

1.As the error is about atapi.sys driver that probably is missing or corrupted I took from another computer (With the same version of Windows in my case XP) that file (atapi.sys) that is in C:\WINDOWS\system32\drivers and I save that file in an USB.

2.Insert a CD of (Linux any version, in my case I did it with ubuntu) into the unit in the computer with the problems.

3.Start the computer with the problem and boot it from the CD (I did it pressing F12 when the computer is starting) Then Boot from CD/DVD

4.In the Linux CD there is an option to use the Operative System without installing it, usually the first option. When you click there you will be in a Ubuntu enviroment.

5.Insert the USB where is the file atapi.sys (that we already got from another computer) and using Linux console (click in applications then console) copy that file from the usb to C:\WINDOWS\system32\drivers. It means replace the old atapi.sys file with the one that we got from the other computer.
This can be done using cp command of linux.


6. Restart the laptop took out the linux cd and should work now.

That is how i fixed.

Hope this can help.
  • 0

#5
ubyte

ubyte

    New Member

  • Member
  • Pip
  • 1 posts
removed malware advice

Edited by Rorschach112, 20 May 2010 - 02:04 PM.

  • 0

#6
pcs365_2

pcs365_2

    Member

  • Banned
  • PipPip
  • 49 posts
Hi,

First, make sure that you have sufficient hard disk space. The Stop error can be caused by insufficient hard disk space.

If you can use safe mode or the Recovery Console to start the computer, delete any unnecessary temporary files, Internet cache files, program backup files, and files that contain saved file fragments from disk scans (.chk files). You can also install Windows XP on another hard disk that has more free space.

If you cannot start the computer, go to the next method to update the computer BIOS.

For more information about safe mode or the Recovery Console, click the following article numbers to view the articles in the Microsoft Knowledge Base:
315222 (http://support.micro....com/kb/315222/ ) A description of the Safe Boot Mode options in Windows XP
314058 (http://support.micro....com/kb/314058/ ) Description of the Windows XP Recovery Console
  • 0

#7
itworks

itworks

    New Member

  • Member
  • Pip
  • 1 posts
Diana Mon - above has the right answer to this STOP issue.

I'd like to add that you can get Ubuntu from here:
http://www.ubuntu.co...ubuntu/download

and it shows you how you can create a bootable CD (or USB memory stick if more useful).

Make sure you're computer will boot from your CD (or USB device) and Ubuntu will then load automatically allowing you to copy over the correct file (in this case atapi.sys) - it really is that easy - the alternative would mean a time-consuming format !

Edited by itworks, 15 June 2010 - 08:46 AM.

  • 0

#8
Big Mac 25

Big Mac 25

    New Member

  • Member
  • Pip
  • 1 posts
I tried the exact same thing in the first post by Stezie and it did not work either. Was still getting the BSOD 0x0000007e atapi.sys error. After I scrolled down further I was starting to download the ubuntu file (700 MB) that was referenced in Diana Mon's posting.

While waiting for that download I came acress "Hirens Mini XP Boot CD". This file was half the size and it worked amazingly well.

http://www.hirensboo...d.html?ver=10.6

I created a bootable CD from it (the program will create everything for you) and placed it in the troubled desktop. It booted up to the CD (here's a link to some screen shots, scroll down to miekiemoes Feb 3, 2010 post) - http://forums.malwar...52

Then I simply copied an atapi.sys file from a similar and working XP SP3 system to a flash drive and from this Mini XP OS was able to simply copy it back to the troubled system. Rebooted and worked like a champ!

the hiren's Mini XP boot CD is a great tool to use in your "bag of tricks"

hope this posting can help someone and save a lot of time and aggrevation.

Mark
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP