![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Memory dumps are overwritten by default.
They disappear when there is another BSOD.
Please look now for C:\windows\memory.dmp
Save the file to the downloads folder.
Zip the file.
Post a share link with only the zipped memory dump.
Please save the file now and upload in the thread using a share link.
Size 2.2 GB > please ZIP
6/06/2022 11:23:42 AM 2254.38 C:\Windows\MEMORY.DMP
One of the two BSOD displayed again misbehaving Intel GPU drivers.
Multiple times these GPU drivers were replaced during the thread.
Each time the same driver was reinstalled.
It is important to test different driver versions.
Please uninstall and reinstall the Intel GPU drivers igdkmd64.sys.
Make sure that the new driver is a different version from: Driver Version 30.0.101.1273
Turn off Windows updates of non-Microsoft drivers: https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html
The drivers displayed on the motherboard website are not 30.0.101.1273
Please install one of the drives displayed on the motherboard website.
One of the bugchecks, 116, displayed video TDR.
Different drivers must be tested to determine whether there is or is not a stable driver.
If there is a stable driver then this driver can be used.
If there is no stable driver then the computer will continue to have hangs, freezes and BSOD until the malfunctioning hardware is replaced.
A common stability problem in graphics occurs when the system appears completely frozen or hung
while processing an end-user command or operation.
Usually the GPU is busy processing intensive graphics operations, typically during game-play.
No screen updates occur, and users assume that their system is frozen.
Users usually wait a few seconds and then reboot the system by pressing the power button.
Windows tries to detect these problematic hang situations and dynamically recover a responsive desktop.
This process of detection and recovery is known as Timeout Detection and Recovery (TDR).
The default timeout is 2 seconds.
In the TDR process for video cards, the operating system's GPU scheduler calls the display miniport driver's
DxgkDdiResetFromTimeout function to reinitialize the driver and reset the GPU.
During this process, the operating system tells the driver not to access the hardware or memory and gives
it a short time for currently running threads to complete.
If the threads do not complete within the timeout, then the system bug checks with 0x116 VIDEO_TDR_FAILURE.
For more information, see Thread Synchronization and TDR.
The system can also bug check with VIDEO_TDR_FAILURE if a number of TDR events occur in a short period of time,
by default more than five TDRs in one minute.
If the recovery process is successful, a message will be displayed, indicating that the
"Display driver stopped responding and has recovered."
Event[221]:
Log Name: System
Source: Display
Date: 2022-05-01T10:58:29.7700000Z
Event ID: 4101
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-N5UBAEP
Description:
Display driver igfx stopped responding and has successfully recovered.
Event[1346]:
Log Name: System
Source: Display
Date: 2022-05-06T11:47:53.7390000Z
Event ID: 4101
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-N5UBAEP
Description:
Display driver igfx stopped responding and has successfully recovered.
Event[7251]:
Log Name: System
Source: Display
Date: 2022-05-30T11:16:06.8070000Z
Event ID: 4101
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-N5UBAEP
Description:
Display driver igfx stopped responding and has successfully recovered.
Event[11332]:
Log Name: System
Source: Display
Date: 2022-06-06T07:29:42.1820000Z
Event ID: 4101
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-N5UBAEP
Description:
Display driver igfx stopped responding and has successfully recovered.
There were many other entries with different dates.
One of the BSOD bugchecks was 116:
The VIDEO_TDR_FAILURE bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.
These were the live kernel event bugchecks: 141 and 193 that were related to problematic video:
The VIDEO_ENGINE_TIMEOUT_DETECTED live dump has a value of 0x00000141. This indicates that one of the display engines failed to respond in timely fashion.
The VIDEO_DXGKRNL_LIVEDUMP live dump has a value of 0x00000193. This indicates a livedump triggered by dxgkrnl occurred.
Name Intel(R) UHD Graphics 630
PNP Device ID PCI\VEN_8086&DEV_9BC5&SUBSYS_D0001458&REV_05\3&11583659&0&10
Adapter Type Intel(R) UHD Graphics Family, Intel Corporation compatible
Adapter Description Intel(R) UHD Graphics 630
Adapter RAM 1.00 GB (1,073,741,824 bytes)
Installed Drivers C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igd12umd64.dll
Driver Version 30.0.101.1273
INF File oem32.inf (iCML_w10_DS section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_0797C0EA8580AE89\IGDKMD64.SYS (30.0.101.1273, 38.15 MB (40,004,152 bytes), 26/02/2022 8:39 AM)