Windows 10 Mavi Ekran hatası

canonsay

Centipat
Katılım
11 Mart 2020
Mesajlar
5
4 Ay önce mavi ekran hatası almaya başladım. Formatlayıp tekrar Windows 10 kurdum. Yaklaşık 1 ay hiç mavi ekran hatası almadım ama sonra tekrar başladı. En çok hatayı League of Legends'ı açarken alıyorum. Custom Game girip 2 dakika oynadıktan sonra mavi ekran hatası almazsam bilgisayarı kapatana kadar bir daha mavi ekran hatası almıyorum. Mavi ekran hatası almadığım duruma gelene kadar en az 3-4 kere mavi ekran hatası alıyorum. RAM'leri memtest ile test ettim sorun bulamadı, tek tek takıp denedim hata almaya devam ettim.
Arka arkaya mavi ekran hataları aldıktan sonra bazen Windows 8 GB olan RAM'in sadece 4 GB'ını kullanıyor. Bu durumda da hiç mavi ekran hatası almıyorum. Son hataların minidump dosyalarını yükledim.
 
Son düzenleyen: Moderatör:
AMD OverDrive yazılımını kaldır.
BIOS'a gir Exit bölümünden Load Defaults yap kaydet çık.

Çalışan bir bellek ile tüm yuvaların sorunsuz olup olmadığını kontrol et.

Ve bellekleri bu şekilde takılı değilse bu şekilde tak;
s1.png


Bu bilgisayarda sürücü bulucu falan mı çalıştı?

HD Tune programı ile sisteme takılı tüm depolama birimlerinin Error Scan ve Health sonuçlarını fotoğraf şeklinde paylaş.

Error Scan testinde Quick Scan yapma.

DDU ile ekran kartı sürücüsünü kaldır tekrar yükle.
Kod:
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffc604b07d5880, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


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

BUGCHECK_P2: 1232

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffffc604b07d5880

FOLLOWUP_IP:
nt!KeUpdateThreadTag+1c7
fffff806`1af3ff77 cf              iretd

CPU_COUNT: 8

CPU_MHZ: dbc

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  Discord.exe

CURRENT_IRQL:  0

DEVICE_OBJECT: 0000000000000000

ANALYSIS_SESSION_HOST:  DESKTOP-BKJR0DQ

ANALYSIS_SESSION_TIME:  03-12-2020 00:43:10.0095

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8061b066cd3 to fffff8061afc2380

STACK_TEXT:
ffff8384`2e87d658 fffff806`1b066cd3 : 00000000`00000044 ffffc604`b07d5880 00000000`00001232 00000000`00000000 : nt!KeBugCheckEx
ffff8384`2e87d660 fffff806`1af3ff77 : 00000000`00000001 00000000`00000002 ffffc604`b1a47200 ffffc604`b0be3ee8 : nt!IopfCompleteRequest+0x146d43
ffff8384`2e87d770 fffff806`1af0a939 : ffffc604`b0be3dd0 ffffc604`a8b21180 00000000`00000001 ffff9900`841da180 : nt!KeUpdateThreadTag+0x1c7
ffff8384`2e87d8b0 fffff806`1b4b2bd5 : ffffc604`b0be3dd0 00000000`00000000 ffffc604`b0be3dd0 fffff806`1b436a71 : nt!IofCallDriver+0x59
ffff8384`2e87d8f0 fffff806`1b4367d6 : ffff8701`00000000 ffffc604`a8568910 ffffc604`b1a47200 ffff8384`2e87db80 : nt!IopSynchronousServiceTail+0x1a5
ffff8384`2e87d990 fffff806`1afd3c18 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`0c7d8dd0 : nt!NtWriteFile+0x676
ffff8384`2e87da90 00000000`77371cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`1229ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77371cbc


THREAD_SHA1_HASH_MOD_FUNC:  03f65ca5d16b5e6cff17f3f1721fd77ae6a595bb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  4a2513fc796c63bb700919455d91040062fe9b13

THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6

FAULT_INSTR_CODE:  448948cf

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KeUpdateThreadTag+1c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.719

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c7

FAILURE_BUCKET_ID:  0x44_nt!KeUpdateThreadTag

BUCKET_ID:  0x44_nt!KeUpdateThreadTag

PRIMARY_PROBLEM_CLASS:  0x44_nt!KeUpdateThreadTag

TARGET_TIME:  2020-03-11T18:38:02.000Z

OSBUILD:  18362

OSSERVICEPACK:  719

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

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x44_nt!keupdatethreadtag

FAILURE_ID_HASH:  {23673408-669a-1309-179f-33e30b03d859}

Followup:     MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80411c45b97, Address of the instruction which caused the bugcheck
Arg3: ffff8c8e1b7e6cc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80411c45b97

BUGCHECK_P3: ffff8c8e1b7e6cc0

BUGCHECK_P4: 0

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

FAULTING_IP:
+0
fffff804`11c45b97 ??              ???

