Really weird Lachesis.sys BSODs and more

Hey guys, time to ask YOU for help :P

I have been having some really weird issues, it all started back when I got this replacement motherboard (old one died). I never install my Razer mouse drivers, I usually always just let Windows install the generic mouse drivers, I only bought the mouse because it looked nice to be honest, so I never needed the Razer drivers for the extra actual intended features.

So, out of the blue, I decided to try and install the drivers for once. I was getting BSODs for awhile. There were varying probable causes, dxgmms1, atikmpag, etc... sometimes core Windows files. I decided to enable Driver Verifier a week ago, and upon booting up after enabling it, I BSOD'd immediately, and it labeled the culprit as Lachesis.sys.

After that, I turned off verifier and uninstalled the Razer Lachesis software from Control Panel and then restarted. After booting back up again, my mouse didn't move, but the mouse itself was being detected (logo was pulsing and LEDs were on). I unplugged the mouse a few times, and after a few tries of plugging it back in, Windows detected it and installed drivers (I can only assume generic Windows mouse drivers?)

Anyways, I thought I was in the clear after that, but I was wrong. I was playing a video game earlier and I BSOD'd again, it blamed DirectX again (dxgmms1.sys). After restarting, my mouse didn't move again, after unplugging it and replugging it a few times, it detected it and installed drivers again.

Out of curiosity, I ran Driver Verifier without the Lachesis drivers from Razer's website installed, and there was NO BSOD upon start up.

Out of curiosity again, I installed the Lachesis drivers again from Razer's website and restarted. This time, my mouse was working after the restart and the cursor was moving. I decided to test Driver Verifier again, and sure enough... BSOD on start up, Lachesis.sys as the culprit.

What is going on guys? Can anybody explain to me / tell me what I should do? I'm close to reformatting, but I'd like to avoid that if possible currently.. have a few things I want to finish before I do that.

Verifier enabled dump is attached, take a look!

Something to note also is the mouse wasn't being detected from what I noticed unless I tried a different USB port than what it was prior to crashing. For example, say it was in one USB port and then crashed, if I restarted and the cursor wouldn't move and tried unplugged and replugging into that same port, it wouldn't detect. However, if I tried an entirely different USB port than the one prior to crashing, it would detect and install the drivers.

Also something to note, in my System32 drivers folder, I have a Lachesis.sys driver date from 10/16/2009. When installing the Lachesis drivers, that driver remained the same date entirely, but the drivers in the Program Files(86x) folder for Lachesis were dated differently, some even dated from 2007.

I've tried renaming this Lachesis.sys driver Lachesis.bak, or even deleting it, but Windows keeps installing it over & over, so I assume this is the generic mouse driver?

Another thing to note is when I installed the Razer drivers at one point, the mouse was fine after a restart. However, I then tried to update the firmware, and after it completed, the mouse stopped moving again. I got a restart off with the keyboard, and after I got back to the desktop, my mouse cursor ceased to move again.

In regards to GPU related questions, I have been monitoring the temperatures of my GPUs and CPU. GPU 1 was around 72c load during a game, and GPU 2 was about ~15c lower. CPU was peaking at around 75c maximum. I have in the past run a Furmark on both cards for at least 15 minutes, temps reached high 90s... but there were no artifacts or crashes.

Just BSOD'd again after exiting a game of League of Legends, culprit was ntkrnl. I enabled Driver Verifier once again, I'll play games & such with Driver Verifier enabled.

I have a feeling this is hardware related, but there are too many variables for me to guess what it is, it's so overwhelming. This started happening right after I had to ship my old Asus P8P67 Pro to Asus. I turned the rig on after powering it down and it told me "current overflow detected", even after resetting the CMOS to stop my overclock. Eventually, after turning on my rig at one point, I had managed to cause a power shortage in my room, and when I went to turn my rig on with the old motherboard, it would just freeze at the motherboard logo screen. I called Asus and he said it sounds like the SATA port died (also killed my old Samsung F3 1TB drive that I ALSO had to RMA and get a replacement for).

So, ever since I got the new replacement HDD and motherboard (I also got two more monitors to add into the mix for eyefinity / just having three monitors in general), and since then.. I have been plagued with BSODs. Way too many variables for me to test, and I'm not sure where to start.