1: kd> k
# Child-SP RetAddr Call Site
00 ffffc388`4ce3e578 fffff807`66e53c4b amdppm!ReadIoMemRaw+0x5b
01 ffffc388`4ce3e580 fffff807`66e59b37 amdppm!ReadGenAddr+0x1f
02 ffffc388`4ce3e5b0 fffff807`66e518d3 amdppm!C2Idle+0x87
03 ffffc388`4ce3e5e0 fffff807`47ae15cf amdppm!AcpiCStateIdleExecute+0x23
04 ffffc388`4ce3e610 fffff807`47ae114b nt!PpmIdleExecuteTransition+0x41f
05 ffffc388`4ce3ea50 fffff807`47c1d034 nt!PoIdle+0x68b
06 ffffc388`4ce3ec40 00000000`00000000 nt!KiIdleLoop+0x541: kd> r if
if=0 <<
1: kd> !irql
Debugger saved IRQL for processor 0x1 -- 0 (LOW_LEVEL) <<x86 işlemcileri gibi bazı sistemlerde iş parçacığı düzeyinde C durumlarının da mevcut olduğu bir gerçek ancak, her bir iş parçacığı daha yüksek C durumları talep edebilirken, herhangi bir güç tasarrufu eylemi yalnızca çekirdek C durumu (CC durumu) çözüldükten sonra gerçekleştirilir. Çekirdek C durumu, en düşük iş parçacığı durumu tarafından belirlenir:
14: kd> k
# Child-SP RetAddr Call Site
00 ffffc388`4d595448 fffff807`47c2dc29 nt!KeBugCheckEx
01 ffffc388`4d595450 fffff807`47c29134 nt!KiBugCheckDispatch+0x69
02 ffffc388`4d595590 00000000`00000001 nt!KiPageFault+0x474
*** WARNING: Unable to verify timestamp for rtwlane_13.sys
03 ffffc388`4d595728 00000000`00000000 afd!AfdTLBufferedSendCompleteBatch
04 ffffc3884d595a78 fffff8074a9d0429 NETIO!NetioPhChecksumIpDatagramWithInitialChecksum+0x69rtwlane_13.sys yani, Realtek PCIEWireless LAN PCI-E NIC hata vermiş. Sürücüsü de bayağı, bayağı eski.nt!MiCleanVad çağrısını görüyorsun ki bu çağrıların görevi sanal bellekteki adresleri fiziksel bellekteki adreslere eşlemek kısmında görev almalarıdır. Ardından farklı bir noktada bu adres alanı için sayfa tablolarını silen nt!MiDeletePagablePteRange çağrısını görüyorsun. Daha sonra adres alanını silmek için başka bir çağrı, ardından adres alanını silmek için son bir çağrı ve ardından mavi ekrana neden olan hata kontrolünü görüyorsun.14: kd> k
# Child-SP RetAddr Call Site
00 ffff8107`bc909018 fffff807`6ec95e79 nt!KeBugCheckEx
01 ffff8107`bc909020 fffff807`6ec8e95e nt!MiDeletePteRun+0x17b9
02 ffff8107`bc909230 fffff807`6ec89f2b nt!MiDeleteVaTail+0x6e
03 ffff8107`bc909260 fffff807`6ec33920 nt!MiDeletePagablePteRange+0x4ab
04 ffff8107`bc909570 fffff807`6f05dd3b nt!MiDeleteVad+0x360
05 ffff8107`bc909680 fffff807`6f05c19f nt!MiCleanVad+0x43
06 ffff8107`bc9096b0 fffff807`6f085ef8 nt!MmCleanProcessAddressSpace+0x137
07 ffff8107`bc909730 fffff807`6f08da4e nt!PspRundownSingleProcess+0x20c
08 ffff8107`bc9097c0 fffff807`6f107f48 nt!PspExitThread+0x5f6
09 ffff8107`bc9098c0 fffff807`6ecc872d nt!KiSchedulerApcTerminate+0x38
0a ffff8107`bc909900 fffff807`6ee02ee0 nt!KiDeliverApc+0x60d
0b ffff8107`bc9099c0 fffff807`6ee1161f nt!KiInitiateUserApc+0x70
0c ffff8107`bc909b00 00007ffc`8838d064 nt!KiSystemServiceExit+0x9f
0d 000000e0`131cf678 00000000`00000000 0x00007ffc`8838d064Bu durumda yaptığın şey yanlış, AM4 işlemcilerin 4 RAM'i Dual channel ayarına aldıkları bilinen bir gerçek. Senin bu RAM'leri OC sınırının altına getirip sistemi kontrol etmen gerekiyor. Bu da 2666 MHz altına tekabül ediyor.
Bu da yanlış bir düşünce, Anakart desteklediği sürece istenilen hızlara çıkılabilir. RAM çiplerin /B Dıe vs./ ve işlemcindeki bellek kontrolcüsü gibi türlü türlü etkenler daha önemlidir bu noktada.
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: fffff80028f50b84, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : Analysis.CPU.mSec
Value: 2515
Key : Analysis.Elapsed.mSec
Value: 6602
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 281
Key : Analysis.Init.Elapsed.mSec
Value: 2738
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Dump.Attributes.AsUlong
Value: 1008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
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_R_nt!Feature_MultiCoreClasses__private_IsEnabledPreCheck
Key : Failure.Hash
Value: {0b4bb673-14d9-f739-3c47-1ac3ce229608}
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80028f50b84
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
FILE_IN_CAB: 032524-5296-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff8002991c470: 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
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: steamwebhelper
STACK_TEXT:
ffffbd00`e2e210e8 fffff800`29146f5a : 00000000`0000001e ffffffff`c0000005 fffff800`28f50b84 00000000`00000000 : nt!KeBugCheckEx
ffffbd00`e2e210f0 fffff800`29022da2 : ffffbd00`e2e21900 ffffbd00`e2e211c0 fffff800`28c00000 fffff800`29020f75 : nt!HvlpVtlCallExceptionHandler+0x22
ffffbd00`e2e21130 fffff800`28f562e3 : fffffb82`ecf48d00 fffffb82`ecf483d8 fffff800`29020f75 fffff800`28ceda40 : nt!RtlpExecuteHandlerForException+0x12
ffffbd00`e2e21160 fffff800`28ec295e : ffffffff`ffffffff fffffb82`ecf48480 fffffb82`ecf48480 ffffbd00`e2e21900 : nt!RtlDispatchException+0x2f3
ffffbd00`e2e218d0 fffff800`29018a12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1ae
ffffbd00`e2e21fb0 fffff800`290189e0 : fffff800`2902d475 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffb82`ecf48298 fffff800`2902d475 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffb82`ecf482a0 fffff800`29028383 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x135
fffffb82`ecf48480 fffff800`28f50b84 : ffffbd00`e2e00180 00000000`00000001 fffffb82`ecf48e00 fffff800`28f5279e : nt!KiGeneralProtectionFault+0x343
fffffb82`ecf48610 fffff800`28f5095b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!Feature_MultiCoreClasses__private_IsEnabledPreCheck+0x4
fffffb82`ecf48660 fffff800`28f4f2f0 : fffff800`257a0630 00000000`0000002e 00000000`00000000 00000000`0000006b : nt!PpmPerfSnapUtility+0x1bb
fffffb82`ecf48700 fffff800`28f0831b : 00000000`00000000 00000000`00000000 fffffb82`ecf48e00 00000000`000008f8 : nt!PpmCheckSnapAllUtility+0xb0
fffffb82`ecf48760 fffff800`28e251bc : 00000000`00000000 00000000`00000001 00000000`00000000 fffffb82`00000002 : nt!PpmCheckRun+0x3b
fffffb82`ecf487c0 fffff800`28e26471 : 00000000`00000020 ffffd38b`00000001 fffff780`00000014 00000000`0018a28c : nt!KiExecuteAllDpcs+0x42c
fffffb82`ecf48d00 fffff800`29020f75 : 00000000`00000000 00000000`00000000 ffffbd00`e2e00180 00000000`00000000 : nt!KiRetireDpcList+0x1b1
fffffb82`ecf48fb0 fffff800`29020f1f : fffffb82`f11a3a79 fffff800`28e29ef5 00007ffd`e14d2220 00000099`65fdf048 : nt!KxSwapStacksAndRetireDpcList+0x5
fffffb82`f11a39e0 fffff800`28e29ef5 : 00007ffd`e14d2220 00000099`65fdf048 00000099`65fdf048 00000099`65fdf04c : nt!KiPlatformSwapStacksAndCallReturn
fffffb82`f11a39f0 fffff800`29020340 : ffffd38b`65550080 00000099`65fdf048 fffffb82`f11a3af8 00000000`00000000 : nt!KiDispatchInterrupt+0xd5
fffffb82`f11a3ae0 00007ffd`e14d22d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x350
00000099`65fdf090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e14d22d4
SYMBOL_NAME: nt!Feature_MultiCoreClasses__private_IsEnabledPreCheck+4
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.3296
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 4
FAILURE_BUCKET_ID: AV_R_nt!Feature_MultiCoreClasses__private_IsEnabledPreCheck
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0b4bb673-14d9-f739-3c47-1ac3ce229608}
Followup: MachineOwner
PPM ile alakalı ibareler var. Çipset sürücülerini güncelle. İşlemciden kaynaklı olabilir.
WinDbg bunu beğenecek.
Teknoloji ne kadar da gelişmiş.Güncellemeyi yarıda bırak ve format at. Bir daha da Driver Booster kullanma.
Teşekkür ederim. Bilgilendirmeniz için ama driver booster geliştiricisini bu konularla alakalı 1 yıl önce iki yorumu oldu.WinDbg bunu beğenecek.
Güncellemeyi yarıda bırak ve format at. Bir daha da Driver Booster kullanma.
Driver Booster'ın bir sürü bilgisayarı arızalandırdığı gerçeği var. Sen bilirsin yine de.
