Solved Storport.sys memory leak. Any ideas on how to fix it?

Been trying to hunt down a memory leak for about a week now and I've finally narrowed it down to the storport.sys driver. Trouble is, this is a Microsoft driver for HDD storage ports. How do I go about redownloading this driver for replacement? I can't seem to find anything related on the Microsoft support page.

To back up my diagnosis, here's the long story of my troubleshooting:

---

Noticed computer would begin to lag severely after 3+ hours of if being turned on. Lag would progress till it froze, requiring hard reset. Activated MSI Afterburners RAM monitor to watch ram useage live while running other programs/games (Nothing is overclocked, using Afterburner solely for monitoring as it supports the LCD display on my Logitech G510). When RAM got to 10gb full, I'd kill all running/active programs to see if any of them were the culprit. Ram still wouldn't decrease in usage and Task Manager/Performance Monitor numbers didn't even add up to more that 1.5gb of ram in use.

Opened up poolmon to see what drivers are active and using the most ram which then pointed me to storport.sys using 8gb of unpaged memory.

---

So, once again, I need help in repairing/replacing the storport.sys driver. Any help on the matter would be very helpful.

sigh...

I ended up installing Windows 8 on a vm, pulling the storport.sys driver from the vm install and replacing the faulty one on my actual pc. This seems to have resolved the issue, although it was a real pain in the butt to do.

Windows 8 repair is only for Start-up functions only, so that didn't fix it. And using "windows refresh" was out of the equation as, even though it says it saves your personal data, it will wipe everything but your users folder. So it will wipe every program you own on it. If you only have 3-4 programs on your machine, that's no big deal, but when you have huge amounts of applications you have to reinstall, track down serial numbers for, and redownload up to 100GB of those programs, it's out of the question.

So thats why I did what I did. Hope no one has this issue in the future, as it's a pain to fix.