this error appears on boot up: XXX STOP: OX0000007B (OX84EODBA0, OXC0000034, OX00000000, OX00000000) what does it mean?

Anonymous

OS: VISTA

HP pre-installed recovery partition which fails to respond to F11 preset Run Recovery.

CPU, Drives, Memory test out perfect under F2 and dropped screen (ALT-F2, HP set hot key).

BIOS seeks an administrator password but I never set one...how can I over ride that?

Recovery disk iniates windows which then crashes.

Boot Section on Drive C: unaccessible

OK the HP might seem like a bunch of junk to many people but i use it, it was speedy, it had a longer than usual boot up with aero running and running but reg was fairly clean, not any cookies stored, no junk programs....How can I get this back up? Windows provides a blue screen and provides the above error code no access to DOS.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Hi,

You probably should seek technical help at your local computer shop (not leeks and peeks at BestBuy or other

big box stores).

Cause

The INACCESSIBLE_BOOT_DEVICE bug check frequently occurs because of a boot device failure. During I/O system initialization, the boot device driver might have failed to initialize the boot device (typically a hard disk). File system initialization might have failed because it did not recognize the data on the boot device. Also, repartitioning the system partition or installing a new SCSI adapter or disk controller might induce this error.

This error can also occur because of incompatible disk hardware. If the error occurred at the initial setup of the system, the system might have been installed on an unsupported disk or SCSI controller. Some controllers are supported only by drivers that are in the Windows Driver Library (WDL). (These drivers require the user to do a custom installation.)

Resolving the Problem

This error always occurs while the system is starting. This error frequently occurs before the debugger connection is established, so debugging can be difficult or impossible.

Resolving a failed boot device problem: If a boot device is at fault, you must edit the boot options.For more information about these options, see Boot Options for Driver Testing and Debugging.

http://msdn.microsoft.com/en-us/library/aa468636.aspx

Resolving an incompatible disk hardware problem: If Setup autodetects the controller, you might have to skip detection and use a specific manufacturer's disk to load the driver. Also, check the availability of updates for the system BIOS and SCSI controller firmware. Updates of this kind are typically available on the Web site or BBS of the hardware manufacturer.

Remove any recently added hardware, especially hard disk drives or controllers, to see if the error is resolved. If the problematic hardware is a hard disk drive, the disk firmware version might be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. If you removed another piece of hardware and the error is resolved, IRQ or I/O port conflicts likely exist. Reconfigure the new device according to the manufacturer's instructions.

Confirm that all hard disk drivers, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List.

If you recently added a driver, restart your computer, and press F8 at the character-based menu that displays the operating system choices. In the Advanced Options menu, select the Last Known Good Configuration option. This option is most effective when you add only one driver or service at a time.

In addition, check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

This error can also occur because of hard disk corruption. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

If you cannot start the system in the last known good configuration, you should try to start off the Windows CD. Then, you can run Chkdsk from the Repair Console.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk drive from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

If your system has SCSI adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination. For IDE devices, define the onboard IDE port as Primary only. Also check each IDE device for the proper master/subordinate/stand alone setting. Try removing all IDE devices except for hard disks. Finally, check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error.

It is helpful to know as much as possible about the boot device that Windows is installed on. For example, you can investigate the following items:

Find out what type of controller the boot device is connected to (SCSI, IDE, 1394, etc). Find the manufacturer of non-IDE controllers (Adaptec, Symbios, and so on).
Note the SCSI ID of the boot device if you are using SCSI.
Indicate if other devices are attached to the same controller that the boot device is on (CD-ROM drives, zip drives, and so on).
Note the file system that is used on the drive.

Rob - Bicycle - Mark Twain said it right.

0 comments

3 additional answers

Anonymous

2009-11-15T05:19:18+00:00

This is exceptionally helpful. I am still working with these facts.

I don't know how the rating box works but I so value your answer it deserves the highest rating. I connected the hp to a functional standard hp also with

authentic vista, and ran a forced diagnostic tool set. You are right where the windows vista or (?) is seeking windows specific drivers ; I had almost all of the drivers running /not corrupt.

I am in process of more testing but the facts you present are exceptionally good. Thanks.

