Plenty of BSOD's, for apparently no reason, all with different error messages

[Swerdy5]

Since two days ago, I've gotten an alarming number of BSOD's. They all happen at random times, whether I'm playing CS:GO or I'm sitting at the login screen. They have gotten very frequent, to where I can maybe get 10 minutes of uptime before it crashes again. Any help is appreciated.

Here are my computer specs: http://pcpartpicker.com/user/Swerdman55/saved/PnbPxr

I've also tried running my computer with one RAM stick at a time, but it happened with each one individually.

I'm currently running memtest, I'll update this post when I get the results on any passes or fails. (It is currently at 2 passes and no errors)

Here is a link to a zip file of all the dump files: http://www.filedropper.com/euclydes-tue0524201617230265

 

[Colif]

I can't read error logs but this can: http://www.resplendence.com/whocrashed
can you download and run it. It will look at your logs and create a summary, maybe even point out the cause

copy/paste results in here and I see if I can help you

 

[Swerdy5]

I can't read error logs but this can: http://www.resplendence.com/whocrashed
can you download and run it. It will look at your logs and create a summary, maybe even point out the cause

copy/paste results in here and I see if I can help you

I will try this when memtest has finished running. I accidentally marked this as the best solution, and I don't know how to undo it...

 

[Colif]

i fixed the best post thing

 

[Swerdy5]

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 5/24/2016 10:44:20 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x18F51)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED



On Tue 5/24/2016 10:39:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-18688-02.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880016B3BD1)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF880016B3BD1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 5/24/2016 10:37:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-19234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F3D0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5/24/2016 10:27:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-41917-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003A42338, 0xFFFFF880211C3C10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5/24/2016 10:17:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-18314-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880014A9BD1)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF880014A9BD1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 5/24/2016 10:07:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-21621-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003A04338, 0xFFFFF8802186DC10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5/24/2016 9:47:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-42837-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1D63D0)
Bugcheck code: 0x50 (0xFFFFF8E0009EE9BC, 0x1, 0xFFFFF800037C2FA2, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 368.22
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 368.22
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.22 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Tue 5/24/2016 9:32:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-22401-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880014CBBD1)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF880014CBBD1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 5/24/2016 9:27:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-18688-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF80003809617)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5/24/2016 9:26:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052416-17986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003864680, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

22 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.22 , NVIDIA Corporation)
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Colif]

So its not often i read a summary and find out there are new Nvidia drivers I don't have yet... that doesn't help really, I wish Nvidia could write drivers better these days. You could try doing this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

are you using a wireless lan card? it would seem it is the cause of many of the errors. NDIS.sys is to do with LAN drivers

not a lot of new drivers on your mobo web site, I would suggest running driver booster and seeing if it can find a new Atheros driver for your usb device... as well as motherboard drivers.

 

[Swerdy5]

I re-installed my NVIDIA driver, hopefully that helps.

Yea, I have a wireless LAN card. It's a TP-LINK card. This one: http://www.tp-link.com/lk/products/details/cat-11_TL-WN851ND.html

I noticed it was flagging the Atheros driver... but when I google it, it looks like Atheros makes their own cards. Why would I have that driver when I don't have one of their cards?

Either way, I'll download driver booster and let you know what it says.

 

[Colif]

try this: http://www.uninstallsupport.com/uninstallsoftware/uninstall-Atheros-Wireless-Lan-Driver-7.2.0.179.zip-7.2.0.179-completely.html#win7 (don't buy the software they offer)

i don't know why you have the drivers installed, maybe it was an older lan card? surely tp link make their own drivers (see here: http://www.tp-link.com/lk/download/TL-WN851ND.html#Driver)

 

[Swerdy5]

I went and uninstalled my network adapter drivers, then downloaded and installed the ones from TP-Link's website.

Then I went ahead and ran Driver Booster, it told me around 30 drivers were out of date, and one of my network adapter drivers was faulty. I went and updated them all through Driver Booster.

Hopefully this does the trick! I can't really test it other then wait to see if my computer Blue Screens again. Thanks for the help! I'll let you know if I get more crashes.