Stop errors

B

BlastOButter42

Hi. I'm running Windows XP SP2 on a Dell laptop with 504 MB RAM and a
1.5 GHz processor. For the past, oh, week or two, I've been getting
Stop errors. I'd had a similar problem a while ago that went away, so
I haven't done anything about this for a little while, but it's
starting to piss me off a lot. I haven't written down any of the codes
at the bottom (I will when it happens again), but the message at the
top is usually "BAD_POOL_HEADER", "BAD_POOL_CALLER" or
"PAGED_FAULT_IN_NONPAGED_AREA". I downloaded a Windows Update today
that mentioned Stop errors (http://support.microsoft.com/kb/936357/en-
us), but it seems to have done nothing for my computer. Can anyone
help me resolve this, or else tell me what might help me identify the
problem?
 
R

Ron Martell

BlastOButter42 said:
Hi. I'm running Windows XP SP2 on a Dell laptop with 504 MB RAM and a
1.5 GHz processor. For the past, oh, week or two, I've been getting
Stop errors. I'd had a similar problem a while ago that went away, so
I haven't done anything about this for a little while, but it's
starting to piss me off a lot. I haven't written down any of the codes
at the bottom (I will when it happens again), but the message at the
top is usually "BAD_POOL_HEADER", "BAD_POOL_CALLER" or
"PAGED_FAULT_IN_NONPAGED_AREA". I downloaded a Windows Update today
that mentioned Stop errors (http://support.microsoft.com/kb/936357/en-
us), but it seems to have done nothing for my computer. Can anyone
help me resolve this, or else tell me what might help me identify the
problem?
Click to expand...

In addition to the name of the error we also need the rest of the
error details from the message, specifically the STOP code, all 4 of
the parameter values, and any file or module names mentioned in the
message.

Device driver issues are a common cause of your "BAD_POOL_HEADER" and
"BAD_POOL_CALLER" errors but there are a number of other factors that
can cause these as well. With "PAGED_FAULT_IN_NONPAGED_AREA" a
possible RAM defect would be a prime suspect but again there are many
other possible causes.

The detailed data from these errors could help to more precisely
identify the actual culprits involved.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
B

BlastOButter42

In addition to the name of the error we also need the rest of the
error details from the message, specifically the STOP code, all 4 of
the parameter values, and any file or module names mentioned in the
message.

Device driver issues are a common cause of your "BAD_POOL_HEADER" and
"BAD_POOL_CALLER" errors but there are a number of other factors that
can cause these as well. With "PAGED_FAULT_IN_NONPAGED_AREA" a
possible RAM defect would be a prime suspect but again there are many
other possible causes.

The detailed data from these errors could help to more precisely
identify the actual culprits involved.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Servicehttp://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
Click to expand...

So far since I posted that message I've had 4 stop errors, of which
i've
managed to write down two. The first didn't give a message at the top
(i.e.
"BAD_POOL_HEADER" etc.) but under technical information it said:
*** STOP: 0x0000007E (0xC0000005,0xAA2F29AA,0xF8905BA4,0xF89058A0)

*** klif.xyx - Address AA2F29AA base at AA2DE000, DateStamp
44d9b0b4


The next one was "BAD_POOL_CALLER":
Technical information:
*** STOPL 0x000000C2 (0x00000007,0x00000CD4,0x0063006F,0xE23D3960)

I'll post any more that I get.
 
B

BlastOButter42

So far since I posted that message I've had 4 stop errors, of which
i've
managed to write down two. The first didn't give a message at the top
(i.e.
"BAD_POOL_HEADER" etc.) but under technical information it said:
*** STOP: 0x0000007E (0xC0000005,0xAA2F29AA,0xF8905BA4,0xF89058A0)

*** klif.xyx - Address AA2F29AA base at AA2DE000, DateStamp
44d9b0b4

The next one was "BAD_POOL_CALLER":
Technical information:
*** STOPL 0x000000C2 (0x00000007,0x00000CD4,0x0063006F,0xE23D3960)

I'll post any more that I get.
Click to expand...

sorry, it's "klif.sys" not "klif.xyx"
 
B

BlastOButter42

