Something within Opera is triggering a system reboot when I close the browser.

[xboxist]

In the past few weeks, my computer has been instantly rebooting -- sometimes -- when I close out of Opera. The reboot is instantaneous and without error messages or prompt.

Prior to this starting to happen, my computer has suffered ZERO rebooting problems/issues since I have owned it (about 3 years now).

I scan regularly for spyware/viral problems.

I upgraded to the newest version of Opera and the random reboots still happened.

I closed Opera again today and one of the famed reboots occurred. Then I remembered about the Event Viewer and decided to check it out. Here are my findings:

Event ID: 1001

Source: Save Dump

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0xf7831d70, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini101205-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Ok, well at least I have some blueprint to work from. I followed that link to a Microsoft help window, and it was pretty vague. It sent the bug report to Microsoft, and I may or may not get a response to the matter. Apparently they don't really do much if it's an isolated incident.

So any ideas from here?

Thanks in advance for input.

 

[dphantom]

Try Event ID at this Link.

Event ID 1000 Source Save Dump also has some similar information.

The above link is a subscription.

 

[Smilin]

This might help. Be aware that it takes some pretty nutty circumstances to cause a double fault... basically an exception happens while an exception is being processed. A more likely cause would be hardware failure.

From the WinDbg helpfiles:

Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP
The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.

This could be either a bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system crash).


Parameters
The first parameter displayed on the blue screen specifies the trap number.

Here are some of the most common trap codes:

0x00000000, or Divide by Zero Error, is caused when a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems, or software failures can cause this error.
0x00000004, or Overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.
0x00000005, or Bounds Check Fault, is generated when the processor, while executing a BOUND instruction, finds the operand exceeds the specified limits. A BOUND instruction is used to ensure that a signed array index is within a certain range.
0x00000006, or Invalid Opcode, is generated when the processor attempts to execute an invalid instruction. This is generally caused when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this is hardware memory corruption.
0x00000008, or Double Fault, is when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
1. A kernel stack overflow. This occurs when a guard page is hit, and then the kernel tries to push a trap frame. Since there is no stack left, a stack overflow results, causing the double fault. If you suspect this has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
2. A hardware problem.

The less-common trap codes include:

0x00000001 ? A system-debugger call
0x00000003 ? A debugger breakpoint
0x00000007 ? A hardware coprocessor instruction with no coprocessor present
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

For other trap numbers, consult an Intel architecture manual.

Cause
Bug check 0x7F usually occurs after the installation of faulty or mismatched hardware (especially memory) or in the event that installed hardware fails.

A double fault can occur when the kernel stack overflows. This can happen if multiple drivers are attached to the same stack. For example, two file system filter drivers can be attached to the same stack and then the file system can recurse back in, overflowing the stack.