Siz memtest yaparklen bende .dmp dosyalarını analiz edeceğim. Yapın testi
- Katılım
- 20 Aralık 2023
- Mesajlar
- 3.232
- Çözümler
- 26
- Beğeniler
- 1.908
Ekran kartı sürücünü de DDU ile "güvenli modda" silip en günceli ya da sırayla eski sürümleri de kurmayı deneyebilirsin.
3. hata. ntkrnlmp.exe
2-3-4 hataları tıpatıp aynı. Senin NVIDIA sürücüsü patlamış. RAM testi bitince @stormhawks47 hocanın üstteki mesajda dediğini yapacaksın.
Hata 5: MEMORY_MANAGEMENT (ntkrnlmp.exe)
Hata 6: (ntkrlmp.exe)
Şimdi senin hatalar RAM ve ekran kartı sürücüsü ile ilgili. EXPO/XMP kapat. Sürücüleri kaldırıp yeniden kur.
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: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000001, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Page.Virtual
Value: 0xffffffffffff0000
Key : AV.Type
Value: Read
Key : Analysis.CPU.mSec
Value: 4031
Key : Analysis.Elapsed.mSec
Value: 5781
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 1000
Key : Analysis.Init.Elapsed.mSec
Value: 8988
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2511.5.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_nt!KiDispatchException
Key : Failure.Exception.IP.Address
Value: 0x1
Key : Failure.Hash
Value: {00781d15-b897-afab-75cd-f83221cbf387}
Key : Faulting.IP.Type
Value: Null
Key : WER.System.BIOSRevision
Value: 6.8.0.0
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 1
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
FILE_IN_CAB: 032726-10906-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffd182202e5080
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff80796dc44c8: 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
ffffffffffffffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Taskmgr.exe
TRAP_FRAME: ffffcf02cce27654 -- (.trap 0xffffcf02cce27654)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00020000ffffd182 rsp=9664bc09ffffd182 rbp=00000000ffffd182
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=3 vip vif ov up di pl nz na po cy
0000:d182 ?? ???
Resetting default scope
UNALIGNED_STACK_POINTER: 9664bc09ffffd182
STACK_TEXT:
ffffcf02`cce26c08 fffff807`961e8c2b : 00000000`0000001e ffffffff`c0000005 00000000`00000001 00000000`00000000 : nt!KeBugCheckEx
ffffcf02`cce26c10 fffff807`964bee45 : ffffd182`0f72b700 ffffe50c`5196f3a0 ffffcf02`cce27654 00000000`00000000 : nt!KiDispatchException+0x91b
ffffcf02`cce27300 fffff807`964b9b25 : ffffd182`00000001 ffffd182`165fc930 00000000`000000c9 00000000`00000000 : nt!KiExceptionDispatch+0x145
ffffcf02`cce274e0 00000000`00000001 : fffff807`9668ed7c ffffd182`202e5900 ffffcf02`00000001 00000000`00020000 : nt!KiGeneralProtectionFault+0x365
ffffcf02`cce27678 fffff807`9668ed7c : ffffd182`202e5900 ffffcf02`00000001 00000000`00020000 7fffffff`00000000 : 0x1
ffffcf02`cce27680 fffff807`968306fe : ffffd182`165fc970 fffff807`9664bc09 00000000`00000000 ffffcf02`cce27970 : nt!AlpcpSendMessage+0x56c
ffffcf02`cce277d0 fffff807`9664a2be : ffffd182`1fcdf5f0 00000000`00020000 000001cc`4a63a0c0 000001cc`521caa88 : nt!AlpcpProcessSynchronousRequest+0x232
ffffcf02`cce278e0 fffff807`964be355 : ffffcf02`cce27aa0 ffffd182`202e5080 0000000c`6512ecf8 fffff807`9614a8ed : nt!NtAlpcSendWaitReceivePort+0x1fe
ffffcf02`cce279b0 00007ffe`a3202c44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000000c`6512ecd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a3202c44
SYMBOL_NAME: nt!KiDispatchException+91b
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.26100.8036
STACK_COMMAND: .process /r /p 0xffffd1822042f080; .thread 0xffffd182202e5080 ; kb
BUCKET_ID_FUNC_OFFSET: 91b
FAILURE_BUCKET_ID: AV_nt!KiDispatchException
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {00781d15-b897-afab-75cd-f83221cbf387}
Followup: MachineOwner2-3-4 hataları tıpatıp aynı. Senin NVIDIA sürücüsü patlamış. RAM testi bitince @stormhawks47 hocanın üstteki mesajda dediğini yapacaksın.
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804437ca49e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Page.Virtual
Value: 0xffffffffffff0000
Key : AV.Type
Value: Read
Key : Analysis.CPU.mSec
Value: 5062
Key : Analysis.Elapsed.mSec
Value: 29524
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 7
Key : Analysis.Init.CPU.mSec
Value: 953
Key : Analysis.Init.Elapsed.mSec
Value: 7104
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2511.5.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_nvlddmkm!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff804437ca49e
Key : Failure.Exception.IP.Module
Value: nvlddmkm
Key : Failure.Exception.IP.Offset
Value: 0x6ca49e
Key : Failure.Hash
Value: {7eea5677-f68d-2154-717e-887e07e55cd3}
Key : Faulting.IP.Type
Value: Paged
Key : Stack.Pointer
Value: PRCBException
Key : WER.System.BIOSRevision
Value: 6.8.0.0
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff804437ca49e
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
FILE_IN_CAB: 032726-8890-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: fffff80497bd15c0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff80497bc44c8: 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
ffffffffffffffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
IP_IN_PAGED_CODE:
nvlddmkm+6ca49e
fffff804`437ca49e 83780800 cmp dword ptr [rax+8],0
STACK_TEXT:
fffff804`2963e0e8 fffff804`971b0ee6 : 00000000`0000001e ffffffff`c0000005 fffff804`437ca49e 00000000`00000000 : nt!KeBugCheckEx
fffff804`2963e0f0 fffff804`972b42cf : fffff804`2963e8f0 00000000`00000000 fffff804`2963e1c0 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
fffff804`2963e130 fffff804`96e7c492 : fffff804`2963e1c0 fffff804`96c00000 fffff804`972abcce fffff804`96d16638 : nt!RtlpExecuteHandlerForException+0xf
fffff804`2963e160 fffff804`96fe866f : fffff804`2963e8f0 fffff804`2963edf0 fffff804`2963e8f0 fffff804`296252c0 : nt!RtlDispatchException+0x2d2
fffff804`2963e8c0 fffff804`972aaef2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x35f
fffff804`2963efb0 fffff804`972aaec0 : fffff804`972bee3e 00000000`000000b4 00000000`00000000 ffffd18d`87130000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff804`296252b8 fffff804`972bee3e : 00000000`000000b4 00000000`00000000 ffffd18d`87130000 ffff93a4`97193b71 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff804`296252c0 fffff804`972b9b25 : ffffd18d`87135000 00000000`00000000 fffff804`296256c0 fffff804`43c3c6cd : nt!KiExceptionDispatch+0x13e
fffff804`296254a0 fffff804`437ca49e : 00000000`00000000 00000000`00000000 ffffd18d`8714f000 ffffd18d`8713f000 : nt!KiGeneralProtectionFault+0x365
fffff804`29625630 00000000`00000000 : 00000000`00000000 ffffd18d`8714f000 ffffd18d`8713f000 00000000`0000000a : nvlddmkm+0x6ca49e
SYMBOL_NAME: nvlddmkm+6ca49e
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xfffff80497bcef00; .thread 0xfffff80497bd15c0 ; kb
BUCKET_ID_FUNC_OFFSET: 6ca49e
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
Followup: MachineOwnerHata 5: MEMORY_MANAGEMENT (ntkrnlmp.exe)
Kod:
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: ffffd40003ca30e0
Arg3: 0000000000000001
Arg4: 0000000000000002
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3125
Key : Analysis.Elapsed.mSec
Value: 12096
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 4
Key : Analysis.Init.CPU.mSec
Value: 1031
Key : Analysis.Init.Elapsed.mSec
Value: 9582
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2511.5.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Bugcheck.Code.TargetModel
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x1a_41790_nt!MiReducePteUseCount
Key : Failure.Hash
Value: {c5aab5ce-7a8e-3052-dfbf-a488d4fe7bce}
Key : WER.System.BIOSRevision
Value: 6.8.0.0
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41790
BUGCHECK_P2: ffffd40003ca30e0
BUGCHECK_P3: 1
BUGCHECK_P4: 2
FILE_IN_CAB: 032726-8796-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffc004f1bde0c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: WerFaultSecure
STACK_TEXT:
ffff938e`0b7ff368 fffff801`ed212b22 : 00000000`0000001a 00000000`00041790 ffffd400`03ca30e0 00000000`00000001 : nt!KeBugCheckEx
ffff938e`0b7ff370 fffff801`ed2dbeaa : ffff938e`0b7ff610 00000000`00000000 fffff801`ed2e3cf0 00000000`00000000 : nt!MiReducePteUseCount+0x202
ffff938e`0b7ff3b0 fffff801`ed2da9b4 : ffff938e`0b7ff550 fffff801`ed2bb00e ffffc004`00000082 ffffc004`f1b134c0 : nt!MiDecommitPagesTail+0x36
ffff938e`0b7ff3e0 fffff801`ed3cc38a : 00000000`00000000 ffffc004`00000000 ffff938e`00000082 ffffffff`ffffffff : nt!MiDeleteVaDirect+0x6b4
ffff938e`0b7ff500 fffff801`ed3cc1ab : 000001ed`8633dfff fffff801`ed2b95c2 ffffc004`f1bde0c0 00000000`00000000 : nt!MiDeletePagablePteRange+0x1b6
ffff938e`0b7ff7c0 fffff801`ed8e54f8 : 00000000`00000000 ffff938e`0b7ff880 00000000`00000000 fffff801`ed8e69ab : nt!MiDeleteVirtualAddresses+0x4b
ffff938e`0b7ff810 fffff801`ed8e52c9 : ffffc004`f1b130c0 ffffc004`f6544240 000001ed`00000000 00000000`00000000 : nt!MiDeleteVad+0x168
ffff938e`0b7ff8c0 fffff801`ed8e4f4a : ffffc004`f6544240 ffff938e`0b7ff969 ffffc004`e31c02f0 000001ed`861f0000 : nt!MiUnmapVad+0x49
ffff938e`0b7ff8f0 fffff801`ed8e4cef : ffffffff`ffffffff 00000000`00000008 ffffc004`dc6c6ba0 000001ed`861f0000 : nt!MiUnmapViewOfSection+0x146
ffff938e`0b7ff9d0 fffff801`ed6be355 : 00000000`00000000 00000000`00000000 ffffc004`f1b130c0 00000064`7b6ef130 : nt!NtUnmapViewOfSection+0x7f
ffff938e`0b7ffa20 00007ff9`57801fd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000064`7b6eec58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`57801fd4
SYMBOL_NAME: nt!MiReducePteUseCount+202
MODULE_NAME: nt
IMAGE_VERSION: 10.0.26100.8036
STACK_COMMAND: .process /r /p 0xffffc004f1b130c0; .thread 0xffffc004f1bde0c0 ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 202
FAILURE_BUCKET_ID: 0x1a_41790_nt!MiReducePteUseCount
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c5aab5ce-7a8e-3052-dfbf-a488d4fe7bce}
Followup: MachineOwnerHata 6: (ntkrlmp.exe)
Kod:
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000404, The subtype of the BugCheck.
Arg2: ffff910145be5a18
Arg3: 80000005043e7867
Arg4: ffff910145be5218
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2937
Key : Analysis.Elapsed.mSec
Value: 10600
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 9606
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2511.5.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Bugcheck.Code.TargetModel
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x1a_404_nt!MiDecommitPrivatePageTail
Key : Failure.Hash
Value: {9f2242b3-781c-bce3-02c4-26d76a23f4ec}
Key : WER.System.BIOSRevision
Value: 6.8.0.0
BUGCHECK_CODE: 1a
BUGCHECK_P1: 404
BUGCHECK_P2: ffff910145be5a18
BUGCHECK_P3: 80000005043e7867
BUGCHECK_P4: ffff910145be5218
FILE_IN_CAB: 032826-5984-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffcf8f81d8f080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: powershell.exe
STACK_TEXT:
ffff9186`29e00148 fffff805`936f2597 : 00000000`0000001a 00000000`00000404 ffff9101`45be5a18 80000005`043e7867 : nt!KeBugCheckEx
ffff9186`29e00150 fffff805`936f2013 : ffffcf8f`71655180 ffffef6b`67c1be23 00000000`00000000 80000003`957e5867 : nt!MiDecommitPrivatePageTail+0x357
ffff9186`29e00200 fffff805`934dbee2 : ffff9186`29e004f0 fffff805`00000003 ffffcf8f`00000003 00000000`00000080 : nt!MiDecommitFreePagesTail+0x2b3
ffff9186`29e00290 fffff805`934da9b4 : ffff9186`29e00430 0000028b`7c689000 00000000`00000080 ffffcf8f`794ba480 : nt!MiDecommitPagesTail+0x6e
ffff9186`29e002c0 fffff805`935cc38a : 00000000`00000000 ffffcf8f`00000000 ffff9186`00000080 ffffffff`ffffffff : nt!MiDeleteVaDirect+0x6b4
ffff9186`29e003e0 fffff805`935cc1ab : 0000028b`7cb4ffff fffff805`934b95c2 ffffcf8f`81d8f080 00000000`00000000 : nt!MiDeletePagablePteRange+0x1b6
ffff9186`29e006a0 fffff805`93ae54f8 : 00000000`00000000 ffff9186`29e00760 00000000`00000000 ffff9101`00000003 : nt!MiDeleteVirtualAddresses+0x4b
ffff9186`29e006f0 fffff805`935cdc8c : ffffcf8f`794ba080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x168
ffff9186`29e007a0 fffff805`93adbe61 : ffff9186`00000000 00000000`00000000 00000000`28b7cb40 fffff805`934fdc88 : nt!MiFreeVadRange+0xb4
ffff9186`29e00800 fffff805`93adba4b : ffffcf8f`794ba080 00000000`00000000 ffff9186`00008000 fffff805`00000000 : nt!MiFreeVirtualMemory+0x229
ffff9186`29e00890 fffff805`93adb86d : fffff805`20a5b180 fffff805`9354a8ed 00000000`00000000 000000e2`0167e620 : nt!MmFreeVirtualMemory+0x1ab
ffff9186`29e009c0 fffff805`938be355 : ffffcf8f`81d8f080 00000000`00000000 ffffcf8f`81d8f080 00000000`00000000 : nt!NtFreeVirtualMemory+0x8d
ffff9186`29e00a20 00007ff9`328e1e54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000e2`0167e5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`328e1e54
SYMBOL_NAME: nt!MiDecommitPrivatePageTail+357
MODULE_NAME: nt
IMAGE_VERSION: 10.0.26100.8036
STACK_COMMAND: .process /r /p 0xffffcf8f794ba080; .thread 0xffffcf8f81d8f080 ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 357
FAILURE_BUCKET_ID: 0x1a_404_nt!MiDecommitPrivatePageTail
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9f2242b3-781c-bce3-02c4-26d76a23f4ec}
Followup: MachineOwnerŞimdi senin hatalar RAM ve ekran kartı sürücüsü ile ilgili. EXPO/XMP kapat. Sürücüleri kaldırıp yeniden kur.
Son düzenleme:
nvidia driverını ddu ile sildim internetim olmadan sitesinden önceden indirdiğim(öncekinde app ile yüklemiştim) 595.97 sürümünü yükledim yukarıdaki yeni bir hata şimdi bilgisayarı teste bırakıyorum ram için sabah sonuçları paylaşıcam
özel ilginiz için teşekkürler @31988
ddu bilgisi için teşekkürler @stormhawks47
DPC_WATCHDOG_VIOLATION (ntkrnlmp.exe)
Genel olarak ekran kartı sürücüsü ve RAM sorunu.
Genel olarak ekran kartı sürücüsü ve RAM sorunu.
Kod:
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff803ab7c43b8, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2953
Key : Analysis.Elapsed.mSec
Value: 6812
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 1031
Key : Analysis.Init.Elapsed.mSec
Value: 16208
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2511.5.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Bugcheck.Code.TargetModel
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x133_ISR_nt!KeAccumulateTicks
Key : Failure.Hash
Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Key : Stack.Pointer
Value: ISR
Key : WER.System.BIOSRevision
Value: 30.2.0.0
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff803ab7c43b8
BUGCHECK_P4: 0
FILE_IN_CAB: 032826-11000-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffff838f87be5080
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: CrashMailer_64
STACK_TEXT:
ffffa700`b627a998 fffff803`aaa9c95c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`ab7c43b8 : nt!KeBugCheckEx
ffffa700`b627a9a0 fffff803`aaa9be8b : 00000000`00000000 00000000`00007891 00000000`00000000 ffffa700`b6280180 : nt!KeAccumulateTicks+0x59c
ffffa700`b627aa10 fffff803`aaa9bb40 : 00000000`0000000e ffffa700`b5a02300 00000000`00007892 ffffa700`b627acd0 : nt!KiUpdateRunTime+0x9b
ffffa700`b627abd0 fffff803`aab3a86a : 00000000`00000000 fffff803`ab721278 ffffa700`b6280180 fffff803`3c1f12c0 : nt!KiUpdateTime+0x380
ffffa700`b627ae40 fffff803`aab3b3cc : ffff838f`497745a0 ffff838f`49774650 fffff803`ab78ee98 00000000`00060001 : nt!KeClockInterruptNotify+0x28a
ffffa700`b627af40 fffff803`aaeace3e : 00000000`00000002 ffff838f`497745a0 000001f2`b8877296 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffffa700`b627afb0 fffff803`aaead64c : 00000001`1f91752b ffffb788`a9a16540 00000001`1f917531 000001d6`380bd385 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffb788`a9a164c0 fffff803`aaa22969 : 00000000`00000000 00000000`00679790 ffffd20c`0007d470 00000000`00037615 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffb788`a9a16650 fffff803`aac2f97e : 00000000`00679790 ffffd200`00000001 ffffd200`136c6b18 00000000`00000000 : nt!MiInsertPageInFreeOrZeroedList+0x759
ffffb788`a9a167c0 fffff803`aaaf649c : ffffd20c`00004300 00000000`00460000 ffffd200`136c2900 00000000`00000002 : nt!MiInsertDemotedPages+0x1d2
ffffb788`a9a16850 fffff803`aaaf76cc : 00000000`00033401 00000000`00000000 00000000`00000000 00000000`00033401 : nt!MiDemoteLocalLargePage+0x47c
ffffb788`a9a16900 fffff803`aaaf4f5a : 00000000`00000005 ffffb788`a9a16a50 00000000`000600a3 00000000`00000001 : nt!MiGetFreeOrZeroPageAnyColor+0x114
ffffb788`a9a16950 fffff803`aaaf370c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00033411 : nt!MiGetPage+0xdaa
ffffb788`a9a16aa0 fffff803`aaaf33d8 : fffff62b`00450000 00000000`00000000 ffffb788`a9a16cf0 ffffb788`a9a16e80 : nt!MiGetLargePage+0x16c
ffffb788`a9a16bf0 fffff803`aaafd223 : ffffb788`80000004 ffff838f`86cb4480 00000000`00000039 00000000`00000080 : nt!MiGetLargePagesForChain+0xf8
ffffb788`a9a16d60 fffff803`aaafe691 : ffff838f`86cdc301 00000000`00000000 ffffb788`a9a16f10 ffffb788`a9a17230 : nt!MiGetPageChain+0x463
ffffb788`a9a16e10 fffff803`aaafeeb3 : ffff838f`00000009 00000000`00000000 ffffffff`ffffffff ffff838f`86cb4480 : nt!MiResolvePrivateZeroFault+0x621
ffffb788`a9a16fd0 fffff803`aaafd9b9 : ffffb788`a9a17190 ffffb788`a9a17150 ffffb788`a9a17158 ffffb788`a9a17168 : nt!MiZeroFault+0x463
ffffb788`a9a170c0 fffff803`aaa1695e : 00000000`05560001 ffff8000`00000018 00000236`2ea20000 00000000`00000000 : nt!MiUserFault+0x459
ffffb788`a9a17150 fffff803`aaeb9ecb : ffffb788`00000000 fffff803`aaa1d899 00000000`00082000 00000000`0000eed0 : nt!MmAccessFault+0x20e
ffffb788`a9a172c0 fffff803`ab0c05d0 : fffff803`ab638c00 00000000`004f2930 ffffa700`b6280180 00000000`000000ed : nt!KiPageFault+0x38b
ffffb788`a9a17450 fffff803`ab2dc397 : ffffb788`a9a174e1 ffffa700`b6280180 fffff803`ab638c00 fffff3d2`80284000 : nt!ProbeForWrite+0x40
ffffb788`a9a17480 fffff803`ab2e1061 : 00000000`00000001 00000236`00000000 00000000`00000068 00000000`00010000 : nt!ExpQuerySystemInformation+0x157
ffffb788`a9a179e0 fffff803`aaebe355 : ffff838f`87be0000 ffff838f`87be5080 ffff838f`87be5080 000000c6`6733c188 : nt!NtQuerySystemInformation+0x91
ffffb788`a9a17a20 00007ff9`358a2154 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000c6`6733c088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`358a2154
SYMBOL_NAME: nt!KeAccumulateTicks+59c
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.26100.8036
STACK_COMMAND: .process /r /p 0xffff838f86cb4080; .thread 0xffff838f87be5080 ; kb
BUCKET_ID_FUNC_OFFSET: 59c
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner- Katılım
- 20 Aralık 2023
- Mesajlar
- 3.232
- Çözümler
- 26
- Beğeniler
- 1.908
dediğiniz gibi yapıcam ram problemleri sonrası
Sol altta "Time" ilerliyor mu?
ilerlemiyordu. 2 ramin yerini değiştirip exp açmayı denedim açıldı şu an windowsu açtım bir 30 dkdır test yapıyorum problem kalmadı
nvidia problemlerinide düzgün şekilde kurdum şimdilik problem çekmiyorum
Benzer konular
Yeni konular
-
1.000 TL'ye kadar bilgisayar masası için ayak destek ünitesi önerisi- Michael MYERS
- Mesaj: 0
-
-
-
-
-
-
-
