Bug check help


  1. Posts : 3
    Windows 10 Pro
       #1

    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 am saving out PSB files (larger than 6GB so far) at the point of failure:

    I've rebuilt the machine twice with a fresh install of the latest Windows 10 build (including all updates)

    - Installed latest NVidia drivers
    - Installed the latest Photoshop 2019 and Illustrator 2019 only
    - Running updated Avast Anti-virus free
    - latest BSOD bugcheck report pasted below

    My system is as follows
    Intel i7-5820K hex core (idle core temp of 40)
    Corsair Vengeance 32GB 2400Mhz RAM (2x16)
    X99E-ITX/AC motherboard
    512GB NVME M.2 drive
    Synology 3TB NAS storage

    If anyone has any ideas please do share:

    Thanks
    Code:
    *************************************
    
    Microsoft (R) Windows Debugger Version 10.0.17763.1 AMD64
    Copyright (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 17134 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff800`f2a96000 PsLoadedModuleList = 0xfffff800`f2e44290
    Debug session time: Tue Oct 16 12:51:54.297 2018 (UTC + 1:00)
    System Uptime: 0 days 0:34:41.072
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck BE, {ffff8680025729d4, 8a00000000200021, ffff9003eb859840, a}
    Probably caused by : memory_corruption ( nt!MiRaisedIrqlFault+31a )
    Followup: MachineOwner
    ---------
    10: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
    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.
    Arguments:
    Arg1: ffff8680025729d4, Virtual address for the attempted write.
    Arg2: 8a00000000200021, PTE contents.
    Arg3: ffff9003eb859840, (reserved)
    Arg4: 000000000000000a, (reserved)
    Debugging Details:
    ------------------
    
    KEY_VALUES_STRING: 1
    
    STACKHASH_ANALYSIS: 1
    TIMELINE_ANALYSIS: 1
    
    DUMP_CLASS: 1
    DUMP_QUALIFIER: 401
    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
    SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
    SYSTEM_SKU: To Be Filled By O.E.M.
    SYSTEM_VERSION: To Be Filled By O.E.M.
    BIOS_VENDOR: American Megatrends Inc.
    BIOS_VERSION: P3.80
    BIOS_DATE: 04/06/2018
    BASEBOARD_MANUFACTURER: ASRock
    BASEBOARD_PRODUCT: X99E-ITX/ac
    BASEBOARD_VERSION: 
    DUMP_TYPE: 1
    BUGCHECK_P1: ffff8680025729d4
    BUGCHECK_P2: 8a00000000200021
    BUGCHECK_P3: ffff9003eb859840
    BUGCHECK_P4: a
    CPU_COUNT: c
    CPU_MHZ: cdc
    CPU_VENDOR: GenuineIntel
    CPU_FAMILY: 6
    CPU_MODEL: 3f
    CPU_STEPPING: 2
    CPU_MICROCODE: 6,3f,2,0 (F,M,S,R) SIG: 3C'00000000 (cache) 3C'00000000 (init)
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0xBE
    PROCESS_NAME: System
    CURRENT_IRQL: 2
    ANALYSIS_SESSION_HOST: DESKTOP-VPGVGJO
    ANALYSIS_SESSION_TIME: 10-16-2018 12:56:19.0299
    ANALYSIS_VERSION: 10.0.17763.1 amd64fre
    TRAP_FRAME: ffff9003eb859840 -- (.trap 0xffff9003eb859840)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffff868000000000 rbx=0000000000000000 rcx=ffff8680025729b0
    rdx=00000000000fffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800f2be3880 rsp=ffff9003eb8599d0 rbp=0000000000000000
    r8=0000000000000000 r9=ffff8680145729b0 r10=0000000fffffffff
    r11=fffffff000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!MiUnlinkNumaStandbyPage+0xcc:
    fffff800`f2be3880 66897924 mov word ptr [rcx+24h],di ds:ffff8680`025729d4=????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff800f2b2400a to fffff800f2c3f490
    STACK_TEXT: 
    ffff9003`eb859688 fffff800`f2b2400a : 00000000`000000be ffff8680`025729d4 8a000000`00200021 ffff9003`eb859840 : nt!KeBugCheckEx
    ffff9003`eb859690 fffff800`f2b8e3e6 : 00000000`00000003 8a000000`00200021 ffff9003`eb8597d0 00000000`00000000 : nt!MiRaisedIrqlFault+0x31a
    ffff9003`eb8596d0 fffff800`f2c4cbda : 00000000`00000000 ffffcc80`a2c80180 ffff9003`e854db00 ffff9588`91f0a040 : nt!MmAccessFault+0x3f6
    ffff9003`eb859840 fffff800`f2be3880 : 00000000`00000087 fffff800`f2cfb831 00000000`00000000 00000000`006c7f87 : nt!KiPageFault+0x31a
    ffff9003`eb8599d0 fffff800`f2be3661 : ffff8680`14572980 00000000`00000000 00000000`00000000 fffff800`f2e65900 : nt!MiUnlinkNumaStandbyPage+0xcc
    ffff9003`eb859a10 fffff800`f2cfc608 : fffff800`f2e65ac0 00000000`00000000 ffff9588`00000000 00000000`00000087 : nt!MiRemoveLowestPriorityStandbyPage+0x381
    ffff9003`eb859aa0 fffff800`f2cfc7d5 : 00000000`00000000 00000000`00000000 fffff800`00000000 00000000`000002fc : nt!MiPruneStandbyPages+0x228
    ffff9003`eb859b30 fffff800`f2aece35 : ffff9588`99494040 fffff800`f2cfc750 ffff9588`91ed0950 fffff800`f2e668e0 : nt!MiRebalanceZeroFreeLists+0x85
    ffff9003`eb859b80 fffff800`f2b094f7 : ffff9588`99494040 00000000`00000080 ffff9588`91ec2440 ffff9588`99494040 : nt!ExpWorkerThread+0xf5
    ffff9003`eb859c10 fffff800`f2c46906 : ffffcc80`a26c0180 ffff9588`99494040 fffff800`f2b094b0 00000000`00008001 : nt!PspSystemThreadStartup+0x47
    ffff9003`eb859c60 00000000`00000000 : ffff9003`eb85a000 ffff9003`eb854000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    THREAD_SHA1_HASH_MOD_FUNC: b179561bcb326c8058e5d68c054c098bd7db2d14
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 08578a6e292ba835cbd13e5fbfa6eb3d386baaee
    THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c
    FOLLOWUP_IP: 
    nt!MiRaisedIrqlFault+31a
    fffff800`f2b2400a cc int 3
    FAULT_INSTR_CODE: 4f8b4ccc
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt!MiRaisedIrqlFault+31a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 5ba316ae
    STACK_COMMAND: .thread ; .cxr ; kb
    IMAGE_NAME: memory_corruption
    BUCKET_ID_FUNC_OFFSET: 31a
    FAILURE_BUCKET_ID: 0xBE_nt!MiRaisedIrqlFault
    BUCKET_ID: 0xBE_nt!MiRaisedIrqlFault
    PRIMARY_PROBLEM_CLASS: 0xBE_nt!MiRaisedIrqlFault
    TARGET_TIME: 2018-10-16T11:51:54.000Z
    OSBUILD: 17134
    OSSERVICEPACK: 0
    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: 2018-09-20 04:40:30
    BUILDDATESTAMP_STR: 180410-1804
    BUILDLAB_STR: rs4_release
    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
    ANALYSIS_SESSION_ELAPSED_TIME: c7c
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0xbe_nt!miraisedirqlfault
    FAILURE_ID_HASH: {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}
    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 3
    Windows 10 Pro
    Thread Starter
       #2

    FYI: I have now changed the BIOS, removed the XMP profile and reverted to running the sticks at 2133Mhz...awaiting another BSOD.
      My Computer


  3. Posts : 3
    Windows 10 Pro
    Thread Starter
       #3

    Kempison said:
    FYI: I have now changed the BIOS, removed the XMP profile and reverted to running the sticks at 2133Mhz...awaiting another BSOD.
    To anyone with a similar issue, so far so good; this seems to have stablilised the system.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:51.
Find Us




Windows 10 Forums