• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

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

@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.
 
WD SN750 BLACK 500 gb

kingston kc3000 2tb

stock vs Solidigm NVMe Custom Modded driver
 

Attachments

  • Screenshot 2024-12-23 055539.jpg
    Screenshot 2024-12-23 055539.jpg
    519.6 KB · Views: 82
  • Screenshot 2024-12-23 060250.jpg
    Screenshot 2024-12-23 060250.jpg
    701.3 KB · Views: 68
  • Screenshot 2024-12-23 062015.jpg
    Screenshot 2024-12-23 062015.jpg
    147.5 KB · Views: 62
  • Screenshot 2024-12-23 062128.jpg
    Screenshot 2024-12-23 062128.jpg
    260.5 KB · Views: 70
  • Screenshot 2024-12-23 061840.jpg
    Screenshot 2024-12-23 061840.jpg
    289 KB · Views: 89
  • Screenshot 2024-12-23 054952.jpg
    Screenshot 2024-12-23 054952.jpg
    175.1 KB · Views: 95
  • Screenshot 2024-12-23 062638.jpg
    Screenshot 2024-12-23 062638.jpg
    172.3 KB · Views: 99
  • Screenshot 2024-12-23 054407.jpg
    Screenshot 2024-12-23 054407.jpg
    179.3 KB · Views: 99
  • Screenshot 2024-12-23 060933.jpg
    Screenshot 2024-12-23 060933.jpg
    185.3 KB · Views: 93
  • Screenshot 2024-12-23 055205.jpg
    Screenshot 2024-12-23 055205.jpg
    588.1 KB · Views: 95
@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.

1734946683627.png
 
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.
 
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.
 
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 :D
 
If we are using the old custom driver. Would it be worth using the new one?
 
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.
 
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 :D
 
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?
 
3DMARK DIRECT STORAGE BENCHMARK TEST
 

Attachments

  • Screenshot 2024-12-26 145333.jpg
    Screenshot 2024-12-26 145333.jpg
    410.2 KB · Views: 75
  • Screenshot 2024-12-26 145257.jpg
    Screenshot 2024-12-26 145257.jpg
    636.9 KB · Views: 74
  • Screenshot 2024-12-26 145030.jpg
    Screenshot 2024-12-26 145030.jpg
    406.1 KB · Views: 77
  • Screenshot 2024-12-26 141153.jpg
    Screenshot 2024-12-26 141153.jpg
    679.8 KB · Views: 81
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?




Maybe this helps :)
 
Last edited:
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?
To add to @DrDre statement and links, I will try to simplify my explanation as much as I can...

True, controllers have the ability to engage and disengage high performance or idle states by itself but in Windows (and maybe in Linux too) provides you the ability to customize it about when does it do that rather than letting the controllers doing it on there own, By default Windows controls those states and it's better that way so that Windows can manage SSD latencies and tries to keep in sync with controllers states.

For example.. whenever controllers tries to come out of idle states... as these process takes time ... it will usually cause high latencies for the operation of concurrent read/write requests happening in real-time and hence Windows will try to throttle some requests giving controllers chance rather than being choked to oblivion (or else it will be forced to reset after 60s timeout of no response) + SSDs aren't effective when they are operating near throttling temperature point so ASPT helps in that as well.

It's a whole complexities happening in the background regarding ASPT :)
 



Maybe this helps :)
To add to @DrDre statement and links, I will try to simplify my explanation as much as I can...

True, controllers have the ability to engage and disengage high performance or idle states by itself but in Windows (and maybe in Linux too) provides you the ability to customize it about when does it do that rather than letting the controllers doing it on there own, By default Windows controls those states and it's better that way so that Windows can manage SSD latencies and tries to keep in sync with controllers states.

For example.. whenever controllers tries to come out of idle states... as these process takes time ... it will usually cause high latencies for the operation of concurrent read/write requests happening in real-time and hence Windows will try to throttle some requests giving controllers chance rather than being choked to oblivion (or else it will be forced to reset after 60s timeout of no response) + SSDs aren't effective when they are operating near throttling temperature point so ASPT helps in that as well.

It's a whole complexities happening in the background regarding ASPT :)

Aah, I understand it better know. So it is somewhat of a way to reduce latency between states, like power modes in Windows 10/11.

Makes much more sense. Thank you very much for the explanation and the articles!
 
Unfortunately no before and after screenshots but I can confirm that the OLD DRIVER works with the Phison PS5021-E21 controller.

1736011752998.png


Unfortunately this laptop only goes up to Gen 3 as its an old HP 830 G5.
 
My Interrupt Policy tool reports that the NVME storage driver has a max MSI limit of 130, although it does show the assigned MSI limit at 2,048 as per the driver settings. But I'm wondering if this is an issue, trying to force more MSI messages than it can actually handle? I think while the PCI Express limit might be 2,048, the devices themselves on the end of PCIe bus can have different limits?
 
CrystalDiskMark_20250111181614.png
Screenshot 2025-01-11 182813.png


Intel DC P5800X 400GB on an overclocked 9800X3D system connected to the primary m.2 slot.

Going thru the X870E chipset/slimsas incurs 7-8% penalty in 4KQ1 for anyone curious.

This is not typical result. It was ran in Windows 11 safe mode just to see how high I can get it to go. Normally would see around 410-418MB/s in normal Windows 11 operation.

Your driver consistently scores higher in this test than the default windows driver. Just wanted to say thanks!
 
My Interrupt Policy tool reports that the NVME storage driver has a max MSI limit of 130, although it does show the assigned MSI limit at 2,048 as per the driver settings. But I'm wondering if this is an issue, trying to force more MSI messages than it can actually handle? I think while the PCI Express limit might be 2,048, the devices themselves on the end of PCIe bus can have different limits?
it's not an issue and it's completely normal. You can't force HW to use more MSI bec. it depends on the controllers design and how the OEM/Vendors decided how much they use MSI. The only control you have is reducing or limiting the MSI usage but not going over the limit. :)

Some HW like for example "Intel Wi-Fi" can go over the limit of MSI but it won't function and will fail to load the drivers :D
 
Unfortunately no before and after screenshots but I can confirm that the OLD DRIVER works with the Phison PS5021-E21 controller.

View attachment 378348

Unfortunately this laptop only goes up to Gen 3 as its an old HP 830 G5.

Following up with the "[New]-Solidigm NVMe Custom Modded-driver[Semi-Final]" drivers.

1736944788212.png


I also have your Killernetwork card drivers running on this laptop too. (Intel ax200/201)
 
Last edited:
Is it recommended to test this driver on a 990 pro running on a laptop? I saw a post that had a 990 pro but no benefits whatsoever
 
Each system is different. You won't know it, if you don't try it yourself.
 
This is what I get on my razer laptop, this is my 990 pro 2tb which is jus for games storage, benchmark is basically nearly identical to the stock drivers so no benefits although im wondering isnt the random write speeds kinda low in general compared to what i've seen here
 

Attachments

  • Screenshot (13).png
    Screenshot (13).png
    32.7 KB · Views: 56
Back
Top