Driver Power State Failure, ntoskrnl.exe?

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 6,458
    x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
       #21

    Ok, great, and good news about best behavoir.
    I think yo're saying that things are better, but I want to be sure.

    But mon ami, you can be of more help
    Did you download / install the driver from my link, reinstall the driver you downloaded before, or use the Nvidia detect?

    Did another BSOD occur or are you in the clear for the moment? You attached a diag and describe sluggishness before a BSOD.

    Is what you describe something that occurred in the past or is this a new BSOD?

    Thanks for the feedback,
    Bill
    .
    Palladion said:
    Slartybart said:
    What enabled you to update the Nvidia drivers this time? Did you follow the excellent instructions in essenbe's post?
    ....
    I didn't know this post existed. Whatever caused the nvidia driver installer to not recognize the fact that there was a 460M either fixed itself, or this was the correct installer this time. I can't say for certain. Wish I could be of more help.

    Also, BSOD. Computer was on its best behavior. Subsequent operations following the BSOD were very slow, sluggish, like it wasn't operating at 100%. Diag attached.

    EDIT: I did notice that this particular driver installer replaced the previous versions it was trying to install, so in my instance, the issue of needing to go back and uninstall the previous drivers was nonexistent.
      My Computer


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

    Slartybart said:
    Ok, great, and good news about best behavoir.
    I think yo're saying that things are better, but I want to be sure.

    But mon ami, you can be of more help
    Did you download / install the driver from my link, reinstall the driver you downloaded before, or use the Nvidia detect?

    Did another BSOD occur or are you in the clear for the moment? You attached a diag and describe sluggishness before a BSOD.

    Is what you describe something that occurred in the past or is this a new BSOD?

    Thanks for the feedback,
    Bill
    .
    Palladion said:
    Slartybart said:
    What enabled you to update the Nvidia drivers this time? Did you follow the excellent instructions in essenbe's post?
    ....
    I didn't know this post existed. Whatever caused the nvidia driver installer to not recognize the fact that there was a 460M either fixed itself, or this was the correct installer this time. I can't say for certain. Wish I could be of more help.

    Also, BSOD. Computer was on its best behavior. Subsequent operations following the BSOD were very slow, sluggish, like it wasn't operating at 100%. Diag attached.

    EDIT: I did notice that this particular driver installer replaced the previous versions it was trying to install, so in my instance, the issue of needing to go back and uninstall the previous drivers was nonexistent.
    Ah, of course. I used the link you provided in the aforementioned post. Worked perfectly. Don't know why the one from earlier in this thread didn't pull through.

    And yes, this is a BSOD that occurred today, after the updating of drivers, just a few hours ago as I started a Starcraft 2 match to sort of impromptu stress test my card, since the game seemed to instigate a crash more than anything else.

    The drivers for my video card may not have been the solution, but again, thanks to everyone for your help so far. It's been invaluable.
      My Computer


  3. Posts : 6,458
    x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
       #23

    Thanks for the clarification. I'm not a dump expert by any means, so I'll fire up the bat signal.

    Yeah, don't know why the driver worked the 2nd time - not important though.

    Bill
    .
      My Computer


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

    This.
      My Computer


  5. Posts : 4,161
    Windows 7 Pro-x64
       #25

    Uninstall the Intel Management Engine Interface. It's using the same IRQ as your display controller. This is not needed unless you rely on an IT department to maintain your PC. It's a system eating hog that runs all the time. Be sure to re-boot after the uninstall.

    If the BSOD 9f continues, uninstall the Daemon tools and see if your problem goes away. It's also hooked to your display.
      My Computer


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

    Done.
      My Computer


  7. Posts : 16
    Windows 7 Home Premium 64bit.
    Thread Starter
       #27

    Still having problems. Any clues?
      My Computer


  8. Posts : 4,161
    Windows 7 Pro-x64
       #28

    Attach the utility output so we can see the latest.
      My Computer


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

    That's... this thing?
      My Computer


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

    Relevant.

    http://i46.tinypic.com/xn9ftu.png

    EDIT: In typical fashion, a length of slower performance concluded with a BSOD, this time with the computer completely in idle on the desktop, something that has never happened before. This occurred minutes after this initial posting, and after the re-installation and updating of my graphics card drivers. Also, I remember, distinctly, performing a clean install of the graphics card drivers. All of them. I double checked tonight, and my driver versions were quite out of date. After installing the drivers again, my machine seems more on the edge of BSOD than ever.
    Last edited by Palladion; 15 Feb 2013 at 02:06.
      My Computer


 
Page 3 of 4 FirstFirst 1234 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:11.
Find Us