Home Desktop PC with BIOSTAR MoBo MBP6PB M2+ ver 6.0 Model - N61PC-M2S Chipset NF-MCP61
with 1 Hard disk = SSD 240 GB
Win 10 Home 32 Bit
BIOS was flashed (previously 2 -3 years ago to upgrade / update 2010) . Do I have to re-flash BIOS?
Athlon 64x2 Dual Core Processor.
Runs on Win 10 2GBx2 Slots = 4GB. (Only 2 slots with max 2GB each available).
Technician at repair shop succeeded (don’t know how) in re-installing from USB Win 10 Home 32 Bit OS after removing RAM from one slot. But I am not convinced that it is a hardware issue. Something is blocking the second RAM slot.
PC runs okay on Win 10 with one slot of 2GB RAM but ends up with the same issue of Detecting Array when both RAM slots are fitted with 2GB RAM each. Earlier (before the issue, Win 10 was running on same PC with 2x2GB RAM properly). How to fix this RAM + Detecting Array issue? I need full 4GB RAM for better performance.
Your report, that only 1 SSD is connected to the mainboard, verfies, that no RAID array has been created and a switch to the IDE mode should be possible, but may require a fresh OS installation (why don’t you use Win10 x64?).
To be able to find out the reason why you cannot use both attached 2 GB RAM modules, I recommend to run a hardware diagnostic tool like HWINFO and/or to swap the connection of the RAM modules.
A fresh / clean Win 10 Home 32 Bit was re-installed successfully with 1x2GB RAM.
(Many programs don’t run on 64 bit and 64 bit is quite confusing as I am used to 32 bit). Re-flashed the BIOS Upgrade again on windows successfully.
If both RAM slots are loaded then PC stops at Detecting Array…
If 1 slot is loaded it runs all okay.
Swapping RAM in slots shows RAM is okay but 1 slot has been identified as the one creating the error Detecting Array. I still doubt it is not hardware issue but perhaps a driver issue.
While making a clean re-install of Win 10, I could not do as instructed – This needs storage drivers to be pre-installed-- as I do not know which storage driver is being asked for. Besides, Win 10 picks its own appropriate driver. Secondly, the Graphic Driver (NVIDIA) do carry 2 extra drivers - 1 of them is SMB Storage driver and other is perhaps Network Driver if installed manually. I have not done a manual re-install of graphic driver.
DUMO freeware shows –
Or is there an error in settings for AHPI, ACPI , AHCI or somethings like that or is it an error / virus in MBR or bcdedit, etc. BIOS settings seem to be okay.
HWiNFO was run without loading the problematic RAM slot. The summary report is as attached – HWInfo results.zip (14.2 KB)
How to fix it?
Edit by Fernando: To save space I have deleted the voluminous HWInfo results and attached them as *.zip archive.
If you want to check a maybe faulty device, you should not remove it before running a tool like HWInfo.
NVIDIA MC61 chipsets don’t support the AHCI data transfer protocol. Your on-board NVIDIA nForce SATA Controller can only be run in IDE or RAID mode.
Trying to get rid of the “RAID Array” , you should enter the BIOS and set the NVIDIA SATA Controller to “IDE”. After having done that, I recommend to re-insert both RAM modules and to do a fresh install of Win10 in IDE mode. The best NVIDIA nForce SATA Controller driver for this configuration is the Win10 in-box Microsoft driver named pciide.sys. It will be installed automaticly during the OS Setup. Don’t ty to change the driver.
If your issue should persist, it is the proof, that your currently in-use mainboard has a severe hardware (RAM management) issue. In this case the complete mainboard should be replaced by a not faulty one.
Point 1 - If I add RAM in both slots, then PC won’t Start but give Detecting Array error. So started PC with 2GB RAM in 1 slot and then added 1 GB RAM in second slot in running PC. And then run HWiNFO and these are the results attached.
Point 2- AHCI settings are done after OS install for Vista and 7 by going into Regedit and also for Win 10 on my PC by restarting in Safe Mode. My PC runs with SSD.
PS/2 keyboard is default in BIOS. By connecting a PS/2 keyboard, BIOS is accessible and then setting USB support as Enabled in BIOS, all USB run okay. And Win 10 OS can be installed from USB.
Point 3 – In BIOS RAID is Disabled by Default.
The Drivers were changed using 3rd party updaters to see if it makes some changes to this old PC. Can be rolled back anytime. But it was worth noting that NVIDIA nForce Serial ATA Controller shifted its position from Storage Controllers to IDE ATA/ATAPI Controllers and yes, it is not the latest version. Latest version comes with Win10 OS setup.
Point 4 - I am hopeful. I know the answer lies somewhere in your commented points 2 and 3. I shall keep trying.
You cannot choose or change any AHCI settings, because your mainboard doesn’t support AHCI.
The installation of any nForce SATA (RAID?) driver was a mistake. Only the Win10 in-box MS SATA driver named PCIIDE.SYS supports your on-board nForce SATA Controller while running in IDE mode. Furthermore this MS driver is the only possibitlity for you to get the SSD perfectly cleaned by using the TRIM command.
… Just trying to re-create events/mistakes to find out what really went wrong and how to fix it.
And why I went to manually update drivers with 3rd party updater on Win 10 was because PC got repeated BSOD at long intervals due to ndis.sys (not ncis.sys-- as mentioned in first post - And that was with all drivers as comes up with Win 10 setup / install (no 3rd party)) and then another BSOD - nvlddmkm.sys. (that was with wrong drivers as selected by me on random). Now with 3rd party drivers (perhaps due to my correct selection), I did not get any BSODs. Something is left out half-baked in my PC. Trying to sort it out before going in to hardware (RAM slots)…Text
After having read all your posts it seems to me, that you may only have updated the OS, but never done a clean OS installation since Vista times. If my impression should be real, it would have been a very big mistake and may explain all your troubles.
Here is my statement to your last post:
Your used “Switch from IDE to AHCI” and “RAID to AHCI” tools cannot have the desired effect for your system, because your mainboard’s NVIDIA nForce chipset doesn’t support the AHCI protocol at all (as already written above).
All Microsoft Operating Systems from Windows XP have the generic SATA IDE driver named PCIIEDE.SYS in-the-box (but with different versions and properties). Provided, that the system drive (SSD or HDD) is connected to a NVIDIA nForce SATA port running in IDE mode, there is nothing to load at the beginning of the OS installation - the OS own IDE driver will be automaticly installed and the related IDE Controller will be listed within the “IDE ATA/ATAPI Controllers” section of the Device Manager as “Standard Serial ATA Controller”.
Regarding the TRIM support it is not enough to check, whether the TRIM command has been sent. Much more important is the question, whether TRIM has been arrived within the SSD cells. Neither NVIDIA’s SATA AHCI Controller (of newer nForce chipsets) nor NVIDIA’s SATA RAID Controllers let the TRIM command pass through. If you want to know whether your SSD is continuously TRIMed, I recommend to run the “TrimCheck Tool”. You can find the related download link and the guide within the start post of >this< thread.
You are right on all counts – 1,2 ,3 ,4 .
TrimCheck Tool also came up with message - NOT Working.
Rolled Back the driver and it dropped down to Storage Controllers.
Yes, there is no standard Serial ATA Controller Driver in Device Manager.
So if MoBo does not support AHCI then what to do? Not to install Win 10 OS?
Which driver did you roll back to which driver?
Please post a screenshot of your Device Manager after having expanded the “IDE ATA/ATAPI Controllers” and “Storage Controllers” sections. If you don’t know how to do it, past the exact names of the listed Controllers(s).
Although NVIDIA nForce chipset systems are officially not supported by Win10, you should be able to get it installed and working in IDE mode. This is what I recommend to do:1
Make a complete backup of your current system drive and store it outside of it.
Create a bootable USB Flash drive with the desired Win10 Image on it by using a tool like Rufus.
Enter the BIOS and make sure, that the NVIDIA nForce SATA Controller is running in IDE mode.
Unplug all currently connected HDDs and SSDs except the target SSD.
Boot off the USB Flash Drive and start the Win10 Installation.
When Setup comes to the point where you have to determine the target location for the OS installation, let the Setup delete all shown partitions of the SSD and create a new one with an appropriate size.
Once the OS installation has been completed, run the Device Manager and look for missing drivers. If needed, I will help you to find them.
As far as installing Win 10 OS procedure is concerned I have done it twice on a separate SSD completely dedicated for all sorts of repairs for this Win 10 on the same PC so that old data on old SSD with Win 10 and its problems are out of the system. All steps 1 to 6 for OS install were correctly followed. Device Manager never comes up with any Yellow Mark or Question Mark - no missing drivers - device manager is okay whether drivers are changed / rolled back. Yet, whether old SSD or new SSD, the moment both RAM inserted, PC shows Detecting Array.
Standard Serial SATA Controller - Driver appears in Have Disk Box when Show compatible drivers only is unchecked - attempted to install it . Got installed and in a moment things in device manager slipped back to the other driver versions. Not compatible. Do we have to look into MBR?
It was a big mistake to use any NVIDIA nForce driver for your specific system.
If you want to “repair” your currently running OS, you should replace the “NVIDIA nForce Serial ATA Controller” by the listed and shown as being compatible “Standard Dual Channel PCI IDE Controller”, which is the Controller’s name while using the MS Win10 in-box IDE driver named PCIIDE.SYS.
1- Did as instructed and we now see 6 (3x2) set of drivers under IDE/ATA ATAPI Controllers- Looks Good!
2- Then inserted both RAM and got Detecting Array on restart.
3- Removed 1 GB RAM from problematic RAM slot and restarted. Got BSOD with D1 - IRQL driver not less or equal (ndis.sys).
4- Restarted PC. Reached desktop normally. This shows that something more is to be fixed.
See the screenshot (combined 3 figures) - We can see 2 more nVIDIA nForce drivers –
1- Network Adapters – Network nForce Networking Controller --ver 220.127.116.1136
2- System Devices - nVIDIA nForce PCI System Management – ver 4.6.9 Are these nVIDIA nForce Drivers also to be replaced? If so, with which ones?
1-By PartedMagic Secure Erased the SSD.
2-The settings in BIOS were checked --BIOS> IDE Function Setup>RAID Config = All Disabled / Serial ATA Controller = All Enabled / All IDE= Enabled. Is this setting okay?
3-The moment both RAM inserted … Detecting Array.
4-Re-installed Win 10 with RAM in 1 slot. OS setup by default picks up RAID driver nVIDIA nForce driver under IDE ATA / ATAPI Controllers for 1 out of 2 Std Dual Channel PCI IDE Controller. Rolled it back.
5- Enabled TRIM using cmd. TrimCheck Results – WORKING! The Question remains RAM and Detecting Array …
Perhaps it is because of the wrong RAID driver loaded manually on Win 10 in order to counter ndis.sys BSOD. Or was the RAM slot failing? Now the BIOS seems to be loaded with RAID driver and is not shaking it off even after BIOS re-flash and reset to default settings. And may be OS Setup brings in a driver Std SATA AHCI Controller but it remains in Non-compatible list… slips when installed… for obvious reasons – AHCI. Only if a suitable Std SATA Controller driver could be found.
The search is ON!
Your mainboard seems to be faulty (1 of the RAM slots is broken/not properly working).
There must be something wrong or misleading:
If your on-board NVIDIA nForce SATA Controller is running in “IDE” mode and you boot off an untouched Win10 Image, the Win10 Setup will automaticly load its in-box MS IDE driver. Win10 has no NVIDIA nForce SATA IDE, but an nForce SATA RAID driver in-the-box, but the RAID driver will only be used, if the Controller is running in “RAID” mode.
A SATA RAID Controller is always listed within the “Storage Controllers” section and never listed wthin the “IDE ATA/ATAPI Controllers” section of the Device Manager.
If you see any “Dual Channel PCI IDE Controller” listed within the “IDE ATA/ATAPI Controllers” section, your in-use NVIDIA nForce SATA port is running in IDE mode und using the generic MS IDE driver named PCIIDE.SYS (and not any NVIDIA driver).
The Win10 Setup will never install any NVIDIA nForce SATA driver onto your old NVIDIA chipset system unless the on-board NVIDIA nForce SATA Controller has been set to “RAID”.
You should never install any NVIDIA nForce SATA driver manually (unless the NVIDIA nForce SATA Controller is running in “RAID” mode).
1- Win10 has no NVIDIA nForce SATA IDE, but an nForce SATA RAID driver in-the-box, but the RAID driver will only be used, if the Controller is running in “RAID” mode. — Most likely! But how? That may be causing Detecting array…
2- Shifting position of Device in the Device Manager was shown (screenshots) in earlier posts.
3- That’s good and okay. as it is supposed to be - I assume.
4- There seems to the half-baked leftovers…
5- That was my error or a chance taken without checking whether it was RAID or SATA. Just wanted to counter ndis.sys BSOD but it led to another BSOD from which the PC never restarted and I had to TurnOfff PC and start again to see Detecting Array ever since…
That’s what I am set to fix. Now if 1 RAM slot or a transistor – UI2 is faulty… only technician can tell. Search for a used MoBo is ON!
RollBack (a button on Driver Properties) It’s meaning is opposite of Update. Rolled back the driver from ver 10.6.0.24 to Std Dual Channel PCI IDE Controller.
As I have already suggested, you should do a clean Win10 installation in IDE mode (without integrating or loading any NVIDIA nForce SATA driver). Only this way you can avoid residues from previous driver installations/replacements/rollbacks.
Since the Win10 in-box NVIDIA nForce driver v10.6.024 named nvraid.sys is a RAID driver and doesn’t support your system while running in IDE mode, you should not use the “roll-back” option.
1- Before making a clean re-install of Win 10 OS, checked for Hidden Devices and Cleaned Ghost Devices/ Drivers with DeviceCleanup Freeware. Disconnected the CD ROM Device. Then checked the BIOS Settings again. Made clean Win 10 OS install from bootable USB with 1 RAM slot loaded by 2GB RAM only.
2- During OS install PC restarts by itself several times and again Win 10 OS by default picked up RAID driver in NVIDIA nForce SATA Controller
3- Whatsoever reason may be, now one thing is certain – it is not due to RAID drivers leftovers or any RAID settings in BIOS.
4- MoBo is not AHCI Compatible. Hence the correct driver Std SATA AHCI Controller will never get installed and will remain in the box as Non-compatible Driver even if it comes with Win 10 OS Install. (Or a suitable Std SATA Controller driver may be found and installed – This is risky - may lead to BSOD - Inaccessible Boot disk).
5- This RAID driver will affect TRIM but Garbage Collection will do the job on SSD. If Driver is rolled back to PCI IDE then TRIM will also work.
The issue of Detecting Array may be due to broken connections in MoBo / RAM slot. It is primarily a Hardware issue. 2 big simultaneous BSODs broke the MoBo / RAM slot or this old PC was slowly failing little by little and BSODs gave the wake-up call. Am I correct?
Thank you very much for having done a clean OS installation in IDE mode and for your interesting report.
After having done a deeper look into the related *.INF files I found the reason why the Win10 Setup installed the old NVIDIA nForce driver instead of the brandnew and TRIM supporting MS driver:
The Win10/11 in-box NVIDIA nForce RAID driver v10.6.0.24 named nvraid.sys is not a “pure” RAID driver, because it additionally supports the NVIDIA nForce SATA IDE Controllers with one of the following DeviceIDs: DEV_0266, DEV_0267, DEV_037E, DEV_037F, DEV_036F, DEV_03F6, DEV_03F7 or DEV_03E7.
The NVIDIA driver has been correctly dated by NVIDIA on 01/06/2017, whereas all MS own Win10 in-box drivers like the pciide.sys are wrongly dated 06/21/2006. If more than 1 driver is compatible with the related hardware device, the OS Setup prefers the one, which seems to be newer (the Device Management of th OS reads only the content of the *.INF file).
This explains why the fresh OS installation hasn’t brought the result I had expected (usage of the generic MS IDE driver from scratch), but you can repair the OS Setup’s fault easily by running the Device Manager and replacing the “NVIDIA vForce Serial ATA Controller” by the as well compatible “Standard Dual Channel PCI IDE Controller” and get this way TRIM support for your SSD.
Anyway you now have a freshly installed clean OS, which should be much better performant without any old garbage.