Windows 10: BSoD error in windows 10 pro 1903

Discus and support BSoD error in windows 10 pro 1903 in Windows 10 BSOD Crashes and Debugging to solve the problem; Unexpected BSoD occurred for 3-4 times continuously. The analysis report of dump is below. Please help me to troubleshoot the error. I have updated the... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Krishnakumar P, Jun 27, 2019.

  1. BSoD error in windows 10 pro 1903


    Unexpected BSoD occurred for 3-4 times continuously. The analysis report of dump is below. Please help me to troubleshoot the error. I have updated the windows version a week before from 1809 to 1903 and installed audio driver (realtek) as it was automatically uninstalled after update.


    UNEXPECTED_STORE_EXCEPTION (154)

    The store component caught an unexpected exception.
    Arguments:
    Arg1: ffff858c67f81000, Pointer to the store context or data manager
    Arg2: ffff960705a366e0, Exception information
    Arg3: 0000000000000001, Reserved
    Arg4: 0000000000000000, Reserved

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

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

    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

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

    SYSTEM_MANUFACTURER: KBS

    SYSTEM_PRODUCT_NAME: Attitude

    SYSTEM_SKU: To Be Filled By O.E.M.

    SYSTEM_VERSION: Gen6.1

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: L7.11B

    BIOS_DATE: 08/11/2017

    BASEBOARD_MANUFACTURER: KBS-OEM

    BASEBOARD_PRODUCT: H110M-HDVP

    BASEBOARD_VERSION:

    DUMP_TYPE: 2

    BUGCHECK_P1: ffff858c67f81000

    BUGCHECK_P2: ffff960705a366e0

    BUGCHECK_P3: 1

    BUGCHECK_P4: 0

    EXCEPTION_RECORD: ffff960705a37688 -- (.exr 0xffff960705a37688)
    ExceptionAddress: fffff8054b05a4cd (nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0x0000000000112211)
    ExceptionCode: c0000420 (Assertion failure)
    ExceptionFlags: 00000000
    NumberParameters: 0
    Assertion: (((NTSTATUS)(Status)) >= 0)

    EXCEPTION_CODE: (NTSTATUS) 0xc0000420 - An assertion failure has occurred.

    FAULTING_IP:
    nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+112211
    fffff805`4b05a4cd cd2c int 2Ch

    FOLLOWUP_IP:
    nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+112211
    fffff805`4b05a4cd cd2c int 2Ch

    EXCEPTION_PARAMETER1: 000000006e62ce4b

    EXCEPTION_PARAMETER2: 0000000000000006

    BUGCHECK_STR: 0x154_c0000420

    CONTEXT: ffff960705a36ed0 -- (.cxr 0xffff960705a36ed0)
    rax=00000000c0000225 rbx=ffff858c67f810e8 rcx=ffff858c6d202000
    rdx=0000000000000502 rsi=0000000000000000 rdi=ffff858c67f81050
    rip=fffff8054b05a4cd rsp=ffff960705a378c0 rbp=ffff858c67f810d0
    r8=0000000000000681 r9=000000006e62ce4b r10=0000000000000006
    r11=000000000000000a r12=ffff858c662e6be8 r13=0000000000000000
    r14=00000000000d02fc r15=ffff858c662e6be8
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00040282
    nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0x112211:
    fffff805`4b05a4cd cd2c int 2Ch
    Resetting default scope

    CPU_COUNT: 4

    CPU_MHZ: e70

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    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)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: MemCompression

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000420 - An assertion failure has occurred.

    EXCEPTION_CODE_STR: c0000420

    ANALYSIS_SESSION_HOST: DESKTOP-54BJ7QG

    ANALYSIS_SESSION_TIME: 06-27-2019 10:53:08.0713

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    LAST_CONTROL_TRANSFER: from fffff8054af48656 to fffff8054b05a4cd

    STACK_TEXT:
    ffff9607`05a378c0 fffff805`4af48656 : 00000000`00000000 ffff9607`05a37969 ffff858c`67f81050 ffff858c`000d02fc : nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0x112211
    ffff9607`05a37900 fffff805`4af4988d : 00000000`00000000 ffff858c`760f8cd0 00000000`00000000 fffff805`4ae5aebb : nt!ST_STORE<SM_TRAITS>::StDmPageRemove+0x202
    ffff9607`05a379d0 fffff805`4ae5a6ea : ffff858c`67f81000 ffff9607`05a37a98 00000000`00000001 ffff858c`61ac6080 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0xc1
    ffff9607`05a37a20 fffff805`4ae5c0b1 : 00000000`00000000 ffff858c`00000000 ffff858c`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x12e
    ffff9607`05a37ae0 fffff805`4af30925 : ffff858c`67f81000 fffff805`4ae5c0a0 ffff9607`0593f178 0000246f`b19bbfff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
    ffff9607`05a37b10 fffff805`4afc3d5a : fffff805`4520c180 ffff858c`61ac6080 fffff805`4af308d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffff9607`05a37b60 00000000`00000000 : ffff9607`05a38000 ffff9607`05a31000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


    THREAD_SHA1_HASH_MOD_FUNC: 0e6af0b4bbb2e57dfd411b7bfdeca0366700b50c

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 38834f314fbe69f2ea4a024e8bd30354b07bb9c6

    THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

    FAULT_INSTR_CODE: b0e92ccd

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+112211

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION: 10.0.18362.30

    STACK_COMMAND: .cxr 0xffff960705a36ed0 ; kb

    BUCKET_ID_FUNC_OFFSET: 112211

    FAILURE_BUCKET_ID: 0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

    BUCKET_ID: 0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

    PRIMARY_PROBLEM_CLASS: 0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

    TARGET_TIME: 2019-06-26T04:29:39.000Z

    OSBUILD: 18362

    OSSERVICEPACK: 30

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    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

    ANALYSIS_SESSION_ELAPSED_TIME: 6e2b

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x154_c0000420_nt!st_store_sm_traits_::stdmpagerecordremove

    FAILURE_ID_HASH: {b82a73ea-d098-8451-8193-a5c6604483ac}

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

    :)
     
    Krishnakumar P, Jun 27, 2019
    #1
  2. Kursah Win User

    BSOD - Registry Error

    Your BSOD code is 0X000000051

    Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

    There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

    This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

    +1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

    Run a Diskchk /R (I know you already ran one, so you can skip this)

    Run SFC /SCANNOW

    Report back.
     
    Kursah, Jun 27, 2019
    #2
  3. BitGamerX Win User
    Couple random BSOD on new machine with Windows 10 1903

    I completed my build 3 weeks ago and I've had a couple BSOD. The first BSOD was during a game and I didn't even get a full memory dump. The second one was right at bootup and I did get a memory dump however error was a generic (IRQL_NOT_LESS_OR_EQUAL) error
    which I've listed below. I'm not overclocking anything and I'm using the drivers that were installed with Win10 1903 except for the Radeon driver and the latest AMD Chipset drivers. I've also run multiple passes of memtest86 and Windows Memory Test without
    error. I'm thinking about disabling Windows Fast Startup because I think it might be part of the issue. Any other suggestions of things to look for?

    MiniDump:

    https://www.dropbox.com/sh/fkjykolhdf28p4j/AABXEV-GXxz5GgCWiw94ThNba?dl=0

    Systems Specs

    Ryzen 2700+

    X470 AORUS GAMING 7 WIFI-50-CF

    sapphire Nitro+ Radeon RX 590 8GB

    Viper Steel Series DDR4 32GB (2 x 16GB) 3200MHz Kit

    XPG SX8200 Pro 1TB PCIe Gen3x4 M.2 NVMe

    Windows 10 1903

    BlueScreenView error listing:

    IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffff800c`3ffc7e6a 00000000`00000002 00000000`00000000 fffff801`62def3b5 ntoskrnl.exe ntoskrnl.exe+1bc8a0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.175 (WinBuild.160101.0800)
    x64 ntoskrnl.exe+1bc8a0 C:\Windows\Minidump\061319-8609-01.dm
     
    BitGamerX, Jun 27, 2019
    #3
  4. Ahhzz Win User

    BSoD error in windows 10 pro 1903

    Windows 10 Tweaks

    Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

    Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

    • Open a new Explorer window.
    • Click View in the ribbon.
    • Click Options.
    • Under General, next to “Open File Explorer to:” choose “This PC.”
    • Click OK


    credit to Lifehacker.
     
    Ahhzz, Jun 27, 2019
    #4
Thema:

BSoD error in windows 10 pro 1903

Loading...
  1. BSoD error in windows 10 pro 1903 - Similar Threads - BSoD error pro

  2. Unable to update to Windows 10 Pro, 1903

    in Windows 10 Installation and Upgrade
    Unable to update to Windows 10 Pro, 1903: Trying to update from Windows 10 Pro 1809 to 1903. Receiving error 0x80070003 from Windows Update in the Settings app. Have tried several methods, such as an in-place upgrade, net stop [services], sfc /scannow, DISM, deleting SystemDistribution folder, and even contacting...
  3. Constant, and ever increasing BSOD's on Windows 10 pro x64 1903 0xc00000124

    in Windows 10 BSOD Crashes and Debugging
    Constant, and ever increasing BSOD's on Windows 10 pro x64 1903 0xc00000124: I am getting lots of full BSOD Crashes and it all started after migrating from Windows 7 Pro x64 to Windows 10 Pro x64 This morning I BSOD'd by just using my browser, but it also happens with gaming, VR, using Photoshop, watching videos, listening to music and sometimes even...
  4. Update to Windows 10 Pro Version 1903

    in Windows 10 Installation and Upgrade
    Update to Windows 10 Pro Version 1903: I just updated, I like to wait until the problems have been solved before I do, but I apparently didn't wait long enough... There are no answers yet. I was still having problems after the prior update when I gave up & contacted Support. They told me that version 1903 fixed...
  5. Windows 10 pro with Build 1803 - Error Updating to 1903 - Error 0x80070003

    in Windows 10 Installation and Upgrade
    Windows 10 pro with Build 1803 - Error Updating to 1903 - Error 0x80070003: I have been working for about a day trying to get my computer to update to Windows 10, 1903. I keep getting the error 0x80070003 Tried the following - Ran Windows Update Troubleshooter - Ran reset-windowsupdate.ps1 through Powershell - Ran DISM.exe /Online /Cleanup-image...
  6. Windows 10 Pro 64bit 1903 update

    in Windows 10 Installation and Upgrade
    Windows 10 Pro 64bit 1903 update: Hi there ! I have 2 versions of Windows , Home and Pro. I have upgraded Home version to 1903 with no problems. Windows update recognize update automatically and installed it. While opposite at Pro version. Windows update doesn't find anything. So, i have downloaded...
  7. Error while update Windows 10 Pro Version 1903

    in Windows 10 Installation and Upgrade
    Error while update Windows 10 Pro Version 1903: Hi, Currently I have try to update my Windows 10 Pro to Version 1903 But finally I have and error the detail error is bellow : [ATTACH] The current version of my Windows 10 Pro is 1809, capture bellow : [ATTACH] The my device Model is ASUS X450JF, capture bellow :...
  8. Win 10 Pro Crashed with BSOD error: iaStor.sys

    in Windows 10 Drivers and Hardware
    Win 10 Pro Crashed with BSOD error: iaStor.sys: Hi Im having lots of crashes after upgrading windows with iastor.sys not same or equal. I found this post describing a potential fix for it. https://appuals.com/fix-iastora-sys-blue-screen/ But my computer a DELL T7600 doesnt show the IDE ATA/ATAPI controllers and cant...
  9. BSOD Windows 10 Pro

    in Windows 10 BSOD Crashes and Debugging
    BSOD Windows 10 Pro: Hello every one, I just got new laptop for a week and recently I experienced BSOD repeatedly in WIn 10 64 Pro. Some with BAD_POOL_HEADER and IRQL_NOT_LESS_OR_EQUAL I did update all drivers as recommend, run the mem test and it pass with no fault, here is the dump file...
  10. BSod Windows 10 Pro

    in Windows 10 BSOD Crashes and Debugging
    BSod Windows 10 Pro: I am having a lot of problems with blue screens on a new pc I assembled from parts I bought. Firstly, this is the last event that always happen before a bluescreen: File System Filter 'npsvctrig' (10.0, ‎2015‎-‎07‎-‎10T05:14:31.000000000Z) has successfully loaded and...