Çözüldü SYSTEM_SERVICE_EXCEPTION mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Charles Vane

Kilopat
Katılım
28 Nisan 2017
Mesajlar
160
Daha fazla  
Cinsiyet
Erkek
Başlıkta belirttiğim gibi mavi ekran hatası aldığım için temiz kurulum yaptım. Fakat tekrardan mavi ekran hatası vermeye başladı. Minidump dosyalarım ektedir.
Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80637643eff, Address of the instruction which caused the bugcheck
Arg3: ffffae0596ad3330, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-2JFVSR6

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 72

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80637643eff

BUGCHECK_P3: ffffae0596ad3330

BUGCHECK_P4: 0

CONTEXT:  ffffae0596ad3330 -- (.cxr 0xffffae0596ad3330)
rax=0000000000000060 rbx=ffffca0654cd90c8 rcx=0000000000000060
rdx=0000000000000065 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80637643eff rsp=ffffae0596ad3d20 rbp=ffffca0654cd9010
r8=000000000000010b  r9=ffffca06509fc000 r10=fffff806298d8880
r11=ffff9304b56ef000 r12=0000000000000000 r13=ffff9304b57d3000
r14=ffff9304b92d3a68 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=00050246
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+0x11f:
fffff806`37643eff 0fbae20d        bt      edx,0Dh
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steamwebhelper.exe

STACK_TEXT:
ffffae05`96ad3d20 fffff806`375d2b25 : ffffca06`47a8ed01 ffffca06`4fc4c5a0 ffff3796`00000001 ffffae05`96ad4a30 : dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+0x11f
ffffae05`96ad3db0 fffff806`34d903d5 : 00000000`00000000 ffff9304`b92d39a0 ffff9304`b92d39a0 ffffae05`96ad4900 : dxgmms2!VidMmReferenceWrittenPrimaries+0x35
ffffae05`96ad3e00 fffff806`34d8fe67 : ffffca06`47a8ede0 ffffae05`96ad4900 ffffae05`96ad4900 ffffca06`47a8ede0 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x3b5
ffffae05`96ad45d0 fffff806`34d9063a : ffff3796`f9c8b427 ffff9304`b9c72080 ffffca06`54cd9010 0000008b`8037e1a0 : dxgkrnl!DxgkSubmitCommandInternal+0x557
ffffae05`96ad4ac0 fffff806`299d2918 : ffff9304`b9c72080 00000002`02580000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommand+0x5a
ffffae05`96ad4b00 00007fff`430b5a44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000008b`8037e0d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`430b5a44


SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.18362.10022

STACK_COMMAND:  .cxr 0xffffae0596ad3330 ; kb

BUCKET_ID_FUNC_OFFSET:  11f

FAILURE_BUCKET_ID:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ca4aec34-89bd-680a-ea1d-bac636b5bd7d}

Followup:     MachineOwner
 
Çözüm
Sıkıntı yaşayacağınızı sanmıyorum fakat eğer ileride tekrar aynısından bir tane daha alırım gibi bir düşünce varsa yapmayın yine bellek problemleri ile karşıla bilirsiniz, eğer 16 GB bellek kullanacaksan direk kit bellek al.
Bellek hatası gibi duruyor, daha önce Memtest86 testi yaptın mı?
Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80637643eff, Address of the instruction which caused the bugcheck
Arg3: ffffae0596ad3330, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80637643eff

BUGCHECK_P3: ffffae0596ad3330

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - <Unable to get error code text>

FAULTING_IP:
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f
fffff806`37643eff 0fbae20d        bt      edx,0Dh

CONTEXT:  ffffae0596ad3330 -- (.cxr 0xffffae0596ad3330)
rax=0000000000000060 rbx=ffffca0654cd90c8 rcx=0000000000000060
rdx=0000000000000065 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80637643eff rsp=ffffae0596ad3d20 rbp=ffffca0654cd9010
 r8=000000000000010b  r9=ffffca06509fc000 r10=fffff806298d8880
