 |
|
|
|
Next: SOS PROBLEMA FLOPPY DRIVE
|
| Author |
Message |
External
Since: May 14, 2004
Posts: 3
|
(Msg. 1) Posted: Tue Oct 26, 2004 1:32 pm
Post subject: Random lockups, Win2000 & XP
Archived from groups: alt>comp>hardware (more info?)
|
|
|
'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 |
|
| Back to top |
|
 | |
External
Since: Jul 13, 2004
Posts: 144
|
(Msg. 2) Posted: Tue Oct 26, 2004 8:09 pm
Post subject: Re: Random lockups, Win2000 & XP [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Kenneth wrote:
> '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
How old is her HD???<!-- ~MESSAGE_AFTER~ --> |
|
| Back to top |
|
| |
External
Since: May 14, 2004
Posts: 3
|
(Msg. 3) Posted: Tue Oct 26, 2004 8:09 pm
Post subject: Re: Random lockups, Win2000 & XP [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Ken wrote:
> Kenneth wrote:
>
>> '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
>
>
>
> How old is her HD???
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<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Random lockups, Win2000 & XP |
|
| Back to top |
|
| |
External
Since: Jan 03, 2004
Posts: 7693
|
(Msg. 4) Posted: Tue Oct 26, 2004 8:18 pm
Post subject: Re: Random lockups, Win2000 & XP [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Tue, 26 Oct 2004 12:32:00 -0500, Kenneth
<kennethNOSPAM DeleteThis @pardue.com> wrote:
>'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
Try replacing as many drivers as possible, and see these:
<a style='text-decoration: underline;' href="http://search.microsoft.com/search/results.aspx?qu=MULTIPLE_IRP_COMPLETE_REQUESTS" target="_blank">http://search.microsoft.com/search/results.aspx?qu=MULTIPLE_IRP_COMPLE...REQUEST</a><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Random lockups, Win2000 & XP |
|
| Back to top |
|
| |
External
Since: Jul 13, 2004
Posts: 144
|
(Msg. 5) Posted: Tue Oct 26, 2004 8:19 pm
Post subject: Re: Random lockups, Win2000 & XP [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Kenneth wrote:
> Ken wrote:
>
>> Kenneth wrote:
>>
>>> '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
>>
>>
>>
>>
>> How old is her HD???
>
>
> 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
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.<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Random lockups, Win2000 & XP |
|
| Back to top |
|
| |
External
Since: Jul 03, 2004
Posts: 321
|
(Msg. 6) Posted: Wed Oct 27, 2004 9:12 am
Post subject: Re: Random lockups, Win2000 & XP [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
"Kenneth" <kennethNOSPAM DeleteThis @pardue.com> wrote in message
news:10nt2hi6nijjm23@corp.supernews.com...
> '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
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<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Random lockups, Win2000 & XP |
|
| Back to top |
|
| |
External
Since: Nov 14, 2004
Posts: 1
|
(Msg. 7) Posted: Sun Nov 14, 2004 2:32 pm
Post subject: Re: Random lockups, Win2000 & XP [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
|
|
| Back to top |
|
| |
| Related Topics: | Win2000 and adding more SDRAM - I have a PC which has a Win2000 OS. It currently works with two DIMMs of 256 and 128MBs. It has an on-board VGA device using 8MB of this memory. If I use a 512MB DIMM the PC typically boots up as normal and runs for a period of time before crashing or...
SATA fails to format in Win2000 - Hi all, just bought a Maxtor DiamondMax Plus10 200GB SATA but I can not get it to work in Windows 2000 in my system. My computer system conatins the following: MB : ABIT KT7-RAID HDD : one (1) 20GB HDD, three (3) 200GB HDD, one (1) CDROM The RAID..
A7V-E lockups - I've seen lots of posts about A7V-e lockups, usually with Duron CPU and GeForce2 video card. Some people even suggested that it had something to do with the video card. Has anybody figured why it's happening ? I did not see any post about someone who..
How to diagnose lockups - I have a new PC that intermittently locks up when I'm using it. Sometimes it'll be after just a couple of minutes, sometimes I'll have it running for hours, but it's locking up every couple of days and I don't know what to do about it. There's no..
system lockups when viewing Flash content on the web? - Basically my Windows 2000 system on an Abit KT7a Motherboard locks up several times a day whilst viewing flash content (e.g banners on websites). The time it crashes is fairly random. I think now it has been traced to a GFX card driver problem (ruled.. |
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
