Mavi Ekran Hatası

Thekeysi

Megapat
Katılım
8 Mayıs 2017
Mesajlar
463
Makaleler
1
Çözümler
2
Yer
İstanbul/Üsküdar
Daha fazla  
Cinsiyet
Erkek
Arkadaşlar, son birkaç gündür yıllardır kullandığım ve sorun yaşamadığım taşınabilir harddiski'mi PC'ye takınca mavi ekran hatası almaya başladım. Harddiski TV'ye takınca sorun olmuyor yani içindeki dosyaları görebiliyorum ve filmleri izleyebiliyorum.

 
DDU ile ekran kartı sürücüsünü kaldırıp yeniden kurun.

Aşağıdaki rehberi uygulayın.

BİOS'u güncelleyin.

Windows 10 20H2 sürümüne geçin.


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


Loading Dump File [C:\Users\maksu\Desktop\121220-7750-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`5da00000 PsLoadedModuleList = 0xfffff805`5de461b0
Debug session time: Sat Dec 12 13:13:43.161 2020 (UTC + 3:00)
System Uptime: 1 days 18:04:28.826
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`5dbc3b20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9a06`cc58daf0=000000000000007e
5: 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: fffff8055dad6401, The address that the exception occurred at
Arg3: ffff9a06cc58eb08, Exception Record Address
Arg4: ffff9a06cc58e350, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 5343

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 23904

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

    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:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8055dad6401

BUGCHECK_P3: ffff9a06cc58eb08

BUGCHECK_P4: ffff9a06cc58e350

EXCEPTION_RECORD:  ffff9a06cc58eb08 -- (.exr 0xffff9a06cc58eb08)
ExceptionAddress: fffff8055dad6401 (nt!CcGetVirtualAddress+0x0000000000000221)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000220
Attempt to write to address 0000000000000220

CONTEXT:  ffff9a06cc58e350 -- (.cxr 0xffff9a06cc58e350)
rax=0000000000000000 rbx=ffffffffee400000 rcx=0000000011040207
rdx=ffff9d85fe38a078 rsi=ffff9d85fb58b2e8 rdi=ffffffffee400000
rip=fffff8055dad6401 rsp=ffff9a06cc58ed40 rbp=0000000000000001
 r8=0000000000600000  r9=ffff9a06cc58ee2c r10=ffff9d85fb56d6c0
r11=ffff9a06cc58ef98 r12=0000000000000001 r13=0000000000000000
r14=ffff9d85fe38a010 r15=ffff9d85efbc9a80
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!CcGetVirtualAddress+0x221:
fffff805`5dad6401 f0ff8020020000  lock inc dword ptr [rax+220h] ds:002b:00000000`00000220=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

WRITE_ADDRESS: fffff8055df713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8055de283b8: Unable to get Flags value from nt!KdVersionBlock
fffff8055de283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000000220

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000220

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffff9a06`cc58ed40 fffff805`5dad4883     : 00000000`00000000 ffff9d85`00000001 ffff9a06`cc58ee20 ffff9a06`cc58ee2c : nt!CcGetVirtualAddress+0x221
ffff9a06`cc58ede0 fffff805`5e0bcf5e     : 00000000`00000001 ffff9a06`cc58efa0 ffff9d85`00001000 00000000`00001000 : nt!CcPinFileData+0xb3
ffff9a06`cc58eee0 fffff805`62aafef7     : ffffffff`ee400000 ffff9a06`cc58f000 00000000`00001000 ffff9a06`00000001 : nt!CcPinRead+0xee
ffff9a06`cc58efa0 ffffffff`ee400000     : ffff9a06`cc58f000 00000000`00001000 ffff9a06`00000001 ffff9a06`cc58f288 : Ntfs+0xbfef7
ffff9a06`cc58efa8 ffff9a06`cc58f000     : 00000000`00001000 ffff9a06`00000001 ffff9a06`cc58f288 ffff9a06`cc58f180 : 0xffffffff`ee400000
ffff9a06`cc58efb0 00000000`00001000     : ffff9a06`00000001 ffff9a06`cc58f288 ffff9a06`cc58f180 ffff8701`5f093e20 : 0xffff9a06`cc58f000
ffff9a06`cc58efb8 ffff9a06`00000001     : ffff9a06`cc58f288 ffff9a06`cc58f180 ffff8701`5f093e20 ffff9d85`f779c180 : 0x1000
ffff9a06`cc58efc0 ffff9a06`cc58f288     : ffff9a06`cc58f180 ffff8701`5f093e20 ffff9d85`f779c180 ffff8701`5f093e20 : 0xffff9a06`00000001
ffff9a06`cc58efc8 ffff9a06`cc58f180     : ffff8701`5f093e20 ffff9d85`f779c180 ffff8701`5f093e20 fffff805`62b49da2 : 0xffff9a06`cc58f288
ffff9a06`cc58efd0 ffff8701`5f093e20     : ffff9d85`f779c180 ffff8701`5f093e20 fffff805`62b49da2 00000000`00000000 : 0xffff9a06`cc58f180
ffff9a06`cc58efd8 ffff9d85`f779c180     : ffff8701`5f093e20 fffff805`62b49da2 00000000`00000000 ffff9d85`f779c180 : 0xffff8701`5f093e20
ffff9a06`cc58efe0 ffff8701`5f093e20     : fffff805`62b49da2 00000000`00000000 ffff9d85`f779c180 ffffffff`ee400000 : 0xffff9d85`f779c180
ffff9a06`cc58efe8 fffff805`62b49da2     : 00000000`00000000 ffff9d85`f779c180 ffffffff`ee400000 ffff9d86`00000001 : 0xffff8701`5f093e20
ffff9a06`cc58eff0 00000000`00000000     : ffff9d85`f779c180 ffffffff`ee400000 ffff9d86`00000001 ffff9a06`cc58f288 : Ntfs+0x159da2


SYMBOL_NAME:  nt!CcGetVirtualAddress+221

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.1256

STACK_COMMAND:  .cxr 0xffff9a06cc58e350 ; kb

BUCKET_ID_FUNC_OFFSET:  221

FAILURE_BUCKET_ID:  AV_nt!CcGetVirtualAddress

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {29384a72-ef4d-957d-a189-e7e039df9dfc}

Followup:     MachineOwner
---------
 
DDU ile ekran kartı sürücüsünü kaldırıp yeniden kurun.

Aşağıdaki rehberi uygulayın.

BİOS'u güncelleyin.

Windows 10 20H2 sürümüne geçin.


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


Loading Dump File [C:\Users\maksu\Desktop\121220-7750-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`5da00000 PsLoadedModuleList = 0xfffff805`5de461b0
Debug session time: Sat Dec 12 13:13:43.161 2020 (UTC + 3:00)
System Uptime: 1 days 18:04:28.826
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`5dbc3b20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9a06`cc58daf0=000000000000007e
5: 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: fffff8055dad6401, The address that the exception occurred at
Arg3: ffff9a06cc58eb08, Exception Record Address
Arg4: ffff9a06cc58e350, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 5343

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 23904

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

    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:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8055dad6401

BUGCHECK_P3: ffff9a06cc58eb08

BUGCHECK_P4: ffff9a06cc58e350

EXCEPTION_RECORD:  ffff9a06cc58eb08 -- (.exr 0xffff9a06cc58eb08)
ExceptionAddress: fffff8055dad6401 (nt!CcGetVirtualAddress+0x0000000000000221)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000220
Attempt to write to address 0000000000000220

CONTEXT:  ffff9a06cc58e350 -- (.cxr 0xffff9a06cc58e350)
rax=0000000000000000 rbx=ffffffffee400000 rcx=0000000011040207
rdx=ffff9d85fe38a078 rsi=ffff9d85fb58b2e8 rdi=ffffffffee400000
rip=fffff8055dad6401 rsp=ffff9a06cc58ed40 rbp=0000000000000001
r8=0000000000600000  r9=ffff9a06cc58ee2c r10=ffff9d85fb56d6c0
r11=ffff9a06cc58ef98 r12=0000000000000001 r13=0000000000000000
r14=ffff9d85fe38a010 r15=ffff9d85efbc9a80
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!CcGetVirtualAddress+0x221:
fffff805`5dad6401 f0ff8020020000  lock inc dword ptr [rax+220h] ds:002b:00000000`00000220=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

WRITE_ADDRESS: fffff8055df713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8055de283b8: Unable to get Flags value from nt!KdVersionBlock
fffff8055de283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000220

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000220

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffff9a06`cc58ed40 fffff805`5dad4883     : 00000000`00000000 ffff9d85`00000001 ffff9a06`cc58ee20 ffff9a06`cc58ee2c : nt!CcGetVirtualAddress+0x221
ffff9a06`cc58ede0 fffff805`5e0bcf5e     : 00000000`00000001 ffff9a06`cc58efa0 ffff9d85`00001000 00000000`00001000 : nt!CcPinFileData+0xb3
ffff9a06`cc58eee0 fffff805`62aafef7     : ffffffff`ee400000 ffff9a06`cc58f000 00000000`00001000 ffff9a06`00000001 : nt!CcPinRead+0xee
ffff9a06`cc58efa0 ffffffff`ee400000     : ffff9a06`cc58f000 00000000`00001000 ffff9a06`00000001 ffff9a06`cc58f288 : Ntfs+0xbfef7
ffff9a06`cc58efa8 ffff9a06`cc58f000     : 00000000`00001000 ffff9a06`00000001 ffff9a06`cc58f288 ffff9a06`cc58f180 : 0xffffffff`ee400000
ffff9a06`cc58efb0 00000000`00001000     : ffff9a06`00000001 ffff9a06`cc58f288 ffff9a06`cc58f180 ffff8701`5f093e20 : 0xffff9a06`cc58f000
ffff9a06`cc58efb8 ffff9a06`00000001     : ffff9a06`cc58f288 ffff9a06`cc58f180 ffff8701`5f093e20 ffff9d85`f779c180 : 0x1000
ffff9a06`cc58efc0 ffff9a06`cc58f288     : ffff9a06`cc58f180 ffff8701`5f093e20 ffff9d85`f779c180 ffff8701`5f093e20 : 0xffff9a06`00000001
ffff9a06`cc58efc8 ffff9a06`cc58f180     : ffff8701`5f093e20 ffff9d85`f779c180 ffff8701`5f093e20 fffff805`62b49da2 : 0xffff9a06`cc58f288
ffff9a06`cc58efd0 ffff8701`5f093e20     : ffff9d85`f779c180 ffff8701`5f093e20 fffff805`62b49da2 00000000`00000000 : 0xffff9a06`cc58f180
ffff9a06`cc58efd8 ffff9d85`f779c180     : ffff8701`5f093e20 fffff805`62b49da2 00000000`00000000 ffff9d85`f779c180 : 0xffff8701`5f093e20
ffff9a06`cc58efe0 ffff8701`5f093e20     : fffff805`62b49da2 00000000`00000000 ffff9d85`f779c180 ffffffff`ee400000 : 0xffff9d85`f779c180
ffff9a06`cc58efe8 fffff805`62b49da2     : 00000000`00000000 ffff9d85`f779c180 ffffffff`ee400000 ffff9d86`00000001 : 0xffff8701`5f093e20
ffff9a06`cc58eff0 00000000`00000000     : ffff9d85`f779c180 ffffffff`ee400000 ffff9d86`00000001 ffff9a06`cc58f288 : Ntfs+0x159da2


SYMBOL_NAME:  nt!CcGetVirtualAddress+221

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.1256

STACK_COMMAND:  .cxr 0xffff9a06cc58e350 ; kb

BUCKET_ID_FUNC_OFFSET:  221

FAILURE_BUCKET_ID:  AV_nt!CcGetVirtualAddress

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {29384a72-ef4d-957d-a189-e7e039df9dfc}

Followup:     MachineOwner
---------
Adımları sırasıyla uygulamama rağmen hala aynı sorun devam ediyor. Farklı bir flash bellek takınca sorun yok ama taşınabilir harddiski takınca mavi ekran hatası veriyor.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı