ASUS ROG G17 G712 mavi ekran hatası

İşletim sistemi
Windows 10

Efe Yavaş

Megapat
Katılım
7 Şubat 2016
Mesajlar
42
Daha fazla  
Cinsiyet
Erkek
Arkadaşım bilgisayarı dün aldı. ASUS'un sitesinden bütün driverları eksiksiz kurduk, temiz kurulum yaptık falan bugün mavi ekran hatası verdi. Sebebi nedir acaba?

 
Son düzenleyen: Moderatör:
Her önüne geleni yüklememen gerekiyordu.
Temiz format atın tekrar. Sadece GPU sürücülerinizi kurun ve Windows güncellemelerini yapın.
Windows'u da zaten güncel kurmamışsınız. 20H2 indirip kurun.

USB cihazlarınızı da çıkarın.
Diskinizle ilgili de bir sorun olabilir format sonrası HDsentinel sağlık sonucunu paylaşın.
 
[CODE title="hata dokumanı"]
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: ffff9706d72f0108, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000405371820, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80460f819d0, 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: 4109

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 101558

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

BUGCHECK_P1: ffff9706d72f0108

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 405371820

BUGCHECK_P4: fffff80460f819d0

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

DISK_HARDWARE_ERROR: There was error with disk hardware

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff9583909cec20 -- (.trap 0xffff9583909cec20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000010 rbx=0000000000000000 rcx=0000000000000010
rdx=ffffde0fcfd201c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804605cb1d7 rsp=ffff9583909cedb0 rbp=0000000000000010
r8=0000000000000020 r9=ffff9583909ced60 r10=ffffde0fcfd201c0
r11=ffff9583909ced30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x66b1d7:
fffff804`605cb1d7 393b cmp dword ptr [rbx],edi ds:00000000`00000000=????????
Resetting default scope

STACK_TEXT:
ffff9583`909ce868 fffff804`465e2832 : 00000000`0000007a ffff9706`d72f0108 ffffffff`c000000e 00000004`05371820 : nt!KeBugCheckEx
ffff9583`909ce870 fffff804`464072ad : 00000000`00000003 ffff9583`00000000 ffff9583`909cea28 fffff804`00000000 : nt!MiWaitForInPageComplete+0x1dbc52
ffff9583`909ce980 fffff804`464cabbb : 00000000`c0033333 00000000`00000000 fffff804`60f819d0 fffff804`60f819d0 : nt!MiIssueHardFault+0x1ad
ffff9583`909cea80 fffff804`465d1b5e : ffffde0f`dbd44050 ffffde0f`cd6cc000 ffffde0f`d5f52000 fffff804`60749699 : nt!MmAccessFault+0x40b
ffff9583`909cec20 fffff804`605cb1d7 : ffffde0f`d5e8c0a0 fffff804`600cab18 00000000`00000000 fffff804`602b8499 : nt!KiPageFault+0x35e
ffff9583`909cedb0 ffffde0f`d5e8c0a0 : fffff804`600cab18 00000000`00000000 fffff804`602b8499 fffff804`606e18b0 : nvlddmkm+0x66b1d7
ffff9583`909cedb8 fffff804`600cab18 : 00000000`00000000 fffff804`602b8499 fffff804`606e18b0 fffff804`6040a83f : 0xffffde0f`d5e8c0a0
ffff9583`909cedc0 00000000`00000000 : fffff804`602b8499 fffff804`606e18b0 fffff804`6040a83f fffff804`60f819d0 : nvlddmkm+0x16ab18


SYMBOL_NAME: nvlddmkm+66b1d7

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 66b1d7

FAILURE_BUCKET_ID: 0x7a_c000000e_nvlddmkm!unknown_function

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ffb9d98c-677c-ab78-1c53-206b2a0a2990}

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

[/CODE]
[CODE title="hata dokumanı"]
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the bugcheck
Arg2: fffff8043589be82, Address of the instruction which caused the bugcheck
Arg3: ffff8805098a93f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3093

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 31326

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: 3b

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff8043589be82

BUGCHECK_P3: ffff8805098a93f0

BUGCHECK_P4: 0

CONTEXT: ffff8805098a93f0 -- (.cxr 0xffff8805098a93f0)
rax=0000000000000000 rbx=ffff8805098a9e40 rcx=0000000000000007
rdx=00000000002e43a0 rsi=0000000000000124 rdi=ffffda041924d000
rip=fffff8043589be82 rsp=ffff8805098a9de8 rbp=ffffda041924d000
r8=000000000000001c r9=ffffae8c638e3080 r10=0000020ab39d53a0
r11=00000000000003a0 r12=000000003a769e06 r13=ffff8805098aa0c0
r14=0000000000000124 r15=0000020ab3a1e024
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!HvpGetCellPaged+0xa2:
fffff804`3589be82 418b02 mov eax,dword ptr [r10] ds:002b:0000020a`b39d53a0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Registry

STACK_TEXT:
ffff8805`098a9de8 fffff804`3585429f : 00000000`d80f3f93 ffff8805`098aa120 0000020a`b3b1bb84 00000000`c0000034 : nt!HvpGetCellPaged+0xa2
ffff8805`098a9df0 fffff804`35852b99 : 00000001`ffffffff 00000000`3a769e06 00000000`d80f3f93 ffffda04`2078f0e0 : nt!CmpDoCompareKeyName+0x2f
ffff8805`098a9e40 fffff804`357fb71a : ffffda04`2078f0e0 00000000`00000001 ffff8805`098aa038 ffff8805`098aa0a0 : nt!CmpWalkOneLevel+0x709
ffff8805`098a9f50 fffff804`357f8784 : ffff8805`0000001c ffff8805`098aa2a0 ffff8805`098aa268 00000000`00000000 : nt!CmpDoParseKey+0x9fa
ffff8805`098aa1f0 fffff804`357f666f : ffffae8c`77f9ca30 ffffda04`1ea20901 00000000`00000000 00000000`00000001 : nt!CmpParseKey+0x274
ffff8805`098aa410 fffff804`357f4ad1 : ffffae8c`77f9ca00 ffff8805`098aa658 00000000`00000040 ffffae8c`633db0c0 : nt!ObpLookupObjectName+0x78f
ffff8805`098aa5d0 fffff804`357fdfec : 00000000`00000001 00000000`00000000 00000000`00000000 ffffae8c`633db0c0 : nt!ObOpenObjectByNameEx+0x201
ffff8805`098aa710 fffff804`357fde6d : 000000e7`65bade50 ffff8805`098aaa80 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x5c
ffff8805`098aa760 fffff804`357ffe8f : 00007ffa`6b488e00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmOpenKey+0x29d
ffff8805`098aa9c0 fffff804`353d5355 : 00007ffa`6b3fb6d8 ffff8805`098aaa80 000000e7`65baea60 00000000`00000000 : nt!NtOpenKeyEx+0xf
ffff8805`098aaa00 00007ffa`6c51ea44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000e7`65badd78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`6c51ea44


SYMBOL_NAME: nt!HvpGetCellPaged+a2

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1316

STACK_COMMAND: .cxr 0xffff8805098a93f0 ; kb

BUCKET_ID_FUNC_OFFSET: a2

FAILURE_BUCKET_ID: 0x3B_c0000006_nt!HvpGetCellPaged

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {68f3db38-ae8e-4bae-c37a-85819946495f}

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

[/CODE]
[CODE title="hata dokumanı"]
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: ffffa30ee0659b90, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000035e30f860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8073599e000, 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 mouclass.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4217

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 38123

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

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

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 35e30f860

BUGCHECK_P4: fffff8073599e000

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

DISK_HARDWARE_ERROR: There was error with disk hardware

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff8b89681bf840 -- (.trap 0xffff8b89681bf840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000000014f
rdx=00000000000000d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8073599e000 rsp=ffff8b89681bf9d0 rbp=ffffbb073885aa40
r8=ffffbb072bbc008a r9=0000000000000002 r10=00000000ffffffff
r11=0000000000000013 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
mouclass+0xe000:
fffff807`3599e000 ?? ???
Resetting default scope

STACK_TEXT:
ffff8b89`681bf488 fffff807`1a3e2832 : 00000000`0000007a ffffa30e`e0659b90 ffffffff`c000000e 00000003`5e30f860 : nt!KeBugCheckEx
ffff8b89`681bf490 fffff807`1a2072ad : 00000000`00000003 ffff8b89`00000000 ffff8b89`681bf648 fffffb80`00000000 : nt!MiWaitForInPageComplete+0x1dbc52
ffff8b89`681bf5a0 fffff807`1a2cabbb : 00000000`c0033333 00000000`00000000 fffff807`3599e000 fffff807`3599e000 : nt!MiIssueHardFault+0x1ad
ffff8b89`681bf6a0 fffff807`1a3d1b5e : 00000000`00000030 00000000`00000001 00000000`00000200 ffffbb07`2bbc0420 : nt!MmAccessFault+0x40b
ffff8b89`681bf840 fffff807`3599e000 : ffffbb07`2bbc0430 ffffbb07`3885aa40 fffff807`3599dfb0 ffffbb07`3653d040 : nt!KiPageFault+0x35e
ffff8b89`681bf9d0 ffffbb07`2bbc0430 : ffffbb07`3885aa40 fffff807`3599dfb0 ffffbb07`3653d040 ffffbb07`2cbf8490 : mouclass+0xe000
ffff8b89`681bf9d8 ffffbb07`3885aa40 : fffff807`3599dfb0 ffffbb07`3653d040 ffffbb07`2cbf8490 fffff807`1a213a7f : 0xffffbb07`2bbc0430
ffff8b89`681bf9e0 fffff807`3599dfb0 : ffffbb07`3653d040 ffffbb07`2cbf8490 fffff807`1a213a7f 00000000`00000000 : 0xffffbb07`3885aa40
ffff8b89`681bf9e8 ffffbb07`3653d040 : ffffbb07`2cbf8490 fffff807`1a213a7f 00000000`00000000 ffffbb07`2cbf8490 : mouclass+0xdfb0
ffff8b89`681bf9f0 ffffbb07`2cbf8490 : fffff807`1a213a7f 00000000`00000000 ffffbb07`2cbf8490 ffffbb07`3885aa40 : 0xffffbb07`3653d040
ffff8b89`681bf9f8 fffff807`1a213a7f : 00000000`00000000 ffffbb07`2cbf8490 ffffbb07`3885aa40 ffffbb07`2b332d40 : 0xffffbb07`2cbf8490
ffff8b89`681bfa00 fffff807`1a259d35 : ffffbb07`242d1a60 ffffbb07`3ba30040 fffff807`1a213980 00000143`0000000c : nt!IopProcessWorkItem+0xff
ffff8b89`681bfa70 fffff807`1a333585 : ffffbb07`3ba30040 00000000`00000080 ffffbb07`24280040 00000143`b9debaa0 : nt!ExpWorkerThread+0x105
ffff8b89`681bfb10 fffff807`1a3cb128 : ffff9301`4b380180 ffffbb07`3ba30040 fffff807`1a333530 00000143`b9de8e00 : nt!PspSystemThreadStartup+0x55
ffff8b89`681bfb60 00000000`00000000 : ffff8b89`681c0000 ffff8b89`681b9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: mouclass+e000

MODULE_NAME: mouclass

IMAGE_NAME: mouclass.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: e000

FAILURE_BUCKET_ID: 0x7a_c000000e_mouclass!unknown_function

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {826de43b-21a7-789c-4697-98e20d22faed}

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

[/CODE]
[CODE title="hata dokumanı"]
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: ffffc38ba5af6560, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000018ff16860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8002b69c960, 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: 3827

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 27555

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

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

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 18ff16860

BUGCHECK_P4: fffff8002b69c960

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

DISK_HARDWARE_ERROR: There was error with disk hardware

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff8b8b252e7860 -- (.trap 0xffff8b8b252e7860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8002b69c960 rbx=0000000000000000 rcx=ffffe58a4eedbe30
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8002b69c960 rsp=ffff8b8b252e79f8 rbp=ffffe58a4eedbe30
r8=ffffe58a611a4490 r9=8000000000002000 r10=fffff8002b69c960
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgkrnl!DpiUnmapIommuIdentityRange+0xf770:
fffff800`2b69c960 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:ffff8b8b`252e7a00=0000000000000000
Resetting default scope

STACK_TEXT:
ffff8b8b`252e74a8 fffff800`127e2832 : 00000000`0000007a ffffc38b`a5af6560 ffffffff`c000000e 00000001`8ff16860 : nt!KeBugCheckEx
ffff8b8b`252e74b0 fffff800`126072ad : 00000000`00000003 ffff8b8b`00000000 ffff8b8b`252e7668 fffff800`00000000 : nt!MiWaitForInPageComplete+0x1dbc52
ffff8b8b`252e75c0 fffff800`126cabbb : 00000000`c0033333 00000000`00000000 fffff800`2b69c960 fffff800`2b69c960 : nt!MiIssueHardFault+0x1ad
ffff8b8b`252e76c0 fffff800`127d1b5e : ffffb301`409c9180 ffffe58a`4e68f040 00000000`00000600 00000000`00000000 : nt!MmAccessFault+0x40b
ffff8b8b`252e7860 fffff800`2b69c960 : fffff800`12613a12 00000000`00000000 ffffe58a`611a4490 ffffe58a`4eedbe30 : nt!KiPageFault+0x35e
ffff8b8b`252e79f8 fffff800`12613a12 : 00000000`00000000 ffffe58a`611a4490 ffffe58a`4eedbe30 fffff800`2b8e5050 : dxgkrnl!DpiUnmapIommuIdentityRange+0xf770
ffff8b8b`252e7a00 fffff800`12659d35 : ffffe58a`4ce9b660 ffffe58a`5ebda080 fffff800`12613980 00000000`00000000 : nt!IopProcessWorkItem+0x92
ffff8b8b`252e7a70 fffff800`12733585 : ffffe58a`5ebda080 00000000`00000080 ffffe58a`4ced2080 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff8b8b`252e7b10 fffff800`127cb128 : ffffb301`40923180 ffffe58a`5ebda080 fffff800`12733530 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8b8b`252e7b60 00000000`00000000 : ffff8b8b`252e8000 ffff8b8b`252e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgkrnl!DpiUnmapIommuIdentityRange+f770

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.18362.1198

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: f770

FAILURE_BUCKET_ID: 0x7a_c000000e_dxgkrnl!DpiUnmapIommuIdentityRange

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {43330f92-3727-4578-9123-8cb20b5ebd8c}

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

[/CODE]
 
Her önüne geleni yüklememen gerekiyordu.
Temiz format atın tekrar. Sadece GPU sürücülerinizi kurun ve Windows güncellemelerini yapın.
Windows'u da zaten güncel kurmamışsınız. 20H2 indirip kurun.

USB cihazlarınızı da çıkarın.
Diskinizle ilgili de bir sorun olabilir format sonrası HDsentinel sağlık sonucunu paylaşın.
Verdiğiniz değerli bilgiler için teşekkür ederim fakat her önümüze geleni kurmadık zaten myasus yazılımı güncellemeniz var dedi güncelle dedik kendimiz hiçbir şey kurmadık yanlış açıklamam için kusura bakmayın. Windowsu bulabildğimiz son güncellemesiyle kurduk ama tekrar bakacağım. Formatı da en kısa sürede halletmeye çalışacağız.
 
Son düzenleme:
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.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Geri
Yukarı