locked
Error pantallaso azul Compaq f500 RRS feed

  • Pregunta

  • Saludes partners de IT:

    Hay un portatil compaq f500 y le han instalado windows 7 y esta presentando pantallaso azul de  volcado  de memoria.. el ultimo salio winsk .sys (algo asi)

    no se le han montado drivers ... ¿Sera por que no es fabricado para windows 7? Pues Hp no da controladores para este sistema .. sera el windows ?

    Que me recomiendan


    Juan Pablo Vidal http://juanvidal.wordpress.com
    sábado, 28 de agosto de 2010 2:06

Respuestas

  • Ya me boto un buen analisis

    Mira.

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


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

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82843000 PsLoadedModuleList = 0x8298b810
    Debug session time: Sun Aug 29 09:38:18.137 2010 (UTC - 5:00)
    System Uptime: 0 days 0:24:10.242
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {838a3bec, 2, 1, 828a6baf}

    Probably caused by : memory_corruption ( nt!MmZeroPageThread+2e1 )

    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 too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 838a3bec, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 828a6baf, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829ab718
    Unable to read MiSystemVaType memory at 8298b160
     838a3bec

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MmZeroPageThread+2e1
    828a6baf f00fba2800      lock bts dword ptr [eax],0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  80786c4c -- (.trap 0xffffffff80786c4c)
    ErrCode = 00000002
    eax=838a3bec ebx=838a3bec ecx=8478e902 edx=00000000 esi=838a3be4 edi=ffff38ff
    eip=828a6baf esp=80786cc0 ebp=80786d44 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MmZeroPageThread+0x2e1:
    828a6baf f00fba2800      lock bts dword ptr [eax],0   ds:0023:838a3bec=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 828a6baf to 8288982b

    STACK_TEXT: 
    80786c4c 828a6baf badb0d00 00000000 82811ba9 nt!KiTrap0E+0x2cf
    80786d44 829ce49b 00000000 80786d90 82a516d3 nt!MmZeroPageThread+0x2e1
    80786d50 82a516d3 8080a398 9f8649a6 00000000 nt!Phase1Initialization+0x14
    80786d90 829030f9 829ce487 8080a398 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MmZeroPageThread+2e1
    828a6baf f00fba2800      lock bts dword ptr [eax],0

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MmZeroPageThread+2e1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

    BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

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


    Juan Pablo Vidal http://juanvidal.wordpress.com


    Puede ser memoria... pero puede ser machaque de areas de otro driver.

    ¿has pasado el analisis de memoria de windows?...


    Jose Manuel Tella Llop news://jmtella.com

    domingo, 29 de agosto de 2010 14:56

