BSOD while playing games

[Rodady]

Well... The problem I have is related to computer crashing, more specifically the bsod. It occurs while im playing some games, as csgo, and it doesnt occur instanty. Instead, it does at mid-game. Usually between 10 and 40 minutes into playing a match (not in the lobby). The error shown changes from one crash to another, but the ones i have seen the most are 'kernel security check failure' , 'page fault in nonpaged area', and 'system service exception'. If I get a different one, I will post it. For now, I will show you the data recorded in the event log:
Log Name: System
Source: Kernel-power
Event ID: 41
Level: Critical
user: SYSTEM
Task category: 63
Keywords: (70368744177664),(2)
Thanks in advance, if you need any more data, just ask please.

 

[Rodady]

Reinstall windows direct x

Just did it, uninstalled dx12 and reinstalled it, still not fixed

 

[Rodady]

so its not the gpu then, as you lead me to believe the igpu also had same stutter? you probably don't have intel vga drivers on PC as you can't have them and the Nvidia ones installed at same time (that only works on laptops)

I don't understand how removing the gpu driver has made PC react like this
its not gpu as its same with igpu
its not drivers - as its laggy in safe mode

Do you have the latest bios for motherboard?

Aaaalright I updated the BIOS and i think it has enhanced my system but it has not solved the laggy issue... I still wonder how reinstalling drivers has caused it

Stuttering, freezing, or lag (network issues)?

It is definitely not network issues, I called it lag because I did not really know how to name it. I have looked up some things and looks like stuttering. It is not freezing because the image does not stop or freeze for long time, rather like fps drop but without them truly dropping (while playing games, the fps 'count' does not drop, and it also happens on the desktop with nothing open but a single window). However, I have seen a youtube video literally called 'screen stuttering' and somehow it looks similar, but without the fast-slow rendering, just as if it was low in fps.
I dont know if i have explained myself well, I hope you understand it with that poor description

 

[okcnaline]

See if setting max framerates to 144 FPS helps.

 

[Rodady]

See if setting max framerates to 144 FPS helps.

I have a 60 fps monitor and I dont even have the chance to change it to 144 fps. I can switch it to 75, but for sure it is not helping

 

[okcnaline]

Limit the framerate ingame to 60 FPS then.

 

[Rodady]

Limit the framerate ingame to 60 FPS then.

Well I had already tried, but just did again to check and it does not solve anything.

 

[Rodady]

I have an update which might help you. I have noticed that since I reinstalled the drives and the bsod thing got solved, the nvidia utilities have not been working well. Also, I have reinstalled the drivers manually and with Geforce Experience and it kept doing the same

For example, now, when I open the Nvidia Geforce Experience, it gets out of connection and shows me no more than my games and the drivers. When I try to do a custom installation (so i can do a clean one), it displays 'error' at the window where I can decide whatcomponents to install. It does not even show the 'install' button, only the 'close' one.
But if I install the drivers manually, downloading the installer from Nvidia website, I have no problem, or at least no error is shown on the screen.

Another example is the Nvidia details i can get from right clicking in the desktop and then going to my GPU details. Even though my computer recognises it, most of the times the window stops working when i click on update drivers from that screen or in details.

 

[okcnaline]

Have you done a memory test? Something is leaking - and I don't like it one bit.

 

[Rodady]

Have you done a memory test? Something is leaking - and I don't like it one bit.

Yup, I have, and it does not show any error message during or after the test

 

[Colif]

Have you done a memory test? Something is leaking - and I don't like it one bit.

what do you mean leaking?

@op what is your ram/hdd usage like? more or less or normal?

Have you done a memory test? Something is leaking - and I don't like it one bit.

Yup, I have, and it does not show any error message during or after the test

what test did you run?

 

[Rodady]

Have you done a memory test? Something is leaking - and I don't like it one bit.

what do you mean leaking?

@op what is your ram/hdd usage like? more or less or normal?

