ntoskrnl.exe and others causing all sorts of BSODs

TheRandomGuy · 30 Jan 2014

Hi there.

Firstly here are the specs to the machine in question:
CPU: AMD Athlon 54 X2 5200+ 2.7GHz.
Mainboard: Biostar GF8200E.
RAM:
1x Chaintech DDR2 800MHz 2GB module.
1x Some other brand DDR2 800MHz 2GB module that I acquired at a later stage.
HDD:
1x SATA2 500GB Seagate drive (primary).
1x SATA2 320GB Seagate drive (secondary).
PSU: Cooler Master Extreme Power 550W.
GPU: GeForce GTS450 AMP! running v332.21 drivers.
OS: Windows 7 Professional 64 bit.
AntiVirus: Kaspersky Internet Security 2014.
KB: Razer Lycosa.
Mouse: CM Storm Sentinel Advanced.

Over the past few weeks my PC has been BSODing. At first it would do so only after exiting a high performance game like War Thunder (not heat related).

This at first I thought was caused by Nvidia drivers. I then updated said drivers and it made no difference. Running the PC in safe mode works perfectly which led me to believe it was indeed driver related. I wasn't able to create minidump files for some reason even when the correct options were set up so there was no way for me to accurately determine the cause back then. I decided to just format my drive and re-do everything. However, even without the Nvidia drivers it would still BSOD randomly. I decided to do some Windows updates just in case but this didn't help either. I went as far as installing Windows on another hdd just in case it was a hdd issue.

Recently the PC has been BSODing as soon as it gets to the desktop and sometimes, if I'm lucky, it'll last a little longer. It's not a heat issue as I've monitored temperatures before the event and they seem normal.

After the re-install I am now able (for some reason the options actually work now) to save dump files after a BSOD and BlueScreenViewer is telling me that these BSODs are being caused by various drivers such as ntoskrnl.exe, tcpip.sys, Ntfs.sys, ndis.sys, win32k.sys and one caused by Kaspersky's kneps.sys.
90% of these BSODs are caused by Windows drivers. This is probably why it would BSOD even after a fresh Windows install.

What I've determined:
- Highly unlikely a hard drive problem. Otherwise it would mean both hard drives have the same error even when check disk reports no problems on either of them.
- Not a power issue. I've tested the system using a new PSU and there's no change.
- It doesn't BSOD in safe mode so would this mean it isn't the RAM? It BSODs with either RAM card installed so it means it's either both RAM cards, neither RAM cards, one of the two, or the RAM slots themselves.

I've also done a re-build of the system just in case it was dust or something. In an extremely clean state it ran well with a huge reduction in BSODs. But then they slowly crept back to the stage it's in now.

Anyway, I've added a few dump files ranging from the 29th to today(30th) Jan.
(I have minidump files dating as far back as 16 Jan if you'd like me to add them)

Let me know what you guys think.
Thanks.

Arc · 30 Jan 2014

Hi TheRandomGuy.

We are seeing a lot of software/drivers are failing those are enough to cause BSODs, but there is something more important error report.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff8d, 1, fffff800030afd0b, ff00000000000000}


Could not read faulting driver name
Probably caused by : hardware ( nt!FsRtlUninitializeOplock+ff )

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

A hardware failure may cause any sort of other failure. So it is the first and most important to check the hardware's part.

Stress test the CPU.
Hardware - Stress Test With Prime95

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

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.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

It seems to be an old biostar. 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: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Will decide the next courses of action seeing these results.

peebee · 30 Jan 2014

I would also remove Kaspersky but am leaning with Arc that this is a hardware problem. You've done a lot of the ground work troubleshooting but just because you can load Safe Mode and it runs doesn't mean it's not a memory issue. You need to run a test like Memtest86+ that will stress each row and cell. I would start there.

TheRandomGuy · 02 Feb 2014

I'm not overclocking by the way.
I'll start with Memtest86 and see what happens.

Thanks guys for the assistance, I'll let you know of any updates.
JP.

TheRandomGuy · 03 Feb 2014

Alright, so I ran memtest86+ for 9 passes with both memory modules installed which took about 13 hours. It reported no errors at all so that rules out the RAM.

I did mention the wattage of the PSU in my original post (550W), but I've already ruled that out. PC BSODs all the same on a new CM GX2 Extreme 475W.

So all that's left to test is the Graphics card and CPU.

Arc · 03 Feb 2014

Good to know that the memory is free from issues.

Let us know about the other tests too.