0x0000007B Problem

Hi, all together,
I am sorry, but English is not my mother's language, but I will give it a try:

A friend of mine got the same problem you described here on the Thread,
on a computer with XP at the first partition (C) and Win7 at the second
partition on the same disk, after several month of using both without any
complication. Starting 24th of February he got an MS update at Win7, and
at the next morning when starting up the system he got the message:
0x0000007B (0xfffff880009a98e8, 0xffffffffc0000034,......0,0)

I wanted to help him, and as I have experiences from my work (40 years
IT, programming, networks, systems ...) and have already had such problems,
most of them solved.

But in this case, we tried all what we have known, all we have found at several
forums and several pages from other users, nothing works, as well not the
posting from social.answers.microsoft.com, where the exact error message
came after a windows update.

I tried:
- Checking both installation for Virus, but none found
- Windows repair, with and without Windows 7 installation CD
- Manually fixing MBR, boot records, boot sectors (on both systems)
- Running sfc /scannow at the Windows 7 partition from PE disk
- Booting directly from the second partition
- Checking boot files (bootmgr.exe, winload.exe, winresume.exe),
all of them are present in Windows\System32 and Windows\System32\Boot
and same size and same version / Date
- Checking IDE and ATA drivers in the registry, as well offline at the
Win7 registry, both in HKLM\SYSTEM\ControlSet001\Services as well as
HKLM\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase
- Checking the Drivers are correct in D:\Windows\System32\Drivers
(atapi.sys, IastorV.sys, pciide.sys, Intelide.sys), but all of them are
from the same date and version
- Changed from SATA to IDE and back, Windows XP is running correct on
both settings, Windows 7 on both not
- Hardware is OK, because from XP we can read und write the partition D:
without any problems, chkdsk shows no errors
- Partitioning seems to be OK, because GPartED shows no problems

Booting in safe mode brings the same blue screen, booting with protocol
ntbtlog.txt does not write any file to any disk. Selecting repair, as well
starting three or more times, says first "repairing" but after the third time
it says, is not repairable.

Did you solve such problem? And if, what did you and how did you it???
May be someone is able to help us, otherwise we have to setup the
Windows 7 new, and reconfiguring all settings and reinstalling all software
and data.

If you need the exact hardware definitions, I have to get it from the
system, the disk is a SAMSUNG HD1035J, and the OS is Windows 7 Home
x64. And please note, that is was working several month before coming up
with this blue screen, as he did not change any hardware or settings, he
just remembers this windows update.

BTW: There where about 30.000 files stored from sfc /scannow at
D:\Windows\winsxs\Temp\PendingRenames and after deleting them
(little complicated, but done) they (not all but many) came back again
after using the windows repair.

Kind regards,
Walter.

Hi Capt.Jack Sparrow,

it is not possible for me to do the BSOD posting instructions, because
I can't start the Windows 7 at all, not in save mode nor in any other way.
So I can't run the "BSOD Dump & System File Collection App", and also not
the System Health Report.

I just can start the XP and can go to the "D:" drive and can send you any
file you want from that, but not a ntbtlog.txt file, because it will not be
written at startup, also when I try it.

Sorry.

More details, I already wrote in my first statement:
- Windows 7 is x64
- Installed at the second partition of the disk, first partition is XP
- Full retail version (original CD)
- Just installed some month ago, never reinstalled, works fine until the BSOD arrived
- System is just 1 year old
- Disk is a SAMSUNG HD1035J

Hi again,

after searching for more informations, as well for the problem "PendingRenames"
I found the following:

Windows 7 Ultimate SP1 installation fails with error code c0000034

and it seems that this sounds like my friend was telling me about an Windows
Update and the BSOD after reboot next day!!! And it's the same date he got
this problem 24th of February!!!

I can imagine, that it comes from this Windows 7 Update SP1 x64, because
there were about 30.000 files after several repair trials at the path
D:\Windows\winsxs\Temp\PendingRenames. After deleting them and further
repair trials there again many files in this path.

May be this can help, I will check files on the friends computer, and possibly
do it as described. What do you think about this whole thing???

Hi,
it's not the same thing. The registry entry isn't there, and as well not
the xml file, just many files under PendingRenames.

We will reinstall Win7 if there is no solution to our problem.

Kind regards,
Walter.

Hi to all, as well to Jack Sparrow,

I hoped, someone at this forum could help us, but it seems that there are
only "fixed ways to follow", otherwise one cannot get any help, just if there
is a solution, but one can get it only, if he follows "your way"!!!

As I wrote, I can not do what you mentioned me, because the system does
not anything, it just gives the blue screen. Is there no possibility, you can
help someone, if he is not able to do your download and start the application?
It's hard for me to believe that, but I found another thread in your forum,
where another user had the exactly same problem as we had, and he also did
not get any attention from your side, because he could not do what you
mentioned. And so he did a reinstall, same as I did after waiting 2 weeks for
any answer.

Best regards for your future to you all.
Walter.

Dear mgorman87,

there are no files at the minidump location, as well as it writes no
ntbtlog.txt when I try to activate that. 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, or earlier in BOOTMGR when loading
NTDETECT???

All things to do I have already tried, but nothing wants working.

Thank you very much.
Walter.