Windows 10 Mavi Ekran Hatası

sinancevikoz

Hectopat
Katılım
17 Eylül 2019
Mesajlar
54
W10 Pro kurulu sisteme 4 kere format attık fakat yine video izlerken, tarayıcıda işlem yaparken vs mavi ekran hatası almaktayız. (W10 orijinal sitesinden indirilip, lisans Key'im ile aktifleştirdim)

Bütün Driverları Iobit Pro sürüm ile güncellendi.
RAM'leri çıkartılıp tekrar takıldı.
SSD kabloları kontrol edildi.
BIOS güncellendi.

Fakat her seferinde başka hata kodu veriyor. Minidump dosyalarını şuraya upload ettim. Yardımcı olabilecek var mıdır?

https://drive.google.com/open?id=1Fa...SQ65yXeQAIpTL9
 
Dün götürebildim ancak, test yaptılar herhangi bir problem olmadıgını söylediler yazılımsal problem dediler.

Windows Pro'yu resmi siteden indirip gittigidiyordan key alıp aktif etmiştim. Bu işlemi 3 kere yaptım. Ne yapmam gerekir sizce tekrar ?
 
Yazılımsal nasıl bir problem varmış 😃 Maden yazılımsal çözememişler mi?
Neyse bence donanımsal sorun var ama güncel dosyaları gönderin. Tekrar donanımsal olduğuna kanaat getirirsem bilgisi olan birine verin donanımsal kontrol yapsın.
 
Harddisk veya SSD arızası gibi duruyor galiba Vatan sizi sallamış.

Kod:
*******************************************************************************
*                                                                             *
*                        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: fffff8067b4f1842, The address that the exception occurred at
Arg3: ffff8808e08bc008, Exception Record Address
Arg4: ffff8808e08bb850, Context Record Address

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


ffff97036958c2d0: Unable to read TableSize for resource

ffff97036958c2d0: Unable to read TableSize for resource

ffff97036958c2d0: Unable to read TableSize for resource
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8067b4f1842

BUGCHECK_P3: ffff8808e08bc008

BUGCHECK_P4: ffff8808e08bb850

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP:
nt!EmpSearchTargetRuleList+12
fffff806`7b4f1842 48394808        cmp     qword ptr [rax+8],rcx

EXCEPTION_RECORD:  ffff8808e08bc008 -- (.exr 0xffff8808e08bc008)
ExceptionAddress: fffff8067b4f1842 (nt!EmpSearchTargetRuleList+0x0000000000000012)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffff8808e08bb850 -- (.cxr 0xffff8808e08bb850)
rax=74694d450303ffe0 rbx=0000000000000000 rcx=ffffbc838fb08b90
rdx=74694d4503040000 rsi=0000000000000001 rdi=ffff8808e08bc330
rip=fffff8067b4f1842 rsp=ffff8808e08bc248 rbp=ffff8808e08bc2c0
r8=ffffbc838fb08b90  r9=0000000000000000 r10=7ffffffffffffffc
r11=ffff8808e08bc2b0 r12=ffff9703711c6130 r13=0000000000000000
r14=fffff8067c95fef0 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!EmpSearchTargetRuleList+0x12:
fffff806`7b4f1842 48394808        cmp     qword ptr [rax+8],rcx ds:002b:74694d45`0303ffe8=????????????????
Resetting default scope

CPU_COUNT: c

CPU_MHZ: d48

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

FOLLOWUP_IP:
ACPI!SyncEvalObject+85
fffff806`7c8f2885 8b8c24b0000000  mov     ecx,dword ptr [rsp+0B0h]

BUGCHECK_STR:  AV

READ_ADDRESS: fffff8067b9733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

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

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  11-06-2019 21:53:43.0648

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LOCK_ADDRESS:  fffff8067b862a20 -- (!locks fffff8067b862a20)

Resource @ nt!PiEngineLock (0xfffff8067b862a20)    Exclusively owned
    Contention Count = 21
     Threads: ffff97036ff8b040-01<*>
1 total locks

PNP_TRIAGE_DATA:
    Lock address  : 0xfffff8067b862a20
    Thread Count  : 1
    Thread address: 0xffff97036ff8b040
    Thread wait   : 0x133ad1

LAST_CONTROL_TRANSFER:  from fffff8067b5dabe4 to fffff8067b5c1220

STACK_TEXT:
ffff8808`e08bc248 fffff806`7b9978e2 : 00000000`00000000 fffff806`00000000 ffff9703`00000000 00000000`00000001 : nt!EmpSearchTargetRuleList+0x12
ffff8808`e08bc250 fffff806`7c8f2885 : 00000000`00000001 ffff8808`e08bc3f1 ffff9703`711c6000 ffff9703`66f3c7b0 : nt!EmClientRuleEvaluate+0x82
ffff8808`e08bc280 fffff806`7c8f24fe : ffff9703`00000001 ffff9703`66f3c828 ffff8808`e08bc3f1 ffff9703`711c60e0 : ACPI!SyncEvalObject+0x85
ffff8808`e08bc330 fffff806`7c8fd3ea : ffff9703`63bbc7e0 ffff9703`63bb8ad0 ffff9703`00000000 ffff9703`63bb87e0 : ACPI!ACPIGet+0x2fe
ffff8808`e08bc430 fffff806`7c9867e7 : ffff9703`63b616d0 ffff8808`e08bc5e8 00000000`00000000 ffff9703`63bb87e0 : ACPI!ACPIDetectPdoDevices+0x15e
ffff8808`e08bc4c0 fffff806`7c97fa47 : ffff9703`6df47520 ffff9703`6df47520 ffff9703`63bb87e0 fffff806`7c97f850 : ACPI!ACPIRootIrpQueryBusRelations+0x53
ffff8808`e08bc530 fffff806`7c8f1266 : ffff9703`63bb87e0 00000000`00000000 ffff9703`6df47680 00000000`00000000 : ACPI!ACPIFilterIrpQueryDeviceRelations+0x1f7
ffff8808`e08bc5e0 fffff806`7b431f39 : 00000000`00000007 ffff9703`65fcbcb0 ffff9703`65fc07b0 00000000`00000000 : ACPI!ACPIDispatchIrp+0x256
ffff8808`e08bc660 fffff806`7c7af247 : 00000000`00000000 ffff9703`65bf8060 00000000`00000000 00000000`00000288 : nt!IofCallDriver+0x59
ffff8808`e08bc6a0 fffff806`7c7af189 : ffff9703`65fc07b0 00000000`0000001b 00000000`00000288 00000000`00000000 : Wdf01000!FxPkgFdo::PnpQueryDeviceRelations+0xb3 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgfdo.cpp @ 472]
ffff8808`e08bc6f0 fffff806`7c7a3c53 : ffff9703`65fc07b0 00000000`00000288 00000000`00000aa0 00000000`57647050 : Wdf01000!FxPkgFdo::_PnpQueryDeviceRelations+0x9 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgfdo.cpp @ 392]
ffff8808`e08bc720 fffff806`7c7aabd2 : ffff9703`6df47520 ffff9703`65fcbcb0 ffff9703`63b5f050 fffff806`7b433254 : Wdf01000!FxPkgPnp::Dispatch+0xb3 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffff8808`e08bc790 fffff806`7b431f39 : ffff8808`e08bc910 ffff9703`63b5f050 00000000`00000300 ffff9703`71023f60 : Wdf01000!FxDevice::DispatchWithLock+0x112 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
ffff8808`e08bc7f0 fffff806`7bb135fe : ffff9703`65fd2060 ffff9703`71023f60 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59
ffff8808`e08bc830 fffff806`7b4cfeda : ffff9703`65fd2060 00000000`00000000 ffff9703`71023f60 00000000`00000000 : nt!PnpAsynchronousCall+0xea
ffff8808`e08bc870 fffff806`7baf9acd : ffff9703`65fd39a0 00000000`00000000 ffff9703`65fd2060 ffff9703`65fd39a0 : nt!PnpSendIrp+0x5e
ffff8808`e08bc8e0 fffff806`7baf9a34 : ffff9703`71023f60 ffff9703`65fd39c8 ffff9703`65fd39a0 00000000`00000001 : nt!PnpQueryDeviceRelations+0x51
ffff8808`e08bc970 fffff806`7baf87e5 : ffff9703`65fd39a0 ffff8808`e08bca18 00000000`00000002 00000000`c0000001 : nt!PipEnumerateDevice+0xc8
ffff8808`e08bc9a0 fffff806`7bb1b1ec : ffff9703`6f7daa00 fffff806`7b439b01 ffff8808`e08bcab0 fffff806`00000002 : nt!PipProcessDevNodeTree+0x191
ffff8808`e08bca60 fffff806`7b55b917 : 00000001`00000003 ffff9703`65fab9a0 ffff9703`6f7daa80 ffff9703`6f7daa80 : nt!PiProcessReenumeration+0x88
ffff8808`e08bcab0 fffff806`7b4bd465 : ffff9703`6ff8b040 ffff9703`63b9fc80 fffff806`7b8612e0 ffff9703`6e7a1490 : nt!PnpDeviceActionWorker+0x207
ffff8808`e08bcb70 fffff806`7b52a725 : ffff9703`6ff8b040 00000000`00000080 ffff9703`63a71040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff8808`e08bcc10 fffff806`7b5c886a : ffffce01`73fc0180 ffff9703`6ff8b040 fffff806`7b52a6d0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8808`e08bcc60 00000000`00000000 : ffff8808`e08bd000 ffff8808`e08b7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  39c463c506be7a4a0d593d23a43249284ac1f4ae

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  15f9badd9c53a8d802bf38d0b4b8d0c040bdb0f8

