Hi,
The attached DMP file is of the
UNEXPECTED_KERNEL_MODE_TRAP (7f) bug check.
This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
BugCheck 7F, {
8, 80050033, 406f8, fffff800040b0447}
The 1st parameter is 8 which indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
- A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault.
If we take a look at the call stack:
Code:
0: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff800`00ba4d28 fffff800`040751a9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`04073672 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`040b0447 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 (TrapFrame @ fffff800`00ba4e70)
fffff880`02ab8c40 fffff800`04075282 : fffff880`02ab9418 00000000`0000004f fffff880`02ab94c0 fffff880`06bcb880 : nt!KiDispatchException+0xab
fffff880`02ab92e0 fffff800`04074933 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ab94c0 fffff800`0406da55 : fffff800`040b4d85 002d0032`0033006e 0070002d`006e0065 002e006c`00630065 : nt!KiDebugServiceTrap+0xf3 (TrapFrame @ fffff880`02ab94c0)
fffff880`02ab9658 fffff800`040b4d85 : 002d0032`0033006e 0070002d`006e0065 002e006c`00630065 00000078`00640069 : nt!DebugPrint+0x15
fffff880`02ab9660 fffff800`040b0888 : 00000000`00000000 fffff880`06b8ee60 fffff880`02ab9b68 fffff880`0684f353 : nt! ?? ::FNODOBFM::`string'+0xc4c2
fffff880`02ab9910 fffff880`069a666d : fffff880`06bcb880 00000000`00000200 fffff880`06bcb880 00000000`ffffffff : nt!DbgPrintEx+0x30
fffff880`02ab9950 fffff880`06bcb880 : 00000000`00000200 fffff880`06bcb880 00000000`ffffffff fffffa80`0a782858 : athrx+0x15866d
fffff880`02ab9958 00000000`00000200 : fffff880`06bcb880 00000000`ffffffff fffffa80`0a782858 fffff880`069c7f35 : athrx+0x37d880
fffff880`02ab9960 fffff880`06bcb880 : 00000000`ffffffff fffffa80`0a782858 fffff880`069c7f35 fffff880`06b8ee60 : 0x200
fffff880`02ab9968 00000000`ffffffff : fffffa80`0a782858 fffff880`069c7f35 fffff880`06b8ee60 fffff880`02ab9b68 : athrx+0x37d880
fffff880`02ab9970 fffffa80`0a782858 : fffff880`069c7f35 fffff880`06b8ee60 fffff880`02ab9b68 fffff880`00000000 : 0xffffffff
fffff880`02ab9978 fffff880`069c7f35 : fffff880`06b8ee60 fffff880`02ab9b68 fffff880`00000000 fffff880`02ab9b68 : 0xfffffa80`0a782858
fffff880`02ab9980 fffff880`06b8ee60 : fffff880`02ab9b68 fffff880`00000000 fffff880`02ab9b68 00000000`00000000 : athrx+0x179f35
fffff880`02ab9988 fffff880`02ab9b68 : fffff880`00000000 fffff880`02ab9b68 00000000`00000000 01000018`00002000 : athrx+0x340e60
fffff880`02ab9990 fffff880`00000000 : fffff880`02ab9b68 00000000`00000000 01000018`00002000 745f7874`5f687461 : 0xfffff880`02ab9b68
fffff880`02ab9998 fffff880`02ab9b68 : 00000000`00000000 01000018`00002000 745f7874`5f687461 66756264`64617178 : 0xfffff880`00000000
fffff880`02ab99a0 00000000`00000000 : 01000018`00002000 745f7874`5f687461 66756264`64617178 65725f64`6c6f6820 : 0xfffff880`02ab9b68
We can see many
athrx.sys (Atheros network adapter driver) calls before the double fault, which more than likely indicates that's what caused it and then the eventual bug check itself. Usually when we have network related crashes like this they are caused by one of two things:
1. Network driver(s) themselves need to be updated. Visit HP's website and ensure all of your network drivers are the latest vesion -
HP Support, Drivers, Contact and Help Forums | HP ® Support
2. 3rd party antivirus or firewall software causing network conflicts. I took a quick look at the loaded modules list and it appears you have neither installed, but just to be sure, do you?
Regards,
Patrick