Does Event Viewer offer any clues as to the cause?
Make a note of the precise text of any error message. You can access Event Viewer by selecting Start, Administrative Tools, Event Viewer. When researching the meaning of the error, information regarding Event ID: and Source Description are important.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default...&Product=winxp
Post details of the Error Report and we can see if we are able to help.
Another approach!
How to Perform a Clean Boot in Windows XP
http://support.microsoft.com/default...&Product=winxp
HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP
http://support.microsoft.com/default...&Product=winxp
~~~~~~
Hope this helps.
Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
(E-Mail Removed)
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~
<(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Fllwg prob & search for it's cause/solution persisting for 4 months:
> I have taken the trouble to be thorough in its descr - TIA 4 ur
> patience & lack of conclusion-jumping before considering all.
>
> Box: Compac notebook Presario 2195US/Ath2500/512/40g no ntwk connect
> & usually no peripherals attached. XP Home, has SP1 & most all recent
> updates.
>
> There is no worm or virus or spyware detectable on this box
> (double-checked with update NAV & Spyhunter, filesearches etc.).
> Earlier post mis-named a process (wrongly from my memory) associated
> with a worm. There are no other observed operating problems beyond
> the fact that it's, well, Windows<g>.
>
> Here is the actual name (abbreviation) list of drivers that load 2+
> minutes after boot is completed, obtained from bootvis by extending
> its dump duration to 3 minutes, in their order of very late loading.
> The rest of the table columns (delay times etc.) are omitted here but
> available if needed. They have to be read & hand-typed because the
> table utility doesn't copy/paste. All major functions are device
> controllers except the first 2 which are CREATE:
>
> Process Driver
> ------------ ---------
>
> explorer.exe(1364) wdmaud
> explorer.exe(1364) ks
> ONETOUCH.EXE(1480) wdmaud
> explorer.exe(1364) wdmaud
> explorer.exe(1364) ks
> explorer.exe(1364) ks
> explorer.exe(1364) wdmaud
> ONETOUCH.EXE(1480) wdmaud
> ONETOUCH.EXE(1480) DkbFltr
> ONETOUCH.EXE(1480) DkbFltr
> winlogon.exe(616) wdmaud
> ONETOUCH.EXE(1480) DkbFltr
> ONETOUCH.EXE(1480) DkbFltr
> ONETOUCH.EXE(1480) DkbFltr
> imapi.exe(1304) imapi
> imapi.exe(1304) MxlW2k
> imapi.exe(1304) Cdr4_xp
> imapi.exe(1304) pfc
> imapi.exe(1304) redbook
> imapi.exe(1304) pwd_2k
> imapi.exe(1304) Cdralw2k
>
> Some relate to necessary navigation & connectivity processes
> (explorer.exe etc.), some are audio functionality, some are just HP
> One-Touch frills etc. You can start any app, but can't do
> anything in it until these load. Of course the logon .wav & audio &
> ntwk tray icons only appear & sound after the delay. Power & touchpad
> icons are unaffected & appear immediately after boot.
>
> Actual boot to GUI cmplts in 30 sec or so.
>
> - did all the usuals: unnecessary startups/any ntwkgn
> startups all cleared in CP & msconfig etc.;
> - some these drvr or refs to them do appear in the prefetch file, but
> appear not to prefetch quickly enough(?) - tried deleting/recreating
> the P/F file too;
> - bootvis has no effect on optimizing these post-boot drvrs, & is not
> a cause since it predates my obtaining it in misguided attempt to fix
> this & resulted in no change; FWIW it *did* shorten actual boot time;
> - unclear whether these are all supposed to be "post-boot" loads & not
> loaded during boot?;
> - the Defrag GUI does indicate a 2nd large immoveable sector halfway
> up the HD, which may or may not hold these drvrs & may or may not be
> relevant; boot defrag flag to "Y" doesn't move it;
> - the 40g HD is 3/4 empty;
> - in *one* instance, before normal defrag, these drvrs were suddenly
> loading within 2-3 sec after boot; after defrag, back to the 2 min
> delay, may or may not be a fluke;
> - no HD activity/seeking is indicated during the 2-min post-boot
> delay, until they begin loading;
> - if one waits at the login screen for the same 2+ minutes before
> loggin on, these drvrs will load immediately (within 2-3 sec) after
> boot, possibly indicating there is some sort of prefetch call for
> them.
>
> Others beginning to rpt same prob on other NG's w/o
> response. Appears no info anywhere on the 'net or in MSKB etc. -
> help?
>
> Email CC much appreciated,
Similar Threads
