BSOD on startup and when trying to update windows on second boot

I have been getting a BSOD with my Zotac AQ01 mini PC when starting up from a cold boot and when I have tried to update windows. The BSOD does not occur every time on startup, it appears to be Random. It does happen every time I try and update windows to a newer version during the phase when it reboots multiple times during the updating process. I use this pc as my htpc for movies and I fell behind updating it so its still on windows 10 version 1511 I have tried multiple things to fix this

1. Checked for missing drivers or the yellow triangle notifications in device manager
2. Ran sfc/scannow chkdsk on C: drive and the DISM restore health / repair commands. Did not get any errors
3. Turned off windows firewall, wireless adapter and unplugged the usb wireless receiver for logitech keyboard when trying to update, Still got BSOD. There was nothing plugged into any of the USB slots.


Here is the BSOD I get when trying to update windows

==================================================
Dump File : setupmem.dmp
Crash Time : 4/21/2018 3:24:02 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff808`01fe12c0
Parameter 3 : fffff486`4c3e8ca8
Parameter 4 : fffff486`4c3e84f0
Caused By Driver : hal.dll
Caused By Address : hal.dll+3356
File Description :
Product Name :
Company :
File Version :
Processor :
x64Crash Address : Wdf01000.sys+12c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp
Processors Count : 4
Major Version : 15Minor
Version : 16299
Dump File Size : 528,364
Dump File Time : 4/21/2018 7:25:02 PM
==================================================

I do not currently have a dmp file for crashes on startup but I know it contains the same crash address Wdf01000.sys and bug check string thread exception not handled. In the past it was infrequent and most of the time I just left the pc on anyways so it wasn't a big deal. I have decided I want to find out what is the cause of the BSOD so I can update it to a newer windows version.

See posting instructions.

Please post both the DM and BETA log collectors.

There is no dmp other than the setupmem.dmp located in the rollback folder and I already posted the contents of that

The log collectors collect various files on the computer and post them on the desktop. Then zip and post into the thread.
The beta log collector collects more useful files.

Help haha

The problem seems to be associated with a driver called usbcharger.sys (this is normally associated with a driver that allows the USB port to act as a charger).

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80801fe12c0, fffff4864c3e8ca8, fffff4864c3e84f0}

*** WARNING: Unable to verify timestamp for USBCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for USBCharger.sys
Probably caused by : USBCharger.sys ( USBCharger+14a4 )

Here is the thread at the time of the crash:

Code:

STACK_TEXT:  
fffff486`4c3e8ee0 fffff808`06cd30ce : fffff802`afe7f000 fffff802`b02ec2d0 00000000`00000001 fffff802`b0125e5f : Wdf01000!imp_WdfObjectGetTypedContextWorker+0x20
fffff486`4c3e8f30 fffff808`06cc5a54 : 00001b79`5dee56d8 ffffe486`9fcbeb40 fffff486`4c3e8ff0 ffffe486`9fcbedc0 : ucx01000!Urb_USBPORTStyle_ProcessURB+0xa6
fffff486`4c3e8f90 fffff808`01fe78b1 : ffffe486`a211a920 00000000`00000088 00000000`0000000f ffffe486`9fcbeb40 : ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x4d4
fffff486`4c3e9020 fffff802`afeb78d9 : 00000000`00000014 fffff802`00000000 ffffe486`9fe28e01 fffff486`4c3e91c0 : Wdf01000!FxDevice::DispatchWithLock+0x601
fffff486`4c3e9110 fffff808`06c414a4 : fffff486`4c3e9290 fffff486`4c3e9444 ffffd40f`cc1f9980 ffffd40f`cc1f5000 : nt!IofCallDriver+0x59
fffff486`4c3e9150 fffff486`4c3e9290 : fffff486`4c3e9444 ffffd40f`cc1f9980 ffffd40f`cc1f5000 00000000`00000000 : USBCharger+0x14a4
fffff486`4c3e9158 fffff486`4c3e9444 : ffffd40f`cc1f9980 ffffd40f`cc1f5000 00000000`00000000 fffff486`00000000 : 0xfffff486`4c3e9290
fffff486`4c3e9160 ffffd40f`cc1f9980 : ffffd40f`cc1f5000 00000000`00000000 fffff486`00000000 00000000`00000001 : 0xfffff486`4c3e9444
fffff486`4c3e9168 ffffd40f`cc1f5000 : 00000000`00000000 fffff486`00000000 00000000`00000001 fffff486`4c3e91c0 : 0xffffd40f`cc1f9980
fffff486`4c3e9170 00000000`00000000 : fffff486`00000000 00000000`00000001 fffff486`4c3e91c0 fffff486`4c3e91b0 : 0xffffd40f`cc1f5000

Can you identify the software that installed it and see if you can update it?

A few months ago when I was looking thru the programs listed in the control panel I uninstalled a program called Fintek USB Charger because I didn't recognize it and it seemed unnecessary. I just checked again and its not under the listed programs in the control panel but there still is a folder for it in x86 program files. Whats the best way to permanently delete it off my computer so windows does not try and verify it. Is deleting the folder in x86 enough? I do not think I have a need for a usb charging program on this particular computer.

willburstyle06 said:

A few months ago when I was looking thru the programs listed in the control panel I uninstalled a program called Fintek USB Charger because I didn't recognize it and it seemed unnecessary. I just checked again and its not under the listed programs in the control panel but there still is a folder for it in x86 program files. Whats the best way to permanently delete it off my computer so windows does not try and verify it. Is deleting the folder in x86 enough? I do not think I have a need for a usb charging program on this particular computer.

That looks to be the culprit. You can manually delete the driver from C:Windows\System32\drivers and use a program like CCleaner to uninstall all traces of Fintek USB Charger. Hopefully that will fix it.

In C:Windows\System32\Drivers it won't let me delete the USBCharger.sys file. It says the action can not be completed because it is open in another program. How do I find what program that is so I can delete it. Looking through task manager there was no obvious usbcharger or fintek background or windows process that was running. I also tried running in safe mode but that did not work either.