BLUE SCREEN: STOP 0x00000019 (0x00000020, 0x89E4B688, 0x89E4b6D0, 0x0A090001)

What is the Recovery Console method?  You mean to run chkdsk?  That looks like another Support Engineer wild goose chase.

I will give you instructions to make a bootable XP Recovery Console CD (no XP media required), but you can use your genuine bootable XP installation SP2 CD to get into the RC if you want to run chkdsk (it will not hurt).  Just be sure you don't accidentally do a Repair Install instead.  If you make your own Recovery Console CD, that possibility is eliminated.

Several of your latest crash dump implicate Chrome.exe and one implicates CCC.exe which is the ATI Catalyst Control Center, one from 020712 implicated the ATI drivers, but that was before you updated them.  One says memory corruption, but several say chrome.exe.

PROCESS_NAME:  chrome.exe

Would you say that you mostly notice these crashes whilst running Chrome?

A few days ago, another annoying BSOD was resolved by uninstalling Chrome and reinstalling it but they have a special method for that which you should use should you entertain that idea (I would).  In that case, the BSOD and BlueScreenView implicated win32k.sys (an XP file), but that was not the real cause of course when you dug a little deeper.

http://support.google.com/chrome/bin/answer.py?hl=en&answer=111899

The consequence is that unless you find out how to save your Chrome bookmarks, you will lose them (check the Chrome forums).  Looking at my Chrome, I don't see how to do that and there may not be a way.

Then, Chrome was reinstalled from this link:

https://www.google.com/chrome/eula.html?standalone=1

It is good that you can upload the dump files, so send any more after 02152012 and send the latest one you have.  Oops!  I see them now and will take a look...

The one from 021712 shows you ntoskrnl.exe, but inside it implicates SearchIndexer.exe which is part of Windows Search.  You may want to get into Services and set that thing to Disabled for a while too.  It is a memory and CPU hog anyway and I would never install it and when I see it on a system I am working on to get performance up, I uninstall it completely.


Here is how to make a bootable RC CD and use it to run chkdsk /r from same:

If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure (no XP media required).

This is not the same as any recovery disks that might have come with a store bought system.  

You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

The bootable ISO image file you need to download is called:

xp_rec_con.iso 

Download the ISO file from here:

http://www.mediafire.com/?ueyyzfymmig

Use a new CD and this free and easy program to burn your ISO file and create your bootable CD:

http://www.imgburn.com/

When installing ImgBurn, DO NOT install the Ask toolbar.

Here are some instructions for ImgBurn:

http://forum.imgburn.com/index.php?showtopic=61

It would be a good idea to test your bootable CD on a computer that is working.

You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk.  These adjustments are made before Windows tries to load.  If you miss it, you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually  1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder.  This is the same as the 

C:\WINDOWS folder you see in explorer.

The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn't find any problems.  It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find.  

It may take a long time for chkdsk to complete or it may appear to be 'stuck'.  Be patient.  If the HDD light is still flashing, chkdsk is doing something.  Keep an eye on the percentage amount to be sure it is still making progress.  It may even appear to go backwards sometimes.

You should run chkdsk /r again until it finds no errors to correct.

Remove the CD and type 'exit' to leave the RC and restart the computer.

You do not have to adjust the BIOS again to boot on the HDD since the CD will not be present.

Also, the errors you are receiving are typical of hardware issues with the first suspect being the physical RAM.

Even though the RAM may have tested OK does not mean there is not a problem with the RAM.

What I would suggest is to re-seat the RAM and re-seat the video card and see if there is any improvement.

If problem persists remove all but one module of RAM.

If problem persists alternate the module or reinstall the old RAM.

Also, for  testing the  VRAM (video RAM) you could try the following application:

http://majorgeeks.com/Video_Memory_Stress_Test__d5896.html