Stop error 0x000008E, Help!

[Jared]

first, let me run down what I have tried...

Updated all drivers, Bios, motherboard etc, all critical
updates. deleted page file and tried resetting.

My Specs:
Windows XP Professional Build 2600
ATI 64 MB DDR RADEON 8500
1 5400 RPM HardDrive (40 GB)
1 100 GB HardDrive (100 GB)
2 512 DDR PC222 CAs2 Hi-Performence Mushkin Ram 2*2*2
Philips 20x10x40 CD-RW Drive
3com Ethernet 10/100 NIc Card
Creative Lab SoundsBlaster SB Live! Value
MSI Motherboard Via Kt266 Pro2 Onboard Raid (Not using)
(my Motherboards link:
http://www.msicomputer.com/product/detail_spec/product_det
ail.asp?model=K7T266_Pro2-RU)
AMD Athon XP 1900+ ~ 1.6 ghz

Description of Error:

Whenever I run applications like Virtual Dub, TMPEC, or
high processing programs. Or sometimes when I Just leave
the computer on.

Info on those programs: They are encoding programs for
converting divx --> Vcd etc or encoding into divx format
etc etc.

I get no file associated with it. just the standard blue
screen:

Windows has been shut down to avoid damaging your
computer, then it gives the messaging about, if this is
the first time you have seen this error, try restarting
your computer. If you have added any hardware etc etc.

Try disable catching in your BIOS etc etc (tried that
also).

Only Issue I can find on this is on MS website about
KMODE error on Install of XP, but I don't get it on
install, its just running my computer that I am getting
that stop error screen.

I hope I have been in depth enough to help!

Also, I have auto-logging on etc, but there is no log
file showing up for this..
~Jared
Webm...@rom-mania.com

[Jim Eshelman]

Jared wrote:
:: Only Issue I can find on this is on MS website about

:: KMODE error on Install of XP, but I don't get it on
:: install, its just running my computer that I am getting
:: that stop error screen.

You're right, that's all that's there explicitly referring to this. Usually
the 0x8E error, though, will name a file (such as a driver file) that is
giving a problem. That's a very good place to start. Besides that, the best
I can think of is to suggest the *generic* Stop Message troubleshooting list
on http://aumha.org/kbestop.htm:

1.. If you've recently added new hardware, remove it and retest.
2.. Run hardware diagnostics supplied by the manufacturer.
3.. Make sure device drivers and system BIOS are up-to-date.
4.. However, if you've installed new drivers just before the problem
appeared, try rolling them back to the older ones.
5.. Open the box and make sure all hardware is correctly installed, well
seated, and solidly connected.
6.. Confirm that all of your hardware is on the Hardware Compatibility
List. If some of it isn't, then pay particular attention to the non-HCL
hardware in your troubleshooting.
7.. Check for viruses.
8.. Examine the System Log and Application Log in Event Viewer for other
recent errors that might give further clues.
9.. Investigate recently added software.
10.. Examine (and try disabling) BIOS memory options such as caching or
shadowing.

--
Jim Eshelman MS-MVP
Windows Support Center: http://aumha.org
Forums: http://forum.aumha.org/

[Andre Vachon [MS]]

You don't say how much RAM you have. If you have at least 256MEG, turn on
driver verifer (using verifier.exe). This will enable a buch of
troubleshooting code in the kernel that will help isolate the faulting
component (bad driver, bad memory, etc).

BTW, Please click the "send error report" button. If there is a bad known
driver on your machine, you'll get an immediate answer back at to what it
was.

-Andre
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

"Jared" <webm...@rom-mania.com> wrote in message
news:1613301c22ae0$3e8acd40$36ef2ecf@tkmsftngxa12...

[Kelly]

"Andre Vachon [MS]" <and...@online.microsoft.com> wrote in
news:u1BPTu0KCHA.2552@tkmsftngp08:

Jared,

I have been troubleshooting system problems with similar although not
exactly the same setup you have. Two things about you setup and
symptoms. I have found that in 99% of the cases it boiled down to a ram
issue, or specifically, pairs of ram. Try removing one stick and see if
your problems go away. Check your bios settings as far as timings are
concerned. If the symptoms clear up, you may have to use more
conservative settings for your ram in order to get them to play nice. If
ram does not clear up the problem, then start looking at your installed
hardware / device drivers one at a time.

Post back and let us know how you are progressing...

Kelly