Windows 10 yeşil ekran MEMORY_MANAGEMENT hatası

Shura_Sama019

Shura_Sama019

Hectopat
Katılım
27 Aralık 2020
Mesajlar
553
Çözümler
1
4. kez aynı olayı yaşıyorum. Neden oldu bilmiyorum. Bilgisi olan arkadaş var mı acaba?
Not: İşletim sistemim Windows 10.

resim_2021-10-12_153036.png
 
Tarihe göre sırala Puana göre sırala
Bir bellek testi yapar mısın?

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...
www.technopat.net www.technopat.net

Kod: 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80760326ec9, Address of the instruction which caused the BugCheck
Arg3: ffff85808f8d9920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 92

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 18996

    Key  : Analysis.Init.CPU.mSec
    Value: 249

    Key  : Analysis.Init.Elapsed.mSec
    Value: 13712

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

    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_DEBUG_TEXT: 
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 772fbcde

WRONG_SYMBOLS_SIZE: 1046000

FAULTING_MODULE: fffff80760000000 nt

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80760326ec9

BUGCHECK_P3: ffff85808f8d9920

BUGCHECK_P4: 0

CONTEXT:  ffff85808f8d9920 -- (.cxr 0xffff85808f8d9920)
rax=ffffda0de9a57b08 rbx=ffffda0df0bec460 rcx=ffffda0ce9a57b08
rdx=0000000068547844 rsi=0000000000000000 rdi=ffffda0de9a57b08
rip=fffff80760326ec9 rsp=ffffd30473c4c910 rbp=0000000000000000
 r8=ffffda0df0bec460  r9=6d06f4d2baa07ff6 r10=0000fffff807606b
r11=ffff757a58a00000 r12=0000000000000000 r13=0000000000000000
r14=ffffda0dedd16080 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt+0x326ec9:
fffff807`60326ec9 48395908        cmp     qword ptr [rcx+8],rbx ds:002b:ffffda0c`e9a57b10=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffffd304`73c4c910 00000000`00000000     : 00000000`68547844 ffffda0d`e9a57540 fffff807`606b0b37 ffffda0d`edd16080 : nt+0x326ec9


STACK_COMMAND:  .cxr 0xffff85808f8d9920 ; kb

EXCEPTION_CODE_STR:  772FBCDE

EXCEPTION_STR:  WRONG_SYMBOLS

PROCESS_NAME:  ntoskrnl.wrong.symbols.exe

IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

SYMBOL_NAME:  nt_wrong_symbols!772FBCDE1046000

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_330513-171406_772FBCDE_nt_wrong_symbols!772FBCDE1046000

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3fbc5df3-d18e-9a75-b220-c98d06b4672b}

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

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: fffff802373b4425, The address that the exception occurred at
Arg3: ffffee02fc715e78, Parameter 0 of the exception
Arg4: ffffbb00529e7920, Parameter 1 of the exception


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 359

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 18934

    Key  : Analysis.Init.CPU.mSec
    Value: 171

    Key  : Analysis.Init.Elapsed.mSec
    Value: 13090

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

    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_DEBUG_TEXT: 
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 772fbcde

WRONG_SYMBOLS_SIZE: 1046000

FAULTING_MODULE: fffff8023b000000 nt

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff802373b4425

BUGCHECK_P3: ffffee02fc715e78

BUGCHECK_P4: ffffbb00529e7920


Unable to get size of nt!_MMPTE - probably bad symbols
 ffffbb00529e7920

EXCEPTION_PARAMETER1:  ffffee02fc715e78

