Black screen on PC, tried everything but nothing works, how to determine if its my gpu or something else, did stress test for memory and GPU, but pc crashed when doing GPU one

Surname101 0 Reputation points
2024-01-22T03:33:59.54+00:00

Problem Event Name: LiveKernelEvent Code: 141 Parameter 1: ffffd6030f762010 Parameter 2: fffff80637bf63a0 Parameter 3: 0 Parameter 4: 540 OS version: 10_0_19045 Service Pack: 0_0 Product: 768_1 OS Version: 10.0.19045.2.0.0.768.101 Locale ID: 1033

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,201 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li 2,245 Reputation points
    2024-01-22T10:07:54.7133333+00:00

    Hello The error code LiveKernelEvent 141 is often associated with hardware components, including the GPU, and can also be caused by corrupted device drivers, overheating, and software conflicts.   Given that your PC crashed during the GPU stress test and the error code you provided, it’s possible that the issue is related to your graphics card or its driver. Here are some steps you can take to troubleshoot this issue:   Update or reinstall your graphics card driver: Your memory dump file indicates that it could be the device driver on your Nvidia graphics card that is causing the system to crash. You should completely remove the current Nvidia device driver using a utility like DDU (Display Driver Uninstaller), then restart your PC and download and install the latest version of the Nvidia device driver from the official Nvidia website.   Check for overheating: Overheating can cause your PC to crash. Monitor the temperature of your GPU to see if it’s running too hot. If it is, you may need to improve the cooling in your system.   Test your GPU: Use a GPU testing tool to check if your GPU is functioning correctly. If the tool reports errors, your GPU may be faulty.   Check other hardware: Although the GPU is a likely culprit given the symptoms, other hardware components could also be causing the issue. Consider testing your RAM, CPU, and hard drive to rule them out as potential causes.

    0 comments No comments