Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - HP Pavilion dv6 - ntoskrnl.exe (nt+0x7CC40)

08 Feb 2012   #11
wooglin7

Windows 7 Professional 64-bit
 
 

It could definitely be related to computer sleeping/waking up. Yesterday when I got the BSOD it was after I tried waking the computer up and this has happened before. There has been a problem where when I close the lid and reopen it a few minutes later the screen does not reappear. I can hear the computer is still running with sounds (critical stop sound etc) but the screen refuses to return unless I force shutdown and restart. If I just leave it on the BSOD will usually come next. This is when I thought it might be my graphics drivers.

Other times when I got the BSOD it was after my computer was sitting idle for a while and may have been going to sleep (or maybe just trying to dim display or turn on screen saver). This always happens on battery, never when I am plugged into power supply.


My System SpecsSystem Spec
.
08 Feb 2012   #12
writhziden

Windows 7 Home Premium 64 Bit
 
 

Your computer has more conservative power settings when unplugged and will typically sleep sooner than when AC power is supplied. I would test a few scenarios with leaving the computer idle. Try turning off your wireless adapter (disable it through Windows, or even better if you have a switch or a Fn + F key sequence to turn it off, turn it off that way). See if it will sleep and resume normally with the wireless off. If you plug in through Ethernet, try disabling the Ethernet adapter and seeing if the computer can sleep and wake more reliably.

Test it with the devices enabled first and see if you continue to get blue screens. Then test with them disabled.
My System SpecsSystem Spec
09 Feb 2012   #13
wooglin7

Windows 7 Professional 64-bit
 
 

OK, so I ran through a few tests just as you suggested and it definitely appears to be related to the wireless adapter. Specifically my main network adapter called Intel Wifi Link 1000 BGN. When I disabled this device in the Device Manager it seemed to eliminate the BSOD but I am still running tests.

Here are the tests I did. All were performed while running on battery only.

Test 1 - Adapter ON - BSOD in about 20 mins (this was before I started timing screen saver, screen off etc)
Test 2 - Adapter OFF - clean through dim, screen saver, screen shutoff
Test 3 - Adapter ON - clean through dim, screen saver, screen shutoff - NO WAKEUP - force shutdown (may not have given it enough time for BSOD to appear - it seems to happen after the attempts to sleep)
Test 4 - Adapter ON - BSOD after screen off (attempting to sleep)
Test 5 - Adapter OFF - clean through dim, screen saver, screen shutoff (attempted to sleep, no wakeup but no BSOD - force shutdown)

I started running further tests with the power supply plugged in and just closing the lid to make the computer sleep. It seems the computer was getting hung up on going to sleep. It gets stuck on "screen off" mode and I cant get the screen to come back up and have to force shutdown (this was with wireless adapter both enabled and disabled) Later on I reverted to testing on battery only and timing the computer through the idle cycle (dim, screen saver, screen off, sleep) and low and behold all the sudden everything was happening on time and properly (earlier in the day it wasnt going to sleep properly and getting hung up on "screen off" mode) Once it started sleeping properly I was able to wake it with no problems.

So I dont know if disabling and enabling my wireless device a number of times helped it operate properly? But I went ahead and installed new drivers for the Intel wireless anyway because there was an updated version available. I will keep testing and see what happens. I like that it seems to be working better but I dont like not knowing why! Dont want to mark as solved just yet...
My System SpecsSystem Spec
.

09 Feb 2012   #14
writhziden

Windows 7 Home Premium 64 Bit
 
 

It may have been a power configuration change due to the switch from AC to battery coupled with your switching the adapter on and off. It is hard to say. If the problem returns, you could try a full BIOS reset to see if there is an issue with how the software/hardware connections are interacting.
  1. Go into your BIOS and load default settings to clear the CMOS memory.
  2. Save Settings and exit the BIOS.
  3. Shut down and turn off the computer.
  4. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
  5. Hold down the power button for 30 seconds. This closes the circuit and ensures all power from components is drained to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory.
  6. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall.
  7. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back your results.
My System SpecsSystem Spec
10 Feb 2012   #15
wooglin7

Windows 7 Professional 64-bit
 
 

Thanks writh. So far so good. If I encounter more problems I will try what you suggested with the BIOS.
My System SpecsSystem Spec
11 Feb 2012   #16
westom

 
 

Quote   Quote: Originally Posted by wooglin7 View Post
It could definitely be related to computer sleeping/waking up. Yesterday when I got the BSOD it was after I tried waking the computer up and this has happened before.
That BSOD contains important numbers and text that define the problem. You are shorting your help of necessary facts by not posting numbers.

Is the problem in hardware or software? Your computer is from a more responsible manufacturer. So comprehensive hardware diagnostics are provided, for free, to answer that question. And more. Diagnostics load and execute without Windows to test only hardware. Best is to repeat that testing with the computer is a warm room. The best diagnostic environment (that immediately finds marginal or intermittent hardware defects) is also executed in a room ideally at 100 degrees F. Heat is a powerful diagnostic tool that finds intermittents.

Windows also sees problems. Records them. And then works around them. Windows could have seen your problems long ago. View the system (event) logs to learn what was discovered and recorded long ago.

