MEMORY_MANAGEMENT mavi ekran hatası

Burakktp

Decapat
Katılım
3 Şubat 2020
Mesajlar
5
Öncelikle merhaba. Yaklaşık 2 gündür mavi ekran hatası alıyorum driverler falan güncel sorunu anlamadım bir türlü yardımcı olursanız sevinirim. Minidump dosyaları da burada: minidump.rar
 
Son düzenleyen: Moderatör:
Bellek arızası. Emin olmak için test edebilirsiniz:


Kod:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffffb3ffe8dcc18
Arg3: 820000040761d205
Arg4: ffff800b6cdfa738

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

Key : Analysis.Memory.CommitPeak.Mb
Value: 68

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 403

BUGCHECK_P2: fffffb3ffe8dcc18

BUGCHECK_P3: 820000040761d205

BUGCHECK_P4: ffff800b6cdfa738

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: SearchUI.exe

STACK_TEXT:
fffff685`1210fa28 fffff803`257e9730 : 00000000`0000001a 00000000`00000403 fffffb3f`fe8dcc18 82000004`0761d205 : nt!KeBugCheckEx
fffff685`1210fa30 fffff803`256b11f7 : 00000000`00000003 fffff685`12110180 fffff685`12110180 fffff685`121100d0 : nt!MiDeletePteRun+0x1d3490
fffff685`1210fc50 fffff803`256acd12 : ffffb70f`3d38c580 fffffb3f`fe8dd000 00000000`00004000 00000000`00000000 : nt!MiDeleteVaTail+0x77
fffff685`1210fc80 fffff803`256acea1 : fffff685`121100d0 fffffb7d`9fff46e0 00000000`00000000 0a000002`205d2867 : nt!MiWalkPageTablesRecursively+0x512
fffff685`1210fd40 fffff803`256acea1 : fffff685`121100d0 fffffb7d`becfffa0 00000000`00000000 0a000003`5a669867 : nt!MiWalkPageTablesRecursively+0x6a1
fffff685`1210fe00 fffff803`256acea1 : fffff685`121100d0 fffffb7d`bedf67f8 fffffb7d`00000000 0a000001`96027867 : nt!MiWalkPageTablesRecursively+0x6a1
fffff685`1210fec0 fffff803`256ac62c : fffff685`121100d0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a1
fffff685`1210ff80 fffff803`256aaa98 : fffff685`121100d0 00000000`00000002 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36c
fffff685`12110080 fffff803`256b8bf0 : ffffffff`ffffffff ffffb70f`3d38c3f8 fffff685`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x268
fffff685`12110420 fffff803`25bc7a5d : ffffb70f`3bdd2080 ffffb70f`3bdd2080 ffffb70f`3d7076c0 ffffb70f`3d38c3f0 : nt!MiDeleteVad+0x860
fffff685`121105e0 fffff803`25bd9e14 : ffffb70f`3d7076c0 ffffb70f`3d45d9a0 ffffb70f`3bdd2080 00000000`00000000 : nt!MiUnmapVad+0x49
fffff685`12110610 fffff803`25bd98cf : ffffb70f`4065a280 ffffb70f`4065a280 ffffb70f`3d38c080 fffff803`25a6a400 : nt!MiCleanVad+0x30
fffff685`12110640 fffff803`25c38771 : ffffffff`00000000 ffffffff`ffffffff fffff685`12110801 ffffb70f`3d38c080 : nt!MmCleanProcessAddressSpace+0x137
fffff685`121106c0 fffff803`25c5e6d3 : ffffb70f`3d38c080 ffff800b`6d6df5f0 fffff685`121108e9 00000000`00000000 : nt!PspRundownSingleProcess+0x139
fffff685`12110740 fffff803`25ccd143 : 00000000`00000001 00000000`00000001 00000078`b9388000 00000000`00000000 : nt!PspExitThread+0x60b
fffff685`12110850 fffff803`2563e551 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x33
fffff685`12110890 fffff803`257c5a60 : 00000000`00000001 fffff685`12110950 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x481
fffff685`12110950 fffff803`257d2dbf : ffffb70f`3bdd2080 00000078`ba6ffb58 00000000`ffffffff fffff803`00001cff : nt!KiInitiateUserApc+0x70
fffff685`12110a90 00007ffd`23e29a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
00000078`ba6ffb38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`23e29a84


SYMBOL_NAME: nt!MiDeletePteRun+1d3490

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 1d3490

