Member Avatar for J-T-S

i recently put this in tips and tweaks by accident and i apologize

i have a custom built computer that i decided to upgrade not to long ago. I bought new ram, cpu, and a mobo to go along with an ide hdd and nx8600gts video card. i use windows xp

mobo is lanPartyDK 790FX series

cpu is an amd athlon 64 x2 dual-core processor

ram is 2 gigs of g.skill ddr2 800

i get a blue screen which used to just flash for about 1/4 of a sec but a was able to stop that by disabling "automatic reboot after system failure" The error was about scanning for viruses which i cant do since it will not load windows. the tech info is "stop: 0x0000007B (0xBACC3528,0xC0000034, 0x00000000, 0x00000000)"

ive been troubleshooting for a few days but nothing has worked so far, my guess is that the hardware is either uncompatable or i need to reformat.

  • 3 Contributors
  • 2 Replies
  • 2K Views
  • 6 Years Discussion Span
  • Latest Post Latest Post by jollyhappytj

Dani AI

Generated

That stop code is INACCESSIBLE_BOOT_DEVICE. After a motherboard swap, XP is often still trying to use the old storage controller driver and can no longer mount the system volume. Your board generation typically exposes one onboard IDE channel alongside SATA. Confirm the drive is on the correct cable (80‑wire), jumpers are set (Master if it is alone on the cable), and the HDD is first in the BIOS hard drive boot order. The symptom still fits a storage driver/boot path issue more than a virus in this scenario. Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE. The DFI 790FX manual shows a single IDE connector for up to two UDMA/133 devices, which is easy to mis‑jumper after a rebuild. DFI 790FX‑M2R User Manual, IDE connector.

Quick fixes that often recover XP after a controller or board change:

  • Boot the XP CD, enter Recovery Console, then run:
chkdsk c: /r
bootcfg /rebuild
fixboot
fixmbr

Reboot after each if needed. Note: fixmbr overwrites non‑standard boot loaders. These commands are standard XP Recovery Console tools to repair the boot sector/MBR and rebuild boot.ini. Recovery Console commands.

If the disk was installed under a different chipset, enable XP’s generic IDE drivers (the old MergeIDE/fix_hdc method) so it can load a compatible miniport at boot; Microsoft documented this for XP when moving a system disk to new hardware. . If that is not possible, do an in‑place repair install of XP and provide the board’s mass‑storage driver during Setup via F6 (or slipstream it into media); XP only loads these OEM drivers from a floppy during text‑mode Setup. In‑place repair overview and .

+1 to for calling out driver start‑type issues; the steps above put that into practice. The 0xD1 link from is for a different bugcheck, so you can ignore it for this thread.

Recommended Answers

All 2 Replies

Member Avatar for Doctor Inferno

You may receive a "Stop 0x0000007B" error message if your computer is infected with a boot-sector virus. If the problem is intermittent and you can start Windows, check your computer for viruses. If you find a virus, also check any floppy disks for viruses before you use them again.


You may also receive a "Stop 0x0000007B" error message in the following scenarios:
• A device driver that the computer boot controller needs is not configured to start during the startup process.
• A device driver that the computer boot controller needs is corrupted.
• Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.

Check the following site for troubleshooting:

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

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.