none
Pantallas azules frecuentes RRS feed

  • Pregunta

  • Hola, hace 6 meses adquiri un equipo acer nitro 5 con Windows 10 home single, no me había generado ningún inconveniente hasta hace 1 semana en la que al abrir un programa especifico (League of legends) y al entrar en pantalla de carga de arroja pantalla azul y un error VIDEO_SCHEDULER_INTERNAL_ERROR he restablecido el equipo a fabrica actualizado desde 0 los controladores y sigue igual, descargue w10 desde la pagina oficial y lo formatee desde cero haciendo una instalación limpia y tampoco sigue apareciendo lo mismo descargue "Bluescreenview" y me arroja lo siguiente.

    ==================================================
    Archivo de volcado: 071919-26406-01.dmp
    Hora del fallo    : 19/7/2019 20:44:33
    Cadena de comprobación de error:
    Código de comprobación de error: 0x00000119
    Parámetro 1       : 00000000`00000e00
    Parámetro 2       : ffff818e`9fb91000
    Parámetro 3       : ffff818e`9fb6fbf0
    Parámetro 4       : ffff818e`9fb6fef0
    Causado por controlador: watchdog.sys
    Causado por dirección: watchdog.sys+41a0
    Descripción       : Watchdog Driver
    Nombre            : Microsoft® Windows® Operating System
    Companía          : Microsoft Corporation
    Versión           : 10.0.18362.1 (WinBuild.160101.0800)
    Procesador        : x64
    Dirección de bloqueo: ntoskrnl.exe+1bc900
    Dirección de pila 1:
    Dirección de pila 2:
    Dirección de la pila 3:
    Nombre del equipo :
    Ruta completa     : C:\Windows\Minidump\071919-26406-01.dmp
    Recuento de procesadores: 8
    Versión principal : 15
    Versión menor     : 18362
    Tamaño del archivo de volcado: 2,338,900
    Tiempo de archivo de volcado: 19/7/2019 20:48:23
    ==================================================

    También use la herramienta de winDbg pero no la se usar bien me arrojo el siguiente archivo

    Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Windows 8 Kernel Version 18362 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff805`01e00000 PsLoadedModuleList = 0xfffff805`022432f0
    Debug session time: Fri Jul 19 20:44:33.625 2019 (UTC - 5:00)
    System Uptime: 0 days 9:45:45.407
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .................
    Loading User Symbols
    
    Loading unloaded module list
    .................................
    
    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntkrnlmp               The system cannot find the file specified
    
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 119, {e00, ffff818e9fb91000, ffff818e9fb6fbf0, ffff818e9fb6fef0}
    
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms2.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : dxgmms2.sys ( dxgmms2+2a499 )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 0000000000000e00, The subtype of the bugcheck:
    Arg2: ffff818e9fb91000
    Arg3: ffff818e9fb6fbf0
    Arg4: ffff818e9fb6fef0
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    
    ADDITIONAL_DEBUG_TEXT:  
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
    
    MODULE_NAME: dxgmms2
    
    FAULTING_MODULE: fffff80501e00000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x119
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8051d3241a0 to fffff80501fbc900
    
    STACK_TEXT:  
    ffffab8d`32a65e18 fffff805`1d3241a0 : 00000000`00000119 00000000`00000e00 ffff818e`9fb91000 ffff818e`9fb6fbf0 : nt!KeBugCheckEx
    ffffab8d`32a65e20 fffff805`02a2a499 : ffff818e`9fb91000 00000000`00000000 ffffab8d`32a66270 fffff805`02a30b16 : watchdog+0x41a0
    ffffab8d`32a65e60 fffff805`02a2a5d9 : ffff818e`9fb6fbf0 ffffab8d`32a66050 ffff818e`a663cdc0 ffff818e`9fb91000 : dxgmms2+0x2a499
    ffffab8d`32a65e90 fffff805`02a2a96f : ffffab8d`32a66270 ffffab8d`00000000 ffffab8d`32a66050 ffff818e`a663cdc0 : dxgmms2+0x2a5d9
    ffffab8d`32a65f50 fffff805`02a20eb8 : 00000000`00000000 fffff805`1ed08b67 00000000`00000000 fffff805`1ed0918b : dxgmms2+0x2a96f
    ffffab8d`32a660a0 fffff805`02a0d46b : 00000000`00000000 00000000`00989680 ffff818e`9fb93bd0 00000000`00000000 : dxgmms2+0x20eb8
    ffffab8d`32a66b20 fffff805`02a154b1 : ffffab8d`32a670c0 00000000`00000000 00000000`00000000 ffffba0f`00000001 : dxgmms2+0xd46b
    ffffab8d`32a66bc0 fffff805`02a12571 : ffffab8d`32a670c0 ffff818e`a48c2bf0 00000000`00000000 fffff805`00000000 : dxgmms2+0x154b1
    ffffab8d`32a66cb0 fffff805`02a16705 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2+0x12571
    ffffab8d`32a66d70 fffff805`02a1659d : 00000000`00000000 ffffab8d`32a66ef0 ffffab8d`32a670c0 ffff818e`9fb91000 : dxgmms2+0x16705
    ffffab8d`32a66dc0 fffff805`02a105b6 : 00000000`00000000 ffffab8d`32a670c0 ffffab8d`32a66ef0 ffff818e`9fba1000 : dxgmms2+0x1659d
    ffffab8d`32a66df0 fffff805`02a2e7c3 : ffffab8d`32a670c0 ffff818e`9fb91000 00000000`00000000 ffff818e`a566b000 : dxgmms2+0x105b6
    ffffab8d`32a67060 fffff805`02a8630c : ffff818e`a2f03b00 ffff818e`9fbdf620 ffff818e`9e4f3820 ffff818e`9fb6fbf0 : dxgmms2+0x2e7c3
    ffffab8d`32a67a80 fffff805`02a8613a : ffff818e`9fb91400 fffff805`02a86070 ffff818e`9fb91000 00000000`00000000 : dxgmms2+0x8630c
    ffffab8d`32a67ad0 fffff805`01f2f725 : ffff818e`9fb9c680 fffff805`00000001 ffff818e`9fb91000 000024ef`bd9bbfff : dxgmms2+0x8613a
    ffffab8d`32a67b10 fffff805`01fc3e6a : fffff805`00502180 ffff818e`9fb9c680 fffff805`01f2f6d0 00000024`0041ce74 : nt!RtlIsNonEmptyDirectoryReparsePointAllowed+0x405
    ffffab8d`32a67b60 00000000`00000000 : ffffab8d`32a68000 ffffab8d`32a61000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x637a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms2+2a499
    fffff805`02a2a499 cc              int     3
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  dxgmms2+2a499
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  dxgmms2.sys
    
    IMAGE_VERSION:  10.0.18362.207
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:wrong_symbols
    
    FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
    
    Followup: MachineOwner
    ---------

    Ya no se que mas hacer :/


    • Editado Bryam1 domingo, 21 de julio de 2019 19:45
    domingo, 21 de julio de 2019 19:39

Todas las respuestas

  • Hola Bryam1, 

    Realmente creo que el problema podría residir en que tu pc no soporta el set de instrucciones necesario para ejecutar los requerimientos de video de LOL. Esto puede pasar especialmente si actualizaste tu S.O. de una vieja version del sistema operativo.

    Te recomendaria actualizar el driver   dxgmms2.sys, aunque si tu W10 ya está actualizado a la ultima version no habría mucho que hacer, realmente me parece que el juego NO es compatible con tu PC ya que se ve que el procesador está trabajando al máximo para intentar soportar las características graficas del juego, podrías bajar las resoluciones del juego si es que es permitido sin embargo te recomendaría verificar que tienes las características minimas para jugar el juego.

    Se la ultima version de LOL pide.

    • 2 GHz processor (supporting SSE2 instruction set or higher).
    • 1 GB RAM (2 GB of RAM for Windows Vista and newer).
    • 8 GB available hard disk space.
    • Shader version 2.0 capable video card.
    • Screen resolutions up to 1920x1200.

    En cuyo caso el problema en tu BSOD podría realmente deberse que no cuentas con tarjeta de video.

    Si gustas proporcionar las características de tu PC y te podríamos apoyar a buscar opciones.

    Gracias por usar los foros de TechNet.
    Erick Rivera
     ____
    Por favor recuerde "Marcar como respuesta" las respuestas que hayan resuelto su problema, es una forma común de reconocer a aquellos que han ayudado, y hace que sea más fácil para los otros visitantes encontrar la solución más tarde.
    Microsoft ofrece este servicio de forma gratuita, con la finalidad de ayudar a los usuarios y la ampliación de la base de datos de conocimientos relacionados con los productos y tecnologías de Microsoft. 
    Este contenido es proporcionado "tal cual" y no implica ninguna responsabilidad de parte de Microsoft.

    • Editado eRiver1 lunes, 22 de julio de 2019 4:02 grámatica
    lunes, 22 de julio de 2019 4:00
  • Hola, hmm no creo que se deba a que no tengo lo necesario para el juego adjunto las especificaciones de mi portatil

    acer nitro 5

    Intel core i5 8tva generación 2,3hz 4 nucleos

    4gbs de Ram

    Tarjeta grafica: Gforce gtx 1050 de 4gbs

    1tb de espacio

    lunes, 22 de julio de 2019 23:39
  • De hecho tu BSDO ocurre porque el procesador / el core 1 intenta reportar una falla de hardware que precisamente consiste en que el procesador parece que no está logrando procesar una instrucción ya que no la entiende, parece ser que el resultado del calculo se sale del stack del procesador. O sea es muy grande el calculo y tu procesador no tiene la cantidad necesaria para realizar dicho calculo.

    Antes de que el procesador colapse le recomendaría buscar con soporte de intel sí existe una actualización para poder ejecutar el juego.

    Y presentarles la siguiente parte.

    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter
    1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 0000000000000e00, The subtype of the bugcheck:
    Arg2: ffff818e9fb91000
    Arg3: ffff818e9fb6fbf0
    Arg4: ffff818e9fb6fef0

    https://www.mathworks.com/matlabcentral/answers/93455-what-is-the-sse2-instruction-set-how-can-i-check-to-see-if-my-processor-supports-it

    O ver los drivers mas actuales compatibles de intel con W10

    https://www.catalog.update.microsoft.com/Search.aspx?q=intel

    O buscar con el soporte de L.O.L. si es que existe alguna configuración que puedas realizar para dirigir completamente ese tipo de cálculos del juego a tu GForce, "un parche al juego"

    Déjeme saber sus comentarios

    Gracias por usar los foros de TechNet.
    Erick Rivera
     ____
    Por favor recuerde "Marcar como respuesta" las respuestas que hayan resuelto su problema, es una forma común de reconocer a aquellos que han ayudado, y hace que sea más fácil para los otros visitantes encontrar la solución más tarde.
    Microsoft ofrece este servicio de forma gratuita, con la finalidad de ayudar a los usuarios y la ampliación de la base de datos de conocimientos relacionados con los productos y tecnologías de Microsoft. 
    Este contenido es proporcionado "tal cual" y no implica ninguna responsabilidad de parte de Microsoft.




    • Editado eRiver1 jueves, 25 de julio de 2019 15:17 grámatica
    jueves, 25 de julio de 2019 15:12