Black screen, high fan speed, GPU stops working?

Dan Larsen 0 Reputation points
2026-11-08T11:36:06.03+00:00

I have been having problems with my computer for a while, been sending it in to see what was wrong with it, my computer keeps going into black screen and turn the fans to high speed when i play some graphic intensive games, i'm usually pretty good at computers and finding the problem, but with this one i have just not been able to locate it, i'm not good at looking at dump files and finding the problem in those, so i have been using ChatGPT to help find out the problems, at first i thought it was my steroe that ran too much power through my computer, but it now seems that's not the case.

I wanna post my shared GPT talk here that people can read through (original is in danish, i made it cope it all and make an english translation as well, but i will share both just in case), i really hope someone can look through it all and give me an idea of what can be the cause, because it hinders my ability to play games, which my computer should have no problems running.

When i sent my computer in they could not recreate the problem and said everything was working fine, i tried switching out ALL cabels, screens everything, it was only my stereo that was still the same, which is why i thought that was the problem, but apparently not, so i'm stumped now.

Original GPT conversation (danish):
https://chatgpt.com/s/cx_6af05a8898e08191abf8f4c6b9dbfce3

Translated to english:
https://chatgpt.com/s/cx_6af05b4112608191be197e59c60cbbf8

I think there is a lot of information here, but if anything else is needed, let me know and i will do my best to get it to you, i really wanna know what could be the problem.
I got 3 zip folders with dump files people can get as well, i couldn't find a way to upload them to this post, so let me know if you want those as well

PC specifications

CPU: AMD Ryzen 7 9700X — 8 cores / 16 threads
Motherboard: ASUS PRIME X870-P
BIOS: Version 1087, dated September 19, 2025

GPU: NVIDIA GeForce RTX 4070 Ti SUPER
VRAM: 16 GB GDDR6X
NVIDIA driver: 621.14 (clean installation performed during troubleshooting)

RAM: 32 GB Kingston DDR5, dual-channel (2 × 16 GB)
Module part number: KF560C30-16
Rated specification: DDR5-6000, CL30
Speed shown in HWiNFO: approximately DDR5-4800
(2395.7 MHz memory clock), with timings 40-39-39-77

Storage:
- Kingston SNV2S2000G — 2 TB NVMe SSD
- Lexar SSD NM790 4TB — 4 TB NVMe SSD

Operating system: Windows 11 Home, 64-bit
Windows for home | Windows 11 | Display and graphics
0 comments No comments

2 answers

Sort by: Most helpful
  1. DaveM121 946.5K Reputation points Independent Advisor
    2026-11-08T12:10:39.0933333+00:00

    Hi Dan,

    Please upload your dump files to OneDrive (https://onedrive.live.com/) or any other cloud service and choose to share them, then please provide the share link here, and I will analyze them for you to try to find the underlying cause of the black screen crashes.

    Was this answer helpful?


  2. AI answer

    2026-11-08T11:37:32.59+00:00

    If the NVIDIA “clean installation” did not use DDU in Safe Mode, completely remove the driver with DDU and test a slightly older NVIDIA driver before changing anything else.

    1. Perform a controlled driver rollback

    A similar Windows 11 system with an RTX 4070 Ti Super and gaming crashes was advised to remove the NVIDIA driver completely and test older driver versions ^1^.

    1. Download DDU (Display Driver Uninstaller) from its developer and download a slightly older RTX 4070 Ti Super driver directly from NVIDIA.
    2. Disconnect from the internet temporarily so Windows Update does not install another display driver during the procedure.
    3. Enter Safe Mode:
      • Settings → System → Recovery → Advanced startup → Restart now
      • Troubleshoot → Advanced options → Startup Settings → Restart
      • Select Safe Mode.
    4. Run DDU and choose GPU → NVIDIA → Clean and restart.
    5. Back in normal Windows, install the older NVIDIA driver using Custom installation and install only the display driver and PhysX.
    6. Restart, reconnect to the internet, and test the same game with the same settings.

    Treat this as a diagnostic rollback, not proof that the current driver is defective. If the older driver fails identically, move to evidence collection and hardware isolation rather than repeatedly reinstalling drivers.

    2. Determine whether Windows recorded a GPU timeout

    Your load-triggered signal loss and fan ramp-up closely resemble a graphics Timeout Detection and Recovery (TDR) failure: Windows detects that the GPU stopped responding and attempts to reset it. A failed reset can produce VIDEO_TDR_FAILURE (0x116), but the underlying cause can still be a driver, cooling, power delivery, memory configuration, motherboard, or defective component ^2^.

    After the next incident:

    1. Search for Reliability Monitor and open View reliability history.
    2. Open the critical event at the failure time and record:
      • LiveKernelEvent code, particularly 141, 117, or 1b8
      • Bug-check code
      • Bucket ID and referenced files
    3. Open Event Viewer → Windows Logs → System.
    4. Filter to the failure time and look for display-driver, WHEA, Kernel-Power, or bug-check events. Kernel-Power after a forced shutdown records the shutdown; it does not by itself identify the original fault.

    Check these dump locations:

    C:\Windows\Minidump
    C:\Windows\LiveKernelReports
    C:\Windows\LiveKernelReports\WATCHDOG
    

    Windows normally stores full live dumps under LiveKernelReports and component-specific minidumps in its subdirectories ^3^.

    3. Extract the useful dump fields

    Install WinDbg with:

    winget install Microsoft.WinDbg
    

    WinDbg supports Windows 11 and can analyze crash dumps ^4^. Open the newest dump, then run:

    .symfix
    .reload
    !analyze -v
    lmvm nvlddmkm
    

    Record only:

    • Bug-check or live-dump code and four parameters
    • MODULE_NAME
    • IMAGE_NAME
    • FAILURE_BUCKET_ID
    • The first meaningful stack entries

    nvlddmkm.sys or dxgkrnl.sys identifies the graphics path involved, but does not by itself distinguish a faulty NVIDIA driver from unstable GPU, PSU, motherboard, or RAM hardware. DirectX dumps can preserve GPU and driver state from the moment of a TDR, although available detail varies by driver ^5^.

    Crash dumps and debugger output can contain usernames, paths, process information, memory contents, or credentials. Prefer posting only the sanitized fields above. If a technician needs the dump, use a restricted OneDrive link shared only with that technician, review it for identifying data, and revoke access afterward—do not publish it openly.

    4. If the rollback fails, isolate hardware under load

    Because you already replaced the display cables and monitors, do not repeat those checks.

    1. Return BIOS and tuning to defaults. Disable CPU/GPU overclocking, undervolting, and memory overclock profiles temporarily. Incorrect compatibility or memory timings and overclocked components are documented TDR causes ^2^.
    2. Log sensors during the same game. Capture GPU temperature, hotspot temperature, GPU power, fan speed, and CPU temperature until failure. Do not infer overheating from fan speed alone.
    3. Inspect GPU power and seating safely. Shut Windows down, switch the PSU off, unplug it, and wait before touching components. Reseat the GPU and its power connector; ensure the connector is fully inserted and not sharply bent at the plug. Never open the PSU.
    4. Run Windows Memory Diagnostic: search Windows Memory Diagnostic → Restart now and check for problems. After reboot, inspect Event Viewer → Windows Logs → System → MemoryDiagnostics-Results ^6^.
    5. Use substitution testing. The decisive tests are this GPU in another known-good PC, another suitable GPU in this PC, or a known-good adequately rated PSU. If only GPU-heavy workloads fail while CPU and memory diagnostics pass, prioritize GPU and PSU substitution.

    If the vendor could not reproduce it, provide the exact game, graphics settings, approximate time-to-failure, Reliability Monitor code, sanitized WinDbg fields, and sensor log. That gives the repair shop a reproducible workload and evidence instead of a generic “black screen” report.


    References

    1. New build Windows 11 repeated, random restarts - Microsoft Q&A
    2. Bug Check 0x116: VIDEO_TDR_FAILURE
    3. Kernel Live Dump Code Reference
    4. Install the Windows debugger
    5. DirectX Dump Files
    6. Bug checks (stop code errors)
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.