An a question for you, Archie, if everyone who runs 64 goes to Crucial and gets blue screens how do all these people get rid of BSODs. I need help for that.
Annie
I'm not Archie (his avatar is cuter), but I've noticed you're battling crashes and I might be able to help.
Think of a BSOD as a failure somewhere in the "engine compartment" of the operating system. There are hundreds of defined types of BSODs, and literally an endless number of possible causes, so when troubleshooting it's a good idea to keep in mind that one person's BSOD doesn't necessarily bear any relation to another's. Even if the "stop code" is the same (the number after the word "stop" in the BSOD message), that doesn't by itself prove any actionable similarity.
The best way to troubleshoot BSODs is to analyse the memory dumps which are created at the time of each crash. Summary versions of those dumps live as DMP files in your \windows\minidump folder. I expect that MS support has probably already asked you for those minidump files since they're troubleshooting the problem.
If not, you might want to create a new thread in the "general" section of the forum, so that this one stays true to Dinesh's issue, and to upload the latest few minidumps from your machine as a ZIP archive. (To zip them up you'll have to copy them to a different location first because the \windows\minidump folder is restricted).
SmartEyeball will then leap onto the dump analysis for you