BSOD Memory Corruption RRS feed

  • Question

  • Hello!

    Could anyone be able to tell me what is causing World of Tanks to crash.

    Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 18362 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff806`7d800000 PsLoadedModuleList = 0xfffff806`7dc432f0 Debug session time: Mon Jul 15 16:08:56.417 2019 (UTC + 3:00) System Uptime: 0 days 5:48:35.925 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .............. Loading User Symbols Loading unloaded module list ....................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`7d9bc900 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff808e`d74668f0=000000000000007e 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8067ded0b0b, The address that the exception occurred at Arg3: ffff808ed7467908, Exception Record Address Arg4: ffff808ed7467150, Context Record Address Debugging Details: ------------------ Page 200 not present in the dump file. Type ".hh dbgerr004" for details KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Write Key : Analysis.CPU.Sec Value: 8 Key : Analysis.Elapsed.Sec Value: 35 Key : Analysis.Memory.CommitPeak.Mb Value: 65 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202 SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd. SYSTEM_PRODUCT_NAME: B450 AORUS M SYSTEM_SKU: Default string SYSTEM_VERSION: Default string BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: F40 BIOS_DATE: 05/16/2019 BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd. BASEBOARD_PRODUCT: B450 AORUS M BASEBOARD_VERSION: Default string DUMP_TYPE: 1 BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff8067ded0b0b BUGCHECK_P3: ffff808ed7467908 BUGCHECK_P4: ffff808ed7467150 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. FAULTING_IP: nt!ExpWnfWorkItemRoutine+1b fffff806`7ded0b0b f0836028fd lock and dword ptr [rax+28h],0FFFFFFFDh EXCEPTION_RECORD: ffff808ed7467908 -- (.exr 0xffff808ed7467908) ExceptionAddress: fffff8067ded0b0b (nt!ExpWnfWorkItemRoutine+0x000000000000001b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 000000000000002b Attempt to write to address 000000000000002b CONTEXT: ffff808ed7467150 -- (.cxr 0xffff808ed7467150) rax=0000000000000003 rbx=ffffe18e53919040 rcx=ffffe18e3e08d280 rdx=0000000000000000 rsi=ffffe18e3e072690 rdi=ffffe18e3e08d288 rip=fffff8067ded0b0b rsp=ffff808ed7467b40 rbp=fffff8067ded0af0 r8=00000000ffffffff r9=7fffa08440044168 r10=7ffffffffffffffc r11=ffff808ed7467b10 r12=0000000000000400 r13=0000000000000000 r14=0000000000000000 r15=fffff8067dd8a240 iopl=0 nv up ei ng nz ac pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050293 nt!ExpWnfWorkItemRoutine+0x1b: fffff806`7ded0b0b f0836028fd lock and dword ptr [rax+28h],0FFFFFFFDh ds:002b:00000000`0000002b=???????? Resetting default scope CPU_COUNT: c CPU_MHZ: e09 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 17 CPU_MODEL: 8 CPU_STEPPING: 2 PROCESS_NAME: System CURRENT_IRQL: 0 FOLLOWUP_IP: nt!ExpWnfWorkItemRoutine+1b fffff806`7ded0b0b f0836028fd lock and dword ptr [rax+28h],0FFFFFFFDh BUGCHECK_STR: AV WRITE_ADDRESS: 000000000000002b DEFAULT_BUCKET_ID: CODE_CORRUPTION ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 000000000000002b ANALYSIS_SESSION_HOST: DESKTOP-C337NBM ANALYSIS_SESSION_TIME: 07-15-2019 16:26:25.0136 ANALYSIS_VERSION: 10.0.18914.1001 amd64fre LAST_CONTROL_TRANSFER: from fffff8067d8c4855 to fffff8067ded0b0b STACK_TEXT: ffff808e`d7467b40 fffff806`7d8c4855 : ffffe18e`3e072690 ffffe18e`3e072600 fffff806`7d868900 ffffe18e`3e072690 : nt!ExpWnfWorkItemRoutine+0x1b ffff808e`d7467b70 fffff806`7d92f725 : ffffe18e`53919040 00000000`00000080 ffffe18e`3e0a7380 ffff808e`00000001 : nt!ExpWorkerThread+0x105 ffff808e`d7467c10 fffff806`7d9c3e6a : ffff8a01`49840180 ffffe18e`53919040 fffff806`7d92f6d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff808e`d7467c60 00000000`00000000 : ffff808e`d7468000 ffff808e`d7462000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff8067dd6b798-fffff8067dd6b79a 3 bytes - nt!_guard_check_icall_fptr [ e0 23 97:d0 52 9c ] fffff8067dd6b7a0-fffff8067dd6b7a2 3 bytes - nt!_guard_dispatch_icall_fptr (+0x08) [ d0 8b 9b:20 53 9c ] Page 200 not present in the dump file. Type ".hh dbgerr004" for details fffff8067ded0b06 - nt!ExpWnfWorkItemRoutine+16 [ 05:0d ] 7 errors : !nt (fffff8067dd6b798-fffff8067ded0b06) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: LARGE STACK_COMMAND: .cxr 0xffff808ed7467150 ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE BUCKET_ID: MEMORY_CORRUPTION_LARGE PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE TARGET_TIME: 2019-07-15T13:08:56.000Z OSBUILD: 18362 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 784 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 1972-02-02 10:33:06 BUILDDATESTAMP_STR: 190318-1202 BUILDLAB_STR: 19h1_release BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202 ANALYSIS_SESSION_ELAPSED_TIME: 8c6a ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:memory_corruption_large FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c} Followup: memory_corruption -----

    Monday, July 15, 2019 1:45 PM


  • Hi,

    Since cannot find any useful information in the debug details above, please try the following general steps to troubleshoot 0x7e: 

    1. Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

    2. Check with your hardware vendor for any ACPI or other firmware updates. Hardware issues, such as system incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

    3. You can also disable memory caching/shadowing of the BIOS to try to resolve the error. You should also run hardware diagnostics, that the system manufacturer supplies.

    Please understand, the dump analysis is not supported from forum side, if the issue is urgent or cannot solved by the solutions above, it's recommended to open a business case with Microsoft. They have a higher level and may have more resources to help you.

    Thanks for your understanding.

    Best regards,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Tuesday, July 16, 2019 5:54 AM