FAILURE_BUCKET_ID: 0x1a_403_nt!MiDeletePteRun

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {6e89a852-58e8-3dbb-af93-60d80dcc29e5}

Followup: MachineOwner
---------


CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01e683308d631, Reserved
Arg2: b3b72aee8589ec46, Reserved
Arg3: fffff8041f895618, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 5

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 9

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 109

BUGCHECK_P1: a3a01e683308d631

BUGCHECK_P2: b3b72aee8589ec46

BUGCHECK_P3: fffff8041f895618

BUGCHECK_P4: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9003`1d88ae98 00000000`00000000 : 00000000`00000109 a3a01e68`3308d631 b3b72aee`8589ec46 fffff804`1f895618 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -db !mssecflt
3 errors : !mssecflt (fffff8041f8956c3-fffff8041f8956fb)
fffff8041f8956c0 48 8b 4b *19 48 8b 44 24 38 48 89 48 30 48 8b 4b H.K.H.D$8H.H0H.K
...
fffff8041f8956f0 83 c0 48 *42 89 40 08 48 89 00 48 *81 44 24 38 48 [email protected]$8H

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup: memory_corruption
---------

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff88017540a38
Arg3: 0000000040000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

Key : Analysis.Memory.CommitPeak.Mb
Value: 68

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: fffff88017540a38

BUGCHECK_P3: 40000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: YourPhone.exe

