nvstor32 and nvstor help  

under non plug and play in device manager there is nvstor and in nvidia serial ata controller driver details there is s nvstor32 both what is the differ between the two

Those two files are part of your Nvidia driver

Info on nvstor.sys:
http://www.runscanner.net/file/nvstor.sys.html

Info on nvstor32.sys:
http://www.runscanner.net/file/nvstor32.sys.html

I also found this in the Nvidia forums:
http://forums.nvidia.com/index.php?showtopic=71048

Quoting from the relevant post from the Nvidia forum link above - highlighted the relevant part in bold:

NVIDIA had changed the names for their S-ATA and RAID drivers. NVSTOR.SYS is the name of Vista's in-box nForce S-ATA driver (32/64bit), the actual 32bit Vista S-ATA drivers are named NVSTOR32.SYS, whereas the 32bit nForce RAID driver name now is NVRD32.SYS (formerly NVRAID.SYS).

In other words, nvstor32.sys indicates your bit system. If you had a 64-bit system, it would be nvstor64.sys.

FYI.
Both file names & descriptions are below.


nvstor32 > nvstor32.sys > Related to nvstor32.sys NVIDIA® nForce(TM) Sata Performance Driver.


nvstor > nvstor.sys > Related to nvstor.sys nForce(TM) Sata Performance Driver from NVIDIA Corporation .

They are legitimate.

i get an error from nvstor32 as i understand it has something to do with raid put i do not use raid so can i disable it

More details are needed re the error you receive.

*Have you checked in Event Viewer?
Type eventvwr in search.
Go to the windows log>application tab.
Look for critical errors (they have red in the left column)that say anything that relates to this particular "problem."
Please note the event ID, and the source codes.

SOLVED!!!!!


I know this thread is wicked old but this issue has plagued me for a very long time and I have finally fixed it across all platforms and for all Hardware!!!


I am posting this fix because there is absolutely no legitimate fix on the entire web that is a true fix and to help anyone else having this annoying issue; especially gamers and NVIDIA MOBO and Graphic Card owners, so here it is (FINALLY!!!):


EventID - 129
Source nvstor, nvstor32, nvstor64
Reset to device, \Device\RaidPort2, was issued (this is one of many messages you may receive)


If for any reason the Registry entries below for the fix don't match your system, search the registry for nvstor and the "like" keys on your own system


The fix is in 3 places on my system so navigate to each one, one at a time



HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2\3&2411e6fe&1&70


You will see a Sub Key named "Properties" which should throw an inaccessible permissions error, take Ownership of it and give your account FULL ACCESS only for that key but uncheck subcontainers and objects


Do the same for the following 2 locations (you may want to search to see if you have additional, similar keys but I only had 3 total):


HKLM\SYSTEM\CurrentControlSet003\Enum\PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2\3&2411e6fe&1&70


HKLM\SYSTEM\CurrentControlSet004\Enum\PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2\3&2411e6fe&1&70


You may or may not have to reboot


After you do this and recheck the keys you will see that they have populated the subkeys with LOTS and LOTS of New Data!!!!!


That's it, FIXED! You will not have access permissions to any of those keys but that is fine.



I have also found that in the nvraid.inf config file it there is an explicit permission for "Administrator" (; allow access from system and administrator only); whether or not you have access to the "Properties" key under the Administrator Account is irrelevant, the issue will not be fixed unless you follow my steps above.


I really hope this helps a lot of other people because this issue was a doozy!!!!!


Best of luck,


B0bbyP

B0bbyP said:

I really hope this helps a lot of other people because this issue was a doozy!!!!!





Best of luck,





B0bbyP

I wish an admin or someone would fix it so we stop getting all these extra blank lines.

I agree johnhoh; it looks fine to me but I have noticed this issue in other posts as well....