Infinite reboot-loop w/ BSOD stop error 0x0000007E post Microsoft Windows OS downgrade from W10x64 back to original OEM W7x64 and need to find root-cause to restore booting into W7x64 OS

Computer unit: HP ProDesk 60 G3 MT "It's a UPS Store customer Kiosk workstation."
OEM Operating System: Microsoft Windows 7 Pro (64-Bit) architecture w/ SP1

Problem details: Upgraded OS from W7 Pro x64 to W10 Pro x64, had to revert Windows 10 upgrade back to Windows 7 due to many BSOD crashes and overall system-wide stability issues and had to go back to previous OS due to bad OS upgrade from W7 to W10 x64.
The Microsoft Window 10 downgrade processed made it to the finish line; however, now Microsoft Windows 7 Pro w/ SP1 x64 is stuck on a infinite Reboot-Loop.

Troubleshooting & diagnostic info: I tried using F8 "Advanced Boot Options" and not able to successfully to load W7 OS using Safe Mode, Safe Mode w/ Networking, Last Known working configuration, etc. I've event tried using a USB flash-drive which contains W7 OS w/ SP1 booting into the Recovery Console.

I've tried using Start-Up repair and here is the most recent log info... "Root cause found: Unspecified changes to system configuration might have caused the problem"
I've tried the usual CHKDSK /F /R, sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows "Says there is a pending repair, but there is No Pending.xml located within the WinSxS container, I've event tried DISM /Image:D:\ /Cleanup-Image /RevertPendingActions and No-Dice "Gives errors msg stating to look @ the DISM logs, etc.

Even tried looking at the Updates and try removing using the following but still get DISM error msg and to refer to logs...
DISM /Image:D:\ /Get-Packages /ScratchDir:D:\temp /Format:Table
DISM /Image:D:\ /ScratchDir:D:\temp /Remove-Package  /PackageName:Package_for_KB###### /NoRestart

I've even tried fixing the Boot records, etc. using the following Command Line... "No-Dice"
D:\windows\system32>Bootrec /fixmbr
D:\windows\system32>Bootrec /fixboot
D:\windows\system32>Bcdedit /export c:\bcdbackup
D:\windows\system32>Attrib c:\boot\bcd -h -r -s
D:\windows\system32>Ren c:\boot\bcd bcd.old 
D:\windows\system32>Bootrec /rebuildbcd 

Unfortunately because of the OS upgrade to W10 and then downgrade back to original OEM W7 OS "There are no System Restore Points"

I tried to acquire a MiniDump @ the usual capture Windows directory and it won't produce one event if I utilize F8 Advanced Boot Options "Windows Error Recovery" and even tried selecting to force Enable Boot Logging, etc. for access via to C:\Windows\ and open the file ntbtlog.txt- still won't create a MiniDump which will reveal the smoking gun.

There is proprietary UPS software built on Microsoft .Net Framework architecture so doing a fresh/clean format re-installation of Microsoft Windows 7 Pro x64 OS is not an option. Too much UPS homegrown developed software & drivers which adds that complication that's preventing a complete fresh install of W7 x64 OS.

I believe I've taken a holistic & comprehensive approach to troubleshooting this particular issue and will greatly appreciate a "second/2nd" pair of eyes that could assist me in clearing out the BSOD stop error: 0x0000007E (0xFFFFFFFF80000003, 0xFFFFF8801E16059, 0xFFFFF880009A9328, 0xFFFFF880009A8B90) infinite loop so that this UPS store customer Kiosk PC boots into W7 Pro x64 OS.  

Many thanks in advance for your assistance!

Brian Rodriguez – IT Consultant & Owner
RELIABLE PC SUPPORT, LLC "Veteran owned & operated business"
Toll Free & Fax: 1-877-REL-PCRX (735-7279)
Direct: (561) 293-2533
E-mail: MSP@ReliablePCSupport.com
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
I wonder if one or more of the drivers that are now Windows 10 drivers did not downgrade.

