Mini stated memory corruption.

So does that mean that my RAM is faulty? I've never had any problems with my memory before. I have 2 sticks of 1GB Corsair XMS PC3200 DDR RAM that I have never had any issues with... Gah this sucks, I so don't feel like sinking any more money into this thing but if I need new RAM, I'm gonna have to face the music I guess.

Well I first suggest that you run MemTest for 7-10 passes to see if indeed it is your memory per se. it could be a bad driver trying to access an IRQ address since it is an 0x0A error.

I understand about the memory. I had BSODs galore and it was my memory; sticks that I had for over 2 years. I just replaced today.

P.S. Memory does become corrupted for no apparent reason.

Well, that's bad news but sh1t happens for no reason sometimes i guess. I'll run my Memtest86+ CD when i get a chance. I'll probably just buy 2 new sticks even if my RAM passes just in case. I understand that sometimes corrupt RAM can pass the test so I'll just get 2 new ones. Thanks for the info.

memory corruption doesn't always mean RAM either though it could also be pagefile or video memory

there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.

^^Funny you should say that... I've been having a slight issue with my pagefile. I tried upping the amount of space on the system disk but for whatever reason it still reads a previous value. I got some kind of warning in the Event Viewer about the pagefile so that's why I wanted to make it bigger.

Getting to the RAM, I ran memtest86+ for ~14-15 hrs last night for a total of 12 passes. When I woke up I checked it and there were NO errors whatsoever. It looks like I won't be buying new sticks. Since I didn't find anything wrong with the RAM and I'm using the factory timings, I guess the problem is being caused by something else. I don't know what else to check though. I don't really understand the whole deal; my system was running flawlessly about a week ago. Frustrating...

when you enter task manager and go to the performance tab, does it show your pagefile maxing out.

How much do you have allocated? what is the maximum? What is the event viewer error ID and source?

The TaskManager doesn't show that the pagefile is maxed out. When I go to adjust the size of the swap, it reads 2047 under "currently allocated." I have 2 gigs of RAM so I want the size to be at least 3072 right? Under Virtual Memory, drive C: has 2-200MB of space for swapfile and drive D: has 2-3200... Why isn't the currently allocated value changing?

and what about event ID and source for those errors

Go to control panel -> administrative tools -> event viewer -> select the event -> right click and select event properties

Sometimes it will give a description of what the ID means sometimes you have to write down the ID and source then look it up