The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)

Hi All,
   My 2003 server system got rebooted by itself. I check the log and saw this error message " The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000) A dump was saved in: C:\WINDOWS\MEMORY.DMP."
   The hosting company explained that it cause by wrong setting of virtual memory. The configuration of virtual memory on my system is 1 GB on drive C: but at that moment I have only 400 MB disk space left on that drive. Ths hosting company said when the virtual memory is used up, the server will reboot. .....Is it true?
    Later on I free up the space on drive C and now I have 1.9 GB on C: and I changed the virtual memory settings on drive C to 512 MB and create another virtual memory file on drive D: at 1512 - 2024 MB. (drive D has 7 GB space) It should solve the virtuala memory problem. But still the system failure and reboot still occur after I changed the virtual memory setting. What else I should check? Please help?

Who is Participating?
CrazyOneConnect With a Mentor Commented:

General Causes of STOP 0x0000007F Errors

This article was previously published under Q137539
You may receive the following error message while running Windows:

This error message can occur if either of the following conditions exists:
Your computer has hardware or software problems (hardware failure is the most common cause).

You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).
The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:

Low-level hardware corruption, such as corrupt memory (RAM)
Mismatched memory modules
A malfunctioning motherboard
To determine an approximate cause, examine the parameters at the top of the STOP screen:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)

The most important parameter is the first one (0x0000000X) which may have several different values. The cause of this trap can vary, depending on the value of this parameter. All traps that cause a STOP 0x7F can be found in any Intel x86 microprocessor reference manual as they are specific to the x86 platform. Here are some of the most common ones:
   Values       Meaning
   ----------   --------------------
   0x00000000   Divide by Zero Error
   0x00000004   Overflow
   0x00000005   Bounds Check Fault
   0x00000006   Invalid Opcode
   0x00000008   Double Fault
Divide by Zero Error
A divide by zero is caused when a DIV instruction is executed and the divisor is 0. Memory corruption (or other hardware problems) or software failures can cause this.
The overflow instruction occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.
Bounds Check Fault
This 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.
Invalid Opcode
This fault 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.
Double Fault
A double fault occurs 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. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.
To resolve this issue, use the appropriate method:
If either software or hardware can cause a particular trap, a debug is required to determine which is the cause. If you suspect a hardware problem, try the following hardware troubleshooting steps:
Run diagnostic software and test the RAM in the computer. Replace any RAM reported as bad. Also, make sure all the RAM in the computer is the same speed.
Try removing or swapping out controllers, cards, or other peripherals.
Try a different motherboard on the computer.
If you are over clocking the speed of your processor, set it back to the speed at which it is designed to run.
Check with the hardware vendor for any updated hardware drivers or BIOS updates, or both.
For more information on processor faults, consult an Intel processor reference manual.
Test the RAM

If you can swap out the RAM with known good modules for testing first if you can't do that then test the machine with one RAM module at a time until you tested every module. Other wise run the the following RAM testers.

NOTE IF THIS DOESN'T FIND ANYTHING WRONG WITH THE RAM THIS DOESN'T MEAN THE RAM IS GOOD you would need to swap out the RAM with known good modules for testing. However if it does find something wrong then chances are the RAM is bad.

DocMemory PC RAM
Diagnostic Software



Windows Memory Diagnostic


I had the same problem and tried all of the above.
After a long search I found a solution.
I had AVG free anti-v and an other internet security pack.
By removing the avg, the problem was solved.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.