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

[THEBOSS619]

Could it be this too:

Forwarding I/O Requests - Windows drivers

Forwarding I/O Requests

learn.microsoft.com

Oh nice find! Yes, I think this is the one I have edited the post Thank you!

 

[DrDre]

New driver is better on my laptop:

The RDN4K write speeds are back


And on the SN850X it's also a tad better:

 

[TheLostSwede]

Latest driver seems very broken. Worst write speeds I've seen from this drive.

Can't seem to get the drive back to normal either.

 

[THEBOSS619]

New driver is better on my laptop:

View attachment 373818

The RDN4K write speeds are back


And on the SN850X it's also a tad better:

View attachment 373825

Oh that's so amazing to hear! I never intended it to be fixing stuff but it's always music to my ears to see that it fixes stuff and in top of it... improves performance! Thank you so much for reporting and sharing your results

Latest driver seems very broken. Worst write speeds I've seen from this drive.

View attachment 373918

Can't seem to get the drive back to normal either.

View attachment 373919

Oh damn, didn't expect that to happen... especially from a Solidigm NVMe brand.

Simply uninstall the driver by following the uninstall instructions that is available on the main post after that install the driver that works best for you

Not every driver can work perfectly for all brands. There's always some NVMe drive that simply doesn't like Solidigm driver either the old ones vs the new ones. Both have greatly different driver in characteristic & how it behaves & how it works

 

[DrDre]

I guess that is why forwarding i/o is disabled,
the soldigm drives can't handle it and others need it.

 

[aliceS]

Made in a WD Blue SN570 1TB in Windows 11 24H2.
These were all made in various time periods.

Win Driver

Solidigm Driver v2 (v1 was pretty much the same)

First v3 Beta

New beta v3 with Foward I/O support

