Difference between revisions of "Breakpoint Encountered (0x80000003) at address 0x77F767CD"
(setting font and breaks) |
(removing broken link to original faq) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
This error can happen when a task has exceeded the maximum CPU time or maximum disk space. The abort message causes the science application to call DebugBreak() which causes the 0x80000003 error code.<br> | This error can happen when a task has exceeded the maximum CPU time or maximum disk space. The abort message causes the science application to call DebugBreak() which causes the 0x80000003 error code.<br> | ||
<br> | <br> | ||
| Line 16: | Line 15: | ||
|- | |- | ||
| Jorden | | Jorden | ||
| − | | | + | | 480 |
| 12-01-2009 | | 12-01-2009 | ||
|- | |- | ||
|} | |} | ||
| − | |||
Latest revision as of 21:34, 16 August 2017
This error can happen when a task has exceeded the maximum CPU time or maximum disk space. The abort message causes the science application to call DebugBreak() which causes the 0x80000003 error code.
The idea being that if either the memory or CPU usage has been exceeded then there is either a memory leak or an infinite loop that the project needs to debug. DebugBreak() will cause the Windows Debugger to start up and dump a stack trace of the stuff the application was doing, and report it back to the project.
Most of the times you come across this error message however is when you have manually aborted one or more tasks that were running at that time.
Aborting running tasks will also call the DebugBreak() routine and do the same dump of information as before.
Address 0x77F767CD
This doesn't mean you have a hardware error. The address 0x77F767CD is the user breakpoint set in ntdll.dll which will allow for a graceful break of your software, rather than dump you to a blue screen of death.
| Original writer | Original FAQ | Date |
|---|---|---|
| Jorden | 480 | 12-01-2009 |
