Windows 10: BSODs during boot

Hello everyone, I have been facing BSODs during boot time for some months now on my laptop. When I turn it on there is a slight chance of not booting normally, where the spinning ring animation freezes and then throws a DPC_WATCHDOG_VIOLATION BSOD and then restarts itself and boots normally. I also asked for help in Microsoft forums but I had no luck there. My laptop is an HP 255 G7 with an AMD Ryzen 3 2200U CPU. Thank you for taking the time. I have also uploaded a dump file. Windows version 21H1 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff8003cefb320, 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.mSec Value: 12390 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 36739 Key : Analysis.Init.CPU.mSec Value: 937 Key : Analysis.Init.Elapsed.mSec Value: 9461 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8003cefb320 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8004051ec20 -- (.trap 0xfffff8004051ec20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000abdbf0d3 rbx=0000000000000000 rcx=ffffa2820e31900e rdx=000000000000004a rsi=0000000000000000 rdi=0000000000000000 rip=fffff8003c523a3a rsp=fffff8004051edb0 rbp=0000000000000160 r8=0000000000000002 r9=0000000000001000 r10=0000000000000000 r11=fffff8004051ed60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!EtwpReserveTraceBuffer+0x12a: fffff800`3c523a3a 48c1e220 shl rdx,20h Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff800`4051edb0 fffff800`3c524049 : 00000000`00000000 00000000`00000000 fffff800`4051eeb0 00000000`00000002 : nt!EtwpReserveTraceBuffer+0x12a fffff800`4051ee40 fffff800`3c4c8f5f : 00000000`00000004 ffffa282`0e303000 00000000`ffffffff 0000004a`00000002 : nt!EtwpLogKernelEvent+0x1e9 fffff800`4051eef0 fffff800`3c5f82d1 : ffffb781`82b44dc8 fffff800`405178b0 ffffb781`82b44dc0 fffff800`3c5f846b : nt!PerfInfoLogInterrupt+0xef fffff800`4051ef70 fffff800`3c5f7ef7 : ffffa282`0eb4c960 ffffa282`0eb4c960 00000000`00000000 ffffa282`0da022c0 : nt!KiScanInterruptObjectList+0x181 fffff800`40517830 fffff800`3c55405d : ff000000`ff000000 ff000000`ff000000 0000004a`00000000 fffff800`3c5f2f20 : nt!KiChainedDispatch+0x37 fffff800`405179c0 fffff800`3c512172 : ffffa282`0da02340 fffff800`3c5604ff 00000000`00000001 ffffa282`00000000 : nt!RtlpHpLfhSubsegmentFreeBlock+0x8d fffff800`40517a70 fffff800`3cbb3149 : 00000000`00000000 00000000`00000001 ffffa282`0ecba040 01000000`00100000 : nt!ExFreeHeapPool+0x362 fffff800`40517b50 fffff800`3c467c2e : ffffffff`ffffffa0 fffff800`3fef8317 00000000`01000010 00000000`00000246 : nt!ExFreePool+0x9 fffff800`40517b80 fffff800`3fef8353 : 00000000`00000001 ffffa282`110fda60 fffff800`40517bd0 00000000`00000018 : nt!IoFreeMdl+0x6e fffff800`40517bb0 fffff800`3fef8241 : 00000000`00000000 00000000`00000000 ffffa282`0e304420 00000000`00000000 : CLASSPNP!DestroyTransferPacket+0x7f fffff800`40517be0 fffff800`3c50a5d2 : 00000000`0000000c 00000000`0000000f fffff800`37f56180 ffffa282`00000002 : CLASSPNP!ClasspCleanupPacketTimerDpc+0x251 fffff800`40517c30 fffff800`3c522b99 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000188 : nt!KiProcessExpiredTimerList+0x172 fffff800`40517d20 fffff800`3c5fdc65 : 00000000`00000000 fffff800`37f56180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x9d9 fffff800`40517fb0 fffff800`3c5fda50 : ffffa282`0e0f0140 ffffa282`0e0f0140 ffffffff`ffffffa0 00000000`43bf25ae : nt!KxRetireDpcList+0x5 fffff908`db853720 fffff800`3c5fd11e : ffffa282`0eab1080 fffff800`3c5fe153 fffff800`37f56180 000f8067`b8bbbdff : nt!KiDispatchInterruptContinue fffff908`db853750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee STACK_COMMAND: .trap 0xfffff8004051ec20 ; kb SYMBOL_NAME: nt!ExFreePool+9 IMAGE_NAME: Pool_Corruption IMAGE_VERSION: 10.0.19041.1052 MODULE_NAME: Pool_Corruption BUCKET_ID_FUNC_OFFSET: 9 FAILURE_BUCKET_ID: 0x133_ISR_nt!ExFreePool OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {53888658-8be2-bca4-3aca-c7e695ecef84} Followup: Pool_corruption ---------

:)

 

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

 

BAD_POOL_HEADER BSOD, Dump File attached


Hi Groggubus,

Welcome to the 10forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please follow this suggestion for the BSOD

1. Please open BitDefender and go to the modules,
2. Go to the firewall settings,
3. Uncheck 'Block port scans in the network',
4. Reboot your system <-- IMPORTANT