Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

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

15 Jul 2013   #1

Windows 7 Professional x64
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)

My System SpecsSystem Spec
15 Jul 2013   #2

Windows 7 Professional x64

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.
My System SpecsSystem Spec
16 Jul 2013   #3

Windows 7 Professional x64

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.
My System SpecsSystem Spec

16 Jul 2013   #4

Windows 7 Professional x64

Any thoughts?
My System SpecsSystem Spec
18 Jul 2013   #5

Windows 7 Professional x64

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!
My System SpecsSystem Spec
18 Jul 2013   #6

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

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

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
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
My System SpecsSystem Spec
20 Jul 2013   #7

Windows 7 Professional x64

Sorry for my delay in answering, work got in the way. I appreciate the thorough answer and I will get on this very soon.
My System SpecsSystem Spec
20 Jul 2013   #8

Windows 7 Professional x64

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?
My System SpecsSystem Spec
21 Jul 2013   #9

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

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
My System SpecsSystem Spec
21 Jul 2013   #10

Windows 7 Professional x64

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.
My System SpecsSystem Spec

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

Thread Tools

Similar help and support threads
Thread Forum
CMOS Bad Checksum
When I restart my computer it always goes to a screen that says CMOS BAD CHECKSUM then I press F1 to start the computer. I have to update my date and time and then everything seems to work fine. But when I click the arrow on the right side of my toolbar it just shows white spaces and I cant use...
General Discussion
Tosh A2OO reboots when both battery and PSU plugged in
Hey folks. So I am looking for second and third opinions on what may be wrong with my old Toshiba Satellite A2OO. The problem that I have is that when I plug in the PSU with the battery in the machine wants to shut down and restart. I have just received shipment of a new compatible battery...
Hardware & Devices
Anyone had any problem with CHECKSUM ERROR- DEFAULTS LOADING, then it asks to press F1 to continue or DEL to enter bios, but nothing happens. NEXT ???
General Discussion
TCP/UDP checksum offloading
hello, i have a voip application. i tested it on Windows 7. when i see the RTP packets with Wireshark, i see that every UDP packet originating from the Windows 7 machine has UDP checksum error, and Wireshark suggests that it might be caused of 'UDP checksum offload'. i received a...
Network & Sharing
Checksum Error
I just installed a new battery, which I also checked with a DVM, so I know the battery is not the problem, but my secondary rig will only retain what I set in the BIOS until I turn off the power switch or unplug the computer. This seems to indicate that the battery isn't able to power whatever it...
Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 18:53.
Twitter Facebook Google+