New
#11
Attachment 139925 Here are the minidumps, the computer crashed instantly when verifier got enabled. Ntoskrnl.exe and faceit.sys seems to be the problems?
Last edited by Krezy; 17 Jun 2017 at 04:14.
BSOD when games are open.
-
-
New #12
Rar files I cannot open. Please use the zip file to update the minidumps:
BSOD - Posting Instructions - Windows 10 Forums
-
New #13
Attachment 140022 Here are the files. When I removed the anticheat programs from the verifier I didn't get any BSOD but I was lagging like crazy in windows. The anticheat programs was faceit.sys and eseadriver2.sys and gave me BSOD instantly.
-
New #14
Code:BugCheck C4, {2003, ffffd1057e9c9068, fffff800e86c0278, ffff9180679f2638} Probably caused by : memory_corruptionCode:BugCheck C4, {2003, ffffad851cbd0be8, fffff80e71d002f8, ffffd5813b3f5638} Probably caused by : memory_corruptionPlease post any information that you have on each:Code:BugCheck 1E, {ffffffffc0000005, fffff803f3f80c35, 1, 110} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+1f5 )
Where did you see these?
faceit.sys
eseadriver2.sys
-
New #15
On Sat 2017-06-17 18:39:44 your computer crashed
crash dump file: C:\Windows\Minidump\061717-5968-01.dmp
This was probably caused by the following module: eseadriver2.sys (ESEADriver2+0x2F8)
Bugcheck code: 0xC4 (0x2003, 0xFFFFAD851CBD0BE8, 0xFFFFF80E71D002F8, 0xFFFFD5813B3F5638)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Users\forci\AppData\Local\Temp\ESEADriver2.sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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: eseadriver2.sys .
Google query: eseadriver2.sys DRIVER_VERIFIER_DETECTED_VIOLATION
------------------------------------------------------------------------------------
On Sat 2017-06-17 10:28:45 your computer crashed
crash dump file: C:\Windows\Minidump\061717-6281-01.dmp
This was probably caused by the following module: faceit.sys (FACEIT+0x278)
Bugcheck code: 0xC4 (0x2003, 0xFFFFD1057E9C9068, 0xFFFFF800E86C0278, 0xFFFF9180679F2638)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\faceit.sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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: faceit.sys .
Google query: faceit.sys DRIVER_VERIFIER_DETECTED_VIOLATION
------------------------------------------------------------------------------------
This is from WhoCrashed
The one im posting down here is from an actual crash before all the tests.
On Tue 2017-06-13 19:23:33 your computer crashed
crash dump file: C:\Windows\Minidump\061317-7937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803F3F80C35, 0x1, 0x110)
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
Last edited by Krezy; 18 Jun 2017 at 05:08.
-
New #16
Is there anything more I can do? I'm kind of stuck now
-
Quote
Related Discussions