r11=ffff9304b56ef000 r12=0000000000000000 r13=ffff9304b57d3000
r14=ffff9304b92d3a68 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=00050246
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+0x11f:
fffff806`37643eff 0fbae20d        bt      edx,0Dh
Resetting default scope

BUGCHECK_STR:  0x3B_c000001d

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  steamwebhelper.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-22-2020 00:36:28.0200

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff806375d2b25 to fffff80637643eff

STACK_TEXT: 
ffffae05`96ad3d20 fffff806`375d2b25 : ffffca06`47a8ed01 ffffca06`4fc4c5a0 ffff3796`00000001 ffffae05`96ad4a30 : dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+0x11f
ffffae05`96ad3db0 fffff806`34d903d5 : 00000000`00000000 ffff9304`b92d39a0 ffff9304`b92d39a0 ffffae05`96ad4900 : dxgmms2!VidMmReferenceWrittenPrimaries+0x35
ffffae05`96ad3e00 fffff806`34d8fe67 : ffffca06`47a8ede0 ffffae05`96ad4900 ffffae05`96ad4900 ffffca06`47a8ede0 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x3b5
ffffae05`96ad45d0 fffff806`34d9063a : ffff3796`f9c8b427 ffff9304`b9c72080 ffffca06`54cd9010 0000008b`8037e1a0 : dxgkrnl!DxgkSubmitCommandInternal+0x557
ffffae05`96ad4ac0 fffff806`299d2918 : ffff9304`b9c72080 00000002`02580000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommand+0x5a
ffffae05`96ad4b00 00007fff`430b5a44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000008b`8037e0d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`430b5a44


THREAD_SHA1_HASH_MOD_FUNC:  f3407c3c81a72aaf9ccf18ec0f7d14e2056c7126

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7a5d68114cec3073283dcec99743f01fbe9bfc39

THREAD_SHA1_HASH_MOD:  8c65e1d066c69c9846699fdc332d91495802a2d2

FOLLOWUP_IP:
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f
fffff806`37643eff 0fbae20d        bt      edx,0Dh

FAULT_INSTR_CODE:  de2ba0f

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  79e12d93

IMAGE_VERSION:  10.0.18362.10022

STACK_COMMAND:  .cxr 0xffffae0596ad3330 ; kb

BUCKET_ID_FUNC_OFFSET:  11f

FAILURE_BUCKET_ID:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

BUCKET_ID:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

PRIMARY_PROBLEM_CLASS:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

TARGET_TIME:  2020-01-21T21:07:43.000Z

OSBUILD:  18362

OSSERVICEPACK:  327

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2031-02-06 14:47:47

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  279e6

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_c000001d_dxgmms2!vidmm_global::vidmmreferencewrittenprimaries

FAILURE_ID_HASH:  {ca4aec34-89bd-680a-ea1d-bac636b5bd7d}

Followup:     MachineOwner
---------
 
Bellek hatası gibi duruyor, daha önce Memtest86 testi yaptın mı?
Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80637643eff, Address of the instruction which caused the bugcheck
Arg3: ffffae0596ad3330, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80637643eff

BUGCHECK_P3: ffffae0596ad3330

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - <Unable to get error code text>

FAULTING_IP:
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f
fffff806`37643eff 0fbae20d        bt      edx,0Dh

CONTEXT:  ffffae0596ad3330 -- (.cxr 0xffffae0596ad3330)
rax=0000000000000060 rbx=ffffca0654cd90c8 rcx=0000000000000060
rdx=0000000000000065 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80637643eff rsp=ffffae0596ad3d20 rbp=ffffca0654cd9010
r8=000000000000010b  r9=ffffca06509fc000 r10=fffff806298d8880
r11=ffff9304b56ef000 r12=0000000000000000 r13=ffff9304b57d3000
r14=ffff9304b92d3a68 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=00050246
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+0x11f:
fffff806`37643eff 0fbae20d        bt      edx,0Dh
Resetting default scope

BUGCHECK_STR:  0x3B_c000001d

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  steamwebhelper.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-22-2020 00:36:28.0200

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff806375d2b25 to fffff80637643eff

