4 / 4 shorts · 1 / 1
My Samsung 990 PRO M.2 SSD would sometimes suddenly stop reading and writing during games. Sometimes Windows still did not see that SSD after a reboot. Rebooting once more, or shutting the PC down and starting it again, would usually bring it back.
My Samsung 990 PRO M.2 SSD would sometimes suddenly stop reading and writing during games.
Sometimes Windows still did not see that SSD after a reboot. Rebooting once more, or shutting the PC down and starting it again, would usually bring it back.
Windows Event Viewer showed stornvme controller errors, disk Event ID 51, and Ntfs write failures around the M.2 SSD.
The only thing I changed was updating the SSD firmware in Samsung Magician.
It was 4B2QJXD7 before the update and 8B2QJXD7 after it.
On Samsung’s official Samsung Storage Firmware page, the note for 7B2QJXD7 says: “To address the intermittent non-recognition and blue screen issue.” The note for 8B2QJXD7 says: “To improve read-operation stability.” In other words, a firmware newer than my previous 4B2QJXD7 had already targeted a symptom very close to what I was seeing.
Reference: Samsung Storage Firmware
So far, the SSD has not disappeared or stopped reading and writing during games again.
The Steam version of SAND: Raiders of Sophie failed to launch with Unexpected error occurred. In the end, after setting Sand BE.exe to run as administrator and rebooting the PC, it started launching from Steam. The reboot seems to have been the trigger, so I still do not know whether that setting alone fixed it.
The Steam version of SAND: Raiders of Sophie failed to launch with Unexpected error occurred.
In the end, after setting Sand_BE.exe to run as administrator and rebooting the PC, it started launching from Steam. The reboot seems to have been the trigger, so I still do not know whether that setting alone fixed it.
This was the dialog I was seeing.
Before that, I tried Steam file verification, moving the install from the E drive to the C drive (the drive with the OS installed), and reinstalling BattlEye. At each point, the same error still appeared.
References: Steam Community / tinyBuild support
The last thing I changed was Sand_BE.exe in the game folder.
I enabled Properties → Compatibility → Run this program as an administrator, then rebooted the PC.
After that reboot, SAND: Raiders of Sophie started launching from Steam.
When I have time, I will move the install location back to the E drive and check whether it still launches.
In the PC version of Shadowverse WB, the QR code reader can create a deck from an image URL pasted into the file picker’s “File name” field. You can try decks found on X without saving the QR image first.
In the PC version of Shadowverse WB, the QR code reader can create a deck from an image URL pasted into the file picker’s “File name” field. You can try decks found on X without saving the QR image first.
For an image on X, right-click the image, choose “Open image in new tab,” and copy an image URL like https://pbs.twimg.com/media/xxxx?format=png.
In the file picker, paste the URL into the “File name” field instead of choosing a saved image, then click “Open.” It is just a small shortcut that skips the local download step.
If the URL includes &name=small, QR reading may fail. If it does not work, remove that part and try again.
This is an example X image URL used as the QR image.
After a PC migration, SourceTree may show fatal: detected dubious ownership in repository... for repositories copied from the old machine. I fixed the ownership mismatch by reassigning the target directory owner with takeown.
After a PC migration, SourceTree may show fatal: detected dubious ownership in repository... for repositories copied from the old machine. I fixed the ownership mismatch by reassigning the target directory owner with takeown.
This comes from Git for Windows’ ownership protection: if the repository owner does not match the current Windows user, Git blocks the repository to avoid unintended execution. Treat it as a copied-directory ownership mismatch before assuming the repository itself is broken.
Open PowerShell as administrator and reassign the owner of the target directory. Replace C:\github with the directory where you keep your repositories.
takeown /F "C:\github" /R /D YAfter running it, SourceTree could open the target repository again. On shared PCs or directories that contain other users’ files, keep the target path as narrow as possible.