Random lockups, Win2000 & XP

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

'm having trouble figuring out what's wrong with a friend's computer.
Recently, without a change in hardware which had been running fine for
the better chunk of a year, her system started locking up. I've tried
putting in new memory, swapping video cards, and removing her ethernet
card... not least of which I've done fresh installs of both Windows XP
and Windows 2000. She continually gets the lockups. Some of the STOP
messages that I've run through google kinda seems to indicate a problem
with the RAM, but I've used two different kinds (one of which was new)
on two different OS's.

Some of the STOP messages below:

STOP 0x00000044 (0x816EE548, 0x81482428, 0x00000000, 0x00000000)
MULTIPLE_IRP_COMPLETE_REQUESTS

STOP 0x000000001 (0x000000B8, 0x0000000D, 0x00000001, 0xBFF8B584)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Address BFF8B584 base at BFF83000, DATESTAMP 3e89d599 - atapi.sys

STOP 0x0000000A (0x00000000, 0x00000002, 0x00000000, 0x8042DD4C)
IRQL_NOT_LESS_OR_EQUAL
Address 8042DD4c base at 80400000, DATESTAMP 3ee6c00z - ntoskrnl.exe

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0x812A3A20, 0x812A3A28)
BAD_POOL_CALLER

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0xE21C1720, 0xE21C1728)
BAD_POOL_CALLER

STOP: 0X0000004E (0X00000007, 0x00007D77, 0x00000001, 0x00000000)
PFN_LIST_CORRUPT

STOP: 0x000000C5 (0x00000000, 0x00000002, 0x00000001, 0x80468EZF)
A device driver has corrupted the executive memory pool.
Address 80468EZF base at 80400000, DATESTAMP 39760637 - ntoskrnl.exe

Any advice or a direction would be greatly appreciated.

Ken
 
Kenneth said:
'm having trouble figuring out what's wrong with a friend's computer.
Recently, without a change in hardware which had been running fine for
the better chunk of a year, her system started locking up. I've tried
putting in new memory, swapping video cards, and removing her ethernet
card... not least of which I've done fresh installs of both Windows XP
and Windows 2000. She continually gets the lockups. Some of the STOP
messages that I've run through google kinda seems to indicate a problem
with the RAM, but I've used two different kinds (one of which was new)
on two different OS's.

Some of the STOP messages below:

STOP 0x00000044 (0x816EE548, 0x81482428, 0x00000000, 0x00000000)
MULTIPLE_IRP_COMPLETE_REQUESTS

STOP 0x000000001 (0x000000B8, 0x0000000D, 0x00000001, 0xBFF8B584)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Address BFF8B584 base at BFF83000, DATESTAMP 3e89d599 - atapi.sys

STOP 0x0000000A (0x00000000, 0x00000002, 0x00000000, 0x8042DD4C)
IRQL_NOT_LESS_OR_EQUAL
Address 8042DD4c base at 80400000, DATESTAMP 3ee6c00z - ntoskrnl.exe

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0x812A3A20, 0x812A3A28)
BAD_POOL_CALLER

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0xE21C1720, 0xE21C1728)
BAD_POOL_CALLER

STOP: 0X0000004E (0X00000007, 0x00007D77, 0x00000001, 0x00000000)
PFN_LIST_CORRUPT

STOP: 0x000000C5 (0x00000000, 0x00000002, 0x00000001, 0x80468EZF)
A device driver has corrupted the executive memory pool.
Address 80468EZF base at 80400000, DATESTAMP 39760637 - ntoskrnl.exe

Any advice or a direction would be greatly appreciated.

Ken
Click to expand...


How old is her HD???
 
Ken said:
How old is her HD???
Click to expand...

Probably a year, year and a half or so. Maybe a little older. Does
that sound like the most likely culprit? Did a error check and it
reported no bytes in bad sectors.

Ken
 
'm having trouble figuring out what's wrong with a friend's computer.
Recently, without a change in hardware which had been running fine for
the better chunk of a year, her system started locking up. I've tried
putting in new memory, swapping video cards, and removing her ethernet
card... not least of which I've done fresh installs of both Windows XP
and Windows 2000. She continually gets the lockups. Some of the STOP
messages that I've run through google kinda seems to indicate a problem
with the RAM, but I've used two different kinds (one of which was new)
on two different OS's.

Some of the STOP messages below:

STOP 0x00000044 (0x816EE548, 0x81482428, 0x00000000, 0x00000000)
MULTIPLE_IRP_COMPLETE_REQUESTS

