Computer died in it's sleep.


  1. Posts : 23
    Windows 7
       #1

    Computer died in it's sleep.


    At least, so far as I can tell. Here's the minidump file.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Twilit Soul said:
    At least, so far as I can tell. Here's the minidump file.
    \




    network driver. Simply re-install it. I would also remove Macaffee and replace with Microsoft security essentials.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\031911-18751-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`018ba4c0?
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`01a03000 PsLoadedModuleList = 0xfffff800`01c40e50
    Debug session time: Sat Mar 19 01:41:44.226 2011 (GMT-4)
    System Uptime: 0 days 15:22:20.007
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8003c96060, fffff800018ba4d8, fffffa8006713620}
    
    *** WARNING: Unable to verify timestamp for netw5v64.sys
    *** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
    Probably caused by : netw5v64.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8003c96060, Physical Device Object of the stack
    Arg3: fffff800018ba4d8, Functional Device Object of the stack
    Arg4: fffffa8006713620, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  fffffa8006713620
    
    DEVICE_OBJECT: fffffa8005016050
    
    DRIVER_OBJECT: fffffa8005022660
    
    IMAGE_NAME:  netw5v64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49cbab84
    
    MODULE_NAME: netw5v64
    
    FAULTING_MODULE: fffff8800344e000 netw5v64
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80001ae2273 to fffff80001a73740
    
    STACK_TEXT:  
    fffff800`018ba488 fffff800`01ae2273 : 00000000`0000009f 00000000`00000003 fffffa80`03c96060 fffff800`018ba4d8 : nt!KeBugCheckEx
    fffff800`018ba490 fffff800`01a7f29e : fffff800`018ba5c0 fffff800`018ba5c0 00000000`00000008 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
    fffff800`018ba530 fffff800`01a7edd6 : fffff800`01c19fc0 00000000`00362115 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`018ba5a0 fffff800`01a7f4be : 00000080`d9370245 fffff800`018bac18 00000000`00362115 fffff800`01bf0528 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`018babf0 fffff800`01a7ecb7 : 0000001a`812b9ec8 0000001a`00362115 0000001a`812b9ea0 00000000`00000015 : nt!KiTimerExpiration+0x1be
    fffff800`018bac90 fffff800`01a7beea : fffff800`01bede80 fffff800`01bfbc40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`018bad40 00000000`00000000 : fffff800`018bb000 fffff800`018b5000 fffff800`018bad00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_netw5v64.sys
    
    BUCKET_ID:  X64_0x9F_IMAGE_netw5v64.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 23
    Windows 7
    Thread Starter
       #3

    Ya know, I made this post and completely forgot about it until my computer blue screened from this same error right in my face.

    I did as you said, thanks =)
      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 20:14.
Find Us