locked
Need help with a minidump file please RRS feed

  • Question

  • Hey everyone:

    Over the last few days I've had a significant BSOD's appear. minidump files have been generated, but I'm absolutely clueless as to how to diagnose these, and am hoping some people would be able to help me understand what's causing the problem!

    I've uploaded the minidump file to skydrive here:

    https://skydrive.live.com/?cid=857bd9e866db4d4a&id=857BD9E866DB4D4A!121

    Would appreciate any and all help!

    Thanks everyone!

    Thursday, February 9, 2012 1:25 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa800f8e9a10, Physical Device Object of the stack
    Arg3: fffff80000ba2748, Functional Device Object of the stack
    Arg4: fffffa800f8dd910, The blocked IRP


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


    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys


    DRVPOWERSTATE_SUBCODE:  3


    IMAGE_NAME:  pci.sys


    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f


    MODULE_NAME: pci


    FAULTING_MODULE: fffff88000fa9000 pci


    CUSTOMER_CRASH_COUNT:  1


    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


    BUGCHECK_STR:  0x9F


    PROCESS_NAME:  PDAgent.exe


    CURRENT_IRQL:  2


    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`02ef2cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0f8e9a10 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`02e905fc : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00ba27a0 fffff800`02e90496 : fffffa80`12f7dc68 fffffa80`12f7dc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba2810 fffff800`02e9037e : 00000002`51f96760 fffff800`00ba2e88 00000000`0000f987 fffff800`02ffe368 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`02e90167 : fffffa80`10991dc3 fffffa80`0000f987 00000000`00000000 00000000`00000087 : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02e87765 : 00000000`00000000 fffffa80`11c5e060 00000000`00000000 fffff880`06338664 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02e8757c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`09dfdaa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue




    STACK_COMMAND:  kb


    FOLLOWUP_NAME:  MachineOwner


    FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys


    BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys


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

    --------------------------------------------------------

    Bug Check Code 0x9F: http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    Please start by updating NVIDIA drivers and check results. Possible that the BSOD was caused by nvlddmkm.sys driver.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Edited by Mr XMVP Saturday, February 11, 2012 9:01 PM
    • Marked as answer by FireMyst Sunday, February 12, 2012 9:28 AM
    Saturday, February 11, 2012 9:00 PM

