Windows 10 notebook NVIDIA driver sorunu

meteorengin2006

Femtopat
Katılım
29 Eylül 2020
Mesajlar
5
Her yeni gelen Windows 10 güncellemesi ile bilgisayarlarımda problemler yaşıyorum. ASUS Vivobook marka laptopumu yeni aldım. Windows 10 güncellemelerini yaptım. İçinden çıkan Windows sürümünde normal olarak çalışan NVIDIA GeForce MX250 ekran kartı driverımda güncellemeden sonra ünlem görünmeye başladı. Daha sonra NVIDIA'nın sitesinden en güncel driverı indirdim ve resimdeki hata ile karşılaşıyorum. Daha sonra ekran kartını tamamen kaldır dedim ve yine olmadı. Bilgisayarı yeniden başlattığımda mavi ekran hatası alıyorum ve Windows açılmıyor. Onarma seçenekleri bile işe yaramıyor ve bilgisayar ne yaptıysam açılmıyor. Ayrıca NVIDIA Control paneli de tıkladağımda açılmıyor. Bilgisayara format atmak zorunda kaldım. Notebookumda harici ekran kartını kullanamamak çok sinir bozucu bir durum. Sorunun kaynağını bilen bir arkadaş yardımcı olursa çok müteşekkir olurum. Yardımlarınız için çok teşekkürler.
Not: Windows 10 versiyonum sürüm 2004.

1.JPG
2.JPG
3.JPG
4.JPG
 
Son düzenleyen: Moderatör:
Ekran kartı bozuk olabilir. DDU ile kaldırıp tekrar yüklemeyi deneyin. Dump dosyaları varsa paylaşır mısınız?
 
Ekran kartı bozuk olabilir. DDU ile kaldırıp tekrar yüklemeyi deneyin. Dump dosyaları varsa paylaşır mısınız?
dump dosyasını nasıl bulabilirim ?
 
 
Intel'in kablosuz Bluetooth sürücüsünü güncelleyiniz.
Kod:
Intel® Dual Band Wireless-AC 3165
Intel® Dual Band Wireless-AC 3168
Intel® Dual Band Wireless-AC 7265
Intel® Dual Band Wireless-AC 8260
Intel® Dual Band Wireless-AC 8265
Intel® Dual Band Wireless-AC 8265 Desktop Kit
Intel® Dual Band Wireless-N 7265
Intel® PROSet/Wireless Software
Intel® Tri-Band Wireless-AC 17265
Intel® Tri-Band Wireless-AC 18260
Intel® Tri-Band Wireless-AC 18265
Intel® Wireless-N 7265
Soruna ekran kartı sebep oluyor DDU işlemini yapıp sürücüyü kurun. Bellek testide yapınız.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8038ea9e0bd, The address that the exception occurred at
Arg3: ffffd486edce69c8, Exception Record Address
Arg4: ffffd486edce6200, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nvlddmkm+34e0bd
fffff803`8ea9e0bd 488b4238        mov     rax,qword ptr [rdx+38h]

EXCEPTION_RECORD:  ffffd486edce69c8 -- (.exr 0xffffd486edce69c8)
ExceptionAddress: fffff8038ea9e0bd (nvlddmkm+0x000000000034e0bd)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038

CONTEXT:  ffffd486edce6200 -- (.cxr 0xffffd486edce6200;r)
rax=ffffe604856e9010 rbx=ffffd486edce6c70 rcx=ffffe6047c2aa890
rdx=0000000000000000 rsi=ffffe6048188e000 rdi=ffffd486edce6c78
rip=fffff8038ea9e0bd rsp=ffffd486edce6c00 rbp=ffffe60488249000
 r8=ffffd486edce6c78  r9=ffffd486edce6c70 r10=fffff8038effe6f0
r11=0000000000000006 r12=000000000000002c r13=0000000000000000
r14=ffffe60485bada38 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x34e0bd:
fffff803`8ea9e0bd 488b4238        mov     rax,qword ptr [rdx+38h] ds:002b:00000000`00000038=????????????????
Last set context:
rax=ffffe604856e9010 rbx=ffffd486edce6c70 rcx=ffffe6047c2aa890
rdx=0000000000000000 rsi=ffffe6048188e000 rdi=ffffd486edce6c78
rip=fffff8038ea9e0bd rsp=ffffd486edce6c00 rbp=ffffe60488249000
 r8=ffffd486edce6c78  r9=ffffd486edce6c70 r10=fffff8038effe6f0
r11=0000000000000006 r12=000000000000002c r13=0000000000000000
r14=ffffe60485bada38 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x34e0bd:
fffff803`8ea9e0bd 488b4238        mov     rax,qword ptr [rdx+38h] ds:002b:00000000`00000038=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000038

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000038

FOLLOWUP_IP:
nvlddmkm+34e0bd
fffff803`8ea9e0bd 488b4238        mov     rax,qword ptr [rdx+38h]

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from b0940a0000000000 to fffff8038ea9e0bd

