Acer Nitro 5 AN515-55 mavi ekran hatası

S

sekilvedat

Centipat
Katılım
19 Ekim 2020
Mesajlar
20
Daha fazla  
Cinsiyet
Erkek
Merhabalar 4 gün önce elime geçen Acer Nitro 5 AN515-55 dizüstü bilgisayarım da ne zaman kapatıp açsam, uyku moduna alsam ya da kapağını kapatıp geri açsam mavi ekran hatası alıyorum. Yardımcı olabilir misiniz?
İşletim sistemi: Windows 10 Pro 64 Bit.
RAM: 16 GB.
İşlemci: i5 10300H.
Ekran kartı: GTX 1650 Ti.
 
Tarihe göre sırala Puana göre sırala

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
 
Artı 1 Eksi

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
 
Artı 1 Eksi
sekilvedat dedi:
Merhabalar 4 gün önce elime geçen Acer Nitro 5 AN515-55 dizüstü bilgisayarım da ne zaman kapatıp açsam, uyku moduna alsam ya da kapağını kapatıp geri açsam mavi ekran hatası alıyorum yardımcı olabilir misiniz?
İşletim sistemi: Windows 10 Pro 64 Bit.
RAM: 16 GB.
İşlemci: i5 10300H.
Ekran kartı: GTX 1650 Ti.
Genişletmek için tıkla...

Bora Dere dedi:

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
Genişletmek için tıkla...

Nasıl dosyaları buraya atabilirim?

ViooYa dedi:

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
Genişletmek için tıkla...

Dosyaları nasıl buraya atabilirim?
 
Artı 0 Eksi
Merhabalar. 4 gün önce elime geçen Acer Nitro5 AN515-55 dizüstü bilgisayarımda ne zaman kapatıp açsam, uyku moduna alsam ya da kapağını kapatıp geri açsam mavi ekran hatası alıyorum yardımcı olabilir misiniz?
İşletim sistemi: Windows 10 Pro 64 Bit.
RAM: 16 GB.
İşlemci: i5 10300H.
Ekran kartı: GTX 1650 Ti.
Minidump dosyaları: minidump.rar
 
Artı 0 Eksi
Ürününüz için BIOS ve sürücü indirme sayfanızı ekliyorum. Ürününüzü kontrol ettikten sonra indirin. Acer Nitro5 AN515-55

  1. BIOS versiyonunuz çok eski. 1.07 sürümüne güncelleyin.
  2. Intel Bluetooth sürücünüzü güncelleyin.
  3. Chipset sürücünüzü güncelleyin.
  4. NVIDIA'ya ait ekran kartı sürücünüzü DDU ile kaldırın ve güncel WHQL sürüm yükleyin.

    Rehber: DDU ile Sürücü Kaldırma Rehberi

    Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
    www.technopat.net www.technopat.net

  5. HD Tune programıyla quick scan kapalı şekilde disklerinizi kontrol edin.
Kod: 
Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa7668.34939\101920-9328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`31200000 PsLoadedModuleList = 0xfffff801`316432f0
Debug session time: Mon Oct 19 12:55:37.225 2020 (UTC + 3:00)
System Uptime: 0 days 0:27:56.991
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`313bc900 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb580`22646c20=00000000000000ef
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffcd8f64633340, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4515

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-IPC9T25

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 48924

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 77

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffcd8f64633340

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

EXCEPTION_RECORD:  ffffcd8f64633900 -- (.exr 0xffffcd8f64633900)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

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

CUSTOMER_CRASH_COUNT:  1

EXCEPTION_STR:  0x0

