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

[wooglin7]

I hope someone here can help me out. I am getting BSODs regularly and I am trying everything before doing a full system restore to factory settings.

My BSOD generally happens when I am not plugged into a power supply (one time it happened plugged in) and it seems to always happen at work. HP has been very little help...we installed new BIOS drivers and I installed new graphics drivers thinking this might be the issue but the BSOD persists. They just want me to wipe the computer and dont seem to want to do real troubleshooting.

I somehow get the feeling it could be related to wireless drivers when I am not hardwired into the LAN at the office (whenever I go wireless I get a message that says 'Your resource "RIRWIN-HP.BFDDEADA" is now offline' - I have no idea what this is and I think the letters/numbers after the HP. are different every time). Then my computer performance seems to struggle, the fans rev up and then BSOD (sometimes preceded by Windows Explorer not responding).

I have attached my jcgriff file and the results of running WhoCrashed. I ran the Resource and Performance Monitor but it never completes so Save As is grayed out (left it running about 20 mins). I filled out my system specs. This computer is less than a year old and everything is OEM.

Thanks for your time and attention.

 

[writhziden]

Loading Dump File [G:\Kingston\BSODDmpFiles\wooglin7\Windows_NT6_BSOD_jcgriff2\012612-38189-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`047033c0?
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0309d670
Debug session time: Thu Jan 26 10:15:05.717 2012 (GMT-7)
System Uptime: 0 days 2:42:42.591
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800cf90060, fffff800047033d8, fffffa801057f010}

Unable to load image \SystemRoot\system32\drivers\btwampfl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btwampfl.sys
*** ERROR: Module load completed but symbols could not be loaded for btwampfl.sys
Probably caused by : usbhub.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800cf90060, Physical Device Object of the stack
Arg3: fffff800047033d8, Functional Device Object of the stack
Arg4: fffffa801057f010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa801057f010

DEVICE_OBJECT: fffffa800cf90060

DRIVER_OBJECT: fffffa800b7024b0

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15

MODULE_NAME: usbhub

FAULTING_MODULE: fffff880052e5000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  7ÜÌ


CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f42cd2 to fffff80002ed4c40

STACK_TEXT:  
fffff800`04703388 fffff800`02f42cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0cf90060 fffff800`047033d8 : nt!KeBugCheckEx
fffff800`04703390 fffff800`02ee05fc : fffff800`047034c0 fffff800`047034c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`04703430 fffff800`02ee0496 : fffff800`0307ff00 00000000`00098c8b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`047034a0 fffff800`02ee037e : 00000016`baf5425b fffff800`04703b18 00000000`00098c8b fffff800`0304e3e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04703af0 fffff800`02ee0167 : 00000004`df66b1c1 00000004`00098c8b 00000004`df66b181 00000000`0000008b : nt!KiTimerExpiration+0x1be
fffff800`04703b90 fffff800`02ecc96a : fffff800`0304ae80 fffff800`03058cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04703c40 00000000`00000000 : fffff800`04704000 fffff800`046fe000 fffff800`04703c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_IMAGE_usbhub.sys

Followup: MachineOwner
---------

Is your network adapter device for your wireless a USB device? Are there any more recent drivers for it? I see a Sierra Wireless Filter Driver that needs updating.

 

[wooglin7]

writhziden, thanks for the quick reply.

My network adapter devices are built in. My only regular USB devices are a keyboard, mouse, and sometimes an external hard drive. I do sometimes connect an AT&T wireless USB device when I am on the road. I did a quick Google search for the Sierra Wireless Filter Driver that you mentioned and it seems to be related to AT&T Connection Manager which is the software for the AT&T wireless USB device. Could this be the problem?! I will look for new driver.

Thanks again.

 

[writhziden]

The AT&T driver may be conflicting with the onboard adapter driver. I would try uninstalling the USB device and see if you continue to have problems. You can always install it again when you go on the road. For help with this, try the http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html steps.

 

[wooglin7]

OK so here is what I did. Drivers related to the AT&T USB aircard do not show up until you plug it in. So I plugged it in (which may have updated the drivers - I dont know) and then deleted all the drivers for it (they were all called GlobeTrotter something or other - nothing called Sierra).

Then I uninstalled the AT&T Communication Manager software. Then I completed all the steps from the link you provided to uninstall USB devices. I uninstalled all grayed out devices from the USB list in the Device Manager (many of which were called GlobeTrotter...). However, there are still grayed out Globetrotter devices under Modems and Network Adapters which I would like to delete as well - should be ok right?

So I will see if the BSOD rears its ugly head again. But like I said I couldnt find anything called Sierra Wireless Filter Driver (the one you said should be updated). Again, maybe it got wiped upon automatic installation of new drivers when I plugged in the wireless USB device.

Thanks

 

[writhziden]

Yeah, as long as you are sure the grayed out devices are part of the same device (which it sounds like they are), you can remove them. See how it goes. Good luck!

 

[wooglin7]

Well, unfortunately that didnt work. BSOD hit about an hour ago. New jcgriff file attached.

I am going to start removing programs to strip things down a bit.

Please let me know if the dump files point to any other possibilities.

Thanks!

 

[writhziden]

There are some problem devices listed for your system:

SonicWALL IPsec Driver	ROOT\LEGACY_SWIPSEC\0000	This device is not present, is not working properly, or does not have all its drivers installed.
SonicWALL Virtual NIC	ROOT\SWVNIC\0000	This device is disabled.

If you are not using the SonicWALL software, it may help stability to uninstall it. Having remnants on the computer may be causing conflicts.

 

[wooglin7]

SonicWALL is my company's VPN software and I have always hated it. It allows me to connect to the office network remotely but for whatever reason it doesnt work from most wireless connections (hotels, airports etc). But I do use it alot if I am working from home. It wouldnt surprise me in the least if it was the culprit.

Is it an issue where you think upgrading drivers for this software would help or do you think it requires a complete uninstall?

Also, if you could detail what the problems are with the program/drivers I could have some info to take to my IT guy to continue trying to convince him that SonicWALL is no good and causes problems.

Thanks again

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\wooglin7\Windows_NT6_BSOD_jcgriff2\020712-24242-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03811000 PsLoadedModuleList = 0xfffff800`03a56670
Debug session time: Tue Feb  7 13:06:51.477 2012 (GMT-7)
System Uptime: 0 days 1:11:50.351
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800a9c4440, fffff80000b9c3d8, fffffa800f451010}

