Ekran Kartı Sürücüsünü Yükledikten Sonra Sonsuz Mavi Ekran

Dempsey

Hectopat
Katılım
28 Ocak 2019
Mesajlar
65
Bir süredir çözmeye çalışıyorum ama bir türlü çözüme ulaşamadım. Geçen aylarda durduk yere başıma geldi bu problem de AMD Raedon Driver'ını sildikten sonra düzeldi. Farklı sürümleri, bayağı eski olanları da denedim ama bir türlü çözemedim. Farklı Windows 10 ve 8.1 sürümleri de denedim, yine çözemedim. Umarım donanımsal değildir. Minidump bırakıyorum. Lenovo'nun sitesindeki son BIOS'u da kurdum ayrıca. Farklı sitelerdeki neredeyse tüm çözümleri denedim ama AMD Driver'ı kurulurken yüzde 90 mavi ekran veriyor. Vermees bile Raedon ayarlarını açtığımda veriyor ve güvenli modda ekran kartını silene kadar PC açılmıyor. Laptop modelim Lenovo G50-80.

minidump: minidump.rar
 
Son düzenleyen: Moderatör:
Maalesef donanımsal. Garantisi varsa servise gönderin. Yoksa AMD GPU'nun Reballing ile değişmesi gerekebilir.
Kod:
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffff9687c3c574c0, 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 "intercepted" bugcheck 0xEA was hit (see notes).

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:  17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  80L0

SYSTEM_SKU:  LENOVO_MT_80L0_BU_idea_FM_Lenovo G50-80

SYSTEM_VERSION:  Lenovo G50-80

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  B0CNA0WW

BIOS_DATE:  09/30/2016

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  Lenovo G50-80

BASEBOARD_VERSION:  31900059 WIN

DUMP_TYPE:  2

BUGCHECK_P1: ffff9687c3c574c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff9687c3c574c0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: 768

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 23'00000000 (cache) 23'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-K01TCKK

ANALYSIS_SESSION_TIME:  03-11-2019 14:13:33.0153

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8031866a790 to fffff80570654440

STACK_TEXT: 
ffffed0c`1cf642f8 fffff803`1866a790 : 00000000`000000ea ffff9687`c3c574c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffed0c`1cf64300 fffff803`1866a86a : ffffed0c`1cf643d8 fffff803`1d4db5dc ffffed0c`1cf643d8 fffff803`1d4edccd : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
ffffed0c`1cf64370 fffff803`1d4edcc0 : ffff9687`c2795000 00000000`00000000 ffff9687`c2795000 fffff803`1d4db5b0 : dxgkrnl!TdrTimedOperationDelay+0xca
ffffed0c`1cf643b0 ffff9687`c2795000 : 00000000`00000000 ffff9687`c2795000 fffff803`1d4db5b0 00000000`01c9c380 : atikmdag+0x4dcc0
ffffed0c`1cf643b8 00000000`00000000 : ffff9687`c2795000 fffff803`1d4db5b0 00000000`01c9c380 00000002`00000028 : 0xffff9687`c2795000


STACK_COMMAND:  .thread 0xffff9687c3c574c0 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1b6e0a437c60d2c16d9ebaaae9cc861a6e13529c

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
fffff803`1866a790 0f1f440000      nop     dword ptr [rax+rax]

FAULT_INSTR_CODE:  441f0f

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.17763.194

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2019-03-10T16:46:30.000Z

OSBUILD:  17763

OSSERVICEPACK:  316

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:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  12de5

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

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

Followup:     MachineOwner
---------
 
Maalesef donanımsal. Garantisi varsa servise gönderin. Yoksa AMD GPU'nun Reballing ile değişmesi gerekebilir.
Kod:
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffff9687c3c574c0, 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 "intercepted" bugcheck 0xEA was hit (see notes).

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:  17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  80L0

SYSTEM_SKU:  LENOVO_MT_80L0_BU_idea_FM_Lenovo G50-80

SYSTEM_VERSION:  Lenovo G50-80

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  B0CNA0WW

BIOS_DATE:  09/30/2016

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  Lenovo G50-80

BASEBOARD_VERSION:  31900059 WIN

DUMP_TYPE:  2

BUGCHECK_P1: ffff9687c3c574c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff9687c3c574c0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: 768

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 23'00000000 (cache) 23'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-K01TCKK

ANALYSIS_SESSION_TIME:  03-11-2019 14:13:33.0153

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8031866a790 to fffff80570654440

STACK_TEXT:
ffffed0c`1cf642f8 fffff803`1866a790 : 00000000`000000ea ffff9687`c3c574c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffed0c`1cf64300 fffff803`1866a86a : ffffed0c`1cf643d8 fffff803`1d4db5dc ffffed0c`1cf643d8 fffff803`1d4edccd : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
ffffed0c`1cf64370 fffff803`1d4edcc0 : ffff9687`c2795000 00000000`00000000 ffff9687`c2795000 fffff803`1d4db5b0 : dxgkrnl!TdrTimedOperationDelay+0xca
ffffed0c`1cf643b0 ffff9687`c2795000 : 00000000`00000000 ffff9687`c2795000 fffff803`1d4db5b0 00000000`01c9c380 : atikmdag+0x4dcc0
ffffed0c`1cf643b8 00000000`00000000 : ffff9687`c2795000 fffff803`1d4db5b0 00000000`01c9c380 00000002`00000028 : 0xffff9687`c2795000


STACK_COMMAND:  .thread 0xffff9687c3c574c0 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1b6e0a437c60d2c16d9ebaaae9cc861a6e13529c

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
fffff803`1866a790 0f1f440000      nop     dword ptr [rax+rax]

FAULT_INSTR_CODE:  441f0f

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.17763.194

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2019-03-10T16:46:30.000Z

OSBUILD:  17763

OSSERVICEPACK:  316

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:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  12de5

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

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

Followup:     MachineOwner
---------
Cevap için teşekkürler. Garantisi yok ne yazık ki. Yeni bir alet alana kadar Intel hd graphics ile idare edeceğim sanırım.
 
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.

Yeni konular

Geri
Yukarı