Solved BSOD - Several Error Types pointing to ntoskrnl.exe

[v4l33]

So basically keep getting random BSODs for a month now and I can't figure out what is causing them.
The error I keep getting are:

• SYSTEM_SERVICE_EXCEPTION
• PAGE_FAULT_IN_NONPAGED_AREA
• KMODE_EXCEPTION_NOT_HANDLED
• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
• DRIVER_IRQL_NOT_LESS_OR_EQUAL
• MEMORY_MANAGEMENT

They seem pretty random but they always point to ntoskrnl.exe as the culprit, tho afaik that happens when the OS has no idea what caused the crash.

What I did so far:

• Tested memory with Windows Memory Diagnostic Tool
• Tested memory with memtest86 overnight, 6 passes
• Swapped the memory modules and inserted them on different slots
• Tested system stability with Prime95 Blend for 2h
• Tested VGA card with Furmark for 30min
• Tested with Windows Driver Verifier
• Tested system files with SFC
• Tested with CHKDSK
• Tested HD with WD Diagnostics
• Reinstalled all drivers with latest WHQL versions or BETA
• Updated BIOS and reflashed it just in case
• Reinstalled Windows

Absolutely every test above ran clean and had no errors whatsoever.

The important thing to mention is that I never got a single BSOD while gaming or running resource intensive applications, it only happens when I'm browsing or the computer is idle.

So anyone has any suggestions of what might cause this or how to fix this? Thank you.

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[v4l33]

Edited.

 

[Arc]

Kaspersky is contributing to the BSOD.

fffff880`099d44e8  fffff880`0493709eUnable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys[/COLOR]
 klif+0x7e09e

Uninstall Kaspersky using Kaspersky Removal Tool. At least as a test. 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.

If still the situation is the same, 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.

Let us know the results.

 

[v4l33]

It's not Kaspersky, I've installed it a few days ago just to do a full scan to be sure even tho MBAM didn't detect anything previously, and had the BSODs before without any antivirus installed. Also already mentioned that I ran memtest86 overnight (11h) without any problems detected.

 

[Arc]

Also already mentioned that I ran memtest86 overnight (11h) without any problems detected.

It the above statement is a fact, then the statement below is not viable.

It's not Kaspersky.

Your data says that Kaspersky is contributing to the BSODs.

Uninstall Kaspersky as suggested.

Let us know how it is running without Kaspersky.

 

[v4l33]

had the BSODs before without any antivirus installed.

I don't see any point of uninstalling it, but I'll do it anyway, honestly tired of these crashes.

 

[Britton30]

had the BSODs before without any antivirus installed.

I don't see any point of uninstalling it, but I'll do it anyway, honestly tired of these crashes.

Possibly to get your system running smoothly? At this time klif.sys Is blamed for this BSOD.It is from Kaspersky Labs.
Do you have Checkpoint Endpoint Security installed too?

 

[Layback Bear]

v4l33 could you list the other places you have been seeking help and what have they recommended?

 

[v4l33]

Possibly to get your system running smoothly?

I know what you saying, but my point is that I got these BSODs even without KAV or any other security suite whatsoever except built-in firewall. So if the crashes occured without Kaspersky software installed then seems logical it's not the culprit.

v4l33 could you list the other places you have been seeking help and what have they recommended?

Haven't got any answers elsewhere so far, tho searching on Google for similar problems gave me a variety of answers, from malware and drivers to memory timings and voltages to hardware failures.
The problem is that there's no specific error over and over again, but seemingly random ones and no idea what could cause them. Also the weird thing is that it happens in low load or idle, never in high load.

 

[Britton30]

My point was to rule out one BSOD cause, then when you have one without KIS the readers of dmp files can see what else is causing it. There can be several layers to an issues, not always easy to pinpoint.

 

[v4l33]

That makes sense, already uninstalled KAV, will come back if I get another BSOD, time unknown tho, usually varies between 1 day and 1 week.

 

[ICIT2LOL]

V I don't know what the dump files mean but I have been using KISS for some years now and I would like to know just where you installed it from and how you configured it?

I find installing from the disk you buy a nightmare to be honest and always pay and get an activation code and download form the website . Plus I don't like the KAV if that is what you are using as I think it is too light on.

I have never had a problem apart from the odd bugs with new versions which unfortunately they change a fair bit.

 

[v4l33]

Was just a trial version downloaded from the official site, got it just to do a full scan just to make sure MBAM didn't miss anything.

Anyway, just got another BSOD today while working, different error as usual and this time without KAV installed, attached the info.

 

