BSOD 0x00000050 gaming Windows 7

deadlytivo

Distinguished
Jan 15, 2013
60
1
18,535
I've been getting a series of BSOD's whilst gaming.

These range from 0x000003b, which I downloaded a hotfix for, and the problem ceased, aswell as 0x00000017 or something, which seemed to have whimsically dissipated. Now, I've been getting the error code 0x0000050.

Here is the dump file from bluescreen view :

Dump file : 050615-9484-01.dmp
Crash time : 6/05/2015 2:49:33 PM
Bug check string : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check code : 0x00000050
Parameter 1 :ffffa218`a331a637
Paramater 2 : 00000000`00000000
Parameter 3 : fffff800`034cd89c
Parameter 4 : 00000000`00000007
Caused by driver : aswKbd.sys
Caused by address : aswKbd.sys+7e3c6a0
Processor : x64
Crash address : ntoskrnl.exe+72a40
Full path : C:\Windows\Minidump\050615-9484-01.dmp
Processor count : 4
Major version : 15
Minor version : 7601
Dump file size : 385,842
Dump file t ime : 6/05/2015 2:50:12 PM

Here is what whocrashed reported on the home version :

On Wed 6/05/2015 4:49:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050615-9484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x50 (0xFFFFA218A331A637, 0x0, 0xFFFFF800034CD89C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Computer specs :


Motherboard : z87x-oc
Gpu - Evga GTX 770
Cpu : i5 4670k 3.4ghz @ 4.4ghz (ive had t his overclock for over a year now)
Vengeance ddr 3 ram : 8gb @ 1600mhz
 
Solution
aswKbd.sys = avast! Keyboard Filter Driver

this can be a bug in the avast driver or more likely any filter driver installed on your machine.

normally to figure this out you have to change your memory dump type to kernel from minidump, run cmd.exe as an admin then run
verifier.exe /standard /all
then reboot your system and wait for the next bugcheck. Put the memory.dmp file on a server and post a link. With luck it will name the bad driver or someone can look in the windows debugger and use the debugger command
!fltkd.filters 1
and maybe see a driver with a bad link (pretty common)

use verifier.exe /reset to turn off verifier.
aswKbd.sys = avast! Keyboard Filter Driver

this can be a bug in the avast driver or more likely any filter driver installed on your machine.

normally to figure this out you have to change your memory dump type to kernel from minidump, run cmd.exe as an admin then run
verifier.exe /standard /all
then reboot your system and wait for the next bugcheck. Put the memory.dmp file on a server and post a link. With luck it will name the bad driver or someone can look in the windows debugger and use the debugger command
!fltkd.filters 1
and maybe see a driver with a bad link (pretty common)

use verifier.exe /reset to turn off verifier.
 
Solution

deadlytivo

Distinguished
Jan 15, 2013
60
1
18,535


Yeah, it's a keyboard related issue.

I remember glancing at a similar problem yesterday, mentioning something to do with a keyboard, so I decided to keep the razer naga application open.

Haven't had a problem since.

Thanks