MEMORY_MANAGEMENT Mavi Ekran Hatası
- Konuyu başlatan Kocakberk
- Başlangıç Tarihi
- Mesaj 22
- Görüntüleme 1B
Jang Geum'un Danji Yemeği
Megapat
- Katılım
- 18 Temmuz 2019
- Mesajlar
- 8.073
- Makaleler
- 8
- Çözümler
- 99
Güvenli modda başlatmayı dener misiniz?
@Murat5038
@Murat5038
Daha fazla
- Cinsiyet
- Erkek
- Profil Kapağı
- 1522743131
Bu sorunun BIOS güncelleme sonrası olduğuna emin misiniz? Önceki mesajınıza göre BIOS güncellemeden önce de mavi ekran hatası alıyormuşsunuz zaten.
Hiçbişey yapamadan mavi ekran veriyor.
Bios güncellemeden önce mavi ekran alıyordum ancak arada alıyordum biosu güncelledikten sonra sürekli almaya başladım hiçbişey yapamıyorum sürekli mavi ekran veriyor.
Daha fazla
- Cinsiyet
- Erkek
- Profil Kapağı
- 1522743131
Bellekleriniz sorunlu olabilir. XMP'yi kapatıp deneyin.
Kod:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: ffff83000020ffa0
Arg3: 01000000d98331df
Arg4: ffff8f095afb9da0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2077
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-05IMVF3
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 10857
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41201
BUGCHECK_P2: ffff83000020ffa0
BUGCHECK_P3: 1000000d98331df
BUGCHECK_P4: ffff8f095afb9da0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: League of Legends.exe
STACK_TEXT:
ffffb606`2c16b548 fffff802`7be4c05a : 00000000`0000001a 00000000`00041201 ffff8300`0020ffa0 01000000`d98331df : nt!KeBugCheckEx
ffffb606`2c16b550 fffff802`7bcb52e4 : 00000000`00001000 00000000`00000000 00000000`00000000 ffff8f09`5afb9da0 : nt!MiGetPageProtection+0x19604a
ffffb606`2c16b5b0 fffff802`7bca31cf : 00000000`00000000 00000000`41f4f000 00000000`41f4e000 00000000`00000000 : nt!MiQueryAddressState+0x2f4
ffffb606`2c16b7d0 fffff802`7c06b85c : ffff8f09`00000000 00000000`00000000 ffff8f09`00000000 00000000`00000000 : nt!MiQueryAddressSpan+0xcf
ffffb606`2c16b890 fffff802`7c06b005 : ffff4db8`ce8d6d21 ffff8341`a0c00008 00000000`77124630 00000000`3940f2e4 : nt!MmQueryVirtualMemory+0x83c
ffffb606`2c16ba40 fffff802`7bdef878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`387ce328 : nt!NtQueryVirtualMemory+0x25
ffffb606`2c16ba90 00007ffe`b8aac224 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`387ce248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`b8aac224
SYMBOL_NAME: nt!MiGetPageProtection+19604a
MODULE_NAME: nt
IMAGE_VERSION: 10.0.19041.450
STACK_COMMAND: .thread ; .cxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 19604a
FAILURE_BUCKET_ID: 0x1a_41201_nt!MiGetPageProtection
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c1fe3b27-3ba8-d99e-656f-85f3d58dc669}
Followup: MachineOwner
---------
KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.
Arguments:
Arg1: ffff8187f7132080, The address of the thread.
Arg2: ffffac0eb429fc90, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2655
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-05IMVF3
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 15838
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 192
BUGCHECK_P1: ffff8187f7132080
BUGCHECK_P2: ffffac0eb429fc90
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
STACK_TEXT:
ffff9500`11159048 fffff806`06025c32 : 00000000`00000192 ffff8187`f7132080 ffffac0e`b429fc90 00000000`00000000 : nt!KeBugCheckEx
ffff9500`11159050 fffff806`063f9ac8 : ffffac0e`b429fc60 00000000`00000000 00000000`00000000 ffff9500`11159940 : nt!ExAcquirePushLockSharedEx+0x142
ffff9500`111590a0 fffff806`063fa298 : ffff9500`11159940 00000000`00000000 ffffac0e`b429fc60 00000000`00000000 : nt!CmpLockKcbStackShared+0x38
ffff9500`111590d0 fffff806`063f2203 : ffff8187`0000001c ffff9500`11159420 ffff9500`111593d8 ffff8187`f97cb010 : nt!CmpDoParseKey+0x7a8
ffff9500`11159370 fffff806`063f58ee : fffff806`063f1f01 00000000`00000000 ffff8187`f97cb010 00000000`00000001 : nt!CmpParseKey+0x2c3
ffff9500`11159510 fffff806`063f134a : ffff8187`f97cb000 ffff9500`11159778 ffff8187`00000040 ffff8187`ef2fc820 : nt!ObpLookupObjectName+0x3fe
ffff9500`111596e0 fffff806`063f112c : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8187`ef2fc820 : nt!ObOpenObjectByNameEx+0x1fa
ffff9500`11159810 fffff806`063f0c51 : 0000009c`8b94d648 ffff9500`11159b80 00000000`00000001 fffff806`0600198e : nt!ObOpenObjectByName+0x5c
ffff9500`11159860 fffff806`063f023f : 0000009c`8b94dae0 00000000`000000d4 00000000`00020119 00000000`00000000 : nt!CmOpenKey+0x2c1
ffff9500`11159ac0 fffff806`061ef878 : 00000000`00000000 00000000`00000000 ffff8187`f7132080 0000024e`b7628a80 : nt!NtOpenKeyEx+0xf
ffff9500`11159b00 00007ffa`611ae1b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000009c`8b94d568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`611ae1b4
SYMBOL_NAME: nt!ExAcquirePushLockSharedEx+142
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.450
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 142
FAILURE_BUCKET_ID: 0x192_nt!ExAcquirePushLockSharedEx
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {292e4563-5d10-0ceb-86fc-152da5e999ce}
Followup: MachineOwner
---------
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8075f8fa320, 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: 2968
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-05IMVF3
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 11941
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8075f8fa320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffffb81fcd79680 -- (.trap 0xfffffb81fcd79680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000100084 rbx=0000000000000000 rcx=ffff9b817f340180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8075ee2aef1 rsp=fffffb81fcd79810 rbp=0000000000000000
r8=ffffb30cbbf584c0 r9=0000000000000080 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeRemoveQueueEx+0x551:
fffff807`5ee2aef1 8b07 mov eax,dword ptr [rdi] ds:00000000`00000000=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: LeagueClientUxRender.exe
STACK_TEXT:
ffff9b81`7f338e18 fffff807`5f05963e : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`5f8fa320 : nt!KeBugCheckEx
ffff9b81`7f338e20 fffff807`5eec98bd : 000010a1`8b6c8850 00000000`00000000 fffffb81`fcd79700 ffff9b81`7f340180 : nt!KeAccumulateTicks+0x18cbee
ffff9b81`7f338e80 fffff807`5eec973a : ffffb30c`af8cd040 fffffb81`fcd79700 00000000`0004f081 00000000`00000000 : nt!KeClockInterruptNotify+0xbd
ffff9b81`7f338f30 fffff807`5ee08725 : ffffb30c`af8cd040 fffff807`5ef43b37 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9b81`7f338f60 fffff807`5efdf9ea : fffffb81`fcd79700 ffffb30c`af8cd040 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9b81`7f338fb0 fffff807`5efdff57 : ffffb30c`baf70280 ffff9b81`7eee0340 ffffb30c`baf70280 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb81`fcd79680 fffff807`5ee2aef1 : ffffb30c`00000000 ffffb30c`00000000 00000000`00000000 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb81`fcd79810 fffff807`5ee2a638 : ffffb30c`bbf584c0 00000000`00000001 ffffb30c`bbaef830 fffff807`00000000 : nt!KeRemoveQueueEx+0x551
fffffb81`fcd798b0 fffff807`5f2dd26d : 00000000`00000000 00000000`00000000 ffff9b81`7eed5180 fffff807`5ee3e2aa : nt!IoRemoveIoCompletion+0x98
fffffb81`fcd799e0 fffff807`5efef878 : ffffb30c`baf70280 00000000`0935ec08 fffffb81`fcd79aa8 00000000`02be1394 : nt!NtRemoveIoCompletion+0x13d
fffffb81`fcd79a90 00000000`77361cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0935ebe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77361cfc
SYMBOL_NAME: nt!KeAccumulateTicks+18cbee
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.450
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 18cbee
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000107, A data mismatch has occurred in the internal hibernation data
structures.
Arg2: 000000000000000a
Arg3: ffffd20724e4b6d0, POP_HIBER_CONTEXT
Arg4: 0000000000000000, PO_MEMORY_RANGE_ARRAY
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2234
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-05IMVF3
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 11034
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
DUMP_FILE_ATTRIBUTES: 0x9
Hiber Crash Dump
Kernel Generated Triage Dump
BUGCHECK_CODE: a0
BUGCHECK_P1: 107
BUGCHECK_P2: a
BUGCHECK_P3: ffffd20724e4b6d0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
fffffe8c`e068b488 fffff802`7fdaf835 : 00000000`000000a0 00000000`00000107 00000000`0000000a ffffd207`24e4b6d0 : nt!KeBugCheckEx
fffffe8c`e068b490 fffff802`7fda008e : ffff9981`31101180 fffff802`7f76f194 00070106`00070106 00000000`00000001 : nt!PopDecompressHiberBlocks+0x11731
fffffe8c`e068b6b0 fffff802`7fd9fdf0 : 00000000`00000000 00000000`00000000 00000000`00000014 00000000`00000000 : nt!PopRestoreHiberContext+0x146
fffffe8c`e068b740 fffff802`7fd9fbb3 : fffff802`800503f0 fffffe8c`e068b960 fffffe8c`e068bb20 ffffd207`288f31b0 : nt!PopHandleNextState+0x210
fffffe8c`e068b790 fffff802`7f63a6be : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopInvokeStateHandlerTargetProcessor+0x53
fffffe8c`e068b860 fffff802`7f6399a4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffffe8c`e068b9d0 fffff802`7f7e1aae : ffffffff`00000000 ffff9981`31101180 ffff9981`3110c340 ffffd207`23487040 : nt!KiRetireDpcList+0x1f4
fffffe8c`e068bc60 00000000`00000000 : fffffe8c`e068c000 fffffe8c`e0686000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!PopDecompressHiberBlocks+11731
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.450
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 11731
FAILURE_BUCKET_ID: 0xa0_107_nt!PopDecompressHiberBlocks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5d9c83f4-ef2e-05d6-286b-9d88881fdb2f}
Followup: MachineOwner
---------
Minidump Dosyalarını Upload Etme | Technopat Sosyal
Güvenli modda deneyin. BIOS default edip kaydedin etmediyseniz.
Dosyaları da paylaşın açınca.
Güvenli modda deneyin. BIOS default edip kaydedin etmediyseniz.
Dosyaları da paylaşın açınca.
Jang Geum'un Danji Yemeği
Megapat
- Katılım
- 18 Temmuz 2019
- Mesajlar
- 8.073
- Makaleler
- 8
- Çözümler
- 99
BIOS Sıfırlama Rehberi
BIOS'u varsayılan ayarlara döndürme işlemine sıfırlama diyoruz. BIOS sıfırlamak için farklı dizüstü ve masaüstü bilgisayarlarda farklı yöntemler mevcut. Yazılımsal yolla sıfırlama: Bu işlem için PC açılırken Del/F2 tuşu ile BIOS'a girilir. Exit sekmesinde Restore Defaults seçeneğinin üstüne...
Yazım kurallarına dikkat etmezseniz sorunun çözümü ciddi bir süre uzar.BIOS Sıfırlama Rehberi
BIOS'u varsayılan ayarlara döndürme işlemine sıfırlama diyoruz. BIOS sıfırlamak için farklı dizüstü ve masaüstü bilgisayarlarda farklı yöntemler mevcut. Yazılımsal yolla sıfırlama: Bu işlem için PC açılırken Del/F2 tuşu ile BIOS'a girilir. Exit sekmesinde Restore Defaults seçeneğinin üstüne...www.technopat.net
Teşekkür ederim. Kusura bakmayın.
Şu an Windows'u kurdum. Çok teşekkür ederim.
Ama şimdi yine mavi ekran verdi.
Bilgisayarım açılıyor masaüstüne girdiğimde 10saniye geçince mavi ekran veriyor. Her seferinde yapıyor bunu. Hangi parçada sıkıntım olduğunu nasıl anlayabilirim?
Son düzenleyen: Moderatör:
Daha fazla
- Cinsiyet
- Erkek
- Profil Kapağı
- 1522743131
Minidump dosyalarını paylaşmaya devam edin. Ayrıca bellek testini hangi yazılımla yaptınız? Ayrıca size BIOS güncelleyin dendi. BIOS güncellemesi yaptınız mı?
Benzer konular
Yeni konular
-
Elektronik Vatan Bilgisayar geceye özel seçili ürünlerde %10 indirim
- furkansama
- Mesaj: 0
-
-
Gigabyte B550 Gaming X V2 anakart için ikinci M.2 SSD önerisi
- Erdem yılmaz09
- Mesaj: 2
-
-
-
-
-
-
-
-
-
