RE: Getting rid of error prompt

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Evan (yeah_at_right.com)
Date: 09/15/04


Date: Wed, 15 Sep 2004 13:11:01 -0700

A quick search on Google for 'how to disable windows
debugger' turned up this:
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;188296

>-----Original Message-----
>I run a gaming server and every time someoen crashes the
>server (I CANNOT PREVENT THIS OR CHANGE THE PROGRAM NOT
>TO DO THIS) windows gives me and error:
>memory cannot be read at "random number" or something
>then click OK to terminate or CANCEL to debug
>I don't mind the error, in fact I don't care that it
>crashes, BUT I do hate this message because I am not at
>my computer most of the time and I cannot click OK to
>terminate. This is a problem because when the server
>crashes another program restarts the server program, but
>it can't do that if I haven't clicked "OK"
>my question is: Is there a way to make Windows
>automatically terminate instead of giving me the option
>to debug (so it terminates by itself without a message)?
>.
>



Relevant Pages

  • Re: Frontpage 2003 crashes when applying DWT
    ... - that means you just need to publish to a DBW to run the updates, then publish changes back to the server ... For the crashes, have you tried the usual repairs in the sequence below: ... In Windows Explorer Find and delete all FP Temp Files ... To find the best Newsgroup for FrontPage support see: ...
    (microsoft.public.frontpage.client)
  • Re: NTVDM Error Message
    ... Choose 'Close' to terminate the application." ... Troubleshooting NTVDM and WOW Startup Errorshttp://support.microsoft.com/kb/q220155/ ... Microsoft Windows NT Server 4.0, Terminal Server Edition, ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Getting rid of error prompt
    ... >>server (I CANNOT PREVENT THIS OR CHANGE THE PROGRAM NOT ... >>then click OK to terminate or CANCEL to debug ... >>crashes, BUT I do hate this message because I am not at ... >>to debug? ...
    (microsoft.public.windowsxp.general)
  • Re: Program crashes in msvcrt.dll
    ... It is not necessary for the development machine to be the same os-version as ... and look at the call stack when it crashes. ... > Windows 2003 Server or Windows 2000 Server. ...
    (microsoft.public.vstudio.development)
  • Re: Program crashes in msvcrt.dll
    ... Server machine, the crashes do not occur. ... The call stack points to USER32 and MSVCRT. ... the USER32 DLL is trying to display a Windows ...
    (microsoft.public.vstudio.development)