Windows 7 - several BSOD per day, all bug check code 0x00000109

Hi Pauly
Thank you for your reply. And please extend my gratefulness to x BlueRobot
I wasn't able to catch back before today. I scanned the laptop with Windows Defender Offine as suggested. After 6 (!) hours running an extensive analysis, it reported the laptop was infected with both
Exploit:Java/CVE-2012-4681 and
Exploit:Java/CVE-2012-1723.gen!A
I removed both on Windows Defender Offline. I was already singing victory but 40min later the BSOD came back. Desilusion.
Do you have some other ideia or recommendation on how can i get rid of it?
I am thinking to use a bootable antivirus (i may try with AVG rescue this time) and leave the laptop scanning tonight to check if there is still any malware infecting the laptop. I will update tomorow.
Txs

Hi Pauly
Report on the past 24H events:
First, i ran AVG rescue (bootable) during last night... time lost since it did not detect anything.
But I later ran the Kaspersky bootkit (like i should have done by x BlueRobot suggestion, instead of using AVG) and after more 6 hours waiting it found some additional malware that windows defender offline has missed - it's name: Exploit:Java/CVE-2010-0840.gg
Despite removed, the laptop kept crashing from BSODs
It was then that I saw your last post and I went to run the chkdsk /f /r command on promp. This time no BSOD during the analysis. Attached the resulting log, fyi.
I will make some time to see if I report any BSOD. The laptop is not mine (it's from my parents) and I am retaining it for longer than they wished to. I guess if a BSOD comes in the next hours I will have no choice than reinstalling Windows 7
In any case I will give feedback.
meanwhile and once again, thank you for all the support ...

ups, i missed to add the file on my last post

Java has many security problems, and it may be best that you remove Java completely. Most programs and website do not even require Java anymore.

• How do I uninstall Java on my Windows computer ?

Some corrections were made to your file system.

Personally, I would create a backup of all your personal files and save these to a external hard-drive or a USB stick, and then restore the computer to it's factory settings which may be a easier option for you:

• Acer Support: Frequently Asked Questions list for How to use Acer eRecovery
• Backup User and System Files

We can then work through removing any bloatware after the factory restore, these are programs which are basically junk and are not needed, they can reduce performance and corrupt your system:

• Clean Up Factory Bloatware

For information purposes and if anyone is interested, here is a description from Microsoft about the malware:

• Encyclopedia entry: Exploit:Java/CVE-2012-4681 - Learn more about malware - Microsoft Malware Protection Center
• Encyclopedia entry: Exploit:Java/CVE-2012-1723.gen!A - Learn more about malware - Microsoft Malware Protection Center

I wasn't able to find anything for Exploit:Java/CVE-2010-0840.gg.

Hi mates. I am glad to say "Problem solved"
After my last post yesterday evening I reported no more BSODs since. In fact the laptop is running smoother than before the first BSOD event last week (I guess the malware was already degrading its performance for some time).
My understanding is that after the malware was finally removed (I got surprised that windows defender missed to catch all the malware but fortunately Kaspersky seems to have finished the job) it was the checkdisk command that repaired the conflit which was triggering the BSODs.
Whatever it was, it is to you guys (Pauly and x BlueRobot) that I owe my gratitude for avoiding to format the laptop. Honestly, it would have been faster ... but the fact is that I am much more informed than 1 week ago and I learn a lot in the meantime. I hope my incident could have expanded your expertise some way and that it may be helpful to someone in future. In short: thanks!

Your very welcome, and that's why I always recommend multiple anti-malware scanners, others will catch viruses and spyware which the other one wasn't able to.