locked
Windows 7 Blue Screen Shutdown Error RRS feed

  • Question

  • My computer's been working fine with Internet and all, but I've had a couple problems in the past week: 1) it hasn't shut down or restarted properly, 2) my printer (Canon MX330) won't connect to the computer. I've gotten this Blue Screen image every time it's started back up unsuccessfully, and looking for help, I've seen many others have similar problems. I've tried System Restore, but now there are no points left since the ones from the last Automatic Updates wouldn't work. I've also tried a detailed Avast Antivirus scan. Found some infected files that were deleted, but that didn't solve the problem. I believe I installed a bad update. Now I've found and tried lots of ways that are either too advanced for me at this point or don't solve the problem, but here is my main error message and I made a folder for my dump files that I will post once my account's been verified.

    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033

    Additional information about the problem:
      BCCode: 1000009f
      BCP1: 0000000000000004
      BCP2: 0000000000000258
      BCP3: FFFFFA8005208B50
      BCP4: FFFFF800040464D0
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1

    Files that help describe the problem:
      C:\Windows\Minidump\100512-17830-01.dmp
      C:\Users\TnTnT\AppData\Local\Temp\WER-2165605-0.sysdata.xml


    Friday, October 5, 2012 8:09 PM

Answers

  • Looks like the BIOS is out of date, you might try the latest one.

    http://www.dell.com/support/drivers/us/en/19/Product/inspiron-545

    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.5, DMIVersion 37, Size=1498]
    BiosMajorRelease = 1
    BiosMinorRelease = 0
    BiosVendor = Dell Inc.
    BiosVersion = A11
    BiosReleaseDate = 09/07/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Inspiron 545
    SystemFamily = 
    SystemVersion = 00
    SystemSKU = 
    BaseBoardManufacturer = Dell Inc.
    BaseBoardProduct = 0N826N
    BaseBoardVersion = A03

    I looked at the most recent dump file, to get a clearer picture of what thread was blocking, we would need to look at a kernel memory dump (vs the minidumps that are being generated now)

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {4, 258, fffffa8005208b50, fffff80000b9c4d0}

    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: fffffa8005208b50, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c4d0

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


    DRVPOWERSTATE_SUBCODE:  4

    FAULTING_THREAD:  fffffa8005208b50

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80002d50e86 to fffff80002cc81c0

    STACK_TEXT: 
    fffff800`00b9c498 fffff800`02d50e86 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`05208b50 : nt!KeBugCheckEx
    fffff800`00b9c4a0 fffff800`02f0234c : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffff800`02ccd81a : nt!PnpBugcheckPowerTimeout+0x76
    fffff800`00b9c500 fffff800`02cd2e3c : fffffa80`07062c60 fffff880`00000000 fffffa80`40290000 00000000`00000001 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
    fffff800`00b9c530 fffff800`02cd2cd6 : fffffa80`085a4748 fffffa80`085a4748 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5a0 fffff800`02cd2bbe : 0000003d`e652b55a fffff800`00b9cc18 00000000`001a0109 fffff800`02e3d3a8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`02cd29a7 : 00000010`47dad7c6 00000010`001a0109 00000010`47dad723 00000000`00000009 : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`02cbfeca : fffff800`02e3ae80 fffff800`02e48cc0 00000000`00000000 fffff880`04893db0 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  .thread 0xfffffa8005208b50 ; kb

    FOLLOWUP_IP:
    nt!PnpBugcheckPowerTimeout+76
    fffff800`02d50e86 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:  4fa390f3

    FAILURE_BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

    BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

    Followup: MachineOwner

    • Marked as answer by TFlaherty Wednesday, October 17, 2012 2:11 PM
    Tuesday, October 9, 2012 2:02 PM
  • Hi,<o:p></o:p>


    I noticed that you have a lot of drivers have not been updated to the latest version. You may update them from the manufactory’s website one by one for a test.


    Kim Zhou

    TechNet Community Support

    • Marked as answer by TFlaherty Wednesday, October 17, 2012 2:09 PM
    Thursday, October 11, 2012 2:48 AM

