TBWinPE boots, but results in BSOD

[pablo]

New Windows 11 installation on a Lenovo WorkStation P330. TBWinPE USB created with IFW 4.03a and latest Win 11 ADK (v24H2).

When I run TBWinPE with either a USB or a CD, the program boots and briefly opens, but then I quickly get a BSOD. The Stop Codes are MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION, or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

I ran the Windows Memory Diagnostic and it showed no errors. The same TBWinPE program on a CD also yields a BSOD. However, an old TBWinPE CD created with Win 10 ADK with IFW 3.57 will boot without failure, but the V3 program won't handle my V4 TBI files. I redid the USB with a fresh install, but it still blue screens.

I need to restore an earlier TBI file of Windows 11, but I can't seem to get around these BSODs. Help me please.

[pablo]

I opened an Administrator Command Prompt and ran "DISM /online /cleanup-image /restorehealth" and got "Operation Completed Successfully".
I also ran "sfc /scannow" and got "found corrupt files and repaired them".
But I still get a blue screen when I try to boot TBWinPE.

I'll run Memtest 86+ overnight.

[TeraByte Support(PP)]

Do you see the same errors if you use a TBWinRE build or a TBWinPE build using the previous version of the Windows 11 ADK as the source?

As a work-around, you could copy in the 4.03a IFW files after booting (or make them accessible on a data partition or USB flash drive) so you can run the current version. For example, copy imagew64.exe and ifw.ini to a USB flash drive, boot to TBWinPE, then run imagew64.exe from the flash drive using a Command Prompt or TBLauncher's Run option. You could also copy the files to the X: drive and run them from there (X: is the RAM drive when booted to TBWinPE). Since you're booting on a system that has 4.03a installed, you could also copy the files directly from there to the X: drive after booting (you wouldn't want to run imagew64.exe from the installed location since you want to restore over it).

[pablo]

The problem seems to have been caused by, of all things, a network card. My computer has two network devices, an onboard Intel Ethernet Connection and a Realtek PCIe card. I mostly use the Intel, but recently switched to the Realtek after updating the driver. It was the Realtek that was causing the MEMORY_MANAGEMENT blue screen. The TBWinPE USB would boot OK and I would briefly see the program, but after the "initializing network" and "startup complete" steps, it would immediately blue screen. That jogged my memory of switching from Intel to Realtek. Switching back to the onboard Intel fixed the problem.
For future use with the Realtek, I guess I'll need to uncheck the "Run network initialization" and "Run initialization programs in background" options when making a TBWinPE recovery USB.
I wonder why the Intel works and the Realtek doesn't. Maybe the new driver?

[TeraByte Support(PP)]

You could try that and see if it works.

Was the driver being used one built into WinPE or were you adding a driver for it (either by placing it in the Drivers folder for the build or enabling the option to include installed drivers)? Whichever way it was you could try the other way and see if you get better results. Also, if Realtek releases a newer driver it may fix the issue.

[pablo]

I haven't placed any drivers in my Drivers folder. I installed the drivers in Device Manager when I did the clean install of Win11.
I created another recovery disk without network initialization and it doesn't bluescreen on boot with the Realtek card in service. Both recovery disks (with & without network) boot properly with the OB Intel in service.
I rolled back the driver for the Realtek, but it still bluescreened. I even found and installed the original Lenovo driver that came with the computer, but it didn't work either. For all I know, there could be a physical problem with the Realtek network card. It's 6 years old and was a cheap $10 add-on. Next time I have the case open for cleaning or inspection, I'll pull the card and toss it.