Reincio con bluescreen minidump
Cerrado
PoyoPR
Mensajes enviados
3
Fecha de inscripción
viernes, 1 de junio de 2012
Estatus
Miembro
Última intervención
jueves, 7 de noviembre de 2013
-
1 jun 2012 a las 06:59
PoyoPR Mensajes enviados 3 Fecha de inscripción viernes, 1 de junio de 2012 Estatus Miembro Última intervención jueves, 7 de noviembre de 2013 - 4 jun 2012 a las 05:54
PoyoPR Mensajes enviados 3 Fecha de inscripción viernes, 1 de junio de 2012 Estatus Miembro Última intervención jueves, 7 de noviembre de 2013 - 4 jun 2012 a las 05:54
Consulta también:
- Reincio con bluescreen minidump
- Ntoskrnl.exe bluescreen - Guide
- Nvlddmkm.sys bluescreen - Guide
- Nombre del evento de problema: BlueScreen Versión del sistema operativo: 6.1.760 - Foro de Windows
1 respuesta
PoyoPR
Mensajes enviados
3
Fecha de inscripción
viernes, 1 de junio de 2012
Estatus
Miembro
Última intervención
jueves, 7 de noviembre de 2013
4 jun 2012 a las 05:54
4 jun 2012 a las 05:54
Alguien que me ayude! aqui les pego el log del error
WARNING: Whitespace at start of path element
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060412-23883-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at start of path element
Symbol search path is:
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0x82c0f000 PsLoadedModuleList = 0x82d584d0
Debug session time: Mon Jun 4 00:50:32.818 2012 (UTC - 3:00)
System Uptime: 0 days 0:18:34.129
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
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: c0640010, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82c97086, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000009, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.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 ***
*** ***
*************************************************************************
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: 82c0f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f766ae5
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
c0640010
FAULTING_IP:
nt+88086
82c97086 8b06 mov eax,dword ptr [esi]
MM_INTERNAL_CODE: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82c50468 to 82c9d3bf
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b61e8f84 82c50468 00000000 c0640010 00000000 nt+0x8e3bf
b61e8f9c 82c97086 badb0d00 00000004 00000000 nt+0x41468
b61e9064 8b051d1f 863ddb88 00000000 00000001 nt+0x88086
b61e9084 8b04d367 85c6f728 00000020 b61e9128 Ntfs+0xdd1f
b61e9100 8b052960 b61e9320 8a92f0f8 85c6f728 Ntfs+0x9367
b61e923c 8b056720 b61e9320 85c6f728 8a92f0f8 Ntfs+0xe960
b61e9310 8b057cf7 b61e9320 85c6f728 00c8070a Ntfs+0x12720
b61e9454 82c465be 863c3020 85c6f728 85c6f728 Ntfs+0x13cf7
b61e946c 833b520c 863d5c30 85c6f728 00000000 nt+0x375be
b61e9490 833b53cb b61e94b0 863d5c30 00000000 fltmgr+0x620c
b61e94c8 82c465be 863d5c30 85c6f728 85c6f728 fltmgr+0x63cb
b61e94e0 82cd39be 863ddb40 85e79230 863ddb10 nt+0x375be
b61e94fc 82cb6590 85d069a0 85e79230 863ddb48 nt+0xc49be
b61e9594 82c9f91b 82d79100 b5f85000 863ddb10 nt+0xa7590
b61e961c 82c50468 00000000 b5f85000 00000000 nt+0x9091b
b61e9634 82e40f57 badb0d00 00000000 00000001 nt+0x41468
b61e96e8 8b0ed2d5 85d069a0 b61e9720 00001000 nt+0x231f57
b61e9710 8b0f2901 85b9f170 8a92f0f8 00005000 Ntfs+0xa92d5
b61e9740 8b0de772 85b9f170 0000000c 00000005 Ntfs+0xae901
b61e9770 8b0d4b7e 85b9f170 c43b9908 bc839060 Ntfs+0x9a772
b61e988c 8b0d6ded 85b9f170 c2d41e58 8a92f0f8 Ntfs+0x90b7e
b61e9a98 8b0f2ce6 85b9f170 864425d8 863c30d8 Ntfs+0x92ded
b61e9acc 8b0f2e2f 85b9f170 c2d41e58 3d16b04e Ntfs+0xaece6
b61e9b34 82c465be 863c3020 864425d8 864425d8 Ntfs+0xaee2f
b61e9b4c 833b520c 863d5c30 864425d8 00000000 nt+0x375be
b61e9b70 833b53cb b61e9b90 863d5c30 00000000 fltmgr+0x620c
b61e9ba8 82c465be 863d5c30 864425d8 864425d8 fltmgr+0x63cb
b61e9bc0 82e39b09 00000398 006f9ff4 82e43e7b nt+0x375be
b61e9be0 82e43ed6 863d5c30 856412f0 00000001 nt+0x22ab09
b61e9c00 82c4d27a 00000398 00000000 00000000 nt+0x234ed6
b61e9c34 77907094 badb0d00 006f9fc8 00000000 nt+0x3e27a
b61e9c38 badb0d00 006f9fc8 00000000 00000000 0x77907094
b61e9c3c 006f9fc8 00000000 00000000 00000000 0xbadb0d00
b61e9c40 00000000 00000000 00000000 00000000 0x6f9fc8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+88086
82c97086 8b06 mov eax,dword ptr [esi]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt+88086
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
WARNING: Whitespace at start of path element
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060412-23883-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at start of path element
Symbol search path is:
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0x82c0f000 PsLoadedModuleList = 0x82d584d0
Debug session time: Mon Jun 4 00:50:32.818 2012 (UTC - 3:00)
System Uptime: 0 days 0:18:34.129
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
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: c0640010, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82c97086, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000009, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.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 ***
*** ***
*************************************************************************
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: 82c0f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f766ae5
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
c0640010
FAULTING_IP:
nt+88086
82c97086 8b06 mov eax,dword ptr [esi]
MM_INTERNAL_CODE: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82c50468 to 82c9d3bf
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b61e8f84 82c50468 00000000 c0640010 00000000 nt+0x8e3bf
b61e8f9c 82c97086 badb0d00 00000004 00000000 nt+0x41468
b61e9064 8b051d1f 863ddb88 00000000 00000001 nt+0x88086
b61e9084 8b04d367 85c6f728 00000020 b61e9128 Ntfs+0xdd1f
b61e9100 8b052960 b61e9320 8a92f0f8 85c6f728 Ntfs+0x9367
b61e923c 8b056720 b61e9320 85c6f728 8a92f0f8 Ntfs+0xe960
b61e9310 8b057cf7 b61e9320 85c6f728 00c8070a Ntfs+0x12720
b61e9454 82c465be 863c3020 85c6f728 85c6f728 Ntfs+0x13cf7
b61e946c 833b520c 863d5c30 85c6f728 00000000 nt+0x375be
b61e9490 833b53cb b61e94b0 863d5c30 00000000 fltmgr+0x620c
b61e94c8 82c465be 863d5c30 85c6f728 85c6f728 fltmgr+0x63cb
b61e94e0 82cd39be 863ddb40 85e79230 863ddb10 nt+0x375be
b61e94fc 82cb6590 85d069a0 85e79230 863ddb48 nt+0xc49be
b61e9594 82c9f91b 82d79100 b5f85000 863ddb10 nt+0xa7590
b61e961c 82c50468 00000000 b5f85000 00000000 nt+0x9091b
b61e9634 82e40f57 badb0d00 00000000 00000001 nt+0x41468
b61e96e8 8b0ed2d5 85d069a0 b61e9720 00001000 nt+0x231f57
b61e9710 8b0f2901 85b9f170 8a92f0f8 00005000 Ntfs+0xa92d5
b61e9740 8b0de772 85b9f170 0000000c 00000005 Ntfs+0xae901
b61e9770 8b0d4b7e 85b9f170 c43b9908 bc839060 Ntfs+0x9a772
b61e988c 8b0d6ded 85b9f170 c2d41e58 8a92f0f8 Ntfs+0x90b7e
b61e9a98 8b0f2ce6 85b9f170 864425d8 863c30d8 Ntfs+0x92ded
b61e9acc 8b0f2e2f 85b9f170 c2d41e58 3d16b04e Ntfs+0xaece6
b61e9b34 82c465be 863c3020 864425d8 864425d8 Ntfs+0xaee2f
b61e9b4c 833b520c 863d5c30 864425d8 00000000 nt+0x375be
b61e9b70 833b53cb b61e9b90 863d5c30 00000000 fltmgr+0x620c
b61e9ba8 82c465be 863d5c30 864425d8 864425d8 fltmgr+0x63cb
b61e9bc0 82e39b09 00000398 006f9ff4 82e43e7b nt+0x375be
b61e9be0 82e43ed6 863d5c30 856412f0 00000001 nt+0x22ab09
b61e9c00 82c4d27a 00000398 00000000 00000000 nt+0x234ed6
b61e9c34 77907094 badb0d00 006f9fc8 00000000 nt+0x3e27a
b61e9c38 badb0d00 006f9fc8 00000000 00000000 0x77907094
b61e9c3c 006f9fc8 00000000 00000000 00000000 0xbadb0d00
b61e9c40 00000000 00000000 00000000 00000000 0x6f9fc8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+88086
82c97086 8b06 mov eax,dword ptr [esi]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt+88086
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
