Pantalla azul después de salir de modo suspensión

as007

Nuevo
Registrado
8 Mar 2018
Mensajes
2
Puntos
0
Edad
44
Buenas tardes;

Desde que me monté el ordenador, me pasa una cosa muy muy rara. El pc me funciona perfectamente, pero de forma aleatoria, a veces, cuando sale del modo de suspensión sale una pantalla azul y se reinicia.
He hecho de todo, pasado el memtest, el crystaldisk, pasado benchmarks y cambiado el antivirus y no me ha mostrado ningún error, alguien me podría ayudar?
Mi configuración es; ASROCK 980 DE3/U3S3, GTX 950, FX 6300.

El resultado de la pantalla azul es el siguiente;

Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\030818-32593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`1a487000 PsLoadedModuleList = 0xfffff800`1a7ee110
Debug session time: Thu Mar 8 17:57:11.842 2018 (UTC + 1:00)
System Uptime: 6 days 3:01:03.897
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8001a4ec2a0, fffffe80da4c0b78, fffffe80da4c03c0}
Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+50 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8001a4ec2a0, The address that the exception occurred at
Arg3: fffffe80da4c0b78, Exception Record Address
Arg4: fffffe80da4c03c0, Context Record Address
Debugging Details:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.16299.248 (WinBuild.160101.0800)
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.00
BIOS_DATE: 09/04/2015
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: 980DE3/U3S3
BASEBOARD_VERSION:
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8001a4ec2a0
BUGCHECK_P3: fffffe80da4c0b78
BUGCHECK_P4: fffffe80da4c03c0
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.
FAULTING_IP:
nt!MiDemoteCombinedPte+50
fffff800`1a4ec2a0 49394720 cmp qword ptr [r15+20h],rax
EXCEPTION_RECORD: fffffe80da4c0b78 -- (.exr 0xfffffe80da4c0b78)
ExceptionAddress: fffff8001a4ec2a0 (nt!MiDemoteCombinedPte+0x0000000000000050)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffe80da4c03c0 -- (.cxr 0xfffffe80da4c03c0)
rax=0000000000000001 rbx=521b6f0175c7a805 rcx=ffff8e00d5e79878
rdx=521b6f0175c7a805 rsi=ffff920248f59810 rdi=000001abcf30f000
rip=fffff8001a4ec2a0 rsp=fffffe80da4c0db0 rbp=fffffe80da4c0e29
r8=8000000000000000 r9=ffff92024f1059c0 r10=8000000000000000
r11=0000000000000000 r12=ffff8e00d5e79878 r13=ffff92024f1059c0
r14=fffffe80da4c1370 r15=7fffffffffffffd0
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!MiDemoteCombinedPte+0x50:
fffff800`1a4ec2a0 49394720 cmp qword ptr [r15+20h],rax ds:002b:7fffffff`fffffff0=????????????????
Resetting default scope
CPU_COUNT: 6
CPU_MHZ: c8a
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 2
CPU_STEPPING: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MicrosoftEdgeC
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
FOLLOWUP_IP:
nt!MiDemoteCombinedPte+50
fffff800`1a4ec2a0 49394720 cmp qword ptr [r15+20h],rax
BUGCHECK_STR: AV
READ_ADDRESS: fffff8001a884380: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff
ANALYSIS_SESSION_HOST: DESKTOP-O1143M1
ANALYSIS_SESSION_TIME: 03-08-2018 18:18:57.0507
ANALYSIS_VERSION: 10.0.16299.91 amd64fre
LAST_CONTROL_TRANSFER: from fffff8001a4eaba3 to fffff8001a4ec2a0
STACK_TEXT:
fffffe80`da4c0db0 fffff800`1a4eaba3 : 00000000`00000000 ffff8e00`d5e74658 00000000`00000000 521b6f01`75c7a805 : nt!MiDemoteCombinedPte+0x50
fffffe80`da4c0e90 fffff800`1a4ea76e : 00000000`00000000 ffff9202`4f1059c0 00000000`00000000 ffff8e00`d5e74658 : nt!MiAgePte+0x263
fffffe80`da4c0f50 fffff800`1a4ea670 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x75e
fffffe80`da4c1010 fffff800`1a4ea670 : 00000000`00000000 00000000`73576d4d 00000000`00000002 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x660
fffffe80`da4c10d0 fffff800`1a4ea670 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x660
fffffe80`da4c1190 fffff800`1a4e9f4f : fffffe80`da4c1480 00000000`00000000 fffffe80`da4c1270 fffffe80`da4c1270 : nt!MiWalkPageTablesRecursively+0x660
fffffe80`da4c1250 fffff800`1a4e9b91 : 00000000`00000000 fffff800`1a4ebbd0 ffff9202`46a43140 00000000`73576d4d : nt!MiWalkPageTables+0x20f
fffffe80`da4c12f0 fffff800`1a4e95b5 : ffff9202`4f1059c0 00000000`00000002 00000000`00000000 ffff9202`510e4400 : nt!MiAgeWorkingSet+0x2b1
fffffe80`da4c17f0 fffff800`1a4e8d29 : 00000000`00000000 fffffe80`da4c1a80 fffffe80`da4c19b0 00000000`0000cf3c : nt!MiTrimOrAgeWorkingSet+0x175
fffffe80`da4c18b0 fffff800`1a5230c2 : fffff800`1a80e0c0 fffff800`1a80e0c0 00000000`000000d2 00000000`000000d2 : nt!MiProcessWorkingSets+0x219
fffffe80`da4c1a60 fffff800`1a5c8260 : 00000000`00000003 00000000`00000003 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xa2
fffffe80`da4c1b20 fffff800`1a59db87 : ffff9202`46b66040 00000000`00000080 fffff800`1a5c8110 00000000`00000000 : nt!KeBalanceSetManager+0x150
fffffe80`da4c1c10 fffff800`1a603be6 : fffff800`1a20f180 ffff9202`46b66040 fffff800`1a59db40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffffe80`da4c1c60 00000000`00000000 : fffffe80`da4c2000 fffffe80`da4bc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC: e3a8964b8ac9f4183e9b225b40d450ed3989dd86
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ce86c3464759c083ef5f18d89a8e01e0e0235cfc
THREAD_SHA1_HASH_MOD: 7f608ac2fbce9034a3386b1d51652e4911d30234
FAULT_INSTR_CODE: 20473949
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiDemoteCombinedPte+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5a7e7659
IMAGE_VERSION: 10.0.16299.248
STACK_COMMAND: .cxr 0xfffffe80da4c03c0 ; kb
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: 50
FAILURE_BUCKET_ID: AV_nt!MiDemoteCombinedPte
BUCKET_ID: AV_nt!MiDemoteCombinedPte
PRIMARY_PROBLEM_CLASS: AV_nt!MiDemoteCombinedPte
TARGET_TIME: 2018-03-08T16:57:11.000Z
OSBUILD: 16299
OSSERVICEPACK: 248
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-02-10 05:34:33
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.16299.248
ANALYSIS_SESSION_ELAPSED_TIME: 11ef
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nt!midemotecombinedpte
FAILURE_ID_HASH: {c577c73b-79a7-0c44-6c62-58e1d697b6d8}
Followup: MachineOwner
---------



