
Quote: Originally Posted by
ocremy14
Windows 7 Ultimate upgrade from vista. 32 bit
HP pavillion dv5 notebook.
Crashes and displays Driver_state_power_failure message
The majority of these were caused by your athrx.sys driver (your atheros WiFi driver). I would start by a re-install with the newest available.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\032011-22776-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x83018000 PsLoadedModuleList = 0x83160810
Debug session time: Sun Mar 20 10:11:13.985 2011 (GMT-4)
System Uptime: 3 days 11:51:13.727
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {30, 2, 0, 918478a5}
Unable to load image \SystemRoot\system32\DRIVERS\athr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : athr.sys ( athr+428a5 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000030, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 918478a5, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 83180718
Unable to read MiSystemVaType memory at 83160160
00000030
CURRENT_IRQL: 2
FAULTING_IP:
athr+428a5
918478a5 8b5130 mov edx,dword ptr [ecx+30h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: firefox.exe
TRAP_FRAME: 807e4b64 -- (.trap 0xffffffff807e4b64)
ErrCode = 00000000
eax=0000001a ebx=8710e1c0 ecx=00000000 edx=00000088 esi=00000000 edi=00000000
eip=918478a5 esp=807e4bd8 ebp=807e4bdc iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
athr+0x428a5:
918478a5 8b5130 mov edx,dword ptr [ecx+30h] ds:0023:00000030=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 918478a5 to 8305e81b
STACK_TEXT:
807e4b64 918478a5 badb0d00 00000088 00000000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
807e4bdc 91847647 00000000 85e516bc 85e20450 athr+0x428a5
807e4c14 91846c52 85df2908 86da4d68 00000000 athr+0x42647
807e4c3c 9186dfc0 85df2828 86da4d68 00000018 athr+0x41c52
807e4c90 9186e8c7 86ce2020 86da4d68 00000000 athr+0x68fc0
807e4de4 9181fcfe 86da4d68 807e4e00 9181cd2f athr+0x698c7
807e4df0 9181cd2f 86da4d68 86d5f028 807e4e10 athr+0x1acfe
807e4e00 918649c7 86d5f028 86da4d68 807e4e38 athr+0x17d2f
807e4e10 918646b7 86d4f628 86da4d68 00000000 athr+0x5f9c7
807e4e38 9181862a 86d4f628 86da4d68 00000000 athr+0x5f6b7
807e4e64 91818414 86d02028 86da4ce0 8710e1c0 athr+0x1362a
807e4e7c 91819499 86d02028 85a9b018 864ab0f0 athr+0x13414
807e4e94 91819525 86d02028 807e4eac 91876554 athr+0x14499
807e4ea0 91876554 86d02028 807e4ec8 9187b1ff athr+0x14525
807e4eac 9187b1ff 86cfb020 807e4ec0 807e4ee8 athr+0x71554
807e4ec8 9181fabd 86cfb020 807e4ee4 91806761 athr+0x761ff
807e4ed4 91806761 86ce2020 86d02028 807e4f20 athr+0x1aabd
807e4ee4 8b068309 86d02028 00000000 807e4f10 athr+0x1761
807e4f20 8b0139f4 8710e1d4 0010e1c0 00000000 ndis!ndisMiniportDpc+0xe2
807e4f48 830804f5 8710e1d4 8710e1c0 00000000 ndis!ndisInterruptDpc+0xaf
807e4fa4 83080358 807c4120 8598e888 00000000 nt!KiExecuteAllDpcs+0xf9
807e4ff4 8307fb1c b1e4fce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e4ff8 b1e4fce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
8307fb1c 00000000 0000001a 00d6850f bb830000 0xb1e4fce4
STACK_COMMAND: kb
FOLLOWUP_IP:
athr+428a5
918478a5 8b5130 mov edx,dword ptr [ecx+30h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: athr+428a5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athr
IMAGE_NAME: athr.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a2ea444
FAILURE_BUCKET_ID: 0xD1_athr+428a5
BUCKET_ID: 0xD1_athr+428a5
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000030, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 918478a5, address which referenced memory
Debugging Details:
------------------
ALSO these drivers (including the atheros) are ancient and need updating.
Code:
AtiPcie.sys 10/30/2006 02:23:10 PM 0x8b1d5000 0x8b1dd000 0x00008000 0x4546430e
HpqKbFiltr.sys 6/18/2007 06:12:03 PM 0x91bc7000 0x91bcb180 0x00004180 0x46770333
Amddfltr.sys 1/8/2008 12:41:55 PM 0x8b1dd000 0x8b1e5000 0x00008000 0x4783a7d3
SynTP.sys 1/18/2008 02:50:15 PM 0x90506000 0x90534680 0x0002e680 0x4790f4e7
enecir.sys 1/24/2008 01:23:11 AM 0x91be8000 0x91c00000 0x00018000 0x479820bf
Accelerometer.sys 3/18/2008 05:24:47 PM 0x9201f000 0x9202a000 0x0000b000 0x47e0331f
Rtlh86.sys 4/14/2008 10:05:06 PM 0x91b24000 0x91b45000 0x00021000 0x48040d52
RTSTOR.SYS 4/21/2008 08:59:02 AM 0x983c4000 0x983d8000 0x00014000 0x480c8f96
stwrt.sys 9/11/2008 12:05:43 PM 0x97921000 0x97984000 0x00063000 0x48c941d7
AGRSM.sys 11/10/2008 10:56:37 AM 0x98221000 0x98327000 0x00106000 0x49184ba5
mcdbus.sys 2/24/2009 06:42:13 AM 0x90400000 0x9041c800 0x0001c800 0x49a3cf05
spldr.sys 5/11/2009 12:13:47 PM 0x8b3df000 0x8b3e7000 0x00008000 0x4a084ebb
GEARAspiWDM.sys 5/18/2009 08:16:53 AM 0x91b45000 0x91b4a280 0x00005280 0x4a1151b5
amdxata.sys 5/19/2009 01:57:35 PM 0x8ad49000 0x8ad52000 0x00009000 0x4a12f30f
athr.sys 6/9/2009 02:04:52 PM 0x91a0a000 0x91b1a000 0x00110000 0x4a2ea444
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page:
http://www.carrona.org/drvrdown.html