none
"Host Process for Windows Services has stopped working" after Windows 7 install

    Question

  • I created a new partition on my main HD that has Windows server 2008 installed on it for Windows 7. While in the Windows server 2008 operating system I installed Windows 7 onto the new partition. While it installed it steup different .tmp files into my temporary files folder that have not gone away and that continue to be created. The error "Host Process for Windows Services has stopped working" pop-ups right at startup and I can't get rid of it even by closing all the windows as they will recur. 


    Here is a copy from Problem Reports and Solutions:

    __________________________________________________________________________________________________________

    Product
    Host Process for Windows Services

    Problem
    Stopped working

    Date
    1/9/2009 9:49 PM

    Status
    Report Sent

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: svchost.exe
    Application Version: 6.0.6001.18000
    Application Timestamp: 48034a4c
    Fault Module Name: svchost.exe
    Fault Module Version: 6.0.6001.18000
    Fault Module Timestamp: 48034a4c
    Exception Code: c0000005
    Exception Offset: 00001b16
    OS Version: 6.0.6001.2.1.0.272.7
    Locale ID: 1033
    Additional Information 1: fd00
    Additional Information 2: ea6f5fe8924aaa756324d57f87834160
    Additional Information 3: fd00
    Additional Information 4: ea6f5fe8924aaa756324d57f87834160

    Extra information about the problem
    Bucket ID: 722971172
    _____________________________________________________________________________

    Various random .tmp files include:

    ~DF1CB.tmp
    BN116F.tmp
    BNC034.tmp
    rdlD383.tmp

    samedi 10 janvier 2009 21:51

Réponses

  • So Windows 7 is installed in a different volume, and Win2008 is having a service crash issue. They really don't seem to be all that related, as Windows 7 was not installed in your Win2008 drive and can't be running while 2008 is running. :-/

    Anyways, at this point your only option is the debugging piece we and others spoke about earlier.


    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    vendredi 23 janvier 2009 06:31

