Re: Dim 8400 problems



As is often the case, the citations for stop codes on the Microsoft web site
prove useless. But here is one from uSoft that may actually help:

http://support.microsoft.com/kb/903251

Here is a thread that claims a rootkit infection:

http://icrontic.com/forum/showthread.php?t=50966

You can google for other possibilities.

But first, I would determine the manufacturer of the drive, then download and
run that manufacturer's diagnostic software. A failing hard drive can cause
all kinds of symptons. I would also download and run the MEMTEST-86 memory
diagnostics.

Unless you know that the hardware is 100% operational, you may be wasting your
time troubleshooting a phantom hardware problem.

.... Ben Myers

On Tue, 31 Jul 2007 14:55:03 -0500, Tom Simchak <not.today@xxxxxxxxxxxx> wrote:

OK, for the 1st time ever, today my box started acting up...in a big way.

It's a Dim 8400 running MCE w/1.5 gigs of RAM. PCI-X card.

When I came in this AM, it looked like the computer had shut itself down
overnight...I leave it on 24/7 during the week, and off on weekends.

I rebooted, and everything seemed OK for about 5 or 10 mins., when I got
the XP equivalent of the BSOD. I rebooted again...hard reboot because I
could not get out of the BSOD. Again, everything seemed OK, this time
for several hours. There was an error message, but it did not reference
any particular component or driver.

This afternoon, it did the same thing, although this time it had a
section entitled "Technical Information"

It made reference to the following:

*** STOP: 0x0000008e (0xc0000005, 0xbf1af979, 0x981896c, 0x00000000

*** ati3duag.dll - address BF1AF979 base at BF084000, datestamp 412ccba1

The physical memory was dumped.

At this point, I shut everything down, unplugged all the peripherals and
opened the case, and use about half a can of air on it. There was some
dust, but not all that much...no dust bunnies anywhere. The machine is
not on the floor, and the building is not all the dusty.

Put everything back together, and rebooted. Got what appeared to be the
same screen as the first one that made no reference to a component or
driver. I rebooted again, and here I am.

I know ATI is the video...is this a warning that the video card is about
to crap out? Or something else? Is the dust issue what was causing
this problem?

Comments, suggestions are welcome.

Thanks.

Tom S.
Houston, TX

(no, not Tom Scales in FL)
.



Relevant Pages

  • Dim 8400 problems
    ... PCI-X card. ... I rebooted again...hard reboot because I could not get out of the BSOD. ... but it did not reference any particular component or driver. ... There was some dust, but not all that much...no dust bunnies anywhere. ...
    (alt.sys.pc-clone.dell)
  • Re: Hard drive or file corruption problem???
    ... It could be a bad HDD but more likely just heat. ... Are the vents to the system fan free of dust or anything else that could ... Have to power down to reboot. ... My first thought on file corruption does not seem to be the ...
    (microsoft.public.windowsxp.general)
  • Re: Power Supply Cause of Crashes?
    ... >>login after a reboot. ... > end of a heat cycle, when ambient room temperature peaked. ... > up that power supply it wasn't particularly full of dust either. ...
    (comp.os.linux.hardware)
  • Re: Power Supply Cause of Crashes?
    ... and now crashes every time I get to the ... >login after a reboot. ... end of a heat cycle, ... up that power supply it wasn't particularly full of dust either. ...
    (comp.os.linux.hardware)
  • RE: "Device not configured" after every command, crashing
    ... I had them clean off the dust and reboot the server, ... >To unsubscribe, send any mail to ...
    (freebsd-questions)