Windows 10: Ntoskrnl.exe BSOD fault, at least one per day. No particular or obvious trigger

Discus and support Ntoskrnl.exe BSOD fault, at least one per day. No particular or obvious trigger in Windows 10 BSOD Crashes and Debugging to solve the problem; ******************************************************************************* *... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Customcrust, Jun 8, 2020.

  1. CUSTOMCRUST
    Customcrust Win User

    Ntoskrnl.exe BSOD fault, at least one per day. No particular or obvious trigger


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

    CRITICAL_STRUCTURE_CORRUPTION 109
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1 A driver has inadvertently or deliberately modified critical kernel code
    or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2 A developer attempted to set a normal kernel breakpoint using a kernel
    debugger that was not attached when the system was booted. Normal breakpoints,
    "bp", can only be set if the debugger is attached at boot time. Hardware
    breakpoints, "ba", can be set at any time.
    3 A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a39fd65dfd28d643, Reserved
    Arg2: b3b6e2e44fa71ee9, Reserved
    Arg3: fffff8003aeffde0, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
    8 : Object type
    9 : A processor IVT
    a : Modification of a system service function
    b : A generic session data region
    c : Modification of a session function or .pdata
    d : Modification of an import table
    e : Modification of a session import table
    f : Ps Win32 callout modification
    10 : Debug switch routine modification
    11 : IRP allocator modification
    12 : Driver call dispatcher modification
    13 : IRP completion dispatcher modification
    14 : IRP deallocator modification
    15 : A processor control register
    16 : Critical floating point control register modification
    17 : Local APIC modification
    18 : Kernel notification callout modification
    19 : Loaded module list modification
    1a : Type 3 process list corruption
    1b : Type 4 process list corruption
    1c : Driver object corruption
    1d : Executive callback object modification
    1e : Modification of module padding
    1f : Modification of a protected process
    20 : A generic data region
    21 : A page hash mismatch
    22 : A session page hash mismatch
    23 : Load config directory modification
    24 : Inverted function table modification
    25 : Session configuration modification
    26 : An extended processor control register
    27 : Type 1 pool corruption
    28 : Type 2 pool corruption
    29 : Type 3 pool corruption
    2a : Type 4 pool corruption
    2b : Modification of a function or .pdata
    2c : Image integrity corruption
    2d : Processor misconfiguration
    2e : Type 5 process list corruption
    2f : Process shadow corruption
    30 : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

    Debugging Details:
    ------------------

    *** WARNING: Unable to verify timestamp for win32k.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 5

    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-6QMMSG6

    Key : Analysis.DebugData
    Value: CreateObject

    Key : Analysis.DebugModel
    Value: CreateObject

    Key : Analysis.Elapsed.Sec
    Value: 5

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 75

    Key : Analysis.System
    Value: CreateObject


    BUGCHECK_CODE: 109

    BUGCHECK_P1: a39fd65dfd28d643

    BUGCHECK_P2: b3b6e2e44fa71ee9

    BUGCHECK_P3: fffff8003aeffde0

    BUGCHECK_P4: 1

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: csrss.exe

    STACK_TEXT:
    ffffd08f`96724e98 00000000`00000000 : 00000000`00000109 a39fd65d`fd28d643 b3b6e2e4`4fa71ee9 fffff800`3aeffde0 : nt!KeBugCheckEx


    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8003af000e0-fffff8003af000e3 4 bytes - nt!EtwpGetAutoLoggerLevelKwFilter+300
    [ 24 28 01 e8:90 22 84 11 ]
    fffff8003af000e7 - nt!EtwpGetAutoLoggerLevelKwFilter+307 +0x07
    [ ff:df ]
    5 errors : !nt fffff8003af000e0-fffff8003af000e7

    SYMBOL_NAME: nt!EtwpGetAutoLoggerLevelKwFilter+0

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.18362.836

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 0

    FAILURE_BUCKET_ID: 0x109_1_nt!EtwpGetAutoLoggerLevelKwFilter

    OS_VERSION: 10.0.18362.1

    BUILDLAB_STR: 19h1_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {5d3bc76c-14e4-e42f-b94d-f0702ecccd0b}

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



    Here is the dump analysis for the most recent crash. Happens at any state of operation, if computer is sitting idle or running a program. If there is anyone who can help it would be much appreciated. New PC build.



    just based of a little bit of reading similar problems i have tried:

    updating all drivers. have updated chipset drivers. havent updated bios yet. have disabled c-states in bios. t


    ASUS x570 prime mobo

    2x corsair vengeance rgb pro 16gb 3200mhz RAM

    amd ryzen 7 3700x

    h100i rgb platinum cpu cooler

    zotac gtx 2060 super amp extreme

    boots from crucial m.2 1tb ssd

    650W silverstone PSU

    :)
     
    Customcrust, Jun 8, 2020
    #1
  2. LEWISH95
    LewisH95 Win User

    Ntoskrnl BSOD

    • Update your Realtek audio driver.
    • Update your computer.
    • Disable overclocking settings.
    • Turn off BlueStacks/ another Android emulator.
    • Clean your registry.
    • Check your disk for errors.
    • Fix bad memory issues.
    • Remove faulty sticks of RAM.
    • I hope these methods help you!
    • Regards,
    • Lewis

      * Added by Moderator: Information from
      https://windowsreport.com/windows-8-bsod-ntoskrnl-exe/

      * Moderator note: Advice given on this page might or might not be safe and/or effective but there are programs usually classified as PUP's (Potentially Unwanted Programs) being pushed that should not be downloaded or installed.
     
    LewisH95, Jun 8, 2020
    #2
  3. MARITZACAPIRO
    MaritzaCapiro Win User
    BSOD ntoskrnl..exe+1b35e0

    Hi, KirbyBakken

    My name is Maritza and I am an Independent Advisor. I would be happy to help you today.

    Check this link, I hope it helps

    https://www.thewindowsclub.com/ntoskrnl-exe-hig...

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
    on the site before you decide to download and install it.

    Let us know if these steps help you to resolve the issue.
     
    MaritzaCapiro, Jun 8, 2020
    #3
  4. REUCUS
    Reucus Win User

    Ntoskrnl.exe BSOD fault, at least one per day. No particular or obvious trigger

    BSOD with no obvious trigger

    I've been getting Blue Screens of Death lately without any apparent trigger.

    They're always DRIVER_IQRL_NOT_LESS_OR_EQUAL but my PC reboots before I'm able to write down all the BSOD details.

    I've tried looking through the Event Viewer log, but I have neither the knowledge nor the experience to understand the logged entries. As this is my first time on the Microsoft board, I can't seem to figure out how to attach the Event Viewer log either.
    Any assistance would be greatly appreciated.
     
    Reucus, Jun 8, 2020
    #4
