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

[yooper1989]

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)

 

[yooper1989]

Update: As of now the BSOD has stopped. The computer will now start to boot, tell me the cmos checksum is bad, I then enter the settings and make sure date and time are good (they always are), I save and continue booting and it is fine.

The catch is nothing I do while on the computer saves. I'm downloading an audio manager, I need to restart to finish the install, every time I restart I need to start over the install, then restart. Its one heck of a vicious cycle lol. I have no idea what to do... Battery is new and I moved a switch on the mobo to reset everything.

 

[yooper1989]

Zip file now attached. With the computer being weird and certain things not saving in between restarts when I set it to save mini dumps it didn't the first couple times. All good there now, and I was wrong, the blue screens are not gone as I'm sure you will see in the info.

 

[yooper1989]

Any thoughts?

 

[yooper1989]

New update that confused me. Really no clue whats going on now and could use the help.

Yesterday I pulled my two 4 gig ram sticks. I put in two 2 gig ram sticks, these were out from previous blue screening in March and I assumed one or both were bad. When I put these two in the PC booted right up 100% normal. Also no checksum bad screen.

After using it for a while I booted down and this morning I started the PC again, same configuration. Still no checksum bad screen but it blue screened again. I was curious, so I put the original two 4 gig ram sticks in and removed the other two 2 gig ram sticks. It booted like normal.

How is it that it boots normal after swapping the ram back and forth? That has to be the craziest thing I've ever heard a computer do!

 

[Arc]

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:

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
---------

 

[yooper1989]

Sorry for my delay in answering, work got in the way. I appreciate the thorough answer and I will get on this very soon.

 

[yooper1989]

Quick question... You mentioned a USB driver failing. I have a literally psycho refurbed Razer Lycosa keyboard that does insane things regularly that I planned on replacing soon. It mostly sticks to repeating a key that is not locked down until I unplug it from the usb and sometimes randomly not working after resetting the repeating key.

The question is could this thing be causing it possibly?

 

[Arc]

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

 

[yooper1989]

Windows Defender Offline told me this: (all the other programs came back with nothing to report.)

Your PC needs to be repaired. Operating system couldn't be loaded because a critical system driver is missing or contains errors.

File: \windows\systems32\drivers\amdsbs.sys

(just wondering too I have 64 bit windows, I know a lot of things are set to 32 and also work on 64, just want to make sure that is one.

error code: 0x000009B

Problem is the PC is really mad lately and I can't even sign on to it. Also, it won't boot to my windows disc, it gets to the windows loading part and freezes. Though I may need a specific repair disc... The one I tried was my windows 7 professional install disc.

 

[Arc]

I think you need to install ATI System Drivers for 7xx/8xx/SB7xx/SB8xx Series (except RS690, 740), version 8.947.0.0 dated 2012-09-20 from MSI Global ? Motherboard - 870-G45 .

What happens if you try to boot the computer normally? Can you follow it:
Troubleshooting Windows 7 Failure to Start

 

[yooper1989]

I'll be going through that tonight or tomorrow, work has finally let up. For normal booting or any booting it usually loads a certain amount and then starts right over like I just turned it on or gets far enough to blue screen.

I don't get how it booted to 2 cds but not my windows disc...

Also Arc thanks for the help, you've been amazing keeping up with this too. Greatly appreciate the help and info, literally would not be this far without you!

 

[yooper1989]

So had a small miracle... Put my newer ram back in swapping the older stuff (I had been swapping back and fourth, idk why but it seemed to work) and I pulled the CMOS battery... And I'm in! Going to get that driver.

 

[Arc]

So had a small miracle... Put my newer ram back in swapping the older stuff (I had been swapping back and fourth, idk why but it seemed to work) and I pulled the CMOS battery... And I'm in! Going to get that driver.

So you are using a RAM mixture here?

Use only one set of RAM. Either the old one or the new one. If you use two RAM sticks at a time which are different, all sort of trouble is expected.

Use the new RAM only and let us know how it is working.

 

[yooper1989]

So had a small miracle... Put my newer ram back in swapping the older stuff (I had been swapping back and fourth, idk why but it seemed to work) and I pulled the CMOS battery... And I'm in! Going to get that driver.

So you are using a RAM mixture here?

Use only one set of RAM. Either the old one or the new one. If you use two RAM sticks at a time which are different, all sort of trouble is expected.

Use the new RAM only and let us know how it is working.

Yes I had a ram mixture of 2 four gigs and 2 two gigs. I'm learning through experience that this was a very bad idea... Though all the issues I've been having I have only used 1 set of ram.

Also I got the suggested drive from you installed. Will be making sure everything is good here soon.

 

[Arc]

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.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[yooper1989]

This was actually a test I ran before posting here and forgot to mention. I did run this and all came back just fine, even with the 2 different ram types. It just seems to work better not running the 2 together though.

 

[yooper1989]

My newest update:

After adding the driver Arc mentioned I'm seeing no change. Really seems like something is wrong in the boot loader or boot loader kernel. I've read that this may be able to be repaired if I can boot to a disc or usb version of my windows 7 professional disc.

As its loading the files (disc and usb flash drive do this) everything goes well until it gets to the windows loading screen, that lasts about 2 seconds and it blue screens. I don't get how its blue screening if it is booting to a disc or usb?

It has booted a few times by moving ram around and/or popping out the CMOS battery. The other thing that happens is the CMOS checksum will go bad messing up my boot order. To add to it the usb flash drive sometimes says its bad and moves on to booting to disc

my boot order for that was, usb, disc drive, ssd (windows 7 here), hdd (just storage)

removing the storage hdd doesn't seem to have any effect.

At this point I'm considering just getting on to the storage hdd one time and moving whatever I need and wiping it. Unless anyone has any ideas that's probably 1-2 days out.

 

[Arc]

Follow it:
Troubleshooting Windows 7 Failure to Start

 

[yooper1989]

I followed all that I could on the list, I think there was one thing I wasn't too sure how to do. Anyways, I decided to just clean install windows, after many attempts spent trying to get the cd to boot (it would freeze or bsod) it is finally going right now.

It is STILL blue screening though... I deleted the hard drive partitions and it began installing. After the first restart a blue screen flashes for an instant and it reboots, repeatedly. So I'm not even able to get a regular windows boot just to finish installing...

I'm guessing the mobo is fried? I'm going to attempt swapping the 2 2 gig sticks in and see what happens. For the most part it has disliked that though.

Again thanks Arc for the help, sorry for my slow responses too!