• Now's your chance win big! Join our community and get entered to win a RTX 2060 GPU, plus more! Join here.

    Pi Cast Episode 3 streams live on Tuesday, August 4th at 2:30 pm ET (7:30 PM BST). Watch live right here!

    Catch Scharon on the Tom's Hardware Show live on Thursday, August 6th at 2:00 pm ET (7:00 PM BST). Click here!

Question Computer crashing when @ 144hz refresh rate


Dec 26, 2009
So I've had this monitor (ASUS VG248QE) for a few years now but have always used it in just normal 60hz refresh rate with no issue. I upgraded my GPU about two years ago, and CPU/mobo/ram a year ago. Finally remembered I have had a 144hz capable monitor for all this time, so I had to order a new DisplayPort cable to activate it as the HDMI I had couldn't do it.

I got the new displayport cord, turned on 144hz and everything seems great for a while. I get into games and play a while (usually at least 10 mins, sometimes up to an hour) but then I'd occasionally get my 144hz screen go black for 2-3 seconds. Note I have dual monitors, the other monitor stays on during this period. If I keep playing it's likely that my computer will crash at which point both my screens turn off, I can still hear the game for like 2 seconds, but then that goes away as well.

My most recent crash last night my 144hz monitor actually wouldn't work anymore with any of my two displayport cords plugged in. I had to switch it back to my HDMI cable. When I try to plug that monitor in via the displayport plugs my other screen keeps flickering, and the 144hz monitor looks like it keeps trying to display something but then says "NO SIGNAL DISPLAY PORT"

From what I've read it seems it can potentially be a problem with PSU, graphics card, or monitor? How can I best eliminate the possibilities without other hardware replacements?

I've looked at the windows .dmp file (can't figure out how to attach it here) - i've pasted the analysis debug details below the part picker list

Here is my pc part picker list:

PCPartPicker Part List

CPU: AMD Ryzen 5 3600 3.6 GHz 6-Core Processor ($167.00 @ Newegg)
Motherboard: ASRock X570 Pro4 ATX AM4 Motherboard
Memory: Crucial Ballistix Elite 16 GB (2 x 8 GB) DDR4-3600 CL16 Memory ($175.99 @ Newegg)
Storage: Samsung 840 EVO 500 GB 2.5" Solid State Drive
Storage: Samsung 970 Evo Plus 1 TB M.2-2280 NVME Solid State Drive ($199.99 @ Adorama)
Video Card: XFX Radeon RX 580 8 GB GTS Black Video Card ($189.99 @ Best Buy)
Case: Corsair 200R ATX Mid Tower Case ($74.98 @ Amazon)
Power Supply: EVGA 750 W 80+ Bronze Certified Semi-modular ATX Power Supply
Optical Drive: Asus DRW-24F1ST DVD/CD Writer ($18.98 @ Amazon)
Total: $826.93

crash dump file analysis
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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

Debugging Details:

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


    Key  : Analysis.CPU.Sec
    Value: 0

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-NBAK5GD

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 0

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 42

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.CorruptModuleList
    Value: 1



BUGCHECK_P1: ffff910afdd4a010

BUGCHECK_P2: fffff80465490818

BUGCHECK_P3: ffffffffc0000001



ffffa10a`9a310a08 fffff804`64acecea : 00000000`00000116 ffff910a`fdd4a010 fffff804`65490818 ffffffff`c0000001 : 0xfffff804`5e1c2390
ffffa10a`9a310a10 00000000`00000116 : ffff910a`fdd4a010 fffff804`65490818 ffffffff`c0000001 00000000`00000003 : 0xfffff804`64acecea
ffffa10a`9a310a18 ffff910a`fdd4a010 : fffff804`65490818 ffffffff`c0000001 00000000`00000003 00000000`00002000 : 0x116
ffffa10a`9a310a20 fffff804`65490818 : ffffffff`c0000001 00000000`00000003 00000000`00002000 ffff910a`fdd4a010 : 0xffff910a`fdd4a010
ffffa10a`9a310a28 ffffffff`c0000001 : 00000000`00000003 00000000`00002000 ffff910a`fdd4a010 fffff804`64a7e1cb : 0xfffff804`65490818
ffffa10a`9a310a30 00000000`00000003 : 00000000`00002000 ffff910a`fdd4a010 fffff804`64a7e1cb fffff804`65490818 : 0xffffffff`c0000001
ffffa10a`9a310a38 00000000`00002000 : ffff910a`fdd4a010 fffff804`64a7e1cb fffff804`65490818 ffff910a`f3d4c000 : 0x3
ffffa10a`9a310a40 ffff910a`fdd4a010 : fffff804`64a7e1cb fffff804`65490818 ffff910a`f3d4c000 ffff910a`f3d4c0d8 : 0x2000
ffffa10a`9a310a48 fffff804`64a7e1cb : fffff804`65490818 ffff910a`f3d4c000 ffff910a`f3d4c0d8 00000000`00000000 : 0xffff910a`fdd4a010
ffffa10a`9a310a50 fffff804`65490818 : ffff910a`f3d4c000 ffff910a`f3d4c0d8 00000000`00000000 ffff910a`fdd4a010 : 0xfffff804`64a7e1cb
ffffa10a`9a310a58 ffff910a`f3d4c000 : ffff910a`f3d4c0d8 00000000`00000000 ffff910a`fdd4a010 00000000`00002000 : 0xfffff804`65490818
ffffa10a`9a310a60 ffff910a`f3d4c0d8 : 00000000`00000000 ffff910a`fdd4a010 00000000`00002000 00000000`00000001 : 0xffff910a`f3d4c000
ffffa10a`9a310a68 00000000`00000000 : ffff910a`fdd4a010 00000000`00002000 00000000`00000001 ffff910a`f3d4c9e0 : 0xffff910a`f3d4c0d8


MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb



OSNAME:  Windows 10

FAILURE_ID_HASH:  {d0ecd047-d84e-1626-7611-d54cbc1cd165}

Followup:     MachineOwner