Arty03
Welcome to Geeks to Go
Sorry you have waited, a little longer than we would wish for a reply
Your crash dump analysis is below
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.x86fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b814d0
Debug session time: Fri Feb 1 16:47:50.188 2013 (UTC - 5:00)
System Uptime: 0 days 0:26:05.438
*******************************************************************************
* *
* 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:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x7f_0
TRAP_FRAME: a6217940 -- (.trap 0xffffffffa6217940)
ErrCode = 00000000
eax=00000000 ebx=a6217ae0 ecx=00000000 edx=00000000 esi=97d46e35 edi=00000001
eip=82ac1f70 esp=a62179b4 ebp=a62179c8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!ExAcquireRundownProtectionCacheAwareEx+0x11:
82ac1f70 f7760c div eax,dword ptr [esi+0Ch] ds:0023:97d46e41=????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ac1f70 to 82a7575b
STACK_TEXT:
a6217940 82ac1f70 badb0d00 00000000 00000000 nt!KiTrap00+0x8b
a62179b8 88c88f09 a6217a24 a6217a10 a62179ec nt!ExAcquireRundownProtectionCacheAwareEx+0x11
a62179c8 88c88fc4 859472b0 00000000 fc01020a tcpip!FlpNdisRequest+0x1b
a62179ec 88c88f9a a6217a10 a6217a90 a6217a24 tcpip!FlpQueryOid+0x20
a62179fc 88c86c62 a6217a10 85947720 84e214d4 tcpip!FlQueryInterface+0x5d
a6217a24 88c88383 859485f0 00000007 fc01020a tcpip!IppQueryInterfaceProperty+0xc3
a6217a94 88b6d294 a6217ae0 00000040 84e21000 tcpip!IpGetAllSubInterfaceParameters+0x184
a6217b4c 8d5a9ba1 84e21000 2b7baa3d 0000003c NETIO!NsiEnumerateObjectsAllParametersEx+0x4e6
a6217bc0 8d5aaefc 84e2103c 00000000 84e21054 nsiproxy!NsippEnumerateObjectsAllParameters+0xeb
a6217be4 8d5aafe5 857d1801 00000000 862e3038 nsiproxy!NsippDispatchDeviceControl+0x78
a6217bfc 82a6dc29 857dae10 857d1800 857d1800 nsiproxy!NsippDispatch+0x33
a6217c14 82c62b29 862e3038 857d1800 857d1870 nt!IofCallDriver+0x63
a6217c34 82c65cfb 857dae10 862e3038 00000000 nt!IopSynchronousServiceTail+0x1f8
a6217cd0 82cac63b 857dae10 857d1800 00000000 nt!IopXxxControlFile+0x6aa
a6217d04 82a748fa 0000011c 00000688 00000000 nt!NtDeviceIoControlFile+0x2a
a6217d04 77247094 0000011c 00000688 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01bdf68c 00000000 00000000 00000000 00000000 0x77247094
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!NsiEnumerateObjectsAllParametersEx+4e6
88b6d294 eb99 jmp NETIO!NsiEnumerateObjectsAllParametersEx+0x46f (88b6d22f)
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!NsiEnumerateObjectsAllParametersEx+4e6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME:
NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 5034f1ea
FAILURE_BUCKET_ID: 0x7f_0_NETIO!NsiEnumerateObjectsAllParametersEx+4e6
BUCKET_ID: 0x7f_0_NETIO!NsiEnumerateObjectsAllParametersEx+4e6
I would start by updating or if you have the latest, reinstalling you network drivers -
Edited by Macboatmaster, 12 February 2013 - 12:56 PM.