STACK_TEXT:
ffffae05`96ad3d20 fffff806`375d2b25 : ffffca06`47a8ed01 ffffca06`4fc4c5a0 ffff3796`00000001 ffffae05`96ad4a30 : dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+0x11f
ffffae05`96ad3db0 fffff806`34d903d5 : 00000000`00000000 ffff9304`b92d39a0 ffff9304`b92d39a0 ffffae05`96ad4900 : dxgmms2!VidMmReferenceWrittenPrimaries+0x35
ffffae05`96ad3e00 fffff806`34d8fe67 : ffffca06`47a8ede0 ffffae05`96ad4900 ffffae05`96ad4900 ffffca06`47a8ede0 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x3b5
ffffae05`96ad45d0 fffff806`34d9063a : ffff3796`f9c8b427 ffff9304`b9c72080 ffffca06`54cd9010 0000008b`8037e1a0 : dxgkrnl!DxgkSubmitCommandInternal+0x557
ffffae05`96ad4ac0 fffff806`299d2918 : ffff9304`b9c72080 00000002`02580000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommand+0x5a
ffffae05`96ad4b00 00007fff`430b5a44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000008b`8037e0d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`430b5a44


THREAD_SHA1_HASH_MOD_FUNC:  f3407c3c81a72aaf9ccf18ec0f7d14e2056c7126

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7a5d68114cec3073283dcec99743f01fbe9bfc39

THREAD_SHA1_HASH_MOD:  8c65e1d066c69c9846699fdc332d91495802a2d2

FOLLOWUP_IP:
dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f
fffff806`37643eff 0fbae20d        bt      edx,0Dh

FAULT_INSTR_CODE:  de2ba0f

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries+11f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  79e12d93

IMAGE_VERSION:  10.0.18362.10022

STACK_COMMAND:  .cxr 0xffffae0596ad3330 ; kb

BUCKET_ID_FUNC_OFFSET:  11f

FAILURE_BUCKET_ID:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

BUCKET_ID:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

PRIMARY_PROBLEM_CLASS:  0x3B_c000001d_dxgmms2!VIDMM_GLOBAL::VidMmReferenceWrittenPrimaries

TARGET_TIME:  2020-01-21T21:07:43.000Z

OSBUILD:  18362

OSSERVICEPACK:  327

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2031-02-06 14:47:47

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  279e6

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_c000001d_dxgmms2!vidmm_global::vidmmreferencewrittenprimaries

FAILURE_ID_HASH:  {ca4aec34-89bd-680a-ea1d-bac636b5bd7d}

Followup:     MachineOwner
---------
Evet bellek testi yaptım. 3000MHz ve 1.35V ile çalıştırmaya çalışınca 13 adet hata veriyordu. 2933 hızında test yaptım hata çıkmadı. Bir süre öyle kullandım fakat yine ara ara mavi ekran vermeye başlayınca en sonunda bugün temiz kurulum yaptım. Tekrardan denemek için BIOS üzerinden belleğimi D.O.C.P ile 3000MHz hızına voltajı da 1.36 olarak ayarlardım ki yine mavi ekran verdi. Bellekleri 2133 hızında da kullanmak istemiyorum açıkcası. Çözüm yolu yok mudur bunun? Anakartım B450 Prime Plus. Belleğim ise Corsair vengaence DDR4 8 GB.
 
2133MHz'de çalıştır demiyorum, 2933MHz'de değil de 2666MHz gibi değerlerde denedin mi?
2133 kısmını yanlış yazmışım. 2933 altında da kullanmak istemiyorum olacaktı. Denemedim. Bu gidişle mecburen öyle kullanacağım gibi. Fakat bir şekilde 3000MHz olarak kullanma şansım yok mudur bu illetleri?
 
Maalesef yok, belleği farklı bir sistemde XMP açık şekilde Memtest86 testi yapın(Intel sistem), orada da kırmızı hatalar alırsanız fotoğrafını çekip, belleği garantiye gönderin.
Peki teşekkür ederim. Bu RAM'i bir şekilde elimden çıkartıp ASUS'un kendi sitesinde belirttiği Anakart ile uyumlu 3200Mhz olanlarından alsam yine bu sıkıntıyı yaşar mıyım?
Uyumlu belleklerden birisi.
 
Sıkıntı yaşayacağınızı sanmıyorum fakat eğer ileride tekrar aynısından bir tane daha alırım gibi bir düşünce varsa yapmayın yine bellek problemleri ile karşıla bilirsiniz, eğer 16 GB bellek kullanacaksan direk kit bellek al.
 
Çözüm
Uyarı! Bu konu 6 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.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Geri
Yukarı