EXCEPTION_PARAMETER2:  ffffbb00529e7920

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffffbb00`529e70a8 fffff802`3b50f82f     : 00000000`0000001e ffffffff`c0000005 fffff802`373b4425 ffffee02`fc715e78 : nt+0x3f71b0
ffffbb00`529e70b0 00000000`0000001e     : ffffffff`c0000005 fffff802`373b4425 ffffee02`fc715e78 ffffbb00`529e7920 : nt+0x50f82f
ffffbb00`529e70b8 ffffffff`c0000005     : fffff802`373b4425 ffffee02`fc715e78 ffffbb00`529e7920 00000000`00000000 : 0x1e
ffffbb00`529e70c0 fffff802`373b4425     : ffffee02`fc715e78 ffffbb00`529e7920 00000000`00000000 ffffee02`fc715e78 : 0xffffffff`c0000005
ffffbb00`529e70c8 ffffee02`fc715e78     : ffffbb00`529e7920 ffffee02`fc715e78 ffffbb00`529e7210 fffff802`3b000000 : Ndu!NduOutboundTransportClassify+0x2b5
ffffbb00`529e7168 ffffbb00`529e7920     : ffffee02`fc715e78 ffffbb00`529e7210 fffff802`3b000000 ffffbb00`529e77c0 : 0xffffee02`fc715e78
ffffbb00`529e7170 ffffee02`fc715e78     : ffffbb00`529e7210 fffff802`3b000000 ffffbb00`529e77c0 fffff802`3b2f8458 : 0xffffbb00`529e7920
ffffbb00`529e7178 ffffbb00`529e7210     : fffff802`3b000000 ffffbb00`529e77c0 fffff802`3b2f8458 fffff802`3b400072 : 0xffffee02`fc715e78
ffffbb00`529e7180 fffff802`3b000000     : ffffbb00`529e77c0 fffff802`3b2f8458 fffff802`3b400072 fffff802`3b0d3ce0 : 0xffffbb00`529e7210
ffffbb00`529e7188 ffffbb00`529e77c0     : fffff802`3b2f8458 fffff802`3b400072 fffff802`3b0d3ce0 ffffbb00`529e7710 : nt
ffffbb00`529e7190 fffff802`3b2f8458     : fffff802`3b400072 fffff802`3b0d3ce0 ffffbb00`529e7710 fffff802`3b3ccd30 : 0xffffbb00`529e77c0
ffffbb00`529e7198 fffff802`3b400072     : fffff802`3b0d3ce0 ffffbb00`529e7710 fffff802`3b3ccd30 00000000`00000000 : nt+0x2f8458
ffffbb00`529e71a0 fffff802`3b0d3ce0     : ffffbb00`529e7710 fffff802`3b3ccd30 00000000`00000000 ffffbb00`529e7760 : nt+0x400072
ffffbb00`529e71a8 ffffbb00`529e7710     : fffff802`3b3ccd30 00000000`00000000 ffffbb00`529e7760 fffff802`3b2e6dd7 : nt+0xd3ce0
ffffbb00`529e71b0 fffff802`3b3ccd30     : 00000000`00000000 ffffbb00`529e7760 fffff802`3b2e6dd7 ffffbb00`529e7710 : 0xffffbb00`529e7710
ffffbb00`529e71b8 00000000`00000000     : ffffbb00`529e7760 fffff802`3b2e6dd7 ffffbb00`529e7710 00000000`00000000 : nt+0x3ccd30


SYMBOL_NAME:  nt_wrong_symbols!772FBCDE1046000

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

EXCEPTION_CODE_STR:  772FBCDE

EXCEPTION_STR:  WRONG_SYMBOLS

PROCESS_NAME:  ntoskrnl.wrong.symbols.exe

IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_330513-171406_772FBCDE_nt_wrong_symbols!772FBCDE1046000

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3fbc5df3-d18e-9a75-b220-c98d06b4672b}

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

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: fffff8059b404425, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: ffff9a87d8303200, Parameter 1 of the exception

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 296

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 24083

    Key  : Analysis.Init.CPU.mSec
    Value: 202

    Key  : Analysis.Init.Elapsed.mSec
    Value: 13151

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

    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_DEBUG_TEXT: 
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 772fbcde

WRONG_SYMBOLS_SIZE: 1046000

FAULTING_MODULE: fffff80583e00000 nt

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8059b404425

BUGCHECK_P3: 1

BUGCHECK_P4: ffff9a87d8303200

WRITE_ADDRESS: *************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_MMPFN                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_MMPTE                                     ***
***                                                                   ***
*************************************************************************
Unable to get size of nt!_MMPTE - probably bad symbols
 ffff9a87d8303200

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  ffff9a87d8303200

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
fffff805`87ea6158 fffff805`842f5a6e     : 00000000`0000001e ffffffff`c0000005 fffff805`9b404425 00000000`00000001 : nt+0x3f71b0
fffff805`87ea6160 00000000`0000001e     : ffffffff`c0000005 fffff805`9b404425 00000000`00000001 ffff9a87`d8303200 : nt+0x4f5a6e
fffff805`87ea6168 ffffffff`c0000005     : fffff805`9b404425 00000000`00000001 ffff9a87`d8303200 fffff805`87ea6720 : 0x1e
fffff805`87ea6170 fffff805`9b404425     : 00000000`00000001 ffff9a87`d8303200 fffff805`87ea6720 fffff805`842f5a4c : 0xffffffff`c0000005
fffff805`87ea6178 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ndu!NduOutboundTransportClassify+0x2b5


SYMBOL_NAME:  nt_wrong_symbols!772FBCDE1046000

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

EXCEPTION_CODE_STR:  772FBCDE

EXCEPTION_STR:  WRONG_SYMBOLS

PROCESS_NAME:  ntoskrnl.wrong.symbols.exe

IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_330513-171406_772FBCDE_nt_wrong_symbols!772FBCDE1046000

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3fbc5df3-d18e-9a75-b220-c98d06b4672b}

Followup:     MachineOwner
---------
Shura_Sama019 dedi:
19041.1 nedir anladım hocam. Geç cevap verdiğim için özür dilerim yine aynı hata oluştu.
Genişletmek için tıkla...

Bellek testi yap. Kullandığın Windows 10 sürümü eski ve hiç güncelleme yapmamışsın. Normalde zaten mavi ekran alman lazım. Yeşil ekran genelde Beta/Geliştirici sürümlerde oluyor. Bu Windows'u kim kurdu sana?
 
Artı 0 Eksi
Recep Baltaş dedi:
Bir bellek testi yapar mısın?

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...
www.technopat.net www.technopat.net

Kod: 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck.
Arg2: fffff80760326ec9, Address of the instruction which caused the BugCheck.
Arg3: ffff85808f8d9920, Address of the context record for the exception that caused the BugCheck.
Arg4: 0000000000000000, zero.
KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 92.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 18996.

 Key : Analysis.Init.CPU.mSec
 Value: 249.

 Key : Analysis.Init.Elapsed.mSec
 Value: 13712.

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

 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_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 772fbcde.

WRONG_SYMBOLS_SIZE: 1046000.

FAULTING_MODULE: fffff80760000000 nt.

BUGCHECK_CODE: 3b.

BUGCHECK_P1: c0000005.

BUGCHECK_P2: fffff80760326ec9.

BUGCHECK_P3: ffff85808f8d9920.

BUGCHECK_P4: 0

CONTEXT: ffff85808f8d9920 -- (.cxr 0xffff85808f8d9920)
rax=ffffda0de9a57b08 rbx=ffffda0df0bec460 rcx=ffffda0ce9a57b08
rdx=0000000068547844 rsi=0000000000000000 rdi=ffffda0de9a57b08
rip=fffff80760326ec9 rsp=ffffd30473c4c910 rbp=0000000000000000
 r8=ffffda0df0bec460 r9=6d06f4d2baa07ff6 r10=0000fffff807606b
r11=ffff757a58a00000 r12=0000000000000000 r13=0000000000000000
r14=ffffda0dedd16080 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt+0x326ec9:
fffff807`60326ec9 48395908 cmp qword ptr [rcx+8],rbx ds:002b:ffffda0c`e9a57b10=????????????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffd304`73c4c910 00000000`00000000 : 00000000`68547844 ffffda0d`e9a57540 fffff807`606b0b37 ffffda0d`edd16080 : nt+0x326ec9

STACK_COMMAND: .cxr 0xffff85808f8d9920 ; kb.

EXCEPTION_CODE_STR: 772FBCDE.

EXCEPTION_STR: WRONG_SYMBOLS.

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols.

SYMBOL_NAME: nt_wrong_symbols!772FBCDE1046000

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_330513-171406_772FBCDE_nt_wrong_symbols!772FBCDE1046000

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {3fbc5df3-d18e-9a75-b220-c98d06b4672b}

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

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: fffff802373b4425, The address that the exception occurred at.
Arg3: ffffee02fc715e78, Parameter 0 of the exception.
Arg4: ffffbb00529e7920, Parameter 1 of the exception.

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 359.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 18934.

 Key : Analysis.Init.CPU.mSec
 Value: 171.

 Key : Analysis.Init.Elapsed.mSec
 Value: 13090.

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

 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_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 772fbcde.

WRONG_SYMBOLS_SIZE: 1046000.

FAULTING_MODULE: fffff8023b000000 nt.

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff802373b4425.

BUGCHECK_P3: ffffee02fc715e78.

BUGCHECK_P4: ffffbb00529e7920.

Unable to get size of nt!_MMPTE - probably bad symbols.
 ffffbb00529e7920.

EXCEPTION_PARAMETER1: ffffee02fc715e78.

EXCEPTION_PARAMETER2: ffffbb00529e7920.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffbb00`529e70a8 fffff802`3b50f82f : 00000000`0000001e ffffffff`c0000005 fffff802`373b4425 ffffee02`fc715e78 : nt+0x3f71b0
ffffbb00`529e70b0 00000000`0000001e : ffffffff`c0000005 fffff802`373b4425 ffffee02`fc715e78 ffffbb00`529e7920 : nt+0x50f82f
ffffbb00`529e70b8 ffffffff`c0000005 : fffff802`373b4425 ffffee02`fc715e78 ffffbb00`529e7920 00000000`00000000 : 0x1e.
ffffbb00`529e70c0 fffff802`373b4425 : ffffee02`fc715e78 ffffbb00`529e7920 00000000`00000000 ffffee02`fc715e78 : 0xffffffff`c0000005
ffffbb00`529e70c8 ffffee02`fc715e78 : ffffbb00`529e7920 ffffee02`fc715e78 ffffbb00`529e7210 fffff802`3b000000 : Ndu!NduOutboundTransportClassify+0x2b5
ffffbb00`529e7168 ffffbb00`529e7920 : ffffee02`fc715e78 ffffbb00`529e7210 fffff802`3b000000 ffffbb00`529e77c0 : 0xffffee02`fc715e78
ffffbb00`529e7170 ffffee02`fc715e78 : ffffbb00`529e7210 fffff802`3b000000 ffffbb00`529e77c0 fffff802`3b2f8458 : 0xffffbb00`529e7920
ffffbb00`529e7178 ffffbb00`529e7210 : fffff802`3b000000 ffffbb00`529e77c0 fffff802`3b2f8458 fffff802`3b400072 : 0xffffee02`fc715e78
ffffbb00`529e7180 fffff802`3b000000 : ffffbb00`529e77c0 fffff802`3b2f8458 fffff802`3b400072 fffff802`3b0d3ce0 : 0xffffbb00`529e7210
ffffbb00`529e7188 ffffbb00`529e77c0 : fffff802`3b2f8458 fffff802`3b400072 fffff802`3b0d3ce0 ffffbb00`529e7710 : nt.
ffffbb00`529e7190 fffff802`3b2f8458 : fffff802`3b400072 fffff802`3b0d3ce0 ffffbb00`529e7710 fffff802`3b3ccd30 : 0xffffbb00`529e77c0
ffffbb00`529e7198 fffff802`3b400072 : fffff802`3b0d3ce0 ffffbb00`529e7710 fffff802`3b3ccd30 00000000`00000000 : nt+0x2f8458
ffffbb00`529e71a0 fffff802`3b0d3ce0 : ffffbb00`529e7710 fffff802`3b3ccd30 00000000`00000000 ffffbb00`529e7760 : nt+0x400072
ffffbb00`529e71a8 ffffbb00`529e7710 : fffff802`3b3ccd30 00000000`00000000 ffffbb00`529e7760 fffff802`3b2e6dd7 : nt+0xd3ce0
ffffbb00`529e71b0 fffff802`3b3ccd30 : 00000000`00000000 ffffbb00`529e7760 fffff802`3b2e6dd7 ffffbb00`529e7710 : 0xffffbb00`529e7710
ffffbb00`529e71b8 00000000`00000000 : ffffbb00`529e7760 fffff802`3b2e6dd7 ffffbb00`529e7710 00000000`00000000 : nt+0x3ccd30

