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

[ingelectronico]

Dear Sirs:
I'm having frequent BSODs, and I already discarded the RAM and Hard Drive Damage options (as I have extensivley tested them). Last time I enabled "verifier" and had frequent crashes at startup.
Attached are the Dump files, in order to ask for your help identifying the faulty driver.
Thanks in advance for the support.

Javier

 

[Arc]

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]

Thanks for the fast answer.
I'll give a try. Sorry to ask but, what is the non-dv information you were asking.
Best regards

 

[Arc]

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.

 

[ingelectronico]

Ok gracias!

 

[ingelectronico]

Dear Arc:
I followed your instructions, disabled DV and installed MBAM. MBAM found some suspicious registry keys, which I deleted. Today, while working with some open programs I got again BSOD with the reason PFN_LIST_Corrupt (two times).
I'm attaching the debug information, again, for you to check if FSecure is still the main reason. I would prefer to keep F-Secure, as was provided by my company.
Thanks again for the support.

 

[Arc]

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

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

 

[ingelectronico]

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.

 

[ingelectronico]

Hi again Arc. I had a new BSOD just a moment ago. Attached is the new report.

 

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

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.

___________________________________________________

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

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

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

 

[ingelectronico]

Hi Arc
I tested the ram with mem test and found several errors. Check the attached image.
The funny thing is that windows memory tests don't show any error.
Best regards

 

[Arc]

Hi Arc
I tested the ram with mem test and found several errors. Check the attached image.
The funny thing is that windows memory tests don't show any error.
Best regards

No image is attached unfortunately.

And you need not to use an inferior tool like windows memory diag.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

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.

Otherwise, if you think this process is time consuming, you may replace the RAM, either with the matching specs of the existing, or the entire kit; but the possibility of a bad slot will remain there.

 

[ingelectronico]

Sorry, I tried to attach the image from the cellphone. Here it goes again. I have 2 memory modules, the original one, of 4Gbytes and an additional Kingston of 8Gbytes (total 12 Gigabytes). For the test shown in the image, I just kept the original one and showed that was failing around 2350Mbytes range.
Today I called Lenovo support and they run their memory diagnostic tool, without errors, so they rejected the case. They just recommended me to update the BIOS (which I did successfully).
I believe is a motherboard problem, because when I add the 8Gbyte module, I also get errors in the memory range of 4700Mbytes, which is double the 2350.
Anyway, I'll mark the case as solved, and just re-post a new thread with more information if the problem continued.
Best regards

 

[Arc]

No problem.