yusuf tayyib
Decapat
- Katılım
- 18 Eylül 2022
- Mesajlar
- 13
Daha fazla
- Cinsiyet
- Erkek
amdkmdag.sys ile alakalı sıkıntı var. Yani AMD grafik sürücüsü.BiosVersion = 2.60 (7C96v26)
BiosReleaseDate = 12/13/2021
SystemProductName = MS-7C96
BaseBoardProduct = B550M-A PRO (MS-7C96)SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealthchkdsk /f /rvwifibus.sys = Virtual WiFi Bus Driver
wdiwifi.sys = WDI Driver Framework Driver
vwifimp.sys = Microsoft Virtual WiFi Miniport Driverrtwlanu.sys = Realtek RTLxxxxx Wireless USB 2.0 Adapter
HWiNFO64A_15 = HWiNFO Kernel Driver
kerneld.x64 = AIDA64 Extreme Edition*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80429f4e04d, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000fffff80429f4, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ContextRecord ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2499
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 11416
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 7440
Key : Analysis.Memory.CommitPeak.Mb
Value: 137
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
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: 091722-3328-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffff80000003
BUGCHECK_P2: fffff80429f4e04d
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80429f4
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000fffff80429f4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: 2df6870d8b48ff8b -- (.trap 0x2df6870d8b48ff8b)
Unable to read trap frame at 2df6870d`8b48ff8b
STACK_TEXT:
ffffc501`f2f52158 fffff804`2a0f5e3e : 00000000`0000001e ffffffff`80000003 fffff804`29f4e04d 00000000`00000000 : nt!KeBugCheckEx
ffffc501`f2f52160 fffff804`2a000c22 : fffff804`2a0f5e1c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffffc501`f2f521a0 fffff804`29edd7b7 : ffffc501`f2f52710 00000000`00000000 fffffb02`a46bfc20 fffff804`29ffb884 : nt!RtlpExecuteHandlerForException+0x12
ffffc501`f2f521d0 fffff804`29edc3b6 : fffffb02`a46bf398 ffffc501`f2f52e20 fffffb02`a46bf398 00000000`00000000 : nt!RtlDispatchException+0x297
ffffc501`f2f528f0 fffff804`29ff8bf2 : c9334508`488d4800 c8eae8d2`3301b041 2df6870d`8b48ff8b 00000001`4041c700 : nt!KiDispatchException+0x186
ffffc501`f2f52fb0 fffff804`29ff8bc0 : fffff804`2a009da5 00000000`00000006 00000001`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffb02`a46bf258 fffff804`2a009da5 : 00000000`00000006 00000001`00000000 00000000`00000000 00000000`00000002 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffb02`a46bf260 fffff804`2a003716 : 00000000`00000001 00000000`00000000 00000000`00000004 ffffc501`f2f00180 : nt!KiExceptionDispatch+0x125
fffffb02`a46bf440 fffff804`29f4e04e : fffffb02`a46bf640 ffff2c5a`3a1b3ce5 00000000`00000001 ffffb184`5950e930 : nt!KiBreakpointTrap+0x316
fffffb02`a46bf5d0 fffffb02`a46bf640 : ffff2c5a`3a1b3ce5 00000000`00000001 ffffb184`5950e930 ffffc501`f2f00180 : nt!RtlStringCopyWorkerW+0x76
fffffb02`a46bf5d8 ffff2c5a`3a1b3ce5 : 00000000`00000001 ffffb184`5950e930 ffffc501`f2f00180 fffff804`29e625a7 : 0xfffffb02`a46bf640
fffffb02`a46bf5e0 00000000`00000001 : ffffb184`5950e930 ffffc501`f2f00180 fffff804`29e625a7 0000001b`a308e1f3 : 0xffff2c5a`3a1b3ce5
fffffb02`a46bf5e8 ffffb184`5950e930 : ffffc501`f2f00180 fffff804`29e625a7 0000001b`a308e1f3 ffffc501`f2f081c8 : 0x1
fffffb02`a46bf5f0 ffffc501`f2f00180 : fffff804`29e625a7 0000001b`a308e1f3 ffffc501`f2f081c8 0000001d`f1a8dad9 : 0xffffb184`5950e930
fffffb02`a46bf5f8 fffff804`29e625a7 : 0000001b`a308e1f3 ffffc501`f2f081c8 0000001d`f1a8dad9 ffffc501`f2f08210 : 0xffffc501`f2f00180
fffffb02`a46bf600 fffff804`29e61286 : 00000b65`ace571a7 00000000`00000001 0000000a`8d5c946c ffffc501`f2f00180 : nt!KeResumeClockTimerFromIdle+0x377
fffffb02`a46bf6b0 fffff804`29e5f9b4 : 00000000`00000000 00001f80`00000000 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x1756
fffffb02`a46bfab0 fffff804`29ffb884 : ffffffff`00000000 ffffc501`f2f0b340 ffffb184`70bce340 00000000`000005f1 : nt!PoIdle+0x374
fffffb02`a46bfc20 00000000`00000000 : fffffb02`a46c0000 fffffb02`a46b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
SYMBOL_NAME: nt!RtlStringCopyWorkerW+75
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1706
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 75
FAILURE_BUCKET_ID: 0x1E_80000003_nt!RtlStringCopyWorkerW
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f92caa72-f6d5-c0c6-dd19-ce4037ae9adb}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff80749e72710, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff80749e72668, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2702
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 54272
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 4933
Key : Analysis.Memory.CommitPeak.Mb
Value: 144
Key : Bugcheck.Code.DumpHeader
Value: 0x139
Key : Bugcheck.Code.Register
Value: 0x139
Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY
Key : FailFast.Type
Value: 3
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: 091722-3375-01.dmp
BUGCHECK_CODE: 139
BUGCHECK_P1: 3
BUGCHECK_P2: fffff80749e72710
BUGCHECK_P3: fffff80749e72668
BUGCHECK_P4: 0
TRAP_FRAME: fffff80749e72710 -- (.trap 0xfffff80749e72710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8389926c25c8 rbx=0000000000000000 rcx=0000000000000003
rdx=fffff80741d8b180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80745440078 rsp=fffff80749e728a0 rbp=ffff8389936c25c0
r8=0000000000000100 r9=000000000000002f r10=0000fffff807456c
r11=ffff87fbda200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KiProcessExpiredTimerList+0x248:
fffff807`45440078 cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: fffff80749e72668 -- (.exr 0xfffff80749e72668)
ExceptionAddress: fffff80745440078 (nt!KiProcessExpiredTimerList+0x0000000000000248)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y n tabanl bir arabelle in ta t n alg lad . Bu ta ma, k t niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.
EXCEPTION_CODE_STR: c0000409
EXCEPTION_PARAMETER1: 0000000000000003
EXCEPTION_STR: 0xc0000409
STACK_TEXT:
fffff807`49e723e8 fffff807`45609c69 : 00000000`00000139 00000000`00000003 fffff807`49e72710 fffff807`49e72668 : nt!KeBugCheckEx
fffff807`49e723f0 fffff807`4560a090 : fffff807`455632a0 fffff807`45530417 00000000`00009c40 fffff807`5a9b2d6d : nt!KiBugCheckDispatch+0x69
fffff807`49e72530 fffff807`45608423 : fffff807`49e728a8 00000000`00000000 00000000`ffffffff 00000000`00000007 : nt!KiFastFailDispatch+0xd0
fffff807`49e72710 fffff807`45440078 : ffff8389`88cdc200 00000000`00000000 ffff8389`92d4a570 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323
fffff807`49e728a0 fffff807`454a0eed : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0030ef3d : nt!KiProcessExpiredTimerList+0x248
fffff807`49e72990 fffff807`455fb8ce : 00000000`00000000 fffff807`41d8b180 fffff807`45f27a00 ffff8389`9127d280 : nt!KiRetireDpcList+0x5dd
fffff807`49e72c20 00000000`00000000 : fffff807`49e73000 fffff807`49e6c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!KiProcessExpiredTimerList+248
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1706
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 248
FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiProcessExpiredTimerList
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9db7945b-255d-24a1-9f2c-82344e883ab8}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
The exception handler for the kernel interrupt object interrupt management was
not able to handle the generated exception.
Arguments:
Arg1: fffff80445081b88, Exception Record (When Available)
Arg2: fffff804450813c0, Context Record (When Available)
Arg3: 0000000000000000, Not used
Arg4: 0000000000000000, Not used
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1968
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 61054
Key : Analysis.Init.CPU.mSec
Value: 327
Key : Analysis.Init.Elapsed.mSec
Value: 6548
Key : Analysis.Memory.CommitPeak.Mb
Value: 128
Key : Bugcheck.Code.DumpHeader
Value: 0x3d
Key : Bugcheck.Code.Register
Value: 0x3d
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: 091522-6812-01.dmp
BUGCHECK_CODE: 3d
BUGCHECK_P1: fffff80445081b88
BUGCHECK_P2: fffff804450813c0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
EXCEPTION_RECORD: fffff80445081b88 -- (.exr 0xfffff80445081b88)
ExceptionAddress: fffff80455e4001c (amdkmdag+0x00000000001c001c)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000fffff80455d4
CONTEXT: fffff804450813c0 -- (.cxr 0xfffff804450813c0)
rax=fffff80455e3ff4c rbx=ffff9f8321dd94e0 rcx=ffff9f8321dd5000
rdx=ffff9f8321dd94e0 rsi=ffffc2001623dbf0 rdi=ffff9f8321dd5000
rip=fffff80455e4001c rsp=fffff80445081dc8 rbp=ffff9f831e5fdbd0
r8=0000000000000000 r9=0000000000000000 r10=0000fffff80455d4
r11=ffffb1ff06000000 r12=000007a7e4ac19ac r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282
amdkmdag+0x1c001c:
fffff804`55e4001c 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:fffff804`45081dd0=0000000000000000
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0x80000003 - { ZEL DURUM} Kesme Noktas Bir kesme noktas na ula ld .
EXCEPTION_CODE_STR: 80000003
EXCEPTION_STR: 0x80000003
STACK_TEXT:
fffff804`45081dc8 fffff804`55e3ff61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdkmdag+0x1c001c
fffff804`45081dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9f83`21dd5000 : amdkmdag+0x1bff61
SYMBOL_NAME: amdkmdag+1c001c
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .cxr 0xfffff804450813c0 ; kb
BUCKET_ID_FUNC_OFFSET: 1c001c
FAILURE_BUCKET_ID: 0x3D_80000003_amdkmdag!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {1a0ee0e2-810f-bd16-6230-76a8cd17936f}
Followup: MachineOwner
---------
Dökümlerden birindeamdkmdag.sysile alakalı sıkıntı var. Yani AMD grafik sürücüsü.
Önce onu bir temizleyip tekrar kurmak lazım.
- Rehber: DDU ile Sürücü Kaldırma Rehberi buraya girip rehberi uygulayın.
- Kaldırdıktan sonra şu sürücüyü kurun: AMD Ryzen™ 5 5600G Drivers & Support
DDU ile kaldırıp en güncel sürücüleri kurduktan sonra hâlâ hata alıyorsanız aşağıdan devam edelim.
BIOS
Bu tür hatalarda genellikle BIOS güncelleme önerisi yapılmış. Yani BIOS'u güncelleyin derim, eski kalmış.
Kullandığınız BIOS:
BiosVersion = 2.60 (7C96v26) BiosReleaseDate = 12/13/2021 SystemProductName = MS-7C96 BaseBoardProduct = B550M-A PRO (MS-7C96)
BIOS listesi: MSI B550M-A PRO Motherboard (AMD Ryzen 3000 3rd Gen AM4, DDR4, M.2, USB 3.2 Gen 1, HDMI, Micro ATX)
Güncel BIOS: https://download.msi.com/bos_exe/mb/7C96v29.zip
ONARMA
Şu rehberi uygulayın: Eksik ve bozuk SYS dosyalarını onarma
Sadece 1. ve 4. komutları uygulamanız yeterlidir. Yani;
SFC /scannow DISM /Online /Cleanup-Image /RestoreHealth
Üsttekiler tamamlandıktan sonra şunu da yapın:
chkdsk /f /r
Ekstra olarak yüklenemeyen/geç yüklenen ve problemli olabilecek sürü listesini paylaşayım:
Windows sürücüleri:
vwifibus.sys = Virtual WiFi Bus Driver wdiwifi.sys = WDI Driver Framework Driver vwifimp.sys = Microsoft Virtual WiFi Miniport Driver
Sizin yüklemeleriniz ile alakalı sürücüler:
rtwlanu.sys = Realtek RTLxxxxx Wireless USB 2.0 Adapter HWiNFO64A_15 = HWiNFO Kernel Driver kerneld.x64 = AIDA64 Extreme Edition
Genelde Windows sürücüleri ile alakalı çok sıkıntı olmaz. Ama kendi yüklediğiniz program sürücüleri sıkıntılı olabilir.
Her ihtimale karşı HWiNFO ve AIDA64 şimdilik kaldırılabilir, belki çakışıyor olabilirler. Realtek sürücüsünde de bir problem olabilir, onu nereden indirdiniz?
Tüm bunlardan sonra düzelmediyse Memtest86 ile RAM testi yapın:
Memtest86 ile Bozuk RAM Testi
Bu rehberimizde Memtes86 ile RAM testi yaparak bozuk RAM modüllerini nasıl tespit edeceğinize bakıyoruz. Bilgisayarda karşılaşılan mavi ekran hatalarıwww.technopat.net
Dökümler:
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffff80000003, The exception code that was not handled Arg2: fffff80429f4e04d, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000fffff80429f4, Parameter 1 of the exception Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** 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: ExceptionRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: ContextRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: ExceptionRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: ContextRecord *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2499 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 11416 Key : Analysis.Init.CPU.mSec Value: 390 Key : Analysis.Init.Elapsed.mSec Value: 7440 Key : Analysis.Memory.CommitPeak.Mb Value: 137 Key : Bugcheck.Code.DumpHeader Value: 0x1e Key : Bugcheck.Code.Register Value: 0x1e 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: 091722-3328-01.dmp BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffff80000003 BUGCHECK_P2: fffff80429f4e04d BUGCHECK_P3: 0 BUGCHECK_P4: fffff80429f4 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000fffff80429f4 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: 2df6870d8b48ff8b -- (.trap 0x2df6870d8b48ff8b) Unable to read trap frame at 2df6870d`8b48ff8b STACK_TEXT: ffffc501`f2f52158 fffff804`2a0f5e3e : 00000000`0000001e ffffffff`80000003 fffff804`29f4e04d 00000000`00000000 : nt!KeBugCheckEx ffffc501`f2f52160 fffff804`2a000c22 : fffff804`2a0f5e1c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22 ffffc501`f2f521a0 fffff804`29edd7b7 : ffffc501`f2f52710 00000000`00000000 fffffb02`a46bfc20 fffff804`29ffb884 : nt!RtlpExecuteHandlerForException+0x12 ffffc501`f2f521d0 fffff804`29edc3b6 : fffffb02`a46bf398 ffffc501`f2f52e20 fffffb02`a46bf398 00000000`00000000 : nt!RtlDispatchException+0x297 ffffc501`f2f528f0 fffff804`29ff8bf2 : c9334508`488d4800 c8eae8d2`3301b041 2df6870d`8b48ff8b 00000001`4041c700 : nt!KiDispatchException+0x186 ffffc501`f2f52fb0 fffff804`29ff8bc0 : fffff804`2a009da5 00000000`00000006 00000001`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12 fffffb02`a46bf258 fffff804`2a009da5 : 00000000`00000006 00000001`00000000 00000000`00000000 00000000`00000002 : nt!KiExceptionDispatchOnExceptionStackContinue fffffb02`a46bf260 fffff804`2a003716 : 00000000`00000001 00000000`00000000 00000000`00000004 ffffc501`f2f00180 : nt!KiExceptionDispatch+0x125 fffffb02`a46bf440 fffff804`29f4e04e : fffffb02`a46bf640 ffff2c5a`3a1b3ce5 00000000`00000001 ffffb184`5950e930 : nt!KiBreakpointTrap+0x316 fffffb02`a46bf5d0 fffffb02`a46bf640 : ffff2c5a`3a1b3ce5 00000000`00000001 ffffb184`5950e930 ffffc501`f2f00180 : nt!RtlStringCopyWorkerW+0x76 fffffb02`a46bf5d8 ffff2c5a`3a1b3ce5 : 00000000`00000001 ffffb184`5950e930 ffffc501`f2f00180 fffff804`29e625a7 : 0xfffffb02`a46bf640 fffffb02`a46bf5e0 00000000`00000001 : ffffb184`5950e930 ffffc501`f2f00180 fffff804`29e625a7 0000001b`a308e1f3 : 0xffff2c5a`3a1b3ce5 fffffb02`a46bf5e8 ffffb184`5950e930 : ffffc501`f2f00180 fffff804`29e625a7 0000001b`a308e1f3 ffffc501`f2f081c8 : 0x1 fffffb02`a46bf5f0 ffffc501`f2f00180 : fffff804`29e625a7 0000001b`a308e1f3 ffffc501`f2f081c8 0000001d`f1a8dad9 : 0xffffb184`5950e930 fffffb02`a46bf5f8 fffff804`29e625a7 : 0000001b`a308e1f3 ffffc501`f2f081c8 0000001d`f1a8dad9 ffffc501`f2f08210 : 0xffffc501`f2f00180 fffffb02`a46bf600 fffff804`29e61286 : 00000b65`ace571a7 00000000`00000001 0000000a`8d5c946c ffffc501`f2f00180 : nt!KeResumeClockTimerFromIdle+0x377 fffffb02`a46bf6b0 fffff804`29e5f9b4 : 00000000`00000000 00001f80`00000000 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x1756 fffffb02`a46bfab0 fffff804`29ffb884 : ffffffff`00000000 ffffc501`f2f0b340 ffffb184`70bce340 00000000`000005f1 : nt!PoIdle+0x374 fffffb02`a46bfc20 00000000`00000000 : fffffb02`a46c0000 fffffb02`a46b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54 SYMBOL_NAME: nt!RtlStringCopyWorkerW+75 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1706 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 75 FAILURE_BUCKET_ID: 0x1E_80000003_nt!RtlStringCopyWorkerW OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f92caa72-f6d5-c0c6-dd19-ce4037ae9adb} Followup: MachineOwner ---------
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: fffff80749e72710, Address of the trap frame for the exception that caused the BugCheck Arg3: fffff80749e72668, Address of the exception record for the exception that caused the BugCheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2702 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 54272 Key : Analysis.Init.CPU.mSec Value: 390 Key : Analysis.Init.Elapsed.mSec Value: 4933 Key : Analysis.Memory.CommitPeak.Mb Value: 144 Key : Bugcheck.Code.DumpHeader Value: 0x139 Key : Bugcheck.Code.Register Value: 0x139 Key : FailFast.Name Value: CORRUPT_LIST_ENTRY Key : FailFast.Type Value: 3 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: 091722-3375-01.dmp BUGCHECK_CODE: 139 BUGCHECK_P1: 3 BUGCHECK_P2: fffff80749e72710 BUGCHECK_P3: fffff80749e72668 BUGCHECK_P4: 0 TRAP_FRAME: fffff80749e72710 -- (.trap 0xfffff80749e72710) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffff8389926c25c8 rbx=0000000000000000 rcx=0000000000000003 rdx=fffff80741d8b180 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80745440078 rsp=fffff80749e728a0 rbp=ffff8389936c25c0 r8=0000000000000100 r9=000000000000002f r10=0000fffff807456c r11=ffff87fbda200000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po cy nt!KiProcessExpiredTimerList+0x248: fffff807`45440078 cd29 int 29h Resetting default scope EXCEPTION_RECORD: fffff80749e72668 -- (.exr 0xfffff80749e72668) ExceptionAddress: fffff80745440078 (nt!KiProcessExpiredTimerList+0x0000000000000248) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y n tabanl bir arabelle in ta t n alg lad . Bu ta ma, k t niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 EXCEPTION_STR: 0xc0000409 STACK_TEXT: fffff807`49e723e8 fffff807`45609c69 : 00000000`00000139 00000000`00000003 fffff807`49e72710 fffff807`49e72668 : nt!KeBugCheckEx fffff807`49e723f0 fffff807`4560a090 : fffff807`455632a0 fffff807`45530417 00000000`00009c40 fffff807`5a9b2d6d : nt!KiBugCheckDispatch+0x69 fffff807`49e72530 fffff807`45608423 : fffff807`49e728a8 00000000`00000000 00000000`ffffffff 00000000`00000007 : nt!KiFastFailDispatch+0xd0 fffff807`49e72710 fffff807`45440078 : ffff8389`88cdc200 00000000`00000000 ffff8389`92d4a570 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323 fffff807`49e728a0 fffff807`454a0eed : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0030ef3d : nt!KiProcessExpiredTimerList+0x248 fffff807`49e72990 fffff807`455fb8ce : 00000000`00000000 fffff807`41d8b180 fffff807`45f27a00 ffff8389`9127d280 : nt!KiRetireDpcList+0x5dd fffff807`49e72c20 00000000`00000000 : fffff807`49e73000 fffff807`49e6c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e SYMBOL_NAME: nt!KiProcessExpiredTimerList+248 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1706 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 248 FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiProcessExpiredTimerList OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {9db7945b-255d-24a1-9f2c-82344e883ab8} Followup: MachineOwner ---------
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) The exception handler for the kernel interrupt object interrupt management was not able to handle the generated exception. Arguments: Arg1: fffff80445081b88, Exception Record (When Available) Arg2: fffff804450813c0, Context Record (When Available) Arg3: 0000000000000000, Not used Arg4: 0000000000000000, Not used Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1968 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 61054 Key : Analysis.Init.CPU.mSec Value: 327 Key : Analysis.Init.Elapsed.mSec Value: 6548 Key : Analysis.Memory.CommitPeak.Mb Value: 128 Key : Bugcheck.Code.DumpHeader Value: 0x3d Key : Bugcheck.Code.Register Value: 0x3d 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: 091522-6812-01.dmp BUGCHECK_CODE: 3d BUGCHECK_P1: fffff80445081b88 BUGCHECK_P2: fffff804450813c0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 EXCEPTION_RECORD: fffff80445081b88 -- (.exr 0xfffff80445081b88) ExceptionAddress: fffff80455e4001c (amdkmdag+0x00000000001c001c) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 1 Parameter[0]: 0000000000000000 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000fffff80455d4 CONTEXT: fffff804450813c0 -- (.cxr 0xfffff804450813c0) rax=fffff80455e3ff4c rbx=ffff9f8321dd94e0 rcx=ffff9f8321dd5000 rdx=ffff9f8321dd94e0 rsi=ffffc2001623dbf0 rdi=ffff9f8321dd5000 rip=fffff80455e4001c rsp=fffff80445081dc8 rbp=ffff9f831e5fdbd0 r8=0000000000000000 r9=0000000000000000 r10=0000fffff80455d4 r11=ffffb1ff06000000 r12=000007a7e4ac19ac r13=0000000000000000 r14=0000000000000001 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282 amdkmdag+0x1c001c: fffff804`55e4001c 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:fffff804`45081dd0=0000000000000000 Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0x80000003 - { ZEL DURUM} Kesme Noktas Bir kesme noktas na ula ld . EXCEPTION_CODE_STR: 80000003 EXCEPTION_STR: 0x80000003 STACK_TEXT: fffff804`45081dc8 fffff804`55e3ff61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdkmdag+0x1c001c fffff804`45081dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9f83`21dd5000 : amdkmdag+0x1bff61 SYMBOL_NAME: amdkmdag+1c001c MODULE_NAME: amdkmdag IMAGE_NAME: amdkmdag.sys STACK_COMMAND: .cxr 0xfffff804450813c0 ; kb BUCKET_ID_FUNC_OFFSET: 1c001c FAILURE_BUCKET_ID: 0x3D_80000003_amdkmdag!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {1a0ee0e2-810f-bd16-6230-76a8cd17936f} Followup: MachineOwner ---------
onarma dahil hepsini eksiksiz yaptım diğer driverlara bakamdım ama onlarıda kontrol etmenin bir yolunu bulurum veya driverları kontrol eden bir program biliyorsanız çok kolaylık olurcevap veremedim ilk forum kullanışım teşekkür ederim sırayla deneyeceğim hepsini umarım başarılı olurum vakit harcayıp değerlendirmeniz bile takdir hakediyor