All replies

  • Hmmm... with all the brilliant people on here nobody's been able to assist?

    *bump*

    Friday, February 10, 2012 2:19 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa800f8e9a10, Physical Device Object of the stack
    Arg3: fffff80000ba2748, Functional Device Object of the stack
    Arg4: fffffa800f8dd910, The blocked IRP


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


    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys


    DRVPOWERSTATE_SUBCODE:  3


    IMAGE_NAME:  pci.sys


    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f


    MODULE_NAME: pci


    FAULTING_MODULE: fffff88000fa9000 pci


    CUSTOMER_CRASH_COUNT:  1


    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


    BUGCHECK_STR:  0x9F


    PROCESS_NAME:  PDAgent.exe


    CURRENT_IRQL:  2


    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`02ef2cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0f8e9a10 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`02e905fc : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00ba27a0 fffff800`02e90496 : fffffa80`12f7dc68 fffffa80`12f7dc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba2810 fffff800`02e9037e : 00000002`51f96760 fffff800`00ba2e88 00000000`0000f987 fffff800`02ffe368 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`02e90167 : fffffa80`10991dc3 fffffa80`0000f987 00000000`00000000 00000000`00000087 : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02e87765 : 00000000`00000000 fffffa80`11c5e060 00000000`00000000 fffff880`06338664 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02e8757c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`09dfdaa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue




    STACK_COMMAND:  kb


    FOLLOWUP_NAME:  MachineOwner


    FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys


    BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys


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

    --------------------------------------------------------

    Bug Check Code 0x9F: http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    Please start by updating NVIDIA drivers and check results. Possible that the BSOD was caused by nvlddmkm.sys driver.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Edited by Mr XMVP Saturday, February 11, 2012 9:01 PM
    • Marked as answer by FireMyst Sunday, February 12, 2012 9:28 AM
    Saturday, February 11, 2012 9:00 PM
  • Thank you so much!

    So looking through this does this it's essentially saying the nvlddmkm.sys driver is bad.

    What about the line that says:

    PROCESS_NAME:  PDAgent.exe

    Is that anything I need to be concerned about?

    Sunday, February 12, 2012 9:27 AM
  • Thank you so much!

    So looking through this does this it's essentially saying the nvlddmkm.sys driver is bad.

    What about the line that says:

    PROCESS_NAME:  PDAgent.exe

    Is that anything I need to be concerned about?

    That means that the BSOD occured when PDAgent.exe process was running. More about it: http://file.net/process/pdagent.exe.html



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Sunday, February 12, 2012 9:37 AM
  • Being a novice to this, would you be able to tell me what program you used to run this analysis please?

    nVidia drivers have been updated, but the issue is still recurring.

    Thanks!

    Tuesday, February 14, 2012 3:12 AM
  • The above is a basic !analyze output from the Microsoft WinDbg tool. The actual output can be a great aid in determining the cause of problems. Unfortunately, interpreting that basic output and using the correct follow up commands to enable an educated guess at the real cause is a skill most of us have yet to acquire.

    What seems to have happened in this BSOD is that a bad driver has corrupted (loaded into) the memory address already allocated by Windows kernel to the nVidia graphics driver - thus the initial error looks like the graphics driver was at fault - it's not.

    I see you have drivers loaded from Saitek that pre-date the launch of even the public Beta of Windows 7, these will need to be updated or uninstalled.

    The NEC Electronics USB 3.0 Host Controller Driver has previously been seen to have issues with BSOD's, please update it - http://www.renesas.com/supp/ or disable it in the BIOS for the duration of testing.

    Please check for an updated driver for the HuaweiWiMAXUSB.sys, I guess it's a USB wireless dongle - if you cannot find a driver from within the last 6 months or so, please uninstall it and remove the drivers - the wireless USB drivers for dongles are beginning to get a reputation for BSOD's (I suspect that some of them may just be 'hacked' versions of Vista drivers).

    There are many other drivers that need updating - from the chip makers sites, not from Microsoft/Windows Update - but I think the above drivers are most likely to include the bad one.

    If you have further dumps, please upload them and link to them here.

    The more detail you can give us on the events immediately leading up to and during the event, the better equipped we will be to spot the offender!

    EDIT: most of the 'brilliant people' in the BSOD field are actually much more active on forums with a decent structure that enables them some measure of collaboration and control within their own areas of expertise.

    • Edited by satrow Tuesday, February 14, 2012 7:42 AM
    Tuesday, February 14, 2012 7:33 AM
  • Hi there:

    Thanks for your reply!

    I've had the issue happen to me twice today. Both times they occurred while I was browsing websites in firefox 10. The Wimax is Huawei's BM358 wimax USB stick for mobile broadband. I could not find any updated drivers for it from Huawei's website -- only manuals. My current driver version on that is 4.6.2.5 dated 11/5/2010.

    Here are links to the latest 2 minidump files:

    https://skydrive.live.com/redir.aspx?cid=857bd9e866db4d4a&resid=857BD9E866DB4D4A!122&parid=857BD9E866DB4D4A!118&authkey=!AApk2SAq-YlwcFA

    and

    https://skydrive.live.com/redir.aspx?cid=857bd9e866db4d4a&resid=857BD9E866DB4D4A!123&parid=857BD9E866DB4D4A!118&authkey=!AN0ePBPf7GfDR3o

    So any help would be appreciated with these to help me figure out what's going on!

    Lastly, where do you see the Saitek drivers from? I went through every item in my device manager and there wasn't one driver listed with Saitek as the manufacturer.

    The issues are occurring on an Alienware M17X-R3 laptop if that helps?

    Thank you!

    Tuesday, February 14, 2012 2:59 PM
  • Here's the list of Saitek drivers:

    Sahdad64.sys Unknown driver - suspect it's part of Saitek device (Saitek HDD Filter Driver), http://www.saitek.com/uk/down/drivers.php
    Saibad64.sys Saitek Volume Filter Driver, http://www.saitek.com/uk/down/drivers.php
    SaibVdAd64.sys Saitek Virtual Disk Driver, http://www.saitek.com/uk/down/drivers.php
    All dated within seconds of each other, Oct 2008, predating the W7 public Beta, considering the data here (from Sysnative.com), it looks like it's for a virtual CD/DVD (rather than the Saitek gaming peripherals I normally associate them with). The software installed may be rebranded, maybe OEM = Alienware? Many virtual CD/DVD drivers, esp. older ones, for W7 are known to cause BSOD's = update them if you can

    The latest dumps are both 0x9f (consistent is good):
    STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE
    Usual causes:  Device driver

    There's a link to a MSFT kb article and available Hotfix that looks like it fits your problem pretty closely: 0x9F Stop error

    One dump debug, probably very close to Mr X's above:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa800db14060, fffff80000b9c3d8, fffffa80126e4200}

    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : pci.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: fffffa800db14060, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, Functional Device Object of the stack
    Arg4: fffffa80126e4200, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  pci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

    MODULE_NAME: pci

    FAULTING_MODULE: fffff88000fba000 pci

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    STACK_TEXT:  
    fffff800`00b9c388 fffff800`02ef8cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0db14060 fffff800`00b9c3d8 : nt!KeBugCheckEx
    fffff800`00b9c390 fffff800`02e965fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00b9c430 fffff800`02e96496 : fffff880`00f832b0 00000000`0000aad2 00000000`00000000 00000001`04070400 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c4a0 fffff800`02e9637e : 00000001`969e8c7a fffff800`00b9cb18 00000000`0000aad2 fffff800`03004cc8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9caf0 fffff800`02e96167 : fffff800`03000ec2 fffffa80`0000aad2 fffffa80`10665370 00000000`000000d2 : nt!KiTimerExpiration+0x1be
    fffff800`00b9cb90 fffff800`02e8296a : fffff800`03000e80 fffff800`0300ecc0 00000000`00000000 fffff880`042446bc : nt!KiRetireDpcList+0x277
    fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

    BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

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

    Bottom line: WiFi drivers look well fitted for this crash, possibly aided and abetted by the USB3 drivers, with a BIOS that has ??? over it. If you uninstall the Huawei (as no drivers seem to be available for it) and use a wired connection for a few days, you should be able to prove the case.

    If not, it's back one step to USB and then BIOS. It might be worthwile checking posts on Dell/Alienware for similar problems too.

    Tuesday, February 14, 2012 4:24 PM
  • Thanks for this!

    I requested the hotfix from Microsoft and will let yo uknow how that goes.

    Unfortunately, being in rural Australia the Huawei is my only connection to the internet, so one way or the other I need that to be able to connect.

    Thanks for the info on those Saitek drivers as well. I will have to see if I can do further research to see where they're installed and what this computer is using them for.

    Tuesday, February 14, 2012 5:19 PM
  • Here's the interesting thing regarding the Saitek drivers:

    1) go to their website that you provided: http://www.saitek.com/uk/down/drivers.php. None of those options for download specify a virtual drive of any sort that I could decipher.

    2) having done a google search, several websites indicate that these files are from Sonic Solutions. To me, that makes more sense because Sonic (formerly Roxio) produced things like Cd/DVD creator software which used such drives. However, nowhere on Roxio's website could I find a download page to get the latest for those drivers.

    Here's a few websites which seems to think those files are from Sonic Solutions rather than saitek:

    http://www.dllerrors-fix.com/dllerrors/SaibVdAd64.sys.html

    http://systemexplorer.net/filereviews.php?fid=4148001

    Any thoughts?

    EDIT: I've read elsewhere that those files could be related to the Roxio SAIB service, Roxio Harddrive, and BOT4Service services. So I've gone into Windows Services and set them to manual instead of "automatic" startup. We'll see if that makes a difference over the next couple of days.


    • Edited by FireMyst Tuesday, February 14, 2012 6:10 PM
    Tuesday, February 14, 2012 5:55 PM
  • No worries, here in the UK there are still areas that eveb that mthod wouldn't be sufficient, but finding a make/model with known good drivers for W7 is still a lottery. I hope the Hotfix will patch at least some of the weaknesses I think I see in your logs.

    The Saitek drivers could well have been bought, sold, rented, leased, from any of those places, it's a bloody shame they (or Dell/Alienware) don't make an honest, open attempt to keep the drivers updated. MagicISO is one piece of clean freeware that, I think, will do the same job - as far as I know, it doesn't seem to trigger the problems that most of the other brands of virtual CD/DVD do, get it from Majorgeeks or the makers site. Doublecheck with Alienware that there isn't a software update for it first, it may be an improvement.

    On a related level, it's becoming increasingly difficult to find honest sources of files using a simple search, most of the top 20+ hits will be almost entirely populated by affiliate software sites, all designed to get you to download crapware that is alleged to fix your problem. Some of their articles are good, shamelessly stolen from honest sources - their downloads could contain anything.

    Good luck!

    Tuesday, February 14, 2012 9:40 PM
  • The Microsoft hotfix hasn't resolved the problem.

    It just happened to me tonight while the computer was shutting down!

    Would someone be able to analyze the following minidump file for me please? this is the one that occurred while the computer was shutting down:

    https://skydrive.live.com/redir.aspx?cid=857bd9e866db4d4a&resid=857BD9E866DB4D4A!124&parid=857BD9E866DB4D4A!118&authkey=!AN8X-m3cFyq1Ic0

    This only started happening within the last month and is getting to be a right pain in the arse.

    THanks!

    Sunday, February 19, 2012 12:00 PM
  • You're going to need to disable all the potentially bad and old drivers if you cannot update or uninstall them, otherwise you're just doing the same loop.

    Is your Alienware a laptop, with dual (Intel + nVidia) switchable graphics?

    Another 0x9F dump, showing the same nVidia driver as corrupt as all the others - have you updated this driver yet, from Dell/Alienware or nVidia?

    The dumps are all consistent in the bottom lines too, blaming Acpi, the driver that controls power-saving states. Start in the BIOS, set power saving to OFF when running on AC and disable any overclocking. Boot into Windows and go to the Control Panel > Power and set everything to not save power when on AC. Then move to the Device Manager and check the properties of both network adapters to NOT allow them to turn off to save power.

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Loading Dump File [C:\Windows\Minidump\021912-15334-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03051670
    Debug session time: Sun Feb 19 11:50:35.965 2012 (UTC + 0:00)
    System Uptime: 0 days 0:11:36.839
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa800db36a10, fffff80000b9c3d8, fffffa8010bb8590}

    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : pci.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: fffffa800db36a10, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, Functional Device Object of the stack
    Arg4: fffffa8010bb8590, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  pci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

    MODULE_NAME: pci

    FAULTING_MODULE: fffff88000d5f000 pci

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    STACK_TEXT:  
    fffff800`00b9c388 fffff800`02ef6cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0db36a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
    fffff800`00b9c390 fffff800`02e945fc : fffff800`00b9c4d8 fffff800`00b9c4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00b9c430 fffff800`02e94496 : fffff880`03dcb990 fffff880`03dcb990 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c4a0 fffff800`02e9437e : 00000001`9f5951bb fffff800`00b9cb18 00000000`0000ae7c fffff800`03002208 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9caf0 fffff800`02e94167 : 00000000`5d183ac3 00000000`0000ae7c 00000000`5d183afe 00000000`0000007c : nt!KiTimerExpiration+0x1be
    fffff800`00b9cb90 fffff800`02e8096a : fffff800`02ffee80 fffff800`0300ccc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

    BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

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

    EDITED: To add 3 threads that may be of interest to you:

    http://www.techsupportforum.com/forums/f299/bsod-help-594292.html

    http://www.techsupportforum.com/forums/f299/solved-driver-power-state-failure-bsod-592946.html

    http://www.techsupportforum.com/forums/f299/solved-bsod-while-playing-league-of-legends-582485.html

    • Edited by satrow Monday, February 20, 2012 1:04 AM
    Monday, February 20, 2012 12:59 AM
  • Ok, without jinxing things, I think I finally got it.

    After this last analysis (thanks!) I uninstalled some Epson Printer drivers, Roxio 2012, and downgraded the Nvidia drivers from 285.69 to 285.62.

    So far it has been a week with no issues.

    Hopefully I'll reinstall Roxio and then everything will still be schweet (I don't need the printer drivers installed).

    Thanks for your help everyone! I really appreciate your time!

    Monday, February 27, 2012 9:58 AM
  • That ties in well with my earlier suspicions regarding USB as being a possible culprit, I just wish there was a shortcut to learning how to debug these things efficiently. I'll keep trying ;)

    I hope that you have sorted now!

    Monday, February 27, 2012 11:31 AM
  • Hi,

    If you run into this error again, feel free to use the second link below for troubleshooting. The post provides detailed instructions on troubleshooting various BSOD errors...
    Monday, February 27, 2012 7:07 PM