Windows Forum
I have a user who downloaded some iomega drivers, restarted and got a blue screen "stop: 0x0000007B (0xED42B84C, 0XC0000034, 0x00000000, 0x00000000) Inaccessible_Boot_Device.
I've tried to repair 2000, but it didn't take. What other options are there for me w/ regard to trying to salvage this users data.
This indicates that Windows has lost access to the system partition during startup.
Cause:
This error often results from 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 result from 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), which requires the user to do a custom installation.
Resolving the Problem:
This error always occurs while the system is starting. This will often happen before the debugger connection is established,making debugging difficult or impossible.
Resolving a failed boot device problem: If this happens on an x86 system, the boot.ini file must be edited. See The boot.ini File for details.
http://www.osr.com/DDK/ddtools/bootini_04xf.htm
(REMOVE SPACES from the pasted URL.)
On an IA-64 system you must edit the OsLoadOptions in the non-volatile RAM.
(continued...)
Resolving an incompatible disk hardware problem: If Setup autodetected the controller, you might need to skip detection and use a specific manufacturer's diskette 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 disks or controllers, to see if the error is resolved. If the offendingpiece of hardware was a hard disk, the disk firmware version might be incompatible with your version of Windows. Contact the manufacturer for updates. If the removal of another piece of hardware resolved the error, IRQ or I/O port conflicts likely exist. Reconfigure the new device according to the manufacturer's instructions.
Confirm that all hard disks, hard disk controllers, and SCSI adapters are listed on the Microsoft Windows Hardware Compatibility List (HCL).
If a driver was recentlyadded, restart your computer, and press F8 at the character-based menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.
In addition, check your computer for viruses 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 be a result of hard disk corruption. Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r.
(continued...)
If you are unable to boot the system to the last known good configuration, you should try to boot off the Windows CD-ROM. Then you can run Chkdsk from the Repair Console.
Warning: If your system partition is formatted with the FAT file system, the long filenames used by all NT-based operating systems can be damaged if Scandisk or another MS-DOS?–based hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from anMS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the version of Chkdsk that matches your Windows version.
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/slave/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 pinpoint the device or driver that is causing the error.
----------
The preceding came from:
http://www.osr.com/DDK/ddtools/bccodes_2gx3.htm
REMOVE SPACES from the pasted URL.
by qpeabody
The answer I needed is found here.
Q306949 - STOP 0x0000007B Inaccessible_Boot_Device Error Message After You Install Iomega Tools.htm
Thanks
by techfish
by qpeabody
The answer I needed is found here.
Q306949 - STOP 0x0000007B Inaccessible_Boot_Device Error Message After You Install Iomega Tools.htm
Thanks
by opatzg9
There's a good chance your problem is with the load portion of the iomega drive. read the guesthlp.txt on the iomega diskette on which aspi driver should be loaded for your system. Then edit the guest.ini file and remove all aspi drivers which your system does not need. This is a scsi disk driver which is probably interfering with your current drive access. Otherwise try merely uninstalling the software for the zip/jazz drive in the add/remove programs. If that can't correct it all you cantry scanning the registry for aspi or zip/jazz and remove all entries there. look at the load programs in the win or system .ini files and remove the guest.exe or any call for the zip/jazz drive there. Then see how it's working.
Good luck
by qpeabody
The answer I need is found here.
Q306949 - STOP 0x0000007B Inaccessible_Boot_Device Error Message After You Install Iomega Tools.htm
by mrjay67
I had the same problems occur for a company I worked for in the past. The problem is closest to answer 3. But, if I understand, and its like the problem we encountered you cant boot into Windows to remove the drivers. Boot to recovery console either by CD or if you have it installed. I forget the exact process as it has ben awhile but you should be able to turn of the aspi svc related to Iomega and re-enable the original ones for your PC. For some reason on occasion Iomega drives have a tendency to activate their aspi drivers/svcs and it doesnt allow NT PCs to boot properly. I can almost assure this is the general process you need as it sounds like the same exact issue. I dont rem the exact commands but you can type HELP at the console prompt to get the correct commands for this.
Hope this helps
Jason
by mrjay67
by mrjay67
i found the resolution i was refering to on Microsofts site, article# Q306949.
RESOLUTION
To resolve this behavior, complete the following steps:
Start your computer by using the Windows 2000 CD.
At the Welcome to Setup screen, press R for repair. At the next prompt, press C to start the Windows 2000 Recovery Console.
Enter the number of the Windows 2000 installation that you want to repair, and then type the Administrator password when you are prompted.
To disable the Iomega drivers, type the following command at the Recovery Console command prompt, and then press ENTER:
disable imgatapi
To see whether the Atapi service is still set to Boot, type the following command, and then press ENTER:
listsvc
If the Atapi service is setto Boot, type exit, and then press ENTER, to restart the computer.
If the Atapi service is set to Disabled, type the following command, and then press ENTER:
enable atapi service_boot_start
Then type exit, and then press ENTER, to restart thecomputer.
Use the Add/Remove Programs utility to remove the Iomega Tools program.
This should resolve your boot problem.
by qpeabody
Thanks, but I found this an on MS website;
Q306949 - STOP 0x0000007B Inaccessible_Boot_Device Error Message After You Install Iomega Tools.htm
Thanks again
by qpeabody
This discussion is closed to new replies.
Sort by Trending