XP Pro System is hosed

On Jun 7, 2:12*pm, Pat <pat_whit...@hotmail.com> wrote:
> Well, new info: This afternoon I found a new BSOD: A process or thread
> crucial to system operation has unexpectedly exited or been
> terminated. STOP: 0x000000F4 (0x00000003, 0x88EA9410, 0x88EA9584,
> 0x805D11F8)
> Now, when I attempt to start this box, I just get non-stop, slow
> beeps, not even pixie boot. Methinks I have a dead MoBo, and this was
> the issue all along!

Well, after doing a little poking around about the beeps, I reseated
both the video card and the memory sticks (no easy feat with my
massive cooling tower over the CPU!), and the system booted right back
up with no problem. I've submitted an RMA for the video card - we'll
see if that makes a difference!

"Pat" <pat_whitted@hotmail.com> wrote in message
news:3eb2252d-2d35-4880-bc28-7d06414ad429@a9g2000prl.googlegroups.com...
On Jun 7, 2:12 pm, Pat <pat_whit...@hotmail.com> wrote:
> Well, new info: This afternoon I found a new BSOD: A process or thread
> crucial to system operation has unexpectedly exited or been
> terminated. STOP: 0x000000F4 (0x00000003, 0x88EA9410, 0x88EA9584,
> 0x805D11F8)
> Now, when I attempt to start this box, I just get non-stop, slow
> beeps, not even pixie boot. Methinks I have a dead MoBo, and this was
> the issue all along!

Well, after doing a little poking around about the beeps, I reseated
both the video card and the memory sticks (no easy feat with my
massive cooling tower over the CPU!), and the system booted right back
up with no problem. I've submitted an RMA for the video card - we'll
see if that makes a difference!

Do you think it may have been a poorly seated video card all along?

In article <3eb2252d-2d35-4880-bc28-7d06414ad429@a9g2000prl.googlegroups.com>, Pat <pat_whitted@hotmail.com> wrote:
>On Jun 7, 2:12=A0pm, Pat <pat_whit...@hotmail.com> wrote:
>> Well, new info: This afternoon I found a new BSOD: A process or thread
>> crucial to system operation has unexpectedly exited or been
>> terminated. STOP: 0x000000F4 (0x00000003, 0x88EA9410, 0x88EA9584,
>> 0x805D11F8)
>> Now, when I attempt to start this box, I just get non-stop, slow
>> beeps, not even pixie boot. Methinks I have a dead MoBo, and this was
>> the issue all along!
>
>Well, after doing a little poking around about the beeps, I reseated
>both the video card and the memory sticks (no easy feat with my
>massive cooling tower over the CPU!), and the system booted right back
>up with no problem. I've submitted an RMA for the video card - we'll
>see if that makes a difference!
Your massive cooling tower could be flexing the hell out of the motherboard
and causing the video card and ram to pop loose. I doubt it the video card.

> Do you think it may have been a poorly seated video card all along?

No, I had gone through and reseated it a few times along the way here.
MAYBE with the memory, since I hadn't touched it since installing it.

NEW INFO: Last night, after having the system running for a couple
hours with Twonky Media streaming media to my DLink, the system locked
up with a BSOD with a MEMORY_MANAGEMENT message, STOP 0x0000001A
(0x00041785, 0x00E00000, 0x00031F70, 0x00000000). After power-cycling
it, it came back up, acting as if nothing had happened. After about
another hour of streaming, it crapped out again, this time with an
"IRQL_NOT_LESS_OR_EQUAL" message. It did that 2 more times before the
night was over. There is a KB article about this, stating that "This
problem occurs because of a race condition in the memory manager.",
for which there is an update that I installed. We'll see what happens
next...

"Pat" <pat_whitted@hotmail.com> wrote in message
news:7a4fa70a-33ea-4845-b2a3-ff74d3b1da99@k30g2000hse.googlegroups.com...
>> Do you think it may have been a poorly seated video card all along?
>
> No, I had gone through and reseated it a few times along the way here.
> MAYBE with the memory, since I hadn't touched it since installing it.
>
> NEW INFO: Last night, after having the system running for a couple
> hours with Twonky Media streaming media to my DLink, the system locked
> up with a BSOD with a MEMORY_MANAGEMENT message, STOP 0x0000001A
> (0x00041785, 0x00E00000, 0x00031F70, 0x00000000). After power-cycling
> it, it came back up, acting as if nothing had happened. After about
> another hour of streaming, it crapped out again, this time with an
> "IRQL_NOT_LESS_OR_EQUAL" message. It did that 2 more times before the
> night was over. There is a KB article about this, stating that "This
> problem occurs because of a race condition in the memory manager.",
> for which there is an update that I installed. We'll see what happens
> next...

This thread has evolved far past the original post where SP3 was the only
suspect (still is, but much more new info). I suggest you start a new post
and try and summarize everything you've experienced in as few words as
possible in order to get some of the eyeballs back for more help.