https://answers.microsoft.com/en-us/windows/forum/windows_vista/blue-screen-error-0x0000007e/579a617b-be5c-4969-8f6a-4ec4d7b8f1a3

Can you replace Video and Networking drivers from the HP Support site putting them on a bootable USB key and updating that way.
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Thanks John, that indeed does sound like the possible culprit, it makes perfect sense that some of the W10 drivers did not properly revert back to W7 OS variant of the drivers once the automated W10 to W7 downgrade finished processing.

Normally I'm able to access the crash capture within the MiniDump and it will show which driver is causing the BSOD stop error: 0x0000007E

The last time this particular PC had a driver relate BSOD stop error, I was able to access the crash capture MiniDump and properly identify that it was the Ralink WLAN wireless adapter so I loaded the Registry Hives pertaining to the startup drivers and set the Ralink value to (4) = disabled... I tried using the same method thinking that the Ralink driver reactivated but it was still set to 4 as value on Registry.

I believe that you're indeed pointing me in the right direction - I'm assuming that if I acquired the original HP OEM drivers from either the HDD and/or HP's support site that the essential drivers could be updated if placed into USB flash drive via Command Line when using the W7 recovery console launched from an optical disk and/or USB flash stick since I can't access the W7 OS using any Safe Mode variant?

I'm puzzled on why the OS refuses to create a crash capture MiniDump, is there a Command that I can execute via the Recovery Console to force the OS to crash capture and generate dump?
JohnBusiness Consultant (Owner)Commented:
I'm assuming that if I acquired the original HP OEM drivers …..the essential drivers could be updated if placed into USB flash drive via Command Line  …  since I can't access the W7 OS using any Safe Mode variant?

I believe this should work.

You can try ProcDump from SysInternals for a dump file

https://docs.microsoft.com/en-us/sysinternals/downloads/procdump

Good luck
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

pgm554Commented:
I'm seeing some pretty new firmware for that box dated as of August of this year.
Is everything up to date?
JohnBusiness Consultant (Owner)Commented:
Good point above and you can update BIOS and Chipset via USB as well.
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Thanks for the tip pgm554 and looks like John concurs - I currently don't have physical access to that PC, however - I do have Intel AMT KVM capability on said PC which has been implemented & operational. I should to able to mount any BIOS/UEFI Firmware using the KVM on either Mesh Commander and/or VNC+ which are both AMT clients.

I'll checkout HP's support site and download the latest certified Firmware release...
HP ProDesk 600 G3 MT
Serial No. MXL716280R
Product No. 2DL57US#ABA
Asset Tag #: 00062675/MXL716280R

I'll flash the Firmware to the latest version release and will post the end results with status update...
nobusCommented:
was the Original windows 7 running stable before the upgrade to win10?
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Hi there nobus, the original OEM version of W7x64 Pro OS was running OK but not swift & snappy even though the hardware has a 7200 RPM w/ 6 Gbps I/O Toshiba Fusion-Drive and 16 Gigabytes of RAM along with a Quad-core CPU, etc. Standard Microsoft Windows based maintenance was processed on that PC including, CHKDSK /f /r, Defrag, CleanMgr, patching via Windows Updates with SP1+, and System Update Readiness tool - CheckSUR including SFC /scannow, etc. "The usual regular essential maintenance"

My SMB customer which owns & operates a UPS store wanted to update the OS for this particular HP ProDesk 600 G3 MT unit from W7x64 Pro to W10x64 Pro because all other UPS store Franchisees were implementing the same update from W7 to W10 along with being compliant. It was clearly a bad update which is rare but does indeed happen from "time-to-time" and when the W10 operating system was reverted back to Previous Build using Advanced Startup Options initiated via <Control Panel\All Control Panel Items\Recovery> before the 30-day grace period that Microsoft offers.

