BSOD 0x00000050/0x0000007F - ntoskrnl/aswSnx.sys/win32k.sys

[adelexi]

Hello everyone,

Lately i have been running into several BSOD which started about a week ago and only seem to be getting worse. I got my first BSOD after installing the program Discord (voice chat program) it gave a faulty installation and a couple of hours later i got a BSOD. After restarting after the first BSOD i did not think much of it since it never happened before and reinstalled the discord program, it gave a faulty installation but the program itself worked. 2 days later everything was still going fine till i opened Discord. the second i opened the program i got a BSOD so after that looked for the discord program in the software removal screen but it was not there. So after that i removed the discord folder and i was hoping to be done with it. Today i got multiple BSOD while gaming/browsing so i started to look what caused it exactly.

I used the driver verifier and it automaticly crashed on startup. Since i could not read the dump files i used BlueScreenView. In the dump logs i could see Ntoskrnl.exe was always a part of the reason why it crashed.
There were other things that came up aswell in a few of them: dtsoftbus01.sys , aswsnx.sys and win32k.sys. After reading around on this forum i deleted the dtsoftbus01.sys since it was knows for causing BSOD. Yet that did not fix it. So after a bit of googling aswsnx.sys is related to avast so i looked that up and on the forum post i read they said it was a false error. To be sure i deleted Avast (avast removal tool in safe mode) and did a clean install. The funny thing is i did NOT go to BSOD when i did a driver scan with avast removed and after i installed it i did a BSOD from the driver scan again. But i think there is a deeper problem, maybe im crazy and it might just be avast only(which i never had problems with to be honest). But i cant read the dump files, i tried to, but they dont make me any wiser. Also not overclocking etc.

The first BSOD was a 0x00000050 and the last one a 0x0000007F, those numbers dont mean a lot to me but maybe it will help someone in figuring this out hopefully.

Seeing as how smart the people on here are with reading those files (are reading other post and seeing the reactions from some members) and how they found the problem i thought i will give it a try here in the hope that someone can help me. As requested for the BSOD post i attached the logs in the zip program. From what i got from it.

To be honest i dont know where to go from here and really dont know what to do, hoping its an easy fix.

Thanks for reading this and taking the time to awnser!


Edit:
did a sfc /scannow and errors came up which were not automaticly fixed it said, read the log but that did say it was fixed. ran sfc /scannow again and it was 100% oke. Also ran seatools and it was 100% oke. No idea if the SFC had anything to do with it. And no idea if they help with this problem at all but saw it suggested in multiple post so i thought why not.

 

[adelexi]

still looking for help so bumping to first page.

 

[axe0]

Hi adelexi,

Welcome to the 7forums.

I am sorry for the delay, there aren't many peoply active in this part of the forum.

Are you still requiring help?
If you do, please run the DM Log Collector tool again, upload the zip file and please give some description of the situation, what happened and what you were doing.