Solved Multiple BSODs (Occurs at start-up or random intervals) unknown errors

[Tachi]

Hello all,
I hope you all are well, I've been having issues with this computer and I'm not quite too sure what the issue is, I'm trying to post this quickly before I have another BSOD lol. I will edit it later and include more information such as specific hardware components. Thank you for your time and patience!

System specs:

Computer type : PC/Desktop
Computer Manufacturer/Model : Custom built
OS : Windows Ultimate x64
CPU :Intel Core i5-660 Clarkdale 3.33GHz LGA 1156 BX80616I5660
Motherboard : Asus P7p55-Pro
Memory : G.SKILL 6 GB (3x 2GB) 240-Pin DDR3 SDRAM DDR3 1600
Graphics Card :EVGA GeForce 9500 GT 1GB PCIe w/Dual Link DVI
Hard Drives:
WD Caviar 640GB Serial ATA HD 7200/16MB/SATA-3G

 

[Arc]

It is a stop ox1. As far as I have noticed, it is caused mostly by the third party antivirus programs. And it appears to be the same for you, too.

Some of your subsequent crash dumps are also indicating to the same observation, directly and/or indirectly.

Klif Mini-Filter fre_wnet_x86 (Kaspersky) is the failing module here.

fffff880`08f16398  fffff880`0463ef0fUnable to load image \SystemRoot\system32\DRIVERS\[URL="http://www.carrona.org/drivers/driver.php?id=klif.sys"]klif.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=klif.sys"]klif.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=klif.sys"]klif.sys[/URL]
 klif+0x36f0f
-------------------------------------------------------------------------------
BugCheck 19, {3, fffff8a010145500, fffff8a010145500, 41006e00690057}

*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )

Followup: Pool_corruption

Description here: Driver Reference Table - klif.sys

Uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Never use multiple AV programs. It is really not a good practice. Uninstall McAfee.

• Start Menu\Programs\McAfee Security Scan Plus

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Uninstall the following bloatware.

• Start Menu\Programs\ASUS
• Start Menu\Programs\ASUS\AI Suite
• Start Menu\Programs\ASUS\ASUSUpdate
• Start Menu\Programs\ASUS\T.Probe

Let us know the results.
____________________________________________________________________
BSOD ANALYSIS:

BugCheck 1, {7719186a, 0, ffff0000, fffff88008f16ca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
-----------------------------------------------------------------------------
BugCheck 19, {3, fffff8a010650500, fffff8a010650500, e24e4d430303020a}

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

Followup: Pool_corruption
------------------------------------------------------------------------------
BugCheck 19, {3, fffff8a010145500, fffff8a010145500, 41006e00690057}

*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )

Followup: Pool_corruption
--------------------------------------------------------------------------------
BugCheck 1A, {5001, fffff781c0000000, e9b0, e9abffffffbe}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

 

[Tachi]

