Share via

Got Error code BugCheck 139 on WIndows 10

Anonymous
2019-01-16T15:00:59+00:00

Hi all,

Recently, i got BSOD after boot on about 5 - 6 minutes.

The minidump file is :

https://drive.google.com/open?id=0B1pNCTx7OkYQbkczMlpreVFPMjQ

BugCheck 139, {3, ffffed8baa14d700, ffffed8baa14d658, 0}

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-01-16T17:03:38+00:00

    From what I can tell, it looks like you have bad memory stick(s).

    Here is a link from HP. Although it is from HP the BIOS should be very similar.

    If your BIOS is different and can't find it, send me your brand and model number of your computer.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-01-16T17:04:00+00:00

    https://support.hp.com/us-en/document/c02097000

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

    0 comments
  3. Sumit 43,796 Reputation points Volunteer Moderator
    2019-01-16T16:17:26+00:00

    Hi,

    Probably caused by : dxgmms2.sys ( dxgmms2! ?? ::NNGAKEGL::`string'+2c87 )

    Completely remove everything of Graphics driver using DDU and install the newest copy of the driver available.

    http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

    You can head to either the card manufacturer or device manufacturer to get the newest driver.

    Let us know if you require any assistance.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-01-16T15:17:22+00:00

    Hi Fernando,

    Thanks for quick reply. Here is the dump text.

    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\Vincent\Desktop\011619-11671-01.dmp]

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

    ************* Symbol Path validation summary **************

    Response                         Time (ms)     Location

    Deferred                                       SRV* C:\Symbols *http://msdl.microsoft.com/download/symbols

    Symbol search path is: SRV* C:\Symbols *http://msdl.microsoft.com/download/symbols

    Executable search path is: 

    Windows 10 Kernel Version 17763 MP (12 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff80475e1d000 PsLoadedModuleList = 0xfffff80476237a50

    Debug session time: Wed Jan 16 21:09:01.774 2019 (UTC + 8:00)

    System Uptime: 3 days 22:54:56.555

    Loading Kernel Symbols

    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

    Run !sym noisy before .reload to track down problems loading symbols.

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

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

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

    Loading User Symbols

    Loading unloaded module list

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

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 139, {3, ffffed8baa14d700, ffffed8baa14d658, 0}

    *** 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

    2: kd> !analyze -v

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    KERNEL_SECURITY_CHECK_FAILURE (139)

    A kernel component has corrupted a critical data structure.  The corruption

    could potentially allow a malicious user to gain control of this machine.

    Arguments:

    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).

    Arg2: ffffed8baa14d700, Address of the trap frame for the exception that caused the bugcheck

    Arg3: ffffed8baa14d658, Address of the exception record for the exception that caused the bugcheck

    Arg4: 0000000000000000, Reserved

    Debugging Details:

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER:  System manufacturer

    SYSTEM_PRODUCT_NAME:  System Product Name

    SYSTEM_SKU:  SKU

    SYSTEM_VERSION:  System Version

    BIOS_VENDOR:  American Megatrends Inc.

    BIOS_VERSION:  4024

    BIOS_DATE:  09/07/2018

    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT:  ROG STRIX B350-F GAMING

    BASEBOARD_VERSION:  Rev X.0x

    DUMP_TYPE:  2

    BUGCHECK_P1: 3

    BUGCHECK_P2: ffffed8baa14d700

    BUGCHECK_P3: ffffed8baa14d658

    BUGCHECK_P4: 0

    TRAP_FRAME:  ffffed8baa14d700 -- (.trap 0xffffed8baa14d700)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=000000000d00116c rbx=0000000000000000 rcx=0000000000000003

    rdx=ffff8380000097b8 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff80475ffbee0 rsp=ffffed8baa14d890 rbp=0000000000000002

     r8=0000000000000000  r9=0000000000000044 r10=0000000000000002

    r11=ffff838000007220 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei ng nz ac pe cy

    nt!MiLargePageFreeToZero+0x1b23f0:

    fffff804`75ffbee0 cd29            int     29h

    Resetting default scope

    EXCEPTION_RECORD:  ffffed8baa14d658 -- (.exr 0xffffed8baa14d658)

    ExceptionAddress: fffff80475ffbee0 (nt!MiLargePageFreeToZero+0x00000000001b23f0)

       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

      ExceptionFlags: 00000001

    NumberParameters: 1

       Parameter[0]: 0000000000000003

    Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

    CPU_COUNT: c

    CPU_MHZ: d42

    CPU_VENDOR:  AuthenticAMD

    CPU_FAMILY: 17

    CPU_MODEL: 8

    CPU_STEPPING: 2

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  CODE_CORRUPTION

    BUGCHECK_STR:  0x139

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ERROR_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

    EXCEPTION_CODE_STR:  c0000409

    EXCEPTION_PARAMETER1:  0000000000000003

    ANALYSIS_SESSION_HOST:  VINCENT

    ANALYSIS_SESSION_TIME:  01-16-2019 23:13:13.0042

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    LAST_CONTROL_TRANSFER:  from fffff80475fe0369 to fffff80475fceb40

    STACK_TEXT:  

    ffffed8baa14d3d8 fffff80475fe0369 : 0000000000000139 0000000000000003 ffffed8baa14d700 ffffed8baa14d658 : nt!KeBugCheckEx

    ffffed8baa14d3e0 fffff80475fe0710 : 000000000000002f fffff8047688dae6 0000000000000000 ffffed8baa14d800 : nt!KiBugCheckDispatch+0x69

    ffffed8baa14d520 fffff80475fdeb08 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiFastFailDispatch+0xd0

    ffffed8baa14d700 fffff80475ffbee0 : fffff80476259a00 0000000000386800 ffff9f0400000000 fffff80400000000 : nt!KiRaiseSecurityCheckFailure+0x308

    ffffed8baa14d890 fffff80475f1f612 : 0000000000000000 0000000000000000 0000000000000000 fffff80476257700 : nt!MiLargePageFreeToZero+0x1b23f0

    ffffed8baa14d910 fffff80475f94d9c : 0000000000000000 ffff9f0445a85ce0 0000000000000002 fffff80476259a00 : nt!MiZeroPage+0x602

    ffffed8baa14db50 fffff80475eac625 : fffff80476259a00 fffff80400000000 fffff80400000000 b4257d5c00000008 : nt!MiZeroPageThread+0x1fc

    ffffed8baa14dc10 fffff80475fd5f9c : ffff8e8184c5b180 ffff9f0445b54040 fffff80475eac5d0 941d589c985d589a : nt!PspSystemThreadStartup+0x55

    ffffed8baa14dc60 0000000000000000 : ffffed8baa14e000 ffffed8baa148000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x1c

    STACK_COMMAND:  kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

        fffff80475e97184 - nt!MiInsertDecayClusterTimer+14

    [ fa:80 ]

        fffff80475eb3549-fffff80475eb354a  2 bytes - nt!MiUnlockPagedAddress+21 (+0x1c3c5)

    [ 80 f6:00 c5 ]

        fffff80475eb3584 - nt!MiUnlockPagedAddress+5c (+0x3b)

    [ fa:80 ]

        fffff80475f94e13 - nt!MiZeroPageThread+273 (+0xe188f)

    [ fa:80 ]

        fffff80475f94e5b - nt!MiZeroPageThread+2bb (+0x48)

    [ fa:80 ]

    6 errors : !nt (fffff80475e97184-fffff80475f94e5b)

    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:  2019-01-16T13:09:01.000Z

    OSBUILD:  17763

    OSSERVICEPACK:  253

    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:  180914-1434

    BUILDLAB_STR:  rs5_release

    BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: 2fa0

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:memory_corruption_large

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

    Followup:     memory_corruption

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-01-16T15:04:56+00:00

    Hi 阿明哦

    My name is Fernando. I am an Independent Advisor. I am here to guide you with your Error code BugCheck 139 on WIndows 10.

    Here is a document explaining what this might be, but also suggests examination of the DMP file. Can you provide use with the dmp file?

    https://docs.microsoft.com/en-us/windows-hardwa...

    I hope this helps. Feel free to ask me any questions and let me know how it goes.

    Respectfully,

    Fernando Y.

    Was this answer helpful?

    0 comments