Crash after failed application launches

**Capt.Jack Sparrow** · 10 Jan 2012

Hello,

Seems like the crashes is caused by athrx.sys i.e. your Atheros WLAN card. I would recommend to remove the existing drivers and reinstall it.

Bugcheck:

Code:

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: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004c49d16, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003300100
 0000000000000018 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+18d16
fffff880`04c49d16 c7401800000000  mov     dword ptr [rax+18h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80004542750 -- (.trap 0xfffff80004542750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800a24c030
rdx=fffffa800a4cadc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c49d16 rsp=fffff800045428e0 rbp=0000000000000000
 r8=0000000000000001  r9=fffff88001a0e9a0 r10=0000000000000010
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
athrx+0x18d16:
fffff880`04c49d16 c7401800000000  mov     dword ptr [rax+18h],0 ds:7110:00000000`00000018=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030cd1e9 to fffff800030cdc40

STACK_TEXT:  
fffff800`04542608 fffff800`030cd1e9 : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`04542610 fffff800`030cbe60 : fffffa80`0732c920 fffff880`016cb8d0 fffff880`084b85c0 fffffa80`0a50d0f0 : nt!KiBugCheckDispatch+0x69
fffff800`04542750 fffff880`04c49d16 : fffffa80`09e401a0 fffffa80`0a4cac80 fffffa80`0a4cac80 00000000`00000001 : nt!KiPageFault+0x260
fffff800`045428e0 fffffa80`09e401a0 : fffffa80`0a4cac80 fffffa80`0a4cac80 00000000`00000001 00000000`00000000 : athrx+0x18d16
fffff800`045428e8 fffffa80`0a4cac80 : fffffa80`0a4cac80 00000000`00000001 00000000`00000000 fffffa80`0a4cadf8 : 0xfffffa80`09e401a0
fffff800`045428f0 fffffa80`0a4cac80 : 00000000`00000001 00000000`00000000 fffffa80`0a4cadf8 00000000`00000000 : 0xfffffa80`0a4cac80
fffff800`045428f8 00000000`00000001 : 00000000`00000000 fffffa80`0a4cadf8 00000000`00000000 00000000`00000000 : 0xfffffa80`0a4cac80
fffff800`04542900 00000000`00000000 : fffffa80`0a4cadf8 00000000`00000000 00000000`00000000 fffffa80`09e401a0 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+18d16
fffff880`04c49d16 c7401800000000  mov     dword ptr [rax+18h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+18d16

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c9fdcaa

FAILURE_BUCKET_ID:  X64_0xD1_athrx+18d16

BUCKET_ID:  X64_0xD1_athrx+18d16

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

schepplerj · 14 Jan 2012

I've updated my nvidia and atheros wlan drivers and it seems that that probably is fairly consistently coming from ntoskrnl.exe. Which makes sense since windows fails to boot/shutdown frequently.

I've run "Free window registry repair" since most of what I read said that would cause the issue, although Im not sure how good of a program it is, and still getting crashes

schepplerj · 16 Jan 2012

bump

**Capt.Jack Sparrow** · 17 Jan 2012

The crash is still pointing to nVidia Drivers. Follow this article Using Driver Verifier to identify issues with Drivers and Enable Driver Verifier

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f20c000 fffff880`0fe83000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Oct 15 11:37:55 2011 (4E99233B)
    CheckSum:         00C61687
    ImageSize:        00C77000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

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: fffffa80074e5060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa8006a88e10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8006a88e10

DEVICE_OBJECT: fffffa8009a8b480

DRIVER_OBJECT: fffffa8009a29220

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff8800f20c000 nvlddmkm

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032eacd2 to fffff8000327cc40

STACK_TEXT:  
fffff800`00b9c388 fffff800`032eacd2 : 00000000`0000009f 00000000`00000003 fffffa80`074e5060 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`032885fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c430 fffff800`03288496 : fffffa80`0b437768 fffffa80`0b437768 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0328837e : 00000001`84975e63 fffff800`00b9cb18 00000000`0000a33f fffff800`033f5a68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`03288167 : 00000000`4bce42c2 00000000`0000a33f 00000000`4bce42d6 00000000`0000003f : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0327496a : fffff800`033f2e80 fffff800`03400cc0 00000000`00000001 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_nvlddmkm.sys

BUCKET_ID:  X64_0x9F_IMAGE_nvlddmkm.sys

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

schepplerj · 17 Jan 2012

Is there any way this good be caused by a hardware issue?

I've run registry cleaners, antimalware, antiviral, antispyware, disk checks, sfc /scannow, uninstalled and reinstalled all my drivers including nvidia's multiple times.

I've done everything I can and it's just getting worse so I'm considering asking MSI for a replacement since it is still under warranty.

**Capt.Jack Sparrow** · 18 Jan 2012

It could be only way to tell is to reinstall Windows i.e. Vanilla install so we would know if it's software or Hardware.

schepplerj · 18 Jan 2012

unfortunately MSI doesn't include a recover disk, simply their "recover" function which reinstalls windows. This I've already done but I feel like if the corrupt information was installed originally then it will just get reinstalled when I run the recovery

schepplerj · 19 Jan 2012

Don't know if this helps any, but this is the error I get when I attempt to launch World of Warcraft and it freezes, thus causing a BSOD

Problem Event Name: AppHangB1
Application Name: Launcher.exe
Application Version: 4.2.1.2617
Application Timestamp: 4ebb345b
Hang Signature: a474
Hang Type: 0
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Hang Signature 1: a474304912927d872f3fd7c339543c4c
Additional Hang Signature 2: 89f2
Additional Hang Signature 3: 89f2c29289572c0b6c681edb9428eb6d
Additional Hang Signature 4: a474
Additional Hang Signature 5: a474304912927d872f3fd7c339543c4c
Additional Hang Signature 6: 89f2
Additional Hang Signature 7: 89f2c29289572c0b6c681edb9428eb6d

**Capt.Jack Sparrow** · 20 Jan 2012

schepplerj said:

unfortunately MSI doesn't include a recover disk, simply their "recover" function which reinstalls windows. This I've already done but I feel like if the corrupt information was installed originally then it will just get reinstalled when I run the recovery

See if you can borrow a disk from a friend and reinstall it. But this is less likely the issue. If you have recovered already and still the same issue it's more likely some hardware component.