Windows 10: BSOD when games are open.

Discus and support BSOD when games are open. in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, I'm getting BSOD a few times each week, only when I'm inside a game. I've ran the dump program Attachment 139328 . I also got memory.dmp files from... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Krezy, Jun 12, 2017.

  1. Krezy Win User

    BSOD when games are open.

    Hi, I'm getting BSOD a few times each week, only when I'm inside a game. I've ran the dump program Attachment 139328 . I also got memory.dmp files from the last crash.

    This is a very common bugcheck.
    Usually the exception address pinpointsthe driver/function that caused the problem.
    Always note this addressas well as the link date of the driver/image that contains this address.Arguments:

    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff803f3f80c35, The address that the exception occurred at
    Arg3: 0000000000000001, Parameter 0 of the exception
    Arg4: 0000000000000110, Parameter 1 of the exception

    I am happy for any answer you might give me.

    Krezy, Jun 12, 2017

  2. Computer keeps shutting down while playing games

    No it is not actually a BSOD.

    The screen goes blank then the power button automatically loses its light after 10-15 seconds.Then when I press the power button again, then the Laptop opens to the desktop with the game in the taskbar.The game keeps on running in the meantime.
    RohanRoy.13, Jun 12, 2017

    Microsoft i need your help , i have some problem thats is a BSOD KERNEL_MODE_EXCEPTION_NOT_HANDLED thats error message i got when i'm open my game but i have a recomended system to run thats game , please answer me , thanks
    MarcellinoMarcell, Jun 12, 2017
  4. zbook New Member

    BSOD when games are open.

    Hi Krezy,
    The logs were in a foreign language. I was not able to read them except for the word memory. If possible please resend them in English so we can read them.

    Code: BugCheck 1E, {ffffffffc0000005, fffff803f3f80c35, 1, 110} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+1f5 )[/quote]
    Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool
    zbook, Jun 13, 2017
  5. Krezy Win User
    Hello zbook,
    The logs are in English for me, don't know why you would get them in swedish.

    I will try the memtest86+ tonight, thanks.
    Krezy, Jun 13, 2017
  6. zbook New Member
    This is from the event log: Åtkomsthistoriken i registreringsdatafilen \SystemRoot\System32\Config\SAM rensades. 1 nycklar uppdaterades och 1 ändrade sidor skapades.
    zbook, Jun 13, 2017
  7. Krezy Win User
    Attachment 139505 Here is the logs, and in English this time. Sorry about that
    Krezy, Jun 13, 2017
  8. zbook New Member

    BSOD when games are open.

    The event log was unremarkable.

    Open administrative command prompt and type or copy and paste these commands:
    1) sfc /scannow
    2) dism /online/ cleanup-image /restorehealth
    3) chkdsk /scan

    Please report the results in the thread.

    For the memory testing it is important to make at least 8 runs. It sometimes takes runs in the teens to find problems.
    zbook, Jun 14, 2017
  9. Krezy Win User
    This is the results i got from command prompt.


    C:\Windows\system32>sfc /scannowBeginning system scan.
    This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.


    C:\Windows\system32>dism /online/ cleanup-image /restorehealth
    Error: 87DISM doesn't recognize the command-line option "cleanup-image".
    For more information, refer to the help by running DISM.exe /?.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


    C:\Windows\system32>chkdsk /scan

    The type of the file system is NTFS.Stage 1: Examining basic file system structure ... 197888 file records processed.
    File verification completed.
    5868 large file records processed.
    0 bad file records processed.Stage 2: Examining file name linkage ...
    266730 index entries processed.Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed.
    34422 data files processed.CHKDSK is verifying Usn Journal...
    39038944 USN bytes processed.Usn Journal verification completed.
    Windows has scanned the file system and found no problems.No further action is required.
    233849855 KB total disk space.
    82451328 KB in 152541 files.
    104612 KB in 34423 indexes.
    0 KB in bad sectors.
    311651 KB in use by the system.
    65536 KB occupied by the log file.
    150982264 KB available on disk.
    4096 bytes in each allocation unit.
    58462463 total allocation units on disk.
    37745566 allocation units available on disk.

    Krezy, Jun 14, 2017
  10. zbook New Member
    On the dism command please rerun with dism /online /cleanup-image /restorehealth
    It should display that it completed successfully.
    zbook, Jun 14, 2017
  11. Krezy Win User
    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0

    Image Version: 10.0.15063.0

    The restore operation completed successfully.

    The operation completed successfully.


    I also ran the memtest+ tonight for 8 hours, I didn't get any errors and was on test 9 when I stopped it.
    Krezy, Jun 14, 2017
  12. zbook New Member
    Please back up all of your files if they are not already backed up.

    Windows driver verifier stimulates drivers to find misbehaving drivers.
    Once a misbehaving driver is identified the driver or its application/driver is uninstalled.
    A replacement driver or application is then chosen and the replacement driver/application is then tested.
    The drivers are tested and tested until you can use the computer for 36 hours without a bsod.

    Before using windows driver verifier you must know how to turn windows driver verifier off.
    Windows driver verifier will keep producing bsod until you turn it off or have no misbehaving drivers.
    In order to turn windows driver verifier off you must use the windows recovery or advanced troubleshooting menu.
    In the menu you will navigate to startup options (not startup repair).
    In startup options you will choose option #6, safe mode with command prompt.
    Typing the command: verifier /reset will turn off windows driver verifier.
    Once windows driver verifier is turned off you will be able to return to the desktop.

    Once you are back on the desktop you will run two software programs to identify the misbehaving drivers.
    Download and install both bluescreenview and whocrashed.

    Blue screen of death (STOP error) information in dump files.
    Resplendence Software - WhoCrashed, automatic crash dump analyzer

    Each time you return to the desktop run these software programs to identify the misbehaving driver.
    Often the two software programs will produce the same result but at times one of them may provide additional useful information.
    Once you identify the misbehaving driver you will uninstall the driver or the application. Then you will go to the computer manufacturers web site and download the most up to date driver. If the most up to date driver fails you may need to go to last known working driver. Sometimes software has drivers that produce bsod. The software then needs to be uninstalled and reinstalled. Sometimes there is software that cannot be used without a possible bsod in the computer environment and in these case an alternative software could be chosen.

    Open administrative command prompt and type or copy and paste this command:
    shutdown /r /o /f /t 00
    Upon reboot you will be in the windows recovery or advanced troubleshooting menu. You will navigate to startup options then choose #6 safe mode with command prompt.
    Once you are comfortable navigating through the menu and rebooting to the desktop you will need to be able to get from a bsod to the windows advanced troubleshooting menu.
    And once you feel comfortable getting to the recovery menu and getting to the desktop you then can use windows driver verifier.
    To start windows driver verifier you will type verifier in the left lower corner search menu.

    These are two important links to study before using windows verifier.
    The first link has information on how to turn automatic restart off by unchecking the default automatic restart.
    With the automatic restart off you will have time to view the bsod screen. On the screen it will display a stop code: the most frequent is driver verifier detected violation. At times it will also display the misbehaving driver typically *.sys. If you see the misbehaving driver please record it for later use.

    The second link are the settings for using Windows driver verifier.
    Once you have made the customized settings you are then ready to have the first bsod. Again you should feel comfortable getting to the windows recovery menu, navigating to safe mode with command prompt and typing the command verifier /reset

    There are two main methods for using windows driver verifier and managing the misbehaving drivers. One method is to uninstall and reinstall drivers and then test the reinstalled drivers. An alternative method is to uninstall all misbehaving drivers and use default Microsoft drivers. Once you no longer have bsod you can then install drivers one at a time and test for misbehaving drivers. You can choose either method. It's preference. The important point is to find a methodical way of addressing the misbehaving drivers and bsod so that they are eliminated and preventative maintenance is performed.

    When you have bsod please update the zip file or create a new one so we can debug the minidumps and guide you in the management.

    BSOD Finding and fixing them - Microsoft Community

    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    zbook, Jun 14, 2017
  13. Krezy Win User

    BSOD when games are open.

    Attachment 139925 Here are the minidumps, the computer crashed instantly when verifier got enabled. Ntoskrnl.exe and faceit.sys seems to be the problems?
    Krezy, Jun 16, 2017
  14. zbook New Member
    zbook, Jun 17, 2017
  15. Krezy Win User
    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.
    Krezy, Jun 17, 2017

