Çözüldü i5 7500 Intel chipset sürücüsü yüklenmiyor

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Kaykerem

Hectopat
Katılım
16 Haziran 2018
Mesajlar
45
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Merhabalar. Dün bilgisayara format attım 2 sürücü dışında tüm sürücüler yüklendi. O sürücüler forumda sorduğumda birinin chipset sürücüsü olduğu söylendi. Sürücüyü indirdim ama kurarken bar sonlardayken görüntü gidiyor Windows'un aygıt çıkartma sesi geliyor ve bilgisayar yeniden başlıyor. Sorun nedir acaba? Sürücüyü hem -overall ile hem de normal yükledim minidump dosyaları dosyaları burada (bilgisayar Casper Nirvana DT300 işlemci i5 7500)
 
Son düzenleyen: Moderatör:
Çözüm
İsteyene minidump analizi:

[CODE title="Minidump analizi"]*******************************************************************************
* *
* 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: fffff8045904c0d8, The address that the exception occurred at.
Arg3: ffffac8ee0825b38, Exception Record Address.
Arg4: ffffac8ee0825370, Context Record Address.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read.

Key : Analysis.CPU.mSec
Value: 8656.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 148028.

Key : Analysis.Init.CPU.mSec
Value: 1406.

Key : Analysis.Init.Elapsed.mSec
Value: 171513.

Key : Analysis.Memory.CommitPeak.Mb
Value: 97.

Key : WER.OS.Branch
Value: vb_release.

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 031722-22750-01.dmp

BUGCHECK_CODE: 7e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8045904c0d8.

BUGCHECK_P3: ffffac8ee0825b38.

BUGCHECK_P4: ffffac8ee0825370.

