BSOD 0x100000B8

Yodaisback · 01 Mar 2015

Hi,

Here is the Whocrashed result about my BSOD :

On Sat 28/02/2015 08:25:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022815-75192-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7769A)
Bugcheck code: 0x100000B8 (0xFFFFFA8003CF3B50, 0xFFFFFA8009250B50, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Perhaps because of athrx.sys file ?

Could you help me ?

Olivier

Arc · 02 Mar 2015

Yodaisback said:

Perhaps because of athrx.sys file ?

Yes.

Yodaisback said:

Could you help me ?

Olivier

Download and install Drivers for Atheros AR9285 and Windows 7.

Let us know for any further BSOD.
______________________________________________

Code:

BugCheck 100000B8, {fffffa8003cf3660, fffffa8007794b50, 0, 0}

*** 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 ( athrx+11bdd9 )

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

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

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffffa8003cf3660, Original thread which is the cause of the failure
Arg2: fffffa8007794b50, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


FAULTING_THREAD:  fffffa8003cf3660

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xB8

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

LAST_CONTROL_TRANSFER:  from fffff80002ec60f2 to fffff80002ec369a

STACK_TEXT:  
fffff800`00b9f870 fffff800`02ec60f2 : fffff880`06b0300a 00000000`00000000 00000000`deadbeef fffff880`052571a5 : nt!KiSwapContext+0x7a
fffff800`00b9f9b0 fffff800`02e844db : fffffa80`0785a030 fffff880`00000880 fffff880`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff800`00b9fa40 fffff800`02e9142d : fffffa80`07858050 00000000`00000000 fffff880`06b0300a fffff880`0525dcf2 : nt!KeWaitForGate+0xfb
fffff800`00b9fa90 fffff800`02ed7b78 : fffffa80`0777a030 00000000`00000000 fffff880`050d66e0 00000000`00000000 : nt!KiAcquireGuardedMutex+0x45
fffff800`00b9fac0 fffff880`051f0dd9 : fffff880`06b03000 fffffa80`00000008 00000000`000000ff fffff880`06b03000 : nt!KeAcquireGuardedMutex+0x38
fffff800`00b9faf0 fffff880`06b03000 : fffffa80`00000008 00000000`000000ff fffff880`06b03000 00000000`000000ff : athrx+0x11bdd9
fffff800`00b9faf8 fffffa80`00000008 : 00000000`000000ff fffff880`06b03000 00000000`000000ff fffff880`0527ed3f : 0xfffff880`06b03000
fffff800`00b9fb00 00000000`000000ff : fffff880`06b03000 00000000`000000ff fffff880`0527ed3f fffffa80`0785a030 : 0xfffffa80`00000008
fffff800`00b9fb08 fffff880`06b03000 : 00000000`000000ff fffff880`0527ed3f fffffa80`0785a030 fffff880`00000880 : 0xff
fffff800`00b9fb10 00000000`000000ff : fffff880`0527ed3f fffffa80`0785a030 fffff880`00000880 fffff880`00000000 : 0xfffff880`06b03000
fffff800`00b9fb18 fffff880`0527ed3f : fffffa80`0785a030 fffff880`00000880 fffff880`00000000 fffff880`051d559a : 0xff
fffff800`00b9fb20 fffffa80`0785a030 : fffff880`00000880 fffff880`00000000 fffff880`051d559a 00000000`0000000a : athrx+0x1a9d3f
fffff800`00b9fb28 fffff880`00000880 : fffff880`00000000 fffff880`051d559a 00000000`0000000a 00000000`00000015 : 0xfffffa80`0785a030
fffff800`00b9fb30 fffff880`00000000 : fffff880`051d559a 00000000`0000000a 00000000`00000015 fffffa80`0785a030 : 0xfffff880`00000880
fffff800`00b9fb38 fffff880`051d559a : 00000000`0000000a 00000000`00000015 fffffa80`0785a030 00000000`00000000 : 0xfffff880`00000000
fffff800`00b9fb40 00000000`0000000a : 00000000`00000015 fffffa80`0785a030 00000000`00000000 fffff880`06b03000 : athrx+0x10059a
fffff800`00b9fb48 00000000`00000015 : fffffa80`0785a030 00000000`00000000 fffff880`06b03000 fffff880`051f12a4 : 0xa
fffff800`00b9fb50 fffffa80`0785a030 : 00000000`00000000 fffff880`06b03000 fffff880`051f12a4 fffffa80`07854030 : 0x15
fffff800`00b9fb58 00000000`00000000 : fffff880`06b03000 fffff880`051f12a4 fffffa80`07854030 fffff880`00000000 : 0xfffffa80`0785a030


STACK_COMMAND:  .thread 0xfffffa8003cf3660 ; kb

FOLLOWUP_IP: 
athrx+11bdd9
fffff880`051f0dd9 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  athrx+11bdd9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ee5fb55

FAILURE_BUCKET_ID:  X64_0xB8_athrx+11bdd9

BUCKET_ID:  X64_0xB8_athrx+11bdd9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xb8_athrx+11bdd9

FAILURE_ID_HASH:  {369abbba-1343-316a-945a-655e137bac08}

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

0: kd> lmvm athrx
start             end                 module name
fffff880`050d5000 fffff880`05387000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Mon Dec 12 18:32:13 2011 (4EE5FB55)
    CheckSum:         002AF309
    ImageSize:        002B2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Yodaisback · 02 Mar 2015

Thanks for your help !

Merci et à bientôt.

Olivier

Arc · 03 Mar 2015

bienvenue.
Faites-nous savoir pour toute autre question.