Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD 0x0000007B at Windows splash screen


  • Please log in to reply

#1
tomdrayson

tomdrayson

    Member

  • Member
  • PipPipPip
  • 198 posts
Hi, this morning I turned on my computer, and about 1 second after the splash screen appeared, I got a blue screen with the code 0x0000007B - this happens every time, including last know good config and safe mode. I had not installed any new hardware or software since I last booted and everything was fine, with no problems whatsoever.
There was no error message with the code, but I believe it signifies the "INACCESSIBLE_BOOT_DEVICE" error.
It is a Seagate Barracuda 250GB SATA HDD connected as SATA1 master. There are 2 partitions on this drive, one with Windows Media Centre Edition, and one with XP Pro. I can boot to the XP Pro partition, and I have run chkdsk on the Media Centre partition, with no errors, and I can access all the files on the partition as well.

The boot.ini is correct, but I have tried bootcfg /rebuild and fixboot from the recovery console anyway, and I still cannot boot. I also have a Maxtor SATA drive connected to the "SATA3" port on my motherboard, which appears as SATA3 Slave in the BIOS/CMOS (can't remember which menu). I didn't think SATA could be master/slave but that's what the BIOS says. The other options in the BIOS are SATA2 Master, and SATA4 slave - which should my second HDD connect to - master or slave?

Anyway the other drive is not the issue, because I still get the error when it is completely disconnected. I cannot boot to my Media Centre partition with the drive connected to any of the 4 SATA ports, but I CAN boot from the XP partition.
I am baffled as to why this has suddenly occurred!
Any ideas?
Thanks

Edited by tomdrayson, 29 April 2006 - 12:15 PM.

  • 0

Advertisements


#2
tomdrayson

tomdrayson

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 198 posts
I have noticed that when I am in the XP Pro partition (which I will be, until I can get back into Media Centre), I can hear 14 short, quiet beeps in succession, over about 4 seconds, every minute or so - coming from the system somewhere, I can't pinpoint exactly where. Anyone know what this means?

Edited by tomdrayson, 29 April 2006 - 12:16 PM.

  • 0

#3
tomdrayson

tomdrayson

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 198 posts
The full error code is:
0x0000007B (0xBACE3524, 0xC0000034, 0x00000000, 0x00000000)
  • 0

#4
SRX660

SRX660

    motto - Just get-er-done

  • Technician
  • 4,345 posts
0x0000007B: INACCESSIBLE_BOOT_DEVICE

Windows lost access to the system partition or boot volume during the startup process. Typical causes: Installing incorrect device drivers when installing or upgrading storage adapter hardware, or a virus.

http://support.micro...=122926&sd=RMVP

SRX660
  • 0

#5
tomdrayson

tomdrayson

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 198 posts
Hi, thanks for your reply - I have actually looked into this problem quite a lot, I always try to do my own research before asking other people to do it for me! Naturally, the first place I looked was the Microsoft knowledgebase...
I do not have any viruses, including boot viruses (according to Norton Antivirus). Other possible causes listed include IRQ confilcts, corrupt file system or registry, or damaged hardware. But I can boot fine into another partition on the same disk, and access all my files on the problematic partition. Chkdsk found no problems. I am confident that there is no damage/corruption to my disk, which leads me to believe there is another issue causing this error. Any ideas?
Thanks
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP