ntbtlog - very big, with lot of 'did not load driver'...Pls help!!!!

Page 2 of 2 FirstFirst 12

  1. Posts : 290
    Windows 7 Home Premium 64bit
       #11

    Try running SFC SFC /SCANNOW Command - System File Checker

    Run it three times, booting between each run.
      My Computer


  2. Posts : 15
    Windows Home Premium 64-bit
       #12

    Probably the original poster has gotten his solution or given up. But having just gone through this myself, I want to post a reply just in case someone has this problem again in future.

    So you get this c:\windows\nbtlog.txt file by repeatedly pressing F8 while booting and then selecting to produce a boot log.

    nbtlog.txt is concatenated each time a log is produced.

    1. So the first thing to do is separate out the old junk by renaming the current nbtlog.txt already there. (For example, nbtlog_upto_2013-01-10.txt)

    2. Re-boot to produce a fresh new log.

    3. You'll probably see most of those "did not load driver" messages are gone. There should be just a few left, for hardware you don't have or duplicate load attempts where an earlier load succeeded.

    4. IF you want to proceed to steps 5 & 6 it is a good idea to run a backup first. (At least create a Windows System Restore Point.)

    5. Optional. Run Driversweeper, looking for drivers for stuff you know you don't have. (You have a laptop, so you won't have updated your video card or network card, but possibly you'll find Dell installed extra drivers.)

    6. Optional. Run CCleaner to clean up your registry.

    7. Rename the current nbtlog.txt again.

    8. Reboot with boot logging enabled and check your new nbtlog.txt.

    9. You'll probably see most of those "did not load driver" messages are gone. There should be just a few left, for hardware you don't have. You might also see them where the driver was loaded earlier. If it is just a few, don't worry about them. (I get this for vga.sys, NDProxy.SYS (4 times), srv.sys.)

    10. If you did steps 5 & 6 and still have a lot of "did not load" messages, post each one in a reply here. What they are for and whether they were previously loaded is probably important to figuring out why they are there.


    If you look through your old renamed nbtlog.txt you'll see the various windows versions/service packs and the time stamp before each concatenated log. A couple date to a month before I got my computer. The others, I suspect they have to do with updates to drivers, software installations, and old safe boots.

    I have a Dell too (Dell XPS 9000 desktop aka Dell Studio 435T), and I too had a whack of those messages. Maybe doing boot-logging automatically during update re-boots is a Dell-specific default? I can see where it would be handy if something went wrong with an update, but it does mean a lot of junk builds up over time.
    Last edited by Keith2468; 10 Jan 2013 at 15:10.
      My Computer


  3. Posts : 1
    MS Windows 7 Ultimate x86, Version 6.1 SP1
       #13

    OS Login Lag


    I had this issue several times in the past on several machines. I agree with Mr ...Indain...'s Post and only have this to add..

    If all above posts did not help, try this;
    !!If there are high-winds, do not do this, wait until weather calms! (static can cause unseen damages)


    • Go to a local mom & pop Electronics Store, or Radio Shack should suffice.
    • Open your machine case, find the cables leading to your hard disk following from the main-board.
    • Normally, there is a tag on each cable inside laptop computers. ID the type of cable and ask the clerk for a replacement or to test the cables to see if they just needed a tighter hug on the ports.


    I have no idea why windows or Co-Linux wouldn't already have standards for detecting this issue but in each incident I had with OS login lags, the ratio, 'problem with cable' to 'virtual problem' is 4>5-1>5.

    I am not sure if this extra bit helps however, on machines I had been asked to fix, Vista 32bit on Gateway & Dell systems were the only computers I encountered which had a malware problem that directly corrupted the login causing a lag, following as you stated, "rebooting several times might for a few moments circumvent."
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:58.
Find Us