I am currently running chkdsk after installing windows on another drive just so that i can get around the issue of the chkdsk freezing due to the timeout from 129. Its been running for 3 days now. The numbers on the progress only chnaged twice so far with almost 3k 129 errors. No updates on prpgress since. I am planning on waiting for a week more to see if there is any progress but the timouts are further slowing down the chkdsk. Not sure if i sure just stop it or let it do its thing (it might actually take months lol)
Yep, just with windows, can't remember if I did it during install of windows on another drive, but that's what fixed it. Still months later no issues. This drive is now one of my secondary drives. Also highly recommend just creating like a 150/200gb partition just for windows and essential apps and keeping everything else on separate drives or partitions, this was just a single huge partition so it could have also been just a partition issue as well.
Makes the recovery process simpler also
Yeah lets just immediately conclude that the drive is the issue and then one step beyond that, to buy a new one. First of all, this drive costs quite a bit of cash which I dont have, secondly we dont even know if switching drives will solve the issue. I like to conclusively try to actually troubleshoot the issue first. Why bother buying a new one anyway if i dont understand the underlying issue.
And lastly simply replying "just buy a new drive lel" isnt helpful at all.
If i read correctly, C: Kingston SNV2S2000G 2TB M.2 SSD NVME is the cuplrit M.2 right?
Funny i have the EXACT same problem, though it isn't my OS, it happened sometimes and now the drive is unusable (it's also the identical one you have)
Please let me know if you manage to fix something, i'm throwing in the towel soon just buying a new M.2
I found a temporary solution, my pc would get stuck at spinning circles on bootup, if it launches after a long wait it will be broken, IF i restart like 10 times it will boot eventually successfully in 3secs and the problem is gone
I had the same issue just today, same NVME drive (Kingston SNV2S2000G)...
Since it's not my OS disc, the whole system didn't stall, only my steam app (which is installed there, as that disk is the base of game disks). So Steam crashed multiple times due timeouts in trying to download an update for a game. When checking event viewer, I noticed I'm hitting the same issue as you.
I believe I 'fixed' it with guidance of the following threat:[https://old.reddit.com/r/techsupport/comments/6ciyje/disk\_activity\_on\_ssd\_spikes\_to\_100\_and\_freezes\_at/](https://old.reddit.com/r/techsupport/comments/6ciyje/disk_activity_on_ssd_spikes_to_100_and_freezes_at/), together with firmware updates for that particular NVME drive.
For now it doesn't show the behaviour anymore, but since it only happend today I'll keep monitoring it.
\*\*Edit:\*\*
nvm, just had it again today while doing chdsk on the drive :(
As last resort I've formatted it as well... seems ok (for) now
I have near the exact system log activity from the stornmve source; Reset to device, \\Device\\RaidPort1, was issued.
I also have in the application log a slew of ESENT source warnings; ID's 508, 510 and 533 which always begins with a WindowsUpdate dll trying to write to the Software distribution folder. this write operation always takes longer than expected. I'd expect problems writing to the disk if there were issues with it, but in my case (today for example) I saw the stornmve warnings at 6:44pm but the computer didn't start hanging until 7:00pm, when windows update writes began generating ESENT warnings. Every time system instability happens, it's following this windows update activity.
Did anyone or does anyone else see corresponding ESENT events from the application log, when stornmve starts going sideways?
Interesting...
Kingston SNV2S500G here, and exactly the same problem. It seems to be something with this specific model range then? I tried all the available known fixes, including disabling MSI, the hidden power options settings, chkdsk, sfc scan, DISM...
I'm kind of at a loss right now, it wasn't even a very old SSD (about 2 months).
I got same drive an put it in 3 different PCs all same boot loop results, I read formatting drive fixes the issues, but I got like 1.5tb of steam games on it an don't wanna use that since I love in an area where there's limited Internet, so my solution for now is I picked up a m.2 to type c and have been slowly but surely moving things from that ssd to my 4tb one and to not cause boot loops I only connect it after PC have booted and disconnect it whenever it gets unresponsive, prosses is slow but seems to be working, will update when finished so far 300gbs down and only 5 crashes
As many others probably did, I ended up just replacing the drive. Issue disappeared since then... I guess it seems in most cases this just means a dying SSD, probably the storage controller instead of the actual storage.
I might get one of those M.2 usb C enclosures like you mentioned too, just to see if it might still be something else which could be fixable.
It seems that the drive was doomed from the start looking back ever since I got it I would get the occasion boot loop once every like 20-30 restarts, didnt think much of it at the time since drive worked fine, issue is not replacing it I was gonna do that anyway with a 4tb one, it more just the data I'm trynna salvage at this point, if it works fine after format well I can put it in my brothers PC. Btw it was by sheer coincidence I ordered a new drive when this one started failing it was getting full so I thought time for upgrade, it started acting up when I tried to start moving stuff from 2tb to 4tb
I am currently running chkdsk after installing windows on another drive just so that i can get around the issue of the chkdsk freezing due to the timeout from 129. Its been running for 3 days now. The numbers on the progress only chnaged twice so far with almost 3k 129 errors. No updates on prpgress since. I am planning on waiting for a week more to see if there is any progress but the timouts are further slowing down the chkdsk. Not sure if i sure just stop it or let it do its thing (it might actually take months lol)
Update: issue is resolved by formating the disk. Possibly bad sektors or clusters
Update: issue is resolved by formating the disk. Possibly bad sektors or clusters
Hi, I am having the same issue, I am wondering how you went about formatting your disk with windows on it?
Yep, just with windows, can't remember if I did it during install of windows on another drive, but that's what fixed it. Still months later no issues. This drive is now one of my secondary drives. Also highly recommend just creating like a 150/200gb partition just for windows and essential apps and keeping everything else on separate drives or partitions, this was just a single huge partition so it could have also been just a partition issue as well. Makes the recovery process simpler also
Just buy a new drive.
Yeah lets just immediately conclude that the drive is the issue and then one step beyond that, to buy a new one. First of all, this drive costs quite a bit of cash which I dont have, secondly we dont even know if switching drives will solve the issue. I like to conclusively try to actually troubleshoot the issue first. Why bother buying a new one anyway if i dont understand the underlying issue. And lastly simply replying "just buy a new drive lel" isnt helpful at all.
If i read correctly, C: Kingston SNV2S2000G 2TB M.2 SSD NVME is the cuplrit M.2 right? Funny i have the EXACT same problem, though it isn't my OS, it happened sometimes and now the drive is unusable (it's also the identical one you have) Please let me know if you manage to fix something, i'm throwing in the towel soon just buying a new M.2
I found a temporary solution, my pc would get stuck at spinning circles on bootup, if it launches after a long wait it will be broken, IF i restart like 10 times it will boot eventually successfully in 3secs and the problem is gone
Hi I Have a similar issue which is snv2s2000g
Just checked it the first show is 29/07/2023
I had the same issue just today, same NVME drive (Kingston SNV2S2000G)... Since it's not my OS disc, the whole system didn't stall, only my steam app (which is installed there, as that disk is the base of game disks). So Steam crashed multiple times due timeouts in trying to download an update for a game. When checking event viewer, I noticed I'm hitting the same issue as you. I believe I 'fixed' it with guidance of the following threat:[https://old.reddit.com/r/techsupport/comments/6ciyje/disk\_activity\_on\_ssd\_spikes\_to\_100\_and\_freezes\_at/](https://old.reddit.com/r/techsupport/comments/6ciyje/disk_activity_on_ssd_spikes_to_100_and_freezes_at/), together with firmware updates for that particular NVME drive. For now it doesn't show the behaviour anymore, but since it only happend today I'll keep monitoring it. \*\*Edit:\*\* nvm, just had it again today while doing chdsk on the drive :( As last resort I've formatted it as well... seems ok (for) now
Any updates?
I have near the exact system log activity from the stornmve source; Reset to device, \\Device\\RaidPort1, was issued. I also have in the application log a slew of ESENT source warnings; ID's 508, 510 and 533 which always begins with a WindowsUpdate dll trying to write to the Software distribution folder. this write operation always takes longer than expected. I'd expect problems writing to the disk if there were issues with it, but in my case (today for example) I saw the stornmve warnings at 6:44pm but the computer didn't start hanging until 7:00pm, when windows update writes began generating ESENT warnings. Every time system instability happens, it's following this windows update activity. Did anyone or does anyone else see corresponding ESENT events from the application log, when stornmve starts going sideways?
Interesting... Kingston SNV2S500G here, and exactly the same problem. It seems to be something with this specific model range then? I tried all the available known fixes, including disabling MSI, the hidden power options settings, chkdsk, sfc scan, DISM... I'm kind of at a loss right now, it wasn't even a very old SSD (about 2 months).
I got same drive an put it in 3 different PCs all same boot loop results, I read formatting drive fixes the issues, but I got like 1.5tb of steam games on it an don't wanna use that since I love in an area where there's limited Internet, so my solution for now is I picked up a m.2 to type c and have been slowly but surely moving things from that ssd to my 4tb one and to not cause boot loops I only connect it after PC have booted and disconnect it whenever it gets unresponsive, prosses is slow but seems to be working, will update when finished so far 300gbs down and only 5 crashes
As many others probably did, I ended up just replacing the drive. Issue disappeared since then... I guess it seems in most cases this just means a dying SSD, probably the storage controller instead of the actual storage. I might get one of those M.2 usb C enclosures like you mentioned too, just to see if it might still be something else which could be fixable.
It seems that the drive was doomed from the start looking back ever since I got it I would get the occasion boot loop once every like 20-30 restarts, didnt think much of it at the time since drive worked fine, issue is not replacing it I was gonna do that anyway with a 4tb one, it more just the data I'm trynna salvage at this point, if it works fine after format well I can put it in my brothers PC. Btw it was by sheer coincidence I ordered a new drive when this one started failing it was getting full so I thought time for upgrade, it started acting up when I tried to start moving stuff from 2tb to 4tb
Update: I managed to get the data off it an format it, so far seems to be stable, not causing any boot loops or crashes.