THREAD_SHA1_HASH_MOD:  88dd1e627bbef4b53ce8be8d9af116347a1e376d

FAULT_INSTR_CODE:  b0248c8b

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ACPI!SyncEvalObject+85

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.1034

STACK_COMMAND:  .cxr 0xffff8808e08bb850 ; kb

BUCKET_ID_FUNC_OFFSET:  85

FAILURE_BUCKET_ID:  AV_ACPI!SyncEvalObject

BUCKET_ID:  AV_ACPI!SyncEvalObject

PRIMARY_PROBLEM_CLASS:  AV_ACPI!SyncEvalObject

TARGET_TIME:  2019-11-06T16:50:49.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

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

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  4d19

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_acpi!syncevalobject

FAILURE_ID_HASH:  {fcaaf35c-ccee-77b9-373e-334cdd21205d}

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

8: kd> lmvm ACPI
Browse full module list
start             end                 module name
fffff806`7c8f0000 fffff806`7c9bc000   ACPI     # (pdb symbols)          C:\ProgramData\dbg\sym\acpi.pdb\5E4888CCC770732D5646C12FF84E1DD41\acpi.pdb
    Loaded symbol image file: ACPI.sys
    Mapped memory image file: C:\ProgramData\dbg\sym\ACPI.sys\90B929F2cc000\ACPI.sys
    Image path: \SystemRoot\System32\drivers\ACPI.sys
    Image name: ACPI.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        90B929F2 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         000C4A0F
    ImageSize:        000CC000
    File version:     10.0.18362.1034
    Product version:  10.0.18362.1034
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ACPI.sys
        OriginalFilename: ACPI.sys
        ProductVersion:   10.0.18362.1034
        FileVersion:      10.0.18362.1034 (WinBuild.160101.0800)
        FileDescription:  ACPI Driver for NT
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
 
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.

Geri
Yukarı