Page 2 of 2 FirstFirst 12
  1.    17 Jun 2017 #11
    Join Date : Jun 2017
    Posts : 9
    Windows 10
    Thread Starter

    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.
      My ComputerSystem Spec
  2.    17 Jun 2017 #12
    Join Date : Apr 2017
    Posts : 8,827
    windows 10 professional version 1607 build 14393.969 64 bit

    Rar files I cannot open. Please use the zip file to update the minidumps:
    BSOD - Posting Instructions - Windows 10 Forums
      My ComputerSystem Spec
  3.    17 Jun 2017 #13
    Join Date : Jun 2017
    Posts : 9
    Windows 10
    Thread Starter

    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.
      My ComputerSystem Spec
  4.    17 Jun 2017 #14
    Join Date : Apr 2017
    Posts : 8,827
    windows 10 professional version 1607 build 14393.969 64 bit

    Code:
    BugCheck C4, {2003, ffffd1057e9c9068, fffff800e86c0278, ffff9180679f2638}
    
    Probably caused by : memory_corruption
    Code:
    BugCheck C4, {2003, ffffad851cbd0be8, fffff80e71d002f8, ffffd5813b3f5638}
    
    Probably caused by : memory_corruption
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff803f3f80c35, 1, 110}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+1f5 )
    Please post any information that you have on each:
    Where did you see these?
    faceit.sys
    eseadriver2.sys
      My ComputerSystem Spec
  5.    18 Jun 2017 #15
    Join Date : Jun 2017
    Posts : 9
    Windows 10
    Thread Starter

    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.
      My ComputerSystem Spec
  6.    20 Jun 2017 #16
    Join Date : Jun 2017
    Posts : 9
    Windows 10
    Thread Starter

    Is there anything more I can do? I'm kind of stuck now
      My ComputerSystem Spec
  7.    20 Jun 2017 #17
    Join Date : Apr 2017
    Posts : 8,827
    windows 10 professional version 1607 build 14393.969 64 bit

    ...
      My ComputerSystem Spec

 
Page 2 of 2 FirstFirst 12


Similar Threads
Thread Forum
BSOD Memory Management - Both During Games and on Exiting Games
Have had a recent run of problems playing WoW, GW2 and today Diablo III. Mainly play WoW and have been plagued by Error #132 crashes (54 since 26 Jan), interspersed with the occasional BSOD Memory Management crash. Thought issue confined to WoW...
BSOD Crashes and Debugging
Solved BSOD playing games, so far 5 multiple BSOD errors, listed inside
Hello, So first of all, I am not a computer wizard. Some terms I might not understand as i've never had a problem like this before, but i'll try to enlist as much information as possible. Since last friday or so, i've suddenly encountered a...
BSOD Crashes and Debugging
BSOD when playing games intensive games 0x00000124
A friend of mine is having bsod issues when playing certain games, example: Rainbox six siege, Battlefield One (BETA) and a few others. Wondering if anyone can give us a clue as to the cause. Windows Format is done, but to no avail,...
BSOD Crashes and Debugging
Solved My games in full-screen minimizes by itself whenever I open it
Help me! Opening my games is not a problem at all, It's not minimizing at first, but when I plug in my headphones this pops up: 86248 "And then I'll check Headphone and then click OK" 86247
Gaming
Crash when open 2 games
I can't open 2 games. Of course i can play just 1, but i need to put one in taskbar (SAMP) and when i want to open other game (it doesn't matter what game ), the second game i open crashes. Any solution? 57640
Gaming
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:14.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums