BSOD 0x7b on a Win7 32bit

If a backup copy is made XiloLee will be able to get it back. I suspect Macrium had already changed the boot configuration anyway. If you want to wait for XiloLee before trying anything more that is OK.
 
philc43 said:
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?
Click to expand...

I tried to turn it on and off three times during the boot process. That didn't fix it.
The BIOS is showing the correct hard drive.

I guess I have no choice but to boot into the Win7 recovery disk. I just feel bad because I know it's going to destroy the updates that XiloLee did.

Docfxit
 
Yes. I have it so it doesn't come up with the blue screen. It boots up to the BSOD 0x7b.
I need to fix the Boot Manager so it's back where it was.

If you have any other ideas to fix the 0x7b I can perform them while I am fixing the boot parameters.

Thanks,

Docfxit
 
I have a few more questions on your system. In an earlier post you said the problem started back in Feb 2017 so I have gone back to that mini-dump. I don't know if the system has changed since then but back then you had 8GB of memory using two different modules. Is it still the same? You are currently trying to use Win7 32bit which will not be able to see all that memory anyway. Also, using two different memory sticks from different manufacturers can give rise to BSOD events. I would take one of them out as part of the troubleshooting tests.

The Feb 2017 mini-dump showed you were on BIOS_VERSION: 9SKT87AUS BIOS_DATE: 01/09/2015. The most up to date BIOS is 9SKT99A dated 2017/07/14 - this looks more recent than the one you mentioned in post #1

Back in post #11 axe0 asked you to answer the questions from the BSOD posting instructions. Can you do this so we have an up to date picture of what your system configuration is.
 
philc43 said:
I have a few more questions on your system. In an earlier post you said the problem started back in Feb 2017 so I have gone back to that mini-dump.
Click to expand...
Yes. That's when the problem started.

philc43 said:
I don't know if the system has changed since then but back then you had 8GB of memory using two different modules. Is it still the same?
Click to expand...
I currently have the same 8GB of memory
I have another partition that is running Win7 64bit just fine.
I just removed one 4GB of memory and started the machine. I got a BSOD 0x7b
I just removed the other 4GB of memory and replaced the first 4GB of memory and started the machine. I got a BSOD 0x7b
I have run Memtest for 24hrs before. It showed no failures.
I did have a memory manager in there to allow me to use the extra memory.

philc43 said:
You are currently trying to use Win7 32bit which will not be able to see all that memory anyway. Also, using two different memory sticks from different manufacturers can give rise to BSOD events. I would take one of them out as part of the troubleshooting tests.

The Feb 2017 mini-dump showed you were on BIOS_VERSION: 9SKT87AUS BIOS_DATE: 01/09/2015. The most up to date BIOS is 9SKT99A dated 2017/07/14 - this looks more recent than the one you mentioned in post #1
Click to expand...


I will update it now.
philc43 said:
Back in post #11 axe0 asked you to answer the questions from the BSOD posting instructions. Can you do this so we have an up to date picture of what your system configuration is.
Click to expand...

I didn't see that. I will take a look and get you all the info.

Thanks,

Docfxit
 
axe0 said:
Could you answer the questions from the posting instructions.
Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista
Click to expand...

I can't run Sysnative BSOD Dump + System File Collection App because I can't boot into the system to run anything.

ยท OS - Windows 7
ยท x86 (32-bit)
ยท The original installed OS on system was Win7
ยท The OS is an OEM version (came pre-installed on system)
ยท Age of system (hardware) I don't remember.
ยท Age of OS installation I don't remember - I have not re-installed the OS.

ยท CPU i7-3770 CPU @ 3.4GHz
ยท Video Card - Intel Sandybridge/Ivybridge Graphics Chipset
ยท MotherBoard - Lenovo M92p
ยท Power Supply - brand & wattage I don't know

ยท System Manufacturer Lenovo
ยท Exact model number M92p

ยท Desktop

Does this answer your questions?

Docfxit
 
To: Xilolee

I was instructed to run Fixing Windows boot problems - v7 - Macrium Reflect
on post #34