STACK_TEXT:
ffffb580`22646c18 fffff801`31ac6c59     : 00000000`000000ef ffffcd8f`64633340 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffb580`22646c20 fffff801`319ce1ff     : ffffcd8f`64633340 fffff801`312a4319 ffffcd8f`64633340 fffff801`312a4470 : nt!PspCatchCriticalBreak+0x115
ffffb580`22646cc0 fffff801`31836da0     : ffffcd8f`00000000 00000000`00000000 ffffcd8f`64633340 ffffcd8f`64633340 : nt!PspTerminateAllThreads+0x17fabb
ffffb580`22646d30 fffff801`31836b89     : ffffffff`ffffffff ffffb580`22646e60 ffffcd8f`64633340 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffb580`22646d70 fffff801`313ce115     : 00007ffa`00000e4c ffffcd8f`646b4080 ffffcd8f`64633340 ffffb580`22646fb0 : nt!NtTerminateProcess+0xa9
ffffb580`22646de0 fffff801`313c06c0     : fffff801`3143251c ffffb580`22647958 ffffb580`22647958 ffffb580`22646fb0 : nt!KiSystemServiceCopyEnd+0x25
ffffb580`22646f78 fffff801`3143251c     : ffffb580`22647958 ffffb580`22647958 ffffb580`22646fb0 00007ffa`68e54000 : nt!KiServiceLinkage
ffffb580`22646f80 fffff801`313ce81d     : ffffcd8f`64633900 fffff801`3128e89d 00000000`00001a00 ffffb580`22647a00 : nt!KiDispatchException+0x16398c
ffffb580`22647820 fffff801`313caa05     : 00000091`c50088f0 ffffb580`22647a80 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
ffffb580`22647a00 00007ffa`6d41e322     : 00000000`00000000 00000091`00000000 00007ffa`6bd08161 00007ffa`6d4a119f : nt!KiPageFault+0x445
00000091`c50015a0 00000000`00000000     : 00000091`00000000 00007ffa`6bd08161 00007ffa`6d4a119f 00007ffa`68e54000 : 0x00007ffa`6d41e322


SYMBOL_NAME:  nt!PspCatchCriticalBreak+115

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.239

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  115

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_646b4080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9937f3d6-0855-fe8b-1516-e605a8845d89}

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


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


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa7668.25827\101920-8468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`1b200000 PsLoadedModuleList = 0xfffff803`1b6432f0
Debug session time: Mon Oct 19 19:08:46.032 2020 (UTC + 3:00)
System Uptime: 0 days 5:16:56.797
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`1b3bc900 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc680`932374b0=000000000000007a
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffa6800d8d1d68, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000014ff75860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80333def470, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3624

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 59716

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 7a

BUGCHECK_P1: ffffa6800d8d1d68

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 14ff75860

