Windows 10: BSOD

icrosoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff804`21400000 PsLoadedModuleList = 0xfffff804`2202a250Debug session time: Sun Jun 21 20:57:35.987 2020 UTC + 4:00System Uptime: 1 days 5:56:20.078Loading Kernel Symbols..........................................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 000000c8`8d588018. Type ".hh dbgerr001" for detailsLoading unloaded module list...................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff804`217dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8301`7f5efe20=00000000000001334: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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: fffff804220fa318, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging 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: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-EFV2N30 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 2 Key : Analysis.Memory.CommitPeak.Mb Value: 64 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff804220fa318BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: firefox.exeSTACK_TEXT: ffff8301`7f5efe18 fffff804`21859472 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`220fa318 : nt!KeBugCheckExffff8301`7f5efe20 fffff804`216ca2ed : 0000b0d1`c91ee7d9 00000000`00000000 fffff98a`e9f3f600 ffff8301`7f5d6180 : nt!KeAccumulateTicks+0x18bff2ffff8301`7f5efe80 fffff804`216ca16a : ffffac08`c30c99a0 fffff98a`e9f3f6e0 00000000`00694105 00000000`00000000 : nt!KeClockInterruptNotify+0xbdffff8301`7f5eff30 fffff804`21608705 : ffffac08`c30c99a0 fffff804`21743b07 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1affff8301`7f5eff60 fffff804`217df4ca : fffff98a`e9f3f6e0 ffffac08`c30c99a0 00000000`00000001 e0ebf845`8b48ccc3 : nt!KiCallInterruptServiceRoutine+0xa5ffff8301`7f5effb0 fffff804`217dfa37 : fffff98a`e9f3f888 ffff8301`7f5d6180 ffffac08`c30c99a0 ffffac08`d5eec0c0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff98a`e9f3f660 fffff804`2163338d : ffffffff`ffffffd2 fffff804`2163f6fe 00000000`00000010 00000000`00040282 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff98a`e9f3f7f0 fffff804`2163f6fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0xdfffff98a`e9f3f820 fffff804`2163e801 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`21ae8e42 : nt!KiDeferredReadySingleThread+0xc3afffff98a`e9f3fa10 fffff804`216d7f1a : 00000000`00000000 00000253`00000000 fffff98a`e9f3fb08 ffff8301`7f5d6180 : nt!KiExitDispatcher+0x141fffff98a`e9f3fa80 fffff804`21a6df65 : ffffac08`00000000 ffffac08`d5eec0c0 fffff98a`e9f3fb80 00000000`00000000 : nt!KeAlertThreadByThreadId+0xd6fffff98a`e9f3fad0 fffff804`217ef378 : ffffac08`d8fa0600 ffffac08`d5eec0c0 00000000`00000000 00000000`00000000 : nt!NtAlertThreadByThreadId+0x45fffff98a`e9f3fb00 00007fff`1218bb84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28000000c8`8ddfe6e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`1218bb84SYMBOL_NAME: nt!KeAccumulateTicks+18bff2MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 18bff2FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicksOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}Followup: MachineOwner---------

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

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