Maybe make sure it stays cool, and don't block vents. I would turn the system off let it cool down and see if it starts up ok. ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-8550U CPU 1.80GHz Identifier = REG_SZ Intel64 Family 6 Model 142 Stepping 10 This will let the system reconfigure all the hardware resources and send a new database to windows. I might go into bios and reset it back to defaults. when the watch dog timer expired the system called a bugcheck. One of the bugchecks looks like the PCI bus told your storage to power up and it did not respond, then the system tried to reset the device and it did not respond. This was probably caused by the following module: ntoskrnl.exe (nt+0x3f5210)īugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80612AFB320) On Wed 10:13:25 your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\120220-113625-01.dmp Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. The crash took place in a storage driver or controller driver. This was probably caused by the following module: storport.sys (storport!storportinitialize+0x26dc)įile path: C:\WINDOWS\system32\drivers\storport.sysĭescription: Microsoft Storage Port Driver Possibly this problem is caused by another driver that cannot be identified at this time. The crash took place in the Windows kernel. This bug check can also occur because of overheated CPUs (thermal issue). This could be caused by either a non-responding driver or non-responding hardware. This was probably caused by the following module: ntoskrnl.exe (nt+0x244567)īugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF805052FA320)įile path: C:\WINDOWS\system32\ntoskrnl.exeīug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. On Fri 00:06:53 your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\120420-37657218-01.dmp Possibly this problem is caused by another driver on your system that cannot be identified at this time. Your system configuration may be incorrect. The crash took place in a Microsoft module. Product: Microsoft® Windows® Operating Systemĭescription: UCM-UCSI KMDF Class Extension This was probably caused by the following module: ucmucsicx.sys (UcmUcsiCx+0x18A82)īugcheck code: 0x1D4 (0x0, 0x12, 0xFFFFD50EA0037840, 0x0)įile path: C:\WINDOWS\system32\drivers\ucmucsicx.sys On Fri 15:12:42 your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\LiveKernelReports\ I used Snappy Driver and have my OS updated to latest possible and it didn't help. When display power is off then my laptop boots normally.Īlso after BSOD finishes it boots as well with monitor turned on so there's no bootloop. This monitor also charges my laptop and has built in USB hub and Ethernet port. They happen when I turn on my Xiaomi Notebook Pro with USB C monitor attached and turned on. Current link in this post has been removed.Few months ago after my Windows 10 automatically updated I started getting weird BSODs while booting. Per this edited comment I started a thread and posted a much more updated version of this here. Feel free to link correct audio drivers as well (I don't use them)Įdit 3: I'm going to go through this a bit better and also look for the audio drivers as well as the Intel ME driver/package and test to make sure they worked. Good luck & have fun!Įdit 2: Official Realtek LAN drivers added, link updated. I don't like Intel's GPU control panel so I install the drive manually (devmgmt.msc -> right click and update driver). I'm not entirely done yet - audio is still missing - but I'll keep this link up for a few deleted** - only has Chipset, SerialIO and GPU. I 100% do not trust the drivers from Erying so I've been working on piecing together later or newest ones directly from Intel/NUC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |