BSOD at random times, driver problem 99,9% likely

Hi ingelectronico.

It would have been better if you supplied us the non-DV enabled crash dumps. Also, all the necessary files are not included in the zip.

Based on what you supplied, I would suggest you to uninstall F Secure. How do I uninstall the product? - F-Secure Community - 15384

Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know the results.
_______________________________________

BugCheck C1, {fffff9801f2e8b40, fffff9801f2e810b, 6b04c0, 23}

*** WARNING: Unable to verify timestamp for fsgk.sys
*** ERROR: Module load completed but symbols could not be loaded for fsgk.sys
Probably caused by : luafv.sys ( luafv!LuafvNormalizeNameComponentEx+fa )

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

ingelectronico said:

Sorry to ask but, what is the non-dv information you were asking.

The crash dumps before you enabled Driver Verifier.

Anyway, let us know the situation after removing F Secure. :)

The previous BSOD was caused by F Secure, and it is still present in the system. With the crasher present, it it tough to take any further decision.
________________________

Code:

fffff880`08f73000 fffff880`08fa8000   fsgk       (deferred)             
    Image path: \??\C:\Program Files (x86)\F-Secure\Anti-Virus\minifilter\fsgk.sys
    Image name: fsgk.sys
    Timestamp:        Mon Jan 27 19:08:50 2014 (52E6616A)
    CheckSum:         00039D50
    ImageSize:        00035000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Thanks, again Arc. I already de-installed F-Secure and installed MS Essentials. I'll keep the thread open for a week and if no other BSOD are found I'll marke it as Solved.
Thanks for the quick answers.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.

___________________________________________________

Code:

BugCheck 19, {3, fffff8a021510600, 20000000013ffac, fffff8a021510600}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

Followup: Pool_corruption
---------