Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, December 4, 2017 5:52 AM
What is the significance of event id: 129 Reset to device, \Device\RaidPort0, was issued.
What determines whether it is a one time or recurrent event?
How do you troubleshoot it?
What is the typical method that fixes it?
If there is no active hardware RAID what is the significance of the event?
If there is not active software RAID what is the significance of the event?
If there was active RAID how does that impact the event?
How does the event happen when there is no use of RAID?
All replies (3)
Tuesday, December 5, 2017 7:16 AM
Hi,
Thank you for your post.
Based on my search and understand, I think this event ID is a known issue.
It always related to the driver (such as intel rapid storage technology, motherboard, video card driver) and power management (PCI Express).
Event ID 129 – storachi – Reset to device, DeviceRaidPort0, was issued.
More information about this Event ID description.
https://www.eventid.net/display.asp?eventno=9180&eventid=129&phase=1
Also it could be caused by a failed HDD.
Hope it will be helpful to you
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, December 5, 2017 10:01 AM
When these events are seen in the event viewer where should troubleshooting begin?
Which tests?
Drive tests?
driver verifier?
graphic card stress tests?
etc.
Which order or priority?
Wednesday, December 6, 2017 1:46 AM
Hi,
As I understand it, if we could find it in event log. We can first search the corresponding information for the event ID. So we have a general troubleshooting direction about software or hardware. Because the event ID and description already indicate the relevant issues. What we need to test is the option to try these fixes.
According to the blog, power management you could first check. Because it's easy to manipulate.
Then drivers mentioned above, such as motherboards, preferred to try to install. This reduces many operations, such as using Driver Verifier.
If the issue still insists, I consider that use Driver Verifier is ok.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].