Windows 10: BSOD - MEMORY_CORRUPTION_LARGE

I have bsod random time.https://drive.google.com/drive/folders/1H6X840cJXmDppthK5t5jFH60Jd5mqZlx?usp=drive_link - minidumpmy pc: Ryzen 7 5800xgigabyte b450 gaming xkingston fury 2x16 3200 xmp rtx 3070thermaltake 850w I tried reinstalling Windows and drivers.

:)

 

BSOD Video_TDR_Timeout & Memory_Corruption_Large

Hi, Vaibhav Srivastava3

Welcome to the Microsoft Community.



Thank you for reaching out to us with the details of the BSOD errors you're encountering.

Based on the information you provided, it seems like the "VIDEO_TDR_TIMEOUT" BSOD is occurring while loading a game. This indicates that the display driver failed to respond in a timely fashion. The GPU is taking more time than permitted to display graphics to your monitor. This behavior can occur for one or more of the following reasons:

1. You may need to install the latest updates for your display driver, so that it properly supports the TDR process.
   
   • Download Display Driver Uninstaller (DDU)< software and extract the file.
     
   • Open DDU ****.exe and run extract program.
     
   • Reboot into Windows* safe mode. (Refer to Start your PC in safe mode in Windows.)
     
   • Go to the DDU extract path and double-click the Display Driver Uninstaller.exe to open DDU.
     
   • Click Close in the Options window.
     
   • Select device type to GPU and select device to Nvidia.
     
   • Click Clean and restart or Clean and Shutdown depending on your needs
     
   • Wait the software to finish the process and auto reboot Windows to the normal mode or shutdown.
     
   • Download the latest adapted drivers from the NVIDIA website: Official Drivers | NVIDIA
     
     Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.
     
2. Hardware issues that impact the ability of the video card to operate properly, including:
   
   • Over-clocked components, such as the motherboard
     
   • Incorrect component compatibility and settings (especially memory configuration and timings)
     
   • Insufficient system cooling
     
   • Insufficient system power
     
   • Defective parts (memory modules, motherboards, etc.). You can run the Windows Memory Diagnostics tool, to test the memory. In the control panel search box, type Memory, and then select Diagnose your computer's memory problems.‌ After the test is run, use Event viewer to view the results under the System log. Look for the MemoryDiagnostics-Results entry to view the results.
     
3. Visual effects, or too many programs running in the background may be slowing your PC down so that the video card can not respond as necessary.
   

Please Check these factors and let me know if you're still experiencing issues. If you need further assistance, feel free to provide more details, and I'll be happy to help.



Best Regards

Martin | Microsoft Community Support Specialist

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

BSOD Video_TDR_Timeout & Memory_Corruption_Large

Hi Team,

I am regularly getting "Video_TDR_timeout" BSOD while loading a game. These were not happening earlier. I had used WinDBG executable to check the minidumps. It keeps throwing Memory_Corruption_large. Below are the links for most recent dump files:

042824-42062-01.dmp

042924-70593-01.dmp

Error message below:

Loading Dump File [C:\Windows\Minidump\042924-70593-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff801`54600000 PsLoadedModuleList = 0xfffff801`5522a790

Debug session time: Mon Apr 29 14:14:56.120 2024 (UTC + 5:30)

System Uptime: 0 days 16:23:49.807

Loading Kernel Symbols

...............................................................

................................................................

................................................................

...................................

Loading User Symbols

Loading unloaded module list

..............

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 116, {ffffd80b82a0b010, fffff8016c8b8a70, ffffffffc0000001, 4}



Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvami.inf_amd64_5a5c892944a7f61d\nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : memory_corruption



Followup: memory_corruption

---------



5: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffffd80b82a0b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8016c8b8a70, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.



Debugging Details:

------------------





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 10.0.19041.4291 (WinBuild.160101.0800)



SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.



SYSTEM_PRODUCT_NAME: GL553VD



SYSTEM_VERSION: 1.0



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: GL553VD.308



BIOS_DATE: 04/29/2019



BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



BASEBOARD_PRODUCT: GL553VD



BASEBOARD_VERSION: 1.0



DUMP_TYPE: 2



BUGCHECK_P1: ffffd80b82a0b010



BUGCHECK_P2: fffff8016c8b8a70



BUGCHECK_P3: ffffffffc0000001



BUGCHECK_P4: 4



FAULTING_IP:

nvlddmkm+1498a70

fffff801`6c8b8a70 488b05c925a2ff mov rax,qword ptr [nvlddmkm+0xebb040 (fffff801`6c2db040)]



DEFAULT_BUCKET_ID: CODE_CORRUPTION



CPU_COUNT: 8



CPU_MHZ: af8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: 9



CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)