Todas las respuestas

  • Saludes partners de IT:

    Hay un portatil compaq f500 y le han instalado windows 7 y esta presentando pantallaso azul de  volcado  de memoria.. el ultimo salio winsk .sys (algo asi)

    no se le han montado drivers ... ¿Sera por que no es fabricado para windows 7? Pues Hp no da controladores para este sistema .. sera el windows ?

    Que me recomiendan


    Juan Pablo Vidal http://juanvidal.wordpress.com

    Analiza el dump, y dejanos el resultado por aquí: http://www.multingles.net/docs/jmt/bsod.htm

     


    Jose Manuel Tella Llop news://jmtella.com

    sábado, 28 de agosto de 2010 7:41
  • Saludes:

    Yo lo tengo configurado para el volcado de memoria sea con la opcion del kernel,, pero no encuentro el arhcivo memory.dmp y el archivo de paginacion se encuentra en la misma particion de windows.

    con los archivos minidump no me bota nada extraño...

    voy a esperar otro error para ver si lo grava..

    gracias


    Juan Pablo Vidal http://juanvidal.wordpress.com
    domingo, 29 de agosto de 2010 14:22
  • Saludes:

    Yo lo tengo configurado para el volcado de memoria sea con la opcion del kernel,, pero no encuentro el arhcivo memory.dmp y el archivo de paginacion se encuentra en la misma particion de windows.

    con los archivos minidump no me bota nada extraño...

    voy a esperar otro error para ver si lo grava..

    gracias


    Juan Pablo Vidal http://juanvidal.wordpress.com

    Dejame aqui la salida del analisis de un minidump...

     


    Jose Manuel Tella Llop news://jmtella.com

    domingo, 29 de agosto de 2010 14:31
  • Ya me boto un buen analisis

    Mira.

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


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

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82843000 PsLoadedModuleList = 0x8298b810
    Debug session time: Sun Aug 29 09:38:18.137 2010 (UTC - 5:00)
    System Uptime: 0 days 0:24:10.242
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {838a3bec, 2, 1, 828a6baf}

    Probably caused by : memory_corruption ( nt!MmZeroPageThread+2e1 )

    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 too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 838a3bec, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 828a6baf, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829ab718
    Unable to read MiSystemVaType memory at 8298b160
     838a3bec

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MmZeroPageThread+2e1
    828a6baf f00fba2800      lock bts dword ptr [eax],0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  80786c4c -- (.trap 0xffffffff80786c4c)
    ErrCode = 00000002
    eax=838a3bec ebx=838a3bec ecx=8478e902 edx=00000000 esi=838a3be4 edi=ffff38ff
    eip=828a6baf esp=80786cc0 ebp=80786d44 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MmZeroPageThread+0x2e1:
    828a6baf f00fba2800      lock bts dword ptr [eax],0   ds:0023:838a3bec=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 828a6baf to 8288982b

    STACK_TEXT: 
    80786c4c 828a6baf badb0d00 00000000 82811ba9 nt!KiTrap0E+0x2cf
    80786d44 829ce49b 00000000 80786d90 82a516d3 nt!MmZeroPageThread+0x2e1
    80786d50 82a516d3 8080a398 9f8649a6 00000000 nt!Phase1Initialization+0x14
    80786d90 829030f9 829ce487 8080a398 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MmZeroPageThread+2e1
    828a6baf f00fba2800      lock bts dword ptr [eax],0

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MmZeroPageThread+2e1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

    BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

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


    Juan Pablo Vidal http://juanvidal.wordpress.com
    domingo, 29 de agosto de 2010 14:46
  • Ya me boto un buen analisis

    Mira.

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


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

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82843000 PsLoadedModuleList = 0x8298b810
    Debug session time: Sun Aug 29 09:38:18.137 2010 (UTC - 5:00)
    System Uptime: 0 days 0:24:10.242
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {838a3bec, 2, 1, 828a6baf}

    Probably caused by : memory_corruption ( nt!MmZeroPageThread+2e1 )

    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 too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 838a3bec, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 828a6baf, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829ab718
    Unable to read MiSystemVaType memory at 8298b160
     838a3bec

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MmZeroPageThread+2e1
    828a6baf f00fba2800      lock bts dword ptr [eax],0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  80786c4c -- (.trap 0xffffffff80786c4c)
    ErrCode = 00000002
    eax=838a3bec ebx=838a3bec ecx=8478e902 edx=00000000 esi=838a3be4 edi=ffff38ff
    eip=828a6baf esp=80786cc0 ebp=80786d44 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MmZeroPageThread+0x2e1:
    828a6baf f00fba2800      lock bts dword ptr [eax],0   ds:0023:838a3bec=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 828a6baf to 8288982b

    STACK_TEXT: 
    80786c4c 828a6baf badb0d00 00000000 82811ba9 nt!KiTrap0E+0x2cf
    80786d44 829ce49b 00000000 80786d90 82a516d3 nt!MmZeroPageThread+0x2e1
    80786d50 82a516d3 8080a398 9f8649a6 00000000 nt!Phase1Initialization+0x14
    80786d90 829030f9 829ce487 8080a398 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MmZeroPageThread+2e1
    828a6baf f00fba2800      lock bts dword ptr [eax],0

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MmZeroPageThread+2e1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

    BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

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


    Juan Pablo Vidal http://juanvidal.wordpress.com


    Puede ser memoria... pero puede ser machaque de areas de otro driver.

    ¿has pasado el analisis de memoria de windows?...


    Jose Manuel Tella Llop news://jmtella.com

    domingo, 29 de agosto de 2010 14:56
  • Ya pase el analisis pero donde veo el resultado del analisis?

    igual cambie de slot de momoria y desinstale contorladores ... me inclino por controladores sin embargo vamos a ver que pasa

    Gracias Jose por la Ayuda


    Juan Pablo Vidal http://juanvidal.wordpress.com
    domingo, 29 de agosto de 2010 16:47
  • Ya pase el analisis pero donde veo el resultado del analisis?

    igual cambie de slot de momoria y desinstale contorladores ... me inclino por controladores sin embargo vamos a ver que pasa

    Gracias Jose por la Ayuda


    Juan Pablo Vidal http://juanvidal.wordpress.com

    Me inclino mas por memoria... De todas maneras, comentanos...

    Jose Manuel Tella Llop news://jmtella.com

    lunes, 30 de agosto de 2010 3:21