Various BSOD + CMOS Bad Checksum

[medrimonia]

Recently, my computer started displaying several differents kinds of BSOD, sometimes when computer was starting up, it displayed a "CMOS bad checksum" at boot.

From my searches on internet, I found that in most of the cases, BSOD were due to old drivers, so I updated my drivers (directly downloading from manufacturer's website), removing the graphic card driver. This didn't help and I'm still getting a lot of BSOD (I think it happens more often before logging or when playing a game, but not only...). I runned two antivirus complete scans with different antivirus without getting any improvement.

Since I'm not able to get my hands on my external bootable drive, I have not launched any memcheck now, but I will try to do it soon. Has any of you ideas about what I should/could do before buying new material?

My configuration is available here: Configuration

BSOD dump summaries should be available from there.

 

[Hawkeye22]

How old is the computer/motherboard? It sounds like it may need a new battery - CR2032

 

[Paul NZ]

Upload the dmp files somewhere else. I cant understand a word on that site

 

[ahnilated]

The CMOS errors are nothing to do with drivers in Windows. That is something that you need to check on the motherboard. It could be a battery or that the bios you have is bad and needs to be reflashed to an updated version.

 

[medrimonia]

The computer is around 2 years old, I agree that a CR2032 is cheap and should be one of the first option to check, but can it result with ntfs_filesystem bsod?

Here is a link to a zip containing the dumps

@ahnilated: I forgot to tell it but the bios version is up to date.

 

[Paul NZ]

The ntfs BSOD means the files or hdd are corrupt. And it can also mean the hdd is failing. You may have to replace it

I would disable / uninstall AMD overdrive. This can cause crashes. Avast MAYBE one of the causes.

But you may sill have to replace the hdd, because of the 0x24 stop error. Since its corrupt

 

[medrimonia]

I agree that the different BSOD have different source of errors, but what bothers me is that since the errors are not related to the same hardware/drivers, this would mean that simultaneously:

- CR2032 got low
- HDD started failing
- Drivers went wrong while they were working well before

While each event separately is "quite common", all of them appearing at the same time seems quite weird to me, and it would imply that I change almost everything.

Is it possible that power supply is "damaged" and that since its capacity has dropped, the different component don't get enough current and "seems" to fail all one after the other?

I also switched from avast to panda free antivirus.

 

[Paul NZ]

Files for avast are still on the system. If you uninstalled avast use their removal tool to remove the rest of it

Are you using bitlocker on this? fvevol.sys is also crashing. And something thats installed maybe conflicting with it

Strange there's 4 files on your system with no names....Maybe corrupt? Run tddskiller see if you've got rootkits

 

[medrimonia]

I removed avast with their removal tool, changed the bios battery and runned tddskiller (no threat detected). Since I cannot "make problem happens", I cannot check if it worked, but I will keep you informed in any case.

 

[ahnilated]

Try getting the manufactures HDD testing tool for your HDD. See if the HDD is failing.

 

[medrimonia]

I just had a BSOD again. Then I was not able to get a signal to the display (I tried several times). I "shaked" a little bit the computer and then I was able to start it again (with a BSOD bad checksum at start). I will try to launch some tests on HDD now.

A fact that I forgot to mention is that a new user named "MASService" was added (I don't know when) and I can't find it in windows configuration.

Additionally, the fact that my "shaking" helped me to get a display (this already happened once) makes me think that there is some kind of poor electrical connection somewhere but I don't know how to diagnose it on a computer.

Here is the log of my last dump, it is still another error code (PFN_LIST_CORRUPT)

 

[Paul NZ]

usbohci.sys is causing that. Whats plugged into the USB ports?

I would get rid of Panda too, it can cause this stop error, then use their removal tool to remove the rest of it

http://www.pandasecurity.com/usa/homeusers/support/card/?id=55509

 

[medrimonia]

I runned the chkdsk on my hdd, there were some errors, but I haven't read the scandisk logs now (memtest is running and sadly, it seems that there is no problem with memory (it woulds be quite cheap to replace)).

I will post the results of the scan disk once I get back home (around 12 hours from now).

I'm considering swapping hdd with another computer, do you think it's a good idea? (It would require me to reinstall all the drivers)

 

[Paul NZ]

Would be better if you replaced the hdd and reinstalled windows. Like I said it may die sooner or later