Normally I'm able to access the crash capture via Recovery Console from USB flash-stick that contains full-blown W7x64 OS w/ SP1 within the MiniDump and it will show which driver is causing the BSOD stop error: 0x0000007E
The issue is that the OS refuses to invoke the capture & creation of the DMP file for analysis even though before this whole ordeal occurred I've set the OS to collect & capture MiniDump and there was plenty of space allocated towards PageFile which is required for all crash captures, etc.

Very strange indeed, if you have a trick up your sleeve please do share this with me as I'll be more grateful and perhaps I can help you get out of a Snag in the future on your end... :-) Thx in advance! IT pro Brian w/ RPS
nobusCommented:
is there nothing more to that BSOD ?  if you see an exception code, it can help
to see the installed drivers, use driverview : http://www.nirsoft.net/utils/driverview.html
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Thanks again nobus for touching-base! :-)

2 quick items pertaining to this inquiry... 1st I've downloaded the latest BIOS/UEFI Firmware for this PC via @ https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-prodesk-600-g3-microtower-pc/15257651/model/15257652/swItemId/vc-216036-1

Catch-22 is that when you try to execute the HP Flashing utility in order for creating the boot-able USB flash stick with either method requires that the BIOS binary file is present on USB media in a specific folder - either "Hewlett-Packard\BIOS\new" or "EFI\HP\BIOS\new". The HPBIOSUPDREC utility has a feature that will copy the image file to the correct folder on a USB device for you.  

For example: As referenced above,  when trying to execute the HPBIOSUPDREC.exe, it displays an AppCrash dialog "see-attached" When trying to execute the HPBIOSUPDREC.exe, it displays an BEX64 dialog

Also, within the same HP Firmware flash utility container, when trying to execute the HPBIOSUPDREC64.exe, it displays the BEX64 dialog "see-attached" Also, within the same HP Firmware flash utility container, when trying to execute the HPBIOSUPDREC64.exe, it displays the BEX64 dialog
I've also tried replicating the same procedure using Microsoft Windows 7 Pro x64 OS as the above MS Windows 8.1 x64 OS and "No-Dice" same error mgs dialog pop-ups.

Perhaps I'll be able to find an alternative certified source of the HP BIOS/UEFI Firmware flashing utility, do you know of any viable 3rd party vendors with clean MD5 hash of said latest HP OEM Firmware?

2nd> I've used NirSoft's utilities before and they're fantastic, I'm assuming that the Nirsoft <Driver-View> is a portable self-executable that can be loaded from a USB flash stick using the Command Line while running the Windows 7 Recovery Console using MS W7 install DVD and/or boot-able USB flash stick? "I can't access any Safe Mode variant, i.e. Safe Mode standard, command line, w/ networking, etc.

Many thanks again for your intervention as it's greatly appreciated! :-)
JohnBusiness Consultant (Owner)Commented:
I have used Nirsoft utilities as well and keep key ones at hand.

I'm assuming that the Nirsoft <Driver-View> is a portable …  from a USB flash stick using the Command Line …. ?

Yes:  Quote "This utility is a standalone executable, so it doesn't require any installation process or additional DLLs. Just run the executable (driverview.exe) and start using it."
JohnBusiness Consultant (Owner)Commented:
Perhaps I'll be able to find an alternative certified source of the HP BIOS/UEFI Firmware flashing utility,

Is there an HP BIOS that you load onto a bootable media?  Lenovo has two:  on board (best if Windows is running) and Bootable Media.
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Thanks for chiming-in John as it's most appreciated! :-)
I'll go ahead and download NirSoft's <Driver-View> utility into a bootble USB flash stick and boot into the MS Windows 7 Recovery Console using OEM install disk on Optical Drive and will provide a status update with my findings...
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Thanks for replying to the BIOS/UEFI flashing utility corruption snag, the catch-22 is that this particular PC won't boot into OS and/or any variant of Safe-Mode, i.e. Safe Mode standard, SM command-line, and SM w/ networking, etc.

So unfortunately the only method of accessing the Registry Hives and NTFS file system is via booting into the MS W7 Recovery Console environment which has many limitations what type of functionality can be implemented.