Have you done a memory test? Something is leaking - and I don't like it one bit.

Yup, I have, and it does not show any error message during or after the test

what test did you run?

chkdsk /f /r (i think its written like that)
mdsched.exe

 

[Colif]

if its a memory leak, the PC would be using more ram or hdd than usual and it is likely to be caused by a driver. That is why i asked Okcaline what type of leak as those tests won't find it.

So is PC using more ram/hdd than usual? as that will cause slow down as the PC will be moving data from ram to storage to cope with it.

As for memory test, I would try running memtest86 on your ram sticks, 1 at a time. Any errors are too many as perfect score is 0. It makes a bootable USB so can run without windows.
I would be surprised if its a physical memory problem as you aren't getting bsod anymore and I find bad ram will show other signs. Memtest won't find memory leaks normally either as they are a software bug

 

[Vic 40]

Tried different peripherals too? With me my Func mouse somehow created lag,using a different one made things more smooth.

 

[Rodady]

Alright i was just about to do the memory test Colif proposed, but first I decided to check what vic 40 said because its faster. Anyway, I have a RAT TE and installed its drivers. Then, the computer instantly bsod'd and would not even pass the desktop loading screen, it was in a bsod cycle. I got into safe mode (in order to not load the drivers) and it did not crash, so it was surely the new mouse drivers I installed (which probably were removed with the tool i used to remove the NVIDIa ones). I reinstalled the drivers and it kept doing bsod on the normal boot mode, so I disabled the drivers check (verifier /reset) and it works perfectly for now. No lag, no bsod, nothing. I have got to the conclussion that the mouse drivers made some kind of conflict with the nvidia ones and caused them to crash. I have run the WHOCRASHED on the last bsod I had, I post them here if you want to check something


On Thu 25/05/2017 22:50:32 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-4875-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1F30)
Bugcheck code: 0xC9 (0x220, 0xFFFFF80B11351F30, 0xFFFFEF815380ECA0, 0xFFFF8883A327F040)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\hidclass.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Biblioteca de clases HID
Bug check description: This is the bug check code for all Driver Verifier
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 Thu 25/05/2017 22:50:32 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!XdvHibernationNotification+0x10547)
Bugcheck code: 0xC9 (0x220, 0xFFFFF80B11351F30, 0xFFFFEF815380ECA0, 0xFFFF8883A327F040)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the bug check code for all Driver Verifier
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.
Google query: Microsoft Corporation DRIVER_VERIFIER_IOMANAGER_VIOLATION



On Thu 25/05/2017 22:50:24 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-11828-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Thu 25/05/2017 22:42:40 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-5000-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1F30)
Bugcheck code: 0xC9 (0x220, 0xFFFFF807C83E1F30, 0xFFFFC30777736CA0, 0xFFFFC38FD07EB5C0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\hidclass.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Biblioteca de clases HID
Bug check description: This is the bug check code for all Driver Verifier
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 Thu 25/05/2017 22:42:33 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-11859-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR





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

6 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has 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:

verifierext.sys (Driver Verifier Extension, Microsoft Corporation)

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.

Thanks for all the advice guys, you helped me so much ^^

 

[Colif]

hidclass sure points at the mouse drivers since we weren't having BSOD before the change and a search reveals its likely to be USB input device

I mean, we can create minidumps and see if there is anything else hiding
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Rodady]

hidclass sure points at the mouse drivers since we weren't having BSOD before the change and a search reveals its likely to be USB input device

