Can it be my PS? MOBO? Processor? Video card? Lack of luck?

Don't really know what to add here Captain

I reread this thread. I go back to the begining that this all started with the new RAM.

Am I correct now in thinking that you cannot recreate the previous working condition?

(Meaning: go back to the way it was prior to the new RAM?)

BSOD's that point to ntoskrnl.exe and or win32k.sys are generally drivers that are knocking out XP. Both ntoskrnl.exe and win32k.sys are XP system files.

win32k.sys is often triggered by graphics drivers.

Well, no I can't. Today I got BSODs when working alone with the single stick and just the new stick. And I can't really call it "working" when I idle the computer on desktop or the main menu of a game, waiting for a crash.

I also updated my graphics drivers today. I got the win32k.sys warning for the first time ever, and conincidentally I had upgraded the drivers.

BSOD's that point to ntoskrnl.exe and or win32k.sys are generally drivers that are knocking out XP. Both ntoskrnl.exe and win32k.sys are XP system files.

win32k.sys is often triggered by graphics drivers.

Anything I can do to fix this? Round it down to the specific card, sound/video?

Is there a remote possibility that buying a new video card will fix all this or would it be waste of money on an already-dead computer?

Sorry for the triple-post, but does that mean that RAM is out of the question?

I'm perhaps considering it could be my power supply...

Failing PSU's can cause a lot of problems but usually they will shut down the computer rather than BSOD.

To trace your drivers you can use PSTAT:

Pstat can tell you what driver is loaded at what address. Install the Windows Support Tools from XP's CD. They left it out of the help file.
Just type pstat in a command prompt. The bottom section will list drivers and their memory address. Match your param 4 on this list. Param 1 is memory it tried to read, param 2 is the IRQL, and for param 3 0 means read and 1 write.

To install Windows Support Tools

You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings may also prevent you from completing this procedure.

1.
Insert the Windows CD into your CD-ROM drive.

2.
Click No if you are prompted to reinstall Windows.

3.
When the Welcome screen appears, click Browse this CD.

4.
Go to the \Support\Tools folder.

For complete Setup information, refer to the Sreadme.doc file available in this folder.

5.
Double-click Setup.exe.

6.
Follow the instructions that appear on your screen.


Warning

• Certain Support Tools, if used improperly, might cause your computer to stop functioning. It is recommended that only experienced users install and use Support Tools.


Note

• The Support Tools and the Support Tools Help are in English only.

• The Setup program installs all the Support Tools files on your hard disk and requires a maximum of 14 megabytes (MB) of free space.

• Setup creates a Windows Support Tools folder within the Programs folder on the Start menu. For information about individual tools, click Tools Help. Tools with Windows interfaces can be selected from the Tools menu.

Another thought is to reinstall XP just to eliminate that as an issue.

I would consider buying new parts towards the idea of: "if I can't get this setup to work at least I can use these parts on a new motherboard"

At this point I would strip the computer of everything but RAM > CPU > Graphics Card > CD Drive > HDD Drive and reinstall XP. See if that gives you a functioning system. Of course you will have to add your Motherboard and Gaphics Card drivers.

I can't format because I don't have a DVD burner, just a CD-RW. Even so, I've read many articles about people having the same problems as I and still having them after a format.

I did a repair install of XP just to eliminate the possibility of corrupt system files. I will try that method you mentioned.

Pstat can tell you what driver is loaded at what address. Install the Windows Support Tools from XP's CD. They left it out of the help file.
Just type pstat in a command prompt. The bottom section will list drivers and their memory address. Match your param 4 on this list. Param 1 is memory it tried to read, param 2 is the IRQL, and for param 3 0 means read and 1 write.

I did all that but I don't know what I have to do with the information that's shown.

Match your param 4 on this list.

For example in your USB dump:

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USB Bugcheck Code:
Arg2: 8660a0e0
Arg3: 808624d2
Arg4: 8609f790

See if you can find the driver responsible at this address: 8609f790

This also might show as f790 8609