I'll provide a status update regarding the NirSoft self-executable portable utility, you're most definitely on the right track regarding those W10x64 OS driver not properly reverting back to W7x64 OS architecture. I'm 99.999% certain that's the smoking gun.

Mission = find W10x64 driver that's invoking the BSOD stop error:  0x0000007E "Which is typically as bad driver that produces the BSOD" and what's making it harder than necessary is that even though there is clearly a PageFile and the configuration is set to capture crash-dump however, the downgraded original W7x64 OS refuses to execute said fail-over triggered task...
JohnBusiness Consultant (Owner)Commented:
There should be a BIOS update that does not require Windows. Perhaps not but you might check your particular model downloads
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Indeed John, the catch-22 is that even though there is a BIOS/UEFI update to Flash Firmware that's not Windows OS dependent, the only way to create the standalone update which creates a boot-able USB flash stick with the required .Bin files onto a specific folder - either "Hewlett-Packard\BIOS\new" or "EFI\HP\BIOS\new". The HPBIOSUPDREC utility has a feature that will copy the image file to the correct folder on a USB device for you.  

That particular utility which was sources via @ https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-prodesk-600-g3-microtower-pc/15257651/model/15257652/swItemId/vc-216036-1

"It was queried & filtered using both the HP ProDesk 600 G3 MT serial # and service tag #s"

Here is what happens when you try to create the Boot-able USB stick w/ Firmware using Windows 7 & 8.1 x64 "tech-bench-shop" workstation PCs for flashing the BIOS/UEFI, etc. see attached/embedded For example: As referenced above,  when trying to execute the HPBIOSUPDREC.exe, it displays an AppCrash dialog "see-attached"Also, within the same HP Firmware flash utility container, when trying to execute the HPBIOSUPDREC64.exe, it displays the BEX64 dialog "see-attached"
JohnBusiness Consultant (Owner)Commented:
Wow. It appears to be a Windows only machine (quote from your link above).  Too bad if it was running a non-Windows operating system.

It may be at this point that you need to do a fresh install of Windows.  If there is important data to keep, you may be able to start with a bootable USB key and recover the data, or move the drive to a carrier and recover it that way.
nobusCommented:
did you try the bios fix on the page you linked to?   it seems to fix problems like you are having?
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Hello again nobus :-)

It appears that HP has published corrupt Firmware on their main support site and FTP server. I've even back tested previous versions of the BIOS/UEFI firmware using my tech-bench PCs running Windows 7 and 8.1 (64-bit) @ my IT tech-shop/office and when you try to create a boot-able Firmware update USB flash stick the utility keeps crashing... "Please see screen capture below"

That particular utility which was sources via @ https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-prodesk-600-g3-microtower-pc/15257651/model/15257652/swItemId/vc-216036-1

"It was queried & filtered using both the HP ProDesk 600 G3 MT serial # and service tag #s"

Here is what happens when you try to create the Boot-able USB stick w/ Firmware using Windows 7 & 8.1 x64 "tech-bench-shop" workstation PCs for flashing the BIOS/UEFI, etc. see attached/embedded For example: As referenced above,  when trying to execute the HPBIOSUPDREC.exe, it displays an AppCrash dialog "see-attached/embedded"
HPBIOSUPDREC.exe-AppCrash-Capture.PNG
Also, within the same HP Firmware flash utility container, when trying to execute the HPBIOSUPDREC64.exe, it displays the BEX64 dialog "see-attached"

Very strange indeed, feel free to test drive the HP OEM Firmware update utility yourself using a physical PC and/or VM Hyper-visor and you'll see that all of their Firmware packages published online for that specific HP ProDesk 600 G3 MT generic and/or serial & service tag # specific so it looks like updating the Firmware won't be an option...

