From: jj4public@vfemail.net   
      
   On Mon, 03 Nov 2014 00:43:51 +0100, Bj��m wrote:   
   > The disk has 64 Kb in bad sectors, but I see from a photo I took of a   
   > blue screen of the disk in November 2009 that it had exactly that   
   > number back then too. And it is just in the last year the booting   
   > problem occured. No such thing before that whatsoever. Bad sectors are   
   > marked by the OS arn't they?   
      
   Yes. The marker would prevent the OS from storing data in bad or unstable   
   sectors.   
      
   > I trace the problem looking at entries in the Event viewer (Se Shadows   
   > post below) to Security Center and the Service Control Manager (in   
   > System). What could this Manager be doing specifically?? The system   
   > crashes almost each and every time this run after booting. No other   
   > entries after it ever listed, so it got to be it. There is an error   
   > message (translated below to english):   
      
   The Service Control Mnager (SCM) is a functionality that's part of the OS   
   kernel (deep in the core). It's the one that oversees and handles all of the   
   services in the system. The files required by the services are likely the   
   ones that caused the error, not the SCM. i.e. one or more are stored in   
   unstable sectors where if read, sometimes good data is returned and   
   sometimes it's errorneous. If the kernel files are actually stored in   
   unstable sectors, your system would crash sooner and more frequently than   
   you think.   
      
   > "The service Automatic LiveUpdate-planning can not be started because   
   > of the following error:   
   > The System can not find the stated path."   
   >   
   > (in original norwegian:   
   > Tjenesten Automatisk LiveUpdate-planlegging kan ikke startes på grunn   
   > av følgende feil:   
   > Systemet finner ikke angitt bane. )   
   >   
   > So obviously there is a path-problem. Bu how can I correct this?   
   > And what is Service Control Manager?   
   > Note that this has probably nothing to do with the Virus Program, it   
   > is Live-Update for the XP-updates.   
   >   
   > Bjørn   
      
   The error detail may be stored in a separate text file as *.LOG or *log*.txt   
   in C:\WINDOWS, the system temporary directory, or the user temporary   
   directory. If you can't find it, use Microsoft Process Monitor to monitor   
   file error events, then start/restart that service to reproduce the problem.   
      
   The missing file may be found in the software installer package. You'll need   
   to manually extract the contents to get the file. Try using 7-Zip or   
   Universal Extractor. If both can't extract them, you'll have to reinstall   
   the whole product.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)