MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
Parameter 2 contains the referenced virtual address.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 0
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: 0
Key : Analysis.Memory.CommitPeak.Mb
Value: 45
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41287
BUGCHECK_P2: 30
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
fffff880`028cc578 fffff800`02c22d02 : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : 0xfffff800`02c88ec0
fffff880`028cc580 00000000`0000001a : 00000000`00041287 00000000`00000030 00000000`00000000 00000000`00000000 : 0xfffff800`02c22d02
fffff880`028cc588 00000000`00041287 : 00000000`00000030 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1a
fffff880`028cc590 00000000`00000030 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x41287
fffff880`028cc598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x30
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1a_41287
OS_VERSION: 7.1.7601.18717
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {fbb1dd26-a286-560b-f852-874d061cdd41}
Followup: MachineOwner
---------
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 00000000000000e6
Arg4: 000000e8000000cc
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mssmbios.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
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: 8
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 1a
BUGCHECK_P1: 5003
BUGCHECK_P2: fffff70001080000
BUGCHECK_P3: e6
BUGCHECK_P4: e8000000cc
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
DPC_STACK_BASE: FFFFF80000BA2FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9cfb0. Use (kF) and (!stackusage) to investigate stack usage.
MISALIGNED_IP:
intelppm+39c2
fffff880`03cdd9c2 0000 add byte ptr [rax],al
STACK_TEXT:
fffff800`00b9cc98 fffff800`02e8f669 : 00000000`001ded3f fffffa80`03860dd8 fffff800`03010cc0 00000000`00000002 : intelppm+0x39c2
fffff800`00b9cca0 fffff800`02e7db9c : fffff800`03002e80 fffff800`00000000 00000000`00000000 fffff880`01063f5c : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
SYMBOL_NAME: intelppm+39c2
MODULE_NAME: hardware
IMAGE_NAME: hardware
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_intelppm.sys
OS_VERSION: 7.1.7601.18717
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {e6544b9d-4668-8ff7-1695-9fca89d9159e}
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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002c7009a, The address that the exception occurred at
Arg3: 0000000000000002, Parameter 0 of the exception
Arg4: ffffffffffffff00, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
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: 1
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff80002c7009a
BUGCHECK_P3: 2
BUGCHECK_P4: ffffffffffffff00
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
FAILED_INSTRUCTION_ADDRESS:
nt!strncat+2a
fffff800`02c7009a fe ???
STACK_TEXT:
fffff880`04a995e8 fffff800`02cc4698 : 00000000`0000001e ffffffff`c000001d fffff800`02c7009a 00000000`00000002 : nt!KeBugCheckEx
fffff880`04a995f0 fffff800`02c78542 : fffff880`04a99dc8 fffff880`009e6180 fffff880`04a99e70 fffffa80`044f1b50 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`04a99c90 fffff800`02c7669f : fffff880`04a99e70 fffff880`04a99e02 fffffa80`0249a800 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`04a99e70 fffff800`02c7009a : 00000000`2f69cc92 fffffa80`044f1b50 00000000`00000002 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`04a9a000 00000000`2f69cc92 : fffffa80`044f1b50 00000000`00000002 00000000`00000000 fffff880`04a9a520 : nt!strncat+0x2a
fffff880`04a9a008 fffffa80`044f1b50 : 00000000`00000002 00000000`00000000 fffff880`04a9a520 00000000`00000000 : 0x2f69cc92
fffff880`04a9a010 00000000`00000002 : 00000000`00000000 fffff880`04a9a520 00000000`00000000 00000000`00000000 : 0xfffffa80`044f1b50
fffff880`04a9a018 00000000`00000000 : fffff880`04a9a520 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
SYMBOL_NAME: nt!strncat+2a
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 6.1.7601.18717
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!strncat+2a
OS_VERSION: 7.1.7601.18717
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {d1c7c579-0296-8821-c622-84915f0b9a22}
Followup: MachineOwner
---------
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: fffff88003fa8b8b, The address that the exception occurred at
Arg3: fffff8800306fd48, Exception Record Address
Arg4: fffff8800306f5a0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.Sec
Value: 1
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: 1
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88003fa8b8b
BUGCHECK_P3: fffff8800306fd48
BUGCHECK_P4: fffff8800306f5a0
EXCEPTION_RECORD: fffff8800306fd48 -- (.exr 0xfffff8800306fd48)
ExceptionAddress: fffff88003fa8b8b (dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x0000000000000267)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000010498b49
Attempt to read from address 0000000010498b49
CONTEXT: fffff8800306f5a0 -- (.cxr 0xfffff8800306f5a0)
rax=0000000010498b41 rbx=fffffa80034e35c0 rcx=fffff8a000fbe7e0
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80034fc440
rip=fffff88003fa8b8b rsp=fffff8800306ff80 rbp=fffff880030706e0
r8=0000000000000000 r9=0000000000000000 r10=fffff8a00104d000
r11=0000000000000022 r12=fffffa80034fc4a0 r13=0000000000000002
r14=fffff88003070cd0 r15=fffff88003070038
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x267:
fffff880`03fa8b8b 83780800 cmp dword ptr [rax+8],0 ds:002b:00000000`10498b49=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
READ_ADDRESS: fffff80003049068: Unable to get Flags value from nt!KdVersionBlock
fffff80003049068: Unable to get Flags value from nt!KdVersionBlock
fffff80003049068: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800031072e0
GetUlongPtrFromAddress: unable to read from fffff80003107490
0000000010498b49
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: 0000000010498b49
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`0306ff80 fffff880`03ef5001 : 00000000`00ffffff 00000000`00ffffff fffff880`030706e0 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x267
fffff880`0306ffd0 fffff880`03ed255e : 00000000`00000002 fffff880`030706e0 fffff8a0`00000000 fffff880`03070218 : dxgkrnl!DXGCONTEXT::PresentFromCdd+0x3c9
fffff880`030701e0 fffff960`006a4c9c : fffff900`c00c1020 00000000`00000030 00000000`00000030 fffff900`c071eb90 : dxgkrnl!DxgkCddPresent+0x1fa
fffff880`03070270 fffff960`006a606c : ffffffff`fffd74f6 00000000`0104002f 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x324
fffff880`030709b0 fffff800`0316cb8a : 00000000`0235c2c7 fffffa80`034b4b50 00000000`00000080 fffffa80`034bfb30 : cdd!PresentWorkerThread+0xd00
fffff880`03070d40 fffff800`02ebf8e6 : fffff880`009e6180 fffffa80`034b4b50 fffffa80`034ce060 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`03070d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_NAME: dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+267
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
IMAGE_VERSION: 6.1.7601.17514
STACK_COMMAND: .cxr 0xfffff8800306f5a0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+267
OS_VERSION: 7.1.7601.18717
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {5711417c-63af-1e79-4c75-9a37a64d79d9}
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: fffff96000093248, Address of the instruction which caused the bugcheck
Arg3: fffff8800291dac0, 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: 1
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: 7
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff96000093248
BUGCHECK_P3: fffff8800291dac0
BUGCHECK_P4: 0
CONTEXT: fffff8800291dac0 -- (.cxr 0xfffff8800291dac0)
rax=000000000000001a rbx=fffff900c07349f0 rcx=000000000104006b
rdx=fffff900c0200e58 rsi=00000000210401b6 rdi=000000000001009a
rip=fffff96000093248 rsp=fffff8800291e4a0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000099 r10=000000005e000000
r11=fffff8800291e498 r12=fffff900c2502cb0 r13=0000000000000000
r14=000000000000001a r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
win32k!SetEmptyRgn+0x4:
fffff960`00093248 8b056ed32600 mov eax,dword ptr [win32k!gZero+0xc (fffff960`003005bc)] ds:002b:fffff960`003005bc=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: LogonUI.exe
STACK_TEXT:
fffff880`0291e4a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SetEmptyRgn+0x4
SYMBOL_NAME: win32k!SetEmptyRgn+4
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
IMAGE_VERSION: 6.1.7601.17514
STACK_COMMAND: .cxr 0xfffff8800291dac0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_c0000005_win32k!SetEmptyRgn+4
OS_VERSION: 7.1.7601.18717
BUILDLAB_STR: win7sp1_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {ae18a052-773b-9bac-d89f-7f52a3ad0e73}
Followup: MachineOwner
---------
Sorun açık zaten. Geriye kalan RAM 4'den az değilse RAM sorunu olduğu açık.Tek RAM'ı çıkarıyorum, bu sefer "bip" sesi ötüyor görüntü gelmiyor.
Abi cevabın için teşekkür ederim. RAM'larım 2+1 3 GB. 1 GB liği ilk çıkardığımda hata çözülmüştü ancak 1 gün sonra açtığımda yine aynı şekilde mavi ekran verdi. WİNDOWS Bellek Tanımlama yaptım RAM'larda sıkıntı çıkmadı.Bu hatalar RAM ile ilgili. Ya RAM'lerin arızalı ya da işlemcinin soğutucusu aşırı sıkıldığından (Intel ise) sorun oluyor.
RAM testi yap bu yazılımla:
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
Kod:MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization. Parameter 2 contains the referenced virtual address. Arg2: 0000000000000030 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 0 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: 0 Key : Analysis.Memory.CommitPeak.Mb Value: 45 Key : Analysis.System Value: CreateObject Key : WER.CorruptModuleList Value: 1 ADDITIONAL_XML: 1 BUGCHECK_CODE: 1a BUGCHECK_P1: 41287 BUGCHECK_P2: 30 BUGCHECK_P3: 0 BUGCHECK_P4: 0 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: fffff880`028cc578 fffff800`02c22d02 : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : 0xfffff800`02c88ec0 fffff880`028cc580 00000000`0000001a : 00000000`00041287 00000000`00000030 00000000`00000000 00000000`00000000 : 0xfffff800`02c22d02 fffff880`028cc588 00000000`00041287 : 00000000`00000030 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1a fffff880`028cc590 00000000`00000030 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x41287 fffff880`028cc598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x30 SYMBOL_NAME: ANALYSIS_INCONCLUSIVE MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1a_41287 OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {fbb1dd26-a286-560b-f852-874d061cdd41} Followup: MachineOwner --------- MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 00000000000000e6 Arg4: 000000e8000000cc Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for mssmbios.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 1 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: 8 Key : Analysis.Memory.CommitPeak.Mb Value: 70 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 1a BUGCHECK_P1: 5003 BUGCHECK_P2: fffff70001080000 BUGCHECK_P3: e6 BUGCHECK_P4: e8000000cc CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System DPC_STACK_BASE: FFFFF80000BA2FB0 STACK_OVERFLOW: Stack Limit: fffff80000b9cfb0. Use (kF) and (!stackusage) to investigate stack usage. MISALIGNED_IP: intelppm+39c2 fffff880`03cdd9c2 0000 add byte ptr [rax],al STACK_TEXT: fffff800`00b9cc98 fffff800`02e8f669 : 00000000`001ded3f fffffa80`03860dd8 fffff800`03010cc0 00000000`00000002 : intelppm+0x39c2 fffff800`00b9cca0 fffff800`02e7db9c : fffff800`03002e80 fffff800`00000000 00000000`00000000 fffff880`01063f5c : nt!PoIdle+0x52a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c SYMBOL_NAME: intelppm+39c2 MODULE_NAME: hardware IMAGE_NAME: hardware STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: X64_IP_MISALIGNED_intelppm.sys OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {e6544b9d-4668-8ff7-1695-9fca89d9159e} 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: ffffffffc000001d, The exception code that was not handled Arg2: fffff80002c7009a, The address that the exception occurred at Arg3: 0000000000000002, Parameter 0 of the exception Arg4: ffffffffffffff00, Parameter 1 of the exception Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 1 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: 1 Key : Analysis.Memory.CommitPeak.Mb Value: 70 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc000001d BUGCHECK_P2: fffff80002c7009a BUGCHECK_P3: 2 BUGCHECK_P4: ffffffffffffff00 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe FAILED_INSTRUCTION_ADDRESS: nt!strncat+2a fffff800`02c7009a fe ??? STACK_TEXT: fffff880`04a995e8 fffff800`02cc4698 : 00000000`0000001e ffffffff`c000001d fffff800`02c7009a 00000000`00000002 : nt!KeBugCheckEx fffff880`04a995f0 fffff800`02c78542 : fffff880`04a99dc8 fffff880`009e6180 fffff880`04a99e70 fffffa80`044f1b50 : nt! ?? ::FNODOBFM::`string'+0x487ed fffff880`04a99c90 fffff800`02c7669f : fffff880`04a99e70 fffff880`04a99e02 fffffa80`0249a800 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`04a99e70 fffff800`02c7009a : 00000000`2f69cc92 fffffa80`044f1b50 00000000`00000002 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f fffff880`04a9a000 00000000`2f69cc92 : fffffa80`044f1b50 00000000`00000002 00000000`00000000 fffff880`04a9a520 : nt!strncat+0x2a fffff880`04a9a008 fffffa80`044f1b50 : 00000000`00000002 00000000`00000000 fffff880`04a9a520 00000000`00000000 : 0x2f69cc92 fffff880`04a9a010 00000000`00000002 : 00000000`00000000 fffff880`04a9a520 00000000`00000000 00000000`00000000 : 0xfffffa80`044f1b50 fffff880`04a9a018 00000000`00000000 : fffff880`04a9a520 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2 SYMBOL_NAME: nt!strncat+2a MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 6.1.7601.18717 STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!strncat+2a OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {d1c7c579-0296-8821-c622-84915f0b9a22} Followup: MachineOwner ---------
Bu hata ekran kartı kaynaklı gibi ama yine RAM arızası da buna sebep olabilir.
Kod: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: fffff88003fa8b8b, The address that the exception occurred at Arg3: fffff8800306fd48, Exception Record Address Arg4: fffff8800306f5a0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.Sec Value: 1 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: 1 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff88003fa8b8b BUGCHECK_P3: fffff8800306fd48 BUGCHECK_P4: fffff8800306f5a0 EXCEPTION_RECORD: fffff8800306fd48 -- (.exr 0xfffff8800306fd48) ExceptionAddress: fffff88003fa8b8b (dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x0000000000000267) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000010498b49 Attempt to read from address 0000000010498b49 CONTEXT: fffff8800306f5a0 -- (.cxr 0xfffff8800306f5a0) rax=0000000010498b41 rbx=fffffa80034e35c0 rcx=fffff8a000fbe7e0 rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80034fc440 rip=fffff88003fa8b8b rsp=fffff8800306ff80 rbp=fffff880030706e0 r8=0000000000000000 r9=0000000000000000 r10=fffff8a00104d000 r11=0000000000000022 r12=fffffa80034fc4a0 r13=0000000000000002 r14=fffff88003070cd0 r15=fffff88003070038 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x267: fffff880`03fa8b8b 83780800 cmp dword ptr [rax+8],0 ds:002b:00000000`10498b49=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: csrss.exe READ_ADDRESS: fffff80003049068: Unable to get Flags value from nt!KdVersionBlock fffff80003049068: Unable to get Flags value from nt!KdVersionBlock fffff80003049068: Unable to get Flags value from nt!KdVersionBlock Unable to get MmSystemRangeStart GetUlongPtrFromAddress: unable to read from fffff800031072e0 GetUlongPtrFromAddress: unable to read from fffff80003107490 0000000010498b49 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: 0000000010498b49 EXCEPTION_STR: 0xc0000005 STACK_TEXT: fffff880`0306ff80 fffff880`03ef5001 : 00000000`00ffffff 00000000`00ffffff fffff880`030706e0 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x267 fffff880`0306ffd0 fffff880`03ed255e : 00000000`00000002 fffff880`030706e0 fffff8a0`00000000 fffff880`03070218 : dxgkrnl!DXGCONTEXT::PresentFromCdd+0x3c9 fffff880`030701e0 fffff960`006a4c9c : fffff900`c00c1020 00000000`00000030 00000000`00000030 fffff900`c071eb90 : dxgkrnl!DxgkCddPresent+0x1fa fffff880`03070270 fffff960`006a606c : ffffffff`fffd74f6 00000000`0104002f 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x324 fffff880`030709b0 fffff800`0316cb8a : 00000000`0235c2c7 fffffa80`034b4b50 00000000`00000080 fffffa80`034bfb30 : cdd!PresentWorkerThread+0xd00 fffff880`03070d40 fffff800`02ebf8e6 : fffff880`009e6180 fffffa80`034b4b50 fffffa80`034ce060 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`03070d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_NAME: dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+267 MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys IMAGE_VERSION: 6.1.7601.17514 STACK_COMMAND: .cxr 0xfffff8800306f5a0 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+267 OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {5711417c-63af-1e79-4c75-9a37a64d79d9} Followup: MachineOwner ---------
Kod:SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff96000093248, Address of the instruction which caused the bugcheck Arg3: fffff8800291dac0, 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: 1 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: 7 Key : Analysis.Memory.CommitPeak.Mb Value: 83 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff96000093248 BUGCHECK_P3: fffff8800291dac0 BUGCHECK_P4: 0 CONTEXT: fffff8800291dac0 -- (.cxr 0xfffff8800291dac0) rax=000000000000001a rbx=fffff900c07349f0 rcx=000000000104006b rdx=fffff900c0200e58 rsi=00000000210401b6 rdi=000000000001009a rip=fffff96000093248 rsp=fffff8800291e4a0 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000099 r10=000000005e000000 r11=fffff8800291e498 r12=fffff900c2502cb0 r13=0000000000000000 r14=000000000000001a r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 win32k!SetEmptyRgn+0x4: fffff960`00093248 8b056ed32600 mov eax,dword ptr [win32k!gZero+0xc (fffff960`003005bc)] ds:002b:fffff960`003005bc=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: LogonUI.exe STACK_TEXT: fffff880`0291e4a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SetEmptyRgn+0x4 SYMBOL_NAME: win32k!SetEmptyRgn+4 MODULE_NAME: win32k IMAGE_NAME: win32k.sys IMAGE_VERSION: 6.1.7601.17514 STACK_COMMAND: .cxr 0xfffff8800291dac0 ; kb FAILURE_BUCKET_ID: X64_0x3B_c0000005_win32k!SetEmptyRgn+4 OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {ae18a052-773b-9bac-d89f-7f52a3ad0e73} Followup: MachineOwner ---------
Windows ile değil Memtest86 ile test yap.
Bu hatalar RAM ile ilgili. Ya RAM'lerin arızalı ya da işlemcinin soğutucusu aşırı sıkıldığından (Intel ise) sorun oluyor.
RAM testi yap bu yazılımla:
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
Kod:MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization. Parameter 2 contains the referenced virtual address. Arg2: 0000000000000030 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 0 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: 0 Key : Analysis.Memory.CommitPeak.Mb Value: 45 Key : Analysis.System Value: CreateObject Key : WER.CorruptModuleList Value: 1 ADDITIONAL_XML: 1 BUGCHECK_CODE: 1a BUGCHECK_P1: 41287 BUGCHECK_P2: 30 BUGCHECK_P3: 0 BUGCHECK_P4: 0 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: fffff880`028cc578 fffff800`02c22d02 : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : 0xfffff800`02c88ec0 fffff880`028cc580 00000000`0000001a : 00000000`00041287 00000000`00000030 00000000`00000000 00000000`00000000 : 0xfffff800`02c22d02 fffff880`028cc588 00000000`00041287 : 00000000`00000030 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1a fffff880`028cc590 00000000`00000030 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x41287 fffff880`028cc598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x30 SYMBOL_NAME: ANALYSIS_INCONCLUSIVE MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1a_41287 OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {fbb1dd26-a286-560b-f852-874d061cdd41} Followup: MachineOwner --------- MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 00000000000000e6 Arg4: 000000e8000000cc Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for mssmbios.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 1 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: 8 Key : Analysis.Memory.CommitPeak.Mb Value: 70 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 1a BUGCHECK_P1: 5003 BUGCHECK_P2: fffff70001080000 BUGCHECK_P3: e6 BUGCHECK_P4: e8000000cc CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System DPC_STACK_BASE: FFFFF80000BA2FB0 STACK_OVERFLOW: Stack Limit: fffff80000b9cfb0. Use (kF) and (!stackusage) to investigate stack usage. MISALIGNED_IP: intelppm+39c2 fffff880`03cdd9c2 0000 add byte ptr [rax],al STACK_TEXT: fffff800`00b9cc98 fffff800`02e8f669 : 00000000`001ded3f fffffa80`03860dd8 fffff800`03010cc0 00000000`00000002 : intelppm+0x39c2 fffff800`00b9cca0 fffff800`02e7db9c : fffff800`03002e80 fffff800`00000000 00000000`00000000 fffff880`01063f5c : nt!PoIdle+0x52a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c SYMBOL_NAME: intelppm+39c2 MODULE_NAME: hardware IMAGE_NAME: hardware STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: X64_IP_MISALIGNED_intelppm.sys OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {e6544b9d-4668-8ff7-1695-9fca89d9159e} 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: ffffffffc000001d, The exception code that was not handled Arg2: fffff80002c7009a, The address that the exception occurred at Arg3: 0000000000000002, Parameter 0 of the exception Arg4: ffffffffffffff00, Parameter 1 of the exception Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 1 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: 1 Key : Analysis.Memory.CommitPeak.Mb Value: 70 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc000001d BUGCHECK_P2: fffff80002c7009a BUGCHECK_P3: 2 BUGCHECK_P4: ffffffffffffff00 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe FAILED_INSTRUCTION_ADDRESS: nt!strncat+2a fffff800`02c7009a fe ??? STACK_TEXT: fffff880`04a995e8 fffff800`02cc4698 : 00000000`0000001e ffffffff`c000001d fffff800`02c7009a 00000000`00000002 : nt!KeBugCheckEx fffff880`04a995f0 fffff800`02c78542 : fffff880`04a99dc8 fffff880`009e6180 fffff880`04a99e70 fffffa80`044f1b50 : nt! ?? ::FNODOBFM::`string'+0x487ed fffff880`04a99c90 fffff800`02c7669f : fffff880`04a99e70 fffff880`04a99e02 fffffa80`0249a800 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`04a99e70 fffff800`02c7009a : 00000000`2f69cc92 fffffa80`044f1b50 00000000`00000002 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f fffff880`04a9a000 00000000`2f69cc92 : fffffa80`044f1b50 00000000`00000002 00000000`00000000 fffff880`04a9a520 : nt!strncat+0x2a fffff880`04a9a008 fffffa80`044f1b50 : 00000000`00000002 00000000`00000000 fffff880`04a9a520 00000000`00000000 : 0x2f69cc92 fffff880`04a9a010 00000000`00000002 : 00000000`00000000 fffff880`04a9a520 00000000`00000000 00000000`00000000 : 0xfffffa80`044f1b50 fffff880`04a9a018 00000000`00000000 : fffff880`04a9a520 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2 SYMBOL_NAME: nt!strncat+2a MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 6.1.7601.18717 STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!strncat+2a OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {d1c7c579-0296-8821-c622-84915f0b9a22} Followup: MachineOwner ---------
Bu hata ekran kartı kaynaklı gibi ama yine RAM arızası da buna sebep olabilir...
Kod: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: fffff88003fa8b8b, The address that the exception occurred at Arg3: fffff8800306fd48, Exception Record Address Arg4: fffff8800306f5a0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.Sec Value: 1 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: 1 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff88003fa8b8b BUGCHECK_P3: fffff8800306fd48 BUGCHECK_P4: fffff8800306f5a0 EXCEPTION_RECORD: fffff8800306fd48 -- (.exr 0xfffff8800306fd48) ExceptionAddress: fffff88003fa8b8b (dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x0000000000000267) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000010498b49 Attempt to read from address 0000000010498b49 CONTEXT: fffff8800306f5a0 -- (.cxr 0xfffff8800306f5a0) rax=0000000010498b41 rbx=fffffa80034e35c0 rcx=fffff8a000fbe7e0 rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80034fc440 rip=fffff88003fa8b8b rsp=fffff8800306ff80 rbp=fffff880030706e0 r8=0000000000000000 r9=0000000000000000 r10=fffff8a00104d000 r11=0000000000000022 r12=fffffa80034fc4a0 r13=0000000000000002 r14=fffff88003070cd0 r15=fffff88003070038 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x267: fffff880`03fa8b8b 83780800 cmp dword ptr [rax+8],0 ds:002b:00000000`10498b49=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: csrss.exe READ_ADDRESS: fffff80003049068: Unable to get Flags value from nt!KdVersionBlock fffff80003049068: Unable to get Flags value from nt!KdVersionBlock fffff80003049068: Unable to get Flags value from nt!KdVersionBlock Unable to get MmSystemRangeStart GetUlongPtrFromAddress: unable to read from fffff800031072e0 GetUlongPtrFromAddress: unable to read from fffff80003107490 0000000010498b49 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: 0000000010498b49 EXCEPTION_STR: 0xc0000005 STACK_TEXT: fffff880`0306ff80 fffff880`03ef5001 : 00000000`00ffffff 00000000`00ffffff fffff880`030706e0 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x267 fffff880`0306ffd0 fffff880`03ed255e : 00000000`00000002 fffff880`030706e0 fffff8a0`00000000 fffff880`03070218 : dxgkrnl!DXGCONTEXT::PresentFromCdd+0x3c9 fffff880`030701e0 fffff960`006a4c9c : fffff900`c00c1020 00000000`00000030 00000000`00000030 fffff900`c071eb90 : dxgkrnl!DxgkCddPresent+0x1fa fffff880`03070270 fffff960`006a606c : ffffffff`fffd74f6 00000000`0104002f 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x324 fffff880`030709b0 fffff800`0316cb8a : 00000000`0235c2c7 fffffa80`034b4b50 00000000`00000080 fffffa80`034bfb30 : cdd!PresentWorkerThread+0xd00 fffff880`03070d40 fffff800`02ebf8e6 : fffff880`009e6180 fffffa80`034b4b50 fffffa80`034ce060 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`03070d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_NAME: dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+267 MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys IMAGE_VERSION: 6.1.7601.17514 STACK_COMMAND: .cxr 0xfffff8800306f5a0 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+267 OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {5711417c-63af-1e79-4c75-9a37a64d79d9} Followup: MachineOwner ---------
Kod:SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff96000093248, Address of the instruction which caused the bugcheck Arg3: fffff8800291dac0, 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: 1 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: 7 Key : Analysis.Memory.CommitPeak.Mb Value: 83 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff96000093248 BUGCHECK_P3: fffff8800291dac0 BUGCHECK_P4: 0 CONTEXT: fffff8800291dac0 -- (.cxr 0xfffff8800291dac0) rax=000000000000001a rbx=fffff900c07349f0 rcx=000000000104006b rdx=fffff900c0200e58 rsi=00000000210401b6 rdi=000000000001009a rip=fffff96000093248 rsp=fffff8800291e4a0 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000099 r10=000000005e000000 r11=fffff8800291e498 r12=fffff900c2502cb0 r13=0000000000000000 r14=000000000000001a r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 win32k!SetEmptyRgn+0x4: fffff960`00093248 8b056ed32600 mov eax,dword ptr [win32k!gZero+0xc (fffff960`003005bc)] ds:002b:fffff960`003005bc=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: LogonUI.exe STACK_TEXT: fffff880`0291e4a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SetEmptyRgn+0x4 SYMBOL_NAME: win32k!SetEmptyRgn+4 MODULE_NAME: win32k IMAGE_NAME: win32k.sys IMAGE_VERSION: 6.1.7601.17514 STACK_COMMAND: .cxr 0xfffff8800291dac0 ; kb FAILURE_BUCKET_ID: X64_0x3B_c0000005_win32k!SetEmptyRgn+4 OS_VERSION: 7.1.7601.18717 BUILDLAB_STR: win7sp1_gdr OSPLATFORM_TYPE: x64 OSNAME: Windows 7 FAILURE_ID_HASH: {ae18a052-773b-9bac-d89f-7f52a3ad0e73} Followup: MachineOwner ---------