F5F Stay Refreshed Software Operating Systems BSOD issues ?

BSOD issues ?

BSOD issues ?

Pages (3): Previous 1 2 3
S
SrNegue_4K
Junior Member
17
12-09-2022, 03:20 PM
#21
No, you haven't figured out if the GPU is overcooked.
S
SrNegue_4K
12-09-2022, 03:20 PM #21

No, you haven't figured out if the GPU is overcooked.

C
colinbmxguy
Junior Member
9
12-09-2022, 08:34 PM
#22
To understand the issue, the GPU failed to meet timing windows and stopped responding. The system reset the bus, and then a network driver bugcheck was performed during reconnection. We are uncertain whether the GPU actually reacted to the bus reset or if it recovered before the bugcheck was applied.

Typically, for such problems I would verify all electronics timing settings are set to defaults and eliminate common causes of GPU failures (such as other sound devices interfering with the GPU sound driver and causing crashes). I would disable any overclocking tools, revert the BIOS to its default configuration (especially if the PCI bus speed was changed from 100Mhz), remove all GPU overclocks, and retest. If you installed a new network driver, the bugcheck should no longer appear.

If the card still has issues, consider a watchdog timeout. This assumes no overclock driver is installed. I often find memory dumps with multiple overclock drivers present, which prevent the drivers from recognizing each other and disrupt timing due to voltage changes, leading to signal misses.

You can use autoruns64.exe from Microsoft to check for third-party overclocking tools and disable them. The drivers will also appear in a crash dump within the Windows debugger.

I have observed cases where people underclocked the GPU to get it working, but memory dumps showed multiple overclock drivers installed—effectively underclocking the card to counteract their interference.

Additionally, many GPUs fail due to an outdated Realtek motherboard sound driver. The old driver would respond to the GPU’s HDMI audio and crash the driver, resulting in timeouts because the HDMI video driver’s sound portion failed to respond. (You can disable the video sound driver and test if the GPU still hangs.)
C
colinbmxguy
12-09-2022, 08:34 PM #22

To understand the issue, the GPU failed to meet timing windows and stopped responding. The system reset the bus, and then a network driver bugcheck was performed during reconnection. We are uncertain whether the GPU actually reacted to the bus reset or if it recovered before the bugcheck was applied.

Typically, for such problems I would verify all electronics timing settings are set to defaults and eliminate common causes of GPU failures (such as other sound devices interfering with the GPU sound driver and causing crashes). I would disable any overclocking tools, revert the BIOS to its default configuration (especially if the PCI bus speed was changed from 100Mhz), remove all GPU overclocks, and retest. If you installed a new network driver, the bugcheck should no longer appear.

If the card still has issues, consider a watchdog timeout. This assumes no overclock driver is installed. I often find memory dumps with multiple overclock drivers present, which prevent the drivers from recognizing each other and disrupt timing due to voltage changes, leading to signal misses.

You can use autoruns64.exe from Microsoft to check for third-party overclocking tools and disable them. The drivers will also appear in a crash dump within the Windows debugger.

I have observed cases where people underclocked the GPU to get it working, but memory dumps showed multiple overclock drivers installed—effectively underclocking the card to counteract their interference.

Additionally, many GPUs fail due to an outdated Realtek motherboard sound driver. The old driver would respond to the GPU’s HDMI audio and crash the driver, resulting in timeouts because the HDMI video driver’s sound portion failed to respond. (You can disable the video sound driver and test if the GPU still hangs.)

0
0sdG4m3r_YT
Member
210
12-10-2022, 12:00 AM
#23
Wow, that's interesting. I don't have any GPU overclocking drivers set up. Maybe my son did install one (I really wish he did, because it shows he's learning and experimenting).

The suggested approach seems to be:
1) Adjust crash dumps to use the kernel type and search for ways to force a Windows memory dump via keyboard.
2) Run autoruns64.exe and remove drivers.
3) Inspect the Realtek sound driver and update it if needed.
0
0sdG4m3r_YT
12-10-2022, 12:00 AM #23

Wow, that's interesting. I don't have any GPU overclocking drivers set up. Maybe my son did install one (I really wish he did, because it shows he's learning and experimenting).

The suggested approach seems to be:
1) Adjust crash dumps to use the kernel type and search for ways to force a Windows memory dump via keyboard.
2) Run autoruns64.exe and remove drivers.
3) Inspect the Realtek sound driver and update it if needed.

Pages (3): Previous 1 2 3