Generic process?

botheredbothered Manchester UK
edited January 2006 in Science & Tech
Hi all,
When I built my sons PC, after installing graphic drivers, I stsrted getting this error 'Generic host process for win32 failed'. I was told by a top SMer to 'install the .net framework as part of the Windows updates before installing the graphics drivers...? The latest ATi drivers requires the .net framework from Microsoft first'. I did this, and reinstalled graphics, and it seemed to go away for a few days, now it's back.
There is a fix from MS, that didn't fix it. I have installed newer graphics drivers. Research says - Change the internet time server, disable the windows imaging acquisition (sp) service (WIA). Tried all this and it makes no differance. The error comes up after booting about 50% of the time. When the error box is closed half the progs in the PC won't work. Internet doesn't work although I can put in the routers IP and get into its setup page, it's a wireless connection, clicking 'home' just gets us a 'server not found' error. Research also points to a scanner or printer problem as being the cause but the PC is connected to niether. The 50% of the time we don't get the error everything works just fine but we are having problems finding the cause.
Any suggestions guys?

Comments

  • botheredbothered Manchester UK
    edited January 2006
    After a few more hours trying to suss this I found it may be a program that's trying to access the net but can't. After turning a few startup progs off and countless reboots later I noticed two things. 1, it makes no differane which startup items I disable, 2, if I log in straight away I get the error, if I wait one minute I get no error. Could it be that the offending prog is trying to access the net before the wireless connection is established? If I don't wait the wireless connection icon shows disconnected for 20 seconds or so but if I do wait it is active as soon as the icon appears. Does this make any sense?
  • ShortyShorty Manchester, UK Icrontian
    edited January 2006
    If you are logging straight in.. then you are right.. it's trying to use the network :)

    Networking is literally one of the last processes to kick in and if you are logging straight in.. it's not got time to start the wireless part properly and hence the error.. absolutely as you thought I would say :D
  • shwaipshwaip bluffin' with my muffin Icrontian
    edited January 2006
    bothered wrote:
    After a few more hours trying to suss this I found it may be a program that's trying to access the net but can't. After turning a few startup progs off and countless reboots later I noticed two things. 1, it makes no differane which startup items I disable, 2, if I log in straight away I get the error, if I wait one minute I get no error. Could it be that the offending prog is trying to access the net before the wireless connection is established? If I don't wait the wireless connection icon shows disconnected for 20 seconds or so but if I do wait it is active as soon as the icon appears. Does this make any sense?

    I used to get the same error on my laptop when I was using the wireless network card instead of the wire. I never made a huge attempt to fix it, as I was planning to (and did) move to linux on my laptop.

    You could take a look at what programs are set to run at startup (via start->run->msconfig, and seeing if there's something that looks like it may be causing the problem.
  • botheredbothered Manchester UK
    edited January 2006
    bothered wrote:
    After turning a few startup progs off and countless reboots later I noticed two things. 1, it makes no differane which startup items I disable,
  • shwaipshwaip bluffin' with my muffin Icrontian
    edited January 2006
    indeed. perhaps it is time for my mid-day nap.

    That kind of implies (to me) that it may be a service automatically started by windows.
    Change the internet time server

    I know you said you tried this, but could you try disabling the automatic sync w/ an internet time server? Thats just a guess based on the 'change the time server' advice you found in research.
  • botheredbothered Manchester UK
    edited January 2006
    It really seems to be a timing problem At the login screen I just have to wait 20 seconds and it's all good. It's such a simple 'fix' that I think I'll just leave it, spent too long on it already.
    Thanks all.
Sign In or Register to comment.