STACK_TEXT: 
ffffd486`edce6c00 b0940a00`00000000 : fffff803`8ec56e8f fffff803`8effe798 fffff803`8f065ea8 ffffe604`8188e000 : nvlddmkm+0x34e0bd
ffffd486`edce6c08 fffff803`8ec56e8f : fffff803`8effe798 fffff803`8f065ea8 ffffe604`8188e000 fffff803`8edae2e4 : 0xb0940a00`00000000
ffffd486`edce6c10 fffff803`8effe798 : fffff803`8f065ea8 ffffe604`8188e000 fffff803`8edae2e4 ffffe604`88249000 : nvlddmkm+0x506e8f
ffffd486`edce6c18 fffff803`8f065ea8 : ffffe604`8188e000 fffff803`8edae2e4 ffffe604`88249000 ffffe604`87944000 : nvlddmkm+0x8ae798
ffffd486`edce6c20 ffffe604`8188e000 : fffff803`8edae2e4 ffffe604`88249000 ffffe604`87944000 00000000`00000000 : nvlddmkm+0x915ea8
ffffd486`edce6c28 fffff803`8edae2e4 : ffffe604`88249000 ffffe604`87944000 00000000`00000000 ffffe604`8188e000 : 0xffffe604`8188e000
ffffd486`edce6c30 ffffe604`88249000 : ffffe604`87944000 00000000`00000000 ffffe604`8188e000 00000000`b0940a00 : nvlddmkm+0x65e2e4
ffffd486`edce6c38 ffffe604`87944000 : 00000000`00000000 ffffe604`8188e000 00000000`b0940a00 fffff803`8e8693ff : 0xffffe604`88249000
ffffd486`edce6c40 00000000`00000000 : ffffe604`8188e000 00000000`b0940a00 fffff803`8e8693ff ffffe604`8824a8e0 : 0xffffe604`87944000


CHKIMG_EXTENSION: !chkimg -lo 50 -d !FLTMGR
    fffff8036922cd05-fffff8036922cd06  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+35
    [ 48 ff:4c 8b ]
    fffff8036922cd0c-fffff8036922cd0f  4 bytes - FLTMGR!DeleteStreamListCtrlCallback+3c (+0x07)
    [ 0f 1f 44 00:e8 8f fd 60 ]
    fffff8036922cd1a-fffff8036922cd1b  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+4a (+0x0e)
    [ 48 ff:4c 8b ]
    fffff8036922cd21-fffff8036922cd24  4 bytes - FLTMGR!DeleteStreamListCtrlCallback+51 (+0x07)
    [ 0f 1f 44 00:e8 3a 3c 6b ]
    fffff8036922cd6a-fffff8036922cd6b  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+9a (+0x49)
    [ 48 ff:4c 8b ]
    fffff8036922cd71-fffff8036922cd74  4 bytes - FLTMGR!DeleteStreamListCtrlCallback+a1 (+0x07)
    [ 0f 1f 44 00:e8 3a 34 6b ]
    fffff8036922cd76-fffff8036922cd77  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+a6 (+0x05)
    [ 48 ff:4c 8b ]
    fffff8036922cd7d-fffff8036922cd80  4 bytes - FLTMGR!DeleteStreamListCtrlCallback+ad (+0x07)
    [ 0f 1f 44 00:e8 0e 0f 5e ]
24 errors : !FLTMGR (fffff8036922cd05-fffff8036922cd80)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffd486edce6200 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8046ac7e0bd, The address that the exception occurred at
Arg3: ffff8782078b69c8, Exception Record Address
Arg4: ffff8782078b6200, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nvlddmkm+34e0bd
fffff804`6ac7e0bd 488b4238        mov     rax,qword ptr [rdx+38h]

EXCEPTION_RECORD:  ffff8782078b69c8 -- (.exr 0xffff8782078b69c8)
ExceptionAddress: fffff8046ac7e0bd (nvlddmkm+0x000000000034e0bd)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038

CONTEXT:  ffff8782078b6200 -- (.cxr 0xffff8782078b6200;r)
rax=ffff9e08b33dc8a0 rbx=ffff8782078b6c70 rcx=ffff9e08b52c5730
rdx=0000000000000000 rsi=ffff9e08b6c5f000 rdi=ffff8782078b6c78
rip=fffff8046ac7e0bd rsp=ffff8782078b6c00 rbp=ffff9e08b1825000
 r8=ffff8782078b6c78  r9=ffff8782078b6c70 r10=fffff8046b1de6f0
r11=0000000000000006 r12=000000000000002c r13=0000000000000000
r14=ffff9e08b394c638 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x34e0bd:
fffff804`6ac7e0bd 488b4238        mov     rax,qword ptr [rdx+38h] ds:002b:00000000`00000038=????????????????
Last set context:
rax=ffff9e08b33dc8a0 rbx=ffff8782078b6c70 rcx=ffff9e08b52c5730
rdx=0000000000000000 rsi=ffff9e08b6c5f000 rdi=ffff8782078b6c78
rip=fffff8046ac7e0bd rsp=ffff8782078b6c00 rbp=ffff9e08b1825000
 r8=ffff8782078b6c78  r9=ffff8782078b6c70 r10=fffff8046b1de6f0
r11=0000000000000006 r12=000000000000002c r13=0000000000000000
r14=ffff9e08b394c638 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x34e0bd:
fffff804`6ac7e0bd 488b4238        mov     rax,qword ptr [rdx+38h] ds:002b:00000000`00000038=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000038

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000038

FOLLOWUP_IP:
nvlddmkm+34e0bd
fffff804`6ac7e0bd 488b4238        mov     rax,qword ptr [rdx+38h]

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from b0940a0000000000 to fffff8046ac7e0bd

STACK_TEXT: 
ffff8782`078b6c00 b0940a00`00000000 : fffff804`6ae36e8f fffff804`6b1de798 fffff804`6b245ea8 ffff9e08`b6c5f000 : nvlddmkm+0x34e0bd
ffff8782`078b6c08 fffff804`6ae36e8f : fffff804`6b1de798 fffff804`6b245ea8 ffff9e08`b6c5f000 fffff804`6af8e2e4 : 0xb0940a00`00000000
ffff8782`078b6c10 fffff804`6b1de798 : fffff804`6b245ea8 ffff9e08`b6c5f000 fffff804`6af8e2e4 ffff9e08`b1825000 : nvlddmkm+0x506e8f
ffff8782`078b6c18 fffff804`6b245ea8 : ffff9e08`b6c5f000 fffff804`6af8e2e4 ffff9e08`b1825000 ffff9e08`b23bf000 : nvlddmkm+0x8ae798
ffff8782`078b6c20 ffff9e08`b6c5f000 : fffff804`6af8e2e4 ffff9e08`b1825000 ffff9e08`b23bf000 00000000`00000000 : nvlddmkm+0x915ea8
ffff8782`078b6c28 fffff804`6af8e2e4 : ffff9e08`b1825000 ffff9e08`b23bf000 00000000`00000000 ffff9e08`b6c5f000 : 0xffff9e08`b6c5f000
ffff8782`078b6c30 ffff9e08`b1825000 : ffff9e08`b23bf000 00000000`00000000 ffff9e08`b6c5f000 00000000`b0940a00 : nvlddmkm+0x65e2e4
ffff8782`078b6c38 ffff9e08`b23bf000 : 00000000`00000000 ffff9e08`b6c5f000 00000000`b0940a00 fffff804`6aa493ff : 0xffff9e08`b1825000
ffff8782`078b6c40 00000000`00000000 : ffff9e08`b6c5f000 00000000`b0940a00 fffff804`6aa493ff ffff9e08`b18268e0 : 0xffff9e08`b23bf000


CHKIMG_EXTENSION: !chkimg -lo 50 -d !FLTMGR
    fffff8044318cd05-fffff8044318cd06  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+35
    [ 48 ff:4c 8b ]
    fffff8044318cd0c-fffff8044318cd10  5 bytes - FLTMGR!DeleteStreamListCtrlCallback+3c (+0x07)
    [ 0f 1f 44 00 00:e8 8f fd 6a 01 ]
    fffff8044318cd1a-fffff8044318cd1b  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+4a (+0x0e)
    [ 48 ff:4c 8b ]
    fffff8044318cd21-fffff8044318cd25  5 bytes - FLTMGR!DeleteStreamListCtrlCallback+51 (+0x07)
    [ 0f 1f 44 00 00:e8 3a 3c 75 01 ]
    fffff8044318cd6a-fffff8044318cd6b  2 bytes - FLTMGR!DeleteStreamListCtrlCallback+9a (+0x49)
    [ 48 ff:4c 8b ]
    fffff8044318cd71-fffff8044318cd77  7 bytes - FLTMGR!DeleteStreamListCtrlCallback+a1 (+0x07)
    [ 0f 1f 44 00 00 48 ff:e8 3a 34 75 01 4c 8b ]
    fffff8044318cd7d-fffff8044318cd81  5 bytes - FLTMGR!DeleteStreamListCtrlCallback+ad (+0x0c)
    [ 0f 1f 44 00 00:e8 0e 0f 68 01 ]
28 errors : !FLTMGR (fffff8044318cd05-fffff8044318cd81)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffff8782078b6200 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
 
driverlarım güncel, DDU ile sürücüyü kaldırdım ve kurmaya çalıştım yine aynı sorun devam ediyor. Garantiye mi versem acaba ya da iade edebilir miyim laptobu alalı 10 günü geçmedi.
 
driverlarım güncel, DDU ile sürücüyü kaldırdım ve kurmaya çalıştım yine aynı sorun devam ediyor. Garantiye mi versem acaba ya da iade edebilir miyim laptobu alalı 10 günü geçmedi.
İade edin hocam kartınızda sıkıntı olabilir. Drive kurulamayan kartların genellikle lehimleri çatlamış oluyor yani hasarlı oluyor. Aşırı ısıya falan maruz kalmadı umarım?
 

Geri
Yukarı