Windows 11 Install Failing with BSOD using Installation Assistant

Having a difficult time installing Windows 11 over my current Windows 10 OS. Hardware passes all the pre install tests, but when running Windows 11 Installation Assistant, I end up getting a BSOD at 80 to 87% install progress. Error notice is "System_Service_Exception". I have tried 5 times so far, and end up at the same result. Should I try with an ISO file instead? Built this about 1 year ago, and NEVER experienced a BSOD until this upgrade attempt.

1) Please run the V2 log collector and post a share link into this thread using drop box, or google drive

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)


2) Run Tuneup plus > post a share link

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

Batch files for use in BSOD debugging - Windows 10 Forums


3) Run: upgrade_failure_info > post a share link

https://www.tenforums.com/attachmen...s-use-bsod-debugging-upgrade_failure_info.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums


4) Run:

Download WhyNotWin11 - MajorGeeks

Post a share link.

Here is the Dropbox link to the folder containing the Troubleshooting files 1 thru 4 above.

1) The BIOS Version/Date American Megatrends International, LLC. L2.71, 4/14/2023

Upgrade the BIOS to the most up to date non-beta BIOS.



2) Uninstall Avast Free Antivirus





3) Uninstall COMODO Firewall




4) Make sure that defender is on



5) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10



6) Create a new restore point

Create System Restore Point in Windows 10



7) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail


Option six and option five in this link:



8) Plan to run the tool with multiple customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial



9) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



Customized tests will then be posted for the next run of WDV.



WDV can run continuously during the testing.



For any BSOD post a new V2 share link into the newest post.



10) Download to a new desktop folder





11) Additional steps will be posted after WDV and before the next upgrade attempt

They can be re-enabled.

First run of WDV:
BSOD Driver_Verifier_IOManager_Violation
PxHlpa64.sys

Link to V2:

1) Uninstall:

a) pxhlpa64 PxHlpa64 c:\windows\system32\drivers\pxhlpa64.sys

b) CloneCD 5.3.4.0 SlySoft



2) Create a new restore point



3) Restart WDV with these groups of customized tests:



Group 1
[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.



Group 2
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.



Group 3
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.



For each group if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



For any BSOD post a new V2 share link into the newest post.





PxHlpa64.sys Thu Mar 21 10:51:08 2019 (5C93B2EC)

anydvd AnyDVD c:\windows\system32\drivers\anydvd.sys
AnyDVD.sys Mon Dec 28 06:52:15 2015 (5681307F)

Questions:
1) How to uninstall pxhlpa64 c: ? Do I have to do that from admin cmd prompt like unregistering a .dll?
Can I just use MS Autoruns and delete it from the drivers tab there?
2) No app CloneCD 5.3.4.o SlySoft on this machine. Only SlySoft app is AnyDVD. I can uninstall it if you don't think the CloneCD might be part of another application installed. I have uninstalled AnyDVD.
3) Do I issue the verifier /reset or verifier /bootmode resetonboot fail commands prior to creating the new restore point?
4) Each of the 3 WDV groups constitute a unique run of WDR, right?
Sorry for all the questions. Really appreciate your help on this.

jsauser11 said:

I have uninstalled AnyDVD

Click to expand...

You may not be able to reinstall it. The company went out of business.

Loss of AnyDVD not a problem. Have gotten Group 1 done, no BSOD. Link to results will be posted in next message.
Group 2 resulted in BSOD. Just obtained reboot and will run and post V2 link in net message. Should I proceed with Group 3?

Group 1 Results: No BSOD
Group 2 Results: BSOD DRIVER_VERIFIER_DETECTED_VIOLATION

Group 3 Results: BSOD DRIVER_VERIFIER_DETECTED_VIOLATION
(Note: Error collection never proceeded beyond 0%)

jsauser11 said:

Questions:
1) How to uninstall pxhlpa64 c: ? Do I have to do that from admin cmd prompt like unregistering a .dll?
Can I just use MS Autoruns and delete it from the drivers tab there?

Click to expand...

The driver may be part of one of these installed software:

