Hocam XMP nasıl kapatılıyor? Bilgisizliğim affolaAynı hatayı XMP kapatarak düzeltmiştim. Sürücülerden de kaynaklı olabilir.
Hocam XMP nasıl kapatılıyor? Bilgisizliğim affola
*******************************************************************************
* *
* 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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff8027211dd16, The address that the exception occurred at
Arg3: ffff830dfa305a30, Parameter 0 of the exception
Arg4: 000000000000005a, 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: Check Image - Checksum mismatch - Dump: 0x3a6c09, File: 0x3b2d78 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\6DD22F2D3aa000\dxgkrnl.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1296
Key : Analysis.Elapsed.mSec
Value: 11494
Key : Analysis.IO.Other.Mb
Value: 17
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 22
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 22164
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Failure.Bucket
Value: 0x1E_C0000094_nt!PpmPerfSelectProcessorState
Key : Failure.Hash
Value: {bde8e2c9-df0d-be8a-6751-181f4d2268d0}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000094
BUGCHECK_P2: fffff8027211dd16
BUGCHECK_P3: ffff830dfa305a30
BUGCHECK_P4: 5a
FILE_IN_CAB: 081924-7671-01.dmp
FAULTING_THREAD: ffff830e007b32c0
EXCEPTION_PARAMETER1: ffff830dfa305a30
EXCEPTION_PARAMETER2: 000000000000005a
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: CompatTelRunner.exe
STACK_TEXT:
fffff802`76e89158 fffff802`722fb19e : 00000000`0000001e ffffffff`c0000094 fffff802`7211dd16 ffff830d`fa305a30 : nt!KeBugCheckEx
fffff802`76e89160 fffff802`72207fb2 : fffff802`722fb17c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff802`76e891a0 fffff802`720ab207 : fffff802`76e89710 00000000`00000000 fffff802`76e7bfb0 fffff802`72205d75 : nt!RtlpExecuteHandlerForException+0x12
fffff802`76e891d0 fffff802`721394f6 : fffff802`76e7b7b8 fffff802`76e89e20 fffff802`76e7b7b8 00000000`00000064 : nt!RtlDispatchException+0x297
fffff802`76e898f0 fffff802`721fe822 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff802`76e89fb0 fffff802`721fe7f0 : fffff802`72211be5 00000000`00000000 fffff802`87fba0f0 ffff830d`fc68e602 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff802`76e7b678 fffff802`72211be5 : 00000000`00000000 fffff802`87fba0f0 ffff830d`fc68e602 fffff802`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff802`76e7b680 fffff802`72209e04 : ffff830d`fc68e6c8 fffff802`7db7b282 00000000`000c098c fffff802`72042bb4 : nt!KiExceptionDispatch+0x125
fffff802`76e7b860 fffff802`7211dd16 : fffff802`6f12a2e8 fffff802`76e7baa9 fffff802`72a1ed88 00000000`00000000 : nt!KiDivideErrorFault+0x304
fffff802`76e7b9f0 fffff802`7211db3e : 000001d3`9b6f8600 00000000`00000001 fffff802`72afc4f0 ffff830d`faac89e0 : nt!PpmPerfSelectProcessorState+0x1a6
fffff802`76e7bb10 fffff802`720b41b0 : fffff802`6f125240 fffff802`76e7be90 fffff802`76e7bcb0 fffff802`76e7be90 : nt!PpmPerfSelectProcessorStates+0x5e
fffff802`76e7bb40 fffff802`720c166e : fffff802`6f125240 ffff830d`f87d7000 fffff802`76e7be70 fffff802`00000002 : nt!PpmCheckRun+0x40
fffff802`76e7bbb0 fffff802`720c0954 : fffff802`6f122180 00000000`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30e
fffff802`76e7bd20 fffff802`72205d75 : 00000000`00000000 fffff802`6f122180 00000000`00000000 0000013e`a878bfd0 : nt!KiRetireDpcList+0x1f4
fffff802`76e7bfb0 fffff802`72205b60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffba08`bdd64ad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
SYMBOL_NAME: nt!PpmPerfSelectProcessorState+1a6
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.3803
STACK_COMMAND: .process /r /p 0xffff830dfdf72080; .thread 0xffff830e007b32c0 ; kb
BUCKET_ID_FUNC_OFFSET: 1a6
FAILURE_BUCKET_ID: 0x1E_C0000094_nt!PpmPerfSelectProcessorState
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {bde8e2c9-df0d-be8a-6751-181f4d2268d0}
Followup: MachineOwner
---------
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133685737545114469
PnpEventInformation: 0
PnpEventInProgress : 0
PnpProblemCode : 21
PnpVetoType : 0
DeviceId : SWD\MSRRAS\MS_NDISWANBH
VetoString :Cihazımı HDD ile kullanırken Windows 10 kullanabiliyordum. SSD taktığımdan beri mavi ekran çıkıyor. Sizin dediğinize göre daha önce de kullanamamış olmam gerekiyor ama HDD ile 4 sene boyunca Windows 10 kullandım.Cihazınızın Windows 10 veya üstüyle yeterli uyumluluğa sahip olmadığını görmek çok da zor değil. Ağ sürücüsü yanında birçok şey patlak vermiş. En mantıklı çözüm yolu cihazınızın desteklediği Windows 8.1'e geçiş yapmak olacaktır. Hem stabil bir işletim sistemi, Windows 10 ve 11'de hâlâ saçma hatalarla karşılaşıyoruz.
Yine de denemek isterseniz GPU ve ağ sürücülerini güncellemeniz işe yarayabilir.
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: ffffffffc0000094, The exception code that was not handled Arg2: fffff8027211dd16, The address that the exception occurred at Arg3: ffff830dfa305a30, Parameter 0 of the exception Arg4: 000000000000005a, 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: Check Image - Checksum mismatch - Dump: 0x3a6c09, File: 0x3b2d78 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\6DD22F2D3aa000\dxgkrnl.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1296 Key : Analysis.Elapsed.mSec Value: 11494 Key : Analysis.IO.Other.Mb Value: 17 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 22 Key : Analysis.Init.CPU.mSec Value: 171 Key : Analysis.Init.Elapsed.mSec Value: 22164 Key : Analysis.Memory.CommitPeak.Mb Value: 82 Key : Bugcheck.Code.LegacyAPI Value: 0x1e Key : Bugcheck.Code.TargetModel Value: 0x1e Key : Failure.Bucket Value: 0x1E_C0000094_nt!PpmPerfSelectProcessorState Key : Failure.Hash Value: {bde8e2c9-df0d-be8a-6751-181f4d2268d0} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc0000094 BUGCHECK_P2: fffff8027211dd16 BUGCHECK_P3: ffff830dfa305a30 BUGCHECK_P4: 5a FILE_IN_CAB: 081924-7671-01.dmp FAULTING_THREAD: ffff830e007b32c0 EXCEPTION_PARAMETER1: ffff830dfa305a30 EXCEPTION_PARAMETER2: 000000000000005a BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: CompatTelRunner.exe STACK_TEXT: fffff802`76e89158 fffff802`722fb19e : 00000000`0000001e ffffffff`c0000094 fffff802`7211dd16 ffff830d`fa305a30 : nt!KeBugCheckEx fffff802`76e89160 fffff802`72207fb2 : fffff802`722fb17c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22 fffff802`76e891a0 fffff802`720ab207 : fffff802`76e89710 00000000`00000000 fffff802`76e7bfb0 fffff802`72205d75 : nt!RtlpExecuteHandlerForException+0x12 fffff802`76e891d0 fffff802`721394f6 : fffff802`76e7b7b8 fffff802`76e89e20 fffff802`76e7b7b8 00000000`00000064 : nt!RtlDispatchException+0x297 fffff802`76e898f0 fffff802`721fe822 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186 fffff802`76e89fb0 fffff802`721fe7f0 : fffff802`72211be5 00000000`00000000 fffff802`87fba0f0 ffff830d`fc68e602 : nt!KxExceptionDispatchOnExceptionStack+0x12 fffff802`76e7b678 fffff802`72211be5 : 00000000`00000000 fffff802`87fba0f0 ffff830d`fc68e602 fffff802`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue fffff802`76e7b680 fffff802`72209e04 : ffff830d`fc68e6c8 fffff802`7db7b282 00000000`000c098c fffff802`72042bb4 : nt!KiExceptionDispatch+0x125 fffff802`76e7b860 fffff802`7211dd16 : fffff802`6f12a2e8 fffff802`76e7baa9 fffff802`72a1ed88 00000000`00000000 : nt!KiDivideErrorFault+0x304 fffff802`76e7b9f0 fffff802`7211db3e : 000001d3`9b6f8600 00000000`00000001 fffff802`72afc4f0 ffff830d`faac89e0 : nt!PpmPerfSelectProcessorState+0x1a6 fffff802`76e7bb10 fffff802`720b41b0 : fffff802`6f125240 fffff802`76e7be90 fffff802`76e7bcb0 fffff802`76e7be90 : nt!PpmPerfSelectProcessorStates+0x5e fffff802`76e7bb40 fffff802`720c166e : fffff802`6f125240 ffff830d`f87d7000 fffff802`76e7be70 fffff802`00000002 : nt!PpmCheckRun+0x40 fffff802`76e7bbb0 fffff802`720c0954 : fffff802`6f122180 00000000`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30e fffff802`76e7bd20 fffff802`72205d75 : 00000000`00000000 fffff802`6f122180 00000000`00000000 0000013e`a878bfd0 : nt!KiRetireDpcList+0x1f4 fffff802`76e7bfb0 fffff802`72205b60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 ffffba08`bdd64ad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue SYMBOL_NAME: nt!PpmPerfSelectProcessorState+1a6 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.3803 STACK_COMMAND: .process /r /p 0xffff830dfdf72080; .thread 0xffff830e007b32c0 ; kb BUCKET_ID_FUNC_OFFSET: 1a6 FAILURE_BUCKET_ID: 0x1E_C0000094_nt!PpmPerfSelectProcessorState OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {bde8e2c9-df0d-be8a-6751-181f4d2268d0} Followup: MachineOwner --------- PnpActivityId : {00000000-0000-0000-0000-000000000000} PnpActivityTime : 133685737545114469 PnpEventInformation: 0 PnpEventInProgress : 0 PnpProblemCode : 21 PnpVetoType : 0 DeviceId : SWD\MSRRAS\MS_NDISWANBH VetoString :
Hocam cihazımda XMP ayarı yok maalesef.
Cihazımı HDD ile kullanırken Windows 10 kullanabiliyordum. SSD taktığımdan beri mavi ekran çıkıyor. Sizin dediğinize göre daha önce de kullanamamış olmam gerekiyor ama HDD ile 4 sene boyunca Windows 10 kullandım.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?