So far since I posted that message I've had 4stoperrors, of which
i've
managed to write down two. The first didn't give a message at the top
(i.e.
"BAD_POOL_HEADER" etc.) but under technical information it said:
***STOP: 0x0000007E (0xC0000005,0xAA2F29AA,0xF8905BA4,0xF89058A0)

*** klif.xyx - Address AA2F29AA base at AA2DE000, DateStamp
44d9b0b4

The next one was "BAD_POOL_CALLER":
Technical information:
*** STOPL 0x000000C2 (0x00000007,0x00000CD4,0x0063006F,0xE23D3960)

I'll post any more that I get.
Click to expand...
 
B

BlastOButter42

So far since I posted that message I've had 4 stop errors, of which
i've
managed to write down two. The first didn't give a message at the top
(i.e.
"BAD_POOL_HEADER" etc.) but under technical information it said:
*** STOP: 0x0000007E (0xC0000005,0xAA2F29AA,0xF8905BA4,0xF89058A0)

*** klif.xyx - Address AA2F29AA base at AA2DE000, DateStamp
44d9b0b4

The next one was "BAD_POOL_CALLER":
Technical information:
*** STOPL 0x000000C2 (0x00000007,0x00000CD4,0x0063006F,0xE23D3960)

I'll post any more that I get.
Click to expand...

Thanks to everyone who's helped so far. I've got a couple more:

This one also didn't provide a message at the top, but the technical
information was:
*** STOP: 0x0000008E (0xC0000005,0x8062A464,0xA84C8340,0x00000000)

The next one said:
*** STOP: 0x00000024 (0x001902FE,0xA7E35504,0xA7E35200,0xF8274C16)
*** Ntfs.sys - Address F8274C16 base at F8250000, DateStamp
45cc56a7)

And the next:
*** STOP: 0x0000008E (0xC0000005,0xBF808408,0xA8702004,0x00000000)
*** win32k.sys - Address BF808408 base at BF800000,
DateStamp45f013f6

And the next:
*** STOP: 0x0000008E (0xC0000005,0x80544AF3, 0xA7E6AA14,0x00000000)

And the next:
The message at the top was "IRQL_NOT_LESS_OR_EQUAL" and the technical
information was:
*** STOP: 0x0000000A (0x006B007E,0x000000FF,0x00000000,0x80531D36)
 
R

Ron Martell

Thanks to everyone who's helped so far. I've got a couple more:

This one also didn't provide a message at the top, but the technical
information was:
*** STOP: 0x0000008E (0xC0000005,0x8062A464,0xA84C8340,0x00000000)

The next one said:
*** STOP: 0x00000024 (0x001902FE,0xA7E35504,0xA7E35200,0xF8274C16)
*** Ntfs.sys - Address F8274C16 base at F8250000, DateStamp
45cc56a7)

And the next:
*** STOP: 0x0000008E (0xC0000005,0xBF808408,0xA8702004,0x00000000)
*** win32k.sys - Address BF808408 base at BF800000,
DateStamp45f013f6

And the next:
*** STOP: 0x0000008E (0xC0000005,0x80544AF3, 0xA7E6AA14,0x00000000)

And the next:
The message at the top was "IRQL_NOT_LESS_OR_EQUAL" and the technical
information was:
*** STOP: 0x0000000A (0x006B007E,0x000000FF,0x00000000,0x80531D36)
Click to expand...

Okay, now we have 3 instances of the same STOP code (STOP: 0x0000008E)
which have occurred at 3 different memory addresses per parameter 2 of
error message.

In my experience the old adage that "software errors are consistent,
hardware errors are variable" may be applicable here so I would
suggest that you look first for a hardware related cause such as

1. Overheating. Make certain that the inside of the computer case is
free from any buildups of dust or fuzz (computers are dust magnets).
If there is any clean it with compressed air. You can buy this in
cans at any good electronics or computer supply store. Make certain
that all of the internal fans (there may be several of these) are
properly secured and are spinning freely. Check with your
computer/motherboard manufacturer for any temperature monitoring
utility for your computer and install it. Make sure that the audibile
or at least visual alarm functions are activated for temperature and
fan speed problems.

2. Defective RAM. Download one of the following free memory testing
utilities and run it for an extended period (e.g. overnight) to check
out the RAM in your machine:
DocMemory http://www.simmtester.com
Windows Memory Diagnostic http://oca.microsoft.com/en/windiag.asp
Memtest86: http://www.memtest.org


One final point. One of your STOP 0x8e errors identified win32k.sys
as the source file. There is a special note on the Microsoft web
site for this error regarding win32k.sys:

"If the problem is associated with Win32k.sys, the source of the error
might be a third-party remote control program. If such software is
installed, the service can be removed by starting the system using the
Recovery Console and deleting the offending system service file."
http://msdn2.microsoft.com/en-us/library/ms794023.aspx

Good luck



Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
B

BlastOButter42

Okay, now we have 3 instances of the sameSTOPcode (STOP: 0x0000008E)
which have occurred at 3 different memory addresses per parameter 2 oferrormessage.

In my experience the old adage that "software errors are consistent,
hardware errors are variable" may be applicable here so I would
suggest that you look first for a hardware related cause such as

1. Overheating. Make certain that the inside of the computer case is
free from any buildups of dust or fuzz (computers are dust magnets).
If there is any clean it with compressed air. You can buy this in
cans at any good electronics or computer supply store. Make certain
that all of the internal fans (there may be several of these) are
properly secured and are spinning freely. Check with your
computer/motherboard manufacturer for any temperature monitoring
utility for your computer and install it. Make sure that the audibile
or at least visual alarm functions are activated for temperature and
fan speed problems.

2. Defective RAM. Download one of the following free memory testing
utilities and run it for an extended period (e.g. overnight) to check
out the RAM in your machine:
DocMemory http://www.simmtester.com
Windows Memory Diagnostic http://oca.microsoft.com/en/windiag.asp
Memtest86: http://www.memtest.org

One final point. One of yourSTOP0x8e errors identified win32k.sys
as the source file. There is a special note on the Microsoft web
site for thiserrorregarding win32k.sys:

"If the problem is associated with Win32k.sys, the source of theerror
might be a third-party remote control program. If such software is
installed, the service can be removed by starting the system using the
Recovery Console and deleting the offending system service file."http://msdn2.microsoft.com/en-us/library/ms794023.aspx

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Servicehttp://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
Click to expand...

Thanks. This computer has an auto-off mechanism if the temperature
gets too high, so heat probably isn't the source.
I'll run the memory test tonight and give the results.
As a matter of fact the other day my friend did install a program
called Logmein which allows him to control my computer (I assume
that's what is meant by a remote-control program); he did a system
restore, which removed the program, and that stop error occurred
either that evening or the next evening.

Also, here's 7 more errors:

"BAD_POOL_HEADER"
Technical information:
*** STOP: 0x00000019 (0x00000020,0xE1D8F648,0xE1d8F690,0x0C090201)

Technical information:
*** STOP: 0x0000008E (0xC0000005,0x80544306,0xA88D1A10,0x00000000)

Technical information:
*** STOP: 0x0000008E (0xC0000005,0x80621AE9,0xA857307C,0x000000000)

Technical information:
*** STOP: 0x0000008E (0xC0000005,0x8054401D,0xA8D6E2BC,0x00000000)

"BAD_POOL_HEADER"
Technical information:
*** STOP: 0x00000019 (0x00000020,0x00700026,0x00700CA6,0x0D909885)

Technical information:
*** STOP: 0x0000008E (0xC0000005,0x80620BEB,0xA9D3AB80,0x00000000)

Technical information:
*** STOP: 0x00000024 (0x001902FE,0xA97F133C,0xA97F1038,0x80544AF3)
 
B

BlastOButter42

Thanks. This computer has an auto-off mechanism if the temperature
gets too high, so heat probably isn't the source.
I'll run the memory test tonight and give the results.
As a matter of fact the other day my friend did install a program
called Logmein which allows him to control my computer (I assume
that's what is meant by a remote-control program); he did a system
restore, which removed the program, and thatstoperror occurred
either that evening or the next evening.

Also, here's 7 more errors:

"BAD_POOL_HEADER"
Technical information:
***STOP: 0x00000019 (0x00000020,0xE1D8F648,0xE1d8F690,0x0C090201)

Technical information:
***STOP: 0x0000008E (0xC0000005,0x80544306,0xA88D1A10,0x00000000)

Technical information:
***STOP: 0x0000008E (0xC0000005,0x80621AE9,0xA857307C,0x000000000)

Technical information:
***STOP: 0x0000008E (0xC0000005,0x8054401D,0xA8D6E2BC,0x00000000)

"BAD_POOL_HEADER"
Technical information:
***STOP: 0x00000019 (0x00000020,0x00700026,0x00700CA6,0x0D909885)

Technical information:
***STOP: 0x0000008E (0xC0000005,0x80620BEB,0xA9D3AB80,0x00000000)

Technical information:
***STOP: 0x00000024 (0x001902FE,0xA97F133C,0xA97F1038,0x80544AF3)
Click to expand...

I ran Windows Memory Diagnostic (extended) test last night and it
turned up nothing.
Since the win32k.sys only showed up once, is it safe to assume that's
not the real source of the problem? If not, could you give me a little
more detail about using the recovery console to remove it?

Also, here's some more:
Technical information:
*** STOP: 0x0000000A (0x006B0130,0x000000FF,0x00000001,0x80531030)

Technical information:
*** STOP: 0x000000C2 (0x00000007,0x00000CD4,0x000000B8,0xE1BE4238)

Technical information:
*** STOP: 0x000000C2 (0x00000007,0x000000CD4,0x00320043,0xE1Bf2998)

Technical information:
*** STOP: 0x00000024 (0x001902FE,0xA8E891C8,0xA8E88EC4,0xF8239FF3)
* Ntfs.sys - Address F8239FF3 base at F8210000, DateStamp
45cc56a7

Technical information:
*** STOP: 0x0000000A (0x0000000C,0x000000FF,0x00000000,0x80531D36)

Technical information:
*** STOP: 0x0000008E (0xC0000005,0x80620CF9,0xA88299FC,0x00000000)

Technical information:
*** STOP: 0x00000019 (0x00000020,0xE23DE1B8,0xE23DE350,0x0C330437)

Technical information:
*** STOP: 0x0000008E (0xC0000005,0x8062A464,0xA90B6850,0x00000000)
 
R

Ron Martell

BlastOButter42 said:
I ran Windows Memory Diagnostic (extended) test last night and it
turned up nothing.
Since the win32k.sys only showed up once, is it safe to assume that's
not the real source of the problem? If not, could you give me a little
more detail about using the recovery console to remove it?
Click to expand...

Wn32k.sys is an essential component of Windows XP and removing it
would render your system unusable. It is a virtual certainty that
your problem is not with Win32k.sys. Something else on your system is
causing Win32k.sys to malfunction, triggering the error reports.

All of the information you have provided only tends to reinforce my
conviction that there is a hardware related cause for this problem

Download one of these memory testing utilities and run it to check for
possible memory errors that the Windows Memory Diagnostic may have
missed. These memory testing utilities are not infallible and
sometimes one program will pick up an error that another program will
miss.
DocMemory http://www.simmtester.com
Memtest86: http://www.memtest.org

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
B

BlastOButter42

Wn32k.sys is an essential component of Windows XP and removing it
would render your system unusable. It is a virtual certainty that
your problem is not with Win32k.sys. Something else on your system is
causing Win32k.sys to malfunction, triggering the error reports.

All of the information you have provided only tends to reinforce my
conviction that there is a hardware related cause for this problem

Download one of these memory testing utilities and run it to check for
possible memory errors that the Windows Memory Diagnostic may have
missed. These memory testing utilities are not infallible and
sometimes one program will pick up an error that another program will
miss.
DocMemory http://www.simmtester.com
Memtest86: http://www.memtest.org

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Servicehttp://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
Click to expand...

I wasn't able to run the DocMemory test, but I ran a memory test from
a Ubuntu live CD that did 3 passes and found nothing. I'll try running
the Memtest86.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Windows XP Sp3 Stop Errors 10
BSOD - Stop Errors 13
Frequent BSOD errors on laptop/notebook PC 2
Erasing data from harddrive 17
Virtual Memory too low 4
Plz Help for the Really BSOD: blue screen of death<---not a usual 2
Multiple Machines getting STOP 7A 2
Stop 7F and instable system 3

Top