This episode has given me new respect for the tenacity of windows even damaged.
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-15T04:51:49+00:00

This is exceptionally helpful. I have made substantial progress with the facts you present. I am not yet able to be free of the blue screen windows self protect.

Preceding work: 1. separated vista program files from all others = 2 separate drives = corrupted the registry

                       2. moved the hp recovery to its own partition which I made the sole boot drive partition: power to factory original preload

                        3. went to dos from start up before vista runs; wrote boot cmd to the hp partition. made a usb boot recovery flash drive.

                        4. closed dos correctly. boot into vista and accessed isolated files partition.

                        5. used the 3x disc cleaner (DOD) in other programs partition only; = the 0000000000 in the above error code.

                        4. restart back into original factory condition which needed vista 1 & 2 service pack, and hp driver updates.

                        6. disabled wireless modems and installed peripheral modem. went on the internet and saved debian project to empty disk partition.

                        7. logged off. shut down. removed battery.

Current condition:    A. Powers up, races through self diagnostic, CPU passes, Disk Passes, Memory Passes.

                              B. In Boot Manager screen not one tool is available but lists many (F8 Command)

                              C. Pre programed to load start up options but none working. (ie: safemode/windows recovery/bios)

                              D. Self starts what I believe is vista boot- the lights loop runs a few times, flashes a blue screen, then goes to pre programmed start up

                                  choices.

                              E. Peripheral modem works but can't access internet w/o os working.

                              F. USB Flash boot lights up, blinks, and shuts off.

                              G. Bought HP factory recovery disk and it flashes a white screen then nothing else.

Might this be a worm or trojan?

Whatever your response rating system is, your answer deserves high rating. I am still working with the facts you provided. Thanks.
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-14T18:20:33+00:00
Hi thisisit,

Welcome to Microsoft Answers Forums.

We would like to get more information from you, to help troubleshoot your issue. Please answer the following questions as best you can.
- When was the last time it was working?
- Do you remember making any changes to the computer recently?
First I would like to let you know that recovery partitions are created by computer manufacturer and we are unaware on how that can be accessed to know more about recovery partition contact the computer manufacturer.

I would suggest that you try running Startup repair on the computer and check.

If you have a Windows Vista installation disc, you need to restart (boot) your computer using the installation disc. If you do not restart your computer from the disc, the option to repair your computer will not appear.

If you have a Windows Vista installation disc:

1. Insert the installation disc.

2. Restart your computer.

Click the Start button, click the arrow next to the Lock button, and then click Restart.

3. If prompted, press any key to start Windows from the installation disc.

Note: If your computer is not configured to start from a CD or DVD, check the information that came with your computer. You may need to change your computer's BIOS settings. For more information, see BIOS: frequently asked questions.

4. Choose your language settings, and then click Next.

5. Click Repair your computer.

6. Select the operating system you want to repair, and then click Next.

7. On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repairs.

**If Startup Repair is a preinstalled recovery option on your computer:**1. Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer.

Click the Start button, click the arrow next to the Lock button, and then click Restart.

2. Do one of the following:

• If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.

• If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to repair, and then press and hold F8.

3. On the Advanced Boot Options screen, use the arrow keys to highlight Repair your computer, and then press ENTER. (If Repair your computer is not listed as an option, then your computer does not include Startup Repair as a preinstalled recovery option.)

4. Select a keyboard layout, and then click Next.

5. Select a user name and enter the password, and then click OK.

6. On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem and, if necessary, it might restart your computer as it makes repairs.

http://windows.microsoft.com/en-US/windows-vista/Make-system-repairs-from-the-Windows-Recovery-Environment-from-Windows-Vista-Inside-Out

How to fix Blue Screen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly

http://support.microsoft.com/kb/958233

A Stop error occurs, or the computer stops responding when you try to start Windows Vista or Windows 7

http://support.microsoft.com/kb/925810

What to do if Windows won't start correctly

http://windows.microsoft.com/en-US/windows-vista/What-to-do-if-Windows-wont-start-correctly

Halima S
- Microsoft Support.
Visit our Microsoft Answers Feedback Forum and let us know what you think.
Was this answer helpful?

0 comments No comments