Alta definición
Registro en forodvd
+ Responder tema
Resultados 1 al 5 de 5

Tema: Problema pantallazo azul windows 7

  1. #1
    aspirante
    Registro
    10 ago, 11
    Mensajes
    12
    Agradecido
    0 veces

    Predeterminado Problema pantallazo azul windows 7

    Regístrate para eliminar esta publicidad

    Hola.
    Tengo el problema del pantallazo azul y ya empieza a ser molesto. Solo me pasa con un juego.
    He hecho un analisis con debugging y como no se adjuntarlo lo pego aqui abajo, gracias.



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


    Loading Dump File [C:\Windows\Minidump\050114-22042-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are 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+ *
    ************************************************** *******************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03463000 PsLoadedModuleList = 0xfffff800`036a66d0
    Debug session time: Thu May 1 13:14:11.155 2014 (UTC + 2:00)
    System Uptime: 0 days 1:34:03.918
    ************************************************** *******************
    * 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+ *
    ************************************************** *******************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ....
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {0, 2, 0, fffff800034dee52}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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 ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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 ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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 : ntoskrnl.exe ( nt+7be52 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800034dee52, address which referenced memory

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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 ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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 ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command 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:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80003463000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    0000000000000000

    CURRENT_IRQL: 0

    FAULTING_IP:
    nt+7be52
    fffff800`034dee52 488b3f mov rdi,qword ptr [rdi]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    LAST_CONTROL_TRANSFER: from fffff800034d8169 to fffff800034d8bc0

    STACK_TEXT:
    fffff880`0622a778 fffff800`034d8169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt+0x75bc0
    fffff880`0622a780 00000000`0000000a : 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`034dee52 : nt+0x75169
    fffff880`0622a788 00000000`00000000 : 00000000`00000002 00000000`00000000 fffff800`034dee52 fffffa80`099025b0 : 0xa


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    nt+7be52
    fffff800`034dee52 488b3f mov rdi,qword ptr [rdi]

    SYMBOL_NAME: nt+7be52

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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

  2. #2
    colaborador Avatar de Tassadar
    Registro
    19 may, 09
    Mensajes
    9,582
    Agradecido
    8149 veces

    Predeterminado Re: Problema pantallazo azul windows 7

    Hola Ultratumbico,

    Es muy dificil aventurarse a un diagnóstico por las cosas que comentas. Si te pasa sola y exclusivamente con un juego podría ser incluso que el juego tuviese algún fichero dañado o algún bug incluso que produjese el problema con tu configuración.

    Podrías probar a estresar tanto el procesador como la gráfica con el programa OCCT, ésto te puede servir para detectar si hay alguna "debilidad" que hace que la estabilidad no sea total, o bien exista un problema de calentamiento que solo sea patente en ese juego.

    Un saludo

  3. #3
    recién llegado Avatar de yester668
    Registro
    21 may, 14
    Mensajes
    6
    Agradecido
    1 veces

    Predeterminado Re: Problema pantallazo azul windows 7

    Hola Ultratumbico,

    El error IRQL_NOT_LESS_OR_EQUAL puede dar en muchos casos.

    ¿Puedes decir con que juego te pasa y que targeta gráfica tienes?

    Saludos.

  4. #4
    Winter is Coming¡¡¡ Avatar de fmallod
    Registro
    03 mar, 14
    Mensajes
    25
    Agradecido
    0 veces

    Predeterminado Re: Problema pantallazo azul windows 7

    Los pantallazos azules en un alto porcentaje son producidos por fallos en el hardware, y sobre todo fallos en la memoria RAM.

    Saludos

  5. #5
    pulgadas de pasión Avatar de baseq2
    Registro
    30 nov, 10
    Ubicación
    Mataró
    Mensajes
    2,045
    Agradecido
    1850 veces

    Predeterminado Re: Problema pantallazo azul windows 7

    Yo voy a ir un paso más allá y me voy a aventurar a decir que es culpa del CRACK que ha usado para el juego.

    De ser original ruego que aceptes mis disculpas y que revises los foros de dicho juego por que muy posiblemente sea algún bug solucionable.
    // Mi rincón: click // Sácale partido al Htpc: click // Calibra y vencerás: click //

+ Responder tema

Temas similares

  1. Problema con resolución automática en Windows
    Por t0r en el foro HTPC: Configuraciones hardware y software
    Respuestas: 11
    Último mensaje: 05/03/2016, 23:20
  2. Pantallazo al acceder al setup de un DVD grabador
    Por jonalamper en el foro Reproductores/Grabadores DVD
    Respuestas: 0
    Último mensaje: 03/04/2013, 13:22
  3. Censo de TV Sony con pantallazo Negro
    Por garimba en el foro TV: General y consejos de compra
    Respuestas: 1
    Último mensaje: 29/10/2011, 21:02
  4. LED-TV - UE37C6530UW - problema - pantalla azul
    Por atomatom en el foro TV: General y consejos de compra
    Respuestas: 2
    Último mensaje: 06/04/2011, 00:11
  5. problema sonido hdmi 5.1 con Asus EeeBox 1501 y windows 7
    Por p300 en el foro HTPC: Configuraciones hardware y software
    Respuestas: 1
    Último mensaje: 22/11/2010, 12:49

Permisos de publicación

  • No puedes crear nuevos temas
  • No puedes responder temas
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •  
Powered by vBulletin® Version 4.2.3
Copyright © 2020 vBulletin Solutions, Inc. All rights reserved.
Search Engine Optimization by vBSEO
Image resizer by SevenSkins