STOP 0x000000001 (0x000000B8, 0x0000000D, 0x00000001, 0xBFF8B584)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Address BFF8B584 base at BFF83000, DATESTAMP 3e89d599 - atapi.sys

STOP 0x0000000A (0x00000000, 0x00000002, 0x00000000, 0x8042DD4C)
IRQL_NOT_LESS_OR_EQUAL
Address 8042DD4c base at 80400000, DATESTAMP 3ee6c00z - ntoskrnl.exe

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0x812A3A20, 0x812A3A28)
BAD_POOL_CALLER

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0xE21C1720, 0xE21C1728)
BAD_POOL_CALLER

STOP: 0X0000004E (0X00000007, 0x00007D77, 0x00000001, 0x00000000)
PFN_LIST_CORRUPT

STOP: 0x000000C5 (0x00000000, 0x00000002, 0x00000001, 0x80468EZF)
A device driver has corrupted the executive memory pool.
Address 80468EZF base at 80400000, DATESTAMP 39760637 - ntoskrnl.exe

Any advice or a direction would be greatly appreciated.

Ken
Click to expand...

Try replacing as many drivers as possible, and see these:
http://search.microsoft.com/search/results.aspx?qu=MULTIPLE_IRP_COMPLETE_REQUESTS
 
Kenneth said:
Probably a year, year and a half or so. Maybe a little older. Does
that sound like the most likely culprit? Did a error check and it
reported no bytes in bad sectors.

Ken
Click to expand...

Most of the time error indications such as you received are RAM
problems, however you said you had tried different RAM. If you can
lower the FSB in CMOS and cause the system to run slower, you might try
that and see if your problems go away. If they don't, I would clone her
HD to another HD and see if that helps. I have seen several instances
where such problems were the HD. I guess it reads the data incorrectly
from the HD and once in RAM it sees the data as invalid.
 
Kenneth said:
'm having trouble figuring out what's wrong with a friend's computer.
Recently, without a change in hardware which had been running fine for the
better chunk of a year, her system started locking up. I've tried putting
in new memory, swapping video cards, and removing her ethernet card... not
least of which I've done fresh installs of both Windows XP and Windows
2000. She continually gets the lockups. Some of the STOP messages that
I've run through google kinda seems to indicate a problem with the RAM,
but I've used two different kinds (one of which was new) on two different
OS's.

Some of the STOP messages below:

STOP 0x00000044 (0x816EE548, 0x81482428, 0x00000000, 0x00000000)
MULTIPLE_IRP_COMPLETE_REQUESTS

STOP 0x000000001 (0x000000B8, 0x0000000D, 0x00000001, 0xBFF8B584)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Address BFF8B584 base at BFF83000, DATESTAMP 3e89d599 - atapi.sys

STOP 0x0000000A (0x00000000, 0x00000002, 0x00000000, 0x8042DD4C)
IRQL_NOT_LESS_OR_EQUAL
Address 8042DD4c base at 80400000, DATESTAMP 3ee6c00z - ntoskrnl.exe

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0x812A3A20, 0x812A3A28)
BAD_POOL_CALLER

STOP: 0x000000C2 (0x00000007, 0x00000B86, 0xE21C1720, 0xE21C1728)
BAD_POOL_CALLER

STOP: 0X0000004E (0X00000007, 0x00007D77, 0x00000001, 0x00000000)
PFN_LIST_CORRUPT

STOP: 0x000000C5 (0x00000000, 0x00000002, 0x00000001, 0x80468EZF)
A device driver has corrupted the executive memory pool.
Address 80468EZF base at 80400000, DATESTAMP 39760637 - ntoskrnl.exe

Any advice or a direction would be greatly appreciated.

Ken
Click to expand...

Other than dodgy ram (which you've effectively ruled out by trying new
modules with the same results), the next most likely cause for this sort of
trouble is a PSU that's on its way to the great power supply heaven in the
sky. Do you have another known good PSU that will supply enough power for
her system which you can use as a temporary test PSU?

PSUs are actually one of the most commonly failing bits of PC hardware
(right up there with hard disk drives in the unreliability stakes). Even if
the current PSU is fairly new, there's still a chance it cant meet the
demands of a system that's expecting to draw to much from it - with the same
general system instability as a result.

Paul
 
Could be due to loose connection. Unplug everything, blow dust out
with air hose at gas staton, reseat everything (particuarly ram) and
it might be ok.
 
Back
Top