Son kullanma tarihi geçmiş, bayatlamış bir tarayıcı kullanıyorsanız, Mercedes kullanmak yerine tosbağaya binmek gibi... Web sitelerini düzgün görüntüleyemiyorsanız eh, bi' zahmet tarayıcınızı güncelleyiniz. Modern Web standartlarını karşılayan bir tarayıcı alternatifine göz atın.
ÇözüldüRTX 3060 Ti sistem minidump dosya incelemesi
Merhaba, az önce bir mavi ekran hatası aldım fakat hatayı tespit edemedim. Bana minidump dosyaları üzerinden yardımcı olabilir misiniz?
Benim için hastalığı tehşis etseniz olur mu? ) 071123-7843-01.dmp
Merhaba, 8 senelik laptopum ASUS X555ln modelinde yakın zamanda Windows 11 geçtim. Hiçbir sorun yoktu fakat son dönemde alakasız zamanlarda KMODE_EXCEPTION_NOT_HANDLED hatası alıyorum. Oyun oynarken de tarayıcıda dolaşırkende gelebiliyor bu hata. Minidump klasöründeki logları inceledim fakat pek...
www.technopat.net
* Disk düzeni GPT ise BIOS'a girin.
BIOS'ta Boot > CSM altında şu işaretlediğim 5 seçenekte sizde hangileri seçili?
Launch CSM = Enabled ise Disabled yapın. Kaydedin ve çıkın.
Boot Device Control kısmını da UEFI only yapın.
Genel önerilerim:
* BIOS eski kalmış.
* 3802 kullanıyorsunuz, 4002 sürümüne güncelleyin.
İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
PC açılınca yeni chipset sürücülerini kurun.
İnterneti bağlayabilirsiniz.
- Tüm bunlar sonucunda mavi ekran alırsanız yeni dökümleri paylaşın.
- Duruma göre Memtest86 ile RAM testi yapmanız gerekecek.
Döküm:
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: fffff80166aae745, 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 : Analysis.CPU.mSec
Value: 1875
Key : Analysis.Elapsed.mSec
Value: 2196
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: 140
Key : Analysis.Init.Elapsed.mSec
Value: 5864
Key : Analysis.Memory.CommitPeak.Mb
Value: 146
Key : Bugcheck.Code.LegacyAPI
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!HvpGetCellContextInitialize
Key : Failure.Hash
Value: {b5ba24f1-6e18-e00f-aeac-aa92a7f9092d}
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80166aae745
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
FILE_IN_CAB: 071123-7843-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff8016711c468: 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: AmpliTube 5.ex
STACK_TEXT:
ffff9002`41676408 fffff801`668cfbf7 : 00000000`0000001e ffffffff`c0000005 fffff801`66aae745 00000000`00000000 : nt!KeBugCheckEx
ffff9002`41676410 fffff801`668443fc : ffff9002`41676d40 00000000`02000000 00000000`00000000 ffffbd08`f2bf6ec4 : nt!KiDispatchException+0x1bb1d7
ffff9002`41676af0 fffff801`6683f483 : 00000000`00000000 ffffad08`ec0f07ec 00000000`00060000 00000000`00000001 : nt!KiExceptionDispatch+0x13c
ffff9002`41676cd0 fffff801`66aae745 : ff7ff801`66aab4ff ffffbd08`f280b930 00000000`81c37ddb 00000000`00000001 : nt!KiGeneralProtectionFault+0x343
ffff9002`41676e68 ff7ff801`66aab4ff : ffffbd08`f280b930 00000000`81c37ddb 00000000`00000001 fffff801`66adec13 : nt!HvpGetCellContextInitialize+0x19
ffff9002`41676e70 ffffbd08`f280b930 : 00000000`81c37ddb 00000000`00000001 fffff801`66adec13 00000000`00000000 : 0xff7ff801`66aab4ff
ffff9002`41676e78 00000000`81c37ddb : 00000000`00000001 fffff801`66adec13 00000000`00000000 00000000`00000000 : 0xffffbd08`f280b930
ffff9002`41676e80 00000000`00000001 : fffff801`66adec13 00000000`00000000 00000000`00000000 00000000`00000000 : 0x81c37ddb
ffff9002`41676e88 fffff801`66adec13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`ffffffff : 0x1
ffff9002`41676e90 fffff801`66aaf814 : ffff9002`41677000 ffff9002`41677120 ffffbd09`076d9bc0 ffffad09`032721e0 : nt!CmpDoWritethroughReparse+0x33
ffff9002`41676f00 fffff801`66ab4375 : ad0901d7`0000001c ffff9002`41677430 ffff9002`416773b8 00000000`00000000 : nt!CmpDoParseKey+0xbc4
ffff9002`41677340 fffff801`66ab891b : fffff801`66ab4001 ffffad08`00000000 ffffad09`032721e0 00000000`00000001 : nt!CmpParseKey+0x2e5
ffff9002`41677530 fffff801`66ab7d92 : ffffad09`032721e0 ffff9002`41677760 00000000`00000040 ffffad08`ec0f07a0 : nt!ObpLookupObjectName+0x63b
ffff9002`416776d0 fffff801`66abb0c4 : 00000000`00000000 ffffad08`ec0f07a0 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffff9002`41677800 fffff801`66abba88 : 00000005`156fef68 ffffffff`ffffffff ffff9002`41677b20 fffff801`66b4acf9 : nt!CmOpenKey+0x2c4
ffff9002`41677a50 fffff801`668439e8 : ffffad09`03a2c500 ffff8000`32c27500 00000000`00000000 ffffad09`00000000 : nt!NtOpenKeyEx+0x48
ffff9002`41677aa0 00007ffa`85e11264 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000005`156fef48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`85e11264
SYMBOL_NAME: nt!HvpGetCellContextInitialize+19
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.1928
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 19
FAILURE_BUCKET_ID: AV_R_nt!HvpGetCellContextInitialize
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b5ba24f1-6e18-e00f-aeac-aa92a7f9092d}
Followup: MachineOwner
---------
Merhaba, 8 senelik laptopum ASUS X555ln modelinde yakın zamanda Windows 11 geçtim. Hiçbir sorun yoktu fakat son dönemde alakasız zamanlarda KMODE_EXCEPTION_NOT_HANDLED hatası alıyorum. Oyun oynarken de tarayıcıda dolaşırkende gelebiliyor bu hata. Minidump klasöründeki logları inceledim fakat pek...
www.technopat.net
* Disk düzeni GPT ise BIOS'a girin.
BIOS'ta Boot > CSM altında şu işaretlediğim 5 seçenekte sizde hangileri seçili?
Launch CSM = Enabled ise Disabled yapın. Kaydedin ve çıkın.
Boot Device Control kısmını da UEFI only yapın.
Genel önerilerim:
* BIOS eski kalmış.
* 3802 kullanıyorsunuz, 4002 sürümüne güncelleyin.
İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
PC açılınca yeni chipset sürücülerini kurun.
İnterneti bağlayabilirsiniz.
- Tüm bunlar sonucunda mavi ekran alırsanız yeni dökümleri paylaşın.
- Duruma göre Memtest86 ile RAM testi yapmanız gerekecek.
Döküm:
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: fffff80166aae745, 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 : Analysis.CPU.mSec
Value: 1875
Key : Analysis.Elapsed.mSec
Value: 2196
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: 140
Key : Analysis.Init.Elapsed.mSec
Value: 5864
Key : Analysis.Memory.CommitPeak.Mb
Value: 146
Key : Bugcheck.Code.LegacyAPI
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!HvpGetCellContextInitialize
Key : Failure.Hash
Value: {b5ba24f1-6e18-e00f-aeac-aa92a7f9092d}
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80166aae745
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
FILE_IN_CAB: 071123-7843-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff8016711c468: 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: AmpliTube 5.ex
STACK_TEXT:
ffff9002`41676408 fffff801`668cfbf7 : 00000000`0000001e ffffffff`c0000005 fffff801`66aae745 00000000`00000000 : nt!KeBugCheckEx
ffff9002`41676410 fffff801`668443fc : ffff9002`41676d40 00000000`02000000 00000000`00000000 ffffbd08`f2bf6ec4 : nt!KiDispatchException+0x1bb1d7
ffff9002`41676af0 fffff801`6683f483 : 00000000`00000000 ffffad08`ec0f07ec 00000000`00060000 00000000`00000001 : nt!KiExceptionDispatch+0x13c
ffff9002`41676cd0 fffff801`66aae745 : ff7ff801`66aab4ff ffffbd08`f280b930 00000000`81c37ddb 00000000`00000001 : nt!KiGeneralProtectionFault+0x343
ffff9002`41676e68 ff7ff801`66aab4ff : ffffbd08`f280b930 00000000`81c37ddb 00000000`00000001 fffff801`66adec13 : nt!HvpGetCellContextInitialize+0x19
ffff9002`41676e70 ffffbd08`f280b930 : 00000000`81c37ddb 00000000`00000001 fffff801`66adec13 00000000`00000000 : 0xff7ff801`66aab4ff
ffff9002`41676e78 00000000`81c37ddb : 00000000`00000001 fffff801`66adec13 00000000`00000000 00000000`00000000 : 0xffffbd08`f280b930
ffff9002`41676e80 00000000`00000001 : fffff801`66adec13 00000000`00000000 00000000`00000000 00000000`00000000 : 0x81c37ddb
ffff9002`41676e88 fffff801`66adec13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`ffffffff : 0x1
ffff9002`41676e90 fffff801`66aaf814 : ffff9002`41677000 ffff9002`41677120 ffffbd09`076d9bc0 ffffad09`032721e0 : nt!CmpDoWritethroughReparse+0x33
ffff9002`41676f00 fffff801`66ab4375 : ad0901d7`0000001c ffff9002`41677430 ffff9002`416773b8 00000000`00000000 : nt!CmpDoParseKey+0xbc4
ffff9002`41677340 fffff801`66ab891b : fffff801`66ab4001 ffffad08`00000000 ffffad09`032721e0 00000000`00000001 : nt!CmpParseKey+0x2e5
ffff9002`41677530 fffff801`66ab7d92 : ffffad09`032721e0 ffff9002`41677760 00000000`00000040 ffffad08`ec0f07a0 : nt!ObpLookupObjectName+0x63b
ffff9002`416776d0 fffff801`66abb0c4 : 00000000`00000000 ffffad08`ec0f07a0 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffff9002`41677800 fffff801`66abba88 : 00000005`156fef68 ffffffff`ffffffff ffff9002`41677b20 fffff801`66b4acf9 : nt!CmOpenKey+0x2c4
ffff9002`41677a50 fffff801`668439e8 : ffffad09`03a2c500 ffff8000`32c27500 00000000`00000000 ffffad09`00000000 : nt!NtOpenKeyEx+0x48
ffff9002`41677aa0 00007ffa`85e11264 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000005`156fef48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`85e11264
SYMBOL_NAME: nt!HvpGetCellContextInitialize+19
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.1928
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 19
FAILURE_BUCKET_ID: AV_R_nt!HvpGetCellContextInitialize
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b5ba24f1-6e18-e00f-aeac-aa92a7f9092d}
Followup: MachineOwner
---------
Merhaba, 8 senelik laptopum ASUS X555ln modelinde yakın zamanda Windows 11 geçtim. Hiçbir sorun yoktu fakat son dönemde alakasız zamanlarda KMODE_EXCEPTION_NOT_HANDLED hatası alıyorum. Oyun oynarken de tarayıcıda dolaşırkende gelebiliyor bu hata. Minidump klasöründeki logları inceledim fakat pek...
www.technopat.net
* disk düzeni GPT ise BIOS'a girin.
BIOS'ta boot > CSM altında şu işaretlediğim 5 seçenekte sizde hangileri seçili?
Launch CSM = enabled ise disabled yapın. Kaydedin ve çıkın.
İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
PC açılınca yeni chipset sürücülerini kurun.
İnterneti bağlayabilirsiniz.
- Tüm bunlar sonucunda mavi ekran alırsanız yeni dökümleri paylaşın.
- Duruma göre Memtest86 ile RAM testi yapmanız gerekecek.
Döküm:
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: fffff80166aae745, 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 : Analysis.CPU.mSec
Value: 1875.
Key : Analysis.Elapsed.mSec
Value: 2196.
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: 140.
Key : Analysis.Init.Elapsed.mSec
Value: 5864.
Key : Analysis.Memory.CommitPeak.Mb
Value: 146.
Key : Bugcheck.Code.LegacyAPI
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!HvpGetCellContextInitialize
Key : Failure.Hash
Value: {b5ba24f1-6e18-e00f-aeac-aa92a7f9092d}
BUGCHECK_CODE: 1e.
BUGCHECK_P1: ffffffffc0000005.
BUGCHECK_P2: fffff80166aae745.
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff.
FILE_IN_CAB: 071123-7843-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008.
Kernel Generated Triage Dump.
EXCEPTION_PARAMETER1: 0000000000000000.
EXCEPTION_PARAMETER2: ffffffffffffffff.
READ_ADDRESS: fffff8016711c468: 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: AmpliTube 5.ex
STACK_TEXT:
ffff9002`41676408 fffff801`668cfbf7 : 00000000`0000001e ffffffff`c0000005 fffff801`66aae745 00000000`00000000 : nt!KeBugCheckEx
ffff9002`41676410 fffff801`668443fc : ffff9002`41676d40 00000000`02000000 00000000`00000000 ffffbd08`f2bf6ec4 : nt!KiDispatchException+0x1bb1d7
ffff9002`41676af0 fffff801`6683f483 : 00000000`00000000 ffffad08`ec0f07ec 00000000`00060000 00000000`00000001 : nt!KiExceptionDispatch+0x13c
ffff9002`41676cd0 fffff801`66aae745 : ff7ff801`66aab4ff ffffbd08`f280b930 00000000`81c37ddb 00000000`00000001 : nt!KiGeneralProtectionFault+0x343
ffff9002`41676e68 ff7ff801`66aab4ff : ffffbd08`f280b930 00000000`81c37ddb 00000000`00000001 fffff801`66adec13 : nt!HvpGetCellContextInitialize+0x19
ffff9002`41676e70 ffffbd08`f280b930 : 00000000`81c37ddb 00000000`00000001 fffff801`66adec13 00000000`00000000 : 0xff7ff801`66aab4ff
ffff9002`41676e78 00000000`81c37ddb : 00000000`00000001 fffff801`66adec13 00000000`00000000 00000000`00000000 : 0xffffbd08`f280b930
ffff9002`41676e80 00000000`00000001 : fffff801`66adec13 00000000`00000000 00000000`00000000 00000000`00000000 : 0x81c37ddb.
ffff9002`41676e88 fffff801`66adec13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`ffffffff : 0x1.
ffff9002`41676e90 fffff801`66aaf814 : ffff9002`41677000 ffff9002`41677120 ffffbd09`076d9bc0 ffffad09`032721e0 : nt!CmpDoWritethroughReparse+0x33
ffff9002`41676f00 fffff801`66ab4375 : ad0901d7`0000001c ffff9002`41677430 ffff9002`416773b8 00000000`00000000 : nt!CmpDoParseKey+0xbc4
ffff9002`41677340 fffff801`66ab891b : fffff801`66ab4001 ffffad08`00000000 ffffad09`032721e0 00000000`00000001 : nt!CmpParseKey+0x2e5
ffff9002`41677530 fffff801`66ab7d92 : ffffad09`032721e0 ffff9002`41677760 00000000`00000040 ffffad08`ec0f07a0 : nt!ObpLookupObjectName+0x63b
ffff9002`416776d0 fffff801`66abb0c4 : 00000000`00000000 ffffad08`ec0f07a0 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffff9002`41677800 fffff801`66abba88 : 00000005`156fef68 ffffffff`ffffffff ffff9002`41677b20 fffff801`66b4acf9 : nt!CmOpenKey+0x2c4
ffff9002`41677a50 fffff801`668439e8 : ffffad09`03a2c500 ffff8000`32c27500 00000000`00000000 ffffad09`00000000 : nt!NtOpenKeyEx+0x48
ffff9002`41677aa0 00007ffa`85e11264 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000005`156fef48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`85e11264
SYMBOL_NAME: nt!HvpGetCellContextInitialize+19
MODULE_NAME: nt.
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.1928
STACK_COMMAND: .cxr; .ecxr ; kb.
BUCKET_ID_FUNC_OFFSET: 19.
FAILURE_BUCKET_ID: AV_R_nt!HvpGetCellContextInitialize
OSPLATFORM_TYPE: x64.
OSNAME: Windows 10.
FAILURE_ID_HASH: {b5ba24f1-6e18-e00f-aeac-aa92a7f9092d}
Followup: MachineOwner.
---------
Dostum selam az önce BIOS'u 4002 güncelledim attığın dosyadan CSM kapalıydı alttaki seçenekler o yüzden yoktu galiba sürücüler geri kurdum dediğin gibi.
Hazır böyle bir üstada denk gelmişken sorayım sorularımı.
PC fazla yavaş kapanıyor reset süreleri falan neden sence?
PC masaya yumruk attığımda neden kapanır (kabloları yokladım 24pin 8pin CPU zart zurt)
- Sistemde HDD yok değil mi? Sadece SSD var yani?
- HDD ile alakalı değilse PSU'da bir temassızlık vardır.
- Veya anakart güç soketlerinde bir temassızlık olabilir, kontrol etmiş olsanız bile 24pin veya 8pin soketlerinden biri arızalanmış olabilir.
Ben masaya sert bir şekilde vurduğumda, masaüstü bilgisayarım ya kilitleniyor ya da reset atıyor. Sebebi ne olabilir? Bunun bir sebebi sabit disk olabilir. Masaya sert vurduğunuzda sabit diskin okuma yazma kafası plakalara sürtebilir. Bu da verilerin bozulmasına sebep olur. İşletim sistemi de...
Merhaba, hızlı başlat seçeneği yüzünden bilgisayarımız kirleniyor, bugün bunu kapatmayı göstereceğim. Windows tuşuna sağ tıklıyoruz ve "Güç Seçenekleri" diyoruz. Biraz sayfayı aşağı kaydırıyoruz, ilgili ayarlar menüsünde "Ek güç ayarlarını" seçiyoruz. Sol tarafta "Güç düğmelerinin...
www.technopat.net
Bunun dışında,
- İşletim sistemi / dosya sistemi bozulmuş olabilir.
- SSD / HDD arızalanmış, bad sectorler oluşmuş olabilir.
- SSD / HDD aşırı yani tıka basa dolu olabilir.
- Sistemde HDD yok değil mi? Sadece SSD var yani?
- HDD ile alakalı değilse PSU'da bir temassızlık vardır.
- Veya anakart güç soketlerinde bir temassızlık olabilir, kontrol etmiş olsanız bile 24pin veya 8pin soketlerinden biri arızalanmış olabilir.
Ben masaya sert bir şekilde vurduğumda, masaüstü bilgisayarım ya kilitleniyor ya da reset atıyor. Sebebi ne olabilir? Bunun bir sebebi sabit disk olabilir. Masaya sert vurduğunuzda sabit diskin okuma yazma kafası plakalara sürtebilir. Bu da verilerin bozulmasına sebep olur. İşletim sistemi de...
Merhaba, hızlı başlat seçeneği yüzünden bilgisayarımız kirleniyor, bugün bunu kapatmayı göstereceğim. Windows tuşuna sağ tıklıyoruz ve "Güç Seçenekleri" diyoruz. Biraz sayfayı aşağı kaydırıyoruz, ilgili ayarlar menüsünde "Ek güç ayarlarını" seçiyoruz. Sol tarafta "Güç düğmelerinin...
www.technopat.net
Bunun dışında,
- İşletim sistemi / dosya sistemi bozulmuş olabilir.
- SSD / HDD arızalanmış, bad sectorler oluşmuş olabilir.
- SSD / HDD aşırı yani tıka basa dolu olabilir.
Teşekkür ediyorum yardımların ve tavsiyelerin için şimdi konuyu çözüldü olarak işaretliyorum eğer sana tekrar ihtiyacım olursa etiketlerim üstat sağ ol.