Ekranda mavi çizgi ve mavi ekran hataları

Umur02

Kilopat
Katılım
5 Temmuz 2015
Mesajlar
17
Daha fazla  
Cinsiyet
Erkek
Merhabalar,dün bilgisayarım tıkır tıkır çalışıyordu üniversitede derste kullanmak için sarj adaptörünü prize taktıktan sonra birbir mavi ekran hataları ve ekranda mavi bir sürü sütünlar halinde mavi çizgiler ortaya çıktı,şuanda da hale o çizgiler var,özellikle görüntünün siyah kısımlarında çıkıyor.Sorun ekran kartında büyük ihtimal ama neden durduk yere hiçbir güncelleme yaptırmazken oldu? Ayrıca mavi ekran hatalarından sonra da operayı açamaz oldum sanırım bad image hatası alıyorum .Ben bilgisayarda tüm Windows güncellemelerini durdurmuştum daha önceden,şuanda tekrar açtım güncellemeleri ve driver booster dan da diğer aygıt güncellemelerini yaptırmaya çalıştım.DMP dosyalarımın linki paylaştımDMP DOSYALARI RAR - Google Drive
 
Aynı hatayı ben de alıyordum 2 gündür sadece opera kullandıktan 15 20 dk sonra oluyordu ya mavi ekran ya da sistem kitleniyordu operayı sildim şuan bi problem yok. Bunu yaşayan 3 - 4 arkadaşım daha var 2 bilgisayarımda da opera hatalara sebep oldu .Bilgisayarlarda son surum windows yuklu butun sürücüler ve yazılımlar guncel.
 
Ekran kartı sürücüsünü güvenli mod da DDU ile eski sürücüyü silip yeni ve en güncel olanını yükleyin, dikkat edin internetiniz kapalı olsun siz yeni sürücüyü kurar iken Windows arka da eski tarihten kalma bir sürücüyü yükler ve sizde sürücüyü yükleyince üst üste sürücü kurmuş olursunuz.


Ayrıca BIOS update edin belki soruna yardımcı olabilir.
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000005, The subtype of the bugcheck:
Arg2: ffffc48572edf000
Arg3: ffffc48572f78620
Arg4: 00000000000001bc

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

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

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

SYSTEM_PRODUCT_NAME:  20217

SYSTEM_SKU:  LENOVO_BI_IDEAPAD 

SYSTEM_VERSION:  Lenovo IdeaPad Y510P

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  74CN44WW(V3.05)

BIOS_DATE:  09/18/2013

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  VIQY0Y1

BASEBOARD_VERSION:  31900004STD

DUMP_TYPE:  2

BUGCHECK_P1: 5

BUGCHECK_P2: ffffc48572edf000

BUGCHECK_P3: ffffc48572f78620

BUGCHECK_P4: 1bc

FAULTING_IP:
nvlddmkm+11c677
fffff802`3836c677 488d8c2490000000 lea     rcx,[rsp+90h]

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  a

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-07-2019 13:40:06.0024

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff802353841a0 to fffff8021d5c1220

STACK_TEXT: 
fffff802`238097a8 fffff802`353841a0 : 00000000`00000119 00000000`00000005 ffffc485`72edf000 ffffc485`72f78620 : nt!KeBugCheckEx
fffff802`238097b0 fffff802`4085f202 : ffffc485`72f8f000 ffffc485`72edf000 00000000`00000010 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff802`238097f0 fffff802`4084d8aa : ffffc485`72ed9000 ffffc485`72edf000 fffff802`23809ab0 fffff802`4084dab3 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x26a
fffff802`23809870 fffff802`4083b421 : ffffc485`000001bc fffff802`23809a29 ffffc485`72ed9000 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1244a
fffff802`238098d0 fffff802`35014aa3 : ffffc485`6fd0a030 fffff802`1d4289fa fffff802`38342524 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff802`23809920 fffff802`3836c677 : ffffc485`6fd0a030 fffff802`23809a29 fffff802`23809ab0 ffffc485`6f887000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff802`23809950 ffffc485`6fd0a030 : fffff802`23809a29 fffff802`23809ab0 ffffc485`6f887000 fffff802`3836c607 : nvlddmkm+0x11c677
fffff802`23809958 fffff802`23809a29 : fffff802`23809ab0 ffffc485`6f887000 fffff802`3836c607 ffffc485`6f887000 : 0xffffc485`6fd0a030
fffff802`23809960 fffff802`23809ab0 : ffffc485`6f887000 fffff802`3836c607 ffffc485`6f887000 00000000`00000000 : 0xfffff802`23809a29
fffff802`23809968 ffffc485`6f887000 : fffff802`3836c607 ffffc485`6f887000 00000000`00000000 00000000`00000000 : 0xfffff802`23809ab0
fffff802`23809970 fffff802`3836c607 : ffffc485`6f887000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffc485`6f887000
fffff802`23809978 ffffc485`6f887000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x11c607
fffff802`23809980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc485`6fd0a030 : 0xffffc485`6f887000


THREAD_SHA1_HASH_MOD_FUNC:  f54730acef609f9d31387d8035ad3630526b7447

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c0224dca694414fad4af82b36f4d5571c3274aaa

THREAD_SHA1_HASH_MOD:  652fb16839a5d49631d78bac2e9893ef3af9b4f7

FOLLOWUP_IP:
nvlddmkm+11c677
fffff802`3836c677 488d8c2490000000 lea     rcx,[rsp+90h]

FAULT_INSTR_CODE:  248c8d48

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  nvlddmkm+11c677

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b5f4c92

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11c677

FAILURE_BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

TARGET_TIME:  2019-12-06T14:23:14.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

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:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  10ab7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x119_5_driver_faulted_system_command_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {55a61c3c-91b1-e527-dcff-f2f0d7348227}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80676f73358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

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

SYSTEM_PRODUCT_NAME:  20217

SYSTEM_SKU:  LENOVO_BI_IDEAPAD 

SYSTEM_VERSION:  Lenovo IdeaPad Y510P

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  74CN44WW(V3.05)

BIOS_DATE:  09/18/2013

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  VIQY0Y1

BASEBOARD_VERSION:  31900004STD

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80676f73358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-07-2019 13:40:10.0060

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80676bee8c1 to fffff80676bc1220

STACK_TEXT: 
fffff806`7be18b08 fffff806`76bee8c1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`76f73358 : nt!KeBugCheckEx
fffff806`7be18b10 fffff806`76a1f857 : 0000008a`78580155 fffff806`731e2180 00000000`00000286 fffff806`7be11530 : nt!KeAccumulateTicks+0x1cbea1
fffff806`7be18b70 fffff806`769601e1 : 00000000`00000000 fffff806`769cbfe0 fffff806`7be115b0 fffff806`769cc090 : nt!KeClockInterruptNotify+0xc07
fffff806`7be18f30 fffff806`76a029e5 : fffff806`769cbfe0 00000000`00000010 ffff9e69`74a11eaa 00000000`00000100 : hal!HalpTimerClockIpiRoutine+0x21
fffff806`7be18f60 fffff806`76bc2cba : fffff806`7be115b0 fffff806`769cbfe0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`7be18fb0 fffff806`76bc3227 : 00000000`00000075 fffff806`76a289fa 00000000`00000001 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`7be11530 fffff806`90b8a3e1 : 00000000`00000000 00000000`00000030 ffff8408`16124000 fffff806`90b95079 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`7be116c0 00000000`00000000 : 00000000`00000030 ffff8408`16124000 fffff806`90b95079 00000000`00002100 : nvlddmkm+0x1ea3e1


THREAD_SHA1_HASH_MOD_FUNC:  bca5d0e2551e8f993bee1fe50bd1f8bafd5f1c55

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1b4438716ac4f8c923fd2461465fe7d4fb469a48

THREAD_SHA1_HASH_MOD:  b6821390c1a7b7750f197edc8d6243a888fe7d24

FOLLOWUP_IP:
nvlddmkm+1ea3e1
fffff806`90b8a3e1 488d83f80d0000  lea     rax,[rbx+0DF8h]

FAULT_INSTR_CODE:  f8838d48

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nvlddmkm+1ea3e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b5f4c92

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1ea3e1

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_nvlddmkm!unknown_function

TARGET_TIME:  2019-12-06T14:32:05.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

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:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  12b5f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000005, The subtype of the bugcheck:
Arg2: ffffd0037d5eb000
Arg3: ffffd0037d687620
Arg4: 0000000000001599

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

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

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

SYSTEM_PRODUCT_NAME:  20217

SYSTEM_SKU:  LENOVO_BI_IDEAPAD 

SYSTEM_VERSION:  Lenovo IdeaPad Y510P

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  74CN44WW(V3.05)

BIOS_DATE:  09/18/2013

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  VIQY0Y1

BASEBOARD_VERSION:  31900004STD

DUMP_TYPE:  2

BUGCHECK_P1: 5

BUGCHECK_P2: ffffd0037d5eb000

BUGCHECK_P3: ffffd0037d687620

BUGCHECK_P4: 1599

FAULTING_IP:
nvlddmkm+11c677
fffff803`7684c677 488d8c2490000000 lea     rcx,[rsp+90h]

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  a

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-07-2019 13:40:15.0109

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff803752241a0 to fffff8035c7c1220

STACK_TEXT: 
fffff803`62e097a8 fffff803`752241a0 : 00000000`00000119 00000000`00000005 ffffd003`7d5eb000 ffffd003`7d687620 : nt!KeBugCheckEx
fffff803`62e097b0 fffff803`7f4df202 : ffffd003`7d680000 ffffd003`7d5eb000 00000000`00000010 fffff803`7690a73c : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff803`62e097f0 fffff803`7f4cd8aa : ffffd003`7d5bb000 ffffd003`7d5eb000 fffff803`62e09ab0 fffff803`7f4cdab3 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x26a
fffff803`62e09870 fffff803`7f4bb421 : ffffd003`00001599 fffff803`62e09a29 ffffd003`7d5bb000 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1244a
fffff803`62e098d0 fffff803`74eb4aa3 : ffffd003`74e78030 fffff803`5a0c5180 fffff803`76822524 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff803`62e09920 fffff803`7684c677 : ffffd003`74e78030 fffff803`62e09a29 fffff803`62e09ab0 ffffd003`74f55000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff803`62e09950 ffffd003`74e78030 : fffff803`62e09a29 fffff803`62e09ab0 ffffd003`74f55000 fffff803`7684c607 : nvlddmkm+0x11c677
fffff803`62e09958 fffff803`62e09a29 : fffff803`62e09ab0 ffffd003`74f55000 fffff803`7684c607 ffffd003`74f55000 : 0xffffd003`74e78030
fffff803`62e09960 fffff803`62e09ab0 : ffffd003`74f55000 fffff803`7684c607 ffffd003`74f55000 00000000`00000000 : 0xfffff803`62e09a29
fffff803`62e09968 ffffd003`74f55000 : fffff803`7684c607 ffffd003`74f55000 00000000`00000000 00000000`00000000 : 0xfffff803`62e09ab0
fffff803`62e09970 fffff803`7684c607 : ffffd003`74f55000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffd003`74f55000
fffff803`62e09978 ffffd003`74f55000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x11c607
fffff803`62e09980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd003`74e78030 : 0xffffd003`74f55000


THREAD_SHA1_HASH_MOD_FUNC:  f54730acef609f9d31387d8035ad3630526b7447

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c0224dca694414fad4af82b36f4d5571c3274aaa

THREAD_SHA1_HASH_MOD:  652fb16839a5d49631d78bac2e9893ef3af9b4f7

FOLLOWUP_IP:
nvlddmkm+11c677
fffff803`7684c677 488d8c2490000000 lea     rcx,[rsp+90h]

FAULT_INSTR_CODE:  248c8d48

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  nvlddmkm+11c677

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b5f4c92

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11c677

FAILURE_BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

TARGET_TIME:  2019-12-06T14:50:43.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

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:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  11bec

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x119_5_driver_faulted_system_command_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {55a61c3c-91b1-e527-dcff-f2f0d7348227}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80784b73358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

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

SYSTEM_PRODUCT_NAME:  20217

SYSTEM_SKU:  LENOVO_BI_IDEAPAD 

SYSTEM_VERSION:  Lenovo IdeaPad Y510P

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  74CN44WW(V3.05)

BIOS_DATE:  09/18/2013

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  VIQY0Y1

BASEBOARD_VERSION:  31900004STD

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80784b73358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-07-2019 13:40:19.0855

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff807847ee8c1 to fffff807847c1220

STACK_TEXT: 
fffff807`87c18b08 fffff807`847ee8c1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`84b73358 : nt!KeBugCheckEx
fffff807`87c18b10 fffff807`8461f857 : 00000101`9012c224 fffff807`7ef6c180 00000000`00000286 fffff807`87c0a220 : nt!KeAccumulateTicks+0x1cbea1
fffff807`87c18b70 fffff807`850b91e1 : 00000000`00000030 fffff807`85124fe0 fffff807`87c0a2a0 fffff807`85125090 : nt!KeClockInterruptNotify+0xc07
fffff807`87c18f30 fffff807`846029e5 : fffff807`85124fe0 00000000`00000000 00000000`00000000 ffff319a`a0830a14 : hal!HalpTimerClockIpiRoutine+0x21
fffff807`87c18f60 fffff807`847c2cba : fffff807`87c0a2a0 fffff807`85124fe0 00000000`00000030 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`87c18fb0 fffff807`847c3227 : ffffffff`ffffffff ffffe782`98fc8000 fffff807`87c0a350 00000000`00000c36 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`87c0a220 fffff807`84633152 : 00000000`00000000 fffff807`9bf954da ffffe782`92c9bdf8 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`87c0a3b0 fffff807`8496f06d : ffffe782`00000200 00000000`00000000 00000000`00000000 00000000`00000018 : nt!ExAllocateHeapPool+0xa92
fffff807`87c0a4f0 fffff807`9be717a3 : 00000000`00000000 00000000`00000018 00000000`00000000 fffff807`00000000 : nt!ExAllocatePoolWithTag+0x5d
fffff807`87c0a540 00000000`00000000 : 00000000`00000018 00000000`00000000 fffff807`00000000 ffffe782`92a97220 : nvlddmkm+0xd17a3


THREAD_SHA1_HASH_MOD_FUNC:  862f6887ac1258206aa4988e7702916ec919e8ac

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0fa7d0b569a0c1fcc1608fb1ef77456f66cbee49

THREAD_SHA1_HASH_MOD:  d0c4326baaecf4e9adb1c8c55d4daee64aa76950

FOLLOWUP_IP:
nvlddmkm+d17a3
fffff807`9be717a3 488bf0          mov     rsi,rax

