Need assistance with troubleshooting? Possible graphics drivers issues that persist?
Need assistance with troubleshooting? Possible graphics drivers issues that persist?
Okay so here's the deal, I have been plagued by constant crashes while gaming for over a year and I have tried everything under the sun to try and troubleshoot it. I have recently replaced my motherboard and now have been getting blue screens that have indicated that the errors are associated with graphics drivers. I have dump files for the most recent crash but I'm not sure how to post them. I have tried reinstalling drivers multiple times as well as I have recently completely wiped my computer and reinstalled windows to no avail. I did notice that when I had a fresh copy I somehow acquired the most recent NVIDIA drivers before I had even downloaded the software. These crashes usually happen 5-10 minutes after I've opened up a game and I've gotten either a blue screen or I've also had the game simply close before as well.
Here are my specs: Intel I9 9900KF, NVIDIA gtx 1070Ti, STRIX Z390-H gaming MOBO, and 32gb DDR4 RAM and I'm using a NZXT H510 case.
Anything that can help is greatly appreciated.
What games or titles experience crashes? Which ones remain stable?
PSU: specifications, make, model, wattage, age, condition (original to build, new, refurbished, used)?
Check the Reliability History and Event Viewer for error messages, alerts, and related events around the crash times.
How are the graphics drivers being installed?
Are you employing a third-party installer or directly fetching the drivers from the manufacturer's official site?
Prefer direct downloads and then manually installing and setting up. No third-party tools or installers.
Before upgrading my motherboard, only GTA, Sea of Thieves, and Dying Light experienced crashes without any blue screen. After switching the board, every game started crashing. Games like CS:GO, Rocket League, and League of Legends that previously didn’t crash are now failing. The PSU is an EVGA 750W, owned by a friend, functioning normally with no issues, and it’s about 3-4 years old. I verified the voltage readings and found nothing unusual. A reliability monitor is displaying some data, but I’m unsure how to extract the needed information from the event viewer.
Reliability History offers a more intuitive experience and provides valuable insights into errors and trends. Event Viewer presents a more complex interface that is harder to interpret, requiring some time to grasp before you can extract useful information. Generally, sticking with one method for a while helps build familiarity before diving into the data. Here are the links shared in the discussion: https://forums. https://www.windowscentral.com/how-use-e...windows-10 In summary, if you're comparing Reliability History and Event Viewer, you may notice a rise in errors and inconsistent issues that raise concerns about the power supply unit (PSU), particularly after 3 to 4 years of use and heavy gaming sessions. It might be nearing its end of life, possibly failing during high power demands. Consider replacing it with a known functional PSU if feasible, and ensure you only use the cables provided with the modular unit.
Would a malfunctioning power supply trigger error codes typically associated with corrupt drivers? Probably not, though issues can sometimes produce error codes unrelated to the actual fault. Many of these codes are too vague or broad to be useful, similar to the "Check Engine" indicator. For instance, a GPU power issue might interfere with code execution, causing Windows to mark it as damaged driver code. The situation becomes more complicated because the PSU supplies multiple voltages (3.3, 5, and 12) to different parts of the system, meaning something might function correctly while others fail. This adds further uncertainty when interpreting error messages. I look for patterns such as a rise in diverse errors, including improper shutdowns that force a reboot. Ultimately, resolving these problems often involves manual steps like downloading, reinstalling, and reconfiguring drivers, or performing system repairs with tools like "sfc /scannow" and "dism." Sometimes fixing the problem is straightforward, but other times it requires more effort.
Took some time but finally had the power supply set up. It worked for a while but then another blue screen appeared with the system_service_exception code. Checking the minidump suggests svchost.exe might have crashed, though I'm still unsure about the implications.
Check the Reliability History and Event Viewer for any preceding error codes, warnings, or informational messages before the blue screen appeared.