Solidigm NVMe Custom Modded Driver for All NVMe Brands SSDs & Any NVMe SSDs

[IMABEARLOL]

@TheLostSwede FYI, likely you are experiencing the firmware bug that SKHynix/Solidigm refuses to address.

I encountered this issue on multiple drives from them.

I believe the issue comes down to the firmware bugging out and failing to do proper block tracking and garbage collection and so trim is actually never happening. People believe it's controller defect which is why no firmware has been released.

If you initialize the disk again performance will return until it runs out of "fresh" flash blocks again. Obviously, benchmarking speeds up this process.

 

[davidaz]

WD SN750 BLACK 500 gb

kingston kc3000 2tb

stock vs Solidigm NVMe Custom Modded driver

 

[TheLostSwede]

@TheLostSwede FYI, likely you are experiencing the firmware bug that SKHynix/Solidigm refuses to address.

I encountered this issue on multiple drives from them.

I believe the issue comes down to the firmware bugging out and failing to do proper block tracking and garbage collection and so trim is actually never happening. People believe it's controller defect which is why no firmware has been released.

If you initialize the disk again performance will return until it runs out of "fresh" flash blocks again. Obviously, benchmarking speeds up this process.

Sadly, running a manual TRIM made no difference.

 

[IMABEARLOL]

Sadly, running a manual TRIM made no difference.

View attachment 376845

This is destructive to all the data, but 'clean' the disk using DISKPART. Then use windows partition manager to initialize and create a new partition and trim it. You should see performance return. But again, this is only until the drive runs out of fresh blocks and the bug returns.

 

[TheLostSwede]

This is destructive to all the data, but 'clean' the disk using DISKPART. Then use windows partition manager to initialize and create a new partition and trim it. You should see performance return. But again, this is only until the drive runs out of fresh blocks and the bug returns.

That's my OS drive, so I won't be doing that.

 

[THEBOSS619]

That's my OS drive, so I won't be doing that.

when you return to MS-Stock In-Box drivers, you regain all the performance back right?

 

[TheLostSwede]

when you return to MS-Stock In-Box drivers, you regain all the performance back right?

We discussed this, the answer is still no, as you can see above.
You suggested a system restore, but I will re-install the OS at some point, but not right now.

 

[THEBOSS619]

We discussed this, the answer is still no, as you can see above.
You suggested a system restore, but I will re-install the OS at some point, but not right now.

Oh indeed indeed, I totally forgot that we discussed this previously. Forgive me for that, Sometimes my brain gets blank from time to time

 

[FreedomEclipse]

If we are using the old custom driver. Would it be worth using the new one?

 

[DrDre]

I think you have to try it, it's not complicated and it takes minutes.
Both are running good, but the latest has more features.

 

[THEBOSS619]

If we are using the old custom driver. Would it be worth using the new one?

as @DrDre mentioned , test is the only way to see if it's worth it or not also once I get back from the break... I have so many ideas of optimization for Solidigm drivers it just takes time due to stability testing & my very limited spare time

 

[aliceS]

I've been scratching my head lately with this ASPT thing. What does it exactly do? Shouldn't controllers already engage and desingage high peformance or idle states by itselves? Does it makes the states switch between quickly by removing something from those calls? Or, perhaps, controllers don't really sleep like CPUs do?