CUSTOMER_CRASH_COUNT: 1



BUGCHECK_STR: 0x116



PROCESS_NAME: System



CURRENT_IRQL: 0



ANALYSIS_SESSION_HOST: KING



ANALYSIS_SESSION_TIME: 04-29-2024 14:28:15.0157



ANALYSIS_VERSION: 10.0.15063.468 x86fre



STACK_TEXT:

fffff887`4b1cf918 fffff801`5dd1543e : 00000000`00000116 ffffd80b`82a0b010 fffff801`6c8b8a70 ffffffff`c0000001 : nt!KeBugCheckEx

fffff887`4b1cf920 fffff801`5dcc59e4 : fffff801`6c8b8a70 ffffd80b`798ec6a0 00000000`00002000 ffffd80b`798ec760 : dxgkrnl!TdrBugcheckOnTimeout+0xfe

fffff887`4b1cf960 fffff801`5dcbe51c : ffffd80b`79909000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174

fffff887`4b1cf990 fffff801`5dd14b65 : 00000000`00000100 ffffd80b`79909a70 00000000`00000000 fffff801`55325440 : dxgkrnl!DXGADAPTER::Reset+0x4dc

fffff887`4b1cfa10 fffff801`5dd14cd7 : fffff801`55325440 ffffd80b`8156d870 00000000`00000000 00000000`00000800 : dxgkrnl!TdrResetFromTimeout+0x15

fffff887`4b1cfa40 fffff801`548c3ea5 : ffffd80b`825f0040 fffff801`5dd14cb0 ffffd80b`6d878cf0 ffffd80b`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27

fffff887`4b1cfa70 fffff801`5494ef55 : ffffd80b`825f0040 00000000`00000080 ffffd80b`6d85e040 0ab23c75`01eac88c : nt!ExpWorkerThread+0x105

fffff887`4b1cfb10 fffff801`54a06a48 : ffff8a01`21ac0180 ffffd80b`825f0040 fffff801`5494ef00 8b782444`8b702444 : nt!PspSystemThreadStartup+0x55

fffff887`4b1cfb60 00000000`00000000 : fffff887`4b1d0000 fffff887`4b1c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





STACK_COMMAND: kb



CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgkrnl

fffff8015daedaff-fffff8015daedb00 2 bytes - dxgkrnl!DxgkPowerRuntimeComponentIdleCallback+4f

[ 48 ff:4c 8b ]

fffff8015daedb06-fffff8015daedb0a 5 bytes - dxgkrnl!DxgkPowerRuntimeComponentIdleCallback+56 (+0x07)

[ 0f 1f 44 00 00:e8 65 e3 e5 f6 ]

fffff8015daedcc4-fffff8015daedcc5 2 bytes - dxgkrnl!DxgkPowerRuntimeDevicePowerNotRequiredCallback+44 (+0x1be)

[ 48 ff:4c 8b ]

fffff8015daedccb-fffff8015daedccf 5 bytes - dxgkrnl!DxgkPowerRuntimeDevicePowerNotRequiredCallback+4b (+0x07)

[ 0f 1f 44 00 00:e8 e0 9a eb f6 ]

fffff8015dcbe520-fffff8015dcbe521 2 bytes - dxgkrnl!DXGADAPTER::Reset+4e0

[ 48 ff:4c 8b ]

fffff8015dcbe527-fffff8015dcbe52a 4 bytes - dxgkrnl!DXGADAPTER::Reset+4e7 (+0x07)

[ 0f 1f 44 00:e8 e4 5b 1a ]

fffff8015dcbe537-fffff8015dcbe538 2 bytes - dxgkrnl!DXGADAPTER::Reset+4f7 (+0x10)

[ 48 ff:4c 8b ]

fffff8015dcbe53e-fffff8015dcbe541 4 bytes - dxgkrnl!DXGADAPTER::Reset+4fe (+0x07)

[ 0f 1f 44 00:e8 1d 52 1a ]

fffff8015dcbe558-fffff8015dcbe559 2 bytes - dxgkrnl!DXGADAPTER::Reset+518 (+0x1a)

[ 48 ff:4c 8b ]

fffff8015dcbe55f-fffff8015dcbe562 4 bytes - dxgkrnl!DXGADAPTER::Reset+51f (+0x07)

[ 0f 1f 44 00:e8 ac 5b 1a ]

fffff8015dcbe56f-fffff8015dcbe570 2 bytes - dxgkrnl!DXGADAPTER::Reset+52f (+0x10)

[ 48 ff:4c 8b ]

fffff8015dcbe576-fffff8015dcbe579 4 bytes - dxgkrnl!DXGADAPTER::Reset+536 (+0x07)

[ 0f 1f 44 00:e8 e5 51 1a ]

fffff8015dcbe586-fffff8015dcbe587 2 bytes - dxgkrnl!DXGADAPTER::Reset+546 (+0x10)

[ 48 ff:4c 8b ]

fffff8015dcbe58d-fffff8015dcbe591 5 bytes - dxgkrnl!DXGADAPTER::Reset+54d (+0x07)

[ 0f 1f 44 00 00:e8 fe ef b4 f6 ]

fffff8015dcbe5be-fffff8015dcbe5bf 2 bytes - dxgkrnl!DXGADAPTER::Reset+57e (+0x31)

[ 48 ff:4c 8b ]

fffff8015dcbe5c5-fffff8015dcbe5cb 7 bytes - dxgkrnl!DXGADAPTER::Reset+585 (+0x07)

[ 0f 1f 44 00 00 48 ff:e8 76 e7 b7 f6 4c 8b ]

fffff8015dcbe5d1-fffff8015dcbe5d5 5 bytes - dxgkrnl!DXGADAPTER::Reset+591 (+0x0c)

[ 0f 1f 44 00 00:e8 1a f4 b7 f6 ]

fffff8015dcbe61b - dxgkrnl!DXGADAPTER::Reset+5db (+0x4a)

[ 48:4c ]

fffff8015dcc59f1-fffff8015dcc59f2 2 bytes - dxgkrnl!ADAPTER_RENDER::Reset+181 (+0x73d6)

[ 48 ff:4c 8b ]

fffff8015dcc59f8-fffff8015dcc59fb 4 bytes - dxgkrnl!ADAPTER_RENDER::Reset+188 (+0x07)

[ 0f 1f 44 00:e8 13 e7 19 ]

fffff8015dcc5a08-fffff8015dcc5a09 2 bytes - dxgkrnl!ADAPTER_RENDER::Reset+198 (+0x10)

[ 48 ff:4c 8b ]

fffff8015dcc5a0f-fffff8015dcc5a12 4 bytes - dxgkrnl!ADAPTER_RENDER::Reset+19f (+0x07)

[ 0f 1f 44 00:e8 4c dd 19 ]

fffff8015dd14cf1-fffff8015dd14cf2 2 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+41 (+0x4f2e2)

[ 48 ff:4c 8b ]

fffff8015dd14cf8-fffff8015dd14cfb 4 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+48 (+0x07)

[ 0f 1f 44 00:e8 93 c3 14 ]

fffff8015dd14d08-fffff8015dd14d09 2 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+58 (+0x10)

[ 48 ff:4c 8b ]

fffff8015dd14d0f-fffff8015dd14d12 4 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+5f (+0x07)

[ 0f 1f 44 00:e8 fc c4 14 ]

fffff8015dd14d31-fffff8015dd14d32 2 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+81 (+0x22)

[ 48 ff:4c 8b ]

fffff8015dd14d38-fffff8015dd14d3b 4 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+88 (+0x07)

[ 0f 1f 44 00:e8 63 cb 14 ]

fffff8015dd14d59-fffff8015dd14d5a 2 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+a9 (+0x21)

[ 48 ff:4c 8b ]

fffff8015dd14d60-fffff8015dd14d63 4 bytes - dxgkrnl!TdrResetFromTimeoutWorkItem+b0 (+0x07)

[ 0f 1f 44 00:e8 ab c3 14 ]

fffff8015dd154cb-fffff8015dd154cc 2 bytes - dxgkrnl!TdrTimedOperationWaitForSingleObject+7b (+0x76b)

[ 48 ff:4c 8b ]

fffff8015dd154d2-fffff8015dd154d6 5 bytes - dxgkrnl!TdrTimedOperationWaitForSingleObject+82 (+0x07)

[ 0f 1f 44 00 00:e8 39 26 b2 f6 ]

103 errors : !dxgkrnl (fffff8015daedaff-fffff8015dd154d6)



MODULE_NAME: memory_corruption



IMAGE_NAME: memory_corruption



FOLLOWUP_NAME: memory_corruption



DEBUG_FLR_IMAGE_TIMESTAMP: 0



MEMORY_CORRUPTOR: LARGE



FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE



BUCKET_ID: MEMORY_CORRUPTION_LARGE



PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE



TARGET_TIME: 2024-04-29T08:44:56.000Z



OSBUILD: 19041



OSSERVICEPACK: 4291



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: unknown_date



BUILDDATESTAMP_STR: 160101.0800



BUILDLAB_STR: WinBuild



BUILDOSVER_STR: 10.0.19041.4291



ANALYSIS_SESSION_ELAPSED_TIME: 3406



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:memory_corruption_large



FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}



Followup: memory_corruption

---------



5: kd> !analyze -v

Please let me know what I can do to resolve this? Thanks!!