Thx Dieter, i will test it 
Hi Fernando!
Thx for your work here. I installed Windows 10 pro x86 on my computer. Mainboard is the ASRock K10N78D with a nForce 720D (MCP78D) Chipset. ASRock Driver fpr Win7 is named ā¦"AllIn1_Win7(15.45)"ā¦ works fine with Windows 10. Then I deleted ASRock Driver fpr Win7 is named ā¦ "AllIn1_Win7 (15.45)" and installed for the SMU Driver (v1.71) modified and Ethernet Driver (v73.3.5) modified from Your "Latest nForce Driverpacks for Win7-10". Both drivers from your "Latest nForce Driverpacks for Win7-10" work fine (in my opinion) without any signs of failure. But in the Device Manager in the NVIDIA nForce System Management properties and NVIDIA nForce Networking Controller properties, in the "Driver" tab in the Digital Signer line displays "Not digitally signed". 1. Should I worry about "Not digitally signed" in the Device Manager ? Which driver of the chipset would you recommend to use for Windows 10 pro x86 (ASRock the SMU Driver "AllIn1_Win7 (15.45) or the SMU Driver (v1.71) modified from your "Latest nForce Driverpacks for Win7-10") ? 2. After installing your Ethernet Driver (v73.3.5) modified (from Your "Latest nForce Driverpacks for Win7-10"), Windows 10 through windows update automatically installs the network controller driver (v7.3.1.7336) from 23.02.2012. Which of these two drivers do you think will be more relevant for my network controller (your Ethernet Driver (v73.3.5) modified from Your "Latest nForce Driverpacks for Win7-10" or installed through windows update network controller driver (v7.3.1.7336) from 23.02.2012) ? P.S. I apologize for my bad English.
Thx
@Amatorcomp :
Welcome at Win-RAID Forum!
No, this wrong and misleading message has no impact on the function of the related driver and the performance resp. stability of the system.
By the way: Havenāt you imported the Win-RAID CA Certificate, before you installed the mod+signed drivers?
Since I cannot test it myself (due to a missing nForce chipset system), you have to find it out yourself. If not, you should have done it.
I am sorry, but I cannot give you an answer, because I have never used my nForce system with Win10 as OS.
Regards
Dieter (alias Fernando)
No. Was it necessary to do this?
Thx
No. Was it necessary to do this?
Yes, if you want to prevent messages regarding the missing signature. The Win-RAID CA Certificate has to be imported, before you are going to install any of my mod+signed drivers.
Ok.
Thx
Having made a fresh install of Windows 10 1703 with the āFernandos Special 64bit nForce RAID Driverpack for Win7-10 x64 v10.4ā RAID Drivers integrated with NTLite, I couldnāt manage to upgrade (after install) the Awy/SMBus/SMU drivers to the custom ones. Having installed the certificate I just could not locate which components to manually update (for use with Have diskā¦ Option) in the device manager. Also trying to use the installer just displays me that no compatible hardware is available.
My Sys Specs are:
M2N-MX SE Plus // Chipset NVIDIA GeForce6100 /nForce430
Windows 10 1703 Build 15063.0
AMD Athlon 64 X2 3600+ 1.90Ghz @ 2.0GHz
Also: Have disabled from Bios my Onboard Sound & Onboard LAN, because using external ones.
@PumpkinEater91 :
Welcome at Win-RAID Forum!
Do you have any problems with the related devices or do they have a yellow flag within the Device Manager?
If yes, please post the HardwareIDs of the related nForce Chipset devices (right click onto them > āPropertiesā > āDetailsā > āPropertyā > āHardwareIDsā). Then I will tell you, which INF file is the correct one for them.
Regards
Dieter (alias Fernando)
Hi Fernando thanks for the welcome!
Actually had No problem (May be with they Sleep/Hibernate but no usage required so far).
Was just asking because I couldnāt locate in the device manager which drivers had to update to enjoy yours mod improvements.
As long as you donāt have any problem, I recommend to let everything as it is now.
Hi Fernando, Iāve found your forum just a few days ago, itās really impressive, congratulations!. Youāve been around for a while helping folks, so first thank you for your work to the community!! 
My old rig mainly dates from 2007 but itās still running as brand new so after years of Win7Ult x64 without problems, I decided to upgrade it to Win10Pro 1703 x64 with a new SSD from scratch to level it to the others computers at the office.
Everything was smooth until I ran my robocopy backup from my 2 disk striped raid to another disk. After 20 mins running I got a crawling mouse and kb for like 40 mins (running with less than 40% of CPU & Memory use), to finnaly crash with a BSOD saying that VIDEO TDR FAILURE on nvlddmkm.sys. After restarting I found an entry on the event viewer 40 mins before the crash with the event 11 on nvraid. All robocopies lasting more than 20 mins, are crashing with the same process.
So I believe itās not the graphic driver (2 x PNY NVIDIA GeForce 7900GS SLI) but the raid driver (EVGA nForce 680i SLI P/N: 122-CK-NF68-AR).
Win10 installed the driver 10.6.0.24 for the raid, so I manually forced to 11.1.0.43 (first from NVIDIA package and then from your package) but Iām missing the entire raid after rebooting (even when itās still in the MediaShield bios, itās ādisconnectedā on Device Manager and MIA in Disk Management). The process Iām following is as you suggested, update the NVIDIA nForce RAID Controller, the NVIDIA nForce Serial ATA Controllerās (3 of them), but I couldnāt find a driver for the NVIDIA nForce RAID Device (2 of them) so that are staying on the in-stock 10.6.0.24 and I believe this could be the problem. Also tried 9.99.0.9 with the same result.
So the questions would be if you share my reasoning and where to find the āDeviceā driver.
Attached find some screens for reference.
Thanks in advance!.
14:30 US-CT
[Update]
Shouldnāt the Hardwared Idās of the Disk drives / NVIDIA Stripe matchs the Storage controlers / NVIDIA nForce RAID Device (see 2nd screen?)
19:00 US-CT
[Update2]
After a some hours, I figured out how to get the raid back using your 11.1.0.43 x64 mod, tomorrow Iāll run more disk intensive test to see if I got rid of my original problem also, the BSOD.
The remaining question on your OneDrive there are two versions āmodā and āorigā āscsidevā, which would be the difference? (booting or not booting raids respectively?)
And again, thanks for all your work on this forum, before I arrive here I was about to give up on Win10 and return to 7ā¦
23:40 US-CT
@langusiii :
Welcome to the Win-RAID Forum!
The devices named āNVIDIA nForce RAID Deviceā (= members of the RAID array) are usually hidden. To show them listed within the āStorage Controllersā section of the Device Manager you have to hit āViewā on the Device Manager menu bar and then check the option āShow hidden devicesā. For details look >here<.
You can find the answer >here<.
Regards
Dieter (alias Fernando)
Hi Fernando,
Of course I "showed hidden devices", but when using the drivers of post #1 on the "NVIDIA nForce RAID Device" says that those drivers didnāt match my hardware. Using your drivers "orig scsidev" from the OneDrive did work and allow me to see the RAID back.
Reading that post I think both are related when the RAID is your System Disk but using my modified or your modified scsidev. In my case the SSD is the System Disk and the RAID the file disk, so I think that post #146 or #311 should work the same to me, right?
However this morning crashed again with the same errors as at the beginning: copying files (this time not involving the raid), some nvrd64 errors (before were on the win10 driver nvraid), start to crawl, and BSOD with VIDEO_TDR_FAILURE. The differences this time were: a) nvrd64 instead of in-box nvraid, b) the last event entry 30 minutes before crash was "Bad Memory Regions", weird, didnāt have any problems on Win7 until last weekend and I havenāt touch the mobo (just plugged the SSD on an existent wire), and c) Fricking WinUpdate was installing the Aug rollout (KB4034674) when it start to crawl, there is not event entry for successfully finishing but checking now says itās up-to-date, weird again.
Will ran memtest intensive (takes like 8 hrs) just to discard memory problems and Iāll be back tonight.
Thanks in advance.
Rgds,
Javier (alias LangusIII)
Which nForce SATARAID driver version did you use and which is the DeviceID of your NVIDIA nForce RAID Controller?
64bit nForce SATARAID drivers v11.1.0.43 for orig scsidev mod+signed by Fernando
DeviceID = HardwareID? ==>
ACPI\NVRAIDBUS
*NVRAIDBUS
Discarded a memory problem: 8 x extended passes of memtest (20hrs run) says "no problem" as I presumed, since no problem for many years of Win7 until last weekend Win10 fresh installā¦
I went through my notes and realized a couple of common factors on Event Viewer among crashes: 1) nvraid before and nvrd64 now, event 11 "The driver detected a controller error on ." x 4 or 5 entries after booting and 1 entry about when the crawling mouse & kb starts, 30 mins before the BOSD crash; and 2) WindowsUpdateClient has started some update that I didnāt authorize (I hate the idea of some lab tech using me as beta tester and messing with my computer performance when I probably need it most, but itās the priceā¦ for now). It is probably something related with the raid controller driver, but I didnāt realized WUC was running (even when Win10 System, pagefile.sys and TEMP are on the SSD not the RAID).
Do you know the meaning for "Device nor Migrated" for the NVIDIA STRIPE Disk? itās because Iām using the MoBo RAID or something else?
Any other ideas to try out?
Thanks in advance and rgds.|addpics|gtb-1-008c.jpg-invaddpicsinvv,gtb-2-a9c7.jpg-invaddpicsinvv|/addpics|
@langusiii :
Thanks for your screenshots, which verify, that you have a lot of storage and USB drives connected to your system.
To find out the origin of your problems I recommend to unplug all these devices except the bootable system drive and the RAID array.
Further questions:
1. Which device manages the listed āMicrosoft VHD Loopback Controllerā?
2. Which is the DeviceID of your NVIDIA nForce Serial ATA Controller"?
The message was āDevice not migratedā and according the related āInformationā it seems, that the OS tried to take the NVIDIA RAID array from the list of the āDisk drivesā due to an USB device.
Hi Fernando, thanks for your answer!..
Iāve just have 3 storage devices plugged as the screenshots shows, 1) both Raid disk on SATA#1, 2) System SSD and 3) an xtra disk which is temporal manual mirror of the Raid on SATA#2 and all others are in gray which I presume is "disconnected" but shown because I "unhide devices". Anyways Iāll follow your suggestion disconnecting 3) for next tests.
I have no idea. On my first post screenshot it wasnāt there, neither is now, but seems that it was early today when I took the previows screnshots. My first gues is an ISO image I mounted early today and second the OneDrive I 've just got rid off.
Sorry for my ignorance, if DeviceID is the same as HardwareID then
PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2
PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE
PCI\VEN_10DE&DEV_037F&CC_010485
PCI\VEN_10DE&DEV_037F&CC_0104
If not please tell me where to find it.
Attached the events #11 on nvrd64 at boot time.
Thanks in advance.
Rgds.
|addpics|gtb-3-f8ea.jpg-invaddpicsinvv|/addpics|
@langusiii :
Thanks for the HardwareIDs of your NVIDIA nForce SATA Controller, which verify, that you have an MCP55 system. Have you ever tried the NVIDIA nForce SataRAID drivers v9.99.0.9?
Zitat von langusiii im Beitrag #517
I have no idea.
Please check the HardwareIDs of that device.
Hi Fernando , thank you for your response!.
Yes, but I used the one on your post#1 so I couldnāt set that driver to the "NVIDIA nForce RAID Device" and I lost the complete RAID, not your OneDrive mods of post#146/*. So Iāll give a try to those and Iāll be back with results.
I found on the online MS documentation that "Microsoft VHD Loopback Controller" is virtual hard drives controller used when you mount a ISO image among others. Yesterday I mounted and unmounted an ISO image just to see what was inside and then took the screenshot (reason because is disabled in gray), but now there is not such device, so itās not related with the RAID issues. Anyways I did mounted again and the HardwareID is {8e7bd593-6e6c-4c52-86a6-77175494dd8e}\MsVhdHba
@langusiii :
The big problem of all nForce RAID users, who are running a modern Windows Operating System from Win7 up, is the fact, that they need to use the NVIDIA nForce SataRAID drivers, although there are no such drivers available, which were optimized by NVIDIA for these Operating Systems. Unfortunately NVIDIA stopped the nForce chipset production and development of the related drivers already in 2009/10. That is why it is so difficult to find the ābestā Win10 compatible nForce SataRAID drivers among the available ones.
For users like you I recommend to use the NVIDIA nForce SataRAID drivers v9.99.09 WHQL, which natively do support MCP55 RAID systems. The mod+signed 64bit variant is attached.
Before you start with the driver update, donāt forget to set a restore point. And donāt forget to update all NVIDIA related devices, which are listed within the āStorage Controllersā section of the Device Manager (incl. the usually hidden ones), before you are going to reboot.
Good luck!
EDIT:
The above text and the attached driverpack has been changed by me at 08/13/2017. When I wrote this post, I didnāt consider, that the OS Win10 from v1607 up doesnāt accept anymore any original NVIDIA nForce RAID driver.
64bit nForce SATARAID drivers v9.99.09 mod+signed by Fernando_for orig scsidev.rar (383 KB)