I have a (customers) Compaq Presario 2200 (2267AP 1.5Ghz Celeron, 256 MB Ram Win XP Home SP2), which consistently suffers a 0x8e BSOD shortly after starting up. Most of the posts I was able to find on this error suggest it is a memory error or driver problem so I have pursued this line but with no success.
I have run various memory tests, including memtest, MS memory diagnostic, and Hp's online health check; none report any problems with the RAM.
On occassions the Microsoft Online Crash Analysis tool has kicked in. The reports from this indicate a problem with the video driver so I have followed the recommendations, installing the latest video driver from the HP website, and, when this didn't help, the latest driver from the Intel website. Also tried turning off hardware acceleration. problem remains.
I have updated any other drivers and bios that were available from the HP website. still no joy.
At this point I did a repair install (inplace upgrade) of windows, but on completing this process the problem remains.
Most recently, (its been a couple of days now!) I noticed that, during startup, one of the SVCHOST processes was using all of the available of CPU and a constantly increasing amount of storage. If left to its own devices the working set for the process climbs steadily to > 100,000kb and then the machine BSODs. If I kill the process the BSOD doesn't occur. So.... a memory leak??
Tasklist shows the SVCHOST is the one that runs a whole swag of the services (of course it is);
svchost.exe 1024 AudioSrv, CryptSvc, Dhcp, ERSvc,
helpsvc, lanmanserver, lanmanworkstation,
Netman, Nla, RasMan, Schedule, seclogon,
SENS, SharedAccess, ShellHWDetection,
srservice, TapiSrv, Themes, TrkWks, W32Time,
winmgmt, wscsvc, wuauserv, WZCSVC
It may be just a coincidence, but windows update seems to be implicated in this problem. If wuauclt is running at startup the bsod occurs. If I kill the svchost but then access the windows update website I see the same pattern of memory usage and then the bsod.
I've got about a 1000 minidumps from this error but don't really know what to do with them. I've tried following the directions in http://support.microsoft.com/kb/315271/EN-US/
but the output doesn't show an ExceptionAddress I could use with PSTAT. I would appreciate any advice or assistance with the minidumps if they'll help isolate the problem. (not sure how to attach one to the question for starters)
I guess I've run out of ideas so the points are there for any suggestions that resolve the problem (apart from the obvious, of a clean install, which is what I'm going to do next anyway)