Mavi ekran hatası Ve MiniDump Dosyası

Mertkarasu

Hectopat
Katılım
24 Kasım 2015
Mesajlar
57
Çözümler
2
Yer
İzmir
Daha fazla  
Cinsiyet
Erkek
Selam arkadaşlar mavi ekran hatası alıyorum.
Fakat sebebini bilmiyorum.
Sizlerle minidump dosyamı paylaşmak istiyorum.
Ben minidump dosyaları nasıl okunur bilmiyorum.
Bilen var ise şimdiden yardımı için teşekkürler.
 
AMD GPU güncelle. Ayrıca sistemdeki ekran kartı nedir? Sanırım eski bir model ve problem olabilir.

Kod:
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffffbb8830eef040, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times this error occurred.  If a debugger is attached,
    this error is not always fatal -- see DESCRIPTION below.  On the
    blue screen, this will always equal 1.

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:  10.0.18362.720 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B28

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  3.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  H.80

BIOS_DATE:  12/26/2019

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  H310M GAMING ARCTIC (MS-7B28)

BASEBOARD_VERSION:  3.0

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: ffffbb8830eef040

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffffbb8830eef040

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: b

CPU_MICROCODE: 6,9e,b,0 (F,M,S,R)  SIG: CA'00000000 (cache) CA'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-LN3VJKJ

ANALYSIS_SESSION_TIME:  03-20-2020 13:12:40.0720

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8015da91085 to fffff801477c2380

STACK_TEXT:  
ffff810d`dda47268 fffff801`5da91085 : 00000000`000000ea ffffbb88`30eef040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff810d`dda47270 fffff801`5da9115e : ffff810d`dda47340 fffff801`4636e707 ffff810d`dda47340 00000000`80000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff810d`dda472e0 fffff801`46140532 : 00000000`00000000 fffff801`4636e6ec ffff810d`dda47460 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff810d`dda47320 00000000`00000000 : fffff801`4636e6ec ffff810d`dda47460 00000000`01c9c380 ffff810d`00000028 : atikmdag+0x30532


STACK_COMMAND:  .thread 0xffffbb8830eef040 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  970f0ef9c97f446d12c903a38e909099ef41a717

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff801`5da91085 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.719

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2020-03-20T05:18:58.000Z

OSBUILD:  18362

OSSERVICEPACK:  720

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.720

ANALYSIS_SESSION_ELAPSED_TIME:  28fd

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

Followup:     MachineOwner
---------
 
AMD GPU güncelle. Ayrıca sistemdeki ekran kartı nedir? Sanırım eski bir model ve problem olabilir.

Kod:
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffffbb8830eef040, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times this error occurred.  If a debugger is attached,
    this error is not always fatal -- see DESCRIPTION below.  On the
    blue screen, this will always equal 1.

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:  10.0.18362.720 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B28

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  3.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  H.80

BIOS_DATE:  12/26/2019

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  H310M GAMING ARCTIC (MS-7B28)

BASEBOARD_VERSION:  3.0

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: ffffbb8830eef040

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffffbb8830eef040

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: b

CPU_MICROCODE: 6,9e,b,0 (F,M,S,R)  SIG: CA'00000000 (cache) CA'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-LN3VJKJ

ANALYSIS_SESSION_TIME:  03-20-2020 13:12:40.0720

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8015da91085 to fffff801477c2380

STACK_TEXT: 
ffff810d`dda47268 fffff801`5da91085 : 00000000`000000ea ffffbb88`30eef040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff810d`dda47270 fffff801`5da9115e : ffff810d`dda47340 fffff801`4636e707 ffff810d`dda47340 00000000`80000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff810d`dda472e0 fffff801`46140532 : 00000000`00000000 fffff801`4636e6ec ffff810d`dda47460 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff810d`dda47320 00000000`00000000 : fffff801`4636e6ec ffff810d`dda47460 00000000`01c9c380 ffff810d`00000028 : atikmdag+0x30532


STACK_COMMAND:  .thread 0xffffbb8830eef040 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  970f0ef9c97f446d12c903a38e909099ef41a717

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff801`5da91085 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.719

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2020-03-20T05:18:58.000Z

OSBUILD:  18362

OSSERVICEPACK:  720

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.720

ANALYSIS_SESSION_ELAPSED_TIME:  28fd

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

Followup:     MachineOwner
---------
Evet ekran kartım baya eski idareten bir kart kullanıyorum. Kartın adı ati radeon x1050 windows 10 driver'ı bile yok internetten buldum windows 10 portable driver'ını. Sanırım ondan kaynaklanıyor. Driver'ı yüklemem gerekiyordu. Çünkü monitör gelen görüntü 1080p desteklemiyordu. O yüzden .inf dosyası olarak yükledim aygıt yöneticisi üzerinden. Sanırım o yüzden alıdım mavi ekran hatası çok teşekkür ederim.
 
Uyarı! Bu konu 6 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ı