SYMBOL_NAME: nt_wrong_symbols!772FBCDE1046000

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .thread ; .cxr ; kb.

EXCEPTION_CODE_STR: 772FBCDE.

EXCEPTION_STR: WRONG_SYMBOLS.

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols.

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_330513-171406_772FBCDE_nt_wrong_symbols!772FBCDE1046000

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {3fbc5df3-d18e-9a75-b220-c98d06b4672b}

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

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: fffff8059b404425, The address that the exception occurred at.
Arg3: 0000000000000001, Parameter 0 of the exception.
Arg4: ffff9a87d8303200, Parameter 1 of the exception.

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 296.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 24083.

 Key : Analysis.Init.CPU.mSec
 Value: 202.

 Key : Analysis.Init.Elapsed.mSec
 Value: 13151.

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

 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_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 772fbcde.

WRONG_SYMBOLS_SIZE: 1046000.

FAULTING_MODULE: fffff80583e00000 nt.

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff8059b404425.

BUGCHECK_P3: 1

BUGCHECK_P4: ffff9a87d8303200.

WRITE_ADDRESS: *************************************************************************
*** ***
*** ***
*** 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: nt!_MMPFN ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_MMPTE ***
*** ***
*************************************************************************
Unable to get size of nt!_MMPTE - probably bad symbols.
 ffff9a87d8303200.

