Windows 10: BSOD Bug Check

Discus and support BSOD Bug Check in Windows 10 BSOD Crashes and Debugging to solve the problem; Ever since I installed the Windows 10 1903 update last 6/19/19 my Windows 10 Professional computer has started crashing seemingly at random and always... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by sagittariusVR, Jun 27, 2019.

  1. BSOD Bug Check

    Ever since I installed the Windows 10 1903 update last 6/19/19 my Windows 10 Professional computer has started crashing seemingly at random and always displaying the same BSOD stopCode:


    Before I installed the aforementioned update, I never had any BSOD. Now it crashes to the same BSOD about one to two times per day, never explicitly specifying which driver(s) are to blame.

    I've been trying to track down the problem by installing WinDbg but unfortunately my knowledge on how to use all its power to find the cause of the problem is very limited. The following is what I got from WinDbg (X64) by running an "!analyze -v" command on the latest memory dump of the last BSOD I got. Since I have 32 GB of RAM installed, the dmp file is a whopping 18 GB (I set the dump file mode to "Active memory Dump").

    1: kd> !analyze -v


    * *

    * Bugcheck Analysis *

    * *



    An attempt was made to write to readonly memory. The guilty driver is on the

    stack trace (and is typically the current instruction pointer).

    When possible, the guilty driver's name (Unicode string) is printed on

    the bugcheck screen and saved in KiBugCheckDriver.


    Arg1: ffffe880c13bef04, Virtual address for the attempted write.

    Arg2: 8a00000000200021, PTE contents.

    Arg3: ffffbf054334f720, (reserved)

    Arg4: 000000000000000a, (reserved)

    Debugging Details:



    Key : Dump.Attributes.FilterDumpFile

    Value: 1







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



    SYSTEM_SKU: Default string


    BIOS_VENDOR: American Megatrends Inc.


    BIOS_DATE: 06/28/2018





    Filter Dump

    DUMP_TYPE: 0

    BUGCHECK_P1: ffffe880c13bef04

    BUGCHECK_P2: 8a00000000200021

    BUGCHECK_P3: ffffbf054334f720

    BUGCHECK_P4: a

    CPU_COUNT: 8

    CPU_MHZ: fa8

    CPU_VENDOR: GenuineIntel


    CPU_MODEL: 5e


    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)




    PROCESS_NAME: System



    ANALYSIS_SESSION_TIME: 06-27-2019 08:24:48.0399

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    TRAP_FRAME: ffffbf054334f720 -- (.trap 0xffffbf054334f720)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=ffffe88000000000 rbx=0000000000000000 rcx=ffffe880c13beee0

    rdx=00000000000fffff rsi=0000000000000000 rdi=0000000000000000

    rip=fffff80373b5cfbc rsp=ffffbf054334f8b0 rbp=0000000000000000

    r8=0000000000000000 r9=0000000fffffffff r10=ffffe880013beee0

    r11=fffffff000000000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl zr na po nc


    fffff803`73b5cfbc 66897924 mov word ptr [rcx+24h],di ds:ffffe880`c13bef04=????

    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80373c4f97d to fffff80373bbc8a0


    ffffbf05`4334f538 fffff803`73c4f97d : 00000000`000000be ffffe880`c13bef04 8a000000`00200021 ffffbf05`4334f720 : nt!KeBugCheckEx

    ffffbf05`4334f540 fffff803`73a7ac2a : 8a000000`00200021 00000000`00000003 ffffbf05`4334f680 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a49d

    ffffbf05`4334f580 fffff803`73bca79a : 00000000`00000000 ffffbf05`406f79c0 00000000`00000002 fffff803`73e657f8 : nt!MmAccessFault+0x48a

    ffffbf05`4334f720 fffff803`73b5cfbc : 00000000`00000000 fffff803`00000001 fffff803`73e65240 fffff803`73e65cc0 : nt!KiPageFault+0x35a

    ffffbf05`4334f8b0 fffff803`73b5ccf7 : fffff803`73e65c20 00000000`00000000 ffffe880`013beeb0 00000000`00000f80 : nt!MiUnlinkNumaStandbyPage+0xc8

    ffffbf05`4334f8f0 fffff803`73cd7cd8 : 00000000`00000000 ffffe880`013bee80 ffffd680`00000000 00000000`00000000 : nt!MiRemoveLowestPriorityStandbyPage+0x177

    ffffbf05`4334f990 fffff803`73cd7ee3 : fffff803`73e65240 00000000`00000000 fffff803`00000000 00000000`0000021e : nt!MiPruneStandbyPages+0x250

    ffffbf05`4334fa20 fffff803`73ac4855 : ffffd680`04766040 fffff803`73cd7e50 ffffd68d`25295ce0 fffff803`73e66ee0 : nt!MiRebalanceZeroFreeLists+0x93

    ffffbf05`4334fa70 fffff803`73b2f725 : ffffd680`04766040 00000000`00000080 ffffd68d`252ba040 fffff803`00000001 : nt!ExpWorkerThread+0x105

    ffffbf05`4334fb10 fffff803`73bc3dfa : ffffac81`39020180 ffffd680`04766040 fffff803`73b2f6d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55

    ffffbf05`4334fb60 00000000`00000000 : ffffbf05`43350000 ffffbf05`43349000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a

    THREAD_SHA1_HASH_MOD_FUNC: b179561bcb326c8058e5d68c054c098bd7db2d14

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4b50445c5a1b3919a8b51a86aecd7b0b50a19742

    THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c



    fffff803`73c4f97d cc int 3

    FAULT_INSTR_CODE: cf8b48cc


    SYMBOL_NAME: nt!MiRaisedIrqlFault+12a49d

    FOLLOWUP_NAME: MachineOwner



    STACK_COMMAND: .thread ; .cxr ; kb

    IMAGE_NAME: memory_corruption


    FAILURE_BUCKET_ID: 0xBE_nt!MiRaisedIrqlFault

    BUCKET_ID: 0xBE_nt!MiRaisedIrqlFault

    PRIMARY_PROBLEM_CLASS: 0xBE_nt!MiRaisedIrqlFault

    TARGET_TIME: 2019-06-27T15:19:22.000Z

    OSBUILD: 18362




    SUITE_MASK: 272



    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS


    USER_LCID: 0

    OSBUILD_TIMESTAMP: unknown_date

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

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



    FAILURE_ID_HASH_STRING: km:0xbe_nt!miraisedirqlfault

    FAILURE_ID_HASH: {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}

    Followup: MachineOwner


    sagittariusVR, Jun 27, 2019
  2. cadaveca Win User

    BSOD/BUG Check 04F

    Microsoft says:

    M4 SSD's dropping off of mobos is stability issue, IMHO. I can replicate it, even, it's caused by making Intel MEI unstable, I think. It's not just M4's, either(I have two), you'll find nearly every SDD has one or two users with this problem. What happens, it seems, is TRIM command is sent to SDD, but it's not completed before the system shuts down, and loses power, and the queued command not being resolved causes the drive to disappear from BIOS.

    as to BSOD codes, you can find the full list here. I just looked up your code.:
    cadaveca, Jun 27, 2019
  3. Tatty_One Win User
    BSOD/BUG Check 04F

    The 04F error code is mainly a hardware error, since you have ruled out the ram, I would suggest it's either a HDD or as you mentioned a pagefile error. I would start by enlarging your pagefile to a fixed (set at min and max) 8096GB and test from there, you may find that solves your problem, as you multitask, open and close different apps the pagefile is just not clearing fast enough.

    If that fails to do the job, I would suggest downloading a free HDD error checking utility, there are a few out there and many are better than the Windows offerings and give that a run and see if it comes up with anything.
    Tatty_One, Jun 27, 2019
  4. BSOD Bug Check

    Taskbar bug: switching to another window -will not appear at the front

    Follow either of these steps to fix the issue with the Active window hiding behind.

    Method 1:
    I suggest you to disable window by hovering over it with the mouse and check if it helps. To do so I suggest you to try the below given steps and check if it helps:

    1. Press Windows key + X key and click on Control Panel.
    2. Select or click Ease of Access.
    3. Click or tap onEase of Access Centre.
    4. Click on Make the Mouse Easier to Use was uncheck Activate Window by hovering over it with the mouse.
    5. Check if issue is resolved.
    Method 2:
    I would suggest you to completely uninstall the touchpad driver and reinstall it. Kindly follow the below given steps.

    1. Press “Windows key + X” and click on “Device Manager”.
    2. In the list of devices, you should see the touchpad drivers.
    3. Right click on the device and then select "Uninstall".
    4. In the uninstall dialog, make sure you select the option to delete the driver package from the system. This causes the driver package installed earlier to be deleted.
    5. In the Action menu of Device manager, select “Scan for Hardware changes” option. This will cause the device driver to be reinstalled. Once the driver is installed, close all windows and restart the computer.
    ChojiTiger, Jun 27, 2019

BSOD Bug Check

  1. BSOD Bug Check - Similar Threads - BSOD Bug Check

  2. Bug Check crashes.

    in Windows 10 BSOD Crashes and Debugging
    Bug Check crashes.: Hey guys, just noticed of late that my computer had been turning off and not going to sleep some days. checked the reliability logs and turns out the system is crashing to a bug check? This is the only information its giving me: Description The computer has rebooted...
  3. Random BSOD On Burst With Different Bug Check

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD On Burst With Different Bug Check: Hi, recently, I have been getting random BSOD on a burst. The laptop would randomly crashes one time and crashes again soon later, and then goes on working fine for the next 4 - 5 days without issues. Then after a period of time it would happen again. I have ran checkdisk...
  4. BSOD Bug Check Code 0x00000133 ntoskrnl.exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bug Check Code 0x00000133 ntoskrnl.exe: Recently I have been getting BSOD's. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 0x0000000000000001, 0x0000000000001e00, 0xfffff80153373358, 0x0000000000000000. A dump was saved in: C:\Windows\Minidump\071320-12750-01.dmp. Report Id:...
  5. Bug in installer checking

    in Windows 10 Installation and Upgrade
    Bug in installer checking: Hi trying to update from W7 ultimate to W10 pro I get for the installer check that 2 files must be uninstalled when searching the registry with Regseeker there are no results and searching thru the registry no results also. Is there a way to reset the installer ? (I've tryed...
  6. bug check 1001

    in Windows 10 BSOD Crashes and Debugging
    bug check 1001: hola recientemente se me esta apagando la computadora repentinamente y no se el motivo, fui a VISOR DE EVENTOS y me sale entre otros errores este bugcheck 1001 El equipo se reinició después de una comprobación de errores. La comprobación de errores fue: 0x00000050...
  7. BSOD Bug Check - Need help analyzing minidumps

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bug Check - Need help analyzing minidumps: Ever since I installed the Windows 10 1903 update last 6/19/19 my Windows 10 Professional computer has started crashing seemingly at random and always displaying the same BSOD stopCode: ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) Before I installed the aforementioned update, I...
  8. Bug check help

    in Windows 10 BSOD Crashes and Debugging
    Bug check help: Hi, As I am almost at my wits end I have succumbed to Forum help. Here is the low-down: All was working fine until last Thursday so I've spend the last few days checking out various BSOD. My Mini-ITX build was working very well (including saving out large 12GB PSB files). I...
  9. BSOD - Multiple error codes/bug checks

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Multiple error codes/bug checks: Attached is my dmp file. This has been happening for months. I reformatted/upgraded my PC recently to Windows 10, which leads me to believe that it shouldn't be a driver issue (I assume it's probably a hardware issue) But I was hoping you guys could help me pin point what it...
  10. BSOD Bug Check Code Reference

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bug Check Code Reference: *Arrow Bug Check Code Reference | Microsoft Docs 108432