After running it the machine booted up to a blue screen with nothing on it. Macrium support didn't know how to fix it. The only way I was able to boot to see anything was to run Recovery console. When I ran Recovery console it deleted all the changes you asked me to put in. I'm very sorry all the work you did was lost.

I wrote a bat file to recreate all the changes you asked me to make. After re-building the boot entries I ran recovery console to test my rebuild.
Recovery console came up with this change:
The following startup options will be added:
Name: Windows Recovery Environment (recovered)
Path: Recovery\b0bb89f1-9f5b-11e7-8057-a0e8978e4021\Winre.wim
Windows Device: Partition=\\?\GLOBALROOT\Device\HarddiskVolume4 (68145 MB)

A copy of the current boot configuration data will be saved as: C:\Boot\BCD.Backup.0004

Is that something I need to add to the boot entries?

Currently this is what I have:
Code: 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {7ea0f578-f306-11e7-b76f-b416b7b9c242}
                        {7ea0f579-f306-11e7-b76f-b416b7b9c242}
timeout                 5

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

Windows Boot Loader
-------------------
identifier              {7ea0f578-f306-11e7-b76f-b416b7b9c242}
device                  partition=\Device\HarddiskVolume2
path                    \Windows\system32\winload.exe
description             Windows XP
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=\Device\HarddiskVolume2
systemroot              \Windows

Windows Boot Loader
-------------------
identifier              {7ea0f579-f306-11e7-b76f-b416b7b9c242}
device                  partition=\Device\HarddiskVolume4
path                    \Windows\system32\winload.exe
description             Windows 7 Ultimate
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=\Device\HarddiskVolume4
systemroot              \Windows

Thanks,

Docfxit
 
Check if you have the bootmgr file and the boot path in c: (in the first partition), and list the files in the boot path.
 
Last edited:
$RECYCLE.BIN DIR 1/5/2018 5:51:54 AM HS
Batch DIR 10/14/2017 9:39:43 AM -
BCD_Backup DIR 1/6/2018 7:37:31 AM -
boot DIR 1/6/2018 3:19:51 PM HSA
Dnload2 DIR 9/7/2017 8:26:57 AM -
FRST DIR 6/1/2017 12:49:50 PM -
HostingSpaces DIR 4/24/2014 7:45:18 AM -
inetpub DIR 12/6/2013 9:59:29 PM -
Intel DIR 4/20/2015 5:19:11 PM -
MyDocuments2 DIR 2/5/2017 6:31:56 PM -
NST DIR 9/26/2017 1:17:20 AM -
Perl DIR 1/8/2014 6:57:04 PM -
PHP DIR 12/29/2015 7:51:29 PM -
Program Files DIR 2/3/2017 5:38:40 PM R
ProgramData DIR 3/6/2017 8:55:06 AM -
Programs DIR 8/29/2017 12:02:40 PM -
Sandbox DIR 2/28/2014 8:09:52 PM R
Scratch DIR 11/29/2016 7:19:48 PM -
swshare DIR 11/10/2015 9:40:09 PM -
SWTOOLS DIR 10/19/2016 11:20:26 PM -
System Volume Information DIR 1/6/2018 10:45:28 AM -
Temp DIR 1/3/2018 6:28:09 PM -
Users DIR 3/6/2017 8:46:39 AM R
WebsitePanel DIR 1/12/2014 8:12:16 PM -
Windows DIR 1/5/2018 9:11:08 AM -
autoexec.bat 24 6/10/2017 7:03:33 AM A
bcdbackup.LOG 9216 6/10/2017 7:03:33 AM A
bdr-bz01 2294848 6/10/2017 7:03:33 AM A
bdr-cf01 308 6/10/2017 7:03:33 AM A
bdr-im01.gz 39692613 6/10/2017 7:03:33 AM A
bdr-ld01 253404 6/10/2017 7:03:33 AM A
bdr-ld01.mbr 9216 6/10/2017 7:03:33 AM A
boot.iniGood 212 6/10/2017 7:03:33 AM A
bootmgr 398156 1/5/2018 3:33:41 PM A
BootOSVer.txt 40 1/6/2018 3:19:48 PM A
cert.txt 62276 6/10/2017 7:03:33 AM A
config.sys 10 6/10/2017 7:03:33 AM A
dude.conf 691 6/10/2017 7:03:33 AM A
e.bat 116 6/10/2017 7:03:33 AM A
install.bin 128 7/1/2017 5:26:55 PM A
IO.SYS 0 12/6/2011 12:59:30 PM RA
MGlogs.zip 85594 6/10/2017 7:03:33 AM A
MSDOS.SYS 0 12/6/2011 12:59:30 PM RA
my.cnf 223 6/10/2017 7:03:33 AM A
ntdetect.com 47564 4/14/2008 7:00:00 AM A
ntldr 250048 4/14/2008 7:00:00 AM A
Null 46 1/6/2018 3:20:05 PM A
Redeploy.log 255748 1/5/2018 3:27:39 PM A
rescuepe.log 757 1/5/2018 3:31:54 PM A
SeeDisk.txt 1284 7/1/2017 5:28:04 PM A
SsRd0001.cif 3133251584 6/10/2017 7:03:33 AM A
 
