6 Replies Latest reply on Jun 7, 2017 11:43 AM by Intel Corporation

    Windows crash (BSOD): dwm.exe X64_MEMORY_CORRUPTION_ONE_BYTE

    uispo3

      My computer got a BSOD from this error. While i was using the Intel Turbo boost Max 3.0. All i did was try to Enable/Disable the Turbo boost , and my computer got BSOD. Any idea what this error means? Have i encountered a bug?

       

      Here's the full log:

       

      MEMORY_MANAGEMENT (1a)

        # Any other values for parameter 1 must be individually examined.

      Arguments:

      Arg1: 0000000000061948, The subtype of the bugcheck.

      Arg2: 0000000000000000

      Arg3: 0000000000000001

      Arg4: 0000000000000000

       

      Debugging Details:

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

       

      TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

       

      BUGCHECK_STR: 0x1a_61948

       

      CUSTOMER_CRASH_COUNT: 1

       

      DEFAULT_BUCKET_ID: CODE_CORRUPTION

       

      PROCESS_NAME: dwm.exe

       

      CURRENT_IRQL: 2

       

      LAST_CONTROL_TRANSFER: from fffff8022ffb2774 to fffff8022ff6e310

       

      STACK_TEXT: 

      ffff9a80`949a4818 fffff802`2ffb2774 : 00000000`0000001a 00000000`00061948 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx

      ffff9a80`949a4820 fffff802`2ff8a7c5 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!MiDereferenceIoPages+0xeff80

      ffff9a80`949a48d0 fffff803`bdd78fb6 : 00000113`c0d70000 ffffab8d`93de2170 ffffab8d`8ebc7e70 00000000`00000000 : nt!MmUnlockPages+0x164325

      ffff9a80`949a49b0 fffff803`bdd788a7 : ffffc300`aee4aae0 fffff802`30155948 ffffc300`00000000 00000000`00000000 : dxgmms2!VIDMM_MDL_RANGE::Unlock+0x12

      ffff9a80`949a49e0 fffff803`bdd986b1 : ffffab8d`7f727fe8 ffffab8d`93588c40 ffff9a80`949a4ad0 fffff802`2feef540 : dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::UnlockRange+0x9b

      ffff9a80`949a4a70 fffff803`bdd93fff : ffffab8d`93588c40 ffffab8d`99cb25e8 ffff9a80`949a4b38 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedUnlock+0xad

      ffff9a80`949a4aa0 fffff803`bdd940ca : fffff803`bdd9ca10 ffffc300`b21dc6b0 ffffc300`b21dcbf8 fffff802`301fa380 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceList+0xdf

      ffff9a80`949a4b00 fffff802`2fe211c8 : 00000000`00000300 fffff803`bdd3fc00 ffffc300`00000000 00000000`000025ca : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::CurationThread+0x62

      ffff9a80`949a4b80 fffff802`2febba37 : 00000000`00000000 00000000`00000080 ffffc300`ace29040 ffffc300`aee4a7c0 : nt!ExpWorkerThread+0xd8

      ffff9a80`949a4c10 fffff802`2ff73796 : ffff9a80`8e7c7180 ffffc300`aee4a7c0 fffff802`2febb9f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47

      ffff9a80`949a4c60 00000000`00000000 : ffff9a80`949a5000 ffff9a80`9499f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

       

       

      STACK_COMMAND: kb

       

      MODULE_NAME: memory_corruption

       

      IMAGE_NAME: memory_corruption

       

      FOLLOWUP_NAME: memory_corruption

       

      DEBUG_FLR_IMAGE_TIMESTAMP: 0

       

      MEMORY_CORRUPTOR: ONE_BYTE

       

      FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BYTE

       

      BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BYTE

       

      Followup: memory_corruption

      ---------