Win7 SP1 Pantalla azul (0xF4)

Cerrado
sflalex Message postés 1 Date d'inscription domingo, 4 de diciembre de 2016 Estatus Miembro Última intervención domingo, 4 de diciembre de 2016 - Modificado por sflalex el 4 dic 2016 a las 16:14
piratacrimson Message postés 16117 Date d'inscription domingo, 29 de marzo de 2009 Estatus Miembro Última intervención viernes, 9 de diciembre de 2022 - 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




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

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.

BugCheck F4, {3, fffffa800a756b10, fffffa800a756df0, fffff800031d3b70}

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

x64 options:
DG <selector> - dump selector
<reg> : [r|e]ax, [r|e]bx, [r|e]cx, [r|e]dx, [r|e]si, [r|e]di, [r|e]bp, [r|e]sp, [r|e]ip, [e]fl,
r8-r15 with b/w/d subregisters
al, ah, bl, bh, cl, ch, dl, dh, cs, ds, es, fs, gs, ss
sil, dil, bpl, spl
dr0, dr1, dr2, dr3, dr6, dr7
cr0, cr2, cr3, cr4
gdtr, gdtl, idtr, idtl, tr, ldtr
xmm0-xmm15
<flag> : iopl, of, df, if, tf, sf, zf, af, pf, cf
<addr> : #<16-bit protect-mode [seg:]address>,
&<V86-mode [seg:]address>

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)

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 7601.23572.amd64fre.win7sp1_ldr.161011-0600

SYSTEM_MANUFACTURER: ASUSTeK Computer Inc.

SYSTEM_PRODUCT_NAME: K53SD

SYSTEM_SKU:

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: K53SD.202

BIOS_DATE: 11/02/2011

BASEBOARD_MANUFACTURER: ASUSTeK Computer Inc.

BASEBOARD_PRODUCT: K53SD

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: fffffa800a756b10

BUGCHECK_P3: fffffa800a756df0

BUGCHECK_P4: fffff800031d3b70

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

EXCEPTION_CODE: (Win32) 0x9d00060 (164626528) - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0x9d00060 - <Unable to get error code text>

CPU_COUNT: 8

CPU_MHZ: 893

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 23'00000000 (cache) 23'00000000 (init)

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: BB8

ANALYSIS_SESSION_TIME: 12-04-2016 16:07:33.0065

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

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

STACK_TEXT:
fffff880`07be7e48 fffff800`0325d852 : 00000000`000000f4 00000000`00000003 fffffa80`0a756b10 fffffa80`0a756df0 : nt!KeBugCheckEx
fffff880`07be7e50 fffff800`0321b09b : 00000000`00000001 fffffa80`09d00060 fffffa80`0a756b10 00000000`00150700 : nt!PspCatchCriticalBreak+0x92
fffff880`07be7e90 fffff800`03184454 : 00000000`00000001 ffffffff`ffffffff fffffa80`0a756b10 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x27296
fffff880`07be7ee0 fffff800`02ec8693 : ffffffff`ffffffff fffffa80`09d00060 fffffa80`0a756b10 00000000`00150700 : nt!NtTerminateProcess+0x284
fffff880`07be7f50 fffff800`02ec4c50 : fffff800`02f496f9 fffff880`07be8a38 fffff880`07be8790 fffff880`07be8ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07be80e8 fffff800`02f496f9 : fffff880`07be8a38 fffff880`07be8790 fffff880`07be8ae0 00000000`00152210 : nt!KiServiceLinkage
fffff880`07be80f0 fffff800`02ec8a82 : fffff880`07be8a38 00000000`000095df fffff880`07be8ae0 00000000`00151ce8 : nt! ?? ::FNODOBFM::`string'+0x40f54
fffff880`07be8900 fffff800`02ec75fa : 00000000`00000001 00000000`00150e18 fffffa80`0a756b01 00000000`000095df : nt!KiExceptionDispatch+0xc2
fffff880`07be8ae0 00000000`772881ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00150e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772881ed


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 323fc2762880972d7780d6f3d445163f6549cd8c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e0d29069e81c7109ee8a4317c34f18d9702295c9

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!PspCatchCriticalBreak+92
fffff800`0325d852 cc int 3

FAULT_INSTR_CODE: 5c8b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PspCatchCriticalBreak+92

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 57fcfdf3

IMAGE_VERSION: 6.1.7601.23572

FAILURE_BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_9d00060_nt!PspCatchCriticalBreak+92

BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_9d00060_nt!PspCatchCriticalBreak+92

PRIMARY_PROBLEM_CLASS: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_9d00060_nt!PspCatchCriticalBreak+92

TARGET_TIME: 2016-12-02T19:15:24.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-10-11 16:57:55