I'm having trouble booting into XP.

This is the latest:
Code: 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {180435b3-f338-11e7-b961-f62f4e29a442}
                        {180435b4-f338-11e7-b961-f62f4e29a442}
timeout                 5

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

Windows Boot Loader
-------------------
identifier              {180435b3-f338-11e7-b961-f62f4e29a442}
device                  partition=D:
path                    \NST\ntldr
description             Windows XP
locale                  en-US
osdevice                partition=D:
systemroot              \Windows

Windows Boot Loader
-------------------
identifier              {180435b4-f338-11e7-b961-f62f4e29a442}
device                  partition=E:
path                    \Windows\system32\winload.exe
description             Windows 7 Ultimate
locale                  en-US
osdevice                partition=E:
systemroot              \Windows
resumeobject            {720b612e-f338-11e7-9951-806e6f6e6963}

The error I get is:
File: \nst\ntldr
Status: 0xc000007b

This partition was running along with the other two partitions just fine.

Thanks,

Docfxit
 
I had all partitions hidden except for the non bootable Windows7_OS and I disconnected one extra drive for troubleshooting. I needed to get some work done so I un hid my XP and Windows 64bit partitions. I couldn't boot into XP. I ended up booting into Windows 64bit and using EasyBCD to fix the XP booting problem.

Currently bootrec /ScanOs gives me these results:

Code: 
Scanning all disks for Windows installations.

Please wait, since this may take a while...

Successfully scanned Windows installations.
Total identified Windows installations: 1
[1]  E:\WINDOWS
The operation completed successfully.

Currently BCDEdit gives me these results: (Which don't look correct to me but it's booting)

Code: 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=D:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {180435b2-f338-11e7-b961-f62f4e29a442}
                        {180435b4-f338-11e7-b961-f62f4e29a442}
                        {default}
timeout                 5
displaybootmenu         Yes

Windows Boot Loader
-------------------
identifier              {180435b2-f338-11e7-b961-f62f4e29a442}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             Windows 7_OS
locale                  en-US
inherit                 {bootloadersettings}
bootdebug               No
osdevice                partition=D:
systemroot              \Windows
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {180435b4-f338-11e7-b961-f62f4e29a442}
device                  partition=F:
path                    \Windows\system32\winload.exe
description             Windows 7 Ultimate
locale                  en-US
osdevice                partition=F:
systemroot              \Windows
resumeobject            {720b612e-f338-11e7-9951-806e6f6e6963}

Real-mode Boot Sector
---------------------
identifier              {default}
device                  partition=F:
path                    \NST\ntldr
description             Microsoft Windows XP
locale                  en-US
custom:250000c2         0

Thanks,

Docfxit
 
softwaremaniac said:
We don't want the App, we want you to download the tools used for testing hardware and boot from a CD/USB in order to test your hardware for faults.
Click to expand...

If you are talking about:
Run HDD Diagnostics - http://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html
ยท Test RAM - http://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html

I have run both of them.

If you are talking about something else please let me know.

Thank you,

Docfxit
 

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

Back
Top