Probably caused by : WUDFRd.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a9c4440, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800f451010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800f451010

DEVICE_OBJECT: fffffa800ccae620

DRIVER_OBJECT: fffffa800ccb2390

IMAGE_NAME:  WUDFRd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a654

MODULE_NAME: WUDFRd

FAULTING_MODULE: fffff88003c00000 WUDFRd

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800038fbcd2 to fffff8000388dc40

STACK_TEXT:  
fffff800`00b9c388 fffff800`038fbcd2 : 00000000`0000009f 00000000`00000003 fffffa80`0a9c4440 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`038995fc : fffff800`00b9c4d8 fffff800`00b9c4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c430 fffff800`03899496 : fffffa80`0cbdb168 fffffa80`0cbdb168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0389937e : 0000000a`092b8379 fffff800`00b9cb18 00000000`0004374e fffff800`03a06c48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`03899167 : 00000002`26c948c5 00000002`0004374e 00000002`26c948af 00000000`0000004e : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0388596a : fffff800`03a03e80 fffff800`03a11cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_WUDFRd.sys

BUCKET_ID:  X64_0x9F_IMAGE_WUDFRd.sys

Followup: MachineOwner
---------

The driver being blamed is Windows Driver Foundation - User-mode Driver Framework Reflector, which suggests that a driver is causing problems with your system, and the driver power state failure suggests the driver was attempting to put a device to sleep (turn it off) or wake it up (turn it back on). These usually occur when a computer is entering sleep, entering hibernate, shutting down, or resuming from one of these three states. Do you remember circumstances of the crash?

When I saw what the crash blamed, I looked at your problem devices and saw SonicWALL. I do not know if it is the culprit, but it stood out to me since it was in the problem devices area and it may interfere with your network adapter's ability to shut down if it is not functioning properly. That was my basic line of reasoning. Can you remove the software for testing and try to recreate the circumstances of the crash? If not, can you ask the IT guy at work to do so? You can see if there is an update to fix the problem, too, as you suggested. If you do an update, uninstall the old version completely first, and then install the update.

 

[wooglin7]

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.

 

[writhziden]

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.

 

[wooglin7]

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...

 

[writhziden]

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.

 

[wooglin7]

Thanks writh. So far so good. If I encounter more problems I will try what you suggested with the BIOS.

 

[westom]

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.

 

[wooglin7]

westom, was that supposed to be helpful? All the details of my BSODs are in the file attachments.

 

[westom]

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.

 

[wooglin7]

westom, thanks for the input. I will look into.

 

[wooglin7]

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