Random BSODs, usually ntkrnlmp.exe

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

ImJustSaiyan said:

EDIT: Also, what program should I use for ISO mounting?

All the ISO mounting programs are kind of troublesome. I would not recommend any of those.

Use either 7-zip (free) or Winrar (little price). Both of them can extract any type of disk image files. So the basic job will be done equally good.

When a DV enablem BSOD itself blames the memory, then it cannot be any driver issue.

If you are certain that memtest passed without any red line, take the following tests ....

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

If both of them are free from errors, too ..... it is a matter to think on something that is beyond testing, so we cannot blame it .... that is the motherboard.

That would be interesting. I did both tests recently and although I'm not exactly sure about the beginning of the BSODs, I don't remember any before exchanging my motherboard to allow a second GPU in CrossFireX mode. I sold the additional card some time ago and I still have the first mobo, so it would actually be great if that's the case. The problem started much before the date of the first dump, but I did several clean installs attempting to solve it by myself. I thought of everything, except the motherboard. Because the PSU is new, the voltages are good (decent difference between idle and full load, inside the optimal range) and all the temperatures are fine I was sure it wouldn't be a hardware issue, maybe something related to basic drivers such as Catalyst or Synapse. I'll do them again but I have to ask if you are sure it couldn't be anything else, if the results of DV are really enough to tell it's a hardware fault. Thanks

EDIT: There's tearing in FurMark even at 11 FPS, though.

Chance is minimum. Still, as you have doubt, take a test.

Seatool for dos: SeaTools | Seagate download

• Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

The situation is making me think about the motherboard. But as it is not possible to test, we cannot blame it directly.