Hi, I'm often seeing Windows server 2008 (32-bit, latest updates) crash and generate a minidump, each time with the same call stack. Has anyone seen this before ? Windbg generates the following call stack: 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 8f84a269, The address that the exception occurred at Arg3: 8a9e39a0, Exception Record Address Arg4: 8a9e369c, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: USBPORT!USBPORT_EndpointFromHandle+e 8f84a269 ff760c push dword ptr [esi+0Ch] EXCEPTION_RECORD: 8a9e39a0 -- (.exr 0xffffffff8a9e39a0) ExceptionAddress: 8f84a269 (USBPORT!USBPORT_EndpointFromHandle+0x0000000e) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 0000000c Attempt to read from address 0000000c CONTEXT: 8a9e369c -- (.cxr 0xffffffff8a9e369c) eax=48706950 ebx=87996480 ecx=8599fd00 edx=00000000 esi=00000000 edi=00000000 eip=8f84a269 esp=8a9e3a68 ebp=8a9e3a70 iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 USBPORT!USBPORT_EndpointFromHandle+0xe: 8f84a269 ff760c push dword ptr [esi+0Ch] ds:0023:0000000c=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 0000000c READ_ADDRESS: GetPointerFromAddress: unable to read from 81d37868 Unable to read MiSystemVaType memory at 81d17420 0000000c FOLLOWUP_IP: USBPORT!USBPORT_EndpointFromHandle+e 8f84a269 ff760c push dword ptr [esi+0Ch] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 8f875e5d to 8f84a269 STACK_TEXT: 8a9e3a70 8f875e5d 00000000 8599f028 87996408 USBPORT!USBPORT_EndpointFromHandle+0xe 8a9e3a88 8f8765ce 8599f028 87996408 8599f028 USBPORT!USBPORT_AbortAllTransfers+0x4b 8a9e3aa8 8f876b83 8599f028 006d6572 00000008 USBPORT!USBPORT_RemoveDeviceHandle+0xc5 8a9e3ac8 8f86d002 564d4552 8599f028 00000100 USBPORT!USBPORT_NeoRemoveDevice+0x76 8a9e3adc 89fa1052 86dd8438 87996408 00000000 USBPORT!USBPORTBUSIF_RemoveUsbDevice+0x3c 8a9e3af0 89f9567c 86ddb028 87996408 00000000 usbhub!Usbh_HubRemoveUsbDevice+0x27 8a9e3b18 89fa266d 86ddb028 8715f6f0 78444833 usbhub!UsbhUnlinkPdoDeviceHandle+0xd3 8a9e3b40 89f95f19 86ddb0e0 8715f6f0 00000003 usbhub!UsbhDeregisterPdo+0xee 8a9e3b64 89f9f34d 86ddb028 8715f6f0 00000018 usbhub!Usbh_Disconnect_PdoEvent+0x51 8a9e3b88 89f9204c 00000006 86de8900 86ddb860 usbhub!Usbh_PCE_BusDisconnect_Action+0xf6 8a9e3ba8 89f925b2 86ddb028 86de8988 0000000b usbhub!UsbhDispatch_PortChangeQueueEventEx+0x104 8a9e3bd4 89f92585 86ddb028 86de8988 0000000b usbhub!UsbhDispatch_PortChangeQueueEvent+0x24 8a9e3c04 89fa0bf4 86ddb028 86de8988 0000000b usbhub!UsbhDispatch_PortChangeQueueNullEvent+0x20 8a9e3c20 89f9d470 86ddb028 86ddb860 00000002 usbhub!UsbhPCE_BusDisconnect+0x68 8a9e3c3c 89f951d4 86ddb028 86ddb860 86ddb860 usbhub!UsbhBusDisconnect_Action+0x3c 8a9e3c58 89f94e85 00000004 86ddb860 0000000b usbhub!Usbh_BS_BusPause+0x71 8a9e3c74 89f9da65 00000004 86ddb860 0000000b usbhub!UsbhDispatch_BusEvent+0xa3 8a9e3c94 89fa6975 86ddb028 86ddb860 86ddb0e0 usbhub!UsbhSyncBusDisconnect+0x31 8a9e3cb8 89fa6d09 86ddb028 86ddb860 00000004 usbhub!UsbhHardReset_Action+0x3e 8a9e3cd4 89f96330 86ddb860 00000004 86ddb028 usbhub!Usbh_HRS_Queued+0x91 8a9e3cf0 89fa6ae2 86ddb028 86ddb860 00000004 usbhub!UsbhDispatch_HardResetEvent+0x114 8a9e3d10 89f88a8a 86ddb028 00000000 86ddb860 usbhub!UsbhHardResetWorker+0x4a 8a9e3d30 81e0dcb9 86ddb028 870d4c58 8507b020 usbhub!UsbhHubWorker+0x51 8a9e3d44 81ca5e22 86f88b28 00000000 8507b020 nt!IopProcessWorkItem+0x23 8a9e3d7c 81dd5fe2 86f88b28 8495eb01 00000000 nt!ExpWorkerThread+0xfd 8a9e3dc0 81c3eefe 81ca5d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: USBPORT!USBPORT_EndpointFromHandle+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: USBPORT IMAGE_NAME: USBPORT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 49e01fcf STACK_COMMAND: .cxr 0xffffffff8a9e369c ; kb FAILURE_BUCKET_ID: 0x7E_USBPORT!USBPORT_EndpointFromHandle+e BUCKET_ID: 0x7E_USBPORT!USBPORT_EndpointFromHandle+e Followup: MachineOwner

Can you provide more information? are you trying to run off a USB attached storage? or is there some application that is writing large amounts of data or IO traffic to the USB at the time of the crash?:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.

Hello, Bug Check Code 0x1000007e: http://msdn.microsoft.com/en-us/library/ff557196(v=VS.85).aspx The BSOD was caused by USBPORT.SYS driver. More about it: http://www.usb-drivers.com/drivers/240/240747.htm Contact Intel Technical Support for more assistance. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 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 Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator

Can you provide more information? are you trying to run off a USB attached storage? or is there some application that is writing large amounts of data or IO traffic to the USB at the time of the crash? The crash was triggered by removing an USB modem.

The BSOD was caused by USBPORT.SYS driver. More about it: http://www.usb-drivers.com/drivers/240/240747.htm Contact Intel Technical Support for more assistance. Thanks for the help, but it's not clear to me why you propose to contact Intel Technical Support ? As far as I can see both USBPORT.sys and USBHUB.sys are Microsoft drivers.