Each is an example of facts necessary for others with better knowledge to provide assistance.
My System SpecsSystem Spec
11 Feb 2012   #17
wooglin7

Windows 7 Professional 64-bit
 
 

westom, was that supposed to be helpful? All the details of my BSODs are in the file attachments.
My System SpecsSystem Spec
12 Feb 2012   #18
westom

 
 

Quote   Quote: Originally Posted by wooglin7 View Post
westom, was that supposed to be helpful? All the details of my BSODs are in the file attachments.
I did not see your attachments. Sorry. But they only discuss the BSOD. Those other 'tests' are also important.


Your BSOD identified the offending device number when the system crashes. I don't have the table that identifies that pointer to that device. Based upon your other statements, we may assume it is the wireless device.

That BSOD typically occurs when the device's driver fails. However, any hardware failure is not supposed to affect the driver. Sometimes a hardware defect trips an undetected bug in the driver. Therefore causing your failure.

So again, that is what the comprehensive hardware diagnostics are for.

I am troubled by so many wireless failures. But I don't have the convenience you have. To associate the many system log failures with the timing of those failures. Again, if wireless failures in the logs coincide with later BSODs, then you have a prime suspect.

Do you know you have the correct driver for wireless? Not just because it loaded. The driver should be identified for that particular model of wireless. You have a list of hardware that specifically defines that wireless card. You can download only that driver from HP. In device manager, remove the old driver. Reboot. And the new downloaded driver can be applied. This is a shotgun solution. But worth the try if the answer to other above questions points to the wireless device.

Outside of your observations, I do not have sufficient facts to blame the wireless. Associating the device number in that BSOD dump (sometimes it was 0xFFFFFA800CF90060) would go a long way to better defining the specific defective part.

And again, execute the comprehensive hardware diagnostic as described earlier. Your problem is why only better computer manufacturers provide those diagnostics.

Resetting the BIOS, et al is not going to solve a hardware problem or fix a driver. The BSOD is pointing to a specific problem that somehow has caused a specific driver to fail.
My System SpecsSystem Spec
14 Feb 2012   #19
wooglin7

Windows 7 Professional 64-bit
 
 

westom, thanks for the input. I will look into.
My System SpecsSystem Spec
16 Feb 2012   #20
wooglin7

Windows 7 Professional 64-bit
 
 

BSOD is back. It continues to be related to two things.

1. Sleep cycle not implementing properly - Whenever things are working properly this cycle works properly (ie screen dim, saver, off, sleep according to set timing). Problems are evident when this cycle does not work properly. It will go straight to screen off mode then most times I can not get it to come back on. If I let it sit then BSOD hits.

2. Wireless adapter - Hard to tell when this causes problems or how it relates to screen problems. Sometimes the HP Wireless Assistant errors out (can I delete that software? I think I can).

Writh, I will try BIOS reset as you suggested when I get a chance.

Thanks
My System SpecsSystem Spec
Reply

 BSOD - HP Pavilion dv6 - ntoskrnl.exe (nt+0x7CC40)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD - ntoskrnl.exe (nt+0x7CC40)
Good day and thank you for reviewing my BSOD issue. I have been getting completely random blue screen crashes for some time now. There is generally no consistency regarding the app used, apps running or time of day. Most reference ntoskrnl.exe (nt+0x7CC40)with errors such as...
BSOD Help and Support
Bsod casued by ntoskrnl (nt+0x7cc40)
Hi all, have recently experienced a bsod. WhoCrashed reports that it was probably caused by ntoskrnl.exe (nt+0x7CC40). Had a similar Bsod attributed to the NTKernel a few weeks ago, after reading up on it. I did a memtest which came back clean and checked the disk for errors, which also showed...
BSOD Help and Support
Random BSOD : ntoskrnl.exe (nt+0x7CC40) Driver Power State Failure
Hi XPS L502x : 2nd generation Intel Core i7-2720QM processor 2.20 GHz with Turbo Boost 2.0 up to 3.30 GH 8Gb Ram Windows 7 64 bit Have been having repeated BSODs lately. Used to get them about once or twice a week but its now a few times a day that it happens. Have attached the zip...
BSOD Help and Support
BSOD ntoskrnl.exe (nt+0x7CC40) - 0xA
I am experienceing the BSOD very often. More than 15 - 20 times a day. Before coming to this site I had already deleted all the files in C:\Windows\minidump to do a clean troubleshooting. Then when I got the BSOD the first time I used the...
BSOD Help and Support
BSOD Doing almost any task, error ntoskrnl.exe (nt+0x7CC40)
Hello, I built this machine approximatley 5 months ago. I have been getting random BSOD about Once or Twice a Month. I have attached all required files for assistance. Any help would be greatly appreciated. Thank you in advance.. David
BSOD Help and Support
BSOD possible ntoskrnl.exe (nt+0x7CC40)
Hi i have been having a few BSOD on a new pc, they seem to be random, but the same problem. Windows 7 oem i5 2500k 8gb ram ocz solid 3 128 GB ssd i have a western digital drive too HDD MSE anti virus This is what WhoCrashed says
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 15:46.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App