EXCEPTION_PARAMETER1: 0000000000000001.

EXCEPTION_PARAMETER2: ffff9a87d8303200.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
fffff805`87ea6158 fffff805`842f5a6e : 00000000`0000001e ffffffff`c0000005 fffff805`9b404425 00000000`00000001 : nt+0x3f71b0
fffff805`87ea6160 00000000`0000001e : ffffffff`c0000005 fffff805`9b404425 00000000`00000001 ffff9a87`d8303200 : nt+0x4f5a6e
fffff805`87ea6168 ffffffff`c0000005 : fffff805`9b404425 00000000`00000001 ffff9a87`d8303200 fffff805`87ea6720 : 0x1e.
fffff805`87ea6170 fffff805`9b404425 : 00000000`00000001 ffff9a87`d8303200 fffff805`87ea6720 fffff805`842f5a4c : 0xffffffff`c0000005
fffff805`87ea6178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ndu!NduOutboundTransportClassify+0x2b5

SYMBOL_NAME: nt_wrong_symbols!772FBCDE1046000

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .thread ; .cxr ; kb.

EXCEPTION_CODE_STR: 772FBCDE.

EXCEPTION_STR: WRONG_SYMBOLS.

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols.

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_330513-171406_772FBCDE_nt_wrong_symbols!772FBCDE1046000

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {3fbc5df3-d18e-9a75-b220-c98d06b4672b}

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

