BSOD's not saving minidumps, multiple 0x9F crashes

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #21

    Crap, sorry. Let me try to sort it out now.
      My Computer


  2. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #22

    I have downloaded the very same zip file and the DMP file IS there! It's 2/3's the way down the list of files and its named 022112-19999-01.dmp

    Here it is anyway:
      My Computer


  3. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #23

    Have you had a chance to look through the dump?
      My Computer


  4. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #24

    Anyone?
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #25

    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\piehole1983\022112-19999-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03049e90
    Debug session time: Mon Feb 20 19:14:48.912 2012 (UTC - 6:00)
    System Uptime: 0 days 0:24:54.005
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {4, 258, fffffa8003c40040, fffff80000b9c510}
    
    Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa8003c40040, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c510
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  fffffa8003c40040
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002f0cea6 to fffff80002e84640
    
    STACK_TEXT:  
    fffff800`00b9c4d8 fffff800`02f0cea6 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`03c40040 : nt!KeBugCheckEx
    fffff800`00b9c4e0 fffff800`030bf3cc : fffff800`00000000 fffffa80`00000000 fffff800`03004c00 fffff800`00b9cc58 : nt!PnpBugcheckPowerTimeout+0x76
    fffff800`00b9c540 fffff800`02e90062 : 00000000`0000000a fffff800`00000000 00000000`00000000 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
    fffff800`00b9c570 fffff800`02e8ff06 : fffff880`03e26ad0 fffff880`03e26ad0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02e8fdee : 00000003`7a7f22e8 fffff800`00b9cc58 00000000`00017618 fffff800`02ff9588 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02e8fbd7 : 00000000`c4adf1ce 00000000`00017618 00000000`c4adf10d 00000000`00000018 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02e7c36a : fffff800`02ff6e80 fffff800`03004cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  .thread 0xfffffa8003c40040 ; kb
    
    FOLLOWUP_IP: 
    nt!PnpBugcheckPowerTimeout+76
    fffff800`02f0cea6 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!PnpBugcheckPowerTimeout+76
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    FAILURE_BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76
    
    BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76
    
    Followup: MachineOwner
    ---------
    Does not identify what driver is causing the problem. Are you getting crashes still? Any new .dmp files?
      My Computer


  6. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #26

    Yes, every single time I shut down. Really frustrating! It still will not save any new dumps either! I think I'm looking at some kind of hardware issue but which part?
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #27

    Use the following to check hardware:
      My Computer


  8. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #28

    Thank you for the information! I started with realtemp and prime95 running together and almost instantly got CPU temps of 88 degrees and seems to be very slowly climbing!

    I'll let it run on for a while and see what happens.
      My Computer


  9. Posts : 32
    Windows 7 Home Premium 64bit
    Thread Starter
       #29

    Check it out after 3 minutes!
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #30

    Could you fill out your system specs? It is a bit annoying to have to search through both of your threads to find information about your system. System Info - See Your System Specs can be used as a guide to filling out the specs.

    Regardless, those temperatures seem very high. Have you blown the dust out of the system in the past six months?

    To remove dust, follow the subsequent general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
    5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
    6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
    7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
    8. Start the computer and see if performance is better.
      My Computer


 
Page 3 of 5 FirstFirst 12345 LastLast

  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 08:53.
Find Us