Windows 10: Windows Blue Screens with "storport.sys" error permanently after raid drives are connected?

Hi there! I have had this computer with a RAID Card and 2 Raid Volumes for several years with no problems. After a failed update most recent 22 version I started getting random blue screens mentioning and couldn't get stability back. I attempted to re-install Windows but the installation kept failing out with a message that the Windows Installer needed a driver, but the "browse" feature lets me view files on the RAID volumes.NO BIOS / EUFI changes have been made No new hardware has been addedI Have attempted to install with an older version of the Windows Installation DVD same issueI have at

:)

 

Are Storport and RAID drivers necessary on my laptop

I have a 4 yrs old Vaio laptop that I updated to win 10 some months ago. (Win 10 version 1511 build 10586.36)

It runs fine, I have no complains but I am trying to lighten the burden that my poor PC has to withstand with the myriad of drivers and services that I think most of them are totally unnecessary and eat up memory and CPU cycles.

So I decided to start from the device drivers that are loaded in my PC and ask for help from the community to know if I can uninstall them safely.

This is the first of a series of post I plan to post and hope that they will also help others that are in my same circumstance.

So, regarding Storport drivers, this is what I found as definition:

storage port driver that is especially suitable for use with high-performance buses, such as fibre channel buses, and RAID adapters.

Now, can somebody explain to me why my laptop needs those drivers. (and same question for RAID drivers)

Here is a list of all the drivers that I suppose are not necessary for a humble Vaio laptop with a miserable 5400 rpm Seagate drive: Can I uninstall them?

3ware LSI 3ware SCSI Storport Driver LSI
c:\windows\system32\drivers\3ware.sys 18-May-15 5:58 PM

ADP80XX PMC-Sierra Storport Driver For SPC8x6G SAS/SATA controller
PMC-Sierra c:\windows\system32\drivers\adp80xx.sys
09-Apr-15 4:19 PM

LSI_SAS LSI Fusion-MPT SAS Driver (StorPort) LSI Corporation
c:\windows\system32\drivers\lsi_sas.sys 25-Mar-15 3:06 PM

LSI_SAS2i LSI SAS Gen2 Driver (StorPort) LSI Corporation
c:\windows\system32\drivers\lsi_sas2i.sys 08-Apr-15 4:28 PM

LSI_SAS3i Avago SAS Gen3 Driver (StorPort) Avago Technologies
c:\windows\system32\drivers\lsi_sas3i.sys 09-Apr-15 1:37 PM

LSI_SSS LSI SSS PCIe/Flash Driver (StorPort) LSI Corporation
c:\windows\system32\drivers\lsi_sss.sys 15-Mar-13 7:09 PM

megasas MEGASAS RAID Controller Driver for Windows Avago Technologies
c:\windows\system32\drivers\megasas.sys 04-Mar-15 10:06 PM

megasr LSI MegaRAID Software RAID Driver LSI Corporation, Inc.
c:\windows\system32\drivers\megasr.sys 03-Jun-13 5:32 PM

nvraid NVIDIA® nForce(TM) RAID Driver NVIDIA Corporation
c:\windows\system32\drivers\nvraid.sys 21-Apr-14 1:58 PM

percsas2i MEGASAS RAID Controller Driver for Windows
LSI Corporation c:\windows\system32\drivers\percsas2i.sys
05-Feb-15 6:21 PM

percsas3i MEGASAS RAID Controller Driver for Windows
Avago Technologies c:\windows\system32\drivers\percsas3i.sys
04-Feb-15 6:22 PM

SiSRaid2 SiS RAID Stor Miniport Driver Silicon Integrated Systems Corp.
c:\windows\system32\drivers\sisraid2.sys 24-Sep-08 1:58 PM

SiSRaid4 SiS AHCI Stor-Miniport Driver Silicon Integrated Systems
c:\windows\system32\drivers\sisraid4.sys 01-Oct-08 5:26 PM

vsmraid VIA RAID DRIVER FOR AMD-X86-64 VIA Technologies Inc.,Ltd
c:\windows\system32\drivers\vsmraid.sys 22-Apr-14 2:51 PM

VSTXRAID VIA StorX RAID Controller Driver VIA Corporation
c:\windows\system32\drivers\vstxraid.sys 21-Jan-13 2:30 PM

 

Blue Screen dxgmms2.sys PAGE_FAULT

Hi,

Dxgmms2.sys blue screen errors are related to corrupted or outdated device driver. We suggest checking this
link for troubleshooting blue screen errors as an initial step to resolve this issue.

Update us with the outcome so we can provide further assistance.

 

Blue Screen because of cm11264.sys

Hi,

This blue screen error due to cm11264.sys error could have happened due to the corrupted Windows component. To resolve your issue, we suggest that you follow the steps provided in this

article.

Let us know if there is anything else we can do to assist.