BUGCHECK_P4: fffff80333def470

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME:  ffffc68093237860 -- (.trap 0xffffc68093237860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80333def470 rbx=0000000000000000 rcx=ffffcd885e142060
rdx=ffffcd885fbec3d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80333def470 rsp=ffffc680932379f8 rbp=ffffcd885e142060
r8=ffffcd884f2f7190 r9=8000000000002000 r10=fffff80333def470
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
kbdclass!KeyboardClassCreateWaitWakeIrpWorker:
fffff803`33def470 4053 push rbx
Resetting default scope

STACK_TEXT:
ffffc680`932374a8 fffff803`1b41beb0 : 00000000`0000007a ffffa680`0d8d1d68 ffffffff`c000000e 00000001`4ff75860 : nt!KeBugCheckEx
ffffc680`932374b0 fffff803`1b29508d : 00000000`00000003 ffffc680`00000000 ffffc680`93237668 fffffb80`00000000 : nt!MiWaitForInPageComplete+0x1867e0
ffffc680`932375c0 fffff803`1b27abab : 00000000`c0033333 00000000`00000000 fffff803`33def470 fffff803`33def470 : nt!MiIssueHardFault+0x1ad
ffffc680`932376c0 fffff803`1b3ca920 : ffffe281`c1ee0180 ffffcd88`5d3e3080 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x40b
ffffc680`93237860 fffff803`33def470 : fffff803`1b26f80f 00000000`00000000 ffffcd88`5c2571b0 ffffcd88`5e142060 : nt!KiPageFault+0x360
ffffc680`932379f8 fffff803`1b26f80f : 00000000`00000000 ffffcd88`5c2571b0 ffffcd88`5e142060 ffffcd88`5dcfb040 : kbdclass!KeyboardClassCreateWaitWakeIrpWorker
ffffc680`93237a00 fffff803`1b2c4855 : ffffcd88`4f0b4cc0 ffffcd88`5d745040 fffff803`1b26f710 ffffcd88`0000000c : nt!IopProcessWorkItem+0xff
ffffc680`93237a70 fffff803`1b32f725 : ffffcd88`5d745040 00000000`00000080 ffffcd88`4f080380 ffffcd88`5badd1f0 : nt!ExpWorkerThread+0x105
ffffc680`93237b10 fffff803`1b3c3e6a : ffffe281`c1b00180 ffffcd88`5d745040 fffff803`1b32f6d0 fffff803`1b3f424f : nt!PspSystemThreadStartup+0x55
ffffc680`93237b60 00000000`00000000 : ffffc680`93238000 ffffc680`93231000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME: nt!MiWaitForInPageComplete+1867e0

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.239

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1867e0

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {329318b9-5fab-73eb-d104-f79603e1bdb3}

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


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


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa7668.47954\101920-8390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`75200000 PsLoadedModuleList = 0xfffff807`756432f0
Debug session time: Mon Oct 19 13:51:27.508 2020 (UTC + 3:00)
System Uptime: 0 days 0:00:57.274
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`753bc900 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff184`76be1c20=00000000000000ef
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffd289c7da8300, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4452

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 28349

Key : Analysis.Memory.CommitPeak.Mb
Value: 76

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffd289c7da8300

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

EXCEPTION_RECORD:  ffffd289c7da88c0 -- (.exr 0xffffd289c7da88c0)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

EXCEPTION_STR: 0x0

STACK_TEXT:
fffff184`76be1c18 fffff807`75ac6c59 : 00000000`000000ef ffffd289`c7da8300 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff184`76be1c20 fffff807`759ce1ff : ffffd289`c7da8300 fffff807`752a4319 ffffd289`c7da8300 fffff807`752a4470 : nt!PspCatchCriticalBreak+0x115
fffff184`76be1cc0 fffff807`75836da0 : ffffd289`00000000 00000000`00000000 ffffd289`c7da8300 ffffd289`c7da8300 : nt!PspTerminateAllThreads+0x17fabb
fffff184`76be1d30 fffff807`75836b89 : ffffffff`ffffffff fffff184`76be1e60 ffffd289`c7da8300 00000000`00000000 : nt!PspTerminateProcess+0xe0
fffff184`76be1d70 fffff807`753ce115 : 00007ff8`000001f8 ffffd289`c8534040 ffffd289`c7da8300 fffff184`76be1fb0 : nt!NtTerminateProcess+0xa9
fffff184`76be1de0 fffff807`753c06c0 : fffff807`7543251c fffff184`76be2958 fffff184`76be2958 fffff184`76be1fb0 : nt!KiSystemServiceCopyEnd+0x25
fffff184`76be1f78 fffff807`7543251c : fffff184`76be2958 fffff184`76be2958 fffff184`76be1fb0 00007ff8`ced62000 : nt!KiServiceLinkage
fffff184`76be1f80 fffff807`753ce81d : ffffd289`c7da88c0 fffff807`7528e89d 00000000`00003600 fffff184`76be2a00 : nt!KiDispatchException+0x16398c
fffff184`76be2820 fffff807`753caa05 : 00000020`a2644d30 fffff184`76be2a80 00000000`00000000 00000020`a267eb40 : nt!KiExceptionDispatch+0x11d
fffff184`76be2a00 00007ff8`d3abe322 : 00000000`00000000 00000020`00000000 00007ff8`d3b3fe0e 00000020`a2581370 : nt!KiPageFault+0x445
00000020`a25812e0 00000000`00000000 : 00000020`00000000 00007ff8`d3b3fe0e 00000020`a2581370 00007ff8`ced62000 : 0x00007ff8`d3abe322


SYMBOL_NAME: nt!PspCatchCriticalBreak+115

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.239

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 115

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c8534040_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f7a7d268-caef-7940-1096-39e7d3c9c6af}

Followup: MachineOwner
---------
 
Artı 0 Eksi
ViooYa dedi:
Ürününüz için BIOS ve sürücü indirme sayfanızı ekliyorum. Ürününüzü kontrol ettikten sonra indirin. Acer Nitro5 AN515-55

  1. BIOS versiyonunuz çok eski. 1.07 sürümüne güncelleyin.
  2. Intel Bluetooth sürücünüzü güncelleyin.
  3. Chipset sürücünüzü güncelleyin.
  4. NVIDIA'ya ait ekran kartı sürücünüzü DDU ile kaldırın ve güncel WHQL sürüm yükleyin.

    Rehber: DDU ile Sürücü Kaldırma Rehberi

    Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
    www.technopat.net www.technopat.net

  5. HD Tune programıyla quick scan kapalı şekilde disklerinizi kontrol edin.
