[SOLVED] GPU driver crashes and resets. Hardware issue?

Apr 28, 2021
1
0
10
Recently I've been having a lot of problems with crashing in games. I think it may be a hardware issue, but perhaps one of the people on this forum that are smarter than me can help further diagnose the issue. Here's the specs of my system:

  • i7-8700K@3.7GHz
  • 32GB DDR4 3200MHz memory
  • 700W 80+ B Power supply
  • RTX 2070 Windforce OC
  • All on a Z370 Gaming 5 Revision 1 motherboard

First I want to list everything I've done to try and fix these problems:
  • Reseated the GPU
  • Underclocked the gpu (it's a factory OC card)
  • Reduced the power limit on the GPU in MSI Afterburner
  • Cleaned the case and parts in the computer with compressed air and made it completely dust free (I got behind the gpu fans to remove dust from the inside as well)
  • Updating drivers
  • Rolling back drivers
  • Completely reinstalling drivers using DDU
None of these helped, this is why I believe it's a hardware issue, however the problem could fall on my GPU or even my PSU. It isn't an overheating issue as when it was at 100% power limit, it ran under 80C, and now with the power limit I run under 60C at all times (maxed at 59C under a MSI Kombustor Stress test with x32 tessellation).

With that out of the way, here's the only error I got that gave me good information, however I'm not sure if this even comes from the same issue because it's an access violation:
Exception thrown at 0x00007FFC4AEE2F06 (WindowManagementAPI.dll) in : 0xC0000005: Access violation reading location 0x0000000000000130.

Also, OBS was giving me issues too, I extracted the relevant log:

Code:
16:16:51.736: ==== Streaming Start ===============================================
16:16:51.741: obs-browser[2]: API: performing call to 'getSystemCPUUsageTimes', callback id 41
16:16:51.741: obs-browser[2]: API: completed call to 'getSystemCPUUsageTimes', callback id 41
16:16:51.741: obs-browser[2]: API: performing call to 'getSystemMemoryUsage', callback id 42
16:16:51.741: obs-browser[2]: API: completed call to 'getSystemMemoryUsage', callback id 42
16:16:51.741: obs-browser[2]: API: performing call to 'getSystemHardwareProperties', callback id 43
16:16:51.742: obs-browser[2]: API: completed call to 'getSystemHardwareProperties', callback id 43
16:16:51.769: [jim-nvenc] get_encoded_packet: nv.nvEncLockBitstream(s, &lock) failed: 8 (NV_ENC_ERR_INVALID_PARAM)
16:16:51.769: Error encoding with encoder 'streaming_h264'
16:16:51.769: [rtmp stream: 'adv_stream'] Encoder error, disconnecting
16:16:51.769: Output 'adv_stream': stopping
16:16:51.769: Output 'adv_stream': Total frames output: 0
16:16:51.769: Output 'adv_stream': Total drawn frames: 53
16:16:51.769: warning: 2 frames left in the queue on closing
16:16:51.770: obs-browser[2]: API: posting call to 'getSystemCPUUsageTimes', callback id 44, args: []
16:16:51.770: obs-browser[4]: CONSOLE: Stream is not started (source: https://obs.streamelements.com/yoink/static/mediaRequest.7b28b375074e78075877.bundle.js?e3bc7bce8ab71e0a53a8:2)
16:16:51.770: obs-browser[2]: API: posting call to 'getSystemMemoryUsage', callback id 45, args: []
16:16:51.770: obs-browser[2]: API: posting call to 'getSystemHardwareProperties', callback id 46, args: []
16:16:51.772: ==== Streaming Stop ================================================

I feel like I'm out of options, and GPUs cost way too much right now to be throwing out a 2070. Does anyone have any ideas? Do you need more info? Thanks
 
Solution

Ralston18

Titan
Moderator
Solution