All replies

  • The link to the minidump files does not appear to work.

    Can you try again?

    Make sure the minidump files are in a "public folder" "shared with everyone".

    Saturday, October 6, 2012 3:12 AM
  • My apologies, here's the public link:

    https://skydrive.live.com/redir?resid=C10248EBA96C7EEB!493

    Saturday, October 6, 2012 3:30 AM
  • The problem may be the wireless adapter driver, the netr7364.sys.

    Here's a "summary" of one of the crashes:

    BUCKET_ID:  X64_0x9F_3_netr7364_IMAGE_usbhub.sys

    The netr7364.sys is dated Mar 12, 2009 and should be updated if possible.

    What wireless adapter do you have and can you obtain a more recent driver?

    Also, recent minidump files show that both Avast and Microsoft Security Essentials are installed with "real-time" protection enabled.

    I would suggest to uninstall one of these applications. For troubleshooting I would suggest to uninstall Avast.

    Saturday, October 6, 2012 4:39 AM
  • I have a Linksys USB which is a few years old, so it should be updated. My desktop is a Dell Intel Premium which doesn't have built in wireless, but I have a Drivers disc I could use; however, I would need to set up an IP address I probably don't have. I'll try uninstalling Avast, but I doubt it's the root of the problem.
    Saturday, October 6, 2012 2:18 PM
  • When I rebooted to uninstall Avast, it restarted normally, but when I shut down, the same Blue Screen issue occurs. Are there any other possibilities? I turned my UAC down lower and have installed VMWorkstation, and this has only happened after these occurrences. If these aren't scapegoats for the problem(s), then I will buy a new wireless adapter.
    Saturday, October 6, 2012 5:45 PM
  • The issue may be solely with the wireless adapter.

    Can you locate the wireless adapter in the Device Manager and right-click the device > Properties > Details, then choose "Hardware Ids" from the drop-down menu under "Property".

    What is listed under "Value"?

    Sunday, October 7, 2012 9:20 PM
  • These are what I get:

    USB\VID_13B1&PID_0020&REV_0001
    USB\VID_13B1&PID_0020
    Monday, October 8, 2012 3:12 AM
  • The Hardware Ids would indicate that is a (Linksys) Compact Wireless G USB Adapter and there should be an updated driver available via Windows Update.

    In the Device Manager, can you right-click the wireless adapter > Update driver software > Search automatically for updated driver software

    Hopefully that will update the driver to a more stable version.

    Monday, October 8, 2012 3:26 PM
  • Can you upload the latest dump files for analysis?
    Monday, October 8, 2012 7:12 PM
  • auggy: It says the USB software is up to date. This might not be entirely true, however.

    Mike: I created the folder Dump2 below

    https://skydrive.live.com/#cid=C10248EBA96C7EEB&id=C10248EBA96C7EEB%21493

    I also tried using System Restore again, but get the error that the creation of a shadow copy has timed out.

    Monday, October 8, 2012 9:06 PM
  • auggy: It says the USB software is up to date. This might not be entirely true, however.

    Try the following:

    Device Manager > right-click the wireless adapter and select "Uninstall" and also select "Delete the driver software for this device".

    Restart the computer and let Windows reinstall the device and driver.

    I might also suggest to visit the Realtek site and obtain an updated driver for the high definition audio and network adapter as you are running older version of these drivers.

    Tuesday, October 9, 2012 1:33 AM
  • Hi,


    After analyzing your latest dump file, here is the result.


    BugCheck 9F, {4, 258, fffffa8005208b50, fffff80000b9c4d0}

    Implicit thread is now fffffa80`05208b50

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

    Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

    Followup: MachineOwner

    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: fffffa8005208b50, The thread currently holding on to the Pnp lock.

    Arg4: fffff80000b9c4d0, nt!TRIAGE_9F_PNP on Win7


    This issue occurs can be caused by the power state transition timed out waiting to synchronize with the PnP subsystem.


    You may refer to this website and find the solution.

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx


    Note, please read
    Debugging bug check 0x9F when Parameter 1 equals 0x4” part.


    Kim Zhou

    TechNet Community Support

    Tuesday, October 9, 2012 7:24 AM
  • Looks like the BIOS is out of date, you might try the latest one.

    http://www.dell.com/support/drivers/us/en/19/Product/inspiron-545

    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.5, DMIVersion 37, Size=1498]
    BiosMajorRelease = 1
    BiosMinorRelease = 0
    BiosVendor = Dell Inc.
    BiosVersion = A11
    BiosReleaseDate = 09/07/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Inspiron 545
    SystemFamily = 
    SystemVersion = 00
    SystemSKU = 
    BaseBoardManufacturer = Dell Inc.
    BaseBoardProduct = 0N826N
    BaseBoardVersion = A03

    I looked at the most recent dump file, to get a clearer picture of what thread was blocking, we would need to look at a kernel memory dump (vs the minidumps that are being generated now)

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {4, 258, fffffa8005208b50, fffff80000b9c4d0}

    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: fffffa8005208b50, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c4d0

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


    DRVPOWERSTATE_SUBCODE:  4

    FAULTING_THREAD:  fffffa8005208b50

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80002d50e86 to fffff80002cc81c0

    STACK_TEXT: 
    fffff800`00b9c498 fffff800`02d50e86 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`05208b50 : nt!KeBugCheckEx
    fffff800`00b9c4a0 fffff800`02f0234c : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffff800`02ccd81a : nt!PnpBugcheckPowerTimeout+0x76
    fffff800`00b9c500 fffff800`02cd2e3c : fffffa80`07062c60 fffff880`00000000 fffffa80`40290000 00000000`00000001 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
    fffff800`00b9c530 fffff800`02cd2cd6 : fffffa80`085a4748 fffffa80`085a4748 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5a0 fffff800`02cd2bbe : 0000003d`e652b55a fffff800`00b9cc18 00000000`001a0109 fffff800`02e3d3a8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`02cd29a7 : 00000010`47dad7c6 00000010`001a0109 00000010`47dad723 00000000`00000009 : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`02cbfeca : fffff800`02e3ae80 fffff800`02e48cc0 00000000`00000000 fffff880`04893db0 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  .thread 0xfffffa8005208b50 ; kb

    FOLLOWUP_IP:
    nt!PnpBugcheckPowerTimeout+76
    fffff800`02d50e86 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:  4fa390f3

    FAILURE_BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

    BUCKET_ID:  X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

    Followup: MachineOwner

    • Marked as answer by TFlaherty Wednesday, October 17, 2012 2:11 PM
    Tuesday, October 9, 2012 2:02 PM
  • auggy: I tried both of these things (High Definition Audio from Realtek), but either they were too slow or just went nowhere.

    Kim: That definitely explains part of it, kernal dumps are too advanced for me at this point however.

    Mike: I did successfully update the BIOS. The computer still didn't restart properly though.

    Thanks for the help, everyone. I'm sure the main problem is PnP related, but it's just so hidden right now.

    Wednesday, October 10, 2012 12:47 PM
  • Hi,<o:p></o:p>


    I noticed that you have a lot of drivers have not been updated to the latest version. You may update them from the manufactory’s website one by one for a test.


    Kim Zhou

    TechNet Community Support

    • Marked as answer by TFlaherty Wednesday, October 17, 2012 2:09 PM
    Thursday, October 11, 2012 2:48 AM
  • I believe I've downloaded all the urgent and some recommended updates. However, I don't know which destination I should choose with the Firmware update. Do you want me to upload a more recent dump folder?
    Friday, October 12, 2012 8:45 PM
  • Hi,


    You’d better to download and install the latest driver from Manufactory’s website instead of Microsoft Update. Please check the graphics card’s driver first.


    Kim Zhou

    TechNet Community Support

    Monday, October 15, 2012 5:25 AM
  • I meant the updates from Dell's website. Where is the best place to check the graphics card?
    Monday, October 15, 2012 8:07 PM
  • Hi,


    If your graphics card is ATI series, please check the update here.

    http://support.amd.com/us/Pages/AMDSupportHub.aspx


    Please Note: Microsoft provides third-party information to help you find technical support. This information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


    If your graphics card is NVidia series, please check the update here.

    http://www.nvidia.com/Download/index.aspx?lang=en-us


    Please Note: Microsoft provides third-party information to help you find technical support. This information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


    You should know the exact model of your graphics card. 


    Kim Zhou

    TechNet Community Support

    Tuesday, October 16, 2012 2:17 AM
  • Kim, I have an Intel(R) G33/G31 Express Chipset Family model and it says it's up to date. Should I replace it anyway?
    Tuesday, October 16, 2012 3:43 AM
  • Okay, it's shut down properly, thanks everyone! I'll say if it's too soon and more errors occur though.
    Wednesday, October 17, 2012 2:14 PM