Buyrun Minidump - Google DriveMinidump Dosyalarını Paylaşın
Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...www.technopat.net
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\maksu\Desktop\Minidumplar\121520-11453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`20200000 PsLoadedModuleList = 0xfffff805`20e2a2b0
Debug session time: Tue Dec 15 23:00:26.508 2020 (UTC + 3:00)
System Uptime: 0 days 1:39:01.129
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`205f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8802`b0a6f370=000000000000000a
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff805005aa913, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff805005aa913, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5562
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2EFLS9
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 9428
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
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: d1
BUGCHECK_P1: fffff805005aa913
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: fffff805005aa913
READ_ADDRESS: fffff80520efa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80520e0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80520e0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffff805005aa913
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffff8802b0a6f4b0 -- (.trap 0xffff8802b0a6f4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffb20a67821638
rdx=ffffb20a67821988 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805005aa913 rsp=ffff8802b0a6f640 rbp=ffff8802b0a6f740
r8=0000000000000001 r9=0000000000000011 r10=000000000000007f
r11=ffffb20a678219a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff805`005aa913 ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
+0
fffff805`005aa913 ?? ???
STACK_TEXT:
ffff8802`b0a6f368 fffff805`20607769 : 00000000`0000000a fffff805`005aa913 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffff8802`b0a6f370 fffff805`20603a69 : 000008fe`00000010 00000015`00000006 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8802`b0a6f4b0 fffff805`005aa913 : 00000000`005aa921 00000000`00000000 ffff8802`b0a6f740 00000000`00000006 : nt!KiPageFault+0x469
ffff8802`b0a6f640 00000000`005aa921 : 00000000`00000000 ffff8802`b0a6f740 00000000`00000006 00000000`00000000 : 0xfffff805`005aa913
ffff8802`b0a6f648 00000000`00000000 : ffff8802`b0a6f740 00000000`00000006 00000000`00000000 00000000`00000000 : 0x5aa921
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
---------
sıkıntı tam olarak nerede ?DDU ile ekran kartı sürücüsünü kaldırıp WHQL (önerilen) sürümü kurun.
Rehber: DDU ile Sürücü Kaldırma Rehberi
Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...www.technopat.net
Kaypersky'ı bir süreliğine kaldırın.
BİOS'u ve LAN sürücüsünü güncelleyin.
PRIME B450M-K|Anakart|ASUS Türkiye
ASUS Prime serisi, AMD ve Intel iÅlemcilerin tüm potansiyelini ortaya çıkarmak için özenle geliÅtirildi. SaÄlam güç tasarımına, kapsamlı soÄutma çözümlerine ve akıllı ayar seçeneklerine sahip olan Prime serisi anakartlar, kendi PCâlerini toplayan kiÅilere kullanıÅlı...www.asus.com
BİOS ve LAN sürücüsünü güncelleyene kadar Wi-Fi'yi kullanmayın.
Kod:Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\maksu\Desktop\Minidumplar\121520-11453-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`20200000 PsLoadedModuleList = 0xfffff805`20e2a2b0 Debug session time: Tue Dec 15 23:00:26.508 2020 (UTC + 3:00) System Uptime: 0 days 1:39:01.129 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........................ Loading User Symbols Loading unloaded module list ........... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`205f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8802`b0a6f370=000000000000000a 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff805005aa913, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: fffff805005aa913, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5562 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-G2EFLS9 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 9428 Key : Analysis.Memory.CommitPeak.Mb Value: 84 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: d1 BUGCHECK_P1: fffff805005aa913 BUGCHECK_P2: 2 BUGCHECK_P3: 8 BUGCHECK_P4: fffff805005aa913 READ_ADDRESS: fffff80520efa390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80520e0f330: Unable to get Flags value from nt!KdVersionBlock fffff80520e0f330: Unable to get Flags value from nt!KdVersionBlock unable to get nt!MmSpecialPagesInUse fffff805005aa913 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffff8802b0a6f4b0 -- (.trap 0xffff8802b0a6f4b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=ffffb20a67821638 rdx=ffffb20a67821988 rsi=0000000000000000 rdi=0000000000000000 rip=fffff805005aa913 rsp=ffff8802b0a6f640 rbp=ffff8802b0a6f740 r8=0000000000000001 r9=0000000000000011 r10=000000000000007f r11=ffffb20a678219a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc fffff805`005aa913 ?? ??? Resetting default scope FAILED_INSTRUCTION_ADDRESS: +0 fffff805`005aa913 ?? ??? STACK_TEXT: ffff8802`b0a6f368 fffff805`20607769 : 00000000`0000000a fffff805`005aa913 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx ffff8802`b0a6f370 fffff805`20603a69 : 000008fe`00000010 00000015`00000006 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffff8802`b0a6f4b0 fffff805`005aa913 : 00000000`005aa921 00000000`00000000 ffff8802`b0a6f740 00000000`00000006 : nt!KiPageFault+0x469 ffff8802`b0a6f640 00000000`005aa921 : 00000000`00000000 ffff8802`b0a6f740 00000000`00000006 00000000`00000000 : 0xfffff805`005aa913 ffff8802`b0a6f648 00000000`00000000 : ffff8802`b0a6f740 00000000`00000006 00000000`00000000 00000000`00000000 : 0x5aa921 SYMBOL_NAME: nt!KiPageFault+469 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.685 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 469 FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403} Followup: MachineOwner ---------
0x000000d1 hatası kablosuz wifi den kaynaklı olduğunu söylüyorlar ama çünkü ekran kartı sürücüsü şuanda en güncel halde ve daha yeni bir sistem bu sorunun hayla ekran kartı veya bios ta olduğunu gösterirmiSıkıntı ekran kartı sürücüsünde, Kaypersky'da ya da BİOS ve ya LAN sürücüsünün güncel olmamasından kaynaklı. Yazdıklarımı uygulayın.
Sorun devam ederse dosyaları paylaşın.
0x000000d1 hatası kablosuz Wi-Fi'den kaynaklı olduğunu söylüyorlar ama.
LAN ne oluyor baktınız mı?BİOS ve LAN sürücüsünü güncelleyene kadar Wi-Fi'yi kullanmayın.
Kablolu ağa kullanmamaktayım tp link wifi adaptörü kullanıyorumLAN ne oluyor baktınız mı?
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.