Recent content by sammyblue

Today I used the drives and USB camera at the same time. Two incidents happened at about 70 and 92 minutes into using them -- both times, an error 157(disk surprise removed), followed by other disk operation errors(IO, read/write, appcrash, whatever I was doing). I have used the camera for 60...

Both of the drive bays are dual. My setup seems the same as yours, as far as formatting and such. I had been using the original drive enclosure for over a year without incident.

Galaxy has been on the machine for over a year.

It happens on various USB ports -- not limited to any one, and issues arose across different physical port arrays. Only with USB connected hard drives. The USB flash drive I had connected did not drop or corrupt, and other USB items continued to function. Removing the USB camera and previous...

Yes, I had to repair windows with the "repair using windows update" function on the evening of the 27th. Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE. Galaxy Client is a game store client that acts in many...

Negative on the motherboard, and the USB drivers are listed as the latest.

Apparently, Windows didn't feel like keeping any reliability data from before the 28th. That day was the biggest offender, so that's the shot below: View: https://imgur.com/a/PnyzO5k The DM Window shows nothing special or unexpected since my last post -- I have not reconnected the camera or...

Windows components began to fail in succession, so I rebooted. I powered off the drive bay with the recorrupting disks and also unplugged a camera I was using last weekend as well. I am going to keep the new/replacement drives in the new bay attached and in use and see how this progresses.

Interesting. I have had the issue recur on the original drives it happened on before, about one hour ago. No components are detecting corrupted in the store. I just saw a "surprise removed" message for the new drives in the new DAS(on UPS).

Regarding inline repair: I utilized the "System Restore using Windows Update". I opted for that when the CBS log showed every component corrupted. I figured there was no way to repair this without replacing that part of the system. That seems to have worked. After the final restart last...

The esd/DISM work has been attempted and failed. DISM will not use any source it is pointed to. I suspect that is because the entire update library may have been corrupted. There is no specific folder or action. Simply by being connected to the computer, all the USB hard drives drop and...

That was attempted as well. It still says the source cannot be found.

I have the install media as a USB drive using the .esd format -- I assume that will work just as well?

USB hard drives keep disconnecting at somewhat random intervals. Event viewer drops 4 to 6 ntfs errors in clusters around each.

I am using Windows 11 installation media created from the MS website. I am using the correct index when attempting the dism string. Nothing works. I expect DISM does not work.