Windows 10: how to identify the driver causing 0xC1900101

tried twice to go from 1909 to 2004 then twice to go from 1919 to 20H2 on an HP255 G6, fails with every time most often on boot the screen goes nuts - looks like the result you get when you try to use an unsupported resolution setting - and I have to hold the power key down until the box stops. In the setupact.log I can see the line:


2021-01-18 21:54:30, Info MOUPG CSetupDiagnostics: Tracing Data [CUSTOM] -> [PostRebootInstall] -> [Package360][04aeb416-3647-4458-96f3-bd1573450c88][B466E151-44B3-4339-BBB9-581A63214664.1][fe9011f7-a9b7-44ca-b04e-794dc4bb6dfb][][Failed][Windows 10 Home][18363][6][5][0xc1900101][0x20017][19041]


which tells me that there's a driver error but how do I identify the driver?


there's no warnings shown in Device Manager and the drivers are up to date as far as I can tell I use HP support to autoupdate


in one of the event logs I see:


The driver \Driver\WudfRd failed to load for the device SWD\DRIVERENUM\{cfabacad-7939-467c-96a7-93781d90d2d8}#WirelessButtonDriver_usersvc&3&3229b8bb&1.


but I'm not sure this is telling me anything - at risk of sounding dull my wireless, being internal to the box, has no buttons so I'm not sure that the driver not loading is any big deal


so I could certainly do with some help, thanks

:)

 

Identifying driver causing BSOD

My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states ntoskrnl.exe. I have the dump files available, will it be helpful in identifying the driver that is causing this
issue?

 

re-installing Windows 10, error 0xC1900101 - 0x20017: bad drivers?

@jonobugs, that's the 'simple' help page. There's a more technical page available. That one says...

Resolve Windows 10 upgrade errors - Windows IT Pro | Microsoft Docs

The log files should identify precisely which driver is at fault.

 

Driver problem?

Hi Sarah,

Driver issues might caused some performance failure. For us to identify the root cause of this issue, kindly answer these questions:

• What is the exact error message that you have received?
• What is the build number and version of your Windows?
• What troubleshooting steps have you done so far?

As an initial troubleshooting, we suggest running the hardware and device troubleshooter.

We will wait for your response.