STOP errors at shut down / reboot on Windows XP [driver?]
HI All. Every Time I shut down or try to reboot, I get a STOP error (BSOD), and a writing memory dump. . . . This ONLY happens at shut down. The Windows report this error. . . suggests it may be a driver problem, but fails to identify WHICH driver is the cause.
HI All. Every Time I shut down or try to reboot, I get a STOP error (BSOD), and a "writing memory dump...".
This ONLY happens at shut down. The Windows "report this error..." suggests it may be a driver problem, but fails to identify WHICH driver is the cause.
Can anyone help?
Thanx
This ONLY happens at shut down. The Windows "report this error..." suggests it may be a driver problem, but fails to identify WHICH driver is the cause.
Can anyone help?
Thanx
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
While it's doing the save dump does it specify the .exe/.dll/.sys file that is causing this to occur or does it save only a quick dump and reboot too fast for you to note anything ?!?
If so then adjust your shutdown options to pause on the BSOD so you can take notes then perhaps we can better figure out what's causing this to occur.
Another think you can do is to look at the Event Viewer,
Click on the Start button, then Run then type the following:
eventvwr.msc and press ok.
Now click on the System log and look for an entry called Save Dump and read off the error codes and addresses. This may provide even more info.
If so then adjust your shutdown options to pause on the BSOD so you can take notes then perhaps we can better figure out what's causing this to occur.
Another think you can do is to look at the Event Viewer,
Click on the Start button, then Run then type the following:
eventvwr.msc and press ok.
Now click on the System log and look for an entry called Save Dump and read off the error codes and addresses. This may provide even more info.
No. It just says STOP error, and a bunch of memoery addresses. No VXD/DLL/EXE is given.
The Event Viewer shows this:
Save Dump
Quote:The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x00000099, 0x00014c97, 0x00000000, 0x00000000). A dump was saved in: C:\WINNT\Minidump\Mini121303-02.dmp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The Event Viewer shows this:
Save Dump
Quote:The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x00000099, 0x00014c97, 0x00000000, 0x00000000). A dump was saved in: C:\WINNT\Minidump\Mini121303-02.dmp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This is the EXACT STOP error I get:
STOP: 0x0000007F (0x0000000D,0x00000000,0x00000000,0x0000000)
I checked out the links you gave me, and here is what I found:
STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
Quote: 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.
Also, I have checked my ram chip (by trying my other ram chips) and the problem is NOT memory related. I get the stop error regardless of which memory chip is installed.
Can anyone please help?
Please Note: The stop error ONLY occurs when I shut down or reboot. I do NOT get the message at boot time or when I use the computer!!!
Also Note: This seems to be a Windows driver problem. This problem DOES NOT EXIST on Linux
If anmyone has any feedback, please do not hesitate as help is much appreciated : D
STOP: 0x0000007F (0x0000000D,0x00000000,0x00000000,0x0000000)
I checked out the links you gave me, and here is what I found:
STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
Quote: 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.
Also, I have checked my ram chip (by trying my other ram chips) and the problem is NOT memory related. I get the stop error regardless of which memory chip is installed.
Can anyone please help?
Please Note: The stop error ONLY occurs when I shut down or reboot. I do NOT get the message at boot time or when I use the computer!!!
Also Note: This seems to be a Windows driver problem. This problem DOES NOT EXIST on Linux
If anmyone has any feedback, please do not hesitate as help is much appreciated : D