Kod: 
Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa7668.34939\101920-9328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`31200000 PsLoadedModuleList = 0xfffff801`316432f0
Debug session time: Mon Oct 19 12:55:37.225 2020 (UTC + 3:00)
System Uptime: 0 days 0:27:56.991
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`313bc900 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb580`22646c20=00000000000000ef
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffcd8f64633340, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4515

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-IPC9T25

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 48924

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 77

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffcd8f64633340

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

EXCEPTION_RECORD:  ffffcd8f64633900 -- (.exr 0xffffcd8f64633900)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

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

CUSTOMER_CRASH_COUNT:  1

EXCEPTION_STR:  0x0

STACK_TEXT:
ffffb580`22646c18 fffff801`31ac6c59     : 00000000`000000ef ffffcd8f`64633340 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffb580`22646c20 fffff801`319ce1ff     : ffffcd8f`64633340 fffff801`312a4319 ffffcd8f`64633340 fffff801`312a4470 : nt!PspCatchCriticalBreak+0x115
ffffb580`22646cc0 fffff801`31836da0     : ffffcd8f`00000000 00000000`00000000 ffffcd8f`64633340 ffffcd8f`64633340 : nt!PspTerminateAllThreads+0x17fabb
ffffb580`22646d30 fffff801`31836b89     : ffffffff`ffffffff ffffb580`22646e60 ffffcd8f`64633340 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffb580`22646d70 fffff801`313ce115     : 00007ffa`00000e4c ffffcd8f`646b4080 ffffcd8f`64633340 ffffb580`22646fb0 : nt!NtTerminateProcess+0xa9
ffffb580`22646de0 fffff801`313c06c0     : fffff801`3143251c ffffb580`22647958 ffffb580`22647958 ffffb580`22646fb0 : nt!KiSystemServiceCopyEnd+0x25
ffffb580`22646f78 fffff801`3143251c     : ffffb580`22647958 ffffb580`22647958 ffffb580`22646fb0 00007ffa`68e54000 : nt!KiServiceLinkage
ffffb580`22646f80 fffff801`313ce81d     : ffffcd8f`64633900 fffff801`3128e89d 00000000`00001a00 ffffb580`22647a00 : nt!KiDispatchException+0x16398c
ffffb580`22647820 fffff801`313caa05     : 00000091`c50088f0 ffffb580`22647a80 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
ffffb580`22647a00 00007ffa`6d41e322     : 00000000`00000000 00000091`00000000 00007ffa`6bd08161 00007ffa`6d4a119f : nt!KiPageFault+0x445
00000091`c50015a0 00000000`00000000     : 00000091`00000000 00007ffa`6bd08161 00007ffa`6d4a119f 00007ffa`68e54000 : 0x00007ffa`6d41e322


SYMBOL_NAME:  nt!PspCatchCriticalBreak+115

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.239

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  115

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_646b4080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9937f3d6-0855-fe8b-1516-e605a8845d89}

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


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


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa7668.25827\101920-8468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`1b200000 PsLoadedModuleList = 0xfffff803`1b6432f0
Debug session time: Mon Oct 19 19:08:46.032 2020 (UTC + 3:00)
System Uptime: 0 days 5:16:56.797
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`1b3bc900 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc680`932374b0=000000000000007a
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffa6800d8d1d68, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000014ff75860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80333def470, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3624

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 59716

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 7a

BUGCHECK_P1: ffffa6800d8d1d68

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 14ff75860

