Win 10 will not boot up with active usb devices plugged in

Hello Gary,

Thank you for visiting Microsoft Community and providing us with the detailed description about the issue.

As per the description, I understand that you are experiencing issue with Windows 10 won’t boot up with active USB devices plugged in the system.

I certainly understand your concern and will try my best to help you.

I would suggest you to try the following methods and check if it helps.

Method 1:

Step 1:

To diagnose whether this issue occurs in “Safe Mode”, let’s reboot the computer in safe mode and check if the issue appears there as well.

Safe mode is a diagnostic mode for Windows that starts your computer in a limited state. Only the basic files and drivers necessary to run Windows are started. This helps us in identifying whether the issue is due to some third party programs conflict. The word Safe mode appear in the concern of your monitor to identify which windows mode you are using.

Follow the steps given below and check if that helps.

1. Type settings in search and click on Settings.

2. Click Update and recovery, and then tap or click Recovery.

3. Under Advanced startup, tap or click Restart now.

4. Once your PC restarts, on the Choose an option screen, tap or click Troubleshoot.

5. If you don't see the Startup Settings option, tap or click advanced options.

6. Tap or click Startup Settings.

7. Tap or click Restart.

8. On the Startup Settings screen, choose the Safe Mode.

9. Sign in to your PC with a user account that has administrator rights.

Step 2:

If the issue does not appear in safe mode, place the computer in clean boot state and check if the issue reappears.

Placing your system in “Clean Boot” state helps in identifying if any third party applications or startup items are causing the issue. You need to follow the steps from the article mentioned below to perform a Clean Boot.

How to perform a clean boot in Windows

 

https://support.microsoft.com/en-us/kb/929135?wa=wsignin1.0

 

If the issue does not occur in “Clean Boot”, then you may determine which application/service on the computer is causing this issue. This can be done by following the instructions for “Windows 8.1 and Windows 8” given in the section “How to determine what is causing the problem by performing a Clean Boot” from the same given link.

 

Note: Refer "How to reset the computer to start normally after clean boot troubleshooting" to reset the computer to start as normal after troubleshooting.

If the issue persists, follow method 2    

              

Method 2:

Let's perform a “Startup Repair” using Windows 10 bootable DVD or USB drive and check if that helps. Initiating repair from CD/DVD may have different results than earlier since the source of boot is different now. So, I would suggest to perform the repair again and check if it helps.

If you don’t have the bootable DVD or USB drive, please refer to the steps in the article given below to create one and then follow the steps given below.

Create installation media for Windows 10

https://www.microsoft.com/en-us/software-download/windows10

Once you have made the bootable USB or DVD drive, please follow the steps.

1. Insert the installation DVD or USB and boot Windows 10 from it.

2. In the ‘Windows setup’ page, select the ‘language to install’, ‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’.

3. Click on ‘Repair your computer’ and select ‘Troubleshoot’.

4. Click on ‘Advanced options’ and select‘Automatic Repair’ and select the operating system.

You might also require to change the boot priority in BIOS in order to allow the computer to boot from CD/DVD.

Important: While scanning the hard drive if any bad sectors are found, the scanner tries to repair that sector, any data available on that might be lost.

Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.

 

For more information:

I would suggest you to refer to the suggestions provided by “Andre Da Costa” replied on January 22, 2015 in the following Microsoft Community link.

Frequently Asked Questions: Windows 10

http://answers.microsoft.com/en-us/insider/wiki/insider_wintp-insider_install/frequently-asked-questions-windows-10/5c0b9368-a9e8-4238-b1e4-45f4b7ed2fb9

I hope this information is helpful.

Please do let us know if you need any further assistance, we will be glad to assist you.

Thank you.

I have the same motherboard and BIOS in an SR1900Z. This MB has an on-board NVIDIA nForce 430 chipset and GeForce 6150LE DPU. I have been able to successfully install and run Win 8.1 32-bit on this system (64-bit not supported). I finally got Win10 (32-bit only) installed after several false starts, but I have a number of problems with devices. I have tried both the default Microsoft drivers and the most recent vendor-supplied drivers (NVIDIA, AMD, and REALTEK). I'd be interested in knowing whether you have also seen these problems.

1) The on-board NVIDIA ethernet controller is recognized but the driver(s) will not function

2) There is no USB connectivity, so my USB WiFi adapter also does not work, nor do any USB storage devices. Neither of the reported PCI to USB host controller devices listed has a functioning driver.

3) No display adapters are recognized, neither the on-board NVIDIA nor the AMD PCI-E display/audio adapter. The AMD-attached monitor works, but is installed as a generic PnP monitor (with no display adapter). Because the display adapter hardware is not even detected, I cannot install the vendor's Win10 driver. This may be related to the 3 reported but non-functioning PCI-to-PCI bridge devices.

4) The on-board REALTEK audio is detected but not identified. The generic MS driver is not functioning and the REALTEK driver can be installed on the system but cannot be found in the menu for installation on the device.

5) The SATA controller drivers do not work, although I have no SATA devices.

Most of the driver problems complain of a code 35 (firmware does not include enough information) asking for a firmware or BIOS update. One of the USB controllers reports a code 10 (device cannot start), and one of the PCI bridge devices reports a code 12 (not enough resources)

With no network or USB, it's not really a usable system beyond Win 8.1.

TRS3;

I have my machine fully operational now. All of my Nvidia devices are functional under windows 10 (32 bit) as well.  Note the drivers for my motherboard are as up-to-date as they can get. Most of the drivers can be found for free somewhere on the web. Although this kind of updating was fraught with landmines of nasty Trojans, viruses, ect...

I have no pci-pci bridge errors. The current driver in Win-10 is 10.0.10240.16390.  I think I updated these device drivers in my motherboard firmware some time ago.  I forget where I got them but I will try to get the information to you if I can find it.  I probably got them from the HP Support website, or from the Motherboard Mfg. 

Video problems and solutions:

I did have some problems with the on-board Nvidia display at first boot, but immediately loaded another through the properties menu from Microsoft.  The on-board was freaking out and the dis

play was unstable until I requested a new driver through the properties menu, and rebooted at lower resolution. Of course there is the on-board setting in the BIOS.

To get back to your video card (if you have one) you then have to delete those drivers, install the card, reset your bios to disable the on-board, and reboot for discovery. Windows did install the usual generic driver for the card, but then you can download the drivers for your card manufacturer to get the correct one.

I now have my EVGA GeForce GT 610 2Gb Nvidia card back in. I went to the Nvidia website, did an auto detect, and installed the preferred driver. as usual it took several reboots to do the swap.

Nvidia nForce Networking Controller  Driver version: 73.1.4.0

USB problems and solutions:

I discovered that this problem was in the BIOS. I had to find the option to disable USB Legacy devices. Once I rebooted all of my USB devices worked fine.  Note: I had a unrelated problem with a memory card reader not being recognized (that front panel with the memory card slots in it), but that was not the cause of any USB problems on boot.  I did disconnect the device to test this out.

SATA problems and solutions:

I had real problems with this and tried many things, but the final solution was to enter the BIOS and set the SATA drive with the Windows-10 boot partition as the primary partition in the boot order. I suspected this when I used the SATA to ATA converter and the primary was drive 0 and it would boot.  So just set your boot order and primary boot drive in your BIOS.  This was of no concern to XP or Win-7, but does matter to Windows-10.

RealTek audio problem and solutions:

I had the same problem, but put it last on my list to correct. At first I used the alternate display through my video card via HDMI, and tested if the Hd-audio configured by Nvidia worked. It worked fine. I downloaded the audio driver set from Realtec ( 0006-32bit_Win7_Win8_Win81_Win10_R279 ), and deleted all other drivers and rebooted and then installed the realtec driver. It all works fine now.

Hope this helps

-Gary

Hi Gary, I have the same motherboard as you and I'm trying to install windows 10 pro 32 bit. However no matter what combination of solutions I've tried, win 10 installation always failed.

Mostly I suspect its the nvidia graphics and nforce controller. So, how exactly did you get win 10 32 bit installed on this motherboard? Did you use a pci-e gpu for the install?

DarrelS: I feel your pain.

- "Did you use a pci-e gpu for the install?"

No I used the on-board gpu. Pull your card, and configure to use the on-board graphics in your BIOS. The resolution will be low for the configuration process, but you can correct that after the OS is functional.

-"So, how exactly did you get win 10 32 bit installed on this motherboard?"

I configured the machine into its most basic hardware and settings. One HD drive (address 0), and all of the other on-board settings at the basic level (See above).

Keep trying.

Thank goodness Gary_606 shared his solutions!

I have the same mobo (A8N-LA Nagami Bios: 3.11) on a Presario SR1913WM), and thanks to Gary I"m now going to try his creative and resourceful solutions to installing Win10 32-bit on my Presario.

I'm hopeful since during my previous failed Win10 install attempts the install DVD-R has been in my ODD on a SATA/IDE adapter.  Thank goodness there's still 16 days before the free Win10 upgrade offer expires.

@Gary_606
How did you get your chipset drivers working?

I ask because I got Windows 10 installed on my Presario SR1913WM (with the same mobo 8N-LA Nagami Bios 3.11 you have)(thanks to your brilliant IDE ribbon trick, and tweaking the BIOS' advanced settings [more on this and my other notes later]), but Windows 10 insn't recognizing much of my hardware, including onboard ethernet port, USB ports, SATA ports, expansion slots, or onboard audio.  Even after installing the latest NVIDIA drivers for the chipset and onboard video, and the latest Realtek drivers for the onboard audio, namely:
http://www.nvidia.com/download/driverResults.aspx/14874/en-us
http://www.geforce.com/drivers/results/82701
http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false#High

ASUS' site contained no relevant drivers.  The drivers on the HP site wouldn't install in Windows 10.  The drivers in the 3 links above installed, but still Windows isn't recognizing my hardware.

My top priority is the onboard ethernet since frankly I'm desperate, with just a week to go in the free upgrade offer, to activate Windows 10.  (Since the expansion slots aren't recognized, my ethernet card is no help now.)  I'm disabled so I really lack the money etc to miss out.

This all sounds very familiar (see my earlier post).

Regrettably, that was a year ago and that machine has since joined the departed. However, I do vaguely remember some things.

You might have a look here:

http://www.win-raid.com/t15f37-NVIDIA-Optimized-nForce-Driverpacks-for-Vista-Win.html

As I recall, there are some missing entries in the .INF files in the driver packs from NVIDIA.

You are looking for the nforce 4/MCP51 drivers. Options B1 or B2 here would probably be the best bets, but I would start by just installing the ethernet driver and see if that solves your network problem. If so, you now have the opportunity to go to Microsoft update from device manager to try to update individual drivers, or you can install other components of this package one by one

if you need them at all.

Good luck.

Thank you VERY much, TRS3, that linked-to-post looks like it could be the answer to my dreams, I'm excited to try it!

Not going great yet, nothing I try works from either B1 or B2.  Even after I run the imported the Certificate and ran the setup.exe files.

Looks like I'll need to post to that thread at win-raid.com

So much to confuse; for example, not sure which of Fernando's drivers to apply to the Device Manager these yellow triangles:

System Devices | "PCI-to-PCI Bridge" (3 of these)
Universal Serial Bus controllers | "Standard Enhanced PCI to USB Host Controller" and "Standard OpenHCD USB Host Controller"

And all that I have tried haven't worked.  Even if I try all the options it offers me to tell it which of 2 or 3 is "my hardware".

Even the one I know which of Fernando's drivers to use...
Network adapters | "NVIDIA nForce Networking Controller"
isn't working.  

A time or two it's said I installed something successfully (IIRC the onboard ethernet), but it still isn't working.

Maybe I've just tried too many things; tomorrow I'll try starting over with a quick clean Win10 install.  Maybe I'll try B3 too.

(And I thought at the start of July, surely I could install Win10 in time for Friday's deadline to get it free.  Wish I had at least gotten a PS/2 mouse so all this time wasn't PS/2-keyboard-only.)