It seems as though that the carb will need to be cleaned. You may luck out and only need to drop the bowl, clean that area, take the straw from a jet spray carb cleaner and work it up into the very center of the stem and spray. Of course, it is good to know that the fuel getting to the carb is clean and fresh. Should further cleaning be required, they can be a bit tricky to remove, clean and reassemble if you are questioning your mechanical ability. If you go further, watch closely how gaskets and links come off. There is a small jet that unscrews in that center stem and a tube that you shake/ push out to clean. Or new carbs are really quite affordable as well.

I have checked with the UW system for their testing info. Standard test includes: pH, lime requirement, organic matter, available phosphorous (P), and available potassium (K). The are additional tests (available for an additional fee) include: lead, soluble salts, physical analysis, boron, sulfur, manganese, zinc, heavy metals Am I okay with just the standard variety?

casi, Disk cloning uses a special software program such as Symantec's Norton Ghost to create an exact copy of one hard disk on a second drive. This does not involve copying files as such. Rather, the software creates an "image file" of the drive's contents which is then applied to a new hard drive, or stored elsewhere. See link provided. Here is a link that might be useful: Disk cloning

Here is the listing from whocrashed. I see that it refers to avast antivirus. When I initially tried to install my new IE* I believe that I had disabled Avast for 10 minutes. But I admit that I have forgotten to disingage it in all of my other actions. I will send this and perhaps I will have time to use your routine above to try uninstalling ie8 again with avast disabled and get back again. If I had any sense, I would have tried system restore. I haven't really done that much with this computer and it likely would have done the trick in the first place. System Information (local) -------------------------------------------------------------------------------- computer name: I4000 windows version: Windows XP Service Pack 3, 5.1, build: 2600 windows dir: C:\WINDOWS CPU: GenuineIntel Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz Intel586, level: 15 1 logical processors, active mask: 1 RAM: 1073143808 total VM: 2147352576, free: 2027573248 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Wed 8/29/2012 1:32:48 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini082812-05.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x18654) Bugcheck code: 0xC2 (0x40, 0x0, 0xFFFFFFFF80000000, 0x0) Error: BAD_POOL_CALLER file path: C:\WINDOWS\system32\drivers\aswsp.sys product: avast! Antivirus company: AVAST Software description: avast! self protection module Bug check description: This indicates that the current thread is making a bad pool request. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software). Google query: aswsp.sys AVAST Software BAD_POOL_CALLER