For the note:
The SSD is not running on RAID;
It is the only SSD on the system;
Second ever drive on the system (the other one is a Samsung HDD that's quite old);
Running from M.2 chipset slot PCIe 4.0, not CPU slot (closest to the CPU).

Overall, all the drivers made things better here. I know this is not a really big test, but I played some L4D2 in this SSD before and after the Modded Solidigm Driver and I got 3 loading screens instead of 4 loading screens.

I've been getting some BSOD, but I think I nailed what was causing it: Dashboard software. I didn't thought of it as a problem because for sometime it never crashed. Upon a new Windows 11 install, I saw that the system was perfectly stable, however some days ago I installed Dashboard to see if there was some firmware or whatever. After this install, I got a BSOD. Just like THEBOSS619 said in the main post, it might have been Dashboard making this problem.

Aside from this only occasion which I rule as a user error, no other problems! System is as stable as a rock! In a few days I'll be receving a new SSD, a WD Black 850X 2TB and I'll test it when I have some time. Of course, posting it in here after that.

Thank you very much for the driver, Mr. THEBOSS619.
Your hard work is appreciated!

 

[TheLostSwede]

Removed every trace of the Solidgm driver, but alas...
Seems like a re-install of Windows is due...

 

[DrDre]

Try the original Solidigm driver. Maybe that helps:

Solidigm Synergy™ Software And Driver For Client Solid State Drives

All-In-One Performance Booster And Drive Manager

www.solidigm.com

 

[THEBOSS619]

I guess that is why forwarding i/o is disabled,
the soldigm drives can't handle it and others need it.

yea, maybe I think so I still need to read more about it

Made in a WD Blue SN570 1TB in Windows 11 24H2.
These were all made in various time periods.

Win Driver
View attachment 374057

Solidigm Driver v2 (v1 was pretty much the same)
View attachment 374058

First v3 Beta
View attachment 374059

New beta v3 with Foward I/O support
View attachment 374060

For the note:
The SSD is not running on RAID;
It is the only SSD on the system;
Second ever drive on the system (the other one is a Samsung HDD that's quite old);
Running from M.2 chipset slot PCIe 4.0, not CPU slot (closest to the CPU).

Overall, all the drivers made things better here. I know this is not a really big test, but I played some L4D2 in this SSD before and after the Modded Solidigm Driver and I got 3 loading screens instead of 4 loading screens.

I've been getting some BSOD, but I think I nailed what was causing it: Dashboard software. I didn't thought of it as a problem because for sometime it never crashed. Upon a new Windows 11 install, I saw that the system was perfectly stable, however some days ago I installed Dashboard to see if there was some firmware or whatever. After this install, I got a BSOD. Just like THEBOSS619 said in the main post, it might have been Dashboard making this problem.

Aside from this only occasion which I rule as a user error, no other problems! System is as stable as a rock! In a few days I'll be receving a new SSD, a WD Black 850X 2TB and I'll test it when I have some time. Of course, posting it in here after that.

Thank you very much for the driver, Mr. THEBOSS619.
Your hard work is appreciated!

Thank you so much for your reports & sharing your results & for your kind words it's such a wonderful thing to see that a driver can make such a difference for vast majority of NVMe brand! I always thought that using the default MS-Stock in-box driver that comes with Windows was more than enough but I guess it's no longer the case any more

Removed every trace of the Solidgm driver, but alas...
Seems like a re-install of Windows is due...

View attachment 374075

I'm really sorry for causing inconveniences to you, please forgive me if I caused any kind of troubles

Look, before nuking windows, Try Windows Repair function. It's under Settings>System>Recovery I use Windows Dev 24H2 Insider and this option always saved me many times from completely nuking windows (due to the nature using Windows Insider releases ) I have never nuked Windows since the very first days of using Win11 22H2 Beta insiders

Here's a picture of this function, it keeps everything as it is without removing a single file

 

[TheLostSwede]

Try the original Solidigm driver. Maybe that helps:

Solidigm Synergy™ Software And Driver For Client Solid State Drives

All-In-One Performance Booster And Drive Manager

www.solidigm.com

Not a huge difference and it doesn't solve the slow write performance.

I'm really sorry for causing inconveniences to you, please forgive me if I caused any kind of troubles

Look, before nuking windows, Try Windows Repair function. It's under Settings>System>Recovery I use Windows Dev 24H2 Insider and this option always saved me many times from completely nuking windows (due to the nature using Windows Insider releases ) I have never nuked Windows since the very first days of using Win11 22H2 Beta insiders

Here's a picture of this function, it keeps everything as it is without removing a single file
View attachment 374076

Not blaming you, I was the one installing the driver, no-one forced me.

I'm on Windows 10 still, so that doesn't appear to be an option I have.

 

[DrDre]

Try to trim the drive.

 

[THEBOSS619]

Not blaming you, I was the one installing the driver, no-one forced me.

I'm on Windows 10 still, so that doesn't appear to be an option I have.

Oh thank you for understanding

For Win10, you can try in-place upgrade through Media Creation Tool or through any official iso by running setup.exe. Those two options provide similar functionality of repairing windows without losing files/settings.

 

[kalima]

Hello @THEBOSS619 ,

Quick test on my desktop with 990Pro 2TO.

3dMark storage

• MS Nvme driver : 4107
• Soldigm 2.2.0.1017 modded + Samsung perf : 4312
• Soldigm 2.3.0.1023 : 4319

Also installed this latest version on my laptop , no issue so far. Great job !

 

[kalima]

First test with new 3DMark directStorage test

Soldigm 2.3.0.1023 modded and 990Pro

 

[aliceS]

It seems that the driver wasn't that stable in my machine after all.

After that post, I got another BSOD and thought it maybe was my PBO setting being unstable, so I changed and stayed fine without any crashes. Today I got another BSOD, now while testing my SN850X.

I don't know if this is fixable or just my machine being incompatibile with the driver, because other SN570 1TB and other SN850X 2TB user were just fine, at least from what I see from the posts.
I wanted to do some tests seeing the differences in games and also if Solidigm would work with Gaming Mode 2.0 (and if it would have any difference).

I'll attach some of the errors I got, I hope they are useful in any way.

Two of them is different from the other. It still got the same error reports on Event Viewer, but the cause (bug check) is different.
0x000000C2 - BAD_POOL_CALLER
0x0000000a - IRQL_NOT_LESS_OR_EQUAL
0x000000b8 - ATTEMPTED_SWITCH_FROM_DPC

These were the three BSOD IDs I've got. Hopefully this helps.

 

[DrDre]

@THEBOSS619
Do you know if bypass i/o is enabled in your driver?

BypassIO in Storage Drivers - Windows drivers

Describes the BypassIO path for storage drivers

learn.microsoft.com

 

[THEBOSS619]

@THEBOSS619
Do you know if bypass i/o is enabled in your driver?

BypassIO in Storage Drivers - Windows drivers

Describes the BypassIO path for storage drivers

learn.microsoft.com

Yes, it's fully supported & enabled I have even added support for Forwarded IO too

It seems that the driver wasn't that stable in my machine after all.

After that post, I got another BSOD and thought it maybe was my PBO setting being unstable, so I changed and stayed fine without any crashes. Today I got another BSOD, now while testing my SN850X.

I don't know if this is fixable or just my machine being incompatibile with the driver, because other SN570 1TB and other SN850X 2TB user were just fine, at least from what I see from the posts.
I wanted to do some tests seeing the differences in games and also if Solidigm would work with Gaming Mode 2.0 (and if it would have any difference).

I'll attach some of the errors I got, I hope they are useful in any way.

Two of them is different from the other. It still got the same error reports on Event Viewer, but the cause (bug check) is different.
0x000000C2 - BAD_POOL_CALLER
0x0000000a - IRQL_NOT_LESS_OR_EQUAL
0x000000b8 - ATTEMPTED_SWITCH_FROM_DPC

These were the three BSOD IDs I've got. Hopefully this helps.

I will be looking into the files & get back to you sorry if I caused any hassle to you. forgive me for that.

Thank you for your time and sharing your results & reports

Sorry for late replies, holidays events & other stuff takes all my free time to be available online.

 

[DrDre]

PS C:\WINDOWS\system32> fsutil bypassIo state /v C:\
BypassIo auf „C:\“ wird derzeit unterstützt
Speichertyp: NVMe
Speichertreiber: BypassIo-kompatibel
Treibername: solidnvm.sys
PS C:\WINDOWS\system32> fsutil bypassIo state /v d:\
BypassIo auf „d:\“ wird derzeit unterstützt
Speichertyp: NVMe
Speichertreiber: BypassIo-kompatibel
Treibername: solidnvm.sys

Jepp you are right. Just tried it and it works fine.
I was just wondering, because my score is lower with DirectStorage enabled.
Could be my old graphics card.

It seems that the driver wasn't that stable in my machine after all.

After that post, I got another BSOD and thought it maybe was my PBO setting being unstable, so I changed and stayed fine without any crashes. Today I got another BSOD, now while testing my SN850X.

I don't know if this is fixable or just my machine being incompatibile with the driver, because other SN570 1TB and other SN850X 2TB user were just fine, at least from what I see from the posts.
I wanted to do some tests seeing the differences in games and also if Solidigm would work with Gaming Mode 2.0 (and if it would have any difference).

It works fine with my SN850X 2TB and my SN570 1TB.
No BSOD's whatever. System is stable even with dram OC (3800 CL14).
Never tested the Gaming Mode 2.0 though.

Sorry for late replies, holidays events & other stuff takes all my free time to be available online.

Private stuff and family's first! No problem

 

[aliceS]

Ooooh... I think I know why it was crashing.

This year I was trying some mem OC out and it was pretty unstable. I found out two days ago I have left some timings on their OC values instead of Auto.
Happens that after making Twrrd on Auto has made my machine stable. Tested Extreme@anta777 config for 1.5h and it didn't gave any error.

It seems I was wrong on my judgement. I'm very sorry for troubling you. Like Mr. DrDre said it is stable. Thank you for comenting about DRAM OC, that reminded me and I was able to found and fix my mistake.

So, now that that's fixed, here's the results of my SN850X 2TB.

Win Driver

Solidigm V3 Beta driver

Like you see, it got a little worse and so I went on to see if I could leave one with the Win driver and other with Solidigm driver.
And yes! I've found a way! I hope this helps anyone with the same need.

You want to go into Device Manager > Disk Drivers > right click on both drives you have installed that use the NVMe driver.

It will be looking like this.

Then, to what we're gonna do, we'll need how Windows recognizes the drive. Go in Events and scroll the entire "Information" to the bottom.

You see that "\VEN_15B7&DEV_5030&SUBSYS_503015B7&REV_01\4&db6900a&0&0009" and "\VEN_15B7&DEV_501A&SUBSYS_501A15B7&REV_00\6&219769e0&0&0020020A"? That's what we gonna need. Yours gonna be different, but the result will be the same.

Go into Device Manager again, now in "Storage controllers". You'll see there's three (or more) controllers. One of them is Microsoft Storage Spaces Controllers, which is not needed and then you'll have the other controllers, which is what we're gonna use.

Go on and open both controllers Proprieties and go to Events again.

You can already see that both have different "Device PCI". Now you just need to see which drive is better with Solidigm and which is better with Microsoft's driver. Check the name it shows under "Device PCI" with the one you see on your drives. That way you'll know which is which.

After knowing which controller is configured to what drive, you will need to: right click the controller you want to swap > Update Driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer > select the desired controller > Restart your PC

After that, you should be using different controllers to different drives.
I'm not sure if this causes any sort of problems for now. Up until now, it has been stable, no problems on using different controllers.
I hope some one founds this useful.


I'll do some tests later because I will be a little occupied this next week. I hope on the next weekend I'll be able to record and show some results with these drivers, at least on games.
Again, I'm very sorry for troubling you with problems that were my mistake! I should've tested things more throughly before reporting it...

 

[aliceS]

I've done the tests. I didn't do many for each, just 1 sample.

It was quite troublesome because you need to restart a lot of times to do these, so it's only natural people would get discouraged.

Anyway, there wasn't as much difference as you would think. All of them were in the miliseconds range.

The tests were done in this way:
-Used a game I've booted before and have played at least a little to cache shaders to NVIDIA shader cache;
-All done in SN850X;
-Gaming Mode tests were done on Auto, with the SteamLibary folder listed as a Gaming Mode folder;
-Changed between drivers using Device Manager;
-Solidigm Driver used was the newest one with Foward I/O support.

Software I've used is:
-LiveSplit = stopwatch;
-HWInfo = some bonus data;
-OBS = recording;
-Resident Evil 4 2023 (Remake) = game used for the test.

I used RE4R because it is a game that don't take a really long time, it's easy to capture and is recent enough to use a NVMe drive to it's max.

As soon as I click, I also pressed the LiveSplit hotkey. Stopwatch ends when the loading bar is 100% full.

Without futher ado, here's the videos:

SN850X MS Driver Gaming Mode OFF

SN850X Solidigm Driver Gaming Mode OFF

SN850X MS Driver Gaming Mode ON

SN850X Solidigm Driver Gaming Mode ON

As you can see, the best peformant ones were MS Driver Gaming Mode ON and Solidigm Driver Gaming Mode OFF. It makes sense why MS Driver Gaming Mode ON would be one of the most peformant. As Western Digital put, Gaming Mode 2.0 uses "Predictive Loading" which, I guess, function like Solidigm's Smart Prefatch, were it finds predictable read streams and keeps a high and stable sequential read. I don't know if their "Adaptive Thermal Management" is also at play, because that naming is very confusing and they don't explain both Predictive Loading and Adaptive Thermal Management in any web page.

Solidigm Driver Gaming Mode ON is the 2° worst peformant one (still very quick!). I assume this is because Predictive Loading and Smart Prefatch are fighting each other to speed sequential reads which makes that take more time and don't do much benefit to the loading times. It just wins by 5 miliseconds versus MS Driver Gaming Mode OFF, which is pretty much a margin of error.

I hope this is helpful to show that the driver does make a difference. Even though my SN850X don't like the Solidigm driver that much, it still makes a difference. If in CrystalDiskInfo you see some difference (especially in sequencial reads), be sure that your game will load, at least, 1s quicker than before. I guess this driver helps more HMB based drives, as those don't have DRAM or some quirky features like Gaming Mode - and Solidigm made these drivers for HMB drives in the first place.

Again, thank you very much, Mr. THEBOSS619 for your hardwork!
Doing all of this for no money at all, in your free time, which is not much since you have a family is very nice of you. On top of all that, even supporting it and coming regularly to this forum to thank, help and improve the custom driver is very heartwarming. The world needs more gentle and nice people like you!

If anyone feels like going out of their way to also test it like this, don't need to be in games, using 3DMark daily use is a very good test already, please, share it with us.

 

[THEBOSS619]

Ooooh... I think I know why it was crashing.

This year I was trying some mem OC out and it was pretty unstable. I found out two days ago I have left some timings on their OC values instead of Auto.
Happens that after making Twrrd on Auto has made my machine stable. Tested Extreme@anta777 config for 1.5h and it didn't gave any error.

It seems I was wrong on my judgement. I'm very sorry for troubling you. Like Mr. DrDre said it is stable. Thank you for comenting about DRAM OC, that reminded me and I was able to found and fix my mistake.

So, now that that's fixed, here's the results of my SN850X 2TB.

Win Driver
View attachment 374905

Solidigm V3 Beta driver
View attachment 374906


Like you see, it got a little worse and so I went on to see if I could leave one with the Win driver and other with Solidigm driver.
And yes! I've found a way! I hope this helps anyone with the same need.

You want to go into Device Manager > Disk Drivers > right click on both drives you have installed that use the NVMe driver.
View attachment 374907
It will be looking like this.

Then, to what we're gonna do, we'll need how Windows recognizes the drive. Go in Events and scroll the entire "Information" to the bottom.
View attachment 374908

You see that "\VEN_15B7&DEV_5030&SUBSYS_503015B7&REV_01\4&db6900a&0&0009" and "\VEN_15B7&DEV_501A&SUBSYS_501A15B7&REV_00\6&219769e0&0&0020020A"? That's what we gonna need. Yours gonna be different, but the result will be the same.

Go into Device Manager again, now in "Storage controllers". You'll see there's three (or more) controllers. One of them is Microsoft Storage Spaces Controllers, which is not needed and then you'll have the other controllers, which is what we're gonna use.
View attachment 374909

Go on and open both controllers Proprieties and go to Events again.
View attachment 374910
You can already see that both have different "Device PCI". Now you just need to see which drive is better with Solidigm and which is better with Microsoft's driver. Check the name it shows under "Device PCI" with the one you see on your drives. That way you'll know which is which.

After knowing which controller is configured to what drive, you will need to: right click the controller you want to swap > Update Driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer > select the desired controller > Restart your PC

After that, you should be using different controllers to different drives.
I'm not sure if this causes any sort of problems for now. Up until now, it has been stable, no problems on using different controllers.
I hope some one founds this useful.


I'll do some tests later because I will be a little occupied this next week. I hope on the next weekend I'll be able to record and show some results with these drivers, at least on games.
Again, I'm very sorry for troubling you with problems that were my mistake! I should've tested things more throughly before reporting it...

I've done the tests. I didn't do many for each, just 1 sample.

It was quite troublesome because you need to restart a lot of times to do these, so it's only natural people would get discouraged.

Anyway, there wasn't as much difference as you would think. All of them were in the miliseconds range.

The tests were done in this way:
-Used a game I've booted before and have played at least a little to cache shaders to NVIDIA shader cache;
-All done in SN850X;
-Gaming Mode tests were done on Auto, with the SteamLibary folder listed as a Gaming Mode folder;
-Changed between drivers using Device Manager;
-Solidigm Driver used was the newest one with Foward I/O support.

Software I've used is:
-LiveSplit = stopwatch;
-HWInfo = some bonus data;
-OBS = recording;
-Resident Evil 4 2023 (Remake) = game used for the test.

I used RE4R because it is a game that don't take a really long time, it's easy to capture and is recent enough to use a NVMe drive to it's max.

As soon as I click, I also pressed the LiveSplit hotkey. Stopwatch ends when the loading bar is 100% full.

Without futher ado, here's the videos:

SN850X MS Driver Gaming Mode OFF

SN850X Solidigm Driver Gaming Mode OFF

SN850X MS Driver Gaming Mode ON

SN850X Solidigm Driver Gaming Mode ON

As you can see, the best peformant ones were MS Driver Gaming Mode ON and Solidigm Driver Gaming Mode OFF. It makes sense why MS Driver Gaming Mode ON would be one of the most peformant. As Western Digital put, Gaming Mode 2.0 uses "Predictive Loading" which, I guess, function like Solidigm's Smart Prefatch, were it finds predictable read streams and keeps a high and stable sequential read. I don't know if their "Adaptive Thermal Management" is also at play, because that naming is very confusing and they don't explain both Predictive Loading and Adaptive Thermal Management in any web page.

Solidigm Driver Gaming Mode ON is the 2° worst peformant one (still very quick!). I assume this is because Predictive Loading and Smart Prefatch are fighting each other to speed sequential reads which makes that take more time and don't do much benefit to the loading times. It just wins by 5 miliseconds versus MS Driver Gaming Mode OFF, which is pretty much a margin of error.

I hope this is helpful to show that the driver does make a difference. Even though my SN850X don't like the Solidigm driver that much, it still makes a difference. If in CrystalDiskInfo you see some difference (especially in sequencial reads), be sure that your game will load, at least, 1s quicker than before. I guess this driver helps more HMB based drives, as those don't have DRAM or some quirky features like Gaming Mode - and Solidigm made these drivers for HMB drives in the first place.

Again, thank you very much, Mr. THEBOSS619 for your hardwork!
Doing all of this for no money at all, in your free time, which is not much since you have a family is very nice of you. On top of all that, even supporting it and coming regularly to this forum to thank, help and improve the custom driver is very heartwarming. The world needs more gentle and nice people like you!

If anyone feels like going out of their way to also test it like this, don't need to be in games, using 3DMark daily use is a very good test already, please, share it with us.

You did an amazing detailed tests I have ever seen for a modded driver, I'm impressed and grateful for your amazing commitment on providing reports and sharing results Thank you so much for that! I can't thank you enough for your amazing work

Your kind words and heartwarming support just keeps me pushing forward, thank you again from all my heart you don't know how grateful and appreciative I am

 

[THEBOSS619]

[Semi-Final] New Solidigm Custom Modded Driver.

We can call this a stable release as I have tested it for almost over 1 month on all kind of workloads & testings.

With beta tests being released through out the last 3 months with no major reports of such problems arise and not a single hitch about it but since I'm releasing it to the public... I gotta play it safe hence the [Semi-Final] tag name

With the help from @AAF Optimus [Huge thanks for his tremendous help!] We have finally finalized and optimized INF driver. Give thanks to this legendary person for his guidance and optimizing the driver code.

So you can imagine how much this Solidigm driver went through optimizations over & over

Previous version (the old ones 2.2.0.1017) most feature was enabled by default but on the newer ones (latest Soldigim version 2.3.0.1023) they applied some kind of checking mechanism to see if you have Solidigm NVME SSD drive installed & after that they disable/enable features according to it. I simply found the keys inside .sys files & enabled it all after digging through deeply inside the .sys file

If you want to know the features and benefits of using Solidigm Custom Modded Driver + Install/Uninstall instructions it's all there on the main post.

Changelog:-

• - Using the latest Soldigim version 2.3.0.1023
• - Added a flag that forces Secondary Bus Reset event if it has sibling functions.
• - Added a flag if a device generates errors that should be ignored during PLDR [Platform-level Device Reset (PLDR)]
• - Added support for Forwarded IO
• - Added keys to enable Fast Lane feature
• - Added keys to enable Dynamic Queues feature
• - Tweaked & Tuned InterruptCoalescing and IRQ routings
• - Added keys to enable NvmeApst and use it
• - Added keys to enable Nvme IO Queues and use it
• - Allow interrupts on processors beyond group 0
• - Make sure that the device's interrupts are of high priority.
• - Make sure all processor in group are used to serve interrupt
• - Add BypassIO_ACPI support

---F.A.Q---
- What is Forwarded IO?
Well, there isn't a well documented definition for it and what are the benefits for it but Windows in-box MS Stock SSD NVMe Driver already supports it by default, It's good to see the Solidigm driver already got support for it as well but they simply didn't want to use it and hence... I have enabled it & added the required flags for it.

I have found a links regarding "Forwarded IO" but I don't know if they are even talking about it or something else but I will share the link anyway here

• - https://www.glennklockwood.com/data-intensive/storage/io-forwarding.html
• - https://learn.microsoft.com/en-us/windows-hardware/drivers/wdf/forwarding-i-o-requests

- What is PLDR?
"Platform-level Device Reset (PLDR)
Platform-level Device Reset is for cases where FLDR cannot be used, or as a last-resort supplement to FLDR. This reset mechanism causes the device to be reported as missing from the bus (during a power cycle, for example) or affects multiple devices (such as a shared power rail or reset line among devices). The reset method is specified in the ACPI table, which might be implemented as toggling a dedicated reset line or power-cycling the D3 power resource. When PLDR is performed, the OS tears down and rebuilds the stacks of all affected devices to ensure everything starts from a pristine state."

- What is NVME ASPT?
APST is a feature that allows the NVMe controller (within the NVMe SSD) to switch between power management states autonomously. It can decide when to enter a different active power state, and support runtime D3 (RD3) for zero power idle state and fast resume.



- Where do I download it?
The new Solidigm driver is posted on the main post attachment.. go download it there! It has a tag name [New] on the file to avoid confusion

Notice:- For those people who used the old driver... no need to uninstall the old driver since the installer script will update to the newer driver automatically + you no longer need the .reg files because it's all baked inside the driver ... so you just only need to install it through setup.bat file

Edit:-

• I'm gonna take the rest of the year 2024 a break from any kind of developmental approach for the time being but I will be around from time to time providing support & help in case of any troubles arises