Win7 BSOD, SFCFIX error subsystem needed does not exist

AlanMintaka · Sep 1, 2019

Hello,
This is my first time here so please bear with me if I don't include relevant info the first time around.

I have a Dell XPS 8700 with Windows 7 Home Premium. I get a BSOD when I try boot - 0x0000007B.
I tried Safe Mode - Command Prompt. The last 3 drivers I could see loading before the BSOD are
FVEVOL.SYS
DISK.SYS
CLASSPNP.SYS
if that means anything.

Next I tried booting with a Win7 Repair disc. The repair returned one of those "unable to repair this system" messages.
So I clicked on the Command Prompt after that and tried bootrec/fixmbr, bootrec/fixboot, and bootrec /rebuildBCD.
They all returned "completed successfully" but I still got the BSOD.

Back in the repair command prompt, I tried sfc /scannow. This returned a message saying that "repairs were pending and will be completed after restart".
Restarting without the repair disc just resulted in another BSOD. Restarting with the repair disk and running SFC again just repeated the same thing: repairs pending after restart.

In another forum I found a suggestion to try
sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=c:\Windows
In my case D: has the boot directory, but so does c: (?). Anyway I tried this combo of drives for lack of knowing what else to do.

I tried to run SFCFIX from the repair command prompt. This returned the message "subsystem needed to support this image type is not present."
I have no idea what this means.

Other miscellaneous things:
chkdsk /F and chkdsk /R both reported no errors on the drive.

DISM /Online /Cleanup-Image /RestoreHealth returned "does not support servicing Windows PE"
DISM /image:c:\ /cleanup-image /revertpendingactions returned "operations completed. Any revert of pending actions will be attempted after restart".
Of course when I restarted without the repair disk I got a BSOD again. When I restarted with a repair disk and ran DISM with the same options, I got the same "pending message", etc etc

That's pretty much the essence of what's been going on. Any ideas on what I could try next? Do I need to post any more info here?

Thanks for your time and patience,
Alan Mintaka

AlanMintaka · Sep 1, 2019

UPDATE: too late to edit the last message. I did get some results with

sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=c:\Windows
This returned "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in
c:\windows\logs\cbs\cbs.log"
This is a huge file full of errors. Most of them mention "reported by windowsupdateagent.info"
At the moment I'm trying to figure out how to get that file off the hard drive drive and into one of these forum postings. Does the INFO filename suggest anything?

Thanks,
Alan Mintaka

Sysnative Windows Update · Sep 1, 2019

Hello and welcome!

Since you have an issue with SFC, I suspect that one of your critical system files got corrupted.

Can you please attach the CBS.log or provide a link to it if it's too large to be attached directly so I could objectively say whether this is fixable or not.

x BlueRobot · Sep 2, 2019

Stop 0x7B is related to an inaccessible bootable drive, so it is likely that both issues are related.

AlanMintaka · Sep 2, 2019

softwaremaniac said:
Hello and welcome!
Since you have an issue with SFC, I suspect that one of your critical system files got corrupted.
Can you please attach the CBS.log or provide a link to it if it's too large to be attached directly so I could objectively say whether this is fixable or not.

Hi softwaremaniac,

Thnx for the fast response. My problem with attaching the file is that I can't figure out a way to get it off the non-booting drive. I may have to use
one of those command-line CD burning programs. Or, I may move the drive into a machine that boots and try to read it from there. Don't know yet.
I have a replacement drive on order already and may just wind up expanding the PC to use the current boot drive as an add-on.

Whatever I manage to do, I'll try to get a copy of that file somehow. At least I've been able to use the repair command prompt to make a backup of it.

I'll keep you posted on whatever I manage to do.

In the meantime, I'm creating a boot disk using UBCD (Ultimate Boot CD). I don't know what that will do for me, but if you have any suggestions about
any of the tools on the CD, please let me know. And thanks again for the response.

Have a good one,
Alan Mintaka

AlanMintaka · Sep 2, 2019

x BlueRobot said:
Stop 0x7B is related to an inaccessible bootable drive, so it is likely that both issues are related.

