Unexpected BSOD results in Multiple Crash Dumps

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Modifyinc, Jul 7, 2013.

  1. Modifyinc

    Modifyinc New Member

    Joined:
    Jul 7, 2013
    Messages:
    4
    Likes Received:
    0
    Hello everyone,

    I have recently had a few crash dumps appear in my c:\windows\minidump.

    I am uploading them here, for those who may wish to review them.

    I am following the instructions as outlined in the youtube video: BSOD, Crash Dump, and Minidump Analysis created by Windows7Forums.

    I also have the Memory.dmp but it is 469 MB, so I will not be uploading it.

    The majority of the minidumps are 0A and 1E.

    Dell Inspiron 5520 running Windows 7 Home Premium 64-Bit.

    View attachment 070413-37861-01.dmp
    View attachment 070213-29998-01.dmp
    View attachment 070213-26910-01.dmp
    View attachment 070213-23680-01.dmp
    View attachment 070213-27939-01.dmp
    View attachment 070213-30435-01.dmp
    View attachment 070313-28906-01.dmp
    View attachment 070413-36176-01.dmp
    View attachment 070413-27440-01.dmp
    View attachment 070413-34897-01.dmp
    View attachment 070213-38142-01.dmp
     
  2. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello there!

    There are lot of random crashes with different Bugcheck which mostly refers to Hardware. Let's run a Hardware Diagnostic Hardware Diagnostic | Captain Debugger both RAM & Hard drive.

    Then reinstall your Network Drivers completely. Run SFC Scannow to rule out any corrupted file systems. SFC /SCANNOW to Repair Windows 7 Files | Captain Debugger

    Code:
    DRIVER_POWER_STATE_FAILURE (9f)A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa8007022660, The thread currently holding on to the Pnp lock.
    Arg4: fffff800047fd3d0, nt!TRIAGE_9F_PNP on Win7
    
    
    Debugging Details:
    ------------------
    
    
    Implicit thread is now fffffa80`07022660
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x9F
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  2
    
    
    LAST_CONTROL_TRANSFER:  from fffff80002e74652 to fffff80002e81b8a
    
    
    STACK_TEXT:  
    fffff880`033b5cf0 fffff800`02e74652 : fffffa80`07022660 fffffa80`07022660 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`033b5e30 fffff800`02e85a9f : fffffa80`0c13d290 fffffa80`0c13d290 fffffa80`00000000 fffff880`01a1124c : nt!KiCommitThreadWait+0x1d2
    fffff880`033b5ec0 fffff800`02eda5c6 : 00000000`00000000 fffffa80`00000000 fffff880`01b69800 fffff880`0191a200 : nt!KeWaitForSingleObject+0x19f
    fffff880`033b5f60 fffff880`01a1914d : 00000000`00000100 0000000c`00000003 00000000`00000000 ffffe572`40010023 : nt! ?? ::FNODOBFM::`string'+0x13006
    fffff880`033b5fd0 fffff880`01b3fb9e : 00000000`c00000bb 00000000`00000008 fffff880`033b6150 fffff880`033b6150 : tcpip!FlPnpEvent+0x17d
    fffff880`033b6040 fffff880`0192fb2f : 00000000`c00000bb 00000000`00000008 00000000`c00000bb fffffa80`0b0551a0 : tcpip!Fl68PnpEvent+0xe
    fffff880`033b6070 fffff880`019304b7 : fffffa80`0c13c010 00000000`00000008 00000000`00000000 fffffa80`0c13c010 : ndis!ndisPnPNotifyBinding+0xbf
    fffff880`033b6100 fffff880`01949911 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0dde6250 : ndis!ndisPnPNotifyAllTransports+0x377
    fffff880`033b6270 fffff880`0194ac5b : 00000000`00000001 fffffa80`0b0551a0 fffffa80`0abcd020 00000000`00000002 : ndis!ndisCloseMiniportBindings+0x111
    fffff880`033b6380 fffff880`018e3bc2 : fffffa80`0b0551a0 fffffa80`0b0551a0 fffffa80`0757b200 fffffa80`0abce901 : ndis!ndisPnPRemoveDevice+0x25b
    fffff880`033b6520 fffff880`0194db69 : 00000000`00000000 fffffa80`0757b200 00000000`00000000 fffffa80`0b0551a0 : ndis!ndisPnPRemoveDeviceEx+0xa2
    fffff880`033b6560 fffff880`00fa57cc : 00000000`00000001 fffffa80`0757b360 00000000`00000000 fffffa80`079ef060 : ndis!ndisPnPDispatch+0x609
    fffff880`033b6600 fffff880`00fa0ebf : 00000000`00000001 fffff880`033b6700 fffff880`033b6700 fffff880`033b6700 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
    fffff880`033b6630 fffff880`00f29ecf : fffffa80`0abcd502 fffff880`033b66f0 00000000`00000000 fffff800`02fb330d : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x123
    fffff880`033b66a0 fffff880`00f219da : fffffa80`0757b200 fffffa80`0757b200 fffffa80`0757b200 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
    fffff880`033b6700 fffff880`00f21aa6 : fffffa80`0757b200 fffffa80`0abc9dc0 fffffa80`0abc9c70 fffffa80`0abc9c70 : Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`033b6740 fffff800`030ef0f9 : fffffa80`0abc9c70 00000000`c00000bb fffff880`033b6838 fffffa80`0757b200 : Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`033b6780 fffff800`0326cf81 : fffffa80`079ef060 00000000`00000000 fffffa80`079efd90 00000000`00000801 : nt!IopSynchronousCall+0xc5
    fffff880`033b67f0 fffff800`02f81253 : fffff8a0`0bbd11a0 fffff8a0`0bbd11a0 00000000`00000016 00000000`00000000 : nt!IopRemoveDevice+0x101
    fffff880`033b68b0 fffff800`0326cad4 : fffffa80`079efd90 00000000`00000000 00000000`00000002 fffffa80`079ef060 : nt!PnpRemoveLockedDeviceNode+0x1a3
    fffff880`033b6900 fffff800`0326cbe0 : 00000000`00000000 fffff8a0`31295601 fffff8a0`13f9c200 ffffe572`5a41adcc : nt!PnpDeleteLockedDeviceNode+0x44
    fffff880`033b6930 fffff800`032fdaa4 : 00000000`00000002 00000000`00000000 fffffa80`079efd90 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
    fffff880`033b69a0 fffff800`032fe0fc : fffff880`00000000 fffffa80`0727f200 fffffa80`07022600 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
    fffff880`033b6ae0 fffff800`031e72ce : 00000000`00000000 fffffa80`0727f270 fffff8a0`043e46b0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
    fffff880`033b6b10 fffff800`02e87ca9 : fffff800`030edf90 fffff8a0`31295640 fffff800`030252d8 fffffa80`07022660 : nt! ?? ::NNGAKEGL::`string'+0x5721b
    fffff880`033b6b70 fffff800`0311f34a : 00000000`00000000 fffffa80`07022660 00000000`00000080 fffffa80`0700bae0 : nt!ExpWorkerThread+0x111
    fffff880`033b6c00 fffff800`02e6f946 : fffff880`031d7180 fffffa80`07022660 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033b6c40 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`033b5b70 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    tcpip!FlPnpEvent+17d
    fffff880`01a1914d 44392d78bd1500  cmp     dword ptr [tcpip!MICROSOFT_TCPIP_PROVIDER_Context+0x24 (fffff880`01b74ecc)],r13d
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  tcpip!FlPnpEvent+17d
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: tcpip
    
    
    IMAGE_NAME:  tcpip.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5189c381
    
    
    FAILURE_BUCKET_ID:  X64_0x9F_4_tcpip!FlPnpEvent+17d
    
    
    BUCKET_ID:  X64_0x9F_4_tcpip!FlPnpEvent+17d
    
    
    Followup: MachineOwner
    
     
  3. Modifyinc

    Modifyinc New Member

    Joined:
    Jul 7, 2013
    Messages:
    4
    Likes Received:
    0
    Thanks for the quick reply.

    I have already completed a few of those requested task earlier.

    sfc /scannow reported no issues.

    chkdsk /f and /r found no issues.

    Though I did not use memtest86+, the Windows 7 Memory Diagnostic Tool found no issues with the RAM after 6 passes.

    I ran the Dell Hardware Diagnostic Tool that is provided when you first power on the laptop. It found no issues.

    The CPU temp reports around 50-60c.

    I will try to follow through with additional test as you suggested.

    This is the output of the memory.dmp as provided by windbg if it helps. I didn't upload the file because of its size.


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


    Loading Dump File [C:\Windows\System32\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: .sympath cache*;srv*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030aa670
    Debug session time: Thu Jul 4 10:08:06.180 2013 (UTC - 4:00)
    System Uptime: 0 days 0:03:41.023
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols

    Loading unloaded module list
    ...
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {d23b, 2, 1, fffff80002f0be45}

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )

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

    2: 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: 000000000000d23b, 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: fffff80002f0be45, address which referenced memory

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

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    WRITE_ADDRESS: 000000000000d23b

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!KeStackAttachProcess+115
    fffff800`02f0be45 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: System

    TRAP_FRAME: fffff880035f5770 -- (.trap 0xfffff880035f5770)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000008 rbx=0000000000000000 rcx=fffffa800701bbb0
    rdx=fffff880035f5a58 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f0be45 rsp=fffff880035f5900 rbp=fffff880035f5a58
    r8=fffffa800701bba0 r9=0000000000000130 r10=fffff880033660c0
    r11=fffffa800701bb50 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!KeStackAttachProcess+0x115:
    fffff800`02f0be45 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax ds:00000000`000000dc=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002edb1e9 to fffff80002edbc40

    STACK_TEXT:
    fffff880`035f5628 fffff800`02edb1e9 : 00000000`0000000a 00000000`0000d23b 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`035f5630 fffff800`02ed9e60 : fffff880`035f57b0 fffff8a0`037205b0 00000000`000000c2 fffffa80`0701bb50 : nt!KiBugCheckDispatch+0x69
    fffff880`035f5770 fffff800`02f0be45 : 00000000`00000000 fffffa80`0701bb50 fffffa80`0701bb50 fffff800`031b12af : nt!KiPageFault+0x260
    fffff880`035f5900 fffffa80`0aa809c8 : fffff880`035f5a80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeStackAttachProcess+0x115
    fffff880`035f5980 fffff880`035f5a80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0aa809c8
    fffff880`035f5988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`035f5a80


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KeStackAttachProcess+115
    fffff800`02f0be45 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!KeStackAttachProcess+115

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935

    FAILURE_BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115

    BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115

    Followup: MachineOwner
    ---------
     
  4. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Windows Memory Diagnostic tool is not accurate run MemTest86+
     

Share This Page

Loading...