Recurring X101 BSOD during gaming

Hello

A few weeks, or even a couple of months ago, my system became very unstable. While I was playing videogames, it would randomely reboot without BSOD, simply freeze, so that I had to manually restart, or, more often than the previous, display a BSOD about "a clock interrupt was not received on a secondary processor within the allocated time interval" (X101).
After some troubleshooting (getting Windows updates, checking drivers, stress testing the CPU), it ocurred to me that it could be related to my voltage regulator, which at the time was an archaic Koblenz one that supported 300 Watt, my power supply unit being 600 Watt. I replaced the regulator for a 1200 W one, and everything was solved. I thought it very strange that the regulator was the cause of the issue, as I had been gaming on the same computer with that regulator for a long time, without any problem, and playing the same games.
Everything was fine for some weeks after replacing the regulator, but 2 days ago, I replaced my PSU for a 750W one, as part of the upgrades I intend to do on my computer. The problems came back. Today I had the aforementioned BSOD happen twice while playing a videogame (7 days to die, if that makes any difference). I also experienced a very strange graphic problem that had also presented itself, although rarely, in the first row of instability, and that is: while playing a first person videogame, I am for instance swinging an object in the game, hence there is an image of said object moving across the screen. Suddenly, the trajectory of the object starts to leave instances of said object, throughout the whole screen, and so, if I continue to swing it, the screen gets cluttered with many images of the object. I hope I explained it correctly, since I don't know the name of that particular error, if it has one.
I started believing that my CPU could be at fault, but after witnessing such a GPU-specific problem as the one described, I am left with no viable hypothesis as to what might be the problem.
So, to conclude: I have now experienced the X101 BSOD twice, as well as that strange graphic problem, and I am running on a 750W PSU plugged to a 1200W voltage regulator. My version of Windows is 7 Ultimate x64 Service Pack 1. The rest of my system specs are on my profile.
I hope you can help me solve this, as it is shaping up to be a real conundrum, and either way, I appreciate any help given. I have attached the compilation of files requested in the instructions for posting this kind of problem.

EDIT: I forgot to mention that I also succesfully upgraded my BIOS to it's latest non-beta version. I would also add that during the first series of BSODS, the reports were somewhow more informative, due to the Windows screen for error reporting that prompted after succesfully rebooting. They used to mention something about ntoskrnl.exe being at fault. During the second wave of instability however, I do not have the privilege of getting those informative Windows prompts after reboot.

Code:

BugCheck 124, {0, fffffa8007fdc7c8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

Let us see the complete set of required data?

Click on button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

Depending on that data we have to build your troubleshooting strategy.

The zip contains four crash dumps only, whereas we should have a lot of other files ind info.

Let us think that the DM log collector is not working properly for you for any reason. You use the SF Diagnostic Tool - Using for Troubleshooting and let us see the resulting log.

Code:

Host Name:                 USER-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          User
Registered Organization:   
Product ID:                00426-OEM-8992662-00006

Counterfeit installations such as yours contains heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable.

My recommendation is to start with a clean slate, and install a genuine version of Windows. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable.