Windows 10: Constants BSOD's on Windows 10

Discus and support Constants BSOD's on Windows 10 in Windows 10 BSOD Crashes and Debugging to solve the problem; This is happening many times, a lot. Here one of the lasts dumps: Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64 Copyright (c)... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Soto1978, Jul 12, 2019 at 9:57 PM.

  1. Soto1978 Win User

    Constants BSOD's on Windows 10

    This is happening many times, a lot.

    Here one of the lasts dumps:

    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\minidump\071219-20328-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 18362 MP (12 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 18362.1.amd64fre.19h1_release.190318-1202

    Machine Name:

    Kernel base = 0xfffff806`2b000000 PsLoadedModuleList = 0xfffff806`2b4432f0

    Debug session time: Fri Jul 12 16:28:16.500 2019 (UTC - 4:00)

    System Uptime: 0 days 0:15:28.258

    Loading Kernel Symbols





    Loading User Symbols

    Loading unloaded module list


    For analysis of this file, run !analyze -v

    9: kd> !analyze -v


    * *

    * Bugcheck Analysis *

    * *



    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high. This is usually

    caused by drivers using improper addresses.

    If a kernel debugger is available get the stack backtrace.


    Arg1: 00000000000000ab, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, bitfield :

    bit 0 : value 0 = read operation, 1 = write operation

    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

    Arg4: fffff8062b113aea, address which referenced memory

    Debugging Details:


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








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

    DUMP_TYPE: 2

    BUGCHECK_P1: ab

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff8062b113aea

    READ_ADDRESS: fffff8062b56e3b0: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd





    fffff806`2b113aea 80b9ba00000002 cmp byte ptr [rcx+0BAh],2

    CPU_COUNT: c

    CPU_MHZ: e70

    CPU_VENDOR: GenuineIntel


    CPU_MODEL: 9e





    PROCESS_NAME: System


    ANALYSIS_SESSION_TIME: 07-12-2019 17:44:31.0417

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    TRAP_FRAME: ffff94047e76a4e0 -- (.trap 0xffff94047e76a4e0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=7fffce9268000000 rbx=0000000000000000 rcx=fffffffffffffff1

    rdx=ffff94047e76a6c0 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8062b113aea rsp=ffff94047e76a678 rbp=0000000000000000

    r8=0000000000010c68 r9=000000000000195a r10=0000000000000001

    r11=ffffb20503544dc0 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl nz na po cy


    fffff806`2b113aea 80b9ba00000002 cmp byte ptr [rcx+0BAh],2 ds:00000000`000000ab=??

    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8062b1ce6e9 to fffff8062b1bc900


    ffff9404`7e76a398 fffff806`2b1ce6e9 : 00000000`0000000a 00000000`000000ab 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

    ffff9404`7e76a3a0 fffff806`2b1caa2b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

    ffff9404`7e76a4e0 fffff806`2b113aea : fffff806`2b1139df 00000000`00000009 ffffb204`f603f490 00000000`00000006 : nt!KiPageFault+0x46b

    ffff9404`7e76a678 fffff806`2b1139df : 00000000`00000009 ffffb204`f603f490 00000000`00000006 00000000`00000000 : nt!MiUpdateClaimDistribution+0xa

    ffff9404`7e76a680 fffff806`2b0b123d : 00000000`001c5396 ffffb204`f603f490 00000000`00000000 ffff9404`7e76a950 : nt!MiComputeAgeDistribution+0x83

    ffff9404`7e76a720 fffff806`2b0b273c : 00000000`00000000 ffff9404`7e76a950 00000000`00000000 00000000`00000000 : nt!MiComputeSystemTrimCriteria+0x301

    ffff9404`7e76a780 fffff806`2b0b0ce0 : fffff806`00000002 fffff806`00000000 00000000`00000000 ffffb204`f603f490 : nt!MiProcessWorkingSets+0x6c

    ffff9404`7e76a930 fffff806`2b2c72a6 : fffff806`2b570cc0 00000000`00000001 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xc8

    ffff9404`7e76a9f0 fffff806`2b187fb5 : 00000000`ffffffff 00000000`00000000 fffff806`2b4651c0 00000000`0000014a : nt!MmWorkingSetManager+0x12

    ffff9404`7e76aa20 fffff806`2b12f725 : ffffb204`f60a2040 00000000`00000080 fffff806`2b187e60 00000000`00000000 : nt!KeBalanceSetManager+0x155

    ffff9404`7e76ab10 fffff806`2b1c3e6a : ffffa181`fe600180 ffffb204`f60a2040 fffff806`2b12f6d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55

    ffff9404`7e76ab60 00000000`00000000 : ffff9404`7e76b000 ffff9404`7e764000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a

    THREAD_SHA1_HASH_MOD_FUNC: 73d62b4574969cf1909c2a0f318aa5a72d788962

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: edce3b34cba864b4f53828c27a9a300fd2739f15

    THREAD_SHA1_HASH_MOD: dc844b1b94baa204d070855e43bbbd27eee98b94



    fffff806`2b113aea 80b9ba00000002 cmp byte ptr [rcx+0BAh],2

    FAULT_INSTR_CODE: bab980


    SYMBOL_NAME: nt!MiUpdateClaimDistribution+a

    FOLLOWUP_NAME: MachineOwner



    IMAGE_VERSION: 10.0.18362.239

    STACK_COMMAND: .thread ; .cxr ; kb

    IMAGE_NAME: memory_corruption


    FAILURE_BUCKET_ID: AV_nt!MiUpdateClaimDistribution

    BUCKET_ID: AV_nt!MiUpdateClaimDistribution

    PRIMARY_PROBLEM_CLASS: AV_nt!MiUpdateClaimDistribution

    TARGET_TIME: 2019-07-12T20:28:16.000Z

    OSBUILD: 18362




    SUITE_MASK: 272



    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS


    USER_LCID: 0

    OSBUILD_TIMESTAMP: 1972-02-02 03:33:06

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

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



    FAILURE_ID_HASH_STRING: km:av_nt!miupdateclaimdistribution

    FAILURE_ID_HASH: {7c92b2df-2a74-4ca9-dcc4-665e1aa7bc54}

    Followup: MachineOwner


  2. Dyan Rey Win User

    KernelBase.dll is broken constant BSOD's constant game crashing.

    Hi Darry,

    User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
    System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

    To create a user profile, follow these steps:

    • Go to Settings. Click Accounts.
    • Select Family & other people.
    • Select the Add someone else to this PC tab.
    • Name the user as Test.
    • Leave the password field blank.
    • Hit Next.
    • Sign in as Test user.

    You may also check this link
    to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.
  3. bkconn Win User
    Constant BSOD even after fresh install

    Step 19. Done

    Constants BSOD's on Windows 10 [​IMG]

    Step 20. Done in the first post.

    Step 21. Done.

    Constants BSOD's on Windows 10 [​IMG]
  4. bkconn Win User

    Constants BSOD's on Windows 10

    Constant BSOD even after fresh install

    Step 16. Restore Point has been turned on and created for drive C:

    Constants BSOD's on Windows 10 [​IMG]

    Step 17. I do not have Ccleaner installed

    Step 18. Speedfan

    Constants BSOD's on Windows 10 [​IMG]

Constants BSOD's on Windows 10

  1. Constants BSOD's on Windows 10 - Similar Threads - Constants BSOD's

  2. Constant BSODS - help PLEASE

    in Windows 10 BSOD Crashes and Debugging
    Constant BSODS - help PLEASE: lots of dump files - really would be grateful for some tech guidance. thanks - Tony Dovale - South Africa...
  3. Windows 10 Constant BSODs

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 Constant BSODs: Basically, I have assembled a PC from mostly used parts (just for productivity purposes. Not gaming or heavy editing) and installed Windows 10 pro onto the system. However, Every so often it Blue screens with a variety of stop codes (DRIVER IRQL_LESS_OR_NOT_EQUAL,...
  4. Constant bsod crashes ntoskrnl.exe cdd.dll

    in Windows 10 BSOD Crashes and Debugging
    Constant bsod crashes ntoskrnl.exe cdd.dll: Constant bsod crashes, been running round for weeks trying to find a fix and I'm now on my last legs, any help appreciated. Logs attached DESKTOP-CP7A9CQ-(2019-06-24_12-34-46).zip 135387
  5. Windows 10 1903 update - Nothing, but constant BSODs

    in Windows 10 Drivers and Hardware
    Windows 10 1903 update - Nothing, but constant BSODs: Hello everyone. 2-3 weeks ago, I bought new parts for my PC, with which I went from Intel to AMD. After installing the parts, I did not reinstall Windows as at that time I didn't have a USB drive to do it with, so I just let the PC be like it is. It was fine, everything...
  6. Constant BSODs (error codes in post)

    in Windows 10 BSOD Crashes and Debugging
    Constant BSODs (error codes in post): Bit of a long story... Posting on behalf of a friend. Just before Christmas my mates PC started acting up. He began to get random BSOD's (we couldn't find any way to trigger it or repeat the errors, it all appears random) . It kept getting worse and got to the point where he...
  7. Win 10 backgroundTaskHost.exe crashed - Constant BSOD when idle

    in Windows 10 BSOD Crashes and Debugging
    Win 10 backgroundTaskHost.exe crashed - Constant BSOD when idle: Hi, Ever since i have purchased my computer a few months ago i'm having BSODs They can occur between every couple of days and a couple of times per day if left idle and perhaps plugged. Most commonly when idle i come back to the BSOD with error:...
  8. Constant BSOD (before or seconds after login in) 0xA ntkrnlmp.exe

    in Windows 10 BSOD Crashes and Debugging
    Constant BSOD (before or seconds after login in) 0xA ntkrnlmp.exe: Hello everyone, My computer undergoes constant BSOD IRQL_NOT_LESS_OR_EQUAL 0xA, either before login in or less than 3 minutes after. The minidump files always point to ntkrnlmp.exe with either nt!KiSystemServiceExit, nt!KiSystemCall64ShadowCommon or...
  9. Constant BSOD IRQL_Not_Equal_Or_Less crashes

    in Windows 10 BSOD Crashes and Debugging
    Constant BSOD IRQL_Not_Equal_Or_Less crashes: Hello, I've been having constant BSOD level crashes while playing video games. I suspect one or more pieces of my hardware are failing (my computer build is 7 years old now and have only replaced the GPU now and again), but I want to rule out any software issues that I can....
  10. New PC. Constant BSODs as I'm installing Win10

    in Windows 10 BSOD Crashes and Debugging
    New PC. Constant BSODs as I'm installing Win10: I'm going crazy troubleshooting for the past 3 days. I just bought PC parts and built it myself. I used the windows media creation tool to copy a real version of windows from my laptop to a thumb drive. Everything about the PC hardware wise seems to run fine. I've been...