BUGCHECK_P4: fffff80333def470

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME:  ffffc68093237860 -- (.trap 0xffffc68093237860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80333def470 rbx=0000000000000000 rcx=ffffcd885e142060
rdx=ffffcd885fbec3d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80333def470 rsp=ffffc680932379f8 rbp=ffffcd885e142060
r8=ffffcd884f2f7190 r9=8000000000002000 r10=fffff80333def470
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
kbdclass!KeyboardClassCreateWaitWakeIrpWorker:
fffff803`33def470 4053 push rbx
Resetting default scope

STACK_TEXT:
ffffc680`932374a8 fffff803`1b41beb0 : 00000000`0000007a ffffa680`0d8d1d68 ffffffff`c000000e 00000001`4ff75860 : nt!KeBugCheckEx
ffffc680`932374b0 fffff803`1b29508d : 00000000`00000003 ffffc680`00000000 ffffc680`93237668 fffffb80`00000000 : nt!MiWaitForInPageComplete+0x1867e0
ffffc680`932375c0 fffff803`1b27abab : 00000000`c0033333 00000000`00000000 fffff803`33def470 fffff803`33def470 : nt!MiIssueHardFault+0x1ad
ffffc680`932376c0 fffff803`1b3ca920 : ffffe281`c1ee0180 ffffcd88`5d3e3080 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x40b
ffffc680`93237860 fffff803`33def470 : fffff803`1b26f80f 00000000`00000000 ffffcd88`5c2571b0 ffffcd88`5e142060 : nt!KiPageFault+0x360
ffffc680`932379f8 fffff803`1b26f80f : 00000000`00000000 ffffcd88`5c2571b0 ffffcd88`5e142060 ffffcd88`5dcfb040 : kbdclass!KeyboardClassCreateWaitWakeIrpWorker
ffffc680`93237a00 fffff803`1b2c4855 : ffffcd88`4f0b4cc0 ffffcd88`5d745040 fffff803`1b26f710 ffffcd88`0000000c : nt!IopProcessWorkItem+0xff
ffffc680`93237a70 fffff803`1b32f725 : ffffcd88`5d745040 00000000`00000080 ffffcd88`4f080380 ffffcd88`5badd1f0 : nt!ExpWorkerThread+0x105
ffffc680`93237b10 fffff803`1b3c3e6a : ffffe281`c1b00180 ffffcd88`5d745040 fffff803`1b32f6d0 fffff803`1b3f424f : nt!PspSystemThreadStartup+0x55
ffffc680`93237b60 00000000`00000000 : ffffc680`93238000 ffffc680`93231000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME: nt!MiWaitForInPageComplete+1867e0

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.239

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1867e0

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {329318b9-5fab-73eb-d104-f79603e1bdb3}

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


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


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa7668.47954\101920-8390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`75200000 PsLoadedModuleList = 0xfffff807`756432f0
Debug session time: Mon Oct 19 13:51:27.508 2020 (UTC + 3:00)
System Uptime: 0 days 0:00:57.274
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`753bc900 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff184`76be1c20=00000000000000ef
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffd289c7da8300, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4452

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 28349

Key : Analysis.Memory.CommitPeak.Mb
Value: 76

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffd289c7da8300

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

EXCEPTION_RECORD:  ffffd289c7da88c0 -- (.exr 0xffffd289c7da88c0)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

EXCEPTION_STR: 0x0

STACK_TEXT:
fffff184`76be1c18 fffff807`75ac6c59 : 00000000`000000ef ffffd289`c7da8300 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff184`76be1c20 fffff807`759ce1ff : ffffd289`c7da8300 fffff807`752a4319 ffffd289`c7da8300 fffff807`752a4470 : nt!PspCatchCriticalBreak+0x115
fffff184`76be1cc0 fffff807`75836da0 : ffffd289`00000000 00000000`00000000 ffffd289`c7da8300 ffffd289`c7da8300 : nt!PspTerminateAllThreads+0x17fabb
fffff184`76be1d30 fffff807`75836b89 : ffffffff`ffffffff fffff184`76be1e60 ffffd289`c7da8300 00000000`00000000 : nt!PspTerminateProcess+0xe0
fffff184`76be1d70 fffff807`753ce115 : 00007ff8`000001f8 ffffd289`c8534040 ffffd289`c7da8300 fffff184`76be1fb0 : nt!NtTerminateProcess+0xa9
fffff184`76be1de0 fffff807`753c06c0 : fffff807`7543251c fffff184`76be2958 fffff184`76be2958 fffff184`76be1fb0 : nt!KiSystemServiceCopyEnd+0x25
fffff184`76be1f78 fffff807`7543251c : fffff184`76be2958 fffff184`76be2958 fffff184`76be1fb0 00007ff8`ced62000 : nt!KiServiceLinkage
fffff184`76be1f80 fffff807`753ce81d : ffffd289`c7da88c0 fffff807`7528e89d 00000000`00003600 fffff184`76be2a00 : nt!KiDispatchException+0x16398c
fffff184`76be2820 fffff807`753caa05 : 00000020`a2644d30 fffff184`76be2a80 00000000`00000000 00000020`a267eb40 : nt!KiExceptionDispatch+0x11d
fffff184`76be2a00 00007ff8`d3abe322 : 00000000`00000000 00000020`00000000 00007ff8`d3b3fe0e 00000020`a2581370 : nt!KiPageFault+0x445
00000020`a25812e0 00000000`00000000 : 00000020`00000000 00007ff8`d3b3fe0e 00000020`a2581370 00007ff8`ced62000 : 0x00007ff8`d3abe322


SYMBOL_NAME: nt!PspCatchCriticalBreak+115

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.239

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 115

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c8534040_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f7a7d268-caef-7940-1096-39e7d3c9c6af}

