Long Shut Down To Blue Screen

Page 1 of 4 123 ... LastLast

  1. Posts : 16
    Windows 7 Home Primium 64bit
       #1

    Long Shut Down To Blue Screen


    I was restarting my computer today and it took about 5 minutes on the shutdown screen then came the blue screen. The blue screen was not up long but when the computer was starting up it took like 4 times longer than normal. Windows gave me this "Windows has recovered from unexpected shut down"
    Code:
    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:    FFFFFA80036EB040
      BCP4:    FFFFF80000B9C510
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    768_1
    
    Files that help describe the problem:
      C:\Windows\Minidump\082513-15522-01.dmp
      C:\Users\MastonMadHouse\AppData\Local\Temp\WER-135830-0.sysdata.xml
      My Computer


  2. Posts : 5,440
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
       #2

    Hi and Welcome to the Forum. This would be much better for you - There is a special BSOD Help and Support Forum, Scroll down from the General Discussion Forum and you will see it. There you will get expert support. Just copy and paste your post and put it there. Get results quicker that way.
      My Computer


  3. Posts : 3,056
    Windows 10
       #3
      My Computer


  4. Posts : 16
    Windows 7 Home Primium 64bit
    Thread Starter
       #4

    Alright here you go.
      My Computer


  5. Posts : 3,056
    Windows 10
       #5

    The cause of your bugchecks are to be attributed to an Anti-Virus Company:
    Code:
    DRIVER_POWER_STATE_FAILURE (9f)
    
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
        subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa80036eb040, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c510, nt!TRIAGE_9F_PNP on Win7
    • A driver has failed to complete a power IRP within a specific time (usually 10 minutes).



    Code:
    fffff880`039aea08  fffff880`051bc4fb kneps+0xa4fb
    fffff880`039aea38  fffff880`051b98aa kneps+0x78aa
    fffff880`039aec50  fffff880`051d44f0 kneps+0x224f0
    fffff880`039aeca8  fffff880`04be2615 kltdi+0x5615
    fffff880`039aecd8  fffff880`04be8288 kltdi+0xb288
    fffff880`039aede8  fffff880`04bdfc41 kltdi+0x2c41



    We know those drivers belong to Kaspersky.
    Code:
    Start Menu\Programs\Kaspersky Internet Security 2013
    Remove Kaspersky Internet Security 2013 using the removal tool.

    Disable the power savings setting for your NVIDIA nForce Networking Controller:


    • Start Menu, search for compmgmt.msc and press enter.

    • Expand Network adapters and select the internet conection that is currently being used (yours should say NVIDIA nForce Networking Controller).
    • Double click the appropriate adapter and choose the Power Management tab, then un-check the checkbox corresponding to Allow the computer to turn off this device to save power
    • OK to confirm the operation.



    Keep us posted :) .
      My Computer


  6. Posts : 16
    Windows 7 Home Primium 64bit
    Thread Starter
       #6

    So the Blue Screen Of Death was from a Kaspersky driver? Is Microsoft security essentials a good virus protection?
      My Computer


  7. Posts : 5,440
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
       #7

    TipTricky said:
    So the Blue Screen Of Death was from a Kaspersky driver? Is Microsoft security essentials a good virus protection?
    MSE is highly recommended. (IMHO)
      My Computer


  8. Posts : 16
    Windows 7 Home Primium 64bit
    Thread Starter
       #8

    Alright then i guess ill stop spending money on a virus protection haha. Ill post back if the BSOD happens again. ANy ideas why it would happen out of the blue like it did?
      My Computer


  9. Posts : 3,056
    Windows 10
       #9

    I second Mitchell on this one, MSSE is well regarded here and we suggest it almost unanimously.
    Why it decided to happen all of a sudden, is a tough question to make.
    Minidumps don't contain much information and are a bit iffy as to what they do retain at the time of the crash
    an what they leave out there is no rhythm to it.
    On top of it we only have access to the public symbol server (it basically phrases the drivers and the like to
    an understandable form for us to read) which is why I couldn't find the symbol for argument 4.
    Code:
    dt nt!TRIAGE_9F_PNP fffff80000b9c510 Symbol nt!TRIAGE_9F_PNP not found.
    So had to go with the stack:
    Code:
    00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    00000444`00000000 00000007`ffffffff : nt!KiCommitThreadWait+0x1d2
    00000000`00000000 fffff880`0531d700 : nt!KeWaitForSingleObject+0x19f
    00000000`00000000 fffff880`01d2c101 : ndis! ?? ::LNCPHCLB::`string'+0x4f4b
    fffffa80`0852ba00 fffffa80`036927f0 : ndis!ndisPnPNotifyAllTransports+0x18f
    fffffa80`0852ba50 fffff880`039af740 : ndis!NdisFNetPnPEvent+0xd2
    fffffa80`03922010 fffff880`039af740 : ndis!NdisFNetPnPEvent+0xa0
    fffffa80`091ac1a0 00000000`00000002 : ndis!NdisFNetPnPEvent+0xa0
    fffff880`01d2c110 fffffa80`091ac1a0 : ndis!ndisDevicePnPEventNotifyFiltersAndAllTransports+0x128
    00000000`00000000 fffffa80`07adb6e0 : ndis!ndisPnPQueryRemoveDevice+0x88
    fffff880`039af970 fffff800`02fdde00 : ndis!ndisPnPDispatch+0x4d4
    00000000`00000000 00000000`00000001 : nt!PnpAsynchronousCall+0xce
    fffff880`039afb40 fffff880`039afc38 : nt!PiIrpQueryRemoveDevice+0xda
    fffff880`039afb40 00000000`00000000 : nt!PnpQueryRemoveLockedDeviceNode+0x67
    fffff8a0`00ec7e10 ffffe7e1`c7dc0f3a : nt!PnpDeleteLockedDeviceNode+0x8d
    fffffa80`04278890 fffff8a0`0faa1a20 : nt!PnpDeleteLockedDeviceNodes+0xa0
    fffffa80`036eb000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x864
    fffff8a0`0faa1a20 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
    fffff800`030832d8 fffffa80`036eb040 : nt! ?? ::NNGAKEGL::`string'+0x551ab
    fffff800`03054e80 fffffa80`036eb040 00000000`00000080 fffffa80`036d8040 : nt!ExpWorkerThread+0x111
    fffff880`0376dfc0 fffff880`03763180 : nt!PspSystemThreadStartup+0x5a
    fffff880`039af9e0 00000000`00000000 : nt!KxStartSystemThread+0x16
    ndis being a legitimate Windows driver it is unlikely that it is the culprit.
    Then I called the RAW stack in search for clues, keeping in mind network related drivers.
    Sure enough Kaspersky Network filtering component &
    Kaspersky KNEPS Power driver were present
    and were consistent across both dumps.
    Other drivers are present in the stack trace and should be updated but giving it is the
    infamous nForce chipset as long as they don't cause any issues its best they are left alone.
    Hope this is suffice :) .
    Do post back here if other issues arise.
    Last edited by YoYo155; 26 Aug 2013 at 06:13. Reason: typos
      My Computer


  10. Posts : 16
    Windows 7 Home Primium 64bit
    Thread Starter
       #10

    Ok well i have a huge problem now. I decided tonight i would go ahead and switch to MSSE and remove kespersky. I downloaded the remover for kespersky and the installer for MSSE. I ran the remover and the computer restared itself and when it rebooted it froze. Now the computer boots windows and freezes seconds later. I need help.
      My Computer


 
Page 1 of 4 123 ... 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:34.
Find Us