BSOD Problems with yet unknown cause

[Shawnie]

Hi everybody

I'm getting much "BAD_POOL_HEADER" or "PAGEFAULT_IN_NONPAGED_AREA" BSODs lately and I have no clue what causes them. After some research I've stumbled upon this promising community and I hope that you guys can help me out =)

I've attached the zip-Folder from the diagnostic tool.

Thank you all in advance!

 

[koolkat77]

Welcome

None of your dumps give a probable cause.

Before we troubleshoot, let us check some things first.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA BSOD Index

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

STOP 0x00000019: BAD_POOL_HEADER BSOD Index

Usual causes: Device driver

May I know what antivirus are you using? (I may have missed it in the msinfo file)

Please uninstall this tool while we are troubleshooting problems with your computer:

Start Menu\Programs\Nexus Mod Manager	Public:Start Menu\Programs\Nexus Mod Manager	Public

BIOS-Version/-Datum	American Megatrends Inc. 1611, [COLOR="Red"]26.11.2008[/COLOR]

Your BIOS version is quite old, get an update for it from the manufacturers website

 

[Shawnie]

Thank you for your answer. I'm using Kaspersky Anti-Virus 2012. I've flashed my BIOS to the newest version and removed the tool. What's next?

 

[koolkat77]

Thank you for your answer. I'm using Kaspersky Anti-Virus 2012. I've flashed my BIOS to the newest version and removed the tool. What's next?

Lets enable driver verifier to rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[Shawnie]

Windows almost imediately crashed with a BSOD and once again while the diagnostic tool was gathering the needed information. I've attached the new dumps.

Thank you for your help!

 

[koolkat77]

Windows almost imediately crashed with a BSOD and once again while the diagnostic tool was gathering the needed information. I've attached the new dumps.

Thank you for your help!

Your BSODs are cause by klif.sys = Kaspersky http://www.carrona.org/drivers/search.php?id=klif.sys

Please uninstall and keep MSE. Its known to be the most compatible (as well as free) antivirus for windows 7.

Download, install and get updated. Observe and let us know if you're having more bsods.
:ar: Microsoft Security Essentials - Free Antivirus for Windows

Analysis:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {0, 0, 1, 0}

Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by :[COLOR="Lime"] klif.sys ( klif+4b584 )[/COLOR]

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

 

[Shawnie]

I'll do as you suggested and report back after a while if anything changed. Thanks! =)

 

[koolkat77]

Sure!
See ya

 

[koolkat77]

Hi

Have you had any BSoDs after your last post?

 

[koolkat77]

Were your BSoD issues resolved?