Hi TMagic and Hatrick
After my last post, I did some searching and found the following info:
STOP: 0x0000007F (0x0000000D,0x00000000,0x00000000,0x0000000)
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:
* A condition that the kernel is not allowed to have or intercept (also known as a bound trap).
* Software problems.
* Hardware failures.
Interpreting the Message
This Stop message has four parameters:
1. Processor exception code.
2. This value is 0x00000000 (zero).
3. This value is 0x00000000 (zero).
4. This value is 0x00000000 (zero).
The first parameter is the most important and can have several different values, indicating different causes of this error. You can find all conditions that cause a Stop 0x7F in any x86 microprocessor reference manual because they are specific to the x86 platform. Here are some of the most common exception codes:
* 0x00000000, or a divide by zero error, occurs when a divide (DIV) instruction is run and the divisor is 0. Memory corruption, other hardware failures, or software problems can cause this message.
* 0x00000004, or Overflow, occurs when the processor carries out a call to an interrupt handler when the overflow (OF) flag is set.
* 0x00000005, or Bounds Check Fault, indicates that the processor, while carrying out a BOUND instruction, found that the operand exceeded the specified limits. BOUND instructions are used to ensure that a signed array index is within a certain range.
* 0x00000006, or Invalid Opcode, is generated when the processor attempts to run an invalid instruction. This typically occurs when the instruction pointer is corrupted due to a hardware memory problem and is pointing to a wrong location.
* 0x00000008, or Double Fault, indicates an exception while trying to call the handler for a prior exception. Normally, two exceptions can be handled serially, but there are certain exceptions (almost always caused by hardware problems) that cause the processor to signal a double fault.
Less common codes include:
* 0x00000001: A system-debugger call.
* 0x00000003: A debugger breakpoint.
* 0x0000000A: A corrupted Task State Segment.
* 0x0000000B: An access to a memory segment that was not present.
* 0x0000000C:An access to memory beyond the limits of a stack.
* 0x0000000D: An exception not covered by some other exception; a protection fault that pertains to access violations for applications.
Based on the info in the last 2 lines above ( * 0x0000000D: An exception not covered by some other exception; a protection fault that pertains to access violations for applications ), could this possibly be a one time freak event?
My specific reason for asking this question is that since installing Firefox Preloader (about a month ago per my last post) as a startup tray item, I have made no adjustments to the program settings and have clicked on that icon 30-40 times a day with absolutely no trouble till it generated the BSOD.
I am most interested in your thoughts on this matter and want to also restate that I have made no changes of any sort to anything in the system hardware or software since my last action around midnight Friday ( that was stopping the running of the Stanford Folding At Home program ). I did update ( per the auto-prompt from the program re an available definition update ) my anti-virus, but that was AFTER rebooting from the BSOD.
Will, per my last post, wait to hear from you before doing anything