Resultados 1 al 2 de 2

Problemas cuelgues de ordenador

Esta es una discusión para el tema Problemas cuelgues de ordenador en el foro Windows XP, bajo la categoría Sistemas Operativos; buenas tardes, ya escribi hace unos días porque tenía el ordenador mal y no conseguía arrancar ni siquiera la bios .Al final era el procesador y tuve que cambiarlo y ...
Página: 1


  1. #1
    Junior Member

    Fecha de ingreso
    25 dic, 06
    Mensajes
    6
    buenas tardes,

    ya escribi hace unos días porque tenía el ordenador mal y no conseguía arrancar ni siquiera la bios .Al final era el procesador y tuve que cambiarlo y todo normal pero ahora de vez en cuando se me queda tostao el ordenador y sale un mensaje en pantallazo azul de error grave......

    Os pongo el archivo memory.dmp que crea windows con los fallos por si me podeis ayudar.Tengo xp profesional y no se si tendrá algo que ver que tuve que resetear la bios cuando probaba cual podía ser el problema que tenía del procesador gracias de antemano :



    Microsoft ® Windows Debugger Version 6.6.0007.5

    Copyright © Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\WINDOWS\MEMORY.DMP]

    Kernel Complete Dump File: Full 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 ntkrnlpa.exe -

    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 2600.xpsp_sp2_gdr.050301-1519

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0

    Debug session time: Sun Dec 31 18:37:00.156 2006 (GMT+1)

    System Uptime: 0 days 4:17:49.806

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

    * 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 ntkrnlpa.exe -

    Loading Kernel Symbols

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

    Loading User Symbols

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

    Loading unloaded module list

    ...........*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -



    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

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

    * *

    * Bugcheck Analysis *

    * *

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



    Use !analyze -v to get detailed debugging information.



    BugCheck 24, {1902fe, a77d8650, a77d834c, 804ede61}



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



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



    *** ERROR: Module load completed but symbols could not be loaded for a347bus.sys

    *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys

    Probably caused by : hardware ( Ntfs+da6 )



    Followup: MachineOwner

    ---------



    kd> !analyze -v

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

    * *

    * Bugcheck Analysis *

    * *

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



    NTFS_FILE_SYSTEM (24)

    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd

    parameters are the exception record and context record. Do a .cxr

    on the 3rd parameter and then kb to obtain a more informative stack

    trace.

    Arguments:

    Arg1: 001902fe

    Arg2: a77d8650

    Arg3: a77d834c

    Arg4: 804ede61



    Debugging Details:

    ------------------



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



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





    FAULTING_MODULE: 804d7000 nt



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    EXCEPTION_RECORD: a77d8650 -- (.exr ffffffffa77d8650)

    ExceptionAddress: 804ede61 (nt!IoCheckQuerySetVolumeInformation+0x00000013)

    ExceptionCode: c0000005 (Access violation)

    ExceptionFlags: 00000000

    NumberParameters: 2

    Parameter[0]: 00000001

    Parameter[1]: 7edb14dd

    Attempt to write to address 7edb14dd



    CONTEXT: a77d834c -- (.cxr ffffffffa77d834c)

    eax=f789836c ebx=86580c98 ecx=86569ab8 edx=855651a0 esi=8653d3e8 edi=855651a0

    eip=804ede61 esp=a77d8718 ebp=a77d8720 iopl=0 nv up ei pl nz na po nc

    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202

    nt!IoCheckQuerySetVolumeInformation+0x13:

    804ede61 66808b450883f80a or byte ptr [ebx-77CF7BBh],0Ah ds:0023:7edb14dd=??

    Resetting default scope



    DEFAULT_BUCKET_ID: DRIVER_FAULT



    BUGCHECK_STR: 0x24



    MISALIGNED_IP:

    nt!IoCheckQuerySetVolumeInformation+13

    804ede61 66808b450883f80a or byte ptr [ebx-77CF7BBh],0Ah



    LAST_CONTROL_TRANSFER: from 804e64f9 to 804ede61



    STACK_TEXT:

    WARNING: Stack unwind information not available. Following frames may be wrong.

    a77d8720 804e64f9 86580be0 855651a0 855652e8 nt!IoCheckQuerySetVolumeInformation+0x13

    a77d874c 804eddf9 863f29d0 855651a0 8653d1d0 nt!CcWaitForCurrentLazyWriterActivity+0x9a1

    a77d876c 804eddf9 865cdb40 855651a0 855651a0 nt!IoBuildPartialMdl+0xed

    a77d878c f7349da6 a77d8a60 865cdb40 1b612000 nt!IoBuildPartialMdl+0xed

    a77d896c f734c6fe a77d8a60 855651a0 e15dcd90 Ntfs+0xda6

    a77d8a4c f734bfbf a77d8a60 855651a0 00000001 Ntfs+0x36fe

    a77d8bfc f74ea027 863b7020 855651a0 865cca90 Ntfs+0x2fbf

    a77d8c10 804eddf9 863b7020 855651a0 865c8550 a347bus+0x3027

    a77d8c28 804eddf9 863bc9c0 855651a0 05af0000 nt!IoBuildPartialMdl+0xed

    a77d8c4c 804ee7eb 863bc9c0 860fae08 860fae58 nt!IoBuildPartialMdl+0xed

    a77d8c6c 8051286a 85609f20 860fae78 860fae58 nt!IoPageRead+0x1b

    a77d8ce8 8051c5b0 e4882780 26c60000 c0136300 nt!MmIsAddressValid+0x2be8

    a77d8d4c 8053f6ec 00000000 26c60000 00000001 nt!MmTrimAllSystemPagableMemory+0x6e84

    a77d8ddc 80540fa2 f7322b85 860ff7a0 00000000 nt!Kei386EoiHelper+0x2674

    a77d8de0 f7322b85 860ff7a0 00000000 4022027f nt!KiDispatchInterrupt+0x5a2

    a77d8de4 860ff7a0 00000000 4022027f 00000000 NDIS+0x6b85

    a77d8de8 00000000 4022027f 00000000 00000000 0x860ff7a0





    FOLLOWUP_IP:

    Ntfs+da6

    f7349da6 807de700 cmp byte ptr [ebp-19h],0



    SYMBOL_STACK_INDEX: 4



    FOLLOWUP_NAME: MachineOwner



    IMAGE_NAME: hardware



    SYMBOL_NAME: Ntfs+da6



    STACK_COMMAND: .cxr 0xffffffffa77d834c ; kb



    MODULE_NAME: hardware



    FAILURE_BUCKET_ID: IP_MISALIGNED



    BUCKET_ID: IP_MISALIGNED



    Followup: MachineOwner

    ---------



    kd> lmvm nt

    start end module name

    804d7000 806cdc00 nt (export symbols) ntkrnlpa.exe

    Loaded symbol image file: ntkrnlpa.exe

    Image path: ntkrnlpa.exe

    Image name: ntkrnlpa.exe

    Timestamp: Wed Mar 02 01:34:37 2005 (42250A1D)

    CheckSum: 001FFC28

    ImageSize: 001F6C00

    File version: 5.1.2600.2622

    Product version: 5.1.2600.2622

    File flags: 0 (Mask 3F)

    File OS: 40004 NT Win32

    File type: 1.0 App

    File date: 00000000.00000000

    Translations: 0c0a.04b0

    CompanyName: Microsoft Corporation

    ProductName: Sistema operativo Microsoft® Windows®

    InternalName: ntkrnlpa.exe

    OriginalFilename: ntkrnlpa.exe

    ProductVersion: 5.1.2600.2622

    FileVersion: 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)

    FileDescription: Sistema y núcleo de Windows NT

    LegalCopyright: Copyright © Microsoft Corporation. Reservados todos los derechos.

     
     
  2. #2
    Junior Member

    Fecha de ingreso
    25 dic, 06
    Mensajes
    6
    me aparecio otro error irql not less or equal , desesperado estoy vaya racha que llevo gracias de antemano:



    Microsoft ® Windows Debugger Version 6.6.0007.5

    Copyright © Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\WINDOWS\MEMORY.DMP]

    Kernel Complete Dump File: Full 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 ntkrnlpa.exe -

    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 2600.xpsp_sp2_gdr.050301-1519

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0

    Debug session time: Sun Dec 31 21:54:23.875 2006 (GMT+1)

    System Uptime: 0 days 2:10:43.444

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

    * 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 ntkrnlpa.exe -

    Loading Kernel Symbols

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

    Loading User Symbols

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

    Loading unloaded module list

    ............*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -



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

    * *

    * Bugcheck Analysis *

    * *

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



    Use !analyze -v to get detailed debugging information.



    BugCheck A, {bf39c, 2, 0, 80533281}



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



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



    Probably caused by : ntkrnlpa.exe ( nt!ExInterlockedExtendZone+157 )



    Followup: MachineOwner

    ---------



    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 todo high. This is usually

    caused by drivers using improper addresses.

    If a kernel debugger is available get the stack backtrace.

    Arguments:

    Arg1: 000bf39c, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000000, value 0 = read operation, 1 = write operation

    Arg4: 80533281, address which referenced memory



    Debugging Details:

    ------------------



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



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





    MODULE_NAME: nt



    FAULTING_MODULE: 804d7000 nt



    DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d



    READ_ADDRESS: unable to get nt!MmSpecialPoolStart

    unable to get nt!MmSpecialPoolEnd

    unable to get nt!MmPoolCodeStart

    unable to get nt!MmPoolCodeEnd

    000bf39c



    CURRENT_IRQL: 2



    FAULTING_IP:

    nt!ExInterlockedExtendZone+157

    80533281 8b8744010000 mov eax,dword ptr [edi+144h]



    DEFAULT_BUCKET_ID: WRONG_SYMBOLS



    BUGCHECK_STR: 0xA



    LAST_CONTROL_TRANSFER: from 80533281 to 8053f853



    STACK_TEXT:

    WARNING: Stack unwind information not available. Following frames may be wrong.

    a87939f8 80533281 badb0d00 01c72d0b a8793a2c nt!Kei386EoiHelper+0x27db

    a8793a74 80533755 a81e1e40 000bf258 00000000 nt!ExInterlockedExtendZone+0x157

    a8793b04 80606a60 01b70000 00010000 a8793d30 nt!ExGetCurrentProcessorCounts+0x18f

    a8793d4c 8053c808 00000005 01b70000 00010000 nt!NtQuerySystemInformation+0x728

    a8793d64 7c91eb94 badb0d00 018cbc54 ffff0000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb1 4

    a8793d68 badb0d00 018cbc54 ffff0000 0000ffff ntdll!KiFastSystemCallRet

    a8793d6c 018cbc54 ffff0000 0000ffff 00000000 0xbadb0d00

    a8793d70 ffff0000 0000ffff 00000000 00000000 0x18cbc54

    a8793d74 00000000 00000000 00000000 00000000 0xffff0000





    STACK_COMMAND: kb



    FOLLOWUP_IP:

    nt!ExInterlockedExtendZone+157

    80533281 8b8744010000 mov eax,dword ptr [edi+144h]



    SYMBOL_STACK_INDEX: 1



    SYMBOL_NAME: nt!ExInterlockedExtendZone+157



    FOLLOWUP_NAME: MachineOwner



    IMAGE_NAME: ntkrnlpa.exe



    BUCKET_ID: WRONG_SYMBOLS



    Followup: MachineOwner

    ---------

     
     

Temas similares

  1. Cuelgues continuos de pc
    Por rubenuben en el foro Windows XP
    Respuestas: 2
    Último mensaje: 02/11/2006, 19:21
  2. Cuelgues PC
    Por jevirulo en el foro Windows XP
    Respuestas: 4
    Último mensaje: 30/06/2005, 18:14
  3. Cuelgues
    Por Nacho20 en el foro Seguridad informática
    Respuestas: 2
    Último mensaje: 03/04/2005, 21:39
  4. Cuelgues del ordenador
    Por eskaker en el foro Hardware
    Respuestas: 1
    Último mensaje: 08/02/2005, 22:25
  5. CUELGUES
    Por antuanol en el foro Windows XP
    Respuestas: 2
    Último mensaje: 22/11/2004, 18:47

Permisos de publicación

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