FAULT_INSTR_CODE:  48f08b48

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  nvlddmkm+d17a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b5f4c92

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d17a3

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_nvlddmkm!unknown_function

TARGET_TIME:  2019-12-06T14:58:50.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

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:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  12918

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
 
Drive Booster 7 den neredeyse tüm aygıtların sürücülerini güncellemiştim ekran kartları (2 tane var,sli) dahil ,şuan bir ekran kartı çalışmıyor ama aygıt yöneticisinde gözüküyor yalnızca sarı ünlem var yanında.Ne yapmalıyım eski bir sürüme dönsem mi eski sürüme dönmek için aygıt yöneticisinde roll back işareti yok, sanırım kendim indirip kurmalıyım?

Ayrıca NVDİA control panelini açmaya çalıştığımda "Nvidia GPU'ya bağlı bir ekran kullanmıyorsunuz" hatası alıyorum halbuki bilgisayarım da intel ekran kartı yok ikiside Nvdia gt755m
 
Son düzenleme:
Emin misin yardımın olmadığına bak yarın olur da sen olmazsın.

Tamamdır arkadaşlar 2. ekran kartı da çıktı ortaya şöyle anladım ki sanırım ben Driver Booster kullandığım için ekran kartlarını NVIDIA GPU diye algılamadı bilgisayar bu yüzden Control panel a giremedim. En son GeForce'tan re-install yaptım aynı sürümü, bu kez 2. ekran kartı da çalıştı.
Teşekkürler yardımını esirgemeyenlere.
Ama bir şey sormak istiyorum neden durup dururken böyle bir şey yaşadım? Hiçbir güncelleme almıyordum, ben şöyle düşünüyordum bilgisayarımın şu anki performansından memnunum o zaman neden güncelleme alayım ki?
Arkadaşlar gene aynı sorun çıktı ortaya.Bilgisayar birden dondu ve uzun süre gelmedi bende power düğmesine basılı tutup kapatmak zorunda kaldım açtığımda tekrardan dik mavi çizgiler karşıma çıktı ,aynı zamanda gpu driver'lar en son güncel sürümde olmasına rağmen aygıt yöneticisinin yanında sarı ünlemler vardı şuan ekran kartlarının ikisinide kullanmıyor sanırsam ,nvdia kontrol paneli filan hala çalışmıyor malesef.
Edit:
Bilgisayarı bir kaç açıp kapamadan sonra mavi çizgiler kendiliğinden gitmiş durumda ancak hala sarı ünlemler devam ediyor ve nvdia kontrol paneli kullanılamıyor
Sürücü bulucu kullananlara yardımım yoktur. BIOS konusunda sadece yardımım olacak.
BIOS güncel değil güncelleyin.
Arkadaşım merhaba BIOS 'u güncellemek istiyorum Lenovo'nun sitesinden baktım:(Sistem BIOS'u nasıl güncellenir - US)
Ben SystemUpdate uygulamasını kurdum fakat yeni bir güncelleme bulamadı,kendi bilgisayarım için son sürüm bios'u nasıl bulabilirim? Sizin attığınız linkin benim bilgisayarım için uygun olduğunu nasıl anlarım?
kendi Lenovo Y510p sistem aygıtlarım için link:laptops and netbooks :: ideapad y series laptops :: ideapad y510p notebook :: 6494 :: 59407130 :: yb01554832 - TR
Arkadaşlar DDU ile en güncel ekran kartı sürücülerini güncelledim, mavi dikey stunlar devam ediyor ve control panel açmaya çalıştığımda "şu anda nvidia gpu'ya bağlı bir ekran kullanmıyorsunuz" hatası alıyorum başka bir forumdan bi arkadaş şöyle çözmüş
(
"Bende bios ayarlarına girdim.
Grafik ayarlarında yer alan graphic bölümünü switchable olarak ön ayarlı olmasına rağman önce integral olarak değiştirip f10 ile kaydedip pcyi açtım.
Sonrasında yeniden başlatıp bios ayarlarından tekrar switchable olarak değiştirip başlattım ve grafik kartı şuanda çalışıyor."
)
acaba bende de işe yarar mı?
 
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.

Geri
Yukarı