The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    DEP shutting down Host Process for Windows Services!!!

    Discussion in 'Windows OS and Software' started by VietNinjaXTC, Apr 9, 2007.

  1. VietNinjaXTC

    VietNinjaXTC Notebook Geek

    Reputations:
    0
    Messages:
    89
    Likes Received:
    0
    Trophy Points:
    15
    **I'm not 100% sure if this is the right forum for this post...but mods please move it to where it's supposed to be if not here.**

    Here's my situation...

    Every so often (usually after my computer is sitting idle for a few hours) I get this popup message on my SZ160 + Vista Biz that says "Host Process for Windows Services has stopped and was closed." or something very close to that. When I click on the help icon in the sys tray it opens the Windows Help and tells me that the Data Execution Prevention closed the process. Theres no way to disable DEP on Vista that I've found...and I've read online that people haven't had any luck trying to disable DEP (boot up problems result).

    I was wondering if anyone has this issue in Vista (seems to be all versions of Vista...not just biz) or if anyone has a solution to it? It doesn't seem to disable any functionality that I can tell...but it's just annoying because it pops up all the time.

    Thanks in advance,
    Jeff
     
  2. skagen

    skagen Notebook Deity

    Reputations:
    278
    Messages:
    885
    Likes Received:
    0
    Trophy Points:
    30
    I cant remember the exact error message, but I think I have had something like this - after I deleted the history and temp files in my browser (IE7).
     
  3. jimc

    jimc Notebook Consultant

    Reputations:
    130
    Messages:
    269
    Likes Received:
    0
    Trophy Points:
    30
    have you looked in the event viewer?
     
  4. Jalf

    Jalf Comrade Santa

    Reputations:
    2,883
    Messages:
    3,468
    Likes Received:
    0
    Trophy Points:
    105
    One solution could be to simply find out which service causes the problem, and then ditch that.

    Properly written software shouldn't trigger DEP.
    If it does, you should (if possible), find alternative software that doesn't cause the problem.

    (At least, in a perfect world. I am aware that in the real work, that may not be possible. I've had to put a few apps under XP on my DEP whitelist because they'd otherwise trigger it)
     
  5. qhn

    qhn Notebook User

    Reputations:
    1,654
    Messages:
    5,955
    Likes Received:
    1
    Trophy Points:
    205
  6. gtsmike

    gtsmike Newbie

    Reputations:
    0
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    5
    i had this samething happen. the first time i ignored it but i could not use my fingerprint reader about the same time. the program ran but i could not get it to read the fingerprint to get on to anything. after reloading the software for the fingerprint it worked.

    then i got the host process error again. and again the fingerprint read would not work. so i turned off the protection that causes the problem and rebooted and now the fingerprint reader worked without reloading the program.

    so why would microsoft think that the fingerprint read software is mal-ware? hope this helps. i found the cmd statement to turn off the protection.
     
  7. shinji257

    shinji257 Notebook Deity

    Reputations:
    243
    Messages:
    1,041
    Likes Received:
    8
    Trophy Points:
    56
    The data execution protection stops a program when it tries to access memory outside of the range it is assigned. Sounds like the drivers are poorly written for your fingerprint reader.

    On a side note. I had this happen to Windows Explorer in XP where DEP closed it to "protect the system". I made sure to screenshot it. ;)