0x0000007B Problem

All four (4) partitions are at the same disk, at the first partition WinXP,
at the second now a new installed Win7, running fine, but we have setup
this newly, and still have to install many programs, at the third partition the
defective Win7, which was originally at the second partition, but we copied this
to the third, to have the possibility to install Win7 new at the second.
At the fourth partiton we have a data partition, which was the third before,
but by inserting a new partition it became the fourth.

The defective Win7 was installed as described, and was working several
month before it crashed at a new boot after a shutdown with updates.
The new Win7 is also installed the correct way, and is working fine until
today.

We have tried also several tips from your forum as well as from social.
technet.microsoft.com, also www.unawave.de/windows-7 and many
other sources like COM Magazin, de.wikipedia.org and so on.

OK, we still have the partition to test on, and find what the problem really was. Just
for another break like this, and maybe helpful for other users. We will wait.
Thank you very much for your help, and kind regards.
Walter.

Booting in safe mode brings the same blue screen
...
It seems, that it break already in the very first state of the startup, may be NTDETECT.COM or
NTOSKRNL.EXE and/or HAL.DLL

1. Check the memory settings in the bios.

Run 10 passes of Memtest86+ - Advanced Memory Diagnostic Tool



2. Diagnose your hard drive:

HD Diagnostic

Dear Cybercore,

Thank you for your posting:

1. MemTest86 already done at the first time, does not show any error

2. HD diagnostic also checked with several tools, all are ok.

Memory settings in BIOS where not changed, SATA/IDE not changed, new installed Win7
on same partiton / same disk is working fine, copied defective partiton on different disk
partition space stays the same (problem is wandering with the copy, so it seems to be
in the content of the partition, not an external problem).

wrb27243 said:

Dear Cybercore,

Thank you for your posting:

1. MemTest86 already done at the first time, does not show any error

2. HD diagnostic also checked with several tools, all are ok.

Memory settings in BIOS where not changed, SATA/IDE not changed, new installed Win7
on same partiton / same disk is working fine, copied defective partiton on different disk
partition space stays the same (problem is wandering with the copy, so it seems to be
in the content of the partition, not an external problem).

Dear wrb27243, could you clarify:

1. How many HDD partitions do you have?
2. What kind of data/OS is stored on each of your HDD partitions?
3. Which OS boots up and works without issues in normal mode?
4. Which OS does not work? What kind of ill behavior do you observe when booting normally? In safe mode?


If your blue screens are all 0x7B: INACCESSIBLE_BOOT_DEVICE - that's the problem. Figure out why it's not accessible -- protected? broken?

All four (4) partitions are at the same disk, at the first partition WinXP,
at the second now a new installed Windows 7, running fine, but we have setup
this newly, and still have to install many programs, at the third partition the
defective Windows 7, which was originally at the second partition, but we copied this
to the third, to have the possibility to install Windows 7 new at the second.
At the fourth partiton we have a data partition, which was the third before,
but by inserting a new partition it became the fourth.

The defective Windows 7 was installed as described, and was working several
month before it crashed at a new boot after a shutdown with updates.
The new Windows 7 is also installed the correct way, and is working fine until
today.

Partition 1: XP Pro - working
Partition 2: Win7 x64 (new setup) - working
Partition 3: Win7 x64 (old parttition 2) - blue screen - in all modes
Partition 4: Data

Chkdsk Partition 3. If you haven't.

You're saying HDD SMART is fine, and if chkdsk finds no errors either, then it could be something with the OS on Partition 3. I would format it and reinstall the OS.

Giving up in this thread. We have installed new, and we have no idea what
the problem was.