BSOD, Checksum bad after new battery, Nothing saved in between reboots

Hey all. First here are my spec

Windows 7 64 bit
1090T AMD 6 core CPU
MSI 870-G45 Mobo
8 Gigs of Ram
XFX 6850 Video Card
2 Hard drives - Hitatchi 500 gig and Samsund SSD 250 gig
Went through device manager and all drivers up to date.
***Replaced CMOS battery within the last 2 hours

My issues - Yesterday when booting my computer I encountered a BSOD. I took a picture of the numbers and rebooted. Got the CMOS checksum bad error. Ran repair, restored, and pc booted up. I downloaded blue screen checker and borderlands 2 later that day.

Today when booting I went through the same process or close, (it doesn't always BSOD) and it booted up. The 2 things I downloaded were still on my hard drive but they were "missing" both needed to be re-installed.

I've restarted a few times in between and have had the same issue.

(this may not be important, may help)
So far I have put in a new cmos battery and checked and redone the settings. Beyond that I'm very confused why nothing is happening. I reformatted in march and have only been running this windows 7 from then. I had random BSOD mostly when gaming then and it stopped some after removing 2 sticks of ram. To make sure nothing else was messed up I reinstalled windows 7 and put in the new SSD. I'm not gonna say this issue is unrelated to the SSD but so far it hasn't given me any issues at all.

Going to post the various BSOD codes I've encountered in just a moment.

in order of most recent

stop: 0x000000F7 (0xFFFFF880009A8C48, 0x00003AF4C63967A0, 0xFFFFC50B39C6985F, 0x0000000000000000)

stop: 0x000000F7 (OxFFFFF880009A8C48, 0xFFFFC50B39C6985F, 0x0000000000000000)

The stop 0xF7 BSODs are not present there in your zip. Probably those are failed to be recorded.

The regular causes of a stop 0xF7 BSOD are malfunctioning Device Driver or malware infection.

From the available dumps, it can be figured out that some USB device driver is malfunctioning, and some HDD malfunctioning, too. All those can be caused by a malware too.

So I will suggest you to do the following :

Scan the system for possible virus infection with the following programs, not with the Avast you have installed.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

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.
• You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.

If both of those tests came clean, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________
BSOD ANALYSIS:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80002cd22be, fffff88003763748, fffff88003762fb0}

Probably caused by : rdyboost.sys ( rdyboost!SmFpAllocate+4f )

Followup: MachineOwner
--------------------------------------------------------------------------------------
BugCheck A, {fffffa7f98936cb0, 2, 0, fffff80002ccdbfe}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ReleaseEpListLock+21 )

Followup: MachineOwner
---------------------------------------------------------------------------------------
BugCheck D1, {fffff87fbd890cd0, 2, 8, fffff87fbd890cd0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbMapDpc_Worker+53 )

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

It may be a problale cause, as the behavior is noticed many a times.

Before abandoning it, try to update the driver a a try.
Razer Support