Hi x BlueRobot,

Thanks for the info about 0x7B. Please see my response to softwaremaniac above for additional details of what I've been doing.

Right now it looks like the replacement drive is the only viable plan, but that could change with UBCD.

Take care,
Alan Mintaka

Sysnative Windows Update · Sep 2, 2019

Hi!

Thanks for the response. I would also first and foremost test the HDD:

Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test

AlanMintaka · Sep 2, 2019

softwaremaniac said:
Hi!
Thanks for the response. I would also first and foremost test the HDD:
Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test

H softwaremaniac,

Looks like GSmartControl is a windows program, so I'll still need to get that drive into a machine that boots. Will let you know what I wind up doing.

Sysnative Windows Update · Sep 2, 2019

Hi!

The link contains the download for a bootable utility Seatools for DOS as well which doesn't require Windows.

AlanMintaka · Sep 2, 2019

softwaremaniac said:
Hi!
The link contains the download for a bootable utility Seatools for DOS as well which doesn't require Windows.

I see that now. I've already tried the Seatools bootable but forgot to include that info in my previous postings.

I got the boot manager OK, but the first boot option just didn't work. A few linux messages appeared, then the screen cleared and nothing else happened.

The second boot option was for the SeaChest utilities. This one booted and I've tried some of the tools. I'm not much of a linux user so I don't
know how to get much done with those. I did manage to run the shortDST diagnostics tool. Once I figured out how to actually get the results
(the --poll option) it reported no errors.

That's as far as I've gotten with Seatools SeaChest so far.

AlanMintaka · Sep 2, 2019

softwaremaniac said:
Can you please attach the CBS.log or provide a link to it if it's too large to be attached directly so I could objectively say whether this is fixable or not.

Hi softwaremaniac,

I have the broken HDD in another machine. Here's a zip of the CBS log file. I added a date stamp to the file name. Let me know if you have any issues with it.

I just ran the GSmartControl short self-test to see what would happen. That reported no errors. The extended self-test is now running, will report in about 3 hrs.

The good news is that all of my own files on the broken HDD are intact.

Alan Mintaka

Sysnative Windows Update · Sep 2, 2019

Hi!

This log does not contain anything useful unfortunately

Do you happen to have access to the whole CBS.log?

AlanMintaka · Sep 2, 2019

softwaremaniac said:
Hi!
This log does not contain anything useful unfortunately Do you happen to have access to the whole CBS.log?

By "whole CBS log" do you mean the entire Windows\logs\CBS directory? If so, I'll have to use a link because it includes a CAB file that's too large to attach here.

OK, try this:

cbs.zip

Let me know if it bombs. ETA on GSmartControl extended self-test is now 2h 40m.

AlanMintaka · Sep 2, 2019

softwaremaniac said:
...I would also first and foremost test the HDD:
Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test

Hi softwaremaniac,

The extended self-test just reported "no errors". FWIW, here's a copy of the self-test log:

Test # Type Status % Completed Lifetime hours LBA of the first error
1 Extended offline Completed without error 100% 32578 -

I've attached a copy of the smartctl data, if that makes any difference.

Meanwhile, on the Attributes tab, non of the entries show red or pink. I've attached a screen shot of that too.

I'm at the point of considering this issue closed. Nothing worked, so I'm going to just use it as an extra HDD now and re-install Windows 7 on a new drive.

Thanks much for all the work and time you've put into this. I wish I had been able to produce some useful info at this end, but it just didn't work out that way.

Search

Search

Win7 BSOD, SFCFIX error subsystem needed does not exist

AlanMintaka

Member

AlanMintaka

Member

Sysnative Windows Update

Inactive

x BlueRobot

Administrator

AlanMintaka

Member

AlanMintaka

Member

Sysnative Windows Update

Inactive

AlanMintaka

Member

Sysnative Windows Update

Inactive

AlanMintaka

Member

AlanMintaka

Member

Attachments

Sysnative Windows Update

Inactive

AlanMintaka

Member

AlanMintaka

Member

Attachments