DVD Flick 1.3.0.7 1.3.0.7 Dennis Meuwissen 20240324
DVD Shrink 3.2 DVD Shrink
DVDFab 13 (x64) 13.0.1.7 DVDFab Software Inc. 06/0/224


Use autoruns as needed: (option six)


Apply to 2) below too.

jsauser11 said:

2) No app CloneCD 5.3.4.o SlySoft on this machine. Only SlySoft app is AnyDVD. I can uninstall it if you don't think the CloneCD might be part of another application installed. I have uninstalled AnyDVD.

Click to expand...

jsauser11 said:

3) Do I issue the verifier /reset or verifier /bootmode resetonboot fail commands prior to creating the new restore point?

Click to expand...

WDV will run indefinitely until the tool is turned off.

The commands verifier /reset or verifier /bootmode resetonbootfail are used to turn off the tool.

A new restore point is created after uninstalling or reinstalling drivers and before the next run of WDV.

jsauser11 said:

4) Each of the 3 WDV groups constitute a unique run of WDR, right?
Sorry for all the questions. Really appreciate your help on this.

Click to expand...

There are approximately 20 plus customized tests.


Uninstall:

a) usb28xxbga USB 28274 Device c:\windows\system32\drivers\embda64.sys

b) Run again the Avast and Comodo uninstall tools

c) pxhlpa64.sys




Create a new restore point.





Restart WDV with all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.


If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



For any BSOD post a new V2 share link into the newest post.

Greetings. Per the last response, I uninstalled DVD Flick, DVD Shrink, and DVDFab. As I previously removed pxhlpa64.sys via autoruns as well. However, this has made my BluRay device inoperable (see BluRay Cannot Start attached), as pxhlpa64 is one of the drivers for it.
embda64.sys is another matter. As you can see from the attached Hauppauge Card Driver file, embda64.sys is a driver of that card. If you want me to disable the Hauppauge device, uninstall the drivers (with Device Manager, since there is no app) and pull the card, I can do that. I believe that is the only way to get that driver out of the system. I could not find the usb28xxbga USB 28274 Device to uninstall it. The only device I could find with embda64.sys was the Hauppauge WinTV Quad card.
Did a restore point and ran the WDV with all customized tests except Randomized low resource simulations checked on all non-Microsoft drivers resulting in a BSOD. V2 file of that is also attached.

Plan to reinstall drivers / software as needed after a successful upgrade.

(Some though could be incompatible with memory integrity)


Please restart WDV with all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.

Test all non-Microsoft drivers except:

PxHlpa64.sys



Whenever possible turn off WDV using commands.

System restore is a last resort as it often deletes the dump file.



If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



For any BSOD post a new V2 share link into the newest post.

​

Ran WDV again with all tests except Randomized low resources simulation.
Driver PxHlpa64.sys is no longer on the non-Microsoft drivers list offered up by WDV.
BSOD on restart (DRIVER_VERIFIER_DETECTED_VIOLATION).
Restarted in safe mode and issued verifier /reset and verifier /bootmode resetonboot fail
Restarted and Windows 10 booted.
Here is the link to the V2 I ran after that:

I just spoke to the tech at Hauppauge, and he had me install a new driver package for the WinTV Quad card. Old driver package was from 2022. New package is from 06/2024. Should I run the last test again to see if this fixed the issue with emBDA64.sys?

Today is 04/14.
The last created mini dump was from 03/13.


Please test all non-Microsoft drivers and restart WDV with these groups of customized tests:


Group a

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).


Group b
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.


Whichever group has a crash > restart WDV after verifier /reset to create multiple crashes

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



For any BSOD post a new V2 share link into the newest post.

Group a)
Ran 2 times, then verifier /reset.
Ran 2 times, then verifier /reset.
All 4 runs, error collection went to 100% on the BSOD.
V2 Link:

Group b)
Ran 2 times, then verifier /reset
Ran 2 times, then verifier /reset
Only on run 2 of 4 did error collection go to 100%, on run 1, 3, and 4 it never went beyond 0% error collection at BSOD.
V2 Link: