Has anyone seen a similar crash? This is a busy system with 16 cores and the crash occurs intermittently. Thanks in advance.!analyze -v info: Symbol search path is: srv*C:\windows\system32\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (16 procs) Free x64Product: Server, suite: Enterprise TerminalServer SingleUserTSBuilt by: 3790.srv03_sp2_gdr.070321-2337Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140Debug session time: Wed Jul 23 08:57:43.743 2008 (GMT-7)System Uptime: 0 days 7:55:59.095Loading Kernel Symbols.......................................................................................................................Loading User Symbols Loading unloaded module list.....******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 44, {fffffadfff663010, d76, 0, 0} Probably caused by : tcpip.sys ( tcpip!TCPDataRequestComplete+e1 ) Followup: MachineOwner--------- 12: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** MULTIPLE_IRP_COMPLETE_REQUESTS (44)A driver has requested that an IRP be completed (IoCompleteRequest()), butthe packet has already been completed. This is a tough bug to find becausethe easiest case, a driver actually attempted to complete its own packettwice, is generally not what happened. Rather, two separate drivers eachbelieve that they own the packet, and each attempts to complete it. Thefirst actually works, and the second fails. Tracking down which driversin the system actually did this is difficult, generally because the trailsof the first driver have been covered by the second. However, the driverstack for the current request can be found by examining the DeviceObjectfields in each of the stack locations.Arguments:Arg1: fffffadfff663010, Address of the IRPArg2: 0000000000000d76Arg3: 0000000000000000Arg4: 0000000000000000 Debugging Details:------------------ IRP_ADDRESS: fffffadfff663010 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x44 PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80001079322 to fffff8000102e890 STACK_TEXT: fffffadf`29d43998 fffff800`01079322 : 00000000`00000044 fffffadf`ff663010 00000000`00000d76 00000000`00000000 : nt!KeBugCheckExfffffadf`29d439a0 fffffadf`26afd691 : 00000000`00001cfe fffffadf`363f5202 fffffadf`379f2c0c fffffadf`35837e40 : nt!IopfCompleteRequest+0xba5fffffadf`29d43a10 fffffadf`26b00cec : fffffadf`31137620 fffffadf`35889790 00000000`00000000 00000000`0000000c : tcpip!TCPDataRequestComplete+0xe1fffffadf`29d43a60 fffffadf`26b10a96 : fffffadf`35889700 00000000`00000002 00000000`00000000 fffffadf`35889790 : tcpip!CompleteRcvs+0x285fffffadf`29d43af0 fffffadf`26b007d5 : fffffadf`0000000c 00000000`000000c8 fffffadf`29d43ba8 fffffadf`29d43ba0 : tcpip!ProcessPerCpuTCBDelayQ+0x21efffffadf`29d43b80 fffffadf`26b0f7ff : fffffadf`26bb86c1 00000000`00000002 00000000`00000000 fffffadf`366da330 : tcpip!ProcessTCBDelayQ+0xebfffffadf`29d43bd0 fffff800`010375ca : fffffadf`26bb7e40 fffffadf`28772010 fffffadf`26bb7e40 fffffadf`28772010 : tcpip!LoopXmitRtn+0x360fffffadf`29d43d00 fffff800`0124a972 : fffffadf`38a027a0 00000000`00000080 fffffadf`38a027a0 fffffadf`29963680 : nt!ExpWorkerThread+0x13bfffffadf`29d43d70 fffff800`01020226 : fffffadf`2995b180 fffffadf`38a027a0 fffffadf`29963680 00000000`00000000 : nt!PspSystemThreadStartup+0x3efffffadf`29d43dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: tcpip!TCPDataRequestComplete+e1fffffadf`26afd691 488b742460 mov rsi,qword ptr [rsp+60h] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: tcpip!TCPDataRequestComplete+e1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 485bbae6 FAILURE_BUCKET_ID: X64_0x44_tcpip!TCPDataRequestComplete+e1 BUCKET_ID: X64_0x44_tcpip!TCPDataRequestComplete+e1nada

Hello, Based on some research, I found that this problem may be caused by some third-party drivers or programs (e.g. antivirus). I would firstly suggest that you contact the hardware manufacturers to make sure that all the drivers are up to date and then, try clean boot to see how it goes. I would also like to suggest that you contact our Microsoft Customer Service and Support (CSS) for this BSOD issue, as to locate the exact problem of the stop error, we need to analyze the crash dump file. You can speak directly with a Microsoft Support Professional to analyze the crash dump. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/directory/overview.asp Thank you for your cooperation and I hope this will be resolved soon. Best regards,Chang Yin