Well the first place we always look when troubleshooting Windows is the Eventviewer. Startmenu - Run - eventvwr
This is where Windows keeps all it's error logs. Look for critical errors and do google searches to see what they mean and where they come from. It will be very confusing at first but over time you'll find that it's the most important tool you have. Just keep in mind that there is no such thing as an eventlog with no errors, you can have system that is working perfectly but have a badly programmed app spitting errors out left and right. However the best thing to look for is what happened right before the BSOD. Hopefully the system has time to spit out some errors before you get BSODed and you'll have something to start your research..
the easiest way to test to make sure it's not a driver issue would be to go in to safe mode but Fancycache might not be able to work in that mode. It's worth a try, hit F8 on system restart (before you see the windows logo but right after bios) and choose safe mode. If it does work and doesn't BSOD then you definitely have some sort of conflict (either driver or software).
A general rule of thumb when you are having stability issues is to make sure all your drivers are up to date, especially the GPU they are the biggest culprits of instability. However it's also a good idea to check the forums to make sure there aren't any major problems with the new driver release.
Next you can deactive any startup items that you have running in the background. Start Menu - Run - msconfig, uncheck everything under the startup tab (make note of what is checked before you do, so you can re-enable them). If the problem goes away with everything unchecked, then slowly reactive everything (troubleshooting usually involves a lot of tedious rebooting).
Finally if that doesn't work you can try running SiSoft Sandra's Burn-in tool
http://www.sisoftware.net/ , it will stress every aspect of your machine and if there is a problem chances are it will BSOD. That will tell you if you have problem with your system or a Fancycache issue. Just be sure to disable Fancycache before you burn-in..
Good luck and let us know what you find