In other words a request was sent to the drive and there was no response within the timeout period. The timeout errors (SRB_STATUS_TIMEOUT and SRB_STATUS_COMMAND_TIMEOUT) indicate a request timed out in the adapter. A list of SRB statuses can be found in srb.h. The most common SRB statuses are below: SRB_STATUS_TIMEOUT - 0x09Ī complete list of SCSI operations and statuses can be found in scsi.h in the WDK. The most common SCSI commands are: SCSIOP_READ - 0x28 In this case the SCSI status was 00 (SCSISTAT_GOOD), the SRB status was 09 (SRB_STATUS_TIMEOUT), and the command was 28 (SCSIOP_READ). In the example above at byte offset 29 is the SCSI status, at offset 30 is the SRB status that caused the retry, and at offset 31 is the SCSI command that is being retried.
STORAHCI ERROR 129 DRIVER
The error returned from the miniport driver is bubbled up to the class driver who can log an event 153 and retry the request.
Resetting the drive is disruptive to the I/O subsystem and may not be necessary if only one request has timed out. This is because the miniport driver can abort the individual request and return an error rather than storport resetting the drive after a timeout.
STORAHCI ERROR 129 DRIVERS
The miniport driver may also be referred to as an adapter driver or HBA driver, this driver is typically written the hardware vendor.īecause the miniport driver has a better knowledge of the request execution environment, some miniport drivers time the request themselves instead of letting storport handle request timing. The difference between a 153 and a 129 is that a 129 is logged when storport times out a request, a 153 is logged when the storport miniport driver times out a request. An event 129 is logged when the storport driver times out a request to the disk I described event 129 messages in a previous article.
STORAHCI ERROR 129 WINDOWS 8
This event was new in Windows 8 and Windows Server 2012 and was added to Windows 7 and Windows Server 2008 R2 starting with hot fix KB2819485.Īn event 153 is similar to an event 129. Event ID 153 is an error associated with the storage subsystem. I then re-installed Windows Search and Office (in that order).Īfter a reboot the search service started working correctly again.In this Blog, I would like to share with you a new event that you may see in the system event log. I found this article, but it did not resolve the issue.Įventually the fix was to uninstall the windows search service and Microsoft Office. Report Id: b5c9d48f-83d6-11ea-80fa-000c290a7afdįaulting package-relative application ID:Īnalyzing the crash dumps pointed to MSPST32.DLL but none of the users had PSTs loaded. 19660, time stamp: 0x5e4586a5įaulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5e8a785bįaulting application start time: 0x01d617e35d974e4fįaulting application path: C:\windows\sysWow64\SearchProtocolHost.exeįaulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll The Event viewer showed the error below, and the crashdumps folder has a ton of files.įaulting application name: SearchProtocolHost.exe, version. I ran into an issue where the Window search service would constantly crash.
0 kommentar(er)
