Yes we know… I know. Electronics manufacturers don’t want to support more than 5 years backwards as well as Software manufacturers… its just programmed obsolescence to generate trash and money…
Anyways, I tried with your attached “64bit nForce SATARAID drivers v9.99.09 WHQL.rar” but I couldn’t find a driver for my NVIDIA nForce RAID Devices (see screenshot because I’m not sure if I’m doing something wrong), and I know if I leave the with 11.1.0.43 will loss the RAID after booting.
I also tried with the one in your OnDrive “64bit nForce SATARAID drivers v9.99.09 for orig scsidev mod+signed by Fernando.rar” and this did indeed installed well (see screenshot). Also a question here, when listing the options for changing the driver on Device Manager, each device (RAID Controler, Device’s and SATA Controler’s) listed like 6 drivers options for the same driver version (see on screenshot). My choice was the first one but If I choose a different one will it make any difference?
However the results on event viewer were the same as with 10.6.24 (in-box) and 11.1.0.43: on booting I’ve have 5 errors on nvrd64, 10 mins later another one, and after a while copying files from the RAID to the other disk mouse and kb start to cwawl then BSOD with error VIDEO_TRD_FAILURE. So no luck yet.
And forgive my ignorance, I saw that the difference between the “v9.99.09* WHQL” and “v9.99.09 for orig scsidev” drivers besides the signature, is in the [NVIDIA.ntamd64] section of the .INF file. What is the meaning of that section and entries?
Any other ideas to give a shot?
Thanks in advance.|addpics|gtb-4-1cb5.jpg-invaddpicsinvv,gtb-5-4913.jpg-invaddpicsinvv|/addpics|
@langusiii :
As you have found out yourself, my advice to install the WHQL variant of the NVIDIA nForce SATARAID drivers was not a good idea. I am sorry about it. When I wrote my last post, I didn’t think about the problems of nForce RAID users, which are running Win10 v1607 or higher on their RAID array. To prevent any troubles for other users I have just edited my last post and changed the attached driverpack.
Yes. The Device Manager shows the names of all compatible devices (in your case additionally with the driver version and date of release), but if you install different variants (WHQL resp. differently modded) of the same driver version, the user has to guess, which driver variant is meant. It may help, if you remember the chronological order you tested the different variants and the Device Manager uses the same order. If you are unsure, it is better to use the “Have Disk” button and to reinstall the related driver variant from scratch.
When you want to install a specific driver for a specific hardware device (here: “NVIDIA(R) nForce RAID Device”), the Device Management looks into the related *.INF file and compares its entries with the HardwareIDs the OS has detected itself. The problem is caused by the fact, that NVIDIA didn’t care much about the nForce RAID device HardwareIDs INF file entries, when the company compiled the nForce RAID drivers. On the other hand Win10 from v1607 up detects SCSI devices another way than before. Microsoft changed the HardwareIDs content of the Win10 v1607 in-box *.INF file named scsidev.inf, with the consequence, that the Device Management prefers to install this MS driver, which is absolutely not compatible with an nForce RAID device.
That is why I have modified the 32/64bit *.INF files of different NVIDIA nForce SATARAID drivers to make them compatible with Microsoft’s changed hardware detection routine. I just added the HardwareIDs, which were missing within the original INF files.
EDIT:
The best NVIDIA nForce IDE drivers were the ones of the v6.xx series. That is why I have just modified the good old NVIDIA nForce SATARAID driver v6.99 for being usable with Win10 v1703.
The mod+signed 64bit driverpack is attached. Don’t forget to follow my advices given in post #520.
Good luck (finger crossed)!
64bit Win7-10 nForce SATARAID drivers v6.99 for orig scsidev mod+signed by Fernando.rar (276 KB)
Hi Fernando,
Tried driver v6.99… didn’t work. When I solved the signature (were signed by NVIDIA but included your cert), I couldn’t boot in again, not even in safe mode, so I restored Windows from scratch.
So starting with a plain & fresh Win10 1703 up-to-date (plain as Windows leaves, not even the graphic drivers), I tried:
- In-box v10.6.0.24
- v11.1.0.43 for orig scsidev mod+signed by Fernando
- v9.99.0.9 for orig scsidev mod+signed by Fernando
- v6.99 for orig scsidev mod+signed by Fernando (again couldn’t boot after this)
- Cold unplug the raid disks.
An the result was the same:
- During booting process 5 Error entries on Event Viewer with Event ID #11 for nvraid / nvrd64 (depending on In-Box or ByFernando drivers)
- 10 mins after boot 1 more Error entry on Event Viewer with Event ID #11 for nvraid / nvrd64
- Tested with some intensive disk use tool as a “robocopy” or “sfc /verifyonly” and after a while running, my mouse / kb start to crawl (I mean moving veeeeery slooowww).
- Normal TaskMgr use for CPU, Memory or Disk during crawling.
- No pattern detectable on Event Viewer entries (besides WindowsUpdateClient running when wasn’t suppose due to pause and deferred 
…, but also happens without this process running)
- Eventually between 20 and 60 mins Windows crash in a BSOD with a VIDEO_TDR_FAILURE but reading the memory.dmp this was the last timeout triggered (before time-update, network, win32, etc has risen their timeouts because everything was so slow).
- Analyzing the memory.dmp see that NVidia network driver tries to write a non-zero memory page. Memtest86+ ran with no problems after 8 extensive passes 20+ hrs.
So even when those Event Errors shouldn’t be there and they were the reason for my posts here, but after disconnecting the RAID but getting the same, I’m not sure if the problem is in fact Win10 with my entire old hardware.
Reading on this post, Kelly_41m narrow this error to a) memory slots setup 2) heat on mobo or 3) weak power supply. I will explore the last two, before give up and return to Win7.
Any more ideas to try?
Thanks in advance.
https://social.technet.microsoft.com/For…n10itprogeneral
@langusiii :
Thanks for having tested all the different available nForce SataRAID drivers and for your detailed report.
Although the Win10 in-box Event Viewer messages should not be overestimated as long as the system is properly running (AFAIK all users see Event Viewer warning or error messages), there seems to be something wrong with your system.
Since I don’t have any further idea about how I can help you to solve your issue, I wish you good luck to find the origin.
If your efforts to solve your problem should be successful, please let us know how you did it.
Finally seems that my system is stable again running Win10.1703 on an EGVA NVIDIA nForce 680i SLI MPC55 with an SanDisk SDD (system disk) and 2 x Seagate HDD in RAID 0 and with PNY NVIDIA GeForce 7900 GS Graphic Card.
I found out that there were two independent problems:
1. I had 2 x GeForce 7900 GS in SLI configuration using NVIDIA driver 309.08 (last update). I unplugged one card, took away the SLI setup and voila! No more BSOD. Simplest approach always seems to be the best. My conclusion is that the driver working with Win10 is not very comfortable working in the SLI setup and is causing some memory corruption. Further test would apply but for now is working and stable with just one card.
2. The nvraid driver (in-box) as well as all your versions of nvrd64 drivers (9.99.09 & 11.1.0.43) generate Error entries (not Warnings) on the Event Viewer (5 times on booting, 1 time 10 minutes after that and eventually one more) but they seem to be harmless. Although is not nice to read those errors, I’ve been monitoring the RAID drive during all the week and all reports are Healthy with no errors at all, even on a quite hard video editing use. Options are to get use to or deactivate those errors through regedit.
When I get some free time back, I would test with both cards again (feels pity having the second card sitting useless on top of the case) and I will be back to report it here just in case somebody needs it, but regarding the RAID setup I wouldn’t pursue further analysis. If somebody finds out why Windows arise those errors and how to solve it I would be more than happy to test them.
Googling on “nvraid event id 11 windows 10” you can read some other cases with the same conclusion as mine.
Thanks for all your help!
Regarding the 2nd issue reported before (RAID driver Errors), I’ve just realized that the Errors occur when I “RESTARTED” Windows but not when I “SHUT IT DOWN” and then “STARTED”.
Speculating, this could be related with Win10 functionality of treating all disk as removables. The booting first 5 Errors would be related to the 4 partitions and the extended one on the 4th. Then the 6th 10 mins later to a timeout for the controller. Shame that I don’t know how to see why the driver is reporting those Errors to Windows.
Rgds,
Okay so I have been reading over this post and forum trying to get things to work. Finally I have made some progress. Let me break a few things down here as I need some help still
MB: Asus M2N32 SLI deluxe wireless edition
CPU: AMD Athlon 64 X2 Dual core 3800+
RAM: 8GB
4 Drives all SATA
1 drive for OS is 500gig
3 Seagate 3 TB drives
Chipset: 590 Nvidia
OS: Windows Home Server 2011 (which is really Server 2008 R2)
BIOS: Asus official 5002
I have setup up the bios to have RAID, set the 3 drives I want to be part of the RAID. I can go into the RAID bios and set up a stripped array because of the bios it will not see 3 TB each drive is limited to 750 gigs. Finally after using your software Windows will now see the RAID array. But I want to use all 9 TB (yes I know I will get like 8 TB after all is said and done). Currently I cannot get the Nvidia software to see the RAID array but windows does. I know the RAID bios is the issue here I have read up on that.
Questions:
1. Do I have to set the RAID up in the BIOS? Or can I just use the RAID software from Nvidia?
2. Windows see the drives and will let me format it but it is like 2.2 TB ish, If I blow the RAID away will the Nvidia software allow me to set up a stripped array?
3. Is there a modded BIOS that would get me the support I need for greater than 750 gigs?
4. Did I do something wrong with install do prevent the control panel from seeing the array?
5. I cannot find the Nvidia mediashield software on the computer so I am guessing it did not install? all i get is the Control panel software, or is that the mediashield?
Thank you for the help.
@4EvilJames :
Welcome to the Win -RAID Forum!
Your questions are BIOS/Option ROM and not driver related. So they have nothing to do with the topic of this thread and the “Important Drivers” Sub-Forum.
I suspect, that your currently in-use nForce RAID ROM version is not able to create and manage an nForce RAID array consisting of >2 TB sized HDDs. Since it is a long time ago that I used an nForce RAID system, I don’t know, whether an update of the nForce RAID ROM module of your mainboard will solve your problem.
The RAID array can be created either by hitting F10 while booting and using the “NVIDIA(R) MediaShield Utility” (=nForce BIOS RAID Utility) or from within the NVIDIA Console Software (requires an already running OS).
For further details please have a look into >this< manual.
Regards
Dieter (alias Fernando)
Okay thank you. I have tried to get that software to run inside of Windows but cannot. Not sure if the pack I had downloaded from you is the cause or solution but I am just not able to get the mediashield to see the drives. Suggestions?
What do you see, when you hit CTRL+I while booting?
This is what I can tell you.
If I turn the RAID functions on the in the BIOS I can then get to the BIOS RAID menu and set up a RAID of any format. Each drive is a matched 3 TB seagate but he RAID bios sees it as a 750gig drive. If I make the drive then Windows sees it as 750 gig x 3 works to be like 2.2 TB. If I do not make a RAID array in the BIOS RAID then I have found 2 things. 1st if I use your driver back Windows will only see 750 gig drives. If I use the new nvidia newest ones 15.58 Windows will see each of the drives as 2.7 TB ish. With either your software pack or the nvidia software pack the Mediashield software will not run. This is why I cannot set up RAID from the nvidia software. I have tried running the program in compatibility mode and every version of windows it has but it will not run. So the issue with your driver pack is it will not see the full size of the drives and the mediashield software will not run. with the nvidia i can get the full size of the drive but the mediashield software will not run. hope that helps.
@4EvilJames :
All drivers (= *.SYS files), which I am offering within the start post of this thread, have been compiled by NVIDIA and were not touched by me. I just have modified some text ( *.INF) files to make the drivers compatible and usable with other nForce chipsets.
If you are not satisfied with the function of the driverpacks I am offering, why don’t you use an appropriate original nForce driverpack?
Hello to all. First time here and needing some help. I have an asus m2n32 ws pro amd cpu motherboard that is working perfectly with win 7 ultimate 64 bit. I have been trying to update it to win 10 1607 64 bit and then on to 1703. I cannot get win 10 to see any hard drives at installation. I have a striped raid array that I want to install it on. I have downloaded some of your driver packs and tried to load drivers for the nvidia 590 raid array but with no success. Is there a driver pack that you can recommend for this set up, and can you tell me which drivers I should be trying to instal at the load drivers stage of the instal. I would be very gratefull for any assistance.
Kind regards to all, JT
@johntee50 :
Welcome to the Win-RAID Forum!
Your problem is wellknown and has been intensively discussed within >this< special thread.
A solution has been offered by me within >this< post.
Since Microsoft will offer on 17. October the new version 1709 of Win10, I recommend to wait these 2 weeks and then to do a fresh install of Win10 v1709.
Regards
Dieter (alias Fernando)
Thanks for your help. I will do as you suggest and wait a couple of weeks for the new update and then try again.
Thanks and kindest regards, JT
Hello, please do not think I am trying to disrespect you. I am just saying I have a problem and am trying to solve it. I stumbled onto your site and found you working on some stuff that might help. I found some issues with it and thought it could help out. I could care less who’s software I use as long as it makes everything work. So with that said any suggestions on making the Nvidia software for the RAID functional?
Fernando- Thank you for creating this site. I have read a dozen of your posts in the last week concerning nForce4 SATA II drivers with Windows 7 x64. I have an Asus A8N-SLI Premium which I just installed a Samsung 840 Pro 512GB SSD. I’ve always used MS Microsoft Standard Dual Channel PCI IDE Controller with Win7 x64. I am shocked to find that MS driver limits SSD to 1.5 Gb/s instead of motherboard SATA II capability. I think it’s a ploy to force peoples to buy new computers by degrading performance and support. Is there any utility to tweak Standard Dual Channel PCI IDE Controller forcing 3.0 Gb/s, or drivers for red SATA II RAID ports to improve performance?
Edit: I looked backwards thru posts and saw comment about ‘StarTech SATA III Controller cards’. Do you know any SATA III controller cards that MS AHCI drivers can control @ 6Gb/s thus utilizing TRIM? I know I have PCI-e version 1.0 4x slot that would limit, but would l’d be happy with 250 Mbps over 122 getting now.
@swagler :
Welcome to the Win-RAID Forum!
It is already a very long time ago, that I owned an nForce4 chipset system and enjoyed the performance of its RAID0 array. That is why I have problems to answer your questions.
The biggest advantage of using the generic MS IDE driver is the TRIM support.
Unfortunately I don’t know any.
The idea to buy a PCIe connected modern SATA Controller card und to speed up this way your Samsung 840 Pro SSD is good, if you don’t want to buy a completely new system.
Regards
Dieter (alias Fernando)
Dieter, Thank you for quick reply. I haven’t found any StarTech SATA III Controller cards, or any other brand, that claim to support TRIM commands through their drivers, only their PCI-e mSata SSD Adapters. Have you heard of any add-on Controller Cards that can be driven by MS generic AHCI Controller driver? I got a bad feeling there isn’t. Years ago I used a Promise IDE Controller to sport two 200GB hard drives, Promise drivers exclusively booted and operated drives by their drivers. The lack Add-on Controller Cards drivers supporting TRIM looks proprietary to the OS.