Help with ongoing Unexpected Kernel Mode Trap

Question

Hello!

I've had some recent BSOD appear more and more frequently, I thought I just had a virus of some sort so ran all the scans I had available and it seemed to have cleared it up. But it's back again, and happening at more frequent intervals.

Link to my most recent DMP file.

http://1drv.ms/1ssKpcQ

Any help would be greatly appreciated!

Answer 1

MB

This one crash was related to your atheros wireless lan driver.  I would install the newest driver available even if it is the same date as drivers do become corrupt

If you continue to crash I would remove Symantec as it is a huge cause of BSOD'S

Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Ken\Desktop\062014-42421-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

OK                                             C:\Users\Ken\Desktop

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: C:\Users\Ken\Desktop

Windows 8 Kernel Version 9200 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 9200.16864.amd64fre.win8_gdr.140309-1509

Machine Name:

Kernel base = 0xfffff80193485000 PsLoadedModuleList = 0xfffff80193751aa0

Debug session time: Fri Jun 20 06:50:48.317 2014 (UTC - 4:00)

System Uptime: 0 days 0:30:55.995

Loading Kernel Symbols

...............................................................

................................................................

.....................................................

Loading User Symbols

Loading unloaded module list

........

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, fffff88001a89cb0, fffff88017ebdf60, fffff8019354cef3}

*** WARNING: Unable to verify timestamp for athw8x.sys

*** ERROR: Module load completed but symbols could not be loaded for athw8x.sys

Probably caused by : athw8x.sys ( athw8x+1779 )

Followup: MachineOwner

---

3: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault).  The first number in the

bugcheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a *portion* of those codes:

If kv shows a taskGate

        use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

        use .trap on that value

Else

        .trap on the appropriate frame will show where the trap was taken

        (on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

Arg2: fffff88001a89cb0

Arg3: fffff88017ebdf60

Arg4: fffff8019354cef3

Debugging Details:

---

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

TRAP_FRAME:  fffff88005f7f29f -- (.trap 0xfffff88005f7f29f)

Unable to read trap frame at fffff880`05f7f29f

LAST_CONTROL_TRANSFER:  from fffff801934de769 to fffff801934df440

STACK_TEXT:  

fffff88001a89b68 fffff801934de769 : 000000000000007f 0000000000000008 fffff88001a89cb0 fffff88017ebdf60 : nt!KeBugCheckEx

fffff88001a89b70 fffff801934dc834 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69

fffff88001a89cb0 fffff8019354cef3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDoubleFaultAbort+0xb4

fffff88017ebdf60 fffff801934de842 : 0000000000000000 fffff88017ebe8c0 fffff88005f7f29f ffadadad00000000 : nt!KiDispatchException+0xb3

fffff88017ebe620 fffff801934ddef3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0xc2

fffff88017ebe800 fffff801934d9cd5 : fffff8019354b402 fffffa8005f89a10 fffffa8004ebe90c 0000000000000000 : nt!KiDebugServiceTrap+0xf3

fffff88017ebe998 fffff8019354b402 : fffffa8005f89a10 fffffa8004ebe90c 0000000000000000 fffff8019354dbc9 : nt!DebugPrint+0x15

fffff88017ebe9a0 fffff8019354dc8c : fffffa8005f89a10 fffffa8004ebe90c fffffa800a04d9d4 fffff88005c2b717 : nt!vDbgPrintExWithPrefixInternal+0x132

fffff88017ebeaa0 fffff88005c2b779 : fffff88005f7f250 0000000000000200 fffff88005f7f250 fffff88017ebe700 : nt!DbgPrintEx+0x30

fffff88017ebeae0 fffff88005f7f250 : 0000000000000200 fffff88005f7f250 fffff88017ebe700 fffffa8004ebe90c : athw8x+0x1779

fffff88017ebeae8 0000000000000200 : fffff88005f7f250 fffff88017ebe700 fffffa8004ebe90c fffff88005d14f0f : athw8x+0x355250

fffff88017ebeaf0 fffff88005f7f250 : fffff88017ebe700 fffffa8004ebe90c fffff88005d14f0f fffff88005ecc9f0 : 0x200

fffff88017ebeaf8 fffff88017ebe700 : fffffa8004ebe90c fffff88005d14f0f fffff88005ecc9f0 fffff88017ebecf8 : athw8x+0x355250

fffff88017ebeb00 fffffa8004ebe90c : fffff88005d14f0f fffff88005ecc9f0 fffff88017ebecf8 fffff88000000000 : 0xfffff880`17ebe700

fffff88017ebeb08 fffff88005d14f0f : fffff88005ecc9f0 fffff88017ebecf8 fffff88000000000 fffff88017ebecf8 : 0xfffffa80`04ebe90c

fffff88017ebeb10 fffff88005ecc9f0 : fffff88017ebecf8 fffff88000000000 fffff88017ebecf8 0000000000000000 : athw8x+0xeaf0f

fffff88017ebeb18 fffff88017ebecf8 : fffff88000000000 fffff88017ebecf8 0000000000000000 fffffa8009ddb030 : athw8x+0x2a29f0

fffff88017ebeb20 fffff88000000000 : fffff88017ebecf8 0000000000000000 fffffa8009ddb030 745f78745f687461 : 0xfffff880`17ebecf8

fffff88017ebeb28 fffff88017ebecf8 : 0000000000000000 fffffa8009ddb030 745f78745f687461 6675626464617178 : 0xfffff880`00000000

fffff88017ebeb30 0000000000000000 : fffffa8009ddb030 745f78745f687461 6675626464617178 65725f646c6f6820 : 0xfffff880`17ebecf8

STACK_COMMAND:  kb

FOLLOWUP_IP:

athw8x+1779

fffff880`05c2b779 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  athw8x+1779

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athw8x

IMAGE_NAME:  athw8x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fd9b1b4

FAILURE_BUCKET_ID:  0x7f_8_athw8x+1779

BUCKET_ID:  0x7f_8_athw8x+1779

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_athw8x+1779

FAILURE_ID_HASH:  {0903544c-cfac-6ee1-d1dc-387b7ac56f91}

Followup: MachineOwner

---

Answer 2

MB

There is a steep learning curve and analyzing them is as much art as science.  If you want to make the effort I would be happy to help you learn.  There is a lot to learn.

Answer 3

Thank you very much for the speedy reply,

I've updated the WLAN driver, it seems to have halted it.

Is it possible for me to analyze my own DMP files to find out the reason for the crashes, I noticed it was as easy as you searching what athw8x.sys was in the information given.

Thank you again!