If it has never thrown a bug check during active operation, it's probably just a display driver bug during sleep/hibernate transitions. Not uncommon at all. I disable both on my Desktop anyway, but considering this is a laptop, not sure if you want to do that.
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
[SOLVED] BSOD with 0x116 error - Windows 7 SP1 x64
- Thread starter SteveInOcala
- Start date
SteveInOcala
Member
Would it make sense to swap out display drivers or maybe get a different video module. This laptop has 2 Nvidia and one ATI video modules available that I might be able to get off eBay. Or if you think it might be the card, I can get another one the same as the one I have...The laptop did fine run from Oct. til Dec. without this problem...then, it just started happening, kind of "out of the blue"...
It's a tough call to make, and the sole reason for that again is you mentioned all previous working versions (as you've tried many) of the display driver now also don't stop the problem. That would define and confirm a clear issue with the hardware itself, but it's a strange issue given it only throws a bug check during transitions from sleep/hibernation states. This isn't new or anything, as faulty hardware doesn't automatically imply "just doesn't work at all", but it's just a strange issue to see.
It's up to you at this point if it's worth attempting to maintain/repair.
It's up to you at this point if it's worth attempting to maintain/repair.
SteveInOcala
Member
Might have solved it and wanted to share in this thread so maybe someone else can be helped...
I found this thread which summarized all the things I had done and almost ignored it until I read the first comment:
"well for me none of those worked on my G60JX Asus i5-430M. So what did I do? I down-clocked the GPU from 500/1800/1323 (factory) to 525/1725/1225 and I have NEVER had that blue screen issue. How to do it? Simple. Install nVidia nTune. Then download nVidiaInspector by Orbmu2k and click on "show over clock" button. Adjust the settings as necessary and the click “Create Shortcut Clock” at the bottom. The shortcut is on your desktop. Put that shortcut in your startup folder and say goodbye to that annoying issue. Just remember clocks can only be reset when the power is on A/C. After that you can remove A/C and it will be as you set it."
So I downloaded nVidiaInspector and tried it...IT WORKED. I've been running all day, including sleeps and hibernates and have resumed each time successfully. I backed the speed down, minimally, and every resume has been successful. I'm currently running my FX1800 video card at 561/1115/1080 vs. factory stock of 561/1125/1099. So I had to make very minimal changes. I've tried it with both the current drivers (341.21) from Nvidia's site and my original (older) ones from HPs site, and both seem to work successfully.
Thanks for all the help and hope this might help someone else.
Steve
I found this thread which summarized all the things I had done and almost ignored it until I read the first comment:
"well for me none of those worked on my G60JX Asus i5-430M. So what did I do? I down-clocked the GPU from 500/1800/1323 (factory) to 525/1725/1225 and I have NEVER had that blue screen issue. How to do it? Simple. Install nVidia nTune. Then download nVidiaInspector by Orbmu2k and click on "show over clock" button. Adjust the settings as necessary and the click “Create Shortcut Clock” at the bottom. The shortcut is on your desktop. Put that shortcut in your startup folder and say goodbye to that annoying issue. Just remember clocks can only be reset when the power is on A/C. After that you can remove A/C and it will be as you set it."
So I downloaded nVidiaInspector and tried it...IT WORKED. I've been running all day, including sleeps and hibernates and have resumed each time successfully. I backed the speed down, minimally, and every resume has been successful. I'm currently running my FX1800 video card at 561/1115/1080 vs. factory stock of 561/1125/1099. So I had to make very minimal changes. I've tried it with both the current drivers (341.21) from Nvidia's site and my original (older) ones from HPs site, and both seem to work successfully.
Thanks for all the help and hope this might help someone else.
Steve
SteveInOcala
Member
Doesn't seem to be much of a performance hit...according to Windows UEI, I'm still getting the same value for my video subsystem as before...
One minor additional data point...It runs just fine (i.e.: it resumes without issue) on Windows 10 Tech Preview without the underclocking...
Again, Patrick, thanks for all the help...
One minor additional data point...It runs just fine (i.e.: it resumes without issue) on Windows 10 Tech Preview without the underclocking...
Again, Patrick, thanks for all the help...
The WEI is one of Microsoft's unfortunate failures that was abandoned. I wouldn't pay attention to the WEI as it's inaccurate and really doesn't portray any useful information. However though, yes, undervolting the core voltage/memory clocks by 10/19 is not a huge hit by any means to performance.
Interesting, maybe the native W10 display drivers are better than the manufacturer ones : )
One minor additional data point...It runs just fine (i.e.: it resumes without issue) on Windows 10 Tech Preview without the underclocking...
Interesting, maybe the native W10 display drivers are better than the manufacturer ones : )
Has Sysnative Forums helped you? Please consider donating to help us support the site!