Ahmet Efe HAZER
Hectopat
Daha fazla
- Cinsiyet
- Erkek
Dosyaları herkese açık olarak paylaşın.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13000.14847\111620-6875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`1f600000 PsLoadedModuleList = 0xfffff803`2022a310
Debug session time: Mon Nov 16 08:23:13.513 2020 (UTC + 3:00)
System Uptime: 0 days 9:52:19.246
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`1f9f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8288`7d263b00=000000000000007e
0: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8032c3bb145, The address that the exception occurred at
Arg3: ffff82887d264af8, Exception Record Address
Arg4: ffff82887d264330, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 4061
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 94160
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8032c3bb145
BUGCHECK_P3: ffff82887d264af8
BUGCHECK_P4: ffff82887d264330
EXCEPTION_RECORD: ffff82887d264af8 -- (.exr 0xffff82887d264af8)
ExceptionAddress: fffff8032c3bb145 (nvlddmkm+0x00000000003fb145)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000208
Attempt to read from address 0000000000000208
CONTEXT: ffff82887d264330 -- (.cxr 0xffff82887d264330)
rax=0000000000000000 rbx=ffff8e8372c30620 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000003 rdi=ffff8e8371f88000
rip=fffff8032c3bb145 rsp=ffff82887d264d30 rbp=ffff82887d264d80
r8=000000000000000a r9=ffff8e8372091000 r10=0000000000000000
r11=ffff82887d264be0 r12=0000000000000002 r13=00000000ffffffff
r14=0000000000000000 r15=0000000000000002
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nvlddmkm+0x3fb145:
fffff803`2c3bb145 ff9008020000 call qword ptr [rax+208h] ds:002b:00000000`00000208=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff803202fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8032020f340: Unable to get Flags value from nt!KdVersionBlock
fffff8032020f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000208
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: 0000000000000208
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff8288`7d264d30 ffff8e83`72c30620 : ffff8288`7d264d80 00000000`00000003 00000000`00000003 00000000`00000000 : nvlddmkm+0x3fb145
ffff8288`7d264d38 ffff8288`7d264d80 : 00000000`00000003 00000000`00000003 00000000`00000000 ffff8e83`72c30620 : 0xffff8e83`72c30620
ffff8288`7d264d40 00000000`00000003 : 00000000`00000003 00000000`00000000 ffff8e83`72c30620 ffff8e83`72091000 : 0xffff8288`7d264d80
ffff8288`7d264d48 00000000`00000003 : 00000000`00000000 ffff8e83`72c30620 ffff8e83`72091000 ffff8e83`70cc3ed0 : 0x3
ffff8288`7d264d50 00000000`00000000 : ffff8e83`72c30620 ffff8e83`72091000 ffff8e83`70cc3ed0 00000000`00000000 : 0x3
SYMBOL_NAME: nvlddmkm+3fb145
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xffff82887d264330 ; kb
BUCKET_ID_FUNC_OFFSET: 3fb145
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
---------
OCCT ile bu işlemlerden sonra ekran kartınızı test edin.
- Intel ve NVIDIA ekran kartı sürücünüzü DDU ile kaldırıp, cihazınıza uyumlu olan en son WHQL sürümü yükleyin.
Rehber: DDU ile Sürücü Kaldırma Rehberi
Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...www.technopat.net - CPU-Z programını kaldırın.
- Xbox 360 Controller kullanıyorsunuz sanırım, yazılımını kaldırın ve bir süre gözlem amaçlı kullanmayın.
- Intel'e ait OC yazılımını kaldırın. Ayarlarınızı varsayılan ayarlara alın.
Kod:Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64. Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13000.14847\111620-6875-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available. ************* Path validation summary ************** Response Time (ms) Location. Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (2 procs) Free x64. Product: WinNt, suite: TerminalServer SingleUserTS Personal. Edition build lab: 19041.1.amd64fre.vb_release.191206-1406. Machine Name: Kernel base = 0xfffff803`1f600000 PsLoadedModuleList = 0xfffff803`2022a310. Debug session time: Mon Nov 16 08:23:13.513 2020 (UTC + 3:00) System Uptime: 0 days 9:52:19.246. Loading Kernel Symbols. ............................................................... ................................................................ ................................................................ ........ Loading User Symbols. Loading unloaded module list. ................... For analysis of this file, run !analyze -v. nt!KeBugCheckEx: fffff803`1f9f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8288`7d263b00=000000000000007e. 0: kd> !analyze -v. ******************************************************************************* * * * 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: fffff8032c3bb145, The address that the exception occurred at. Arg3: ffff82887d264af8, Exception Record Address. Arg4: ffff82887d264330, Context Record Address. Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys. KEY_VALUES_STRING: 1. Key : AV.Dereference. Value: NullClassPtr. Key : AV.Fault. Value: Read. Key : Analysis.CPU.mSec. Value: 4061. Key : Analysis.DebugAnalysisProvider.CPP. Value: Create: 8007007e on DESKTOP-IPC9T25. Key : Analysis.DebugData. Value: CreateObject. Key : Analysis.DebugModel. Value: CreateObject. Key : Analysis.Elapsed.mSec. Value: 94160. Key : Analysis.Memory.CommitPeak.Mb. Value: 76. Key : Analysis.System. Value: CreateObject. 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. ADDITIONAL_XML: 1. OS_BUILD_LAYERS: 1. BUGCHECK_CODE: 7e. BUGCHECK_P1: ffffffffc0000005. BUGCHECK_P2: fffff8032c3bb145. BUGCHECK_P3: ffff82887d264af8. BUGCHECK_P4: ffff82887d264330. EXCEPTION_RECORD: ffff82887d264af8 -- (.exr 0xffff82887d264af8) ExceptionAddress: fffff8032c3bb145 (nvlddmkm+0x00000000003fb145) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000. NumberParameters: 2. Parameter[0]: 0000000000000000. Parameter[1]: 0000000000000208. Attempt to read from address 0000000000000208. CONTEXT: ffff82887d264330 -- (.cxr 0xffff82887d264330) rax=0000000000000000 rbx=ffff8e8372c30620 rcx=0000000000000000. rdx=0000000000000000 rsi=0000000000000003 rdi=ffff8e8371f88000. rip=fffff8032c3bb145 rsp=ffff82887d264d30 rbp=ffff82887d264d80. r8=000000000000000a r9=ffff8e8372091000 r10=0000000000000000. r11=ffff82887d264be0 r12=0000000000000002 r13=00000000ffffffff. r14=0000000000000000 r15=0000000000000002. [/QUOTE]
OCCT ile bu işlemlerden sonra ekran kartınızı test edin.
- Intel ve NVIDIA ekran kartı sürücünüzü DDU ile kaldırıp, cihazınıza uyumlu olan en son WHQL sürümü yükleyin.
Rehber: DDU ile Sürücü Kaldırma Rehberi
Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...www.technopat.net - CPU-Z programını kaldırın.
- Xbox 360 Controller kullanıyorsunuz sanırım, yazılımını kaldırın ve bir süre gözlem amaçlı kullanmayın.
- Intel'e ait OC yazılımını kaldırın. Ayarlarınızı varsayılan ayarlara alın.
Kod:Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64. Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13000.14847\111620-6875-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available. ************* Path validation summary ************** Response Time (ms) Location. Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (2 procs) Free x64. Product: WinNt, suite: TerminalServer SingleUserTS Personal. Edition build lab: 19041.1.amd64fre.vb_release.191206-1406. Machine Name: Kernel base = 0xfffff803`1f600000 PsLoadedModuleList = 0xfffff803`2022a310. Debug session time: Mon Nov 16 08:23:13.513 2020 (UTC + 3:00) System Uptime: 0 days 9:52:19.246. Loading Kernel Symbols. ............................................................... ................................................................ ................................................................ ........ Loading User Symbols. Loading unloaded module list. ................... For analysis of this file, run !analyze -v. nt!KeBugCheckEx: fffff803`1f9f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8288`7d263b00=000000000000007e. 0: kd> !analyze -v. ******************************************************************************* * * * 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: fffff8032c3bb145, The address that the exception occurred at. Arg3: ffff82887d264af8, Exception Record Address. Arg4: ffff82887d264330, Context Record Address. Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys. KEY_VALUES_STRING: 1. Key : AV.Dereference. Value: NullClassPtr. Key : AV.Fault. Value: Read. Key : Analysis.CPU.mSec. Value: 4061. Key : Analysis.DebugAnalysisProvider.CPP. Value: Create: 8007007e on DESKTOP-IPC9T25. Key : Analysis.DebugData. Value: CreateObject. Key : Analysis.DebugModel. Value: CreateObject. Key : Analysis.Elapsed.mSec. Value: 94160. Key : Analysis.Memory.CommitPeak.Mb. Value: 76. Key : Analysis.System. Value: CreateObject. 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. ADDITIONAL_XML: 1. OS_BUILD_LAYERS: 1. BUGCHECK_CODE: 7e. BUGCHECK_P1: ffffffffc0000005. BUGCHECK_P2: fffff8032c3bb145. BUGCHECK_P3: ffff82887d264af8. BUGCHECK_P4: ffff82887d264330. EXCEPTION_RECORD: ffff82887d264af8 -- (.exr 0xffff82887d264af8) ExceptionAddress: fffff8032c3bb145 (nvlddmkm+0x00000000003fb145) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000. NumberParameters: 2. Parameter[0]: 0000000000000000. Parameter[1]: 0000000000000208. Attempt to read from address 0000000000000208. CONTEXT: ffff82887d264330 -- (.cxr 0xffff82887d264330) rax=0000000000000000 rbx=ffff8e8372c30620 rcx=0000000000000000. rdx=0000000000000000 rsi=0000000000000003 rdi=ffff8e8371f88000. rip=fffff8032c3bb145 rsp=ffff82887d264d30 rbp=ffff82887d264d80. r8=000000000000000a r9=ffff8e8372091000 r10=0000000000000000. r11=ffff82887d264be0 r12=0000000000000002 r13=00000000ffffffff. r14=0000000000000000 r15=0000000000000002. iopl=0 nv up ei pl nz na pe nc. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202. nvlddmkm+0x3fb145: fffff803`2c3bb145 ff9008020000 call qword ptr [rax+208h] ds:002b:00000000`00000208=???????????????? Resetting default scope. BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1. CUSTOMER_CRASH_COUNT: 1. PROCESS_NAME: System. READ_ADDRESS: fffff803202fb390: Unable to get MiVisibleState. Unable to get NonPagedPoolStart. Unable to get NonPagedPoolEnd. Unable to get PagedPoolStart. Unable to get PagedPoolEnd. fffff8032020f340: Unable to get Flags value from nt!KdVersionBlock. fffff8032020f340: Unable to get Flags value from nt!KdVersionBlock. unable to get nt!MmSpecialPagesInUse. 0000000000000208. 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: 0000000000000208. EXCEPTION_STR: 0xc0000005. STACK_TEXT: ffff8288`7d264d30 ffff8e83`72c30620 : ffff8288`7d264d80 00000000`00000003 00000000`00000003 00000000`00000000 : nvlddmkm+0x3fb145. ffff8288`7d264d38 ffff8288`7d264d80 : 00000000`00000003 00000000`00000003 00000000`00000000 ffff8e83`72c30620 : 0xffff8e83`72c30620. ffff8288`7d264d40 00000000`00000003 : 00000000`00000003 00000000`00000000 ffff8e83`72c30620 ffff8e83`72091000 : 0xffff8288`7d264d80. ffff8288`7d264d48 00000000`00000003 : 00000000`00000000 ffff8e83`72c30620 ffff8e83`72091000 ffff8e83`70cc3ed0 : 0x3. ffff8288`7d264d50 00000000`00000000 : ffff8e83`72c30620 ffff8e83`72091000 ffff8e83`70cc3ed0 00000000`00000000 : 0x3. SYMBOL_NAME: nvlddmkm+3fb145. MODULE_NAME: nvlddmkm. IMAGE_NAME: nvlddmkm.sys. STACK_COMMAND: .cxr 0xffff82887d264330 ; kb. BUCKET_ID_FUNC_OFFSET: 3fb145. 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. ---------
İhtiyacınız yoksa HWMonitor'u kaldırabilirsiniz. Kartınızı test edin, oradan gelen durum belirler muhtemelen sonucu.
Kart veri iletmediğinde o hatayı verir, donanımsal bir arızadır. Sadece o oyunda olabiliyor diyebilirsiniz ama oluyor, yapacak bir şey yok. Cihazı servise vermeniz gerekebilir. Farklı fikir edinmek adına akil hocamı da etiketleyeyim, o da fikir belirtsin. @24099
Batarya ile kullanma imkanım yok maalesef çünkü batarya çok dayanmıyor 7 yıllık bir laptoptan bahsediyoruz sonuçta. Bir de bunu deneyeyim duruma göre geri dönüş yaparım.3DMark Fire Strike ve Cinebench R23 ile ekran kartınızı test edin. CPU-Z ve HWiNFO aynı anda kullanmayın.
@ViooYa hocamın dediklerine ek olarak Avast! kaldırın ve aşağıdaki klasörlerin içlerini temizleyin.
C:\Windows\Prefetch
C:\Windows\Temp
%Temp%
Daha sonra konuya geri dönüş yapın duruma göre. Bataryasız kullanıyorsanız laptopu bataryasını takıp kullanın.