BUILDDATESTAMP_STR: 161011-0600

BUILDLAB_STR: win7sp1_ldr

BUILDOSVER_STR: 6.1.7601.23572.amd64fre.win7sp1_ldr.161011-0600

ANALYSIS_SESSION_ELAPSED_TIME: b94

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xf4_csrss.exe_bugcheck_critical_process_9d00060_nt!pspcatchcriticalbreak+92

FAILURE_ID_HASH: {055a9de9-f6e6-8453-6e97-a0e25fc706ac}

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

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)

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 7601.23572.amd64fre.win7sp1_ldr.161011-0600

SYSTEM_MANUFACTURER: ASUSTeK Computer Inc.

SYSTEM_PRODUCT_NAME: K53SD

SYSTEM_SKU:

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: K53SD.202

BIOS_DATE: 11/02/2011

BASEBOARD_MANUFACTURER: ASUSTeK Computer Inc.

BASEBOARD_PRODUCT: K53SD

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: fffffa800a756b10

BUGCHECK_P3: fffffa800a756df0

BUGCHECK_P4: fffff800031d3b70

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

EXCEPTION_CODE: (Win32) 0x9d00060 (164626528) - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0x9d00060 - <Unable to get error code text>

CPU_COUNT: 8

CPU_MHZ: 893

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 23'00000000 (cache) 23'00000000 (init)

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: BB8

ANALYSIS_SESSION_TIME: 12-04-2016 16:07:36.0045

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

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

STACK_TEXT:
fffff880`07be7e48 fffff800`0325d852 : 00000000`000000f4 00000000`00000003 fffffa80`0a756b10 fffffa80`0a756df0 : nt!KeBugCheckEx
fffff880`07be7e50 fffff800`0321b09b : 00000000`00000001 fffffa80`09d00060 fffffa80`0a756b10 00000000`00150700 : nt!PspCatchCriticalBreak+0x92
fffff880`07be7e90 fffff800`03184454 : 00000000`00000001 ffffffff`ffffffff fffffa80`0a756b10 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x27296
fffff880`07be7ee0 fffff800`02ec8693 : ffffffff`ffffffff fffffa80`09d00060 fffffa80`0a756b10 00000000`00150700 : nt!NtTerminateProcess+0x284
fffff880`07be7f50 fffff800`02ec4c50 : fffff800`02f496f9 fffff880`07be8a38 fffff880`07be8790 fffff880`07be8ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07be80e8 fffff800`02f496f9 : fffff880`07be8a38 fffff880`07be8790 fffff880`07be8ae0 00000000`00152210 : nt!KiServiceLinkage
fffff880`07be80f0 fffff800`02ec8a82 : fffff880`07be8a38 00000000`000095df fffff880`07be8ae0 00000000`00151ce8 : nt! ?? ::FNODOBFM::`string'+0x40f54
fffff880`07be8900 fffff800`02ec75fa : 00000000`00000001 00000000`00150e18 fffffa80`0a756b01 00000000`000095df : nt!KiExceptionDispatch+0xc2
fffff880`07be8ae0 00000000`772881ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00150e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772881ed


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 323fc2762880972d7780d6f3d445163f6549cd8c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e0d29069e81c7109ee8a4317c34f18d9702295c9

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!PspCatchCriticalBreak+92
fffff800`0325d852 cc int 3

FAULT_INSTR_CODE: 5c8b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PspCatchCriticalBreak+92

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 57fcfdf3

IMAGE_VERSION: 6.1.7601.23572

FAILURE_BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_9d00060_nt!PspCatchCriticalBreak+92

BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_9d00060_nt!PspCatchCriticalBreak+92

PRIMARY_PROBLEM_CLASS: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_9d00060_nt!PspCatchCriticalBreak+92

TARGET_TIME: 2016-12-02T19:15:24.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-10-11 16:57:55

BUILDDATESTAMP_STR: 161011-0600

BUILDLAB_STR: win7sp1_ldr

BUILDOSVER_STR: 6.1.7601.23572.amd64fre.win7sp1_ldr.161011-0600

ANALYSIS_SESSION_ELAPSED_TIME: 904

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xf4_csrss.exe_bugcheck_critical_process_9d00060_nt!pspcatchcriticalbreak+92

FAILURE_ID_HASH: {055a9de9-f6e6-8453-6e97-a0e25fc706ac}

Followup: MachineOwner

Muchas Gracias,
Espero que me indiquéis que necesitáis para poder daros mas pistas y acabar con la incidencia.

1 respuesta

piratacrimson Message postés 16117 Date d'inscription domingo, 29 de marzo de 2009 Estatus Miembro Última intervención viernes, 9 de diciembre de 2022 11.613
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,
0