Followup: MachineOwner
---------
Genişletmek için tıkla...
Söylenen işlemlerin hepsini uyguladım ama bir sonuç alamayınca bilgisayarımı reset atıp Driver Booster ile bütün sürücülerimi güncelleyip tekrar deneyince yine bir sonuç alamadım.
Yeni minidump dosyaları: 102020-6250-01.zip
 
Artı 0 Eksi
sekilvedat dedi:
Driver Booster ile bütün sürücülerimi güncelleyip
Genişletmek için tıkla...
Hatanın sebebi şimdi belli oldu, muhtemelen bilgisayar eline geçtiğinde de bunu yaptın.

Formatla temiz kurulum yap. Yaptıktan sonra da sürücülerini elle kur, sürücü bulucu yazılımlara başvurma.

Otomatik sürücü bulan yazılımlar çok yüksek oranla eski, yanlış sürücüleri kurar ve mavi ekran alınmasına sebebiyet verir. Keşke en başında Driver Booster kullandığını belirtseydin, donanımsal bir sorun olup olmadığını kontrol ettirir, donanımsal sorun yoksa direkt temiz kurulum yapmanı söylerdik.
 
Artı 0 Eksi
KITT dedi:
Hatanın sebebi şimdi belli oldu, muhtemelen bilgisayar eline geçtiğinde de bunu yaptın.

Formatla temiz kurulum yap. Yaptıktan sonra da sürücülerini elle kur, sürücü bulucu yazılımlara başvurma.

Otomatik sürücü bulan yazılımlar çok yüksek oranla eski, yanlış sürücüleri kurar ve mavi ekran alınmasına sebebiyet verir. Keşke en başında Driver Booster kullandığını belirtseydin, donanımsal bir sorun olup olmadığını kontrol ettirir, donanımsal sorun yoksa direkt temiz kurulum yapmanı söylerdik.
Genişletmek için tıkla...
Bilgisayar elime geçtiğinde manuel olarak sürücülerimi güncelledim -Acer'in kendi web sitesinden- sorunun onunla alakalı olduğunu sanmıyorum.
sekilvedat dedi:
Bilgisayar elime geçtiğinde manuel olarak sürücülerimi güncelledim -Acer'in kendi web sitesinden- sorunun onunla alakalı olduğunu sanmıyorum. Ama şuan bilgisayarıma format atılıyor umarım sorun çözülür.
Genişletmek için tıkla...
 
Artı 0 Eksi

Benzer konular

A
  • Soru
Acer Nitro AN515-55 açılırken mavi ekran hatası
2
Mesaj
16
Görüntüleme
936
ygt_bydrr
ygt_bydrr
doloreshaze
  • Soru
Acer Nitro 5 AN515-55 Sebepsizce Başlayan Mavi Ekran Hatası
Mesaj
7
Görüntüleme
331
freakcnsl
freakcnsl
melih121
  • Soru
Nitro 5 AN515-55 mavi ekran hatası
Mesaj
4
Görüntüleme
287
melih121
melih121
Raionxx
  • Soru
Acer Nitro 5 AN515-57 mavi ekran hatası
Mesaj
4
Görüntüleme
163
Raionxx
Raionxx
ygt_bydrr
  • Soru
Acer Nitro 5 AN515-57 mavi ekran hatası
2 3
Mesaj
24
Görüntüleme
1B
ygt_bydrr
ygt_bydrr

Yeni konular

Yeni mesajlar

Geri
Yukarı