BSOD - fileinfo.sys and ntoskrnl.exe

The 3 crashes included were before I:
-updated Realtek HD audio drivers
-disabled the AMD HD audio driver
-turned HD sleep to never
-updated video driver

System has been running with no issue since Sept 2011 up until July 2012. I've already done a repair install so I don't not have all the dump files unfortunately from last month .

I've had no issues in the last day, but prior to the repair install I could get a week or so of the system running before it would crash. Because the crashes were so random before I can't really know if something is wrong still.

The first crash was when I tried to use disk cleaner to remove windows.old folder.
The other 2 were when system was idle, I've never had an actual crash while using the system or gaming.

I just wanted experts to look at it to see if they see anything that stands out.

Thanks

I was able to complete removal of windows.old without a BSOD. If I can get 2 weeks of stability I'll consider it solved.

System appeared to be running smooth, so I ran memtest for the heck of it.

After completing the first pass, the screen filled with random text but appeared to keep running. I tried to view the error log and it locked up showing like 3k on test 3 and I had to restart to get out of it.

Got this BSOD as soon as windows restarted. I'm going to assume it's ram at this point?

The crazy screen I had was with memtest86 which I heard is common with 86 but not 86+. I took a stick out and got a clean pass. I've got memtest86+ and will run through my 4 sticks today.

All 4 sticks passed individually, running all 4 for a few hours now. If the ram passes what would be the next step? Driver verifier?

I went to bios and checked voltage and speed of ram, running 1333 and 1.5v as recommended.

completed 18 hours of memtest86+ with no errors, so I guess it's not the ram.

What now?

Sept 20 is when my warranties are up. I'd really appreciate some help.

found updated audio drivers and ATI audio drivers on the Realtek website. They were updated as of 6-22-12 and I started having issues on 7-11-12 hopefully this is the answer. I'll keep the thread updated

The only thing that changed is that I installed borderlands 2 last night, I assume it has something to do with that? Is there any drivers that looked really out of date?