BSOD happens randomly


  1. Posts : 1
    64 bit Windows 7 Professional
       #1

    BSOD happens randomly


    I am analyzing the problem with WinDbg I am not sure where to go from here. Please check the dmp file


    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\032917-22916-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23677.amd64fre.win7sp1_ldr.170209-0600
    Machine Name:
    Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032a9730
    Debug session time: Wed Mar 29 11:57:24.547 2017 (UTC - 6:00)
    System Uptime: 1 days 0:46:01.406
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    ERROR: FindPlugIns 8007007b
    ERROR: Some plugins may not be available [8007007b]
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffff30020e5abd0, 1, fffff800030d8740, 7}


    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3a251 )

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

    7: kd> !analyze -v
    ERROR: FindPlugIns 8007007b
    ERROR: Some plugins may not be available [8007007b]
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: fffff30020e5abd0, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff800030d8740, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000007, (reserved)

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


    Could not read faulting driver name

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 7601.23677.amd64fre.win7sp1_ldr.170209-0600

    DUMP_TYPE: 2

    BUGCHECK_P1: fffff30020e5abd0

    BUGCHECK_P2: 1

    BUGCHECK_P3: fffff800030d8740

    BUGCHECK_P4: 7

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003313100
    Unable to get MmSystemRangeStart
    GetUlongPtrFromAddress: unable to read from fffff800033132e8
    GetUlongPtrFromAddress: unable to read from fffff80003313498
    GetPointerFromAddress: unable to read from fffff800033130b8
    fffff30020e5abd0

    FAULTING_IP:
    nt!memset+b0
    fffff800`030d8740 480fc311 movnti qword ptr [rcx],rdx

    MM_INTERNAL_CODE: 7

    CPU_COUNT: 8

    CPU_MHZ: ae9

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 46

    CPU_STEPPING: 1

    CPU_MICROCODE: 6,46,1,0 (F,M,S,R) SIG: 12'00000000 (cache) 12'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: LDISCN32.EXE

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: L81503W

    ANALYSIS_SESSION_TIME: 03-29-2017 14:29:45.0995

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    TRAP_FRAME: fffff88007738410 -- (.trap 0xfffff88007738410)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff30020e5abd0 rbx=0000000000000000 rcx=fffff30020e5abd0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030d8740 rsp=fffff880077385a8 rbp=0000000000000001
    r8=0000000000000030 r9=00000015ffab3910 r10=0000000000000000
    r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nt!memset+0xb0:
    fffff800`030d8740 480fc311 movnti qword ptr [rcx],rdx ds:fffff300`20e5abd0=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80003152db9 to fffff800030d6440

    STACK_TEXT:
    fffff880`077382a8 fffff800`03152db9 : 00000000`00000050 fffff300`20e5abd0 00000000`00000001 fffff880`07738410 : nt!KeBugCheckEx
    fffff880`077382b0 fffff800`030d456e : 00000000`00000001 fffff300`20e5abd0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3a251
    fffff880`07738410 fffff800`030d8740 : fffff800`0339bbd7 fffffa80`00000000 fffffa80`0000bb3e 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`077385a8 fffff800`0339bbd7 : fffffa80`00000000 fffffa80`0000bb3e 00000000`00000000 00000000`0001e600 : nt!memset+0xb0
    fffff880`077385b0 fffff800`033d9f62 : fffffa80`1a06c340 00000000`00000000 00000000`00000002 fffff880`07738870 : nt!MiCreateImageFileMap+0x847
    fffff880`077387e0 fffff800`033b4eda : fffff880`07738a40 00000000`00000002 00000000`00000000 fffff880`07738a38 : nt!MmCreateSection+0x712
    fffff880`077389f0 fffff800`030d56d3 : fffffa80`14b3fb50 00000000`00d8e7c8 fffff880`07738a88 00000000`00000000 : nt!NtCreateSection+0x171
    fffff880`07738a70 00000000`76dbc1da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00d8e7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dbc1da


    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 683480236dd0aa7a8fa5db5bb39bf70b260b1256

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1f941cd3a8e40107c0b71c2ea3cd47925985aeb5

    THREAD_SHA1_HASH_MOD: cb5f414824c2521bcc505eaa03e92fa10922dad8

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+3a251
    fffff800`03152db9 cc int 3

    FAULT_INSTR_CODE: 11fa80cc

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3a251

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 589c915d

    IMAGE_VERSION: 6.1.7601.23677

    FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+3a251

    BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+3a251

    PRIMARY_PROBLEM_CLASS: X64_0x50_nt!_??_::FNODOBFM::_string_+3a251

    TARGET_TIME: 2017-03-29T17:57:24.000Z

    OSBUILD: 7601

    OSSERVICEPACK: 1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 7

    OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2017-02-09 08:57:17

    BUILDDATESTAMP_STR: 170209-0600

    BUILDLAB_STR: win7sp1_ldr

    BUILDOSVER_STR: 6.1.7601.23677.amd64fre.win7sp1_ldr.170209-0600

    ANALYSIS_SESSION_ELAPSED_TIME: 4eb

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x50_nt!_??_::fnodobfm::_string_+3a251

    FAILURE_ID_HASH: {9deefd5d-d151-b276-4612-70b2283714c2}

    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Hi sbarton,

    Try the steps in this tutorial :)
      My Computer


 

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

© Designer Media Ltd
All times are GMT -5. The time now is 13:45.
Find Us