久々にWindowsネタ
現象が発生しないPCのダンプを見た。
wlatNUGv.sys で不具合が発生している。
しかし、今回は0x7Fというコードだが、他の3つは0x9Fというコードだった。
このダンプだけなぜかパラメータが全て「0」だった。
最初はメモリかと思ったが、他のダンプも全て「wlatNUGv.sys 」で不具合を起こしている。
この「wlatNUGv.sys 」は何かと思うと、
Image path: \SystemRoot\system32\DRIVERS\wlatNUGv.sys
という場所にあるらしいので、プロパティで確認するとAtermのWL300??という機種の持ち物だった。
他にも不具合があるかもしれないが、Atermのドライバにも不具合がある可能性が高い。
しかし、この「wlatNUGv.sys 」というファイル、Googleで検索しても引っかからない。
よほど情報がなかったと考えればいいのか？
---------------------------------------------------------------------------------
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\wlatNUGv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wlatNUGv.sys
*** ERROR: Module load completed but symbols could not be loaded for wlatNUGv.sys
Probably caused by : wlatNUGv.sys ( wlatNUGv+4b340 )
Followup: MachineOwner
---------
1: 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: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1
TRAP_FRAME: 96b5ecf4 -- (.trap 0xffffffff96b5ecf4)
ErrCode = 00000000
eax=a2654330 ebx=00000000 ecx=851cd000 edx=851cd000 esi=8512c118 edi=00000000
eip=a2657340 esp=96b5ed68 ebp=96b5ed68 iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
wlatNUGv+0x4b340:
a2657340 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 8209c836 to 81eebadf
STACK_TEXT:
96b5ec94 8209c836 0000007f 2cc007b5 a2657340 nt!KeBugCheck+0x14
96b5ece8 81e69a08 96b5ecf4 96b5ed68 a2657340 nt!Ki386CheckDivideByZeroTrap+0x44
96b5ece8 a2657340 96b5ecf4 96b5ed68 a2657340 nt!KiTrap00+0x88
WARNING: Stack unwind information not available. Following frames may be wrong.
96b5ed64 96b5ed7c a262054d 851cd000 a3111370 wlatNUGv+0x4b340
96b5ed68 a262054d 851cd000 a3111370 a3111370 0x96b5ed7c
96b5ed7c 81ff3c42 851cd000 2cc0069d 00000000 wlatNUGv+0x1454d
96b5edc0 81e5cefe a2620460 851cd000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
wlatNUGv+4b340
a2657340 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: wlatNUGv+4b340
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wlatNUGv
IMAGE_NAME: wlatNUGv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4987a275
FAILURE_BUCKET_ID: 0x7f_0_wlatNUGv+4b340
BUCKET_ID: 0x7f_0_wlatNUGv+4b340
Followup: MachineOwner
---------
1: kd> lmvm wlatNUGv
start end module name
a260c000 a26a2000 wlatNUGv T (no symbols)
Loaded symbol image file: wlatNUGv.sys
Image path: \SystemRoot\system32\DRIVERS\wlatNUGv.sys
Image name: wlatNUGv.sys
Timestamp: Tue Feb 03 10:48:37 2009 (4987A275)
CheckSum: 000714AC
ImageSize: 00096000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4