Reset to device, \Device\RaidPort0, was issued.

[Elixer]

This is annoying, today, out of the blue, was using windows, and all of the sudden, everything locked up for ~60 secs.

From experience, I knew this is because of something (HD or SSD) is going bad.
Well, looking at the event logs I see "Reset to device, \Device\RaidPort0, was issued."

I am not using RAID, so, no idea which device that is.
I shutdown, and swapped controller cables around, thinking that it would say something different if (when) the lockup will happen again.

Booted up and... eventually, it locked up again for ~60 secs, and it was the same message. "Reset to device, \Device\RaidPort0, was issued."

Grrr. so, even with the HD using a different controller channel, and the SSD as well, it says the same generic message.
Looking in registry, there is no RaidPort0 anyplace.
CrystaldiskInfo does show the drives using new channels, as well as disk management.

Looking at some of the other messages in the event log show:
wuaueng.dll (956) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 946176 (0x00000000000e7000) for 65536 (0x00010000) bytes succeeded, but took an abnormally long time (32 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Yeah, since the system was locked up for that amount of time (though, it seemed longer), that don't prove the fault is with the SSD.

SMART is fine on all devices, both short and extended tests.

I suppose the next task is to just boot with the SSD, and do benchmarks or something like that to see if I can get it to lockup again without any HD being connected.

What troubles me the most is the same \Device\RaidPort0 error messages. Why wouldn't that change, and what the heck is that supposed to be pointing to ?

 

[BonzaiDuck]

This is annoying, today, out of the blue, was using windows, and all of the sudden, everything locked up for ~60 secs.

From experience, I knew this is because of something (HD or SSD) is going bad.
Well, looking at the event logs I see "Reset to device, \Device\RaidPort0, was issued."

I am not using RAID, so, no idea which device that is.
I shutdown, and swapped controller cables around, thinking that it would say something different if (when) the lockup will happen again.

Booted up and... eventually, it locked up again for ~60 secs, and it was the same message. "Reset to device, \Device\RaidPort0, was issued."

Grrr. so, even with the HD using a different controller channel, and the SSD as well, it says the same generic message.
Looking in registry, there is no RaidPort0 anyplace.
CrystaldiskInfo does show the drives using new channels, as well as disk management.

Looking at some of the other messages in the event log show:
wuaueng.dll (956) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 946176 (0x00000000000e7000) for 65536 (0x00010000) bytes succeeded, but took an abnormally long time (32 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Yeah, since the system was locked up for that amount of time (though, it seemed longer), that don't prove the fault is with the SSD.

SMART is fine on all devices, both short and extended tests.

I suppose the next task is to just boot with the SSD, and do benchmarks or something like that to see if I can get it to lockup again without any HD being connected.

What troubles me the most is the same \Device\RaidPort0 error messages. Why wouldn't that change, and what the heck is that supposed to be pointing to ?

If I were sitting there and troubleshooting this, I would study the device-tree in Control-Panel->Device Manager. And I would scour all the nodes for any devices with a yellow-bang and "!" -- or any abnormality about the driver, "Unknown Device," or the opposite of "This devices is functioning properly."

That's like . . . step 0. . .

And also a question. Do you know, or are you sure of -- how your SATA disk devices are configured in the system BIOS? And can you confirm the current setting?

 

[Elixer]

If I were sitting there and troubleshooting this, I would study the device-tree in Control-Panel->Device Manager. And I would scour all the nodes for any devices with a yellow-bang and "!" -- or any abnormality about the driver, "Unknown Device," or the opposite of "This devices is functioning properly."

That's like . . . step 0. . .

And also a question. Do you know, or are you sure of -- how your SATA disk devices are configured in the system BIOS? And can you confirm the current setting?

Erm, none of them have any issues, they all say "This devices is functioning properly."
IIRC, the only time device manager can tell you anything is if actually failed, and then you see the "!" (or sometimes a "X")

And yeah, I know how they are configured in BIOS.
For what it is worth, when I swap the cables around, BIOS also sees that they were swapped (as well as windows, since, as I mentioned disk management shows the changes), but, still getting that "Reset to device, \Device\RaidPort0, was issued."

Looks like the Toshiba SSD is having issues.

 

[BonzaiDuck]

Erm, none of them have any issues, they all say "This devices is functioning properly."
IIRC, the only time device manager can tell you anything is if actually failed, and then you see the "!" (or sometimes a "X")

And yeah, I know how they are configured in BIOS.
For what it is worth, when I swap the cables around, BIOS also sees that they were swapped (as well as windows, since, as I mentioned disk management shows the changes), but, still getting that "Reset to device, \Device\RaidPort0, was issued."

Looks like the Toshiba SSD is having issues.

And you're saying the BIOS "SATA-mode" is "AHCI?" If it isn't, it may need to be unless you have a multi-drive RAID configuration and

Is this a laptop computer? Or a desktop? Look again at the device-tree in DM and see whether the storage controller is configured among "Ide/ATA/ATAPI controllers" or another item labeled "Storage Controllers." If the device shows up in "Storage Controllers," enter the Properties screen and select the action to "update the driver." Try it both ways -- "Windows search . . internet" and "My local computer-whatever." IF -- during one of these updates -- the item newly appears in the "IDE/ATA/ATAPI controller" tab and "Storage Controllers" disappears (unless you have yet other devices), that would indicate problem solved.

If that doesn't address the problem, then you may have hardware trouble. But I had run into this symptom before, and it can result from a mis-installed driver or driver conflict.

 

[Elixer]

And you're saying the BIOS "SATA-mode" is "AHCI?" If it isn't, it may need to be unless you have a multi-drive RAID configuration and

Is this a laptop computer? Or a desktop? Look again at the device-tree in DM and see whether the storage controller is configured among "Ide/ATA/ATAPI controllers" or another item labeled "Storage Controllers." If the device shows up in "Storage Controllers," enter the Properties screen and select the action to "update the driver." Try it both ways -- "Windows search . . internet" and "My local computer-whatever." IF -- during one of these updates -- the item newly appears in the "IDE/ATA/ATAPI controller" tab and "Storage Controllers" disappears (unless you have yet other devices), that would indicate problem solved.

If that doesn't address the problem, then you may have hardware trouble. But I had run into this symptom before, and it can result from a mis-installed driver or driver conflict.

The system has been fine for a very long time. And, of course it is a hardware problem. I was just trying to figure out why windows is saying Device\RaidPort0 when there is no Device\RaidPort0 that I can locate anyplace.