So I tested my regfix with my new crashing software. My regfix doesn't affect the way "xxx has encountered an error and needs to close" works at all.
I did some more searching and the correct settings are found under gpedit.msc, computer configuration, administrative templates, system, error reporting, display error notification, set to disabled.
This tested is for windows XP SP3 only.
This will cause the process for a crashed app to terminate so you can automate a restart instead of sitting there waiting for a user to click "don't send"
Topic: need to simulate a windows system hard error (Read 1631 times)
I'm looking for utility that will generate a windows system hard error in windows XP 32-bit.
(I also can develop in VB6 if anyone knows of a technique to generate the error.)
It needs to be a reproducible effect that generates the message "xxxx.exe has encountered an error and needs to close".
I'm trying to monitor mining processes that seems to crash every few days or so, and I want to detect when the process terminates so I can automate their restart.
The problem is the process doesn't terminate until I click "Don't send error report" so the monitoring software doesn't see the process as failed.
I found a regfix to disable the errors, but I can't test it properly without being able to simulate the error in the first place.
Thanks
I'm not sure about VB syntax, but in C(I also can develop in VB6 if anyone knows of a technique to generate the error.)
It needs to be a reproducible effect that generates the message "xxxx.exe has encountered an error and needs to close".
I'm trying to monitor mining processes that seems to crash every few days or so, and I want to detect when the process terminates so I can automate their restart.
The problem is the process doesn't terminate until I click "Don't send error report" so the monitoring software doesn't see the process as failed.
I found a regfix to disable the errors, but I can't test it properly without being able to simulate the error in the first place.
Thanks
char * p = 0;
*p = 1;
will give you C5 exception.
To close Windows Error Reporting (WER) window pragmatically, you need to search for werfault.exe process, look at the parent process to make sure it belongs to the process you are trying to monitor and kill it. For examples, look at my akbash watchdog code:
https://bitcointalksearch.org/topic/akbash-1012-open-source-cgminer-watchdog-remote-monitoring-emails-http-76208
Messing up a pointer. That did it! Thanks for the tip. I have it crashing nicely in vb6.
I will check out your software when I have some time. It looks interesting.
I'm looking for utility that will generate a windows system hard error in windows XP 32-bit.
(I also can develop in VB6 if anyone knows of a technique to generate the error.)
It needs to be a reproducible effect that generates the message "xxxx.exe has encountered an error and needs to close".
I'm trying to monitor mining processes that seems to crash every few days or so, and I want to detect when the process terminates so I can automate their restart.
The problem is the process doesn't terminate until I click "Don't send error report" so the monitoring software doesn't see the process as failed.
I found a regfix to disable the errors, but I can't test it properly without being able to simulate the error in the first place.
Thanks
(I also can develop in VB6 if anyone knows of a technique to generate the error.)
It needs to be a reproducible effect that generates the message "xxxx.exe has encountered an error and needs to close".
I'm trying to monitor mining processes that seems to crash every few days or so, and I want to detect when the process terminates so I can automate their restart.
The problem is the process doesn't terminate until I click "Don't send error report" so the monitoring software doesn't see the process as failed.
I found a regfix to disable the errors, but I can't test it properly without being able to simulate the error in the first place.
Thanks
Jump to: