locked
BSOD almost every 15 minutes , even in safe mode RRS feed

  • Question

  • Could someone please help me troubleshoot the BSOD i've experieced , below is the first dump file bug check results 

    Microsoft (R) Windows Debugger Version 10.0.10586.567 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Rchid\Downloads\020816-10951-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SystemCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SystemCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`03287e50
    Debug session time: Sun Feb  7 23:18:40.346 2016 (UTC + 0:00)
    System Uptime: 0 days 0:10:01.719
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {41790, fffffa80008101e0, ffff, 0}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 )

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

    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffa80008101e0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000

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


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  7600.16385.amd64fre.win7_rtm.090713-1255

    SYSTEM_MANUFACTURER:  MSI

    SYSTEM_PRODUCT_NAME:  MS-7758

    SYSTEM_SKU:  To be filled by O.E.M.

    SYSTEM_VERSION:  2.0

    BIOS_VENDOR:  American Megatrends Inc.

    BIOS_VERSION:  V10.6

    BIOS_DATE:  10/23/2012

    BASEBOARD_MANUFACTURER:  MSI

    BASEBOARD_PRODUCT:  B75A-G43 (MS-7758)

    BASEBOARD_VERSION:  2.0

    DUMP_TYPE:  2

    BUGCHECK_P1: 41790

    BUGCHECK_P2: fffffa80008101e0

    BUGCHECK_P3: ffff

    BUGCHECK_P4: 0

    BUGCHECK_STR:  0x1a_41790

    CPU_COUNT: 4

    CPU_MHZ: bb1

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3a

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 15'00000000 (cache) 15'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  nvspcaps64.exe

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  RCHID-PC

    ANALYSIS_SESSION_TIME:  02-09-2016 14:59:56.0779

    ANALYSIS_VERSION: 10.0.10586.567 x86fre

    LAST_CONTROL_TRANSFER:  from fffff8000312e328 to fffff800030bbf00

    STACK_TEXT:  
    fffff880`0d3a3188 fffff800`0312e328 : 00000000`0000001a 00000000`00041790 fffffa80`008101e0 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`0d3a3190 fffff800`0308eeee : fffffa80`09ddab30 fffffa80`00000008 fffff8a0`0000037e 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33a98
    fffff880`0d3a3a40 fffff800`0339e7af : fffff8a0`02b40a90 00000000`00000001 00000000`00000000 fffffa80`091b6b60 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`0d3a3a90 fffff800`03377cb8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x47f
    fffff880`0d3a3b60 fffff800`030bb153 : fffffa80`09ddab30 fffff880`00000000 fffffa80`091b6b60 000007fe`faa80000 : nt!NtTerminateProcess+0x138
    fffff880`0d3a3be0 00000000`76d2017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0021fca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d2017a


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  a69c46532e1910b23a4fdf90139e16e15a241013

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  eca573e458d95b0bc6f1a8c7444a7c2d853347b5

    THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+33a98
    fffff800`0312e328 cc              int     3

    FAULT_INSTR_CODE:  cd8b4ccc

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33a98

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

    IMAGE_VERSION:  6.1.7600.16385

    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33a98

    BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33a98

    PRIMARY_PROBLEM_CLASS:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33a98

    TARGET_TIME:  2016-02-07T23:18:40.000Z

    OSBUILD:  7600

    OSSERVICEPACK:  0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 7

    OSEDITION:  Windows 7 WinNt TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2009-07-13 23:40:48

    BUILDDATESTAMP_STR:  090713-1255

    BUILDLAB_STR:  win7_rtm

    BUILDOSVER_STR:  6.1.7600.16385.amd64fre.win7_rtm.090713-1255

    ANALYSIS_SESSION_ELAPSED_TIME: 766

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+33a98

    FAILURE_ID_HASH:  {a6e38bb7-e467-1c85-a114-30a357f6f745}

    Followup:     MachineOwner

    Tuesday, February 9, 2016 9:04 PM

All replies

  • Hi .

    The MEMORY_MANAGEMENT (0x0000001A) bug check  indicates that a severe memory management error occurred.
    According to the DMP file, the process nvspcaps64.exe is involved in the error: this module is known as the NVIDIA Capture Server and belongs to the NVIDIA drivers package for the installed video card, so the first actions to take should be upgrading the drivers to a newer version or reverting them back to the previous one if that worked fine.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Sunday, February 19, 2017 5:01 PM