Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\072710-46562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82846000 PsLoadedModuleList = 0x82985570
Debug session time: Tue Jul 27 18:25:12.916 2010 (GMT-4)
System Uptime: 0 days 0:26:43.712
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {f07ab8, 2, 0, 89b5d794}
Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\ipsdefs\20100723.001\IDSvix86.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IDSvix86.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvix86.sys
Probably caused by : IDSvix86.sys ( IDSvix86+25794 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00f07ab8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 89b5d794, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 829a5700
Unable to read MiSystemVaType memory at 829850c0
00f07ab8
CURRENT_IRQL: 2
FAULTING_IP:
IDSvix86+25794
89b5d794 8b1b mov ebx,dword ptr [ebx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 80e45f64 -- (.trap 0xffffffff80e45f64)
ErrCode = 00000000
eax=000002bf ebx=00f07ab8 ecx=84fb1028 edx=000002bf esi=80e460ac edi=00000202
eip=89b5d794 esp=80e45fd8 ebp=80e45fe8 iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010283
IDSvix86+0x25794:
89b5d794 8b1b mov ebx,dword ptr [ebx] ds:0023:00f07ab8=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 89b5d794 to 8287eb7b
STACK_TEXT:
80e45f64 89b5d794 badb0d00 000002bf 82814ba9 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
80e45fe8 89b633e4 000004c1 84fb1010 80e46014 IDSvix86+0x25794
80e45ff8 89b6140a 80e460ac 84fbaff4 84fba858 IDSvix86+0x2b3e4
80e46014 89b5ee66 80e460ac 00000000 84fba7e8 IDSvix86+0x2940a
80e46044 89b5f0b6 80e460ac 84fba7e8 849575b0 IDSvix86+0x26e66
80e46060 89b5bdc2 00000001 80e460ac 00000000 IDSvix86+0x270b6
80e46084 89b3af3b 849575b0 00000001 80e460ac IDSvix86+0x23dc2
80e460e8 89b4aa48 849575b0 8756e870 00000001 IDSvix86+0x2f3b
80e4615c 896b2ef2 80e4641c 80e4644c 84bd49c0 IDSvix86+0x12a48
80e46180 8969c912 00000000 89b4a970 80e4641c NETIO!ProcessNonBufferedCallout+0x23
80e461dc 8969d334 00000018 80e4641c 80e4644c NETIO!ProcessCallout+0x184
80e46250 8969c25c 00000018 80e4641c 80e4644c NETIO!ArbitrateAndEnforce+0xae
80e46360 898c5a74 00000018 80e4641c 80e4644c NETIO!KfdClassify+0x1c7
80e465a8 89894c72 00000011 000055cd 000055cd tcpip!WFPDatagramDataShimV4+0x3e0
80e46604 89891746 84e03008 87568cc8 87568cc8 tcpip!WfpDatagramDataIndicate+0x67
80e46758 89894919 80e4680c 00000011 00000002 tcpip!ProcessALEForTransportPacket+0x4db
80e46804 89891f52 84e03008 80e46a50 00000011 tcpip!ProcessAleForNonTcpIn+0x92
80e46a64 89893c76 00000011 00000002 000055cd tcpip!WfpProcessInTransportStackIndication+0x5c8
80e46ab8 89892e7b 84e03008 00000002 00000011 tcpip!InetInspectReceiveDatagram+0x100
80e46b78 89893351 855f4f80 86cfd9c0 00000000 tcpip!UdpBeginMessageIndication+0x54
80e46bc4 8989dd52 00000000 86cfd9c0 86c8c100 tcpip!UdpDeliverDatagrams+0x1d9
80e46c10 898a018f 855f4f80 00c8c100 80e46c4c tcpip!UdpReceiveDatagrams+0x142
80e46c20 8989f48e 80e46c34 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
80e46c4c 8989f251 898ff114 80e46ca0 c000023e tcpip!IppDeliverListToProtocol+0x49
80e46c6c 8989ef26 898fed98 00000011 80e46ca0 tcpip!IppProcessDeliverList+0x2a
80e46cc4 8985a872 898fed98 00000011 855f4a10 tcpip!IppReceiveHeaderBatch+0x1f2
80e46cec 82a32f8c 855baf08 008fed98 848b8d48 tcpip!IppLoopbackTransmit+0x52
80e46d00 828a1083 855f4a10 00000000 848b8d48 nt!IopProcessWorkItem+0x23
80e46d50 82a2dd6e 00000001 9e1373c6 00000000 nt!ExpWorkerThread+0x10d
80e46d90 828cf159 828a0f76 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
IDSvix86+25794
89b5d794 8b1b mov ebx,dword ptr [ebx]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: IDSvix86+25794
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: IDSvix86
IMAGE_NAME: IDSvix86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bfe26aa
FAILURE_BUCKET_ID: 0xD1_IDSvix86+25794
BUCKET_ID: 0xD1_IDSvix86+25794
Followup: MachineOwner
---------