Minidump

Discussion in 'Windows -ongelmat' started by Tsiki1, Jan 17, 2014.

  1. Tsiki1

    Tsiki1 Member

    Joined:
    Jan 16, 2013
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    11
    Pitäiskö tästä nyt ymmärtää jotain? o_O

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\011414-18859-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff802`04805000 PsLoadedModuleList = 0xfffff802`04ac9990
    Debug session time: Tue Jan 14 14:25:57.404 2014 (UTC + 2:00)
    System Uptime: 2 days 18:23:23.143
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .........................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 139, {3, ffffd00025d71550, ffffd00025d714a8, 0}

    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::prepareDmaBuffer+19090 )

    Followup: MachineOwner
    ---------

    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Unknown bugcheck code (139)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000003
    Arg2: ffffd00025d71550
    Arg3: ffffd00025d714a8
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x139

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff8020495e7e9 to fffff80204952ca0

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: ffffd00025d714c0

    STACK_COMMAND: dds FFFFD00025D714C0-0x20 ; kb

    STACK_TEXT:
    ffffd000`25d714a0 02b52000
    ffffd000`25d714a4 ffffe000
    ffffd000`25d714a8 c0000409
    ffffd000`25d714ac 00000001
    ffffd000`25d714b0 00000000
    ffffd000`25d714b4 00000000
    ffffd000`25d714b8 01873e20
    ffffd000`25d714bc fffff800
    ffffd000`25d714c0 00000001
    ffffd000`25d714c4 00000000
    ffffd000`25d714c8 00000003
    ffffd000`25d714cc 00000000
    ffffd000`25d714d0 0000018e
    ffffd000`25d714d4 00000000
    ffffd000`25d714d8 00000201
    ffffd000`25d714dc 00000000
    ffffd000`25d714e0 01e5b010
    ffffd000`25d714e4 ffffc000
    ffffd000`25d714e8 04957e45
    ffffd000`25d714ec fffff802
    ffffd000`25d714f0 00000000
    ffffd000`25d714f4 00000000
    ffffd000`25d714f8 049542b3
    ffffd000`25d714fc fffff802
    ffffd000`25d71500 00000000
    ffffd000`25d71504 00000000
    ffffd000`25d71508 04955baf
    ffffd000`25d7150c fffff802
    ffffd000`25d71510 00000000
    ffffd000`25d71514 00000000
    ffffd000`25d71518 00000000
    ffffd000`25d7151c 00000000


    FOLLOWUP_IP:
    dxgmms1!VIDMM_GLOBAL::prepareDmaBuffer+19090
    fffff800`01873e20 cd29 int 29h

    SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::prepareDmaBuffer+19090

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME: dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5277b2b7

    FAILURE_BUCKET_ID: X64_0x139_dxgmms1!VIDMM_GLOBAL::prepareDmaBuffer+19090

    BUCKET_ID: X64_0x139_dxgmms1!VIDMM_GLOBAL::prepareDmaBuffer+19090

    Followup: MachineOwner
    ---------
     
  2. 1pertti

    1pertti Senior member

    Joined:
    Sep 10, 2008
    Messages:
    9,156
    Likes Received:
    1,219
    Trophy Points:
    243
    Ainakaan foorumin sääntöjen mukaan samasta asiasta ei jatkuvasti pidä avata uusia ketjuja.
     
  3. Tsiki1

    Tsiki1 Member

    Joined:
    Jan 16, 2013
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    11
    Ei tarvitsisi tehdä jos joku vastaisi siellä valmiiksi tehdyssä ketjussa.
    http://keskustelu.afterdawn.com/t.cfm/f-122/kernel_security_check_failure_windows_8_1-970631/

    Uuden ketjun tekemällä vastauksen ongelmaan saa viimeistään päivän kuluessa, mutta kun kirjoittaa jo tehtyyn ketjuun niin vastausta ei tule saamaan tuskin koskaan.
     

Share This Page