From: Sh@dow.br   
      
   On Thu, 30 Oct 2014 17:57:50 +0100, Bjørn Sørheim   
    wrote:   
      
   >On Thu, 30 Oct 2014 12:36:24 -0200, Shadow  wrote:   
   >   
   >>On Thu, 30 Oct 2014 14:57:40 +0100, Bjørn Sørheim   
   >> wrote:   
   >>   
   >>>On Thu, 30 Oct 2014 11:55:35 +0200, Steve Hayes   
   >>> wrote:   
   >>>   
   >>>>On Thu, 30 Oct 2014 01:14:46 +0100, Bjørn Sørheim    
   >>>>wrote:   
   >>>>   
   >>>>>   
   >>>>>   
   >>>>>I got a booting problem on my Acer Xp-machine that I don't understand,   
   >>>>>and I have had for over half a  year. Which has led me to abandon the   
   >>>>>machine for most of the time, since it is almost impossible to get   
   >>>>>through.   
   >>>>>   
   >>>>>It may have something to to with the boot disk being almost full? It   
   >>>>>is a 200 Gb disk, and when the problem started it had maybe less than   
   >>>>>2Gb free, even 1Gb. The exact number, I'm not shure of. Currently I   
   >>>>>had about 10 Gb space when I last booted, and have been able to remove   
   >>>>>3 more since then.   
   >>>>   
   >>>>How much RAM does the machine have?   
   >>>>   
   >>>>I had a laptop with 250 Mb RAM, and there were some programs that   
   >>>>automatically updated themselves, becoming more bloated with each update,   
   so   
   >>>>that the machine ran slower and slower, and would take half and hour to   
   boot,   
   >>>>and almost as long to shut down, with much swapping to disk as it needed   
   more   
   >>>>memory.   
   >>>   
   >   
   >>>2Gb of RAM, so I don't think it is that. Something else.   
   >>   
   >>	That's a lot of ram. Probably not the problem.   
   >>	Try eventvwr.   
   >>	There should be an error in the log  with the approximate   
   >>timestamp of the crash.   
   >>	[]'s   
   >   
   >Thanks for the advice about eventvwr. Here is a dump of the events for   
   >Program and System.   
   >It's in norwegian, so here is a  translation of some probably unknown   
   >words:   
   >   
   >Dato = Date   
   >Tid = Time   
   >Kilde = Source   
   >Hendelse = Event   
   >Bruker = User   
   >Ingen = None   
   >Feil = Error   
   >   
   >My first try at booting after April 22 was October 12 at 15:25. You   
   >see that there is a timegap after the SecurityCenter/Service Control   
   >Manager-entries of either 10 minutes (which is checking the disk for   
   >consequence) or just a bit over a minute (when I opt to skip it).   
   >So is it the Service Control Manager which crashes (what is that?) or   
   >what can you possibly read out of this?   
   >   
   >Bjørn   
   >   
   >   
   >Events for ** Program:   
   >   
   >Type	Dato	Tid	Kilde	Kategori	Hendelse	Bruker   
   >Datamaskin   
   >Informasjon	12.10.2014	16:08:58	Winlogon	Ingen   
   >1001	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:58:34	gupdate	Ingen	0 I/T   
   >OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:57:20	SecurityCenter	Ingen   
   >1800	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:57:14	NIS	Ingen	35   
   >SYSTEM	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:57:13	NIS	Ingen	34   
   >SYSTEM	OEM-DATAM-2004B   
   >Feil	12.10.2014	15:57:12	PerfNet	Ingen	2004	I/T   
   >OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:57:10	gupdate	Ingen	0 I/T   
   >OEM-DATAM-2004B   
      
   	Fail after gupdate, which appears to be a Google update thing.   
   Perfnet error 2004 is "'impossible to open Server service...'".   
      
   >Informasjon	12.10.2014	15:57:07	Winlogon	Ingen   
   >1001	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:47:25	SecurityCenter	Ingen   
   >1800	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:47:08	NIS	Ingen	35   
   >SYSTEM	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:47:03	NIS	Ingen	34   
   >SYSTEM	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:46:58	gupdate	Ingen	0 I/T   
   >OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:45:37	SecurityCenter	Ingen   
   >1800	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:45:20	NIS	Ingen	35   
   >SYSTEM	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:45:17	NIS	Ingen	34   
   >SYSTEM	OEM-DATAM-2004B   
   >Feil	12.10.2014	15:45:17	PerfNet	Ingen	2004	I/T   
   >OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:45:15	gupdate	Ingen	0 I/T   
   >OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:45:11	Winlogon	Ingen   
   >1001	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:35:33	SecurityCenter	Ingen   
   >1800	I/T	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:35:16	NIS	Ingen	35   
   >SYSTEM	OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:35:14	NIS	Ingen	34   
   >SYSTEM	OEM-DATAM-2004B   
   >Feil	12.10.2014	15:35:14	PerfNet	Ingen	2004	I/T   
   >OEM-DATAM-2004B   
   >Informasjon	12.10.2014	15:35:10	gupdate	Ingen	0 I/T   
   >OEM-DATAM-2004B   
      
   Again. same error. gupdate followed by a network error.   
      
   	Try disabling the gupdate service. Might solve the problem.   
   	[]'s   
      
   (the wrapping made it hard to read)   
      
   --   
   Don't be evil - Google 2004   
   We have a new policy  - Google 2012   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)