0x7b - 0xC34 - Win7 Pro 32bit

Arc · 16 Mar 2013

Boot to System Recovery Options . Try Safe Mode with Command Prompt. In the command prompt .... enter the command ....

start msconfig

It will open the system configuration window, with the "general" tab selected.

Click the "startup" tab. Click "Disable all" > Apply > OK.
Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK

Then try to boot again normally. Is it failing still?

If so, boot to System Recovery Options once again. Try Enable Boot Logging. It will create a file named ntbtlog.txt. Collect it and upload it. If you cannot do it within windows, Boot with a live Linux disc and collect it in a USB stick, use the usb stick in another computer and upload it. It is necessary.

BTW, if you can , post the data following the Blue Screen of Death (BSOD) Posting Instructions?

Cosmitz · 16 Mar 2013

No Safemode gets past classpnp.

I can access the registry via the hive to HKLM\System\ControlSet2 (my default in Select and the one it's trying to boot)\services and disable whatever services i need disabling from there. And no, no other control set boots.

As i've mentioned, no minidump, no ntbtlog and no memory.dmp gets logged. CrashDumpEnabled is set for a complete dump also. I know ntbtlog should be in C:\Windows\ and no it's not there.

As for the BSOD posting instructions as mentioned, the system does not boot, i cannot use said app, and as far as i've seen, said app cannot retrieve them remotely even IF they would create. If i had a minidump to analyze via Bluescreenviewer, it would have been a piece of cake to solve.

Before posting this thread, i was trying to get the USB drivers to boot ahead of everything else, and have the minidump redirected to a USB stick if it can't write on the hard drives, seeing how they're both on SATA and share drivers.

Arc · 16 Mar 2013

In such a situation it is better you start afresh.

First, move any data in the SSD that is important: Copy & Paste - in Windows Recovery Console

Then perform a Clean Reinstall - Factory OEM Windows 7

Cosmitz · 16 Mar 2013

Not the help i was looking for. I could have backedup and reinstalled the system in under 30 minutes of the BSOD appearing, but i intend on making this install boot. Just thought i'd get more knowledgeable info on these forums.

Arc · 16 Mar 2013

I requested gregrocker to look at your issue. He is offline now, so you have to wait.

Cosmitz · 16 Mar 2013

Time i have, thanks for the assistance.

LE: Tried to get all the usb-related drivers in category group, WdfLoadGroup in my case, to load sooner, with all having set Start 0, but i'm missing something i guess, since the minidumps still aren't created, and i went through C: to F: setting the with two extra usb thumbdrives attached, trying to make it write on them in case it was bugging out writing on the system drive or the storage. I guess i also need to boot the file manager or something in that case, but i'm at a loss. Restored the original hive in any case, waiting on further info.

gregrocker · 16 Mar 2013

All repairs should be done with all other HD's and peripherals unplugged. If they weren't then do them over.

Your System boot files are corrupt and non-functioning as signified by no Boot flag on any partition in PW listings.

Try creating a new boot partition by Resizing Win7 by 200mb from the left, creating a New NTFS Primary partition there, marking it Active, then running 3 separate Startup Repairs which are the number required to check all parameters while also attempting to boot OS:
Partition Wizard Resize Partition - Video Help.
Partition Wizard Create Partition Video Help
How to Set Active/Inactive partition -Partition Wizard Video Help.

If this fails run Partition Wizard Partition surface test

Cosmitz · 16 Mar 2013

Hello and good morning,

I did as you asked, disconnected everything minus the HDD in question. PW, resized 200mb from the left, new NTFS, Primary, Active. NTLDR missing. Loaded up Win7 disk, repair-try to boot, ntldr missing, repair, ntldr missing, repair, Starting Windows. 0x0000007B. Windows Startup repair this time, StartupRepairOffline/Autofailover/BadPatch. Second startup repair, Root cause, A patch is preventing the system from starting. Repair action, System files integrity check and repair. Third startup repair, repairing disk errors. Restart your computer to complete the repairs.

Starting windows... STOP:0x0000007B.

Did the surface test earlier today, but redid it for completeness' sake and it came out green across the board.

gregrocker · 16 Mar 2013

Try Partition Wizard Rebuild MBR - Video Help followed by 3 more Startup Repairs.

Then try the bootrec and bootsect commands as demonstrated in Troubleshooting Windows 7 Failure to Start, followed by Startup Repairs again.

You've now done everything possible to repair the boot. It may in fact be corruption in the OS (bad patch) blocking boot. Have you tried SFC /SCANNOW Run in Command Prompt at Boot?

Unfortunately a bad patch or Update is best remedied by System Restore. Do you think your Restore Points were intact before this? I'd try it again from DVD Recovery Options.

Cosmitz · 16 Mar 2013

Repaired MBR via PW. 7B. Bootrec'd/bootsect'd, ran sfc /scannow /offbootdir /offwindir. Also, there are no restore points.

Let me reiterate what's happening:

Nothing will boot into windows, 7B at the windows logo. Safe mode loads drivers up to CLASSPNP.sys and then dies, see the first post attachements please. No minidumps, ntbtlogs or such are getting created on any drive that i try to path them to via CrashControl Controlset registry key. Besides my suspicion of Intel drivers, i also listed a full 0 and 1 start services/drivers with the ServiceGroup startups listed in my original post. I tried getting a minidump flushed to a pendrive via booting all usb drivers before controllers but it didn't stick.

It is seeing and reading the drive and the boot, but it's 7B'ing once it loads drivers.