Bellek testi yap. Kullandığın Windows 10 sürümü eski ve hiç güncelleme yapmamışsın. Normalde zaten mavi ekran alman lazım. Yeşil ekran genelde Beta/Geliştirici sürümlerde oluyor. Bu Windows'u kim kurdu sana?
Genişletmek için tıkla...

Bu Windows'u bilgisayarı nasıl desem bilmiyorum ama telefoncu bir adam kurmuştu.
Hocam bu arada bellek testi yapamıyorum Browse'a tıkladığımda ise böyle bir görsel çıkıyor.

resim_2021-10-12_170002.png
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Neden Help klasörüne baktığınızı anlayamadım. Dosya memtest86-usb klasöründe.
Shura_Sama019 dedi:
Bu Windows'u bilgisayarı nasıl desem bilmiyorum ama telefoncu bir adam kurmuştu.
Genişletmek için tıkla...
Güncelleyin.
 
Artı 0 Eksi

Benzer konular

Emir Bozat
Windows 10 yeşil ekran hatası
Mesaj
4
Görüntüleme
368
kel584
kel584
linuxzen
Windows 10 yeşil ekran hatası
Mesaj
9
Görüntüleme
2B
linuxzen
linuxzen
O
Windows 10 MEMORY_MANAGEMENT hatası
2
Mesaj
19
Görüntüleme
1B
Enes3078
Enes3078
D
Windows 10 Memory_Management Hatası
Mesaj
2
Görüntüleme
577
Dilekci
D
Zaturcem
  • Kilitli
  • Çözüldü
Çözüm  Windows 10 MEMORY_MANAGEMENT hatası
Mesaj
2
Görüntüleme
925
Zaturcem
Zaturcem

Yeni konular

Yeni mesajlar

Geri
Yukarı