running Windows NT4 installation on a Dell inspiron 1501 2007 laptop, but BSOD 0x0000007B INACCESSIBLE_BOOT_DEVICE crashes, how can I fix this?
I don't have one, but I managed to get to stage 1 and stage 2 of the installation, but I couldn't get to the desktop.
Yes, just attempting to provide verbiage closer to what Dell used in those days. I've been through quite a few 98SE installs on Dell desktops from that era. Which reminds me, @Rinas228, you should try Safe Mode and see if that works too.
Code: Microsoft Windows 2000 / NT 4.0 error message "0x7B: INACCESSIBLE_BOOT_DEVICE" - Servers Troubleshooting Problem Microsoft Windows 2000 / NT 4.0 error message "0x7B: INACCESSIBLE_BOOT_DEVICE" for Servers. Resolving The Problem Symptom 0x7B: INACCESSIBLE_BOOT_DEVICE This error means the system was unable to access the boot device (hard disk drive). Possible causes If you have just installed the Microsoft Windows NT Service Pack, it may have overwritten the Adaptec SCSI driver file (AIC78xx.sys) with a version that is incompatible with the Adaptec 7895 SCSI controller. An incorrect (or old) SCSI or ServeRAID driver was installed during the Windows NT or 2000 installation. You have attempted to install Windows NT on an IDE drive that is larger than 504MB and uses more than 1,024 cylinders (see below). A virus may have infected the master boot record (MBR). The device you are trying to boot from may not be in the F1 bootup sequence. The device you are trying to boot from may not be getting power, or spinning up. The driver for the boot device may have failed to initialize the device that the system is attempting to boot from during initialization of the I/O system. The file system may have failed its initialization. - In this case, parameter p1 is the address of a Unicode string data structure that is the ARC name of the device from which the boot was being attempted (see parameters below). The file system simply may not have recognized the data on the boot device as being a file system structure. - In this case, parameter p1 is the address of the device object that could not be mounted (see parameters below). Actions Ensure you are using the correct and latest version of the SCSI/RAID device driver. If using a ServeRAID adapter, make sure the driver and firmware levels are the same. Ensure all settings are correct in the SCSISelect Utilities (Ctrl+A at bootup) or ServeRAID Manager. Scan all hard disk drives for viruses. - If the Master Boot Record is infected, Windows NT or 2000 may not see the hard disk drive properly (even with NTFS). Ensure all hard disk drives are getting power, and all cables are properly connected. Check the SCSI chain to ensure proper termination; use active rather than passive termination. Ensure the boot hard disk drive SCSI ID is set correctly (e.g. to SCSI ID = 0). Reinstall the operating system with the correct SCSI/RAID device drivers. If installing NT/2000, make sure to press F6 on the “Setup is now inspecting your computer’s hardware…” screen to specify an IBM driver (ServeRAID). This error can also be caused by the installation of a new SCSI adapter or RAID controller, or by repartitioning the disk with the system partition. If this is the case, on x86 systems, the BOOT.INI file must be edited; on ARC systems, Setup must be run. For information on changing BOOT.INI, see the Windows NT/2000 "Administrator's Guide". If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows NT. If you are installing Windows NT for the first time, check the Windows NT system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows NT. If Windows NT is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.