Share via

Computer Reboot During Gameplay

Anonymous
2024-10-31T06:01:55+00:00

I have my computer rebooting (no blue screen, just reboot in the middle of a game) in the middle of playing a game.

I can't figure if this is a hardware issue or software issue.

System Event Logger has an Error
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffffc08c54be2460, 0xfffff8006b690a40, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\WINDOWS\Minidump\103024-15984-01.dmp. Report Id: 7f8adc7b-9848-4476-b034-93480b5d32ee.

I also got the dmp file, but don't know how to view it for more info, any help would be appreciated.

https://drive.google.com/file/d/1I7zaqHHkr5LxYBLa5j2d0BqJlI5uk2O5/view?usp=sharing

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

6 answers

Sort by: Most helpful
  1. Anonymous
    2024-11-04T06:50:59+00:00

    Had another black screen and reboot today.

    VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffff8a83fbbb6460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff806acca0a40, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data.

    ...

    SYMBOL_NAME: nvlddmkm+1700a40
    MODULE_NAME: nvlddmkm
    IMAGE_NAME: nvlddmkm.sys

    Did some more research, disabled Low Level IO in MSI Afterburner, let's see how it goes.

    Regards,

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-11-04T04:35:04+00:00

    Hi Sakiko

    I have already done that, and it is smooth by far with Riot Games.

    However, I also disabled XMP, so I gave away little bit of RAM processing, no blue screens yet. After some time I will enable XMP and keep it that way to see if more issues occur!

    Still want to figure the reason behind VIDEO_TDR_FAILURE (116).

    Thanks,

    Was this answer helpful?

    0 comments No comments
  3. Sakiko 39,240 Reputation points Independent Advisor
    2024-11-01T16:40:04+00:00

    Thanks for the update.

    Your dump file shows Vanguard causing the blue screen, which usually comes from Valorant.

    Please uninstall the game temporarily and see if the blue screen still occurs.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-11-01T06:07:22+00:00

    Hi Sakiko

    Thanks for your response.

    I disabled XMP, and I enabled the Verifier.

    After the restart, system had blue screen 3 times in a row, and it went into restore mode, and after the restore it successfully booted.

    These issues started when I reset my Windows and installed fresh Windows 11.

    I checked the Bugcheck details, and it is giving me

    VIDEO_TDR_FAILURE (116).

    Please also note that I tried to remove the Drivers using DDU tool and installing Geforce Experience from scratch.

    After the Verifier, there is another DMP file, this one says DRIVER_VERIFIER_DETECTED_VIOLATION (c4), here is the link to dmp file.
    I can't figure which driver is it, can you please advise? https://drive.google.com/file/d/1N3PdIeTM50SrHQZS-3uC_YiWRLiOIfUY/view?usp=sharing

    ___

    I also found Critical error in Event View after the changes, there seems to be no DMP file, but the content is as follows.

    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    • <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
    • <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /><EventID>41</EventID><Version>9</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2024-11-01T05:52:24.0934036Z" /><EventRecordID>4364</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>Arm</Computer><Security UserID="S-1-5-18" /></System>
    • <EventData> <Data Name="BugcheckCode">196</Data><Data Name="BugcheckParameter1">0x62</Data><Data Name="BugcheckParameter2">0xffffa2091148af70</Data><Data Name="BugcheckParameter3">0xffffa209292f3310</Data><Data Name="BugcheckParameter4">0x1</Data><Data Name="SleepInProgress">0</Data><Data Name="PowerButtonTimestamp">0</Data><Data Name="BootAppStatus">0</Data><Data Name="Checkpoint">0</Data><Data Name="ConnectedStandbyInProgress">false</Data><Data Name="SystemSleepTransitionsToOn">0</Data><Data Name="CsEntryScenarioInstanceId">0</Data><Data Name="BugcheckInfoFromEFI">false</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">0</Data><Data Name="LongPowerButtonPressDetected">false</Data><Data Name="LidReliability">false</Data><Data Name="InputSuppressionState">0</Data><Data Name="PowerButtonSuppressionState">0</Data><Data Name="LidState">3</Data></EventData> </Event>

    Was this answer helpful?

    0 comments No comments
  5. Sakiko 39,240 Reputation points Independent Advisor
    2024-10-31T06:34:06+00:00

    Hello, I'm here to help.

    The information you have provided indicates a problem with the system kernel, usually caused by a driver, which we need to verify further. Please first create a restore point for your system, then please refer to this article: https://learn.microsoft.com/en-us/windows-hardw... to enable driver verifier. In the third step select "Automatically select all drivers installed on this computer", wait for a couple of new blue screens and then collect 2-3 new dump files and share the new dump files with me.

    If the computer has any automatic overclocking features enabled (including XMP, PBO, etc.) or manual overclocking, please restore the defaults first.

    Driver verifier puts heavy pressure on the drivers in your system to troubleshoot drivers that are in poor condition or misbehaving. It is normal for your computer to run slowly after driver verifier is turned on. The computer will also crash more frequently and generate dump files during this process.

    If your system fails to boot after driver verifier is turned on or enough dump files are generated, please restore via the restore point.

    Please feel free to reply. This is not a live chat channel and I may be in a different time zone than you. As a result, replies may be delayed and I may respond minutes to hours later.

    Was this answer helpful?

    0 comments No comments