Recurring BSODs every ~10 days. BlueScreenView pics attached. Any opinions on what might be wrong?

[evo23]

The BSODs started occurring roughly when I put in both a new SSD and WLAN card, but not sure if that's related or a coincidence.
BlueScreenView

Pics: http://imgur.com/a/heGpO

Specs: Windows 10, Home-Built i5-760. The newish SSD is a Samsung 850 EVO 250GB, and the network card is a TP-LINK TL-WN881ND Wireless N300.

Any advice greatly welcomed!

 

[Colif]

athwnx.sys - Driver for Qualcomm Atheros Extensible Wireless LAN (CB42/CB43/MB42/MB43) Network Adapter device driver. Shame latest driver appears to be win 8: http://www.tp-link.com/en/download/TL-WN881ND.html#Driver

Should be a law against selling old hardware still...

the other two things are windows

 

[evo23]

athwnx.sys - Driver for Qualcomm Atheros Extensible Wireless LAN (CB42/CB43/MB42/MB43) Network Adapter device driver. Shame latest driver appears to be win 8: http://www.tp-link.com/en/download/TL-WN881ND.html#Driver

Should be a law against selling old hardware still...

the other two things are windows

Do you think that Windows itself could be the culprit and needs to be reinstalled? Or both are the culprit?

 

[Colif]

The two named BSOD on the report are against the atheros driver. The problems started as soon as you plugged it in.. that isn't a coincidence. The other two can be caused by drivers as well as CPU. http://www.tenforums.com/bsod-crashes-debugging/25996-bsod-once-week-bug-check-code-0x00000124.html

hal.dll = hardware abstraction layer, it deals with software requests to hardware
ntoskrnl = new technology operating system kernel - part of windows that deals with driver requests.
both are critical parts of windows and when they crash, so does windows.

So i driver asked ntoskrnl to do something with hardware that caused hal.dll to crash. So two errors were caused by the part of windows that deals with driver requests conflicting with the part of windows that deals with hardware.

If you didn't have any errors before and they all started at same time, I would blame the new hardware. And I don't mean the SSD. SSDZ have no drivers and would cause different behavior than crashing hal.dll.