Windows 10: LiveKernelEvent 141

Discus and support LiveKernelEvent 141 in Windows 10 Drivers and Hardware to solve the problem; 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... Discussion in 'Windows 10 Drivers and Hardware' started by AliBoHamad1, Jun 8, 2020.

  1. 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 listed a hardware fail event, livekernelevent code 141 , not once maybe 12 time.


    run a disk check, check memory, underclock my gpu, set my fan at max, uninstalling my gpu with and without ddu , oc my cpu, uc and even disable all startup app and the code comeback no matter what.


    now after playing 2 custom game the error come again with event id 2 and 3.


    Relevant info:

    Motherboard : a msi a pro x570 with the latest bios

    CPU : AMD 3700x no oc at all

    GPU : RTX 2070 super ventos oc Latest Nvidia drivers 446.14

    SSD : is Samsung 970 evo plus 1TB

    PSU : Thermaltake Toughpower Grand RGB 850W Gold Fully Modular

    RAM : 16gb G.Skill 3600MHz cl19Windows 10 pro Version 2004 OS build 1941.264 Latest updates


    Description

    A problem with your hardware caused Windows to stop working correctly.



    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 141

    Parameter 1: ffffd70905810460

    Parameter 2: fffff8058aae2610

    Parameter 3: 0

    Parameter 4: 2550

    OS version: 10_0_19041

    Service Pack: 0_0

    Product: 256_1

    OS Version: 10.0.19041.2.0.0.256.48

    Locale ID: 1033



    Extra information about the problem

    Bucket ID: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown

    Server information: 49305239-259f-4253-a140-59054a9ccfaa






    And for dump file name memory.dump






    Microsoft 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 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff806`1c200000 PsLoadedModuleList = 0xfffff806`1ce2a250Debug session time: Mon Jun 8 13:49:32.843 2020 UTC + 3:00System Uptime: 0 days 16:32:53.482Loading Kernel Symbols.....................................................................Page 10b76d not present in the dump file. Type ".hh dbgerr004" for details...............................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 00000000`01062018. Type ".hh dbgerr001" for detailsLoading unloaded module list.................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff806`1c5dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9505`93539f90=000000000000001a14: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************MEMORY_MANAGEMENT 1a # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE.Arg2: ffffb80000008028Arg3: 0000000000200000Arg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-46O5G3P Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 9 Key : Analysis.Memory.CommitPeak.Mb Value: 65 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 1aBUGCHECK_P1: 41792BUGCHECK_P2: ffffb80000008028BUGCHECK_P3: 200000BUGCHECK_P4: 0MEMORY_CORRUPTOR: ONE_BITBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: MSI.True Color.exeSTACK_TEXT: ffff9505`93539f88 fffff806`1c65418e : 00000000`0000001a 00000000`00041792 ffffb800`00008028 00000000`00200000 : nt!KeBugCheckExffff9505`93539f90 fffff806`1c4c215f : ffffe30f`11eba700 00000000`01000000 ffffb800`00000002 ffff9505`9353a180 : nt!MiDeleteVa+0x191e6effff9505`9353a080 fffff806`1c4a787f : 00000000`00000000 00000000`00000060 ffffe30f`11eba7c0 ffffe30f`10baf2c0 : nt!MiDeletePagablePteRange+0x31fffff9505`9353a500 fffff806`1c866a13 : ffffe30f`11eba080 00000000`00000000 ffffe30f`00000000 ffffe30f`00000001 : nt!MiDeleteVad+0x41fffff9505`9353a630 fffff806`1c8678b3 : ffffe30f`114d6e70 ffffe30f`114d6e70 ffffe30f`114d62e0 ffffe30f`11eba080 : nt!MiCleanVad+0x43ffff9505`9353a660 fffff806`1c8b9e87 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffe30f`11eba080 : nt!MmCleanProcessAddressSpace+0x137ffff9505`9353a6e0 fffff806`1c7e8c32 : ffffe30f`11eba080 ffffcb02`05e207f0 ffff9505`9353a920 00000000`00000000 : nt!PspRundownSingleProcess+0x13bffff9505`9353a760 fffff806`1c8f4c98 : 00000000`40010004 00000000`00000001 00000000`00000000 00000000`0108b000 : nt!PspExitThread+0x5f6ffff9505`9353a860 fffff806`1c42a4e7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38ffff9505`9353a8a0 fffff806`1c5e1fc0 : 00000000`0636fec8 ffff9505`9353a950 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x487ffff9505`9353a950 fffff806`1c5ef41f : 00000000`00000001 ffff9505`9353ab80 00000000`0626fda0 ffffe30f`0d8b21c0 : nt!KiInitiateUserApc+0x70ffff9505`9353aa90 00007ffb`c6419004 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f00000000`0626e708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`c6419004MODULE_NAME: hardwareIMAGE_NAME: memory_corruptionSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BITOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}Followup: MachineOwner---------





    And this file for event viewer


    https://1drv.ms/u/s!Arb0CMfONSDLiVUZuZx_zBTCgH9W?e=x5WBPR


    need help <3

























    :)
     
    AliBoHamad1, Jun 8, 2020
    #1

  2. 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, Jun 8, 2020
    #2
  3. 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, Jun 8, 2020
    #3
  4. LiveKernelEvent 141

    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 Event Name: LiveKernelEvent
    Code: 141
    Parameter 1: ffffc40436750010
    Parameter 2: fffff8063f6db938
    Parameter 3: 0
    Parameter 4: 0
    OS version: 10_0_18363
    Service Pack: 0_0
    Product: 768_1
    OS Version: 10.0.18363.2.0.0.768.100
    Locale ID: 13321

    Extra information about the problem
    Bucket ID: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown
    Server information: 8fd09d68-57b6-48e3-88bf-18ca23387fab
     
    Enrico B.de Guzman, Jun 8, 2020
    #4