I mean, we can create minidumps and see if there is anything else hiding
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Unfortunately I have been playing for around 30 minutes and it happened again TT
Looks like installint the mouse (RAT TE) drivers has erased the lag but again has caused the pc to crash on some games (as far as i know only csgo is problematic, as I managed to solve WoW's crashes). I have done the steps in order to create minidump in c windows/ and will upload it asap. Also, from the crashes that i have got they are usually the same 2 files the ones that cause them.

Here, the last crashes I have had

On Fri 26/05/2017 17:07:29 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-5828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800296742B6, 0xFFFFBD011C05C930, 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 Fri 26/05/2017 17:07:29 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800296742B6, 0xFFFFBD011C05C930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Thu 25/05/2017 23:29:30 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-5968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1A (0x41792, 0xFFFFAD3FFDFA4110, 0xBF00000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

MINIDUMP



https://mega.nz/#F!FUsHyJTQ!CqzMrpaHiBf1lM59pWNK7Q

 

[gardenman]

Hi, WhoCrashed reported:

Spoiler

On Thu 5/25/2017 4:50:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-4875-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1F30)
Bugcheck code: 0xC9 (0x220, 0xFFFFF80B11351F30, 0xFFFFEF815380ECA0, 0xFFFF8883A327F040)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
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.

In addition, the Win 10 Kit Debugger reported: https://pastebin.com/kCwreKBb

I can't help you with these. Wait for Colif or someone else to reply.

 

[Colif]

Hi, WhoCrashed reported:

Spoiler

On Thu 5/25/2017 4:50:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-4875-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1F30)
Bugcheck code: 0xC9 (0x220, 0xFFFFF80B11351F30, 0xFFFFEF815380ECA0, 0xFFFF8883A327F040)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
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.

In addition, the Win 10 Kit Debugger reported: https://pastebin.com/kCwreKBb

I can't help you with these. Wait for Colif or someone else to reply.

The more i look at those, the less I feel I know. They all seem to say code corruption and Memory corruption large, these days, I am sure the ones from last year used to tell the name of the file responsible in the text.

 

[gardenman]

I agree, but WhoCrashed said it was hidclass.sys. I looked it up and it said maybe a keyboard or mouse, another page said possibly a USB driver. It also says "HIDCLASS!HidpMajorHandler+0" in the debugger.

I don't remember if you had the OP try a different keyboard and mouse yet or not. I would also unplug ALL USB devices and test it for a while. Then start hooking them up one at a time over a long period to see if you catch it. It could be a single USB device, or could be the USB drivers itself. But I'm just taking a wild guess.

 

[Colif]

Go to the download page for motherboard , choose win 10 and in the utilities tab, download AI Suite. I only suggest this for one tool, EZ Update. If you have it already, don't dl it again (obvious). I wouldn't let it run at start up and don't use its 5 step optimization as don't need a software overclock to complicate matters. But if you run EZ Update it will check the Asus site against your installed drivers and confirm you have latest. If the problem is a USB driver for motherboard, this will at least tell you if you have the latest

Don't install new BIOS if it offers one. Unless you on a really old one, it may not be necessary at this stage.

I knew hidclass was USB and guessed it was related to the mouse driver he updated recently, didn't click it might have set off another driver

 

[Rodady]

Go to the download page for motherboard , choose win 10 and in the utilities tab, download AI Suite. I only suggest this for one tool, EZ Update. If you have it already, don't dl it again (obvious). I wouldn't let it run at start up and don't use its 5 step optimization as don't need a software overclock to complicate matters. But if you run EZ Update it will check the Asus site against your installed drivers and confirm you have latest. If the problem is a USB driver for motherboard, this will at least tell you if you have the latest

Don't install new BIOS if it offers one. Unless you on a really old one, it may not be necessary at this stage.

I knew hidclass was USB and guessed it was related to the mouse driver he updated recently, didn't click it might have set off another driver

A couple of days ago Iupdated the bios to the latest and i got really scared because i got the american megatrends screen xD. Then it restarted and everything is fine now,

If you feel it could solve anything, I could try to play with a completely different mouse to see if it still triggers the bsod error

 

[Vic 40]

If you feel it could solve anything, I could try to play with a completely different mouse to see if it still triggers the bsod error

Please do for testing.