Windows 10: LiveKernelEvent 141 error DAILY

Discus and support LiveKernelEvent 141 error DAILY in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, I know that there are other posts about this error, but they haven't helped at all and most of them are outdated. I have been getting this... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Thirtyben, Oct 18, 2020.

  1. THIRTYBEN
    Thirtyben Win User

    LiveKernelEvent 141 error DAILY


    Hello,

    I know that there are other posts about this error, but they haven't helped at all and most of them are outdated. I have been getting this error for months and I can't seem to find a solid solution to this problem. There doesn't seem to be a pattern or anything that I have noticed. I appreciate any help.

    Things I have tried:

    • Full Windows Reinstall
    • Clean graphics driver reinstall
    • Updating Windows
    • Running SFC and CHKDSK
    • Replacing GPU
    • Replacing my SSDs
    • And probably more that I forgot to list

    This error happens almost daily at this point as seen in reliability monitor:

    LiveKernelEvent 141 error DAILY 06e4ba2a-3897-4fbf-9ec0-2d2ef81f3e58?upload=true.png


    When it happens, my monitors go black for about 30 seconds and all applications crash/reset. I have checked the MEMORY.DMP file and this is what shows up:


    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: fffff803784fa320, 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

    Key : Analysis.CPU.Sec

    Value: 1

    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on BENS-PC

    Key : Analysis.DebugData

    Value: CreateObject

    Key : Analysis.DebugModel

    Value: CreateObject

    Key : Analysis.Elapsed.Sec

    Value: 4

    Key : Analysis.Memory.CommitPeak.Mb

    Value: 72

    Key : Analysis.System

    Value: CreateObject


    BUGCHECK_CODE: 133


    BUGCHECK_P1: 0


    BUGCHECK_P2: 501


    BUGCHECK_P3: 500


    BUGCHECK_P4: fffff803784fa320


    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED


    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1


    PROCESS_NAME: System


    STACK_TEXT:

    ffffbe81`11c92e18 fffff803`77c595ba : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

    ffffbe81`11c92e20 fffff803`77ac98bd : 0002174f`d28c3436 00000000`00000000 ffffa808`2785f000 ffffbe81`11c40180 : nt!KeAccumulateTicks+0x18cb6a

    ffffbe81`11c92e80 fffff803`77ac973a : ffffd605`d94e39a0 ffffa808`2785f0c0 00000000`0147dd24 ffffbe81`00000001 : nt!KeClockInterruptNotify+0xbd

    ffffbe81`11c92f30 fffff803`77a08725 : ffffd605`d94e39a0 00000000`00000000 00000000`00000000 ffff202b`330c6b0c : nt!HalpTimerClockIpiRoutine+0x1a

    ffffbe81`11c92f60 fffff803`77bdf9ea : ffffa808`2785f0c0 ffffd605`d94e39a0 00000000`00000006 ffffd605`f4598080 : nt!KiCallInterruptServiceRoutine+0xa5

    ffffbe81`11c92fb0 fffff803`77bdff57 : ffffd605`e1d17000 00000000`00000006 00000000`00000000 fffff803`9089031c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    ffffa808`2785f040 fffff803`90b8de33 : ffffd605`e8f99010 00000000`00000000 ffffd605`e926b000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    ffffa808`2785f1d0 fffff803`90b8e594 : 00000000`00000010 ffffd605`e1d13050 000029fa`1e2e9000 ffffd605`e8f9b010 : nvlddmkm+0x42de33

    ffffa808`2785f200 fffff803`90b6ca1a : 00000000`00000000 00000000`00000006 00000000`00000000 ffffd605`e926b000 : nvlddmkm+0x42e594

    ffffa808`2785f240 fffff803`90ad2249 : 00000000`00000000 ffffa808`2785f2d0 000029fa`1e2e9000 ffffd605`e49e8ca0 : nvlddmkm+0x40ca1a

    ffffa808`2785f290 fffff803`90ad84e7 : ffffa808`00000000 ffffd605`e1d20000 00000000`00000200 00000000`00000020 : nvlddmkm+0x372249

    ffffa808`2785f310 fffff803`90ad1cd3 : ffffd605`e926b000 00000000`00000003 ffffd605`e8f9b010 00000000`00000001 : nvlddmkm+0x3784e7

    ffffa808`2785f350 fffff803`90ad1ebf : ffffd605`f9d17920 ffffd605`00000023 ffffd605`e926b000 ffffd605`e49e8ca0 : nvlddmkm+0x371cd3

    ffffa808`2785f3a0 fffff803`90ad2f2e : 00000000`00000003 ffffa808`2785f5b0 00000000`00000003 ffffd605`e926b000 : nvlddmkm+0x371ebf

    ffffa808`2785f420 fffff803`90c6de7c : 00013154`2b1a6678 00013154`2b1a6678 ffffd605`e926b000 ffffd605`e8f9b010 : nvlddmkm+0x372f2e

    ffffa808`2785f480 fffff803`9086fd4a : ffffd605`e926b000 ffffd605`e8f9b010 ffffd605`e8f9b010 00000000`00000000 : nvlddmkm+0x50de7c

    ffffa808`2785f4b0 fffff803`77a3a6be : ffffbe81`11c43240 00000000`00000000 ffffa808`2785fa20 ffffbe81`11c40180 : nvlddmkm+0x10fd4a

    ffffa808`2785f760 fffff803`77a399a4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e

    ffffa808`2785f8d0 fffff803`77be1aae : ffffffff`00000000 ffffbe81`11c40180 ffffbe81`11c4b540 ffffd605`f4598080 : nt!KiRetireDpcList+0x1f4

    ffffa808`2785fb60 00000000`00000000 : ffffa808`27860000 ffffa808`27859000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e



    SYMBOL_NAME: nvlddmkm+42de33


    MODULE_NAME: nvlddmkm


    IMAGE_NAME: nvlddmkm.sys


    STACK_COMMAND: .thread ; .cxr ; kb


    BUCKET_ID_FUNC_OFFSET: 42de33


    FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function


    OS_VERSION: 10.0.19041.1


    BUILDLAB_STR: vb_release


    OSPLATFORM_TYPE: x64


    OSNAME: Windows 10

    FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

    Followup: MachineOwner


    Also, here is my PC info just in case:

    Operating System

    Windows 10 Pro 64-bit

    CPU

    Intel Core i9 10900K @ 3.70GHz 25 °C

    Comet Lake 14nm Technology

    RAM

    32.0GB Dual-Channel Unknown @ 1799MHz 18-19-19-39

    Motherboard

    ASUSTeK COMPUTER INC. ROG MAXIMUS XII HERO WI-FI LGA1200 22 °C

    Graphics

    Dell S2417DG 2560x1440@144Hz

    Dell S2417DG 2560x1440@144Hz

    4095MB NVIDIA GeForce RTX 3090 EVGA 24 °C

    Storage

    1863GB Samsung SSD 970 EVO Plus 2TB Unknown SSD

    232GB Samsung SSD 970 EVO Plus 250GB Unknown SSD

    :)
     
    Thirtyben, Oct 18, 2020
    #1
  2. THOMASPRISCO
    ThomasPrisco Win User

    LiveKernelEvent 141

    I have been getting LiveKernelEvent 141 in reliability monitor and it causes games to crash. I checked everything with my graphics drivers and disabled other programs. What can I do do fix it?

    Thanks in advance
     
    ThomasPrisco, Oct 18, 2020
    #2
  3. MELIK TECHBUDDY
    Melik TechBuddy Win User
    Melik TechBuddy, Oct 18, 2020
    #3
  4. REGILE REB
    Regile Reb Win User

    LiveKernelEvent 141 error DAILY

    LiveKernelEvents 141 and 117

    Hello,

    One of the possible reasons why you're having this issue is due to video card driver failure. We found a thread with a similar concern. We recommend that you see the answer of
    ZigZag3143 (MS -MVP) on this
    link     to address this matter.

    Let us know what happens after.
     
    Regile Reb, Oct 18, 2020
    #4
Thema:

LiveKernelEvent 141 error DAILY

Loading...

  1. LiveKernelEvent 141 error DAILY - Similar Threads - LiveKernelEvent 141 error

  2. LiveKernelEvent 141 ERROR

    in Windows 10 Gaming
    LiveKernelEvent 141 ERROR: i was playing halo infinite when the game crashed and after a few minutes the computer starts getting sluggish and then eventually freezes Problem Event Name: LiveKernelEventCode: 141Parameter 1: ffffbd860ad29010Parameter 2: fffff80242c960c8Parameter 3: 0Parameter 4: 6054OS...

  3. livekernelevent 141 error

    in Windows 10 BSOD Crashes and Debugging
    livekernelevent 141 error: So i was playing Halo Infinite yesterday and my pc began locking itself. I disabled my laptop's ability to hibernate when plugged in due to low battery and it stopped locking itself. After that I played for a while and the game became static-y, no longer responding as colored...

  4. LiveKernelEvent 141

    in Windows 10 Drivers and Hardware
    LiveKernelEvent 141: Hello everyone, have new pc and clean install windows 10 pro with may 10 update and software for my pc for motherboard, processor and gpu, after playing multiple games AAA games, dota 2 and lol suddenly screen lag and then freeze , when I checked reliability history it...

  5. LiveKernelEvent 141

    in Windows 10 Drivers and Hardware
    LiveKernelEvent 141: Hi, can anyone help me with this hardware problem that keeps on occuring to me? It crashes mk11 whenever I play it and it happens around 30 minutes into a session. Description A problem with your hardware caused Windows to stop working correctly. Problem signature Problem...

  6. LiveKernelEvent 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141: Hello everyone! Since yesterday morning, my pc freezes, presenting a screen full of vertical lines and emitting an annoying sound through the headphones as if the audio track, from Youtube video or videogame, started playing the same note: since I don't get answers through...

  7. LiveKernelEvent 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141: I receive a LiveKernel141 Error when I am gaming. Here is the description via reliability monitor. Description A problem with your hardware caused Windows to stop working correctly. Problem signature Problem Event Name: LiveKernelEvent Code: 141 Parameter 1:...

  8. LiveKernelEvent 141

    in Windows 10 Customization
    LiveKernelEvent 141: I have been getting LiveKernelEvent 141 in reliability monitor and it causes games to crash. I checked everything with my graphics drivers and disabled other programs. What can I do do fix it? Thanks in advance...

  9. LiveKernelEvent 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141: Hello, I am experiencing multiple system crashes a day and I have no idea how to stop them. They happen mostly in one game called "The Hunt Showdown". I've tried reinstalling the game and I reached out to the support of the game but they said they're not qualified to help me...

  10. LiveKernelEvent 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141: Hey people, lately my computer keeps crashing after a livekernelevent 141 hardware failure. When it occurs, both screens go black, I hear still sound for a few seconds, and then my pc reboots. I have already completely reinstalled my video card drivers, and I ran sfc and...

Users found this page by searching for:

  1. livekernelevent 141 ffff9984cc710010