Windows 8.1 Pro BSOD Randomly

Discussion in 'Windows 8 Blue Screen of Death (BSOD)' started by insanegod94, Feb 10, 2015.

  1. insanegod94

    insanegod94 New Member

    Joined:
    Feb 10, 2015
    Messages:
    3
    Likes Received:
    1
    Hello,

    I decided to upgrade my pc and last night I got everything together and did a fresh install of 8.1 Pro on a new SSD. I also made some hardware changes in the form of a new video card (970GTX) and took out 8 gigs of Mushkin Blackline ram and put in 16 gigs of Mushkin Redline ram. Some of these DMP files were screaming memory at me so I currently have memtest running while I am at work to see what comes of that. The computer will randomly bluescreen on me. The only drivers I have installed were the latest Nvidia driver and my Realtek LAN driver from the Asus website for my mobo. I attached my .dmp files in a zip below. Also going to post them in the body. If anyone has some time to lend me assistance I would appreciate it! They are posted in the order they occurred.



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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\020915-8031-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff801`1128d000 PsLoadedModuleList = 0xfffff801`11551990
    Debug session time: Mon Feb 9 23:00:19.236 2015 (UTC - 5:00)
    System Uptime: 0 days 0:58:24.341
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    .................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {8886, fffffa80010a1de0, fffffa80010ec1b0, 200}

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

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

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

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000008886, The subtype of the bugcheck.
    Arg2: fffffa80010a1de0
    Arg3: fffffa80010ec1b0
    Arg4: 0000000000000200

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


    BUGCHECK_STR: 0x1a_8886

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: explorer.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff801113f3a91 to fffff801113daca0

    STACK_TEXT:
    ffffd000`2760fa88 fffff801`113f3a91 : 00000000`0000001a 00000000`00008886 fffffa80`010a1de0 fffffa80`010ec1b0 : nt!KeBugCheckEx
    ffffd000`2760fa90 fffff801`1133a390 : 00000000`00001700 fffffa80`010a1de0 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x8901
    ffffd000`2760fb20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmPurgeSection+0x36c


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+8901
    fffff801`113f3a91 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+8901

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4

    FAILURE_BUCKET_ID: X64_0x1a_8886_nt!_??_::FNODOBFM::_string_+8901

    BUCKET_ID: X64_0x1a_8886_nt!_??_::FNODOBFM::_string_+8901

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



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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\020915-7328-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff800`92c13000 PsLoadedModuleList = 0xfffff800`92ed7990
    Debug session time: Mon Feb 9 23:01:54.378 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:19.125
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {ffffe000ffc89798, 2, 1, fffff80001962ac9}

    Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys ( Rt64win7+16ac9 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: ffffe000ffc89798, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff80001962ac9, address which referenced memory

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


    OVERLAPPED_MODULE: Address regions for 'condrv' and 'WUDFRd.sys' overlap

    WRITE_ADDRESS: fffff80092ec5340: Unable to get special pool info
    fffff80092ec5340: Unable to get special pool info
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    ffffe000ffc89798

    CURRENT_IRQL: 2

    FAULTING_IP:
    Rt64win7+16ac9
    fffff800`01962ac9 48894108 mov qword ptr [rcx+8],rax

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from fffff80092d6c7e9 to fffff80092d60ca0

    STACK_TEXT:
    ffffd000`2076b218 fffff800`92d6c7e9 : 00000000`0000000a ffffe000`ffc89798 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`2076b220 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    Rt64win7+16ac9
    fffff800`01962ac9 48894108 mov qword ptr [rcx+8],rax

    SYMBOL_NAME: Rt64win7+16ac9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Rt64win7

    IMAGE_NAME: Rt64win7.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e53b15d

    FAILURE_BUCKET_ID: X64_0xD1_Rt64win7+16ac9

    BUCKET_ID: X64_0xD1_Rt64win7+16ac9

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


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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\020915-7203-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff803`1167d000 PsLoadedModuleList = 0xfffff803`11941990
    Debug session time: Mon Feb 9 23:14:43.612 2015 (UTC - 5:00)
    System Uptime: 0 days 0:12:08.358
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {fffffaafda52962a, 2, 0, fffff803116b1822}

    Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+82 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffaafda52962a, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff803116b1822, address which referenced memory

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


    READ_ADDRESS: fffff8031192f340: Unable to get special pool info
    fffff8031192f340: Unable to get special pool info
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    fffffaafda52962a

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiPfnShareCountIsZero+82
    fffff803`116b1822 0fb6501a movzx edx,byte ptr [rax+1Ah]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: consent.exe

    LAST_CONTROL_TRANSFER: from fffff803117d67e9 to fffff803117caca0

    STACK_TEXT:
    ffffd000`2ba9fc08 fffff803`117d67e9 : 00000000`0000000a fffffaaf`da52962a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`2ba9fc10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    nt!MiPfnShareCountIsZero+82
    fffff803`116b1822 0fb6501a movzx edx,byte ptr [rax+1Ah]

    SYMBOL_NAME: nt!MiPfnShareCountIsZero+82

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0xA_nt!MiPfnShareCountIsZero+82

    BUCKET_ID: X64_0xA_nt!MiPfnShareCountIsZero+82

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



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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\020915-6937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff802`64202000 PsLoadedModuleList = 0xfffff802`644c6990
    Debug session time: Mon Feb 9 23:51:36.198 2015 (UTC - 5:00)
    System Uptime: 0 days 0:05:56.944
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {ffffffffffffffff, 0, fffff96000136911, 0}


    Could not read faulting driver name
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

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

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

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


    Could not read faulting driver name

    READ_ADDRESS: fffff802644b4340: Unable to get special pool info
    fffff802644b4340: Unable to get special pool info
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    ffffffffffffffff

    FAULTING_IP:
    win32k!HMValidateHandle+e1
    fffff960`00136911 482300 and rax,qword ptr [rax]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x50

    PROCESS_NAME: explorer.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80264364fd8 to fffff8026434fca0

    STACK_TEXT:
    ffffd000`2a79d288 fffff802`64364fd8 : 00000000`00000050 ffffffff`ffffffff 00000000`00000000 ffffd000`2a79d470 : nt!KeBugCheckEx
    ffffd000`2a79d290 fffff802`642630fd : 00000000`00000000 ffffe000`05468080 ffffd000`2a79d470 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4e48
    ffffd000`2a79d330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x7ed


    STACK_COMMAND: .bugcheck ; kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
    7 errors : !win32k (fffff96000136903-fffff9600013693b)
    fffff96000136900 35 00 74 *00 48 8b ce e8 74 eb ff ff f7 d8 48 1b 5.t.H...t.....H.
    fffff96000136910 c0 48 23 *00 48 85 db 74 39 48 8b *00 48 8b 5c 24 .H#.H..t9H..H.\$
    fffff96000136920 40 48 8b *00 24 48 48 8b 74 24 50 *00 8b 7c 24 58 @H..$HH.t$P..|$X
    fffff96000136930 48 83 c4 *00 41 5f 41 5e 41 5c c3 *ff 80 fe ff 0f H...A_A^A\......

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: STRIDE

    FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

    BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

    Followup: memory_corruption
    ---------


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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\021015-9062-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff801`a167a000 PsLoadedModuleList = 0xfffff801`a193e990
    Debug session time: Tue Feb 10 00:32:57.632 2015 (UTC - 5:00)
    System Uptime: 0 days 0:34:43.378
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ....................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {fffffd7fffffffe0, 2, 1, fffff801a17384bd}

    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+139 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffd7fffffffe0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801a17384bd, address which referenced memory

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


    WRITE_ADDRESS: fffff801a192c340: Unable to get special pool info
    fffff801a192c340: Unable to get special pool info
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    fffffd7fffffffe0

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiReplenishPageSlist+139
    fffff801`a17384bd f0410fba691000 lock bts dword ptr [r9+10h],0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from fffff801a17d37e9 to fffff801a17c7ca0

    STACK_TEXT:
    ffffd000`28423438 fffff801`a17d37e9 : 00000000`0000000a fffffd7f`ffffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`28423440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    nt!MiReplenishPageSlist+139
    fffff801`a17384bd f0410fba691000 lock bts dword ptr [r9+10h],0

    SYMBOL_NAME: nt!MiReplenishPageSlist+139

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+139

    BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+139

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

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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\021015-8687-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff800`7261a000 PsLoadedModuleList = 0xfffff800`728de990
    Debug session time: Tue Feb 10 00:51:08.469 2015 (UTC - 5:00)
    System Uptime: 0 days 0:17:13.215
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c000001d, fffff80000611f6b, ffffd0002afcf710, 0}

    Probably caused by : WdFilter.sys ( WdFilter!MpAmPreCreate+32b )

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

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

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c000001d, Exception code that caused the bugcheck
    Arg2: fffff80000611f6b, Address of the instruction which caused the bugcheck
    Arg3: ffffd0002afcf710, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

    FAULTING_IP:
    WdFilter!MpAmPreCreate+32b
    fffff800`00611f6b 480f44de cmove rbx,rsi

    CONTEXT: ffffd0002afcf710 -- (.cxr 0xffffd0002afcf710)
    rax=0000000000000000 rbx=ffffe000021eb010 rcx=000000000000fffc
    rdx=000000000000fffc rsi=0000000000000001 rdi=0000000000000000
    rip=fffff80000611f6b rsp=ffffd0002afd0140 rbp=ffffd0002afd01d9
    r8=0000000000000000 r9=ffffd0002afd0240 r10=ffffd0002afd1000
    r11=fffff8000076c9c3 r12=ffffe000118d3ce8 r13=ffffe000118d3c90
    r14=fffff80000609010 r15=ffffe00011a7b0e8
    iopl=0 nv up ei ng nz ac po cy
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297
    WdFilter!MpAmPreCreate+0x32b:
    fffff800`00611f6b 480f44de cmove rbx,rsi
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: TiWorker.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80000611f6b

    STACK_TEXT:
    ffffd000`2afd0140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WdFilter!MpAmPreCreate+0x32b


    FOLLOWUP_IP:
    WdFilter!MpAmPreCreate+32b
    fffff800`00611f6b 480f44de cmove rbx,rsi

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: WdFilter!MpAmPreCreate+32b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: WdFilter

    IMAGE_NAME: WdFilter.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 526865d9

    STACK_COMMAND: .cxr 0xffffd0002afcf710 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_WdFilter!MpAmPreCreate+32b

    BUCKET_ID: X64_0x3B_WdFilter!MpAmPreCreate+32b

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

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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\021015-8593-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff800`5a075000 PsLoadedModuleList = 0xfffff800`5a339990
    Debug session time: Tue Feb 10 01:07:10.028 2015 (UTC - 5:00)
    System Uptime: 0 days 0:15:11.773
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 139, {3, ffffd0002b587e80, ffffd0002b587dd8, 0}

    Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClassIoComplete+42 )

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

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

    Unknown bugcheck code (139)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000003
    Arg2: ffffd0002b587e80
    Arg3: ffffd0002b587dd8
    Arg4: 0000000000000000

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


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x139

    PROCESS_NAME: MsMpEng.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff8005a1ce7e9 to fffff8005a1c2ca0

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: ffffd0002b587c40

    STACK_COMMAND: dds 2B587C40-0x20 ; kb

    STACK_TEXT:
    00000000`2b587c20 ????????
    00000000`2b587c24 ????????
    00000000`2b587c28 ????????
    00000000`2b587c2c ????????
    00000000`2b587c30 ????????
    00000000`2b587c34 ????????
    00000000`2b587c38 ????????
    00000000`2b587c3c ????????
    00000000`2b587c40 ????????
    00000000`2b587c44 ????????
    00000000`2b587c48 ????????
    00000000`2b587c4c ????????
    00000000`2b587c50 ????????
    00000000`2b587c54 ????????
    00000000`2b587c58 ????????
    00000000`2b587c5c ????????
    00000000`2b587c60 ????????
    00000000`2b587c64 ????????
    00000000`2b587c68 ????????
    00000000`2b587c6c ????????
    00000000`2b587c70 ????????
    00000000`2b587c74 ????????
    00000000`2b587c78 ????????
    00000000`2b587c7c ????????
    00000000`2b587c80 ????????
    00000000`2b587c84 ????????
    00000000`2b587c88 ????????
    00000000`2b587c8c ????????
    00000000`2b587c90 ????????
    00000000`2b587c94 ????????
    00000000`2b587c98 ????????
    00000000`2b587c9c ????????


    FOLLOWUP_IP:
    CLASSPNP!ClassIoComplete+42
    fffff800`00863c01 90 nop

    SYMBOL_NAME: CLASSPNP!ClassIoComplete+42

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: CLASSPNP

    IMAGE_NAME: CLASSPNP.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 5215cff7

    FAILURE_BUCKET_ID: X64_0x139_CLASSPNP!ClassIoComplete+42

    BUCKET_ID: X64_0x139_CLASSPNP!ClassIoComplete+42

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


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


    Loading Dump File [C:\Users\kmanning\Desktop\dmp files\021015-8984-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff802`4c609000 PsLoadedModuleList = 0xfffff802`4c8cd990
    Debug session time: Tue Feb 10 07:11:16.578 2015 (UTC - 5:00)
    System Uptime: 0 days 6:03:27.324
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005, fffff8024c7178a6, ffffd00020a19478, ffffd00020a18c80}

    Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+42 )

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

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8024c7178a6, The address that the exception occurred at
    Arg3: ffffd00020a19478, Exception Record Address
    Arg4: ffffd00020a18c80, Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt!MiDemoteCombinedPte+42
    fffff802`4c7178a6 4939442420 cmp qword ptr [r12+20h],rax

    EXCEPTION_RECORD: ffffd00020a19478 -- (.exr 0xffffd00020a19478)
    ExceptionAddress: fffff8024c7178a6 (nt!MiDemoteCombinedPte+0x0000000000000042)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT: ffffd00020a18c80 -- (.cxr 0xffffd00020a18c80)
    rax=0000000000000001 rbx=8000000400a18963 rcx=fffff6e00004a320
    rdx=8000000000000000 rsi=fffff6e00004a320 rdi=fffff781000202f8
    rip=fffff8024c7178a6 rsp=ffffd00020a196b0 rbp=0000058000000000
    r8=0000000fffffffff r9=8000000000000000 r10=0000007ffffffff8
    r11=0000098000000000 r12=7fffffffffffffd0 r13=fffff6e00004a320
    r14=0000000000004037 r15=fffffa800c01e480
    iopl=0 nv up ei ng nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
    nt!MiDemoteCombinedPte+0x42:
    fffff802`4c7178a6 4939442420 cmp qword ptr [r12+20h],rax ds:002b:7fffffff`fffffff0=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: fffff8024c8bb340: Unable to get special pool info
    fffff8024c8bb340: Unable to get special pool info
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    ffffffffffffffff

    FOLLOWUP_IP:
    nt!MiDemoteCombinedPte+42
    fffff802`4c7178a6 4939442420 cmp qword ptr [r12+20h],rax

    BUGCHECK_STR: 0x7E

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8024c7178a6

    STACK_TEXT:
    ffffd000`20a196b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDemoteCombinedPte+0x42


    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiDemoteCombinedPte+42

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4

    STACK_COMMAND: .cxr 0xffffd00020a18c80 ; kb

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0x7E_nt!MiDemoteCombinedPte+42

    BUCKET_ID: X64_0x7E_nt!MiDemoteCombinedPte+42

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

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffd7fffffffe0, 2, 1, fffff801a17384bd}
    
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+139 )
    
    Followup: MachineOwner
    
    Hi,
    I looked through most of your dumps and although you have quite a few different Bugchecks most blame memory corruption. I have a feeling though that your issue is Bios related:
    BiosVersion = 0901
    BiosReleaseDate = 11/24/2011
    BaseBoardManufacturer = ASUSTeK COMPUTER INC.
    BaseBoardProduct = SABERTOOTH 990FX
    The latest Bios downloadable from the motherboard support page (please double check that this page is correct for your moBo) is 1604. Please update:
    http://www.asus.com/uk/Motherboards/SABERTOOTH_990FX/HelpDesk_Download/

    Obviously the other thing to do would be check the RAM but as your already running memtest86 I'll await your results.
     
  3. insanegod94

    insanegod94 New Member

    Joined:
    Feb 10, 2015
    Messages:
    3
    Likes Received:
    1
    I have not gotten to updating the BIOS yet. When I got home memtest was frozen without even completing a single pass and had about 46 million errors. I rebooted and within the first 2 minutes memtest already had about 70 errors. I thought there was no way this RAM was that bad so I moved the RAM to my other channel and made sure it was firmly seated. About 40 minutes now without any errors at all. If the pass completes with no errors then I will boot windows and see if I experience crashes. If I do then I will progress to driver verifier troubleshooting and updating the BIOS. I know that poorly seated RAM can cause all sorts of havoc and is often overlooked being so simple. Just wanted to provide an update. I will update with either resolution or continued steps once I get there.



    Thanks again for your time.
     
  4. insanegod94

    insanegod94 New Member

    Joined:
    Feb 10, 2015
    Messages:
    3
    Likes Received:
    1
    After re-seating the RAM in my other channel I proceeded to boot into windows and use my computer normally for about 3 hours with no crashes at all. I am going to say this is resolved for right now. The BIOS update is scheduled for tonight. Thank you for your time kemical.
     
    kemical likes this.
  5. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Sounds good.. Thank you for updating your thread and best of luck.. :)
     

Share This Page

Loading...