I'm going to try using NirtSoft's driver-view self-executable utility that John recommended in another thread, if used NirSoft's utilities in the past and they're fantastic - however, the catch-22 = since the computer won't boot into any form of Safe Mode while doing F8 Advanced Startup Options, the only recourse I have to limited Windows Registry Hives and NTFS file system is using a Microsoft Windows 7 Pro (64-Bit) optical disk and/or boot-able USB stick and invoking the Recovery Console.

Hopefully, Nirsoft's driver-view self-executable will allow me to call it up via Command Line within the Windows 7 Recovery Console environment. I'll post any important status updates. It's now X-mas here in USA southeast Florida EST so I may not be able to send out said status update and/or situation report until the 26th, etc.

Many thanks again nobus for touching-base as it's most appreciated and we'll be in touch! :-)
HPBIOSUPDREC64.exe-BEX64-Capture.PNG
nobusCommented:
did you look yet at the fix i suggested?
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Hello again nobus,

Are you referring to the tip about flashing the BIOS/UEFI Firmware?
If yes, please refer to my reply above w/ screen-captures...
Merry X-mas and please let me know if you know of an official HP alternate mirror to acquire a viable non-corrupt Firmware update, etc.
nobusCommented:
well - in the above  i can't find anything about that fix, sorry
check if this site has a better bios and tools :  https://support.hp.com/be-nl/drivers/selfservice/hp-prodesk-600-g3-microtower-pc/15257651
pgm554Commented:
Good old HP.
There's a reason why I don't use their products anymore.
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Due to the holiday season and New Year's eve approaching my IT biz has been trying to balance work & family - I'm currently implementing a comprehensive hail-marry holistic troubleshooting workflow and will post my findings right after New Year's day along with any request for a meeting of the IT minds to confirm theories, etc...
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
nobusCommented:
what are you saying, or asking?
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Hi there NOBUS, happy new year! 2019
I'm currently implementing a comprehensive hail-marry holistic troubleshooting workflow; in the meantime, I'm posting screen-captures to document my current efforts and if another other IT professional are available to team-up with me regarding solving that issue posted at the top of this thread...

Currently I'm on the Command Line via Windows Recovery console and as of right now, I'm trying to revert any Windows packages via DISM in order to get this specialty HP customer Kiosk PC for a UPS store @  Southeast Florida, USA.

I've pulled up all packages using this DISM command-line...
DISM /Image:C:\ /ScratchDir:C:\temp /Get-Packages /Format:Table
You can then replace the package name into this command and it will attempt to remove them.
DISM /Image:C:\ /ScratchDir:C:\temp /Remove-Package /PackageName:Package_for_KB###### /NoRestart

Removal of Windows Updates “Offline”...
DISM /Image:C:\ /ScratchDir:C:\temp /Cleanup-Image /RevertPendingActions (change C to the applicable drive letter)

SFC offline repair...
sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows

I will post my findings soon after and hopefully they will be promising...
nobusCommented:
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Hi nobus, thanks for the tip but DISM for Windows 10 is much more robust than the Microsoft Windows 7 x64 Kiosk PC that I'm trying to rescue. The only DISM command line that Windows 7 architecture will process is " DISM /Online /Cleanup-Image /ScanHealth" and the catch-22 will be that the OS image needs to be online as it won't work on a offline Recovery Console.
nobusCommented:
you don't have a prior image of the win 7 drive?
Brian RodriguezIT Consultant & Owner w/ RPS "Veteran owned business"Author Commented:
Hi there again nobus and thanks for checking-up...
Unfortunately there is no backup image of the UPS store Kiosk Microsoft Windows 7 (64-bit) volume, I'm currently throwing everything at this particular issue except the kitchen sink...LOL!

Also, due to the proprietary software framework stack architecture that UPS runs on their Kiosk PCs - there is no viable option like reformatting the HDD and reinstalling the OS, hardware drivers, and essential software program applications, etc.
nobusCommented:
sinc e you mentioned many crashes, i suggestto take a new disk and install an OS on it for testing
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Operating Systems

From novice to tech pro — start learning today.