[ICIT2LOL]

V give this a try



PSU- Jump Start

for a reference
PowerSupply 101: A Reference Of Specifications - Power Supplies as you will see there is a +/- 5% variance that can make allthe difference so 11.4v is way too low and 12.6v way too high.

Plus remember correct volts do not necessarily mean correct current (amps - inturn watts)

Suppose you have tried reseating everything too??

 

[v4l33]

Can you explain more why I have to jump start my PSU?
I don't think it's the PSU, I get the crashes only in low load or idle, can stress test for hours or playing games a whole day without a single crash.

These are the voltages on idle (AIDA and HWInfo):

And yes, reaseated everything, including the CPU,memories, switched cables, slots, etc. Also cleaned any trace of dust on the components.

UPDATE: Uninstalled IDM since I read it can lead to random BSODs sometimes, will see if it works.

 

[ICIT2LOL]

Well it is just a suggestion V as I am running out of ideas and if the PSU is failing then that jump test will show the actual volts and particularly watching the volts at pin 8 (grey cable) on the 24 pin socket is to see exactly what the volts are with a dedicated digital multimeter - not that I doubt the tests you have run are wrong but again something simple and takes no time at all to do.

Have a quick look at page 2 I that ref link I sent - the Power_Good signal.

 

[v4l33]

Problem is I don't have a multimeter and no way of getting one, unless I buy one, and I'm guessing it's not exactly cheap.

Downloaded Ultimate Boot CD and will try stress testing again with the tools there, maybe there's something memtest86 and prime95 missed.

 

[Arc]

Good to know that the Kaspersky is removed. It was essential to go deeper through the issue; and our intention is successful. Though the success is not a good one, because of what we are finding here.

Realtek PCIe GBE Family Controller. the onboard LAN is failing.

fffff800`00b9b020  fffff880`04a5d900Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys[/COLOR]
 Rt64win7+0x2900

Despite of not being an old driver.

fffff880`04a5b000 fffff880`04b35000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
[COLOR=Red]    Image name: Rt64win7.sys
    Timestamp:        Mon Oct 28 08:05:06 2013[/COLOR] (526DCD5A)
    CheckSum:         000DB1D7
    ImageSize:        000DA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have a try ... get the latest one from Realtek.

AMD PCI Root Bus Lower Filter is failing, too.

fffff800`00b9baa8  fffff880`01940220Unable to load image \SystemRoot\system32\DRIVERS\amdkmpfd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmpfd.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for amdkmpfd.sys[/COLOR]
 amdkmpfd+0x7220

A chipset element. Not old, too.

fffff880`01939000 fffff880`01946000   amdkmpfd T (no symbols)           
    Loaded symbol image file: amdkmpfd.sys
    Image path: \SystemRoot\system32\DRIVERS\amdkmpfd.sys
[COLOR=Red]    Image name: amdkmpfd.sys
    Timestamp:        Wed May 22 06:35:52 2013[/COLOR] (519C19F0)
    CheckSum:         0000E144
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I have never seen such an element to fail. People like Britton30 who is having much more knowledge about hardware may say about it. Please wait for his instruction about it.

The display driver is also failing.

fffff800`00b9c508  fffff880`0450fb36*** WARNING: Unable to verify timestamp for atikmpag.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys[/COLOR]
 atikmpag+0x45b36

And the driver is the latest.

fffff880`044ca000 fffff880`0456a000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
[COLOR=Red]    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013[/COLOR] (52A231D9)
    CheckSum:         0009FEFF
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So at a maximum you may try to roll it back to a version that worked good for you.

Overall impression is not good. It all may be caused by any of the following reasons:

• Failing RAM
• Failing CPU
• Inadequate Power Supply
• Virus Infection
• Corrupt Motherboard.

You said that you did Memtest already. Can you do it once again? May be a second run is ble to detect the errors.
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 possible, let us see a camera snap when 8 passes are complete.

Stress test the CPU.
Hardware - Stress Test With Prime95

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

For the PSU, follow what ICit2lol suggested.

Unfortunately we cannot check the motherboard without swapping it.

 

[v4l33]

Updated the network driver about a week or go, so think it's the latest version, same for all the other drivers I have. Also pretty sure the PC is malware free, scaned with MBAM, KAV, Bitdefender and Spybot S&D.

Will let memtest86 run again tonight and give you guys a screenshot after.

I just don't understand why I never get a BSOD while playing resource intensive games or running prime95, but when I browse or let my PC idle I often get random crashes.