EXCEPTION_RECORD: ffffac8ee0825b38 -- (.exr 0xffffac8ee0825b38)
ExceptionAddress: fffff8045904c0d8 (nvlddmkm+0x000000000063c0d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000.
NumberParameters: 2
Parameter[0]: 0000000000000000.
Parameter[1]: 000000000000094c.
Attempt to read from address 000000000000094c.

CONTEXT: ffffac8ee0825370 -- (.cxr 0xffffac8ee0825370)
rax=ffffc30d70564000 rbx=ffffc30d75a539c0 rcx=0000000000000000
rdx=ffffc30d70564000 rsi=ffffc30d7711e000 rdi=ffffc30d714eb000
rip=fffff8045904c0d8 rsp=ffffac8ee0825d70 rbp=ffffac8ee0825e70
r8=ffffac8ee0826000 r9=0000000000000000 r10=fffff804406ccce0
r11=0000000000000000 r12=ffffc30d77974800 r13=ffffc30d7605f6e0
r14=ffffc30d75d72000 r15=ffffac8ee0826000
iopl=0 nv up ei ng nz na po nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x63c0d8:
fffff804`5904c0d8 448b814c090000 mov r8d,dword ptr [rcx+94Ch] ds:002b:00000000`0000094c=????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

READ_ADDRESS: fffff80440efa390: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
000000000000094c.

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: 000000000000094c.

EXCEPTION_STR: 0xc0000005.

STACK_TEXT:
ffffac8e`e0825d70 00000000`00000000 : 00000000`00000001 ffffc30d`7711e000 00000000`00000000 fffff804`40e45620 : nvlddmkm+0x63c0d8

SYMBOL_NAME: nvlddmkm+63c0d8

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffac8ee0825370 ; kb.

BUCKET_ID_FUNC_OFFSET: 63c0d8.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner.
---------[/CODE]

Ayrıca bunları denedin mi;
2side aynı tek farkı dosya uzantısı.
Hangi dosya uzantısını istiyorsanız seçin.
2side aynı sürücü demiştim.
Yanlış biliyor da olabilirim.
@Kaykerem
@Kaykerem

Denerim birazdan teşekkürler.
İsteyene minidump analizi:

[CODE title="Minidump analizi"]*******************************************************************************
* *
* 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: fffff8045904c0d8, The address that the exception occurred at.
Arg3: ffffac8ee0825b38, Exception Record Address.
Arg4: ffffac8ee0825370, Context Record Address.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read.

Key : Analysis.CPU.mSec
Value: 8656.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 148028.

Key : Analysis.Init.CPU.mSec
Value: 1406.

Key : Analysis.Init.Elapsed.mSec
Value: 171513.

Key : Analysis.Memory.CommitPeak.Mb
Value: 97.

Key : WER.OS.Branch
Value: vb_release.

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 031722-22750-01.dmp

BUGCHECK_CODE: 7e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8045904c0d8.

BUGCHECK_P3: ffffac8ee0825b38.

BUGCHECK_P4: ffffac8ee0825370.

EXCEPTION_RECORD: ffffac8ee0825b38 -- (.exr 0xffffac8ee0825b38)
ExceptionAddress: fffff8045904c0d8 (nvlddmkm+0x000000000063c0d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000.
NumberParameters: 2
Parameter[0]: 0000000000000000.
Parameter[1]: 000000000000094c.
Attempt to read from address 000000000000094c.

CONTEXT: ffffac8ee0825370 -- (.cxr 0xffffac8ee0825370)
rax=ffffc30d70564000 rbx=ffffc30d75a539c0 rcx=0000000000000000
rdx=ffffc30d70564000 rsi=ffffc30d7711e000 rdi=ffffc30d714eb000
rip=fffff8045904c0d8 rsp=ffffac8ee0825d70 rbp=ffffac8ee0825e70
r8=ffffac8ee0826000 r9=0000000000000000 r10=fffff804406ccce0
r11=0000000000000000 r12=ffffc30d77974800 r13=ffffc30d7605f6e0
r14=ffffc30d75d72000 r15=ffffac8ee0826000
iopl=0 nv up ei ng nz na po nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x63c0d8:
fffff804`5904c0d8 448b814c090000 mov r8d,dword ptr [rcx+94Ch] ds:002b:00000000`0000094c=????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

READ_ADDRESS: fffff80440efa390: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
000000000000094c.

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: 000000000000094c.

EXCEPTION_STR: 0xc0000005.

STACK_TEXT:
ffffac8e`e0825d70 00000000`00000000 : 00000000`00000001 ffffc30d`7711e000 00000000`00000000 fffff804`40e45620 : nvlddmkm+0x63c0d8

SYMBOL_NAME: nvlddmkm+63c0d8

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffac8ee0825370 ; kb.

BUCKET_ID_FUNC_OFFSET: 63c0d8.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner.
---------[/CODE]

Ayrıca bunları denedin mi;
2side aynı tek farkı dosya uzantısı.
Hangi dosya uzantısını istiyorsanız seçin.
2side aynı sürücü demiştim.
Yanlış biliyor da olabilirim.
@Kaykerem
@Kaykerem

Bu sürücüleri daha denemedim ama Intel Driver Support Asistant'dan anakart modelini gördüm Google'a yazdığımda ECS elitegroup diye bir firmanın anakartı olduğunu buldum sitede chipset sürücüsü var ama biraz eski bir sorun olur mu ?
1648055959785.png

Denerim birazdan teşekkürler.

Bu sürücüleri daha denemedim ama Intel driver Support Asistant'dan anakart modelini gördüm Google'a yazdığımda ECS elitegroup diye bir firmanın anakartı olduğunu buldum sitede chipset sürücüsü var ama biraz eski bir sorun olur mu?
1648055959785.png

Ayrıca anakartın indirmeleri burada bunlardan biri temel sistem aygıtı olabilir mi. https://www.ecs.com.tw/en/Product/Motherboard/H110M4-C2H/download
ECS'nin sitesindeki sürücü normal bir şekilde yüklendi ve temel sistem aygıtı ve PCI veri alma verme sürücüsünün ünlemi kalktı.
İsteyene minidump analizi:

[CODE title="Minidump analizi"]*******************************************************************************
* *
* 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: fffff8045904c0d8, The address that the exception occurred at.
Arg3: ffffac8ee0825b38, Exception Record Address.
Arg4: ffffac8ee0825370, Context Record Address.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read.

Key : Analysis.CPU.mSec
Value: 8656.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 148028.

Key : Analysis.Init.CPU.mSec
Value: 1406.

Key : Analysis.Init.Elapsed.mSec
Value: 171513.

Key : Analysis.Memory.CommitPeak.Mb
Value: 97.

Key : WER.OS.Branch
Value: vb_release.

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 031722-22750-01.dmp

BUGCHECK_CODE: 7e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8045904c0d8.

BUGCHECK_P3: ffffac8ee0825b38.

BUGCHECK_P4: ffffac8ee0825370.

EXCEPTION_RECORD: ffffac8ee0825b38 -- (.exr 0xffffac8ee0825b38)
ExceptionAddress: fffff8045904c0d8 (nvlddmkm+0x000000000063c0d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000.
NumberParameters: 2
Parameter[0]: 0000000000000000.
Parameter[1]: 000000000000094c.
Attempt to read from address 000000000000094c.

CONTEXT: ffffac8ee0825370 -- (.cxr 0xffffac8ee0825370)
rax=ffffc30d70564000 rbx=ffffc30d75a539c0 rcx=0000000000000000
rdx=ffffc30d70564000 rsi=ffffc30d7711e000 rdi=ffffc30d714eb000
rip=fffff8045904c0d8 rsp=ffffac8ee0825d70 rbp=ffffac8ee0825e70
r8=ffffac8ee0826000 r9=0000000000000000 r10=fffff804406ccce0
r11=0000000000000000 r12=ffffc30d77974800 r13=ffffc30d7605f6e0
r14=ffffc30d75d72000 r15=ffffac8ee0826000
iopl=0 nv up ei ng nz na po nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x63c0d8:
fffff804`5904c0d8 448b814c090000 mov r8d,dword ptr [rcx+94Ch] ds:002b:00000000`0000094c=????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

READ_ADDRESS: fffff80440efa390: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
000000000000094c.

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: 000000000000094c.

EXCEPTION_STR: 0xc0000005.

STACK_TEXT:
ffffac8e`e0825d70 00000000`00000000 : 00000000`00000001 ffffc30d`7711e000 00000000`00000000 fffff804`40e45620 : nvlddmkm+0x63c0d8

SYMBOL_NAME: nvlddmkm+63c0d8

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffac8ee0825370 ; kb.

BUCKET_ID_FUNC_OFFSET: 63c0d8.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner.
---------[/CODE]

Ayrıca bunları denedin mi;
2side aynı tek farkı dosya uzantısı.
Hangi dosya uzantısını istiyorsanız seçin.
2side aynı sürücü demiştim.
Yanlış biliyor da olabilirim.
@Kaykerem
@Kaykerem
 
Son düzenleme:
İsteyene minidump analizi:

[CODE title="Minidump analizi"]*******************************************************************************
* *
* 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: fffff8045904c0d8, The address that the exception occurred at.
Arg3: ffffac8ee0825b38, Exception Record Address.
Arg4: ffffac8ee0825370, Context Record Address.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read.

Key : Analysis.CPU.mSec
Value: 8656.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 148028.

Key : Analysis.Init.CPU.mSec
Value: 1406.

Key : Analysis.Init.Elapsed.mSec
Value: 171513.

Key : Analysis.Memory.CommitPeak.Mb
Value: 97.

Key : WER.OS.Branch
Value: vb_release.

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 031722-22750-01.dmp

BUGCHECK_CODE: 7e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8045904c0d8.

BUGCHECK_P3: ffffac8ee0825b38.

BUGCHECK_P4: ffffac8ee0825370.

EXCEPTION_RECORD: ffffac8ee0825b38 -- (.exr 0xffffac8ee0825b38)
ExceptionAddress: fffff8045904c0d8 (nvlddmkm+0x000000000063c0d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000.
NumberParameters: 2
Parameter[0]: 0000000000000000.
Parameter[1]: 000000000000094c.
Attempt to read from address 000000000000094c.

CONTEXT: ffffac8ee0825370 -- (.cxr 0xffffac8ee0825370)
rax=ffffc30d70564000 rbx=ffffc30d75a539c0 rcx=0000000000000000
rdx=ffffc30d70564000 rsi=ffffc30d7711e000 rdi=ffffc30d714eb000
rip=fffff8045904c0d8 rsp=ffffac8ee0825d70 rbp=ffffac8ee0825e70
r8=ffffac8ee0826000 r9=0000000000000000 r10=fffff804406ccce0
r11=0000000000000000 r12=ffffc30d77974800 r13=ffffc30d7605f6e0
r14=ffffc30d75d72000 r15=ffffac8ee0826000
iopl=0 nv up ei ng nz na po nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x63c0d8:
fffff804`5904c0d8 448b814c090000 mov r8d,dword ptr [rcx+94Ch] ds:002b:00000000`0000094c=????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

READ_ADDRESS: fffff80440efa390: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
000000000000094c.

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: 000000000000094c.

EXCEPTION_STR: 0xc0000005.

STACK_TEXT:
ffffac8e`e0825d70 00000000`00000000 : 00000000`00000001 ffffc30d`7711e000 00000000`00000000 fffff804`40e45620 : nvlddmkm+0x63c0d8

SYMBOL_NAME: nvlddmkm+63c0d8

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffac8ee0825370 ; kb.

BUCKET_ID_FUNC_OFFSET: 63c0d8.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner.
---------[/CODE]

Ayrıca bunları denedin mi;
2side aynı tek farkı dosya uzantısı.
Hangi dosya uzantısını istiyorsanız seçin.
2side aynı sürücü demiştim.
Yanlış biliyor da olabilirim.
@Kaykerem
@Kaykerem

Denerim birazdan teşekkürler.
İsteyene minidump analizi:

[CODE title="Minidump analizi"]*******************************************************************************
* *
* 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: fffff8045904c0d8, The address that the exception occurred at.
Arg3: ffffac8ee0825b38, Exception Record Address.
Arg4: ffffac8ee0825370, Context Record Address.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read.

Key : Analysis.CPU.mSec
Value: 8656.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 148028.

Key : Analysis.Init.CPU.mSec
Value: 1406.

Key : Analysis.Init.Elapsed.mSec
Value: 171513.

Key : Analysis.Memory.CommitPeak.Mb
Value: 97.

Key : WER.OS.Branch
Value: vb_release.

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 031722-22750-01.dmp

BUGCHECK_CODE: 7e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8045904c0d8.

BUGCHECK_P3: ffffac8ee0825b38.

BUGCHECK_P4: ffffac8ee0825370.

EXCEPTION_RECORD: ffffac8ee0825b38 -- (.exr 0xffffac8ee0825b38)
ExceptionAddress: fffff8045904c0d8 (nvlddmkm+0x000000000063c0d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000.
NumberParameters: 2
Parameter[0]: 0000000000000000.
Parameter[1]: 000000000000094c.
Attempt to read from address 000000000000094c.

CONTEXT: ffffac8ee0825370 -- (.cxr 0xffffac8ee0825370)
rax=ffffc30d70564000 rbx=ffffc30d75a539c0 rcx=0000000000000000
rdx=ffffc30d70564000 rsi=ffffc30d7711e000 rdi=ffffc30d714eb000
rip=fffff8045904c0d8 rsp=ffffac8ee0825d70 rbp=ffffac8ee0825e70
r8=ffffac8ee0826000 r9=0000000000000000 r10=fffff804406ccce0
r11=0000000000000000 r12=ffffc30d77974800 r13=ffffc30d7605f6e0
r14=ffffc30d75d72000 r15=ffffac8ee0826000
iopl=0 nv up ei ng nz na po nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x63c0d8:
fffff804`5904c0d8 448b814c090000 mov r8d,dword ptr [rcx+94Ch] ds:002b:00000000`0000094c=????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

READ_ADDRESS: fffff80440efa390: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
000000000000094c.

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: 000000000000094c.

EXCEPTION_STR: 0xc0000005.

STACK_TEXT:
ffffac8e`e0825d70 00000000`00000000 : 00000000`00000001 ffffc30d`7711e000 00000000`00000000 fffff804`40e45620 : nvlddmkm+0x63c0d8

SYMBOL_NAME: nvlddmkm+63c0d8

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffac8ee0825370 ; kb.

BUCKET_ID_FUNC_OFFSET: 63c0d8.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner.
---------[/CODE]

Ayrıca bunları denedin mi;
2side aynı tek farkı dosya uzantısı.
Hangi dosya uzantısını istiyorsanız seçin.
2side aynı sürücü demiştim.
Yanlış biliyor da olabilirim.
@Kaykerem
@Kaykerem

Bu sürücüleri daha denemedim ama Intel Driver Support Asistant'dan anakart modelini gördüm Google'a yazdığımda ECS elitegroup diye bir firmanın anakartı olduğunu buldum sitede chipset sürücüsü var ama biraz eski bir sorun olur mu ?
1648055959785.png

Denerim birazdan teşekkürler.

Bu sürücüleri daha denemedim ama Intel driver Support Asistant'dan anakart modelini gördüm Google'a yazdığımda ECS elitegroup diye bir firmanın anakartı olduğunu buldum sitede chipset sürücüsü var ama biraz eski bir sorun olur mu?
1648055959785.png

Ayrıca anakartın indirmeleri burada bunlardan biri temel sistem aygıtı olabilir mi. https://www.ecs.com.tw/en/Product/Motherboard/H110M4-C2H/download
ECS'nin sitesindeki sürücü normal bir şekilde yüklendi ve temel sistem aygıtı ve PCI veri alma verme sürücüsünün ünlemi kalktı.
 
Son düzenleme:
Çözüm

Geri
Yukarı