Early this morning my computer suddenly crashed with a bugcheck of 0x000000D1, Debbuging tools for windows says the probable cause was TCPIP.sys this is also not the first time ive had a crash related to TCPIP.sys here is info from the crash dump 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: fffffa800aec0000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88001970ae7, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: fffffa800aec0000 CURRENT_IRQL: 2 FAULTING_IP: tcpip!Ipv6AddressType+27 fffff880`01970ae7 664439410a cmp word ptr [rcx+0Ah],r8w DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800cdb6a10 -- (.trap 0xfffff8800cdb6a10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000220 rbx=0000000000000000 rcx=fffffa800aebfff6 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001970ae7 rsp=fffff8800cdb6ba0 rbp=fffffa8005cd8cb0 r8=000000000000fe5e r9=fffffa800aebfff6 r10=0000000000001000 r11=fffff8800cdb6d48 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc tcpip!Ipv6AddressType+0x27: fffff880`01970ae7 664439410a cmp word ptr [rcx+0Ah],r8w ds:aef0:0000=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034dbbe9 to fffff800034dc640 STACK_TEXT: fffff880`0cdb68c8 fffff800`034dbbe9 : 00000000`0000000a fffffa80`0aec0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0cdb68d0 fffff800`034da860 : fffffa80`03c3c3c0 fffff880`0196e224 00000000`00000000 fffffa80`04835010 : nt!KiBugCheckDispatch+0x69 fffff880`0cdb6a10 fffff880`01970ae7 : fffffa80`0aebffae 00000000`00000000 00000000`00000000 fffffa80`05cd8cb0 : nt!KiPageFault+0x260 fffff880`0cdb6ba0 fffff880`0190e6fc : fffff880`0cdb6e40 fffffa80`05cd8cb0 00000000`00000000 fffffa80`05cdb3b0 : tcpip!Ipv6AddressType+0x27 fffff880`0cdb6bd0 fffff880`018f5111 : fffffa80`0484a1e0 fffff880`0cdb6e40 00000000`00000002 fffffa80`04dbfe38 : tcpip!IppValidateSetAllRouteParameters+0x8c fffff880`0cdb6cd0 fffff880`019008a2 : fffffa80`04835010 fffffa80`05cd8cb0 fffffa80`05cd8cb0 fffffa80`05c8aef0 : tcpip!IppUpdateUnicastRouteUnderLock+0x81 fffff880`0cdb6d50 fffff880`01a045bc : fffffa80`05cdb3b0 fffffa80`0aebffae fffffa80`0aebfff6 00000000`ffffffff : tcpip!IppUpdateUnicastRoute+0xb2 fffff880`0cdb6df0 fffff880`01a2b2f9 : 00000000`00000020 00000000`00000e10 fffffa80`05cd8cb0 fffffa80`07c2aa60 : tcpip!IppUpdateAutoConfiguredRoute+0xac fffff880`0cdb6e70 fffff880`01a2b99b : fffffa80`04818000 fffffa80`057e4440 00000000`00000086 00000000`00000000 : tcpip!Ipv6pHandleRouterAdvertisement+0x6a9 fffff880`0cdb6fd0 fffff880`0194619e : fffff880`082e5480 00000000`00000000 fffff880`01a55800 00000000`0000ffff : tcpip!Icmpv6ReceiveDatagrams+0x34b fffff880`0cdb7070 fffff880`01945caa : 00000000`00000000 00000000`00000000 fffff880`01a55800 fffffa80`05827d58 : tcpip!IppDeliverListToProtocol+0xfe fffff880`0cdb7130 fffff880`019452a9 : fffffa80`05bab820 fffff880`06c30549 fffffa80`05bad0c0 fffff880`0cdb7220 : tcpip!IppProcessDeliverList+0x5a fffff880`0cdb71d0 fffff880`01942fff : 00000000`00000000 00000000`05cd4b01 fffff880`01a55800 fffff880`01a55800 : tcpip!IppReceiveHeaderBatch+0x23a fffff880`0cdb72b0 fffff880`019425f2 : fffffa80`05c8aef0 00000000`00000000 fffffa80`05cd4b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f fffff880`0cdb74b0 fffff880`01941a8a : fffffa80`05cd4ba0 fffff880`0cdb75e0 fffffa80`05cd4ba0 fffffa80`05720001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`0cdb7590 fffff800`034e9078 : fffffa80`07c2a930 00000000`00004800 fffffa80`04628b60 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`0cdb75e0 fffff880`01942152 : fffff880`019419b0 fffff800`00040004 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8 fffff880`0cdb76c0 fffff880`015830eb : fffffa80`05cd98d0 00000000`00000000 fffffa80`058a61a0 fffff800`0364ee80 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`0cdb7730 fffff880`0154cad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`0cdb77a0 fffff880`01514a3e : fffffa80`058a61a0 00000000`00000002 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 fffff880`0cdb7c20 fffff880`01514d33 : fffffa80`058a61a0 fffffa80`058a61a0 00000000`00000000 fffffa80`058a7300 : ndis!ndisDoPeriodicReceivesIndication+0x14e fffff880`0cdb7c80 fffff880`014fef3d : 00000000`00010302 00000000`00000002 00000000`00000000 fffffa80`058a7388 : ndis!ndisPeriodicReceivesWorker+0x63 fffff880`0cdb7cb0 fffff800`03779cce : 00000000`00000001 fffffa80`04628b60 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x1bd fffff880`0cdb7d40 fffff800`034cdfe6 : fffff880`009ed180 fffffa80`04628b60 fffffa80`071fdb60 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0cdb7d80 00000000`00000000 : fffff880`0cdb8000 fffff880`0cdb2000 fffff880`0cdb7a00 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: tcpip!Ipv6AddressType+27 fffff880`01970ae7 664439410a cmp word ptr [rcx+0Ah],r8w SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: tcpip!Ipv6AddressType+27 FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79420 FAILURE_BUCKET_ID: X64_0xD1_tcpip!Ipv6AddressType+27 BUCKET_ID: X64_0xD1_tcpip!Ipv6AddressType+27 Followup: MachineOwner here is a link to the memory dump http://www.filefactory.com/file/cb35c7b/n/MEMORY_DMP

I see two possibilities: a firewall issue (ZoneAlarm has a bad reputation here) - try deactivating it and see if it makes a difference; or a driver issue with the NIC - try updating that one from the manufacturer's website.My grandmother always used to say: "::1: sweet ::1:"

SYMBOL_NAME: tcpip!Ipv6AddressType+27 Do you use IPv6? If not, please uncheck it in the network and sharing center. In addition, update the BIOS and network card to the latest one. If the issue persists, since troubleshoot this kind of kernel crash issue is beyond what we can do in this forum. Please contact Microsoft Customer Service and Support http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Bug Check Code 0xD1: http://msdn.microsoft.com/en-us/library/ff560244(VS.85).aspx ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffffa800aec0000, 2, 0, fffff88001970ae7} Probably caused by : tcpip.sys ( tcpip!Ipv6AddressType+27 ) Followup: MachineOwner --------- 0: 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: fffffa800aec0000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88001970ae7, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: fffffa800aec0000 CURRENT_IRQL: 2 FAULTING_IP: tcpip!Ipv6AddressType+27 fffff880`01970ae7 664439410a cmp word ptr [rcx+0Ah],r8w DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800cdb6a10 -- (.trap 0xfffff8800cdb6a10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000220 rbx=0000000000000000 rcx=fffffa800aebfff6 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001970ae7 rsp=fffff8800cdb6ba0 rbp=fffffa8005cd8cb0 r8=000000000000fe5e r9=fffffa800aebfff6 r10=0000000000001000 r11=fffff8800cdb6d48 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc tcpip!Ipv6AddressType+0x27: fffff880`01970ae7 664439410a cmp word ptr [rcx+0Ah],r8w ds:aef0:0000=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034dbbe9 to fffff800034dc640 STACK_TEXT: fffff880`0cdb68c8 fffff800`034dbbe9 : 00000000`0000000a fffffa80`0aec0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0cdb68d0 fffff800`034da860 : fffffa80`03c3c3c0 fffff880`0196e224 00000000`00000000 fffffa80`04835010 : nt!KiBugCheckDispatch+0x69 fffff880`0cdb6a10 fffff880`01970ae7 : fffffa80`0aebffae 00000000`00000000 00000000`00000000 fffffa80`05cd8cb0 : nt!KiPageFault+0x260 fffff880`0cdb6ba0 fffff880`0190e6fc : fffff880`0cdb6e40 fffffa80`05cd8cb0 00000000`00000000 fffffa80`05cdb3b0 : tcpip!Ipv6AddressType+0x27 fffff880`0cdb6bd0 fffff880`018f5111 : fffffa80`0484a1e0 fffff880`0cdb6e40 00000000`00000002 fffffa80`04dbfe38 : tcpip!IppValidateSetAllRouteParameters+0x8c fffff880`0cdb6cd0 fffff880`019008a2 : fffffa80`04835010 fffffa80`05cd8cb0 fffffa80`05cd8cb0 fffffa80`05c8aef0 : tcpip!IppUpdateUnicastRouteUnderLock+0x81 fffff880`0cdb6d50 fffff880`01a045bc : fffffa80`05cdb3b0 fffffa80`0aebffae fffffa80`0aebfff6 00000000`ffffffff : tcpip!IppUpdateUnicastRoute+0xb2 fffff880`0cdb6df0 fffff880`01a2b2f9 : 00000000`00000020 00000000`00000e10 fffffa80`05cd8cb0 fffffa80`07c2aa60 : tcpip!IppUpdateAutoConfiguredRoute+0xac fffff880`0cdb6e70 fffff880`01a2b99b : fffffa80`04818000 fffffa80`057e4440 00000000`00000086 00000000`00000000 : tcpip!Ipv6pHandleRouterAdvertisement+0x6a9 fffff880`0cdb6fd0 fffff880`0194619e : fffff880`082e5480 00000000`00000000 fffff880`01a55800 00000000`0000ffff : tcpip!Icmpv6ReceiveDatagrams+0x34b fffff880`0cdb7070 fffff880`01945caa : 00000000`00000000 00000000`00000000 fffff880`01a55800 fffffa80`05827d58 : tcpip!IppDeliverListToProtocol+0xfe fffff880`0cdb7130 fffff880`019452a9 : fffffa80`05bab820 fffff880`06c30549 fffffa80`05bad0c0 fffff880`0cdb7220 : tcpip!IppProcessDeliverList+0x5a fffff880`0cdb71d0 fffff880`01942fff : 00000000`00000000 00000000`05cd4b01 fffff880`01a55800 fffff880`01a55800 : tcpip!IppReceiveHeaderBatch+0x23a fffff880`0cdb72b0 fffff880`019425f2 : fffffa80`05c8aef0 00000000`00000000 fffffa80`05cd4b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f fffff880`0cdb74b0 fffff880`01941a8a : fffffa80`05cd4ba0 fffff880`0cdb75e0 fffffa80`05cd4ba0 fffffa80`05720001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`0cdb7590 fffff800`034e9078 : fffffa80`07c2a930 00000000`00004800 fffffa80`04628b60 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`0cdb75e0 fffff880`01942152 : fffff880`019419b0 fffff800`00040004 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8 fffff880`0cdb76c0 fffff880`015830eb : fffffa80`05cd98d0 00000000`00000000 fffffa80`058a61a0 fffff800`0364ee80 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`0cdb7730 fffff880`0154cad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`0cdb77a0 fffff880`01514a3e : fffffa80`058a61a0 00000000`00000002 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 fffff880`0cdb7c20 fffff880`01514d33 : fffffa80`058a61a0 fffffa80`058a61a0 00000000`00000000 fffffa80`058a7300 : ndis!ndisDoPeriodicReceivesIndication+0x14e fffff880`0cdb7c80 fffff880`014fef3d : 00000000`00010302 00000000`00000002 00000000`00000000 fffffa80`058a7388 : ndis!ndisPeriodicReceivesWorker+0x63 fffff880`0cdb7cb0 fffff800`03779cce : 00000000`00000001 fffffa80`04628b60 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x1bd fffff880`0cdb7d40 fffff800`034cdfe6 : fffff880`009ed180 fffffa80`04628b60 fffffa80`071fdb60 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0cdb7d80 00000000`00000000 : fffff880`0cdb8000 fffff880`0cdb2000 fffff880`0cdb7a00 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: tcpip!Ipv6AddressType+27 fffff880`01970ae7 664439410a cmp word ptr [rcx+0Ah],r8w SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: tcpip!Ipv6AddressType+27 FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79420 FAILURE_BUCKET_ID: X64_0xD1_tcpip!Ipv6AddressType+27 BUCKET_ID: X64_0xD1_tcpip!Ipv6AddressType+27 Followup: MachineOwner --------- 0: kd> lmvm tcpip start end module name fffff880`018e9000 fffff880`01aed000 tcpip (pdb symbols) downstreamstore\tcpip.pdb\ABB23D00EE7E4165B6AFF66F2DF02EB22\tcpip.pdb Loaded symbol image file: tcpip.sys Image path: \SystemRoot\System32\drivers\tcpip.sys Image name: tcpip.sys Timestamp: Sat Nov 20 10:25:52 2010 (4CE79420) CheckSum: 001E58E5 ImageSize: 00204000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 ________________________________________________________________________________________ I don't see a Microsoft hotfix for that. Start by updating your NIC Card drivers and check again. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

i do not currently use IPv6, i do have a firewall, Comodo Internet Security i will update the BIOS from 0901 to 0902, and will update the LAN driver later in the day and reply with the results.

updated the BIOS and the NIC drive was up to date. also disabled IPv6 but have not tested it yet (it happened during a multiplayer game)

Update all possible drivers and check again. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

this happened during a game so i dont know if there really is a way to check it again i think it might be faulty motherboard or ram.