Resultados 1 al 7 de 7

Tema: pantallazo azul en xp

  1. #1
    Crystal Maiden Avatar de -RylaiCrestFall-
    Fecha de Ingreso
    22 oct, 08
    Ubicación
    En el Dota
    Mensajes
    52

    pantallazo azul en xp

    me sale una pantalla azul y volcado de memoria fisica y se reinicia

    q puede ser ????

  2. #2
    Just be Avatar de VaMPiRu
    Fecha de Ingreso
    06 may, 05
    Ubicación
    mp3please.com
    Mensajes
    2,597

    Re: pantallazo azul en xp

    Eso es por algo de hardware y/o software que es incompatible con el XP o está dañado.

    Normalmente suele ser la memoria o la gráfica para el hardware. La manera de saberlo al 100% es ir sustituyendo cada pieza e ir probando a ver si se arregla.

    Pasa un MEMTEST. Revisa todos los drivers funcionen correctamente y que sean para XP. También si hay updates de los mismos.
    Última edición por VaMPiRu; 29/10/2008 a las 08:09

  3. #3

    Re: pantallazo azul en xp

    Anota el codigo de error que te sale y googlealo.

  4. #4

    Re: pantallazo azul en xp

    Puden ser varias cosas. Yo te diría que si tenés posibilidades de formatear y reinstalar el SO, lo hagas. En caso de que aún reinstalando el winXP (después de formatear, obvio, no lo hagas sobre el que ya tenés) te sigue ocurriendo, probamos un par de cosas a nivel hardware (limpieza más que nada)

    btw, no uses windows colossus o ue o alguna otra versión "recortada".

  5. #5
    Crystal Maiden Avatar de -RylaiCrestFall-
    Fecha de Ingreso
    22 oct, 08
    Ubicación
    En el Dota
    Mensajes
    52

    Re: pantallazo azul en xp

    mi pces nueva , la natifua la bote hace 3 meses por eso creo q es raro q sea hardware
    le pase el debbuging tool for win xp me arrojo esto.

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: SRV*c:\websymbols*Symbol information


    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Oct 28 20:43:27.609 2008 (GMT-5)
    System Uptime: 0 days 0:32:33.349
    Loading Kernel Symbols
    .................................................. .................................................. ...................
    Loading User Symbols
    Loading unloaded module list
    ..........
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10000050, {e3945000, 0, 8052d77f, 1}


    Could not read faulting driver name
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e3945000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8052d77f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000001, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: e3945000

    FAULTING_IP:
    nt!RtlInitUnicodeString+1b
    8052d77f f266af repne scas word ptr es:[edi]

    MM_INTERNAL_CODE: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x50

    PROCESS_NAME: IEXPLORE.EXE

    LAST_CONTROL_TRANSFER: from 8054060c to 8052d77f

    STACK_TEXT:
    b42a8d48 8054060c 00000b3c 0735f6a0 0735f6c3 nt!RtlInitUnicodeString+0x1b
    b42a8d48 b5f75d98 00000b3c 0735f6a0 0735f6c3 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b42a8d7c 00000000 00000000 00000000 00000000 0xb5f75d98


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80579dc4-80579dd9 22 bytes - nt!NtSetInformationFile
    [ 6a 64 68 e0 93 4d 80 e8:b8 c4 9d 57 80 3d c9 9d ]
    22 errors : !nt (80579dc4-80579dd9)

    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

    Followup: memory_corruption
    ---------

    0: kd> lmvm memory_corruption
    start end module name
    0: kd> lmvm memory_corruption
    start end module name
    0: kd> start
    *** WARNING: Unable to verify timestamp for dump_nvata.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_nvata.sys
    *** WARNING: Unable to verify timestamp for secdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for secdrv.sys
    *** WARNING: Unable to verify timestamp for RtkHDAud.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
    *** WARNING: Unable to verify timestamp for nv4_mini.sys
    *** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
    *** WARNING: Unable to verify timestamp for NVNRM.SYS
    *** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS
    *** WARNING: Unable to verify timestamp for HDAudBus.sys
    *** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
    *** WARNING: Unable to verify timestamp for nvata.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvata.sys
    *** WARNING: Unable to verify timestamp for DepFrzLo.sys
    *** ERROR: Module load completed but symbols could not be loaded for DepFrzLo.sys
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for NVENETFD.sys
    *** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys
    *** WARNING: Unable to verify timestamp for AmdK8.sys
    *** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys
    *** WARNING: Unable to verify timestamp for nvnetbus.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvnetbus.sys
    *** WARNING: Unable to verify timestamp for fdc.sys
    *** ERROR: Module load completed but symbols could not be loaded for fdc.sys
    *** WARNING: Unable to verify timestamp for HBKernel32.sys
    *** ERROR: Module load completed but symbols could not be loaded for HBKernel32.sys
    *** WARNING: Unable to verify timestamp for DepFrzHi.sys
    *** ERROR: Module load completed but symbols could not be loaded for DepFrzHi.sys
    *** WARNING: Unable to verify timestamp for nv4_disp.dll
    *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
    Couldn't resolve error at 'tart'
    0: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e3945000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8052d77f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000001, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: e3945000

    FAULTING_IP:
    nt!RtlInitUnicodeString+1b
    8052d77f f266af repne scas word ptr es:[edi]

    MM_INTERNAL_CODE: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x50

    PROCESS_NAME: IEXPLORE.EXE

    LAST_CONTROL_TRANSFER: from 8054060c to 8052d77f

    STACK_TEXT:
    b42a8d48 8054060c 00000b3c 0735f6a0 0735f6c3 nt!RtlInitUnicodeString+0x1b
    b42a8d48 b5f75d98 00000b3c 0735f6a0 0735f6c3 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b42a8d7c 00000000 00000000 00000000 00000000 0xb5f75d98


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80579dc4-80579dd9 22 bytes - nt!NtSetInformationFile
    [ 6a 64 68 e0 93 4d 80 e8:b8 c4 9d 57 80 3d c9 9d ]
    22 errors : !nt (80579dc4-80579dd9)

    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

    Followup: memory_corruption
    ---------

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e3945000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8052d77f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000001, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: e3945000

    FAULTING_IP:
    nt!RtlInitUnicodeString+1b
    8052d77f f266af repne scas word ptr es:[edi]

    MM_INTERNAL_CODE: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x50

    PROCESS_NAME: IEXPLORE.EXE

    LAST_CONTROL_TRANSFER: from 8054060c to 8052d77f

    STACK_TEXT:
    b42a8d48 8054060c 00000b3c 0735f6a0 0735f6c3 nt!RtlInitUnicodeString+0x1b
    b42a8d48 b5f75d98 00000b3c 0735f6a0 0735f6c3 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b42a8d7c 00000000 00000000 00000000 00000000 0xb5f75d98


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80579dc4-80579dd9 22 bytes - nt!NtSetInformationFile
    [ 6a 64 68 e0 93 4d 80 e8:b8 c4 9d 57 80 3d c9 9d ]
    22 errors : !nt (80579dc4-80579dd9)

    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

    Followup: memory_corruption
    ---------

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e3945000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8052d77f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000001, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: e3945000

    FAULTING_IP:
    nt!RtlInitUnicodeString+1b
    8052d77f f266af repne scas word ptr es:[edi]

    MM_INTERNAL_CODE: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x50

    PROCESS_NAME: IEXPLORE.EXE

    LAST_CONTROL_TRANSFER: from 8054060c to 8052d77f

    STACK_TEXT:
    b42a8d48 8054060c 00000b3c 0735f6a0 0735f6c3 nt!RtlInitUnicodeString+0x1b
    b42a8d48 b5f75d98 00000b3c 0735f6a0 0735f6c3 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b42a8d7c 00000000 00000000 00000000 00000000 0xb5f75d98


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80579dc4-80579dd9 22 bytes - nt!NtSetInformationFile
    [ 6a 64 68 e0 93 4d 80 e8:b8 c4 9d 57 80 3d c9 9d ]
    22 errors : !nt (80579dc4-80579dd9)

    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

    Followup: memory_corruption
    ---------

    mi pces nueva , la natifua la bote hace 2 meses por eso creo q es raro q sea hardware
    le pase el debbuging tool for win xp me arrojo esto.

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: SRV*c:\websymbols*Symbol information


    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Oct 28 20:43:27.609 2008 (GMT-5)
    System Uptime: 0 days 0:32:33.349
    Loading Kernel Symbols
    .................................................. .................................................. ...................
    Loading User Symbols
    Loading unloaded module list
    ..........
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10000050, {e3945000, 0, 8052d77f, 1}


    Could not read faulting driver name
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e3945000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8052d77f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000001, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: e3945000

    FAULTING_IP:
    nt!RtlInitUnicodeString+1b
    8052d77f f266af repne scas word ptr es:[edi]

    MM_INTERNAL_CODE: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x50

    PROCESS_NAME: IEXPLORE.EXE

    LAST_CONTROL_TRANSFER: from 8054060c to 8052d77f

    STACK_TEXT:
    b42a8d48 8054060c 00000b3c 0735f6a0 0735f6c3 nt!RtlInitUnicodeString+0x1b
    b42a8d48 b5f75d98 00000b3c 0735f6a0 0735f6c3 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b42a8d7c 00000000 00000000 00000000 00000000 0xb5f75d98


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80579dc4-80579dd9 22 bytes - nt!NtSetInformationFile
    [ 6a 64 68 e0 93 4d 80 e8:b8 c4 9d 57 80 3d c9 9d ]
    22 errors : !nt (80579dc4-80579dd9)

    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

    Followup: memory_corruption
    ---------
    Última edición por -RylaiCrestFall-; 29/10/2008 a las 19:34 Razón: Automerged Doublepost

  6. #6
    Just be Avatar de VaMPiRu
    Fecha de Ingreso
    06 may, 05
    Ubicación
    mp3please.com
    Mensajes
    2,597

    Re: pantallazo azul en xp

    Todos del iexplore.exe? lol!

    Elimina el Internet Explorer o reinstálalo y prueba de nuevo.

  7. #7
    Shilen Saint [UltraEia] Avatar de sugusrojo
    Fecha de Ingreso
    26 sep, 07
    Ubicación
    Enfrente del monitor
    Mensajes
    1,601

    Re: pantallazo azul en xp

    Proba de testear la memoria o directamnte cambiandola si podes

Permisos de Publicación

  • No puedes crear nuevos temas
  • No puedes responder temas
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •  

ESCORTS Capital Federal | ESCORTS Zona Sur | ESCORTS Zona Norte | ESCORTS Zona Oeste | ESCORTS Mar del Plata | ESCORTS La Plata | ESCORTS Cordoba | ESCORTS Rosario | ESCORTS Tucuman | Escorts Almagro | Escorts Belgrano | Escorts Caballito | Escorts Centro | Escorts Flores | Escorts Microcentro | Escorts Once | Escorts Palermo | Escorts Recoleta | Escorts Tribunales | Escorts Devoto | Escorts Villa Urquiza | Escorts Caba