BSOD when games are open.

  1. BSOD when games are open. - Similar Threads - BSOD games are

  2. BSOD When Gaming

    in Windows 10 BSOD Crashes and Debugging
    BSOD When Gaming: Good afternoon, I have been experiencing a variety of BSOD issues. My drivers are up to date, Windows is up to date, etc. My gut is that it's an issue with the memory, but I want to be certain before replacing it. Today's crashes, based on BlueScreenView, are a result of -...

    in Windows 10 Drivers and Hardware
    BSOD WHEN GAMING: Dear,anyone can help me find the problem, i always get the BSOD when i play the andrpid emulator WIN10 new laptop bought from last year. I update the driver already, BSOD Code is different every times. the new one is " Microsoft (R) Windows Debugger Version...
  4. BSOD when gaming

    in Windows 10 BSOD Crashes and Debugging
    BSOD when gaming: Hello, recently i've started to get random BSOD again when playing some specific games, usually it just goes with sound lag and then to BSOD, I would appriciate any help related to this issue. The app didnt create zip so i made it my self with all the files! Thanks in...
  5. BSOD When Playing Game

    in Windows 10 BSOD Crashes and Debugging
    BSOD When Playing Game: Hi Everyone I have been having BSOD problems when i play game that used alot of graphic such as Dota 2 , Overwatch etc. The BSOD that i getting is Internal_Video_Scheduler_Error , Video_Tdr_Error and sometimes the graphic driver has been stopped and successfully recovered...
  6. BSOD when gaming

    in Windows 10 BSOD Crashes and Debugging
    BSOD when gaming: Hello, First post here. I am looking to troubleshoot a recurring BSOD that I have been experiencing for awhile. The issue usually occurs when playing a resource-intensive gaming title (BF4 or GTAV). I have an r9 390 now, but I had similar issues when I was using a gtx660....
  7. BSOD when shutting down or opening a game.

    in Windows 10 BSOD Crashes and Debugging
    BSOD when shutting down or opening a game.: I can't open dumps from this machine (such as the one attached) with WinDBG and I'm not sure why (I did verify I can open the test dump of the instructions). Code: Symbol search path is: SRV*C:\SymCache*Symbol information Executable search path is: Unable to load image...
  8. BSOD when gaming and not gaming

    in Windows 10 BSOD Crashes and Debugging
    BSOD when gaming and not gaming: BSOD persists after fresh install of Windows 10 from windows 8.1, happens when playing heroes of the storm quite often but has happened while browsing pinterest/facebook. 18888
  9. BSOD when playing games

    in Windows 10 BSOD Crashes and Debugging
    BSOD when playing games: Hi, I keep having the blue screen when I'm gaming and its says something like etd.sys or whatever it is. Hope that I can get some help from here. 91885
  10. Bsod when starting a game

    in Windows 10 BSOD Crashes and Debugging
    Bsod when starting a game: Hey guys, When im using my PC for normal use (internet,word,music, etc..) I have no problem. But the moment I start up a game I get a bsod. Does anyone know what the problem is and how to solve it? Thanks in advance! 34221