sflalex
Mensajes enviados1Fecha de inscripcióndomingo, 4 de diciembre de 2016EstatusMiembroÚltima intervencióndomingo, 4 de diciembre de 2016
-
Modificado por sflalex el 4 dic 2016 a las 16:14
piratacrimson
Mensajes enviados16438Fecha de inscripcióndomingo, 29 de marzo de 2009EstatusMiembroÚltima intervenciónmiércoles, 8 de mayo de 2024
-
4 dic 2016 a las 20:04
Incidencia:
Se producen reinicios con pantalla azul, los siguientes casos son los más claros.
En este portátil no se han realizado cambios de hardware recientemente.
-Fallo al abrir google Chrome (al rato se reinicia con pantallazo azul).
-Fallo al ver películas (al rato se reinicia con pantallazo azul).
-Fallo del Windows Update con las actualizaciones de Office 2016.
Actuaciones:
Antivirus instalado: 360 Total Security
Programas usados frecuentemente para analizar y revisar el equipo: CCleaner, Malwarebytes Anti-Malware, Spybot-S&D Start Center.
Se han instalado las siguientes herramientas para analizar los códigos de las pantallas azules *.dmp (memory y carpeta minidump)
-WhoCrashed
-Windows kit
A continuación muestro parte del informe del WhoCrashed :
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: K53SD, ASUSTeK Computer Inc.
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8355115008 bytes total
On Fri 02/12/2016 20:15:24 your computer crashed
crash dump file: C:\Windows\Minidump\120216-41121-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A756B10, 0xFFFFFA800A756DF0, 0xFFFFF800031D3B70)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 02/12/2016 20:15:24 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A756B10, 0xFFFFFA800A756DF0, 0xFFFFF800031D3B70)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 27/11/2016 10:09:21 your computer crashed
crash dump file: C:\Windows\Minidump\112716-80543-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A5F9060, 0xFFFFFA800A5F9340, 0xFFFFF80003190B70)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 27/11/2016 9:49:00 your computer crashed
crash dump file: C:\Windows\Minidump\112716-118030-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A4D9710, 0xFFFFFA800A4D99F0, 0xFFFFF800031C3B70)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 25/11/2016 6:29:15 your computer crashed
crash dump file: C:\Windows\Minidump\112516-50185-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008194B10, 0xFFFFFA8008194DF0, 0xFFFFF800031E1B70)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
A continuación cuelgo la lectrura del memory.dmp desde WinDbg(X64) analyze-v:
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.
*
Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`0309b730
Debug session time: Fri Dec 2 20:15:24.466 2016 (UTC + 1:00)
System Uptime: 0 days 1:15:08.356
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*
Bugcheck Analysis *
*
Use !analyze -v to get detailed debugging information.
Page 1e463f not present in the dump file. Type ".hh dbgerr004" for details
Page 1e463f not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+92 )
Followup: MachineOwner
---------
Hit Enter...analize-v
analize-v
<expr> unary ops: + - not by wo dwo qwo poi hi low
binary ops: + - * / mod(%) and(&) xor(^) or(|)
comparisons: == (=) < > !=
operands: number in current radix, public symbol, <reg>
<type> : b (byte), w (word), d[s] (doubleword [with symbols]),
a (ascii), c (dword and Char), u (unicode), l (list)
f (float), D (double), s|S (ascii/unicode string)
q (quadword)
<pattern> : [(nt | <dll-name>)!]<var-name> (<var-name> can include ? and *)
<range> : <address> <address>
: <address> L <count>
Kernel-mode options:
~<processor>s - change current processor
I<b|w|d> <port> - read I/O port
O<b|w|d> <port> <expr> - write I/O
RDMSR <MSR> - read MSR
SO [<options>] - set kernel debugging options
UX [<address>] - disassemble X86 BIOS code
WRMSR <MSR> - write MSR
.cache [size] - set vmem cache size
.reboot - reboot target machine
Open debugger.chm for complete debugger documentation
0: kd> !analyze -v
*
Bugcheck Analysis *
*
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800a756b10, Terminating object
Arg3: fffffa800a756df0, Process image file name
Arg4: fffff800031d3b70, Explanatory message (ascii)
TRAP_FRAME: fffff88007be8ae0 -- (.trap 0xfffff88007be8ae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000001519f0
rdx=0000000000151500 rsi=0000000000000000 rdi=0000000000000000
rip=00000000772881ed rsp=0000000000150e20 rbp=0000000000151500
r8=0000000000000000 r9=0000000000000000 r10=000000007739f010
r11=000007fefcf3d000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
0033:00000000`772881ed ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000325d852 to fffff80002ec9400
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800a756b10, Terminating object
Arg3: fffffa800a756df0, Process image file name
Arg4: fffff800031d3b70, Explanatory message (ascii)
TRAP_FRAME: fffff88007be8ae0 -- (.trap 0xfffff88007be8ae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000001519f0
rdx=0000000000151500 rsi=0000000000000000 rdi=0000000000000000
rip=00000000772881ed rsp=0000000000150e20 rbp=0000000000151500
r8=0000000000000000 r9=0000000000000000 r10=000000007739f010
r11=000007fefcf3d000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
0033:00000000`772881ed ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000325d852 to fffff80002ec9400
piratacrimson
Mensajes enviados16438Fecha de inscripcióndomingo, 29 de marzo de 2009EstatusMiembroÚltima intervenciónmiércoles, 8 de mayo de 202411.636 4 dic 2016 a las 20:04
Hola Sr,pruebe hacerle una restauración al equipo al día que le iba bien o al día que le deje y coméntenos si lo resolvió saludos,