Thema:

LiveKernelEvent 141

Loading...
  1. LiveKernelEvent 141 - Similar Threads - LiveKernelEvent 141

  2. I keep crashing, and getting LiveKernelEvent 117, 133, 141, 193

    in Windows 10 BSOD Crashes and Debugging
    I keep crashing, and getting LiveKernelEvent 117, 133, 141, 193: I have had these issues for a while and manufacturer isn't much help. can someone help me what does this mean? Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: Fault bucket...
  3. LiveKernelEvent 117 & 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 117 & 141: My PC is having critical errors whereby the screen flickers and after which, the computer often reboots. On reliability monitor is gives a couple of critical errors, both code 117 and 141. The PC is only a couple months old, drivers have been reinstalled, memory check...
  4. LiveKernelEvent 141, 171, Display 4101 Display driver amdkmdag stopped responding and has...

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141, 171, Display 4101 Display driver amdkmdag stopped responding and has...: I am having crashes when I am playing Assassin's Creed Valhalla. The screen goes black, then the application closes and windows doesn't crash. I already clean installed Windows 10 twice and used DDU to install AMD drivers, however the issue persists. This PC is new, 2 months...
  5. Windows LiveKernelEvent 141 and game crashing

    in Windows 10 BSOD Crashes and Debugging
    Windows LiveKernelEvent 141 and game crashing: Hello, I am having a persistent problem that started several months ago. I have attempted to fix the issue but it persists no matter what I do. The issue is crashing in certain games with no error message or BSOD. The game will just freeze, requiring me to exit manually...
  6. LiveKernelEvent Code 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent Code 141: LiveKernelEvent Code: 141 Parameter 1: ffffbb0ad3acf010 Parameter 2: fffff8038d6571c0 Parameter 3: 0 Parameter 4: 1004 OS version: 10_0_18363 Service Pack: 0_0 Product: 256_1 OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 1033 This doesn't seem to be triggerable or...
  7. Constant LiveKernelEvent 141 and 117 crashes

    in Windows 10 BSOD Crashes and Debugging
    Constant LiveKernelEvent 141 and 117 crashes: Over Christmas I did some PC upgrades and since I have been experiencing constant crashes during GPU 'stressing' gameplay or data plotting on MATLAB. Original upgrades included MSI MAG b550m Mortar Wifi mobo, ram and cpu. The crashes kernel 117 would occur as a frozen screen,...
  8. Computer black screen and restarting randomly LiveKernelEvent 141 and 117

    in Windows 10 BSOD Crashes and Debugging
    Computer black screen and restarting randomly LiveKernelEvent 141 and 117: Hi just started happening and not sure what caused it or how to resolve it. When looking at the problem details it comes up with this. Description A problem with your hardware caused Windows to stop working correctly. Problem signature Problem Event Name:...
  9. LiveKernelEvent 141, BSODs + Fuzzy Blue/Red Squares Crash

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141, BSODs + Fuzzy Blue/Red Squares Crash: Hi there, Last summer I upgraded from an MSI GTX 750 Ti to an MSI GTX 980 Ti. I'm running an Intel Core i7-4770 CPU with a Gigabyte H87M-HD3 Motherboard. I have 16GB of DDR3 RAM. Since that time, I have been experiencing intermittent crashes where blue squares appear...
  10. LiveKernelEvent Code:141 Hardware error

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent Code:141 Hardware error: Hi, a week or so ago, while I was playing a game, my screen turned black and the sound got stuck or something like that I dont know how to describe it. It stayed like that for a few seconds and then my laptop rebooted. When I checked the Reliability Monitor I found the...