Hello, I'm hoping someone can assist me with a few servers that are blue screening. I recovered the minidump file from the c:\windows\minidump directory, and loaded them into the Windows debugger and ran a !analyze -v on them, I it comes back with "Probably caused by: i8042.sys". Being this is a built in driver into Windows, I am unsure that is really the culprit. For what it is worth, These are Server 2008 R2 boxes (non SP1), running on VMWare ESI 4.1, with VMTools up to date. Maybe someone can provide some guidance. Here is a copy and paste of the results of the minidump file: Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [Z:\Dump Files\happ-vpatmgrwb2\010212-106703-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 UP Free x64 Product: Server, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`01656000 PsLoadedModuleList = 0xfffff800`01893e50 Debug session time: Mon Jan 2 02:58:37.750 2012 (GMT-6) System Uptime: 0 days 0:00:52.515 Loading Kernel Symbols ............................................................... .......................................... Loading User Symbols Loading unloaded module list . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 44, {fffffa80044d7a50, eae, 0, 0} Probably caused by : i8042prt.sys ( i8042prt!I8xPnP+2b0 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MULTIPLE_IRP_COMPLETE_REQUESTS (44) A driver has requested that an IRP be completed (IoCompleteRequest()), but the packet has already been completed. This is a tough bug to find because the easiest case, a driver actually attempted to complete its own packet twice, is generally not what happened. Rather, two separate drivers each believe that they own the packet, and each attempts to complete it. The first actually works, and the second fails. Tracking down which drivers in the system actually did this is difficult, generally because the trails of the first driver have been covered by the second. However, the driver stack for the current request can be found by examining the DeviceObject fields in each of the stack locations. Arguments: Arg1: fffffa80044d7a50, Address of the IRP Arg2: 0000000000000eae Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ IRP_ADDRESS: fffffa80044d7a50 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x44 PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800016b0365 to fffff800016c6740 STACK_TEXT: fffff880`01f628f8 fffff800`016b0365 : 00000000`00000044 fffffa80`044d7a50 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx fffff880`01f62900 fffff880`011c8ac5 : 00000000`c00000bb 00000000`00000005 fffffa80`045aae40 fffffa80`03c9ce60 : nt! ?? ::FNODOBFM::`string'+0x3ec7e fffff880`01f629e0 fffff880`011ca6d5 : fffff880`011ca6b8 fffffa80`045aae40 fffffa80`03eb9360 fffff880`01f62aa0 : ACPI!ACPIIrpInvokeDispatchRoutine+0x7d fffff880`01f62a20 fffff880`0119ba6f : fffffa80`04421b40 fffff880`02b7c437 fffffa80`044d7a50 00000000`00000000 : ACPI!ACPIBusIrpQueryCapabilities+0x1d fffff880`01f62a60 fffff880`02b88930 : 00000000`00000000 fffffa80`044219f0 00000000`00000000 fffffa80`044219f0 : ACPI!ACPIDispatchIrp+0x17b fffff880`01f62ae0 fffff880`02bb6cb6 : fffffa80`044d7a00 00000000`00000000 fffffa80`0444e300 fffff800`0000000c : i8042prt!I8xPnP+0x2b0 fffff880`01f62b70 fffff880`02bb0f60 : fffffa80`044d7a50 00000000`00000040 fffff800`0186b5a0 00000000`00000000 : mouclass!MouseSendIrpSynchronously+0x76 fffff880`01f62bd0 fffff880`02bb112f : fffffa80`044d7a50 fffff800`0186b5a0 fffffa80`042c7300 fffffa80`044471b0 : mouclass!MouseStart+0x94 fffff880`01f62c50 fffff800`019c2c43 : fffffa80`04447060 fffffa80`03cc5680 fffffa80`03cce9b0 fffffa80`03cc5680 : mouclass!MouseStartWorker+0x1f fffff880`01f62c80 fffff800`016d3961 : fffffa80`03cce900 fffff800`016ba358 fffff800`018cd150 e8e08b4c`00000000 : nt!IopProcessWorkItem+0x23 fffff880`01f62cb0 fffff800`0196ac06 : 85485024`4c8b4800 fffffa80`03cc5680 00000000`00000080 fffffa80`03cb7040 : nt!ExpWorkerThread+0x111 fffff880`01f62d40 fffff800`016a4c26 : fffff800`01840e80 fffffa80`03cc5680 fffffa80`03cc5b60 08740000`012024ac : nt!PspSystemThreadStartup+0x5a fffff880`01f62d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: i8042prt!I8xPnP+2b0 fffff880`02b88930 8bd8 mov ebx,eax SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: i8042prt!I8xPnP+2b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: i8042prt IMAGE_NAME: i8042prt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d FAILURE_BUCKET_ID: X64_0x44_i8042prt!I8xPnP+2b0 BUCKET_ID: X64_0x44_i8042prt!I8xPnP+2b0 Followup: MachineOwner ---------

Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Thanks

Hi, For general blue screen troubleshooting, http://mikemstech.blogspot.com/2011/11/windows-crash-dump-analysis.html MULTIPLE_IRP_COMPLETE_REQUESTS is a hard one to debug and it isn't likely due to i8042prt.sys. Do you have a kernel memory dump available? I might be able to point you in a couple of directions if you upload it to skydrive and post a link, http://mikemstech.blogspot.com/2010/08/skydrive-uploading-files-for-community.html If you need to split the file into smaller files, http://mikemstech.blogspot.com/2011/12/how-to-split-large-file-for-e-mail-and.html -- Mike Burr Technology