Random BSODs: WIN7_DRIVER_FAULT ntoskrnl.exe

Hey there. I've been getting random BSODs (I say random as I haven't identified a specific event that has caused them) throughout this week. I haven't experienced a BSOD before, making these my first. I've gone through them with WinDBG and the only things that stood out to me were "WIN7_DRIVER_FAULT" and "ntoskrnl.exe". Again, this is the first I've ever come across a BSOD, so I've got no clue what I'm looking for. Hopefully you guys can identify what's going on.

I've uploaded the dump files here:
https://www.dropbox.com/sh/s2uk5qsrq...0HhQzeELa?dl=0

Apologies if I've made a mistake in this thread. Thanks in advance.

EDIT:

I didn't read the posting instructions. Please check my second post. Thanks.

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information like the dump files, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

The network driver needs to update.

Code:

fffff880`08d09418  fffff880`0511f92fUnable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 athrx+0xef92f

Update it from https://www.atheros.cz/atheros-wirel...et=38&system=6

The antivirus is also contributing to the BSOD.

Code:

fffff880`08d09d88  fffff880`01683d64Unable to load image \SystemRoot\system32\DRIVERS\avc3.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avc3.sys
*** ERROR: Module load completed but symbols could not be loaded for avc3.sys
 avc3+0x10d64

Uninstall BitDefender. Follow How to uninstall Bitdefender
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

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.

There are more failing modules too, but it will be better to go slow and having a close observation.

TrueJiNx said:

I installed and booted memtest86+. Immediately after starting the test, a whole load of errors (red lines) were displayed.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

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:

No code has to be inserted here.

It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.

It is a motherboard issue. The particular slot is bad.

The whole process may take a time, but it is worth doing. Do it, and let us know the result accordingly.

TrueJiNx said:

Thanks again for the reply. I took some time to test the individual RAM cards and slots and found out both RAM cards were faulty (I made sure by testing them in different memory slots).

Buy a new kit of RAM then. Make it sure that the RAM you are buying is authorized by the motherboard manufacturer.

Let us know how the computer is running after replacing the RAM.