Toutes les réponses

  • Is there nothing in your event viewer?

    Maybe there is a eventID or something.

    dimanche 11 janvier 2009 20:06
  • Rob Jager said:

    Is there nothing in your event viewer?

    Maybe there is a eventID or something.


    Yes. It simply shows svchost.exe errors: 

    "Faulting application svchost.exe, version 6.0.6001.18000, time stamp 0x48034a4c, faulting module svchost.exe, version 6.0.6001.18000, time stamp 0x48034a4c, exception code 0xc0000005, fault offset 0x00001b16, process id 0x698, application start time 0x01c9750a54983da5."

    Please help.
    mardi 13 janvier 2009 03:24
  • Please help.

    samedi 17 janvier 2009 07:38
  • BUMP
    dimanche 18 janvier 2009 08:17
  • help

    lundi 19 janvier 2009 02:35
  • How come no one helps here?
    mardi 20 janvier 2009 04:04
  • Sir, people do try to help, but it might just be that someone that does know how to help with this problem has not seen this thread yet.
    For help with Server 2008, you might want to try the Windows Server forum: http://social.technet.microsoft.com/Forums/en-US/category/windowsserver/ .
    mardi 20 janvier 2009 04:15
  • The reason you have no answer is because it is not possible to diagnose this issue with this data. We'd need to have a debugger attached or have your actual memory dump files. The OS has already uploaded this crash info automatically so simply check every so often to see if a fix has been reported back. SVCHOST is a generic service host, it is getting an access violation - but that is all I can cull from this data you have. Without a stack trace, the modules, etc... what is displayed here is not helpful. All that goo gets sent to us.

    When I get into the office tomorrow I'll see if your bucket ID here has anything useful in our bug database, but please don't expect too much - these are the risks of running beta software.
    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    mardi 20 janvier 2009 04:58
  • Ned Pyle [MSFT] said:

    The reason you have no answer is because it is not possible to diagnose this issue with this data. We'd need to have a debugger attached or have your actual memory dump files. The OS has already uploaded this crash info automatically so simply check every so often to see if a fix has been reported back. SVCHOST is a generic service host, it is getting an access violation - but that is all I can cull from this data you have. Without a stack trace, the modules, etc... what is displayed here is not helpful. All that goo gets sent to us.

    When I get into the office tomorrow I'll see if your bucket ID here has anything useful in our bug database, but please don't expect too much - these are the risks of running beta software.


    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team



    Thank you very much for the response. How can I get the debugger or the memory dump files to post them here?
    mardi 20 janvier 2009 10:56
  • svchost.exe is a process that hosts other processes within it.  You can use the free program Process Explorer to see what's running in that particular svchost.exe process.  It's available here:  Link

    You'll have to figure out which of the several svchost.exe processes are causing this (by PID number).  Once you determine this, you can hover your mouse over that svchost.exe process to see what processes are running inside of it.

    As for the crash dump, here's a link that'll get you started:  How to read the small memory dump files that Windows creates for debugging

    - John
    mercredi 21 janvier 2009 00:09
    Auteur de réponse
  • I just noticed something very important here - your SVCHOST.EXE process has a version of 6.0.6001.18000. That is the version of SVCHOST.EXE for Vista Sp1/Win2008 Sp1 - not Windows 7.

    I wonder if you have some application that brought it's own copy of this file? Please search your entire Win7 hard drive as an adminstrator for SVCHOST.EXE. You should only have copies in (assuming your path is C:):

    C:\Windows\System32
    C:\Windows\SysWOW64
    C:\Windows\winsxs\amd64_microsoft-windows-services-svchost_31bf3856ad364e35_6.1.7000.0_none_8243db50f9a2c3fb
    C:\Windows\winsxs\x86_microsoft-windows-services-svchost_31bf3856ad364e35_6.1.7000.0_none_26253fcd414552c5

    Please check the version of that file on all 4 locations - it should be: 6.1.7000.0. If it's not, let me know. Also, if you find any copies elsewhere, tell me that too (and what their version(s) are).

    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    mercredi 21 janvier 2009 00:25
  • Ummm... and it says your OS version is Vista Sp1/Windows Server 2008 Sp1... you sure you're having a Windows 7 issue? It's possible the error is reporting incorrectly for OS I suppose...
    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    mercredi 21 janvier 2009 00:33
  • Ned Pyle [MSFT] said:

    I just noticed something very important here - your SVCHOST.EXE process has a version of 6.0.6001.18000. That is the version of SVCHOST.EXE for Vista Sp1/Win2008 Sp1 - not Windows 7.

    I wonder if you have some application that brought it's own copy of this file? Please search your entire Win7 hard drive as an adminstrator for SVCHOST.EXE. You should only have copies in (assuming your path is C:):

    C:\Windows\System32
    C:\Windows\SysWOW64
    C:\Windows\winsxs\amd64_microsoft-windows-services-svchost_31bf3856ad364e35_6.1.7000.0_none_8243db50f9a2c3fb
    C:\Windows\winsxs\x86_microsoft-windows-services-svchost_31bf3856ad364e35_6.1.7000.0_none_26253fcd414552c5

    Please check the version of that file on all 4 locations - it should be: 6.1.7000.0. If it's not, let me know. Also, if you find any copies elsewhere, tell me that too (and what their version(s) are).


    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team



    Yes those are the only location of svchost.exe on the Windows 7 harddrive and they are 6.1.7000.0. The problem started when I was installing Windows 7 beta through the Windows 2008 OS onto a seperate parition and the setup created .tmp files in my Server 2008 OS folders. These files are the ones that give me problems and continue to recur after being deleted.
    mercredi 21 janvier 2009 07:19
  • I'm afraid I now have absolutely no idea what you are talking about then... you said that you have an error popping up, and you posted that in the Windows 7 forum. Are you saying that there is nothing bad happening with your Windows 7 OS at all? :-/
    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    jeudi 22 janvier 2009 05:47
  • Ned Pyle [MSFT] said:

    I'm afraid I now have absolutely no idea what you are talking about then... you said that you have an error popping up, and you posted that in the Windows 7 forum. Are you saying that there is nothing bad happening with your Windows 7 OS at all? :-/


    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team



    Let me reiterate this. The Windows 7 installation was the "cause" for the problem I am having. The Server 2008 OS essentially did not have anything to do with the problem per se. Why would I post this elsewhere??
    jeudi 22 janvier 2009 10:38
  • So Windows 7 is installed in a different volume, and Win2008 is having a service crash issue. They really don't seem to be all that related, as Windows 7 was not installed in your Win2008 drive and can't be running while 2008 is running. :-/

    Anyways, at this point your only option is the debugging piece we and others spoke about earlier.


    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    vendredi 23 janvier 2009 06:31