STACK_TEXT:
ffffd182`87d63b98 fffff801`0dc252ee : 00000000`0000001a 00000000`00041792 fffff880`17540a38 00000000`40000000 : nt!KeBugCheckEx
ffffd182`87d63ba0 fffff801`0daac9e7 : 00000000`00000000 fffff880`17540a38 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x176b0e
ffffd182`87d63cb0 fffff801`0daacea1 : ffffd182`87d64100 fffff8fc`400baa00 00000000`00000000 0a000003`c35d7867 : nt!MiWalkPageTablesRecursively+0x1e7
ffffd182`87d63d70 fffff801`0daacea1 : ffffd182`87d64100 fffff8fc`7e2005d0 00000000`00000000 0a000001`b9899867 : nt!MiWalkPageTablesRecursively+0x6a1
ffffd182`87d63e30 fffff801`0daacea1 : ffffd182`87d64100 fffff8fc`7e3f1000 fffff8fc`00000000 0a000001`ad198867 : nt!MiWalkPageTablesRecursively+0x6a1
ffffd182`87d63ef0 fffff801`0daac62c : ffffd182`87d64100 fffff801`0fd496cf ffffbe81`00000000 fffff801`00000001 : nt!MiWalkPageTablesRecursively+0x6a1
ffffd182`87d63fb0 fffff801`0daaaa98 : ffffd182`87d64100 00000000`00000002 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36c
ffffd182`87d640b0 fffff801`0dab8bf0 : ffffffff`ffffffff ffffbe81`91c8d5b8 ffffbe81`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x268
ffffd182`87d64450 fffff801`0dfd9e31 : ffffbe81`940df080 00000000`00000000 ffffbe81`9207d330 ffffbe81`940df080 : nt!MiDeleteVad+0x860
ffffd182`87d64610 fffff801`0dfd98cf : ffffbe81`95758c80 ffffbe81`95758c80 ffffbe81`91c8d240 fffff801`0de6a400 : nt!MiCleanVad+0x4d
ffffd182`87d64640 fffff801`0e038771 : ffffffff`00000001 ffffffff`ffffffff ffffd182`87d64801 ffffbe81`91c8d240 : nt!MmCleanProcessAddressSpace+0x137
ffffd182`87d646c0 fffff801`0e05e6d3 : ffffbe81`91c8d240 ffffd70a`df2dd770 ffffd182`87d648e9 00000000`00000000 : nt!PspRundownSingleProcess+0x139
ffffd182`87d64740 fffff801`0e0cd143 : 00000000`40010004 00000000`00000001 0000002e`a78fa000 00000000`00000000 : nt!PspExitThread+0x60b
ffffd182`87d64850 fffff801`0da3e551 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x33
ffffd182`87d64890 fffff801`0dbc5a60 : 00000000`00000001 ffffd182`87d64950 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x481
ffffd182`87d64950 fffff801`0dbd2dbf : ffffbe81`940df080 0000002e`a7dff6b8 00000000`00007530 00000000`00001cff : nt!KiInitiateUserApc+0x70
ffffd182`87d64a90 00007ff8`18559a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
0000002e`a7dff698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`18559a84


MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner
---------


MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff833ffd6dfc08
Arg3: 0000000001000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

Key : Analysis.Memory.CommitPeak.Mb
Value: 67

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffff833ffd6dfc08

BUGCHECK_P3: 1000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MicrosoftEdge.exe

STACK_TEXT:
ffffb808`bdebbb68 fffff807`512252ee : 00000000`0000001a 00000000`00041792 ffff833f`fd6dfc08 00000000`01000000 : nt!KeBugCheckEx
ffffb808`bdebbb70 fffff807`510ac9e7 : 00000000`00000000 ffff833f`fd6dfc08 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x176b0e
ffffb808`bdebbc80 fffff807`510acea1 : ffffb808`bdebc0d0 ffff8341`9ffeb6f8 00000000`00000000 0a000003`4d5c3867 : nt!MiWalkPageTablesRecursively+0x1e7
ffffb808`bdebbd40 fffff807`510acea1 : ffffb808`bdebc0d0 ffff8341`a0cfff58 00000000`00000000 0a000003`88fce867 : nt!MiWalkPageTablesRecursively+0x6a1
ffffb808`bdebbe00 fffff807`510acea1 : ffffb808`bdebc0d0 ffff8341`a0d067f8 ffff8341`00000000 0a000000`ce311867 : nt!MiWalkPageTablesRecursively+0x6a1
ffffb808`bdebbec0 fffff807`510ac62c : ffffb808`bdebc0d0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a1
ffffb808`bdebbf80 fffff807`510aaa98 : ffffb808`bdebc0d0 ffffa50f`00000002 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36c
ffffb808`bdebc080 fffff807`510b8bf0 : ffffffff`ffffffff ffffa50f`551863f8 ffffb808`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x268
ffffb808`bdebc420 fffff807`515c7a5d : ffffa50f`53903080 ffffa50f`53903080 ffffa50f`59525ee0 ffffa50f`551863f0 : nt!MiDeleteVad+0x860
ffffb808`bdebc5e0 fffff807`515d9e14 : ffffa50f`59525ee0 ffffa50f`57755c00 ffffa50f`53903080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffb808`bdebc610 fffff807`515d98cf : ffffa50f`59507d00 ffffa50f`59507d00 ffffa50f`55186080 fffff807`5146a400 : nt!MiCleanVad+0x30
ffffb808`bdebc640 fffff807`51638771 : ffffffff`00000001 ffffffff`ffffffff ffffb808`bdebc801 ffffa50f`55186080 : nt!MmCleanProcessAddressSpace+0x137
ffffb808`bdebc6c0 fffff807`5165e6d3 : ffffa50f`55186080 ffffb90f`77bbd730 ffffb808`bdebc8e9 00000000`00000000 : nt!PspRundownSingleProcess+0x139
ffffb808`bdebc740 fffff807`516cd143 : 00000000`00000001 00000000`00000001 00000085`f5650000 00000000`00000e8c : nt!PspExitThread+0x60b
ffffb808`bdebc850 fffff807`5103e551 : ffffb808`bdebcb00 ffff833f`fd7201a8 ffff8341`9ffeb900 ffff8341`a0cfff58 : nt!KiSchedulerApcTerminate+0x33
ffffb808`bdebc890 fffff807`511c5a60 : ffffa50f`55186501 ffffb808`bdebc950 00000000`00000110 00000000`00000000 : nt!KiDeliverApc+0x481
ffffb808`bdebc950 fffff807`511d2dbf : 00000000`746c6644 ffffb808`bdebcb00 ffffa50f`53903080 00000085`f7c4f738 : nt!KiInitiateUserApc+0x70
ffffb808`bdebca90 00007ffb`0aa1cc14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
00000085`f7c4f718 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`0aa1cc14


MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner
---------
 

Dosya Ekleri

  • 9506def0-3b95-4fe4-a5cd-f55ebb06cc7a.jpg
    9506def0-3b95-4fe4-a5cd-f55ebb06cc7a.jpg
    135,8 KB · Görüntüleme: 33
Tamam, kit değiller işte neden kit diyorsun.

Yukarıda denilen Memtest86 testi yap, eğer bellekler problemsiz geçerse bilgisayara tek bellek tak o şekilde kullan hala mavi ekran alıyorsan diğer belleği tak, hala mavi ekran alıyorsan anakart problemli olabilir.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Yeni konular

Geri
Yukarı