New
#1
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.