Blue Screen Crash Error Code 0x000000F4

Blue Screen Crash Error Code 0x000000F4 (0x00000003, 0x81EBA020, 0x81EBA194,
0x805F9F88) This occurred while sitting idle. Had just completed disk
defragmenter

I am sure this is a Hardware problem, if you cannot find someone locally to
have a good look inside then try this group:

microsoft.public.windowsxp.hardware

You'll have much better odds on getting a respons that you can handle.


Tony. . .


"rlmarr" <rlmarr@discussions.microsoft.com> wrote in message
news:C584B4CF-AAD2-4A49-8C51-249B75851E01@microsoft.com...
> Blue Screen Crash Error Code 0x000000F4 (0x00000003, 0x81EBA020,
0x81EBA194,
> 0x805F9F88) This occurred while sitting idle. Had just completed disk
> defragmenter

Everyone here has said it many times. You have major problems with this
machine. Failing hardware, or my suspicion, a major infestation. In either
case, pull the files off that you say you need, and start OVER. From
scratch. Rebuild it from "bare metal" - boot from the XP CD, delete all
existing partitions on the HD, and then create new ones and format them.

Meanwhile, before you even try to rebuild, copy all your critical data files
off onto something. Floppy, USB device, CD - whatever you prefer to use.
Then start over. Please.

--
Charlie.
http://msmvps.com/xperts64


"rlmarr" <rlmarr@discussions.microsoft.com> wrote in message
news:C584B4CF-AAD2-4A49-8C51-249B75851E01@microsoft.com...
> Blue Screen Crash Error Code 0x000000F4 (0x00000003, 0x81EBA020,
> 0x81EBA194,
> 0x805F9F88) This occurred while sitting idle. Had just completed disk
> defragmenter

It may well be hardware (he's already admitted to an unseated memory DIMM),
but I actually think he's got a serious infestation of some sort.

In any case, I agree. Find someone local that knows what they're doing and
get some help.

This is NOT the place for this.

Charlie.

"Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
news:e95S02yCHHA.5068@TK2MSFTNGP02.phx.gbl...
>I am sure this is a Hardware problem, if you cannot find someone locally to
> have a good look inside then try this group:
>
> microsoft.public.windowsxp.hardware
>
> You'll have much better odds on getting a respons that you can handle.
>
>
> Tony. . .
>
>
> "rlmarr" <rlmarr@discussions.microsoft.com> wrote in message
> news:C584B4CF-AAD2-4A49-8C51-249B75851E01@microsoft.com...
>> Blue Screen Crash Error Code 0x000000F4 (0x00000003, 0x81EBA020,
> 0x81EBA194,
>> 0x805F9F88) This occurred while sitting idle. Had just completed disk
>> defragmenter
>
>

Hmm, you may well be right. Honestly, though - by the sound of it, I've
scrapped better gear than that, even in the good old days when I couldn't
afford it.


Tony. . .

"Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message
news:O1BVO8zCHHA.4060@TK2MSFTNGP03.phx.gbl...
> It may well be hardware (he's already admitted to an unseated memory
DIMM),
> but I actually think he's got a serious infestation of some sort.
>
> In any case, I agree. Find someone local that knows what they're doing and
> get some help.
>
> This is NOT the place for this.
>
> Charlie.
>
> "Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
> news:e95S02yCHHA.5068@TK2MSFTNGP02.phx.gbl...
> >I am sure this is a Hardware problem, if you cannot find someone locally
to
> > have a good look inside then try this group:
> >
> > microsoft.public.windowsxp.hardware
> >
> > You'll have much better odds on getting a respons that you can handle.
> >
> >
> > Tony. . .
> >
> >
> > "rlmarr" <rlmarr@discussions.microsoft.com> wrote in message
> > news:C584B4CF-AAD2-4A49-8C51-249B75851E01@microsoft.com...
> >> Blue Screen Crash Error Code 0x000000F4 (0x00000003, 0x81EBA020,
> > 0x81EBA194,
> >> 0x805F9F88) This occurred while sitting idle. Had just completed disk
> >> defragmenter
> >
> >
>
>