Thema:

Ntoskrnl.exe BSOD fault, at least one per day. No particular or obvious trigger

Loading...

  1. Ntoskrnl.exe BSOD fault, at least one per day. No particular or obvious trigger - Similar Threads - Ntoskrnl exe BSOD

  2. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...

  3. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...

  4. BSOD per day

    in Windows 10 BSOD Crashes and Debugging
    BSOD per day: 070321-8953-01.dmp - Google Drive i try to use v2 log collector,however,there is a error message in cmd : Get-MpPreference : The term 'Get-MpPreference' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or...

  5. Always get BSOD at least once per day! Help Please!!

    in Windows 10 BSOD Crashes and Debugging
    Always get BSOD at least once per day! Help Please!!: I always get BSOD at lease once per day! Based on WinDbg, I've uninstall rainmeter, Nvidia Geforce Experience, and Asus Armoury Crate, but the result still the same!! I even has replaced my Memory and PSU, the result still the same!! : I already run Windows Memory...

  6. BSoD once at least every day

    in Windows 10 BSOD Crashes and Debugging
    BSoD once at least every day: My PC blue screens randomy at least once a day, i checked the eroor in computer managment and its all the same. The BSoD error messages vary from IRQL_not_LESS_OR_EQUAL to System service exception to apc index mismatch. I have tested the memory with memtest and the windows...

  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...

  8. Almost reproducible BSOD triggered by fault in cldflt.sys

    in Windows 10 BSOD Crashes and Debugging
    Almost reproducible BSOD triggered by fault in cldflt.sys: Since few days I'm frequently experiencing BSOD crashes while running/debugging a Python application. The crash usually occurs immediately at launch of the Python program. This is almost reproducible as it happens around 1 in 5 times. The minidump analysis always looks the...

  9. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...

  10. BSOD with no obvious trigger

    in Windows 10 BSOD Crashes and Debugging
    BSOD with no obvious trigger: I've been getting Blue Screens of Death lately without any apparent trigger. They're always DRIVER_IQRL_NOT_LESS_OR_EQUAL but my PC reboots before I'm able to write down all the BSOD details. I've tried looking through the Event Viewer log, but I have neither the...