locked
Need help reading Windows 7 Minidump RRS feed

  • Question

  • First post... got a few BSOD with driver_power_state_failure yesterday while system was idle.  Could not successfully download SDK to get the windbg tool, so am in need for someone to help me read these from a win 7 x64 system.

    Zip file can be found at:

    https://onedrive.live.com/redir?resid=E1F64F3885DAC395!131&authkey=!AKNVVzENXcqJ1cY&ithint=file%2czip

    Thanks in advance for your assistance.

    -Jay

    Saturday, February 21, 2015 1:21 PM

Answers

  • LJ

    Still nVidia and you did not update to the newest driver available.  There is a Feb 2015 driver yours is from early 2014

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022215-11684-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*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
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`0364e000 PsLoadedModuleList = 0xfffff800`03892890
    Debug session time: Sun Feb 22 05:13:30.196 2015 (UTC - 5:00)
    System Uptime: 0 days 19:14:35.445
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800d459a10, fffff80005054748, fffffa801b0a5e10}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800d459a10, Physical Device Object of the stack
    Arg3: fffff80005054748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa801b0a5e10, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS: fffffa801b0a5e10
    
    DEVICE_OBJECT: fffffa800e19c480
    
    DRIVER_OBJECT: fffffa800e361300
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a
    
    MODULE_NAME: nvlddmkm
    
    FAULTING_MODULE: fffff8800f4e1000 nvlddmkm
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  CloudBerry.Bac
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    DPC_STACK_BASE:  FFFFF80005054FB0
    
    STACK_TEXT:  
    fffff800`050546f8 fffff800`03733b92 : 00000000`0000009f 00000000`00000003 fffffa80`0d459a10 fffff800`05054748 : nt!KeBugCheckEx
    fffff800`05054700 fffff800`036cecfc : fffff800`05054aa0 fffff800`05054aa0 00000000`00000000 00000000`00000010 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`050547a0 fffff800`036ceb96 : fffffa80`0e23f938 00000000`0043c146 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`05054810 fffff800`036cea7e : 000000a1`4b621301 fffff800`05054e88 00000000`0043c146 fffff800`03842b48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`05054e60 fffff800`036ce867 : fffffa80`0f5288eb fffff800`0043c146 00000000`00000000 00000000`0000003e : nt!KiTimerExpiration+0x1be
    fffff800`05054f00 fffff800`036c5925 : 00000000`00000000 fffffa80`15d72b50 00000000`00000000 fffff880`0164d800 : nt!KiRetireDpcList+0x277
    fffff800`05054fb0 fffff800`036c573c : fffffa80`00000000 00000000`00000002 00000000`ffffff01 00000000`00000001 : nt!KxRetireDpcList+0x5
    fffff880`0c770710 fffff800`0370ead3 : fffff800`036be903 fffff800`036be96f fffff880`0d3f3820 00000000`00000000 : nt!KiDispatchInterruptContinue
    fffff880`0c770740 fffff800`036be96f : fffff880`0d3f3820 00000000`00000000 00000000`00000004 00000000`00000000 : nt!KiDpcInterruptBypass+0x13
    fffff880`0c770750 fffff800`03697b3b : fffff800`0367089a 00000000`00000000 fffff880`009ed180 fffff880`009ed180 : nt!KiChainedDispatch+0x19f
    fffff880`0c7708e8 fffff800`0367089a : 00000000`00000000 fffff880`009ed180 fffff880`009ed180 00000000`00000001 : nt!KeSetSystemGroupAffinityThread+0x3
    fffff880`0c7708f0 fffff800`036ccf34 : 00000000`00000000 fffffa80`11bc5b30 fffffa80`0caeca40 00000000`00000000 : nt!KeFlushQueuedDpcs+0x196
    fffff880`0c7709a0 fffff800`039bc0b4 : fffffa80`11bc5b30 00000000`00000000 fffffa80`15d72b50 00000000`00000000 : nt!ObfDereferenceObject+0xd4
    fffff880`0c770a00 fffff800`039bc664 : 00000000`00000738 fffffa80`11bc5b30 fffff8a0`022baa20 00000000`00000738 : nt!ObpCloseHandleTableEntry+0xc4
    fffff880`0c770a90 fffff800`036c2153 : fffffa80`15d72b50 fffff880`0c770b60 00000000`7493473e fffffa80`19105b40 : nt!ObpCloseHandle+0x94
    fffff880`0c770ae0 00000000`758cd842 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`1a16f558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x758cd842
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {42f94646-13b7-b017-1e08-4befcf4d9f5e}
    
    Followup: MachineOwner
    ---------
    
    

       Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Jul 02 13:42:02 2014 (53B4446A)
        CheckSum:         00C4C7C9
        ImageSize:        00C8E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Tuesday, March 3, 2015 2:51 AM
    Sunday, February 22, 2015 1:29 PM
  • Either update you BitDefender AV to the latest available, OR remove it and replace it with the free up to date Microsoft security Essentials

    Uninstall Tools for Bitdefender Products.

    http://www.bitdefender.com/uninstall/

    Microsoft Security Essentials

    http://windows.microsoft.com/en-US/windows/security-essentials-download

    0: kd> !thread fffffa8015d72b50
    GetPointerFromAddress: unable to read from fffff800038fc000
    THREAD fffffa8015d72b50  Cid 09c4.27c0  Teb: 000007fffff9c000 Win32Thread: 0000000000000000 RUNNING on processor 0
    Not impersonating
    GetUlongFromAddress: unable to read from fffff8000383bba8
    Owning Process            fffffa8011bc5b30       Image:         CloudBerry.Bac
    Attached Process          N/A            Image:         N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      4440705     
    Context Switch Count      16            
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address 0x000007fef6d293d4
    Stack Init fffff8800c770c70 Current fffff8800c7705c0
    Base fffff8800c771000 Limit fffff8800c76b000 Call 0
    Priority 30 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5

    Disable cloudberry backup, at least for temporary troubleshooting purposes

    update Chipset

    HECIx64.sys  Tue Oct 19 19:33:43 2010 (4CBE2AD7)

    update

    EtronHub3 EtronHub3.sys Mon Jul 25 17:30:59 2011 (4E2DE093)
    EtronXHCI EtronXHCI.sys Mon Jul 25 17:30:56 2011 (4E2DE090)

     Z68AP-D3 support and drivers.

    http://www.gigabyte.com/products/product-page.aspx?pid=4015#driver

    • Marked as answer by ZigZag3143x Tuesday, March 3, 2015 2:51 AM
    Saturday, February 28, 2015 5:26 AM

All replies

  • Jay

    This was related to your nVidia driver.  I would remove the current driver and install the newest driver available.

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022015-11356-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*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
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`03604000 PsLoadedModuleList = 0xfffff800`03848890
    Debug session time: Fri Feb 20 20:55:57.164 2015 (UTC - 5:00)
    System Uptime: 0 days 10:38:50.413
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800d461060, fffff80000ba0748, fffffa801869d4f0}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800d461060, Physical Device Object of the stack
    Arg3: fffff80000ba0748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa801869d4f0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS: fffffa801869d4f0
    
    DEVICE_OBJECT: fffffa800e465480
    
    DRIVER_OBJECT: fffffa800e334c70
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408
    
    MODULE_NAME: nvlddmkm
    
    FAULTING_MODULE: fffff8800f448000 nvlddmkm
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    STACK_TEXT:  
    fffff800`00ba06f8 fffff800`036e9b92 : 00000000`0000009f 00000000`00000003 fffffa80`0d461060 fffff800`00ba0748 : nt!KeBugCheckEx
    fffff800`00ba0700 fffff800`03684cfc : fffff800`00ba0a88 fffff800`00ba0a88 00000000`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00ba07a0 fffff800`03684b96 : fffff880`0197a4f0 00000000`00257de5 00000000`00000000 fffffa80`0cb02510 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba0810 fffff800`03684a7e : 00000059`3eb4ca19 fffff800`00ba0e88 00000000`00257de5 fffff800`037f9f28 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba0e60 fffff800`03684867 : fffffa80`0ed5f9de fffff800`00257de5 00000000`00000000 00000000`000000de : nt!KiTimerExpiration+0x1be
    fffff800`00ba0f00 fffff800`0367b925 : 00000000`00000000 fffffa80`0cacab50 00000000`00000000 fffff880`016f8800 : nt!KiRetireDpcList+0x277
    fffff800`00ba0fb0 fffff800`0367b73c : fffffa80`00000000 fffff800`0367496f fffffa80`0cacab01 fffff800`036c499c : nt!KxRetireDpcList+0x5
    fffff880`035e0920 fffff800`036c4ad3 : fffff800`03674903 fffff800`0367496f 00000000`00000319 fffff800`037f5e80 : nt!KiDispatchInterruptContinue
    fffff880`035e0950 fffff800`0367496f : 00000000`00000319 fffff800`037f5e80 00000000`00000000 00000000`7d0acd48 : nt!KiDpcInterruptBypass+0x13
    fffff880`035e0960 fffff800`03633a44 : fffffa80`0cacac10 00000000`00000000 00000000`00000000 fffff800`0367e127 : nt!KiChainedDispatch+0x19f
    fffff880`035e0af0 fffff800`03633b47 : fffff800`037f5e80 fffffa80`0cacab50 fffffa80`0cacab50 fffff800`03633b64 : nt!KiExecuteAllDpcs+0x150
    fffff880`035e0bb0 fffff800`03917b8a : 00000000`00000000 fffffa80`0cacab50 00000000`00000080 fffffa80`0ca8d040 : nt!KiExecuteDpc+0xcb
    fffff880`035e0c00 fffff800`0366a8e6 : fffff880`03365180 fffffa80`0cacab50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`035e0c40 00000000`00000000 : fffff880`035e1000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {42f94646-13b7-b017-1e08-4befcf4d9f5e}
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa801869d4f0 1
    Irp is active with 3 stacks 2 is current (= 0xfffffa801869d608)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
    Flags = 00000000
    ThreadListEntry.Flink = fffffa801869d510
    ThreadListEntry.Blink = fffffa801869d510
    IoStatus.Status = c00000bb
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = 00000000
    UserEvent = 00000000
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = fffffa801869d568
    Tail.Overlay.Thread = 00000000
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = fffff8000382ad20
    Tail.Overlay.ListEntry.Blink = fffff8000382ad20
    Tail.Overlay.CurrentStackLocation = fffffa801869d608
    Tail.Overlay.OriginalFileObject = 00000000
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa800e465480 00000000 00000000-00000000    pending
    	       \Driver\nvlddmkm
    			Args: 00015400 00000001 00000004 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800df40c80    
    
    			Args: 00000000 00000000 00000000 00000000
    


    Wanikiya and Dyami--Team Zigzag

    Saturday, February 21, 2015 2:00 PM
  • Kudos to Team Zigzag.  Amazing what can be done with that secret decoder ring.  Have updated driver and will reboot now.  Will post asap if still having problems, or in a couple of days to say all seems good.

    Thanks for the help

    -Jay

    Saturday, February 21, 2015 2:24 PM
  • LJ

    Its not rocket science but thanks.  I was having far too many BSOD"S and decided to learn why.  Good Luck


    Wanikiya and Dyami--Team Zigzag

    Saturday, February 21, 2015 2:37 PM
  • THought I was okay, but got same BSOD this morning.  Could you check out this minidump and let me know what it points to?

    https://onedrive.live.com/redir?resid=E1F64F3885DAC395!132&authkey=!AAz8iFMNwU71okE&ithint=file%2czip

    Thanks again,

    -Jay

    Sunday, February 22, 2015 1:16 PM
  • LJ

    Still nVidia and you did not update to the newest driver available.  There is a Feb 2015 driver yours is from early 2014

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022215-11684-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*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
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`0364e000 PsLoadedModuleList = 0xfffff800`03892890
    Debug session time: Sun Feb 22 05:13:30.196 2015 (UTC - 5:00)
    System Uptime: 0 days 19:14:35.445
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800d459a10, fffff80005054748, fffffa801b0a5e10}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800d459a10, Physical Device Object of the stack
    Arg3: fffff80005054748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa801b0a5e10, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS: fffffa801b0a5e10
    
    DEVICE_OBJECT: fffffa800e19c480
    
    DRIVER_OBJECT: fffffa800e361300
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a
    
    MODULE_NAME: nvlddmkm
    
    FAULTING_MODULE: fffff8800f4e1000 nvlddmkm
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  CloudBerry.Bac
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    DPC_STACK_BASE:  FFFFF80005054FB0
    
    STACK_TEXT:  
    fffff800`050546f8 fffff800`03733b92 : 00000000`0000009f 00000000`00000003 fffffa80`0d459a10 fffff800`05054748 : nt!KeBugCheckEx
    fffff800`05054700 fffff800`036cecfc : fffff800`05054aa0 fffff800`05054aa0 00000000`00000000 00000000`00000010 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`050547a0 fffff800`036ceb96 : fffffa80`0e23f938 00000000`0043c146 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`05054810 fffff800`036cea7e : 000000a1`4b621301 fffff800`05054e88 00000000`0043c146 fffff800`03842b48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`05054e60 fffff800`036ce867 : fffffa80`0f5288eb fffff800`0043c146 00000000`00000000 00000000`0000003e : nt!KiTimerExpiration+0x1be
    fffff800`05054f00 fffff800`036c5925 : 00000000`00000000 fffffa80`15d72b50 00000000`00000000 fffff880`0164d800 : nt!KiRetireDpcList+0x277
    fffff800`05054fb0 fffff800`036c573c : fffffa80`00000000 00000000`00000002 00000000`ffffff01 00000000`00000001 : nt!KxRetireDpcList+0x5
    fffff880`0c770710 fffff800`0370ead3 : fffff800`036be903 fffff800`036be96f fffff880`0d3f3820 00000000`00000000 : nt!KiDispatchInterruptContinue
    fffff880`0c770740 fffff800`036be96f : fffff880`0d3f3820 00000000`00000000 00000000`00000004 00000000`00000000 : nt!KiDpcInterruptBypass+0x13
    fffff880`0c770750 fffff800`03697b3b : fffff800`0367089a 00000000`00000000 fffff880`009ed180 fffff880`009ed180 : nt!KiChainedDispatch+0x19f
    fffff880`0c7708e8 fffff800`0367089a : 00000000`00000000 fffff880`009ed180 fffff880`009ed180 00000000`00000001 : nt!KeSetSystemGroupAffinityThread+0x3
    fffff880`0c7708f0 fffff800`036ccf34 : 00000000`00000000 fffffa80`11bc5b30 fffffa80`0caeca40 00000000`00000000 : nt!KeFlushQueuedDpcs+0x196
    fffff880`0c7709a0 fffff800`039bc0b4 : fffffa80`11bc5b30 00000000`00000000 fffffa80`15d72b50 00000000`00000000 : nt!ObfDereferenceObject+0xd4
    fffff880`0c770a00 fffff800`039bc664 : 00000000`00000738 fffffa80`11bc5b30 fffff8a0`022baa20 00000000`00000738 : nt!ObpCloseHandleTableEntry+0xc4
    fffff880`0c770a90 fffff800`036c2153 : fffffa80`15d72b50 fffff880`0c770b60 00000000`7493473e fffffa80`19105b40 : nt!ObpCloseHandle+0x94
    fffff880`0c770ae0 00000000`758cd842 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`1a16f558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x758cd842
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {42f94646-13b7-b017-1e08-4befcf4d9f5e}
    
    Followup: MachineOwner
    ---------
    
    

       Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Jul 02 13:42:02 2014 (53B4446A)
        CheckSum:         00C4C7C9
        ImageSize:        00C8E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Tuesday, March 3, 2015 2:51 AM
    Sunday, February 22, 2015 1:29 PM
  • I used Windows Device Manager to get that 2014 updated driver.  Now I went to GEFORCE site and although this system is not used for gaming, I installed the Feb 2015 driver with its proactive monitoring.

    Will let you know if stable, though not sure why this has suddenly started to throw BSODs after a year or two.

    Thanks again for the assist!

    -Jay

    Sunday, February 22, 2015 2:18 PM
  • Jay

    You should not use device manager because even if it is the newest driver (it wasnt) the driver could be corrupt.  Drivers become corrupt all the time hence why it started crashing now


    Wanikiya and Dyami--Team Zigzag

    Sunday, February 22, 2015 2:29 PM
  • Hey Team Zigzag - haven't seen BSOD since updating driver (thanks), but now machine won't Sleep/Wakeup properly (I have to reboot from sleep).  Any connection or are the gremlins just out to get me?

    -Jay

    Tuesday, February 24, 2015 2:04 PM
  • Jay

    Happy to help.  Waking from sleep may still be the video driver but lets try something else.

    Please run powercfg -a from an elevated command prompt and tell us the results.


    Wanikiya and Dyami--Team Zigzag

    Wednesday, February 25, 2015 1:27 PM
  • It's weird - I can hear devices power up when I move the mouse, but no video (dual monitors return to powersave mode).  Here's powercfg info.  I appreciate your efforts to help debug this.

    -Jay


    C:\Windows\system32>powercfg -a
    The following sleep states are available on this system: Standby ( S3 ) Hibernate Hybrid Sleep
    The following sleep states are not available on this system:
    Standby (S1)
            The system firmware does not support this standby state.
    Standby (S2)
            The system firmware does not support this standby state.

    C:\Windows\system32>powercfg -devicequery wake_armed

    Microsoft USB Dual Receiver Wireless Mouse (IntelliPoint)
    Realtek PCIe GBE Family Controller
    Realtek PCI GBE Family Controller
    HID Keyboard Device
    HID-compliant mouse (004)
    Microsoft USB Dual Receiver Wireless Keyboard (IntelliType Pro)


    Wednesday, February 25, 2015 2:08 PM
  • LJ

    Have you checked for BIOS updates?

    What is the date on the current video driver?

    Please provide us with your Event Viewer administrative logs by following these steps:


    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post
    *
    If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem.  The work around is to edit the registry.  If you are not comfortable doing this DONT.  If you are, backup the key before you do
    Press Win+"R" and input regedit

    Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"


    Wanikiya and Dyami--Team Zigzag

    Wednesday, February 25, 2015 4:14 PM
  • Hey Team Zigzag,

    NVIDIA driver is 2/5/2015.  BIOS hasn't been updated in about 1 year - I'll check for updates next break I get.

    Event viewer content can be found at:
    https://onedrive.live.com/redir?resid=E1F64F3885DAC395!133&authkey=!AEmZzArY107vN0Y&ithint=file%2czip

    The VSS errors at 1:30am are due to Cloudberry Backup and don't seem to have any impact on the system. Their response to controlling the error is useless.

    As far as DELETING a registry entry, I am on Win 7 x64, so deprecated entry does not apply to me

    Thanks in advance,

    -Jay

    P.S. BIOS is most current GA version
    • Edited by Laserjay Wednesday, February 25, 2015 8:24 PM
    Wednesday, February 25, 2015 5:35 PM
  • Hello Jay,

    After update the display driver to the 2/5/2015, the BSOD is resolved? And you got a new issue about can’t wake up the monitor?

    Please take the following steps for troubleshooting:
    1. Try to use one single monitor and check if you can normally wake it up.
    2. Install the display card driver from the manufacturer website.
    3. Do you use both Intel HD Graphics and NVIDIA display card?
    If yes, please disable one and check if the issue still exists.

    Best regards,
    Fangzhou CHEN


    Fangzhou CHEN
    TechNet Community Support

    Friday, February 27, 2015 9:11 AM
  • Thanks for the suggestions - I'll let you know if it helps

    -Jay

    Friday, February 27, 2015 1:04 PM
  • Either update you BitDefender AV to the latest available, OR remove it and replace it with the free up to date Microsoft security Essentials

    Uninstall Tools for Bitdefender Products.

    http://www.bitdefender.com/uninstall/

    Microsoft Security Essentials

    http://windows.microsoft.com/en-US/windows/security-essentials-download

    0: kd> !thread fffffa8015d72b50
    GetPointerFromAddress: unable to read from fffff800038fc000
    THREAD fffffa8015d72b50  Cid 09c4.27c0  Teb: 000007fffff9c000 Win32Thread: 0000000000000000 RUNNING on processor 0
    Not impersonating
    GetUlongFromAddress: unable to read from fffff8000383bba8
    Owning Process            fffffa8011bc5b30       Image:         CloudBerry.Bac
    Attached Process          N/A            Image:         N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      4440705     
    Context Switch Count      16            
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address 0x000007fef6d293d4
    Stack Init fffff8800c770c70 Current fffff8800c7705c0
    Base fffff8800c771000 Limit fffff8800c76b000 Call 0
    Priority 30 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5

    Disable cloudberry backup, at least for temporary troubleshooting purposes

    update Chipset

    HECIx64.sys  Tue Oct 19 19:33:43 2010 (4CBE2AD7)

    update

    EtronHub3 EtronHub3.sys Mon Jul 25 17:30:59 2011 (4E2DE093)
    EtronXHCI EtronXHCI.sys Mon Jul 25 17:30:56 2011 (4E2DE090)

     Z68AP-D3 support and drivers.

    http://www.gigabyte.com/products/product-page.aspx?pid=4015#driver

    • Marked as answer by ZigZag3143x Tuesday, March 3, 2015 2:51 AM
    Saturday, February 28, 2015 5:26 AM
  • I've updated all drivers and excluded Cloudberry Backup from Bitdefender scanning - will see if that helps before getting any more aggressive.

    Thanks for the help

    -Jay

    Saturday, February 28, 2015 1:42 PM
  • Another BSOD occurred on wake-up from sleep, but monitor was not showing anything.  Anyone available to let me know what's in the minidump?

    https://onedrive.live.com/redir?resid=E1F64F3885DAC395!133&authkey=!AEmZzArY107vN0Y&ithint=file%2czip

    Thanks in advance

    -Jay

    Saturday, February 28, 2015 3:01 PM
  • LJ

    Still nVidia I am afraid.  May be time to start thinking about hardware.

    Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
    FurMark Setup:

    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
    - Click "Quit" to exit


    Wanikiya and Dyami--Team Zigzag

    Saturday, February 28, 2015 3:12 PM
  • Thanks Zigzag.  I'll try stress test at next break.  Any recommendations for a Dual DVI card used for business purposes only (not gaming) using hires 24" monitors?

    -Jay

    Saturday, February 28, 2015 3:28 PM
  • LJ

    I do not really know your requirements nor system specs.  I suspect you are better off Googling your needs.  Happy to help if you narrow down the field


    Wanikiya and Dyami--Team Zigzag

    Saturday, February 28, 2015 3:35 PM
  • Hey Zigzag - taking your advice I ordered a new card on Saturday and this morning the nVidia card died:)  If only it could have stayed alive until the new card arrived... I think it was the FurMark pounding that wore it out...  

    I guess those BSODs are sometimes good predictors of pending hw problems.

    Thanks for all your help

    -Jay

    P.S. limping along on old single video display card is torture... cannot go backwards without pain

    Tuesday, March 3, 2015 2:35 AM
  • LJ

    Thanks for letting us know.  Feel free to ask if you need help with the new card


    Wanikiya and Dyami--Team Zigzag

    Tuesday, March 3, 2015 2:50 AM