Alright, thank you I'll do it first thing in the morning and let you know!
Also if more BSOD errors occur should I repost in here or start a new thread?( sorry for any informalities I'm a tad new to this . )

 

[Arc]

At first you report it back here. Then, depending on the situation, if this particular issue gets solved, and any other BSOD issue comes back later, you may think about that. But the present situation is this present issue, and you need to continue here for it.

 

[Tachi]

Thank you very much Arc!
So far so good, I've done all you suggested and it seems to be fine for now, I also ran Windows Memory Diagnostic, and nothing has showed up. Currently scanning using MB and MSE. Hopefully this will resolve the issues and then I can move onto the software issues. Thank you very much again I'll re-post( and edit this later to let you know after the scans ) later if there is another BSOD.

 

[Tachi]

Seems there are still errors, I cannot seem to complete a full scan with MSE ( it auto-shuts down and turns off protection causing me to turn it back on, and MB came up with no viruses). I had 2 BSOD errors again( 1 that is Bad_Pool_Header 0x00000019, other error I wasn't able to look at it quick enough to get the error name.) , I'll re-upload the minidump folder again.

 

[Arc]

Seems there are still errors, I cannot seem to complete a full scan with MSE ( it auto-shuts down and turns off protection causing me to turn it back on, and MB came up with no viruses).

Do some more virus scans ... Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Seatool for dos: SeaTools | Seagate download

• Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
• You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.

If all those comes free from 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.
______________________________________________________________________

Child-SP          RetAddr           Call Site
fffff880`0891dd58 fffff800`02db04b3 nt!KeBugCheckEx
fffff880`0891dd60 fffff880`012f9485 nt!ExDeferredFreePool+0xa53
fffff880`0891de50 fffff880`012cad9b [COLOR=Red]Ntfs!NtfsCreateFcb+0x2c9[/COLOR]
fffff880`0891df30 fffff880`012ef209 [COLOR=Red]Ntfs!NtfsOpenFile+0x1cb[/COLOR]
fffff880`0891e120 fffff880`01257a0d [COLOR=Red]Ntfs!NtfsCommonCreate+0xc49[/COLOR]
fffff880`0891e300 fffff800`02c88968 [COLOR=Red]Ntfs!NtfsCommonCreateCallout+0x1d[/COLOR]
fffff880`0891e330 fffff880`0125818f nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0891e410 fffff880`012f1a2c [COLOR=Red]Ntfs!NtfsCommonCreateOnNewStack+0x4f[/COLOR]
fffff880`0891e470 fffff880`01109bcf [COLOR=Red]Ntfs!NtfsFsdCreate+0x1ac[/COLOR]
fffff880`0891e620 fffff880`011292b9 [COLOR=Red]fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f[/COLOR]
fffff880`0891e6b0 fffff800`02f7f0fc [COLOR=Red]fltmgr!FltpCreate+0x2a9[/COLOR]
fffff880`0891e760 fffff800`02f7aa78 nt!IopParseDevice+0x14d3
fffff880`0891e8c0 fffff800`02f7bc96 nt!ObpLookupObjectName+0x588
fffff880`0891e9b0 fffff800`02f7d59c nt!ObOpenObjectByName+0x306
fffff880`0891ea80 fffff800`02f88b64 nt!IopCreateFile+0x2bc
fffff880`0891eb20 fffff800`02c7bed3 nt!NtCreateFile+0x78

 

[Tachi]

Currently scanning again with MB. While you were offline I read different articles on SF and ran a memtest86 for a few hours( noticed a bad RAM slot, hopefully that explains the "Bad Pool Header" BSOD). I've already done a TDSSKiller scan, and I've enabled Driver Verifier.

Currently scanning overnight with MB again, has detected 2 objects no further BSOD after swapping RAM into a new memory slot so far, will post again on follow up after ALL scans / if more BSOD occur.

 

[Arc]

So many errors within first pass

Go to the Part 3 of the tutorial How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight. But at the occurrance of the first red line, stop testing.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. 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.

 

[Tachi]

Hey, I found out it was a bad slot that one of my RAMs were in, I had found that guide before you posted and tested it haha. However I got another BSOD with DV enabled, I looked at it using BlueScreenView, was a tad lost on finding the specific driver, here is the SF Diagnostic Zip Folder.

 

[Arc]

Either dont use that particular slot, or replace the motherboard.

If that sitution also generated BSODs, then we may think for DV and other stuff. In the present situation, dont need DV atm. And, rightly it is showing a result which is not very logical.

SO, avoid the failing slot (best is to replace the motherboard) and run the computer normally. See what happens there.

 

[Tachi]

Hey, sorry for the long reply was doing several test on the mobo\cpu\ram\video card, finally solved the issue. the culprit was actually a faulty hard drive( and a bad RAM slot on mobo), currently using an old one and so far has been working flawlessly for a few days. I would like to thank you Arc, and everyone on the sevenforums staff for putting up guides and helping me through with this problem. Hope all is well, thank you again and take care!

 

[Arc]

Well done on solving the issue. Congrats.
For any further issue, let us know.