CONTEXT:  ffff8c8e1b7e6cc0 -- (.cxr 0xffff8c8e1b7e6cc0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000
00000000`00000000 ??              ???
Resetting default scope

BUGCHECK_STR:  0x3B_c0000005

CPU_COUNT: 8

CPU_MHZ: dbc

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-BKJR0DQ

ANALYSIS_SESSION_TIME:  03-12-2020 00:41:21.0003

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80411dc1510

STACK_TEXT:
ffff8c8e`1b7e6388 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff804`11dc1510


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID:  CORRUPT_MODULELIST_0x3B_c0000005

DEFAULT_BUCKET_ID:  CORRUPT_MODULELIST_0x3B_c0000005

PRIMARY_PROBLEM_CLASS:  CORRUPT_MODULELIST_0x3B_c0000005

FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_0x3B_c0000005

TARGET_TIME:  2020-03-10T11:37:16.000Z

OSBUILD:  18362

OSSERVICEPACK:  0

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

ANALYSIS_SESSION_ELAPSED_TIME:  26

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:corrupt_modulelist_0x3b_c0000005

FAILURE_ID_HASH:  {74bb4c27-742f-ebb4-fa0a-8074317b8a14}

Followup:     MachineOwner
---------
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000046, Attempt to free an invalid pool address
Arg2: ffffd18400000000, Starting address
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

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


KEY_VALUES_STRING: 1


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

BUGCHECK_P2: ffffd18400000000

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_IP:
nt!IopfCompleteRequest+b23
fffff806`2a2481e3 4533ff          xor     r15d,r15d

BUGCHECK_STR:  0xc2_46

CPU_COUNT: 8

CPU_MHZ: dbc

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-BKJR0DQ

ANALYSIS_SESSION_TIME:  03-12-2020 00:41:15.0846

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8062a51ad63 to fffff8062a3c1510

STACK_TEXT:
ffffd184`c34f3e38 fffff806`2a51ad63 : 00000000`000000c2 00000000`00000046 ffffd184`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd184`c34f3e40 fffff806`2a51add8 : 00000000`00000016 ffffd184`c34f4179 ffffd184`00000000 fffff806`2a66e158 : nt!RtlpHeapHandleError+0x2b
ffffd184`c34f3e80 fffff806`2a51aa01 : ffffd184`c34f3f50 fffff806`2a66e158 00000000`00000000 00000005`18400100 : nt!RtlpHpHeapHandleError+0x58
ffffd184`c34f3eb0 fffff806`2a2ea7b7 : ffffd184`c34f3f50 fffff806`2a239ddd ffff8008`6e94b080 ffffdd80`8b3ba848 : nt!RtlpLogHeapFailure+0x45
ffffd184`c34f3ee0 fffff806`2a2ea730 : ffffd184`c34f4010 ffffd184`c34f40b0 00000000`00000000 ffff8008`7529a680 : nt!RtlpHpVaMgrCtxQuery+0x4b
ffffd184`c34f3f20 fffff806`2a246389 : ffff8008`77f494e0 ffffd184`00000000 a2e64ead`a2e64ead fffff806`2bf1bb22 : nt!RtlpHpQueryVA+0x54
ffffd184`c34f3f80 fffff806`2a56f0a9 : ffffdd80`97edecb0 ffff8008`00000001 fffff806`2ef10030 fffff806`2bee3c9d : nt!ExFreeHeapPool+0x809
ffffd184`c34f40a0 fffff806`2a2481e3 : ffffdd80`8b3ba800 fffff806`00000000 ffff8008`70b18010 00000000`00000000 : nt!ExFreePool+0x9
ffffd184`c34f40d0 fffff806`2a2476a7 : ffffd184`c34f4310 ffffffff`ffffff01 ffff8008`70b18010 00000000`00000103 : nt!IopfCompleteRequest+0xb23
ffffd184`c34f41e0 fffff806`2bee580a : ffff8008`784ac9e0 ffff8008`6e959240 00000000`00000008 ffff8008`784ac9e0 : nt!IofCompleteRequest+0x17
ffffd184`c34f4210 fffff806`2bf1cd27 : ffffd184`c34f42d0 fffff806`00000000 00000020`00000000 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x38a
ffffd184`c34f4290 fffff806`2a231f79 : ffff8008`7750ca00 fffff806`2a7e5d45 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x307
ffffd184`c34f4340 fffff806`2a231024 : 00000000`00000000 00000000`00000000 ffff8008`77f49910 fffff806`2a29d81e : nt!IofCallDriver+0x59
ffffd184`c34f4380 fffff806`2a7e638b : ffffd184`c34f4640 fffff806`2a7e5d45 ffffd184`c34f45b0 ffffd184`c34f4890 : nt!IoCallDriverWithTracing+0x34
ffffd184`c34f43d0 fffff806`2a7ed35f : ffff8008`708ef8f0 ffff8008`708ef845 ffff8008`77271010 00000000`00000001 : nt!IopParseDevice+0x62b
ffffd184`c34f4540 fffff806`2a7eb7c1 : ffff8008`77271000 ffffd184`c34f4788 00000000`00000040 ffff8008`6e8f8560 : nt!ObpLookupObjectName+0x78f
ffffd184`c34f4700 fffff806`2a8b13f6 : ffffd184`00000001 000000fa`52e7dfb0 00000000`00008001 000000fa`52e7e3c0 : nt!ObOpenObjectByNameEx+0x201
ffffd184`c34f4840 fffff806`2a3d2e18 : 00000285`02a7cdda ffffd184`c34f4b80 ffff8008`6e94b080 000000fa`52e7e3c0 : nt!NtQueryAttributesFile+0x1e6
ffffd184`c34f4b00 00007ff8`7bb3c864 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000fa`52e7df48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`7bb3c864


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8062a7e5dc2 - nt!IopParseDevice+62
    [ 89:8b ]
1 error : !nt (fffff8062a7e5dc2)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME:  2020-03-10T12:31:26.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

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:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  2291

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     memory_corruption
---------

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000012, Type of corruption detected
Arg2: ffffc98b11e02100, Address of the heap that reported the corruption
Arg3: ffffc98b1ccfd000, Address at which the corruption was detected
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


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

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

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

BIOS_DATE:  08/06/2013

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  970A-UD3P

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 12

BUGCHECK_P2: ffffc98b11e02100

BUGCHECK_P3: ffffc98b1ccfd000

BUGCHECK_P4: 0

CORRUPTING_POOL_ADDRESS: fffff802677733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffc98b1ccfd000

FAULTING_IP:
nt!ExAllocatePoolWithTag+5d
fffff802`6756f06d 4885c0          test    rax,rax

BUGCHECK_STR:  0x13a_12

CPU_COUNT: 8

CPU_MHZ: dbc

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-BKJR0DQ

ANALYSIS_SESSION_TIME:  03-12-2020 00:41:12.0060

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8026751ad78 to fffff802673c1510

STACK_TEXT:
ffff9780`88b53b28 fffff802`6751ad78 : 00000000`0000013a 00000000`00000012 ffffc98b`11e02100 ffffc98b`1ccfd000 : nt!KeBugCheckEx
ffff9780`88b53b30 fffff802`6751add8 : 00000000`00000012 00000000`016b0000 ffffc98b`11e02100 ffffc98b`18285118 : nt!RtlpHeapHandleError+0x40
ffff9780`88b53b70 fffff802`6751aa01 : ffffc98b`11e02280 00000000`00000000 ffffc98b`180ef460 ffffc98b`180ef460 : nt!RtlpHpHeapHandleError+0x58
ffff9780`88b53ba0 fffff802`67242d3d : 00000000`00000000 00000000`00000000 00000000`000000c0 fffff802`67239a69 : nt!RtlpLogHeapFailure+0x45
ffff9780`88b53bd0 fffff802`67232b18 : ffffc98b`0000016b fffff802`00001690 ffffc98b`00001690 ffffc98b`11e02000 : nt!RtlpHpVsContextAllocateInternal+0x38d
ffff9780`88b53c40 fffff802`6756f06d : 00000000`00000200 00000000`00000000 00000000`00000000 00000000`00001688 : nt!ExAllocateHeapPool+0x418
ffff9780`88b53d80 fffff802`6be0c915 : ffffc98b`183b6c40 ffff9780`88b54b80 ffff9780`88b54900 00000000`00000000 : nt!ExAllocatePoolWithTag+0x5d
ffff9780`88b53dd0 fffff802`6bf0b177 : fffff802`67cbae70 fffff802`67cb7848 00000000`00000000 fffff802`6723a5a7 : dxgkrnl!operator new+0x31
ffff9780`88b53e00 fffff802`6bf0ad77 : ffffdf8e`20102de0 ffff9780`88b54900 ffff9780`88b54900 ffffdf8e`20102de0 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x247
ffff9780`88b545d0 fffff802`6bf0b54a : 00000000`00000020 fffff802`6bf2def4 ffffdf8e`1f62d210 0000000b`e94fcdf0 : dxgkrnl!DxgkSubmitCommandInternal+0x557
ffff9780`88b54ac0 fffff802`673d2e18 : ffffc98b`18bd9080 00000000`00000000 ffffc98b`124a8600 00000000`40000000 : dxgkrnl!DxgkSubmitCommand+0x5a
ffff9780`88b54b00 00007fff`65f15a44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000000b`e94fcd28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`65f15a44


THREAD_SHA1_HASH_MOD_FUNC:  667e850afb8df204ce86540608a121afd2c8e9d6

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  f730e5cd349f4cf9bad98d2b83c3be51013043dc

THREAD_SHA1_HASH_MOD:  6e63506211a7a887b05383b5f9eb13e5982898ba

FOLLOWUP_IP:
dxgkrnl!operator new+31
fffff802`6be0c915 4883c428        add     rsp,28h

FAULT_INSTR_CODE:  28c48348

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgkrnl!operator new+31

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4305f7c

IMAGE_VERSION:  10.0.18362.657

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  31

FAILURE_BUCKET_ID:  0x13a_12_dxgkrnl!operator_new

BUCKET_ID:  0x13a_12_dxgkrnl!operator_new

PRIMARY_PROBLEM_CLASS:  0x13a_12_dxgkrnl!operator_new

TARGET_TIME:  2020-03-09T20:41:27.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

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:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  c38e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x13a_12_dxgkrnl!operator_new

FAILURE_ID_HASH:  {b349f4a5-651b-df82-c082-6e3e19db583f}

Followup:     MachineOwner
---------
 
@MayCrasH
Bilgisayarımda AMD OverDrive yüklü değil.

Daha önceden BIOS ayarlarımı sıfırlamıştım. Garanti olsun diye tekrar sıfırladım.

Elimdeki 2 belleği, 4 yuvada tek tek denedim bütün yuvalar çalışıyor. Bellekler de çalışıyor. Bellekler şemada gösterildiği gibi takılı. (DDR3_2 ile DDR3_1)

Sorunun sürücülerle alakalı olabileceğini düşünüp sürücü bulucu bir program indirmiştim. USB sürücüsü güncellemesi dışında birşey bulamadı.

HD Tune testlerinin sonuçlarını ekledim.
SSD:
hdtunehealthSSD.jpg
hdtuneerrorscanSSD.jpg



HDD:
hdtunehealthHDD.jpg

hdtuneerrorscanHDD.jpg



DDU ile ekran kartı sürücüsünü kaldırıp tekrar yükledim.

Bunları yaparken bilgisayar şu anda mavi ekran vermeyen durumda olduğu için(ilk mesajda açıklamıştım) hiç mavi ekran yemedim. Hata aldığımda yeni minidump dosyalarını buraya ekleyeceğim.
 
Geçmişte ekran kartını değiştiğimde pc yük altına girince mavi ekran hatası almaya başlamıştım, testler yapınca psu yetersiz kalmış. Psu değişince sorun ortadan kalkmıştı. Sizinki farklı bir durum da olabilir.
Sisteminizi de yazsaydınız keşke.
Mavi ekranda hata kodu nedir?
Donanımlarınızda kir birikintisi veya soğutmayı önleyecek bir durum var mı?
 
BIOS sürümümü f1'den f2g'ye yükselttim.

5 senedir aynı sistemi kullanıyorum. Arızalanmadıysa PSU'nun yetersiz olması gibi bir durum söz konusu değil. Donanımları yeni temizledim. Mavi ekran hatalarını %90 bilgisayarı yeni açmışken alıyorum. Sıcaklıklar kritik seviyelere hiç yükselmiyor.

Minidump dosyaları, yasaklı siteye yüklediğim için kaldırılmış. Minidumps.rar

Sistem Bilgileri;
Windows 10 Pro
Anakart: Gigabyte 970a-UD3P
İşlemci: AMD FX-8320
Ekran Kartı: Sapphire R9-270X
Ram: 2X4GB G.Skill 1866mhz ddr3
HDD: WD Caviar Blue 1 TB
SSD: WD 240GB
PSU: Cooler Master 600W
İşlemci Soğutucu: Cooler Master Blizzard T2 Mini
 
Yazılımsal bir problem de olabilir, donanım arızası da olabilir.
Mavi ekran hata kodunu bulmak için BlueScreenView yükleyip taratabilirsin. Sonrasında hata kodunu da paylaşırsan bir sonuç elde edebiliriz.
 
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.

Yeni konular

Geri
Yukarı