Windows 10: BSOD

Discus and support BSOD in Windows 10 BSOD Crashes and Debugging to solve the problem; Got a BSOD but dont know how to read and find the source of the problems... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by A_Zed, Apr 22, 2020.

  1. A_Zed Win User

    BSOD


    Got a BSOD but dont know how to read and find the source of the problems

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DPC_WATCHDOG_VIOLATION 133
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count in ticks.
    Arg3: 0000000000000500, The DPC time allotment in ticks.
    Arg4: fffff8043a773358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

    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


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202


    SYSTEM_VERSION: Default string

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: F4 C1

    BIOS_DATE: 09/11/2018

    BASEBOARD_MANUFACTURER: Gigabyte

    BASEBOARD_PRODUCT: Gigabyte

    BASEBOARD_VERSION: Default string

    DUMP_TYPE: 1

    BUGCHECK_P1: 0

    BUGCHECK_P2: 501

    BUGCHECK_P3: 500

    BUGCHECK_P4: fffff8043a773358

    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

    CPU_COUNT: c

    CPU_MHZ: c78

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,9e,a,0 F,M,S,R SIG: 96'00000000 cache 96'00000000 init

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: System

    CURRENT_IRQL: d

    ANALYSIS_SESSION_TIME: 04-22-2020 02:29:41.0485

    ANALYSIS_VERSION: 10.0.18362.1 x86fre

    LAST_CONTROL_TRANSFER: from fffff8043a43d82d to fffff8043a3c2390

    STACK_TEXT:
    ffffba80`e9124b08 fffff804`3a43d82d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    ffffba80`e9124b10 fffff804`3a2b8e2c : 00003a38`dcea9321 ffffba80`e9105180 00000000`00138ff2 00000000`00138ff2 : nt!KeAccumulateTicks+0x1815bd
    ffffba80`e9124b70 fffff804`3a15d567 : 00000000`00000000 ffff9a83`164af5e0 ffff9a83`164af660 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
    ffffba80`e9124f30 fffff804`3a22cc75 : 0000002e`a3f64af6 ffffe00f`4a8d6d00 ffffe00f`4a8d6db0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
    ffffba80`e9124f60 fffff804`3a3c3e1a : ffff9a83`164af660 ffffe00f`4a8d6d00 00000000`00000000 ffffe00f`4a8d6d00 : nt!KiCallInterruptServiceRoutine+0xa5
    ffffba80`e9124fb0 fffff804`3a3c4387 : ffffe00f`4fb5ef00 ffff9a83`164af668 00000000`80000000 fffff804`3a3c4394 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    ffff9a83`164af5e0 fffff804`3a2b523b : ffffffff`ffffffd1 fffff804`3a246c54 00000000`00000010 00000000`00000a87 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffff9a83`164af770 fffff804`3a246c59 : ffffe00f`4bafe240 00000000`00010001 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
    ffff9a83`164af7a0 fffff804`3a2c115a : ffffba80`e9107f80 00000000`1f7e06f5 ffff9a83`164af7a8 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0x139
    ffff9a83`164af7f0 fffff804`3a2c07af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x30a
    ffff9a83`164af930 fffff804`3a3c5ebe : 00000000`00000000 ffffba80`e9105180 ffffba80`e9116340 ffffe00f`5d1cf080 : nt!KiRetireDpcList+0x1ef
    ffff9a83`164afb60 00000000`00000000 : ffff9a83`164b0000 ffff9a83`164a9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e


    THREAD_SHA1_HASH_MOD_FUNC: 2256b43df37e7f14f955ca675786cc7d811634c4

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c56b0d8f44bce0ef56ff353c93f8ac2fd5e13859

    THREAD_SHA1_HASH_MOD: de26d798fe7dc370d1bae481b581f432e20583f4

    FOLLOWUP_IP:
    nt!KeAccumulateTicks+1815bd
    fffff804`3a43d82d cc int 3

    FAULT_INSTR_CODE: f68445cc

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KeAccumulateTicks+1815bd

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5629d63a

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1815bd

    FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

    BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

    PRIMARY_PROBLEM_CLASS: 0x133_DPC_nt!KeAccumulateTicks

    TARGET_TIME: 2020-04-22T06:11:33.000Z

    OSBUILD: 18362

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 784

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2015-10-23 02:39:54

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

    ANALYSIS_SESSION_ELAPSED_TIME: 18bd

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_dpc_nt!keaccumulateticks

    FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

    Followup: MachineOwner
    ---------

    :)
     
    A_Zed, Apr 22, 2020
    #1
  2. ARC
    Arc Win User

    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.
     
  3. cplpro Win User
    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 BSOD :)
     
    cplpro, Apr 22, 2020
    #3
  4. axe0 Win User

    BSOD

    BAD_POOL_HEADER BSOD, Dump File attached


    Hi Groggubus,

    Welcome to the 10forums BSOD :)

    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

    BSOD [​IMG]

    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
     
Thema:

BSOD

Loading...
  1. BSOD - Similar Threads - BSOD

  2. BSOD from gaming and random

    in Windows 10 BSOD Crashes and Debugging
    BSOD from gaming and random: Hi thereI've been having a rough week when it comes to my PC. This picture should give you an idea:I have a memory dump if anyone can help explain what is going on?https://drive.google.com/file/d/1mnIUt3mg505qpZMVALSgn9roMsAkP5qA/view?usp=drivesdk...
  3. PC sudden freezes and restarts without BSOD

    in Windows 10 Installation and Upgrade
    PC sudden freezes and restarts without BSOD: I ran verifier and kept getting BSODhere is the minidump and sysinfohttps://we.tl/t-rB0LFgASR4the errors in eventvwr areThe computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff807038fa320. A...
  4. occasionally BSODs, error 154 store component exception

    in Windows 10 BSOD Crashes and Debugging
    occasionally BSODs, error 154 store component exception: Hello guys.recently I've been struggling with occasional and random BSODs.They appear totally random, with no specific event to make them happen.some days ago, nothing except official Telegram app and IDM was running on pc, suddenly saw my Kernal_Data_inpage error and...
  5. occasionally BSOD, error 154 store component exception

    in Windows 10 BSOD Crashes and Debugging
    occasionally BSOD, error 154 store component exception: Hello guys.recently I've been struggling with occasional and random BSODs.They appear totally random, with no specific event to make them happen.some days ago, nothing except official Telegram app and IDM was running on pc, suddenly saw my Kernal_Data_inpage error and...
  6. System worked for 2 months...constant BSOD ever since.

    in Windows 10 BSOD Crashes and Debugging
    System worked for 2 months...constant BSOD ever since.: Hello, I am at my wits end with my latest build. I built my machine back in October 2020. I got 2 months of use and 8 months of chasing my tail. Here are the specs: Operating System: Windows 10 Home build 19043 64-bitCPU Type: AMD Ryzen 9 3900XT 12-Core Motherboard: MAG...
  7. BSOD CRITICAL PROCESS DIED

    in Windows 10 BSOD Crashes and Debugging
    BSOD CRITICAL PROCESS DIED: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000de 0x0000000000000002, 0xffff980837181368, 0xffff98084a78d530, 0x00002001d452a8c0. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: eb58b8dd-be5e-423c-b96a-755860a63e7bi can send the MEMORY.dmp file if...
  8. BSOD, Blank Screen and Buzz Sound

    in Windows 10 BSOD Crashes and Debugging
    BSOD, Blank Screen and Buzz Sound: From many days, I am having problems of these.BSOD happens with stop codes: SYSTEM SERVICE EXCEPTION, UNEXPECTED STORE EXCEPTION and rarely other. BSOD screen will stuck at 0% and no memory dumps are collected. Need to hard reboot every time. Happens once every two days.Blank...
  9. BSOD Constantly Again

    in Windows 10 BSOD Crashes and Debugging
    BSOD Constantly Again: I'm starting to think that this is a physical issue now but one more try,I ran so many tests through cmd and everyyyything my minidump wont log anything and my event viewer is totally wack and not giving any info After BSODThe only place I can find any info on this stuff is...
  10. Constant BSOD on ASUS Zephyrus G14 2020

    in Windows 10 BSOD Crashes and Debugging
    Constant BSOD on ASUS Zephyrus G14 2020: Hello, I am having an issue, well multiple issues with my laptop.i get constant bsod's, black screens, and screen freezes, and it makes it difficult to get any work done.it mainly happens when idle or under low work load like working on music or browsing the internet, when i...