Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Computer locking up and BSOD


  • Please log in to reply

#1
Reddoug

Reddoug

    Member

  • Member
  • PipPipPip
  • 291 posts
Hi All

HP Pavalion dv-7 1260us Win7 Pro. Originally came with Vista. I wiped drive and did clean install, not an upgrade 6 months ago. This just started last week.

I am having trouble with my laptop locking up and BSOD. Sometimes when it starts to act up it will just freeze and then the screen goes black and I have to hold down power button to shutdown. I have run Windbg and I think the problem is with my wireless adapter, Atheros AR5009. I have uninstall and reinstalled it, updated BIOS to the latest. HP's website does not list any drivers for Atheros and more, only list a Broadcom driver. Not sure if it will work with my computer. Also I had Virtual box installed, (I unistalled it) but it left a Virtualbox bridge networking driver miniport #4 in device manager and I can not remove it. Right now I am running in safemode with no problems and I have this comp dual booted with ubuntu 11.4 in classic mode. Was having problem with unity. I do not have any problem locking up in ubuntu. Trying to find the problem without wiping the drive and reinstalling OS's which would be easier but I would not learn as much.
Any help will be greatly appreciated.

Thanks, Doug

Below is the minidump data.


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\061611-48594-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e45650
Debug session time: Thu Jun 16 21:15:52.365 2011 (GMT-5)
System Uptime: 0 days 0:15:00.347
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800468d060, fffff80000ba2748, fffffa80aae6fc60}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.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: fffffa800468d060, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa80aae6fc60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa80aae6fc60

DEVICE_OBJECT: fffffa8005180050

DRIVER_OBJECT: fffffa8004e93820

IMAGE_NAME: athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4acea2b7

MODULE_NAME: athrx

FAULTING_MODULE: fffff88004461000 athrx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002cec9c2 to fffff80002c7fd00

STACK_TEXT:
fffff800`00ba26f8 fffff800`02cec9c2 : 00000000`0000009f 00000000`00000003 fffffa80`0468d060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`02c8b652 : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00ba27a0 fffff800`02c8b4f6 : fffffa80`04b9ec68 fffffa80`04b9ec68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`02c8b3de : 00000002`18a60dd8 fffff800`00ba2e88 00000000`0000e172 fffff800`02df60c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`02c8b1c7 : fffff800`02df2ec3 fffff800`0000e172 00000000`00000001 00000000`00000072 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02c82765 : 00000000`00000000 fffffa80`03ce3680 00000000`00000000 fffff880`042a6588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02c8257c : fffffa80`03c01000 fffff800`031f3895 fffff800`03219460 fffff880`02fd9660 : nt!KyRetireDpcList+0x5
fffff880`02fd95a0 fffff800`02ccba13 : fffff800`02c7c260 fffff800`02c7c2cc fffffa80`04afba60 00000000`01ff7e84 : nt!KiDispatchInterruptContinue
fffff880`02fd95d0 fffff800`02c7c2cc : fffffa80`04afba60 00000000`01ff7e84 fffffa80`00000002 fffffa80`04b3d6f0 : nt!KiDpcInterruptBypass+0x13
fffff880`02fd95e0 fffff800`02da9233 : 00000000`00000000 fffff880`02fd97c0 00000000`00000000 fffff800`02c918ec : nt!KiInterruptDispatchNoLock+0x1fc
fffff880`02fd9770 fffff800`02dab3f6 : fffff800`02e08480 00000000`00000028 00000000`00000004 00000000`00000000 : nt!MiAllocatePoolPages+0xbb3
fffff880`02fd98b0 fffff800`02f63c0f : fffff8a0`00000000 fffffa80`2d3a3440 fffffa80`04681060 fffff800`00000001 : nt!ExAllocatePoolWithTag+0x316
fffff880`02fd99a0 fffff880`045fc992 : 00000000`00000008 fffffa80`04681060 fffff880`02fd9af0 fffff800`02c8c254 : nt!IoBuildDeviceIoControlRequest+0xaf
fffff880`02fd9a10 fffff880`045fa7d0 : fffffa80`05282190 00000000`00000000 fffffa80`05282320 00000000`000007ff : CmBatt!CmBattSendDownStreamIrp+0x76
fffff880`02fd9aa0 fffff880`045fc28a : fffffa80`05282190 fffffa80`05282a60 5453425f`42696541 00000000`00000000 : CmBatt!CmBattGetBstData+0x98
fffff880`02fd9ae0 fffff880`045fc075 : fffffa80`00000000 fffff8a0`09f1d7c0 fffffa80`05282190 ffffe739`4e287c0e : CmBatt!CmBattGetBatteryStatus+0x26
fffff880`02fd9b60 fffff880`00e0ec99 : 00000000`6b49d200 fffff800`02c54a77 fffffa80`046c8380 ffffe739`4e287c3e : CmBatt!CmBattQueryStatus+0x21
fffff880`02fd9b90 fffff880`00e0eaaf : fffffa80`05282a60 00000000`00026161 fffff880`00e0e848 fffffa80`053120b8 : BATTC!BattCCheckStatusQueue+0xd1
fffff880`02fd9c10 fffff800`02c8a021 : fffff880`00e01228 fffff880`00e0e848 fffff800`02e1d2b8 fffffa80`03ce3680 : BATTC!BattCWorkerThread+0x267
fffff880`02fd9cb0 fffff800`02f1c32e : 00000000`00000000 fffffa80`03ce3680 00000000`00000080 fffffa80`03cce9e0 : nt!ExpWorkerThread+0x111
fffff880`02fd9d40 fffff800`02c71666 : fffff880`009e8180 fffffa80`03ce3680 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fd9d80 00000000`00000000 : fffff880`02fda000 fffff880`02fd4000 fffff880`02fd99e0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_IMAGE_athrx.sys

BUCKET_ID: X64_0x9F_IMAGE_athrx.sys

Followup: MachineOwner
---------
  • 0

Advertisements


#2
Reddoug

Reddoug

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 291 posts
I wiped drive and reloaded Windows 7.

Doug
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP