Share via

Delay on boot due to multiple attempts to install NDProxy.sys, Srv.sys, and vga.sys

Anonymous
2010-01-23T04:27:46+00:00

Recently installed a fresh copy of Windows 7 x86 and x64 in separate instances to see if the problem of a two minute period between the "windows is starting" screen and the desktop. Neither had a visible impact. I looked around online and found how to create a boot log. The following are the drivers/services that could not be installed during my startup:

4 instances of NDProxy.svs

1 instance of vga.sys (hadn't installed video card driver yet)

1 instance of srv.sys

After installing the necessary drivers and with no alert from the device manager, the boot time is still roughly 2 minutes.

My system specs:

Core 2 duo 2.4 GHz

Asus Commando Motherboard

Adaptec 2120S SCSI raid controller

2 x 73 GB Seagate Cheetah SCSI 15K raid 0

2 x 250 GB Seagate Barracuda non raid for install

2 GB Corsair DDR 800

EVGA 9800 GTS 512 MB

Right now I am at a loss on what to do. For reference my avg startup time in XP was around 10 seconds from the windows logo. Any help would greatly be appreciated.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2012-02-05T23:52:58+00:00

    My Welcome screen stays on for 30-40 seconds, including a black screen with mouse cursor and loading circle spinning.  I've read dozens of articles regarding this problem and found after logging the Win 7 boot process, that I have the exact same errors in Peterka01's boot log (top message in this thread).

    I have used msconfig to run a "clean boot" and a safe mode boot as well.  I found that welcome screen delay disappears when I safe boot, or activate and logon with a guest account.  The wallpaper bug that is often blamed for this, is not my issue, I have downloaded and installed all Windows 7 updates, including SP1.  I tried the KB hotfix after, just to make sure, and it said that I did not need to install it.

    Also, I should point out that I just installed Win 7 clean on a new motherboard.  I have checked the components and cannot find any devices whose drivers are not installed/glitching.  Here's my platform specs:

    Gigabyte GA-X58-UD3R, bios FH

    Intel Core i7 920

    Corsair Dominator, 2x4 1600mhz, 8gb

    Mushkin Chronos 120GB SSD -- SATA3, Windows 7 Boot Drive

    OCZ Vertex I, 2x30GB SSD's in RAID 0

    WD20EARX 2TB HDD

    Seagate Barracuda 7200.11 2TB HDD

    Sapphire HD6850

    Seasonic X-Series 760W PSU

    I have found the NDProxy.SYS file in the windows\system32\drivers directory where the boot log said it was looking for it .. only difference I could see, was that the NDProxy.SYS .. appears as "ndproxy.sys" in actual directory.  I can't change the file name in the directory, so I'm wondering where in the registery this located.  I found a registry entry for ndproxy.sys .. but there's no directory string to modify that I can see.  I checked my network adapters in the device manager also, but I only have one Realtek adapter installed.  There is another category below it that I usually don't see, Network Modules, with one device installed there.  I think it's for my router.  I'll try uninstalling that and or the adapter and reinstalling to see if anything happens.  Advice would be welcome!

    2 people found this answer helpful.
    0 comments
Answer accepted by question author
  1. Anonymous
    2010-01-24T02:37:04+00:00

    Hi Peterka01,

    1.      Check if the issue persists in safe mode with networking, to boot the computer in safe mode with networking, restart the computer and press and hold F8 key (Press and hold f8 key before the windows logo). From the advanced boot option select ‘Safe mode’.

    Link you may refer to: Start you computer in safe mode:

    ******http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode**

    2.      If the issue does not persist in safe mode, then boot the computer in clean boot and check if any third party program is causing the problem. To help troubleshoot error messages and other issues, you can start Windows 7 by using a minimal set of drivers and startup programs. This kind of startup is known as a "clean boot." A clean boot helps eliminate software conflicts.

    Follow the Steps listed below in the link to perform clean boot:**http://support.microsoft.com/kb/929135******Might be some third party application or program is causing the issue.

    After you have finished troubleshooting, follow these steps to reset the computer to start as usual:

    i.                    Click Start, type msconfig.exe in the Start Search box, and then press ENTER.

    ii.                  If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

    iii.                On the General tab, click the Normal Startup option, and then click OK.

    iv.                 When you are prompted to restart the computer, click Restart.

    3.      You can even perform startup repair. Follow these steps:

    i.        Boot Into 7 installation DVD

    ii.      Choose your language settings and click Next

    iii.    Click repair your computer

    iv.   Choose your operating system and click Next. This should bring up system recovery options.

    v.     Click on startup repair.

    Link for reference: Startup Repair: frequently asked questions: http://windows.microsoft.com/en-US/windows7/Startup-Repair-frequently-asked-questions

    Check the below link: Ways to improve performance: http://windowshelp.microsoft.com/Windows/en-US/help/95f70af6-edd6-4f2f-9f02-7d6bdf0190611033.mspx

    Thanks and Regards:

    Samhrutha G S - Microsoft Support.

    Visit our Microsoft Answers Feedback Forum and let us know what you think.

    1 person found this answer helpful.
    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-03-15T07:40:38+00:00

    In my case, I had the exact same set of Drivers not being able to be loaded. 

    My solution was : I found that the INF files pointing to these Driver Files and its dependencies - had a few paths that did not resolve. In short : paths were invalid and the driver files themselves are not present in these paths. This is because they were actually on a harddrive that I disconnected - so I reconnected it back (its not a bootable drive and doesnt not have MBR or any OS in it) and startup was back to normal (3 seconds).

    However, in your cases, you need to get Autoruns for Windowshttp://technet.microsoft.com/en-us/sysinternals/bb963902.aspx - it's a simple tool that exactly tells you what drivers are loaded at boottime in what order and where the files are. Then you have 2 options :

    • Fix the paths of the non-loaded drivers
    • Disable them if you don't need them (disabling important drivers like graphics card and harddisk and CDROM will FlusterCuck your machine up for good) so better -
    • Fix them by finding the missing files or -
    • Reinstalling them from their vendor again.

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2011-02-22T15:54:25+00:00

    I have exactly the same problem. After more than an hour on the web I have concluded that there are a lot of people out there with the same problem.Could you post the findings from running the steps outlined above. I might be able to save a lot of testing if I have some idea what the cause was. I think Microsoft should also look into this - with multiple people having the same problem

    Thanks

    Tom

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2012-02-05T23:55:53+00:00

    @ChandirasekarT: I tried Autoruns for Windows - I couldn't find NDProxy.SYS or anything like it in the list.  I did notice a few entries were highlighted in pink - seemingly because they didn't have a description or publisher listed.  Does it only list what has loaded?  I'm guessing that it won't show ndproxy.sys because it didn't load.

    0 comments