Thanks for the reply man. You where right. it was a letter drive issue, funny it didn’t gave me the option to change it last night. The SSD is set as a RAID0. the old HDD is an NTFS and it is only a single drive, not array.
The reason why is that i couldn’t. Because I believe i’m having an issue the PSU. Every time i try to ISO windows 10 on the USB, my computer crashes. No BOSD, just a black screen and sometimes i hear sound from the speakers…
The boot sector and the MRB are copy over from the old HHD all the same partition. So both…
lol i didnt see that attachment option.
Thank you for your help. My brain died on me last night.
EDIT by Fernando: Unneeded blank lines have been removed (to save space) and the quotation code simplified (quoted text is automaticly shown with italic characters).
Hello, Many thanks for the great work! My system is M3N78-EM, RAID 1, Win 10 64 bit. I had problems with the update Win 10 1511 to 1607 - "INACCESSABLE_BOOT_DEVICE" When you try to clean install of Win 10 1607 - found no RAID to install OS. I followed the instructions in this post: [HOT] Win10 Update makes nForce RAID arrays unaccessable (21) And then the installation was successful. To add section “Storage” in the NVidia control panel, installed manually by Fernandos Latest 64bit nForce Driverpack for Win7-10 x64 v10.4.rar \IDE\Win764\raidtool\setup.exe In customize Win 10 ISO I Insert these drivers https://onedrive.live.com/?authkey=%21AK…014229B9E752333 v11.1.0.43. But as someone else had written here, Windows did not want to sleep. I did update with nForce SATARAID v10.6.0.23 section “Storage Controllers” all NVidia devices and problem falling asleep gone.
My only question is whether I have used the correct drivers (AHCI / RAID drivers and nForce SATARAID drivers) for insertion into ISO file? EDIT: BTW, to me there is no “Expand the section System Devices” and look for devices named “Generic SCSI Array Device” (or similar with another language). These are the members (HDD / SSD) of your nForce RAID array (s) " Is it normal ? If not, what is the reason?
@Slavov : Welcome at Win-RAID Forum and thanks for your report! It is fine, that you got Win10 v1607 ("Anniversary Update") properly installed onto your nForce RAID array.
If everything is running fine now, you have inserted the correct nForce RAID driver into the ISO file.
Yes, this is normal. The reason is, that you have removed the original MS INF file named scsidev.inf from the Win10 v1607 image and replaced it by my modded variant, which doesn’t support this "Generic SCSI Array Device".
Hey Fernando. I followed your steps on #146. Have an Nforce 780i mobo and the update just before the 1607 made my raid 0 not populate. These drivers of yours worked well. I hope I don’t have any more trouble. Thanks for the instructions and drivers.
@CoeW1167 : Welcome at Win-RAID Forum and thanks for your feedback! It is fine, that you got Win10 v1607 finally installed and working on your nForce RAID array. Merry Christmas and a Happy New Year! Dieter (alias Fernando)
The only problem I see now is this: When using v10.6.0.23 for orig scsidev mod + signed by Fernando - in Nvidia control panel is not visible raid, but the computer sleeps. When using v11.1.0.43 for orig scsidev mod + signed by Fernando - in Nvidia control panel shows the raid, but the computer does not sleep and can not be turn off from the start shut down (it is possible only by power button). Fernando, do you have any ideas and solutions to this problem?
Having got an nForce array working under Widows 10 (a few posts ago), I now have exactly the same issue with a RevoDrive (an OCZ dual SandForce PCI-E card) not being accessable during installation, even with the drivers. Could this be fixed in similar way? I’ve searched through your forums but can’t see anything obvious. The drivers are Silicon Image SiI 3124 SoftRAID 5 ones.
Probably yes, if your current problem has a similar reason. Question: Is the system drive inside or outside the RAID array? If it is outside, the problem may be solved by forcing the installation of a modified Sil3124 driver. In the other case you may have to do a fresh OS installation by using an ISO file, where you had replaced the in-box Silicon Image RAID driver and the scsidev.inf file by modded variants. If you attach the latest Sil3124 RAID driver, I may do the modification for you.
@Englishman : Thanks for having attached the related Silicon Image Sil3124 SoftRaid5 drivers. After having checked them and done a Google search for alternative solutions, here is my comment:
Your problem has nothing to do with the topic of this thread and cannot be solved in a similar manner.
As you can see >here<, there is obviously no solution available.
According to >this< MS Update page there are no drivers available, which do support your Silicon Image RAID5 SoftRaid5 Controller while running Win10 x64.
If you are not able to get the old Sil3124 SoftRaid5 driver installed while running Win10 (not even by using the "Let me pick… > “Have Disk” option), I recommend to use an older Windows OS like Win7 with this old Sil3124 SoftRaid5 Controller.
Well, I now have the Revodrive as boot device under Win10 x64.
I did some more investigations and it seems that simply no version of Win10 allows the Silicon Image driver 1.5.23.00 to be installed during the installation process, using the ‘Have Disk’ or any other option. I tried three versions, including the Anniversary and original versions, none of them worked. Hence I concur that this isn’t the Anniversary update issue.
However, I found I could install the SiL driver and hence use the Revodrive when installing Win7. I then upgraded the Win7 installation to Win10 and it is still working fine as the boot device.
First, thanks for the drivers! I recently update to Win 10 1607 and couldn’t see my non-system RAID. I followed the instructions in post #146 and was able to get access to my RAID again.
I’ve now started running into BSOD DPC_Watchdog_Violation what seems to be every 24 hours. I’ve found a few posts referencing a “24 hour” bug related to the anniversary update. (https://www.tenforums.com/bsod-crashes-d…-10-1607-a.html & https://answers.microsoft.com/en-us/wind…21329a29?page=1) The recommendations seem to be get latest drivers, but that isn’t an option. I’m just wondering if you’ve received any other reports of similar problems. I tried searching through the forum, but I didn’t see anything stand out regarding a BSOD with that particular message. I’ve done some digging with winDbg and it seems to point to nvstor64.sys. I’m using the 11.1.0.43 version of the modified driver. I’m at a loss for what to try next. Any input would be appreciated.
After having entered "DPC_Watchdog_Violation" into the "Search" box of our Forum I got a lot of hints. Since I don’t have an nForce system anymore since several years, I don’t have any own experience about how to solve your problem.
I’ve started experiencing exactly the same thing. Then when booting into the BIOS screen I have 2 degraded arrays instead of 1 healthy. I was starting to think I had a hardware failure, and that I was going to have to bite the bullet and upgrade the motherboard. But seeing this post I now think it must be a win10 related issue. I’ve worked around the issue temporarily by disabling the MOBO raid, but that leaves my data unmirrored so looking for a better solution. (MOBO upgrade is still on the cards as I need a faster CPU and more memory…)
I’ve started experiencing exactly the same thing. […]
My aunt (whose main PC is nearly the same as the one I have setup as a NF4 SATA/RAID single drive for AHCI, but hers is IDE) has been having this blue screen intermittently (weekly or so) for a long time. Perhaps it was with the anniversary edition update; I always suspected the NVidia network driver. However, other differences; I use a realtek Gb and SB Live (using the kX driver) cards instead of the NVidia onboard NIC/audio. I’ve never had this error, but I also normally use this PC for Linux work. Anyway, given the DPC watchdog is a driver issue, I’ve been messing w/ the Windows drivers on this PC to see if it helps hers…and now maybe you guys can join the testing. Or maybe the Creator’s Update will fix everything… :-/
Has anyone yet tried the Preview slow ring build from last week on a boot-drive RAID install?
I’ve just installed the Windows Insider preview 1703 on a PC that wouldn’t install the previous few versions for the reasons in this forum. It has an nForce chipset 430, I think. I can confirm that…
The 1703 version works like a dream on nForce chipsets!!!
Admittedly I’ve only installed it, and not done any testing other than that. I had to boot from the CD and do a fresh install, for some reason it wouldn’t run setup from the desktop, I’m not sure why. My other 2 PCs were fine with just an upgrade. Perhaps it’s because I’d had to disable updates for a while. Thank you Microsoft, and thank you everyone who has worked so hard to keep Windows working on nForce chipsets over the last few versions of windows. I hope other people can confirm that it also works on other versions of nForce.
@Zelphium : Welcome at Win-RAID Forum and thanks for your report, which seems to be really good news for all nForce RAID users, who want to run Win10 v1703 (as fresh install or as update). Enjoy your old nForce RAID system in combination with the latest Windows OS version! Regards Dieter (alias Fernando)
I have tried to follow the post about editing the iso file and I end up not being about to uncheck scsidev.inf. I am missing a step i am supose to be doing. I have a raid 0 i am running an Xps 720.
The 1703 version works like a dream on nForce chipsets!!! 