BSOD 0x7b on a Win7 32bit

You can't edit CurrentControlSet that way since it does not appear in a static hive when doing an offline edit. You can make the changes in CurrentControlSet001 or 002 depending on which one is active. See here for more details. Only proceed with this method if you are comfortable making the changes and know what you are doing.
 
SleepyDude said:
Hi,

Can I ask how did you disable the Driver Verifier?
Click to expand...

In recovery console type:
verifier

The Driver Verifier screen with come up
Delete existing settings.

There is also a cmd line you can use. I don't remember what It is.

Docfxit
 
{bootmgr} now shows {bootloadersettings} instead of {globalsettings}.
Repeat:
Code: 
bcdedit /set {bootmgr} inherit {globalsettings}
You can also try:
Code: 
bcdedit /set {bootmgr} device partition=\Device\HarddiskVolume[B]?[/B]
You need to put the correct number instead of ?, in this last command (if c: partition is the first partition, it should be 1... If it's the second partition, it should be 2... And so forth).
 
philc43 said:
You can't edit CurrentControlSet that way since it does not appear in a static hive when doing an offline edit. You can make the changes in CurrentControlSet001 or 002 depending on which one is active. See here for more details. Only proceed with this method if you are comfortable making the changes and know what you are doing.
Click to expand...

I found CurrentControlSet001 was active according to the instructions.
It had:
HKEY_LOCAL_MACHINE\System\CurrentControlSet001\Services\Msahci

With Start in the Name column already set to "0" as suggested
It did not have:
HKEY_LOCAL_MACHINE\System\CurrentControlSet001\Services\IastorV
in the registry.
The instructions said to modify one of the following registry subkeys.

So I guess that wasn't the problem.

Thanks,
Docfxit
 
xilolee said:
{bootmgr} now shows {bootloadersettings} instead of {globalsettings}.
Repeat:
Code: 
bcdedit /set {bootmgr} inherit {globalsettings}
You can also try:
Code: 
bcdedit /set {bootmgr} device partition=\Device\HarddiskVolume[B]?[/B]
You need to put the correct number instead of ?, in this last command (if c: partition is the first partition, it should be 1... If it's the second partition, it should be 2... And so forth).
Click to expand...

I have added the above successfully.
I have re-booted. I get a BSOD 0x7b.
I have re-booted into repair console.
Code: 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {fd233d74-93f3-11e7-b991-8148a1c79c42}
                        {fd233d75-93f3-11e7-b991-8148a1c79c42}
timeout                 5

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
inherit                 {bootloadersettings}
bootdebug               No
osdevice                partition=C:
systemroot              \Windows
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {fd233d74-93f3-11e7-b991-8148a1c79c42}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             Windows 7 Ultimate (recovered) 
locale                  en-US
osdevice                partition=D:
systemroot              \Windows

Windows Boot Loader
-------------------
identifier              {fd233d75-93f3-11e7-b991-8148a1c79c42}
device                  partition=\Device\HarddiskVolume2
path                    \WINDOWS\system32\winload.exe
description             Microsoft Windows XP (recovered) 
locale                  en-US
osdevice                partition=\Device\HarddiskVolume2
systemroot              \WINDOWS

Thanks,

Docfxit
 
It shows device partition=c: instead of device partition=\Device\HarddiskVolume1.
It seems you are using only one partition in c:, therefore it should be partition 1 = harddiskvolume1.
Re-try:
Code: 
bcdedit /set {bootmgr} device partition=\Device\HarddiskVolume1

Does the bios have the option Launch CSM or CSM or compatibility support module?
It should be enabled.
(I think it is enabled, otherwise you couldn't boot with your other devices...)
 
Last edited:
xilolee said:
It shows device partition=c: instead of device partition=\Device\HarddiskVolume1.
It seems you are using only one partition in c:, therefore it should be partition 1 = harddiskvolume1.
Re-try:
Code: 
bcdedit /set {bootmgr} device partition=\Device\HarddiskVolume1
Click to expand...

HardDiskVolume1 has 4 partitions. Right now 3 are hidden.
Do you still want me to make the above change?

Thanks,

Docfxit
 
xilolee said:
Does the bios have the option Launch CSM or CSM or compatibility support module?
It should be enabled.
(I think it is enabled, otherwise you couldn't boot with your other devices...)
Click to expand...

The BIOS does have CSM Enabled.

Thanks,

Docfxit
 
Docfxit said:
SleepyDude said:
Hi,

Can I ask how did you disable the Driver Verifier?
Click to expand...

In recovery console type:
verifier

The Driver Verifier screen with come up
Delete existing settings.

There is also a cmd line you can use. I don't remember what It is.

Docfxit
Click to expand...

Maybe I'm wrong but I don't think none of those methods work to stop Driver Verifier from the Recovery Console! that is why is recommended to create a System Restore point before enabling Driver Verifier.

There is this guide Disable Driver Verifier Outside Windows (Vista / 7 / 8 / 10)

If you don't fill comfortable to work on the registry this way let me know and I will try to help doing the changes using FRST - Farbar Recovery Scan Tool Download
 
I think the screenshot of the partitions is most helpful. I am assuming you want to boot from disk 1 using the Windows7_OS partition. [Note: You would really benefit from having more free space on that partition for optimum performance.]

Currently the boot manager is on disk 2 so when you remove that disk the system looks for the boot manager on disk 1, I suspect the boot manager sits on the XP partition so when that is hidden the system does not know what to do. Quite why you get the BSOD I do not know since the system should just report a missing bootmgr, this makes me think something else could also be wrong.

Can you confirm that you have rebuilt the MBR on the Windows7_OS partition? If not I would use the Macrium Reflect (Free) software and this link will show you the steps to perform the repair: Fixing Windows boot problems - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase

You will need to make a Macrium Rescue USB first: Creating rescue media - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase

You should also be able to do this using the Win7 recovery disk and running startup repair but you need to run it at least three times to be effective. This catches most people out and is why I like to use Macrium reflect instead.
 
philc43 said:
I think the screenshot of the partitions is most helpful. I am assuming you want to boot from disk 1 using the Windows7_OS partition. [Note: You would really benefit from having more free space on that partition for optimum performance.]
Click to expand...

Thanks for the info. I'm happy to make that happen after I get it to boot.

philc43 said:
Currently the boot manager is on disk 2 so when you remove that disk the system looks for the boot manager on disk 1, I suspect the boot manager sits on the XP partition so when that is hidden the system does not know what to do. Quite why you get the BSOD I do not know since the system should just report a missing bootmgr, this makes me think something else could also be wrong.
Click to expand...

The boot manager has been all over the place. Before this testing it was on a drive I have unplugged for this testing.

philc43 said:
Can you confirm that you have rebuilt the MBR on the Windows7_OS partition? If not I would use the Macrium Reflect (Free) software and this link will show you the steps to perform the repair: Fixing Windows boot problems - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase

You will need to make a Macrium Rescue USB first: Creating rescue media - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
Click to expand...

I have rebuilt the MBR many times in the past. I'm happy to do it again. In the past I have done it manually with the Win7 recovery disk or with Partition Wizard. Today I ran Macrium Reflect Fix Windows Boot Problems.

philc43 said:
You should also be able to do this using the Win7 recovery disk and running startup repair but you need to run it at least three times to be effective. This catches most people out and is why I like to use Macrium reflect instead.
Click to expand...

After running Macrium Reflect, Fix Windows Boot Problems, I rebooted the machine. It now comes up with a light blue screen with no writing and no cursor. (It's not the dark blue like a BSOD. It's a light blue like the Reflect screen)

I used a rescue USB that I updated today with the latest version of Reflect. I created the rescue USB on my laptop running Win7 32bit. (Not the machine we are working on.)

Any suggestions as to why it's not booting and I'm getting a blue screen?

Thanks,

Docfxit
 
I am wondering if the light blue screen is Windows trying to complete some sort of update. Is there any disk activity? How long have you left it in that state?
 
philc43 said:
I am wondering if the light blue screen is Windows trying to complete some sort of update. Is there any disk activity? How long have you left it in that state?
Click to expand...

There is no disk activity. I left it up quite a while but I didn't time it. I was trying to update Reflect on a USB drive connected to the problem machine so I could create the rescue USB from that machine.
I have now rebooted back to the blue screen and left it running. I'm timing it now.

Thanks,

Docfxit
 
I have been on a remote session with Macrium support. They can't figure out why it would only show a blue screen.
I have tried to bring up the safe mode F8 screen and I only get the same blue screen.
Now I can't see the BSOD 0x7b or the safe mode screen.

Any suggestions?

Thanks,

Docfxit
 
You can try and force the system into recovery mode by turning it on and off three times during the boot process. If this does not work can you boot from the W7 recovery disk and try to initiate a series of at least three startup repairs.

Can you get into the BIOS and ensure that it is seeing the correct harddisk and booting from it?
 
I'm trying to boot into the Win7 recovery CD. It wants to repair the boot files. That will loose all the work XiloLee did to get the BCD configured correctly.
It says it will put a copy of the boot configuration into C:\Boot\BCD.Backup.0002.

I don't want to mess up what XiloLee did.

What should I do now?

Thanks,
Docfxit
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top