O zaman eski hâline çekmeyi deneyin. Belki sorunun kaynağı RAM'ler olabilir.Bu olaylar RAM'i 3466MHz'ye çekince başladı.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80142a72982, The address that the exception occurred at
Arg3: ffffbd05b03878d8, Exception Record Address
Arg4: ffffbd05b0387110, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 5671
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 21374
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
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: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80142a72982
BUGCHECK_P3: ffffbd05b03878d8
BUGCHECK_P4: ffffbd05b0387110
EXCEPTION_RECORD: ffffbd05b03878d8 -- (.exr 0xffffbd05b03878d8)
ExceptionAddress: fffff80142a72982 (dxgmms2!VidSchiAdjustWorkerThreadPriority+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000990
Attempt to read from address 0000000000000990
CONTEXT: ffffbd05b0387110 -- (.cxr 0xffffbd05b0387110)
rax=ffff860320989000 rbx=ffff86032abc0010 rcx=ffff86032abc0010
rdx=0000000000000000 rsi=ffff860325ecf010 rdi=0000000000000000
rip=fffff80142a72982 rsp=ffffbd05b0387b10 rbp=ffff86032091a000
r8=ffff860319c428c0 r9=0000000000000000 r10=fffff801325421b0
r11=ffffbd05b0387b60 r12=0000000000000000 r13=0000000000000000
r14=ffff86032091a000 r15=ffff860320989000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
dxgmms2!VidSchiAdjustWorkerThreadPriority+0x12:
fffff801`42a72982 8b8790090000 mov eax,dword ptr [rdi+990h] ds:002b:00000000`00000990=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80132efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80132e0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80132e0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000990
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000990
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffbd05`b0387b10 fffff801`42aeadb3 : ffff8603`25f5d010 ffff8603`25ecf010 ffff8603`2abc0010 00000000`00000000 : dxgmms2!VidSchiAdjustWorkerThreadPriority+0x12
ffffbd05`b0387b80 fffff801`42aeacfa : ffff8603`2091a400 fffff801`42aeac30 ffff8603`2091a000 ffffd480`7b740100 : dxgmms2!VidSchiRun_PriorityTable+0xa3
ffffbd05`b0387bd0 fffff801`324a2ae5 : ffff8603`208cc080 fffff801`00000001 ffff8603`2091a000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffbd05`b0387c10 fffff801`325fbbf8 : ffffd480`7b740180 ffff8603`208cc080 fffff801`324a2a90 c36b1a6e`cb623727 : nt!PspSystemThreadStartup+0x55
ffffbd05`b0387c60 00000000`00000000 : ffffbd05`b0388000 ffffbd05`b0382000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiAdjustWorkerThreadPriority+12
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.546
STACK_COMMAND: .cxr 0xffffbd05b0387110 ; kb
BUCKET_ID_FUNC_OFFSET: 12
FAILURE_BUCKET_ID: AV_dxgmms2!VidSchiAdjustWorkerThreadPriority
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8df3c829-26e9-7f3c-e865-4e37e1a8d040}
Followup: MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8057bec16fd, Address of the instruction which caused the bugcheck
Arg3: fffff18f5f7867a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6342
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 53300
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
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: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff8057bec16fd
BUGCHECK_P3: fffff18f5f7867a0
BUGCHECK_P4: 0
CONTEXT: fffff18f5f7867a0 -- (.cxr 0xfffff18f5f7867a0)
rax=fff7f8057bb08738 rbx=00000000c000000d rcx=ffff8002c85a3000
rdx=fffff18f5f7876b8 rsi=fffff18f5f7876b8 rdi=ffff8002c85a3000
rip=fffff8057bec16fd rsp=fffff18f5f7871a0 rbp=fffff18f5f7872a0
r8=fffff8057bb0d590 r9=fffff18f5f787224 r10=0000000000000000
r11=ffffb8fc80000000 r12=0000000000000000 r13=fffff8057bb0d590
r14=fffff18f5f7876b8 r15=00000000c000000d
iopl=0 nv up ei pl nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050213
nvlddmkm+0xc416fd:
fffff805`7bec16fd ff5010 call qword ptr [rax+10h] ds:002b:fff7f805`7bb08748=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csgo.exe
STACK_TEXT:
fffff18f`5f7871a0 00000000`c000000d : fffff18f`5f7872a0 fffff18f`5f7876b8 00000000`00000000 00000000`00000001 : nvlddmkm+0xc416fd
fffff18f`5f7871a8 fffff18f`5f7872a0 : fffff18f`5f7876b8 00000000`00000000 00000000`00000001 00000000`00000000 : 0xc000000d
fffff18f`5f7871b0 fffff18f`5f7876b8 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffff18f`5f7872a0
fffff18f`5f7871b8 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff18f`5f7876b8
SYMBOL_NAME: nvlddmkm+c416fd
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff18f5f7867a0 ; kb
BUCKET_ID_FUNC_OFFSET: c416fd
FAILURE_BUCKET_ID: 0x3B_c0000005_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {63c41bff-3ea4-15a0-a72c-26a548d17abe}
Followup: MachineOwner
---------
XMP ayarını şimdilik kapatın. MemTest86 yaparsanız iyi olur.@yika38 belleklere overclock yapmıştım, "Thread" yazınca ondan şüphe etmedim değil.
Corsair SSD Toolbox yazılımı var ama nasıl kullanıldığını bilmiyorum.SSD için bir program var mi?
Manuel yapınca bu sıkıntılar başladı gibi XMP ile hiç sorun yaşamamıştım. SSD Toshiba ondan resim atabilirim. As SSD ile test yaptığımda bir sorun yoktu.XMP ayarını şimdilik kapatın.
Ayarı eski hâline getirmeyi deneyin o zaman.Manuel yapınca bu sıkıntılar başladı gibi, XMP ile hiç sorun yaşamamıştım.
Umarım bir TR200 vakası değildir ama bilmiyorum, mavi ekranlarda sorun ekran kartında gibi duruyordu. FurMark ile test yapabilirsiniz. OCCT'yi de deneyebilirsiniz ancak OCCT çok sağlam yük bindiriyor, bu da beni biraz çekindiriyor.SSD Toshiba, ondan resim atabilirim.
OCZ Utility'in ana sayfasından resim atabilir misiniz?
Yok daha bitmedi. Altta 3 yazıyor onda 8'de vardi, dogru secmis miyim? Test bitsin yine hata verirse onu da deneyecegim. Bu olaylar RAM'i 3466MHz'ye cekince basladı.Anladığım kadarıyla 1 saate yakın test yaptınız.
O zaman eski hâline çekmeyi deneyin. Belki sorunun kaynağı RAM'ler olabilir.Bu olaylar RAM'i 3466MHz'ye çekince başladı.
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.