- Right-click My Computer on the desktop if using the classic Windows start menu (otherwise, right-click My Computer on the start menu)
- Click Properties
- In System Properties, go to the Advanced tab
- Click Error Reporting
- Click Disable error reporting
- It's optional whether you want to be informed of critical Windows errors
- Click Ok > "Ok out of system properties," and this should disable the error reporting
Listening to: Madonna - Don't Tell Me
Don't even talk to me about those windows XP error messages. I'm doing some programming in SDL. You remember, the one with the pretty diagrams. Anyway, whenever I run it, I get that stupid Windows XP error message. Of course, when I step through the code, to see what is actually causing the problem, it doesn't crash. Sorry, i know you can't help. I'm just venting.
ReplyDeleteIt sounds like a timing / thread thing. Usually you get this sort of thing when debugging because then the program has enough time to finish vs. just running it and it crashing all the time.
ReplyDeleteI don't know. SDL doesn't really deal too much with threads. just kind of sends out signal X, processes signal X. sends out signal Y, processes signal Y. It's not very concurrent at all.
ReplyDeleteIs there a purpose to those error reporting messages? Does microsoft (or whoever) actually do anything with the information they receive?
ReplyDeleteWho has access to error report data
ReplyDeleteMicrosoft employees, contractors and vendors who have a business need to use the error report data are provided access. If the error report indicates that a third-party product is involved, Microsoft may send the data to the vendor of that product, who may in turn send the data to sub-vendors and partners.
Taken from:
http://oca.microsoft.com/en/dcp20.asp
If the sw crashes, it allows them to figure out just where, and fix the problem. Some errors just can't be found in the lab.
ReplyDeleteLike, this error only happens 1 / 1000000 hours of operation (on average) or that if you have sw A and B and C and it's a tuesday, the error happens...
There are some things that the sw people blame on the hardware, others on timing. Other sw people just try to make their programs better, but we're only human. ;-)
registry settings
ReplyDelete