Windows 10: BSOD while booting

I'm getting BSODs on windows startup, making me unable to boot into boot into windows, this problem started after installing 2004 update, As of now, only way to use windows is using safe mode.

My Laptop specs: (using inxi -F in manjaro (dual booted))

Machine: Type: Convertible System: LENOVO product: 80S9 v: Lenovo YOGA 510-14AST Mobo: LENOVO model: Lenovo YOGA 510-14AST v: SDK0J40679 WIN serial: <root required> UEFI: LENOVO v: 1RCN27WW(V1.07) date: 01/13/2017 Battery: ID-1: BAT1 charge: 17.1 Wh condition: 30.5/35.0 Wh (87%) CPU: Topology: Dual Core model: AMD A9-9410 RADEON R5 5 COMPUTE CORES 2C+3G bits: 64 type: MCP L2 cache: 1024 KiB Speed: 1397 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1738 2: 1751 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.8 driver: amdgpu FAILED: ati unloaded: modesetting tty: N/A OpenGL: renderer: AMD STONEY (DRM 3.35.0 5.4.44-1-MANJARO LLVM 10.0.0) v: 4.5 Mesa 20.0.7 Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Family 15h Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.44-1-MANJARO Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 IF: enp2s0 state: down mac: 98:29:a6:09:2c:6e Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter driver: ath10k_pci IF: wlp3s0 state: up mac: 3c:95:09:ff:e9:5f Device-3: Qualcomm Atheros type: USB driver: btusb IF-ID-1: docker0 state: down mac: 02:42:77:f4:d0:ae Drives: Local Storage: total: 931.51 GiB used: 67.27 GiB (7.2%) ID-1: /dev/sda vendor: Western Digital model: WD10SPCX-24HWST1 size: 931.51 GiB Partition: ID-1: / size: 316.45 GiB used: 67.24 GiB (21.2%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 9.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6 Sensors: System Temperatures: cpu: 47.9 C mobo: N/A gpu: amdgpu temp: 47 C Fan Speeds (RPM): N/A Info: Processes: 180 Uptime: 16m Memory: 6.75 GiB used: 1.70 GiB (25.1%)

The stop code of the BSOD is

DPC_WATCHDOG_VIOLATION

If I understand correctly, this means some program or driver is getting stuck and it times out, then windows watchdog kills it and throws the BSOD

------

Here's the analysis of MEMORY.DMP using Windbg

DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff80577cfa318, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 8 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-CAEBGI6 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 174 Key : Analysis.Memory.CommitPeak.Mb Value: 67 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff80577cfa318 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED BLACKBOXNTFS: 1 (!blackboxntfs) PROCESS_NAME: smss.exe STACK_TEXT: ffffda80`6033fe18 fffff805`77459472 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`77cfa318 : nt!KeBugCheckEx ffffda80`6033fe20 fffff805`772ca2ed : 00000060`022f3eed 00000000`00000000 ffff9083`d86f2100 ffffda80`601c0180 : nt!KeAccumulateTicks+0x18bff2 ffffda80`6033fe80 fffff805`772ca16a : ffff8003`7bc7b480 ffff9083`d86f2160 fffff805`00002099 00000000`00000000 : nt!KeClockInterruptNotify+0xbd ffffda80`6033ff30 fffff805`77208705 : ffff8003`7bc7b480 ffffda80`6033ff40 00000000`0000000c ffff6fd2`0ef2ccd6 : nt!HalpTimerClockIpiRoutine+0x1a ffffda80`6033ff60 fffff805`773df4ca : ffff9083`d86f2160 ffff8003`7bc7b480 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffda80`6033ffb0 fffff805`773dfa37 : 00000000`00000400 fffff805`773df565 00000000`00000400 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff9083`d86f20e0 fffff805`769a001c : fffff805`773d9dfb 00000000`00000000 ffff9083`d86f24b0 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff9083`d86f2278 fffff805`773d9dfb : 00000000`00000000 ffff9083`d86f24b0 00000000`00000000 00000000`00000000 : 0xfffff805`769a001c ffff9083`d86f2280 fffff805`772eda1b : 00000000`00000000 00001f80`00ff02ff 00000000`00000000 00001f80`00c602f0 : nt!HvlSwitchToVsmVtl1+0xab ffff9083`d86f23c0 fffff805`7737f4d5 : 00000000`001d792b 00000000`00000010 00000000`00000001 00000000`00000000 : nt!VslpEnterIumSecureMode+0x197 ffff9083`d86f2490 fffff805`7736074f : 00000000`001d792b 00000000`00000000 00000000`00000010 00000000`00000002 : nt!VslSetPlaceholderPages+0x6d ffff9083`d86f2540 fffff805`7725db4f : ffffbf00`0586b810 ffffffff`ffffffff 00000000`001d792b 00000000`00000000 : nt!MiUpdateSlabPagePlaceholderState+0x97 ffff9083`d86f2580 fffff805`7725da2c : ffffffff`ffffff91 00000000`00000000 fffff805`77c50ac0 00000000`00000000 : nt!MiGetPageFromSlabAllocator+0xcf ffff9083`d86f25c0 fffff805`77299d06 : ffff8003`7dbbf530 ffff9083`d86f26b9 00000000`00000000 80037dbb`f5300420 : nt!MiGetSlabPage+0x40 ffff9083`d86f25f0 fffff805`77211515 : ffff9083`d86f2880 ffffc983`d18c4bf8 ffffbf00`0322b930 ffff9083`d86f2860 : nt!MiResolveMappedFileFault+0x6f6 ffff9083`d86f2720 fffff805`77214695 : ffff9083`d86f2880 00000000`00000000 ffff9083`d86f2860 ffff9083`d86f2a20 : nt!MiResolveProtoPteFault+0x11e5 ffff9083`d86f2820 fffff805`77212a69 : 00007ffa`4119f000 fffff805`00000003 00000000`c0000016 00000000`00000004 : nt!MiDispatchFault+0x3d5 ffff9083`d86f2960 fffff805`773ebb1e : 00007ffa`410519e0 0000023f`53c02448 00000000`00000000 00000000`c0000034 : nt!MmAccessFault+0x189 ffff9083`d86f2b00 00007ffa`41053ed2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e 00000090`3767f250 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`41053ed2 SYMBOL_NAME: nt!KeAccumulateTicks+18bff2 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.329 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 18bff2 FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------

I also tried a third party program called "WhoCrashed" to analyze the dump files, here are the result from that

On Thu 25-06-2020 08:19:21 AM your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\062520-32421-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20) Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8035D2FA318, 0x0) Error: DPC_WATCHDOG_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 25-06-2020 08:19:21 AM your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x68932) Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8035D2FA318, 0x0) Error: DPC_WATCHDOG_VIOLATION Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Now, after doing all this, I'm stuck, I can't figure out what seems to be the issue, I originally thought this was an issue with 2004 update since 1909 use to work just fine, however that may not be the case, though I'm not 100% sure.

Also this is a fresh installation of windows, I did a complete re-installation last week, cause I was suffering from very same issue then, and I thought that a re-installation might fix the issue, it didn't

Any help is appreciated, thank you

submitted by /u/KayMK11
[link] [comments]

:)

 

ughhh! BSOD on boot

I guess my computer BSOD on boot right before getting to windows. not sure what the problem is though, everything is stable.

It gave me a list of two files in windows that could have caused the problems

 

Boot Process

Hi,

Please suggest me a link that can explain the boot process step by step of ...

• Windows 7,
• Windows 8.1,
• Windows 10,
• Windows Server 2008 R2 and
• Windows Server 2012 R2

With Regards

InTech

 

BSOD during boot every other time

The Event Logs did not show any evidence of BSODs so they may not even be recorded in the Event Viewer.

At this point I might suggest to try a clean boot, restart the computer a few times, and see if the same BSODs occur:

https://support.microsoft.com/en-us/kb/929135

Follow the steps for Windows 8.1. Windows Key + S opens Search