Agradecería que me echarais una mano.
 

Consultor

Master Chapuzas
Registrado
25 Ene 2015
Mensajes
13.269
Puntos
113
Hola as, bienvenido.

¿Desde cuando te pasa esto? ¿Alguna fecha/cambio en concreto?

Yo lo que haría, tras todas las pruebas que has hecho, es descargar la última bios y flashear, y por último y evidente, poner bios por defecto, entonces volver a suspender.

Si sigue el problema, puedes optar por otra cosa, usar la Suspensión Híbrida.
Diferencia entre suspender, hibernar y suspension hibrida

Yo he probado las tres: hibernar, suspender y suspender de forma híbrida y te digo que entre estas dos últimas, la diferencia es poca/ninguna en cuanto a "despertar" el equipo, si es cierto que se nota más lento que "suspender normal", pero tampoco es para tanto, además es una opción más segura, si no tienes un SAI/batería en el equipo, es un peligro tener el equipo suspendido (no hibrido), ya que se necesita energía constante para mantener los datos en la ram.
 

darkastro

Master Chapuzas
Registrado
5 Ene 2015
Mensajes
149
Puntos
18
Edad
41
Actualiza windows a la ultima version y los drivers del equipo, aparte haz un reset de bios y carga valores por defecto.
 
Arriba