Solved BSOD - Several Error Types pointing to ntoskrnl.exe

[Arc]

Updated the network driver about a week or go, so think it's the latest version, same for all the other drivers I have.

It is not.

Your drivers date is 28/10/2013 and the date of the latest version is 26-11-2013.

Also pretty sure the PC is malware free, scaned with MBAM, KAV, Bitdefender and Spybot S&D.

It is not any valid surety until and unless it is scanned with these two programs.

Why you are readily refusing anything that is suggested?

One more of such event will be enough to revoke myself from this thread.

 

[v4l33]

Sorry, I'm just getting fed up trying to get to the bottom of this for over a month , gotta believe me that I think I got older with 10 years trying to figuring this out.
Will do as you suggested and post the results of the scans after they finish.

 

[ICIT2LOL]

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.

Well you can get a simple and also a good digital multimeter for a few dollars for what you want it doesn't have to be fancy.

I haven't noticed any mention of a rootkit either maybe it might be worth running one of these perhaps. I would start with the Kaspersky one even though there ahs been some suspicions re the Kaspersky 5 Bootable AntiVirus Rescue CD for Windows: Free Download

 

[Arc]

Its OK mate. Frustrations are all possible.

But, doing random and haphazard things will not help you .... you have to proceed systematically.

You can see that even the motherboard is included in the list of suspects, and I also confessed that some failures I also have not faced yet. So there is no doubt that the issue is rare and difficult.

But as the goal is to discover the source and recover it, the works are all needed. Otherwise, we may take wrong decision, and spend energy and money on wrong stuff.

If is to keep a cool head when the situation is tough than usual We all are with you. But as the computer is with you, you have to perform the jobs

 

[v4l33]

Both scans were clean, also updated the NIC driver.







Will come back tommorow with the memtest86+ scan again, I seriously hope it will find errors this time, atleast that way I'll know what's wrong.

@ICit2lol Will try to find one at a local hardware store, if not then I'm gonna go to a service store and ask them to check the voltages for me.

 

[Arc]

Good going

Keep us informed

 

[Britton30]

I noticed you said you use Spybot S&D. I would consider uninstalling that as well, at least till the cause is found.
My reason is that I have tried it on w7 with horrible results, freezing, shut downs, PC got really slow. This program was excellent with XP and earlier though.

You can try either reinstalling the chipset driver or getting the previous version and installing it ignoring the warning you have a newer version installed. I would suggest trying first reinstalling the new one from a fresh download from ASrock.

 

[Arc]

Gary, please have a look at post #19? Your opinion is needed on AMD PCI Root Bus Lower Filter failure.

 

[Britton30]

Post edited Arc.

 

[Arc]

Post edited Arc.

Thanks

 

[v4l33]

I finally managed to get memtest86 to run overnight again, tho just for 6 passes (11.5h), don't have the time to leave it for longer atm because I rely on the PC for my work.



@Britton30 I uninstalled Spybot right after the scan, I don't like having software installed on my PC that I just use once a year, it's a habbit.
As for the drivers I will try to do that if I get another BSOD, would make sense since the crashes occured lately after numerous driver updates, one of them might be causing problems.

Currently waiting to see if uninstalling IDM and updating the NIC drivers will make a difference.

 

[Arc]

Memtest passed good (though 8 passes would be better).

Let us know how it goes.

 

[v4l33]

Got another crash today, this is the most serious so far, no crash dump created.



Went for a shower for about 20min, left MS Publisher and Firefox open, and this is what I got when i got back. I have no idea what's going on.

 

[ICIT2LOL]

Again my 2 cents worth may be worth trying one of these and I would start with the Kaspersky one

5 Bootable AntiVirus Rescue CD for Windows: Free Download

 

[v4l33]

Gonna format all the partitions and reinstall the OS today, tired of losing work because of these crashes, hopefully it's something software related and the problems will solve this way.

 

[v4l33]

Reinstalled Windows clean, 3 days later another BSOD. I'm inclining to believe is a hardware problem, but no idea what exactly, could it be the motherboard?

 

[Arc]

It appears that some issue with the display driver is there.

fffff880`02f8cf38  fffff880`02d4ffc1Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** 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+0x2efc1

Despite of using the latest one, 13.12 WHQL, as was seen in post #19.

If you know that the RAM, CPU, GPU and PSU are not failing, then the issue will be tagged with the motherboard.

 

[v4l33]

Well the last crash was during a game. And something I didn't mention regarding the GPU because I thought it was irrelevant. I got a Sapphire HD 7770 OC edition, the clock and memory are overclocked from factory, and before getting all these ntoskrnl.exe crashes I kept getting crashes related to the video driver but only in a few games, never while idle or low load. Decided to lower the frequencies a little and those errors dissapeared. Could it be that lowering the frequencies closer to stock AMD ones is causing these ntoskrnl.exe related crashes? Tho the GPU passes Furmark stress tests without a problem.

 

[Arc]

ntoskrnl.exe is not anything responsible for the crash, but it is the karnel on which the crash is occurring. When the dump recording mechanism fails to assign a cause, it blames the karnel itself, wrongly.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[v4l33]

Speccy link here.
Tested again with Furmark with Xtreme Burn-in and PostFX options enabled, at default OC factory clocks, no artifacts and no crashes, temperature evens out at 83 degrees Celsius.
This I don't get it, the GPU seems fine with OC clocks during burn-in tests but crashes in some games. Before the BSODs in games I get screen flickering because Windows reports GPU timeout and trying to recover, and after 3-4 attempts it goes to BSOD. Once I lower the GPU clocks these problems disappear so guess it's either the GPU, PSU or the PCIE bus. But a stress test should give a hint if there's a problem, shouldn't it? :/