BSOD - Several Error Types pointing to ntoskrnl.exe

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.

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.

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??

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.

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.

Code:

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

Despite of not being an old driver.

Code:

fffff880`04a5b000 fffff880`04b35000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Mon Oct 28 08:05:06 2013 (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.

Code:

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

A chipset element. Not old, too.

Code:

fffff880`01939000 fffff880`01946000   amdkmpfd T (no symbols)           
    Loaded symbol image file: amdkmpfd.sys
    Image path: \SystemRoot\system32\DRIVERS\amdkmpfd.sys
    Image name: amdkmpfd.sys
    Timestamp:        Wed May 22 06:35:52 2013 (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.

Code:

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

And the driver is the latest.

Code:

fffff880`044ca000 fffff880`0456a000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013 (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.