BSOD With No Dump Files Being Generated, Happens In Firefox And BF3

These BSODs dont let Windows finish to create a dump file...as you can see in the pictures, it always hangs in the "Initializing disk for crash dump..." and then reboots. Only one time it finished, and it was something related to Ready Boost (which was never used or allowed to be used in the system, so I am considering this as not related to the problem...I already looked for BSODs related to Ready Boost, and it came in no help). So, since the Windows dont make a dump file, I am afraid the dump files collected from your "tool" are not related to this problem. I also believe that the Bluethoot devices listed as problematic in the diagnostic tools are not related to the problem also, since I almost never use any bluethoot device with my PC.After the system reboots from the BSODs it looks like the BIOS is weird, it usually says that "no operational system was detected", so I have to turn off the PC and then wait some time and turn it on again, and usually this makes the BIOS "see" the Windows again (sometimes I have to unplug the power cable and wait until all the LEDs are off). Just a couple of times the messages were different, like "The CPU could not be overclocked" opening another BIOS screen from American Megatrends.

These BSODs usually started just after I opened Firefox...my Firefox is with a little problem at the first start up...it starts to consume 25% of my CPU and hangs...I have to kill the firefox process and then open it back again to use it (the second time it loads fine)...if I didnt I would have gotten an BSOD in just a few seconds. This happened in a few other programs too, but randomly, first the process hangs, then the entire system and then the BSOD cames. Almost all the BSODs had no usefull data on them as you can see in the pictures.But since Firefox is a memory hog and some times I got KERNEL_IN_PAGE_ERROR and KERNEL_IN_MEMORY_ERROR (I dont have that picture I think), I started to believe that the problem may be in the RAM timings, or some other RAM related problem...Now with these new Ram timings I let firefox consume 25% of my CPU, at the first start of firefox, for minutes, and the system doesn't crash anymore. Also the only 2 times Firefox had set an BSOD it came with a message from Windows before, saying that "Instruction 0x123456 (i dont know the number :P) could not be read" and then it crashed explorer.exe and then the computer crashed. As I said, it's more stable, but still not "stable".