Windows Vista Startup Blue Screen STOP: 0X0000007B

original title: Windows Vista BSOD STOP: 0X0000007B (0X80599BB0, 0XC000034, 0X00000000, Vista keeps on giving me the BSOD on start up.

Hello everyone,

Windows Vista (32bit Home Premium) recently gave me the BSOD error STOP: 0X0000007B (0X80599BB0, 0XC000034, 0X00000000, 0X0000000) after a sudden power loss. I can't even load Vista with out the Blue Screen of Death. Safe mode does not work, with it crashing when getting to crcdisk.sys. Startup repair can't find an errors. System restore doesn't do anything helpful. CHKDSK doesn't seem to find any errors. The last thing I want to do is to reinstall my OS. Before my computer became like this, I did not have any viruses on my computer, and was not installing and driver software. However, I did toggle around with the boot options to allow both processors to boot the computer, but I did not let it do a restart. I suspect something around the boot settings is causing trouble. My computer was working fine the day before, and this incident is terribly infuriating. I would greatly appreciate it if someone could give me a hand.


Question Info

Last updated June 27, 2019 Views 24,385 Applies to:


this means windows can't find the HDD. Check the cables, please.

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.



Be sure to check the BIOS as Chris suggested.


Check this thread for information on using BlueScreenView, MyEventViewer, and other methods to
troubleshoot BlueSceens - top 3 replies.


You probably need a real computer shop (not leeks and peeks at a BestBuy or other BigBox stores)
or your System maker's support.

Try running chkdsk /f /r   from the Command Prompt of your Vista boot disk (see next message for more).

You can also try System Restore from there.

BCCode: 7b     0x0000007b


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, seeBoot Options for Driver Testing and Debugging .

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 theAdvanced Options menu, select theLast 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 runChkdsk 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 propermaster/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.

BCCode: 7b     0x0000007b  <-- read this*1138.html?order=date


If you can gain some access and still have issues this troubleshooter should help.

Look in the Event Viewer to see if anything is reported about those.

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.

Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.


Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen
info that would help. Such as the BCC and the other 4 entries on the lower left. And any other
error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes,
and displays the information about all crashes in one table - Free

Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.

This tells you how to access the System Recovery Options and/or from a Vista DVD

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Vista


Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe)
program generates in Windows Vista cbs.log

The log might give you the answer if there was a corrupted driver. (Does not tell all the
possible driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Vista


Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

How to Install a Device Driver in Vista Device Manager

How To Disable Automatic Driver Installation In Windows Vista - Drivers


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

Troubleshooting Vista Blue Screen, STOP Errors

Understanding and Decoding BSOD (blue screen of death) Messages

Windows - Troubleshooting Blue Screen Errors


In some cases this might be required.

StartUp Repair from Recovery Options or Vista disk

How to do a Startup Repair

This tells you how to access the System Recovery Options and/or from a Vista DVD

Hope this helps.

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.
Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.