EgeMen67
Hectopat
- Katılım
- 5 Nisan 2020
- Mesajlar
- 9
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) hatası
- Konuyu başlatan EgeMen67
- Başlangıç Tarihi
- Mesaj 13
- Görüntüleme 1.013
KS
KS
EgeMen67
Hectopat
- Katılım
- 5 Nisan 2020
- Mesajlar
- 9
Yardımınız için teşekkür ederim. Dediğiniz her şeyi yaptıktan sonra yine aynı sorunu yaşarsam buraya tekrar cevap yazarım eğer ilgilenirseniz tabii ki.
Muhtemelen ekran kartında donanımsal bir sorun var. Kartın marka/modeli neydi?
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: fffff8800493b805, The address that the exception occurred at
Arg3: fffff88006b1fca8, Exception Record Address
Arg4: fffff88006b1f4e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1749
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3967
Key : Analysis.Init.CPU.mSec
Value: 718
Key : Analysis.Init.Elapsed.mSec
Value: 36422
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8800493b805
BUGCHECK_P3: fffff88006b1fca8
BUGCHECK_P4: fffff88006b1f4e0
EXCEPTION_RECORD: fffff88006b1fca8 -- (.exr 0xfffff88006b1fca8)
ExceptionAddress: fffff8800493b805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88006b1f4e0 -- (.cxr 0xfffff88006b1f4e0)
rax=0000000000000000 rbx=fffffa800b348440 rcx=af4bf467c96c0000
rdx=8000000000000020 rsi=fffffa800b348440 rdi=0000000000000000
rip=fffff8800493b805 rsp=fffff88006b1fee0 rbp=fffffa8008d81010
r8=fffff88004436870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007c44010 r12=000000000000000f r13=fffff88006b202f8
r14=0000000000000000 r15=fffffa8008acb000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0xd2a805:
fffff880`0493b805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff803769d4370
GetUlongPtrFromAddress: unable to read from fffff803769d4488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`06b1fee0 fffff880`048e0c90 : fffff880`04868ffd fffff880`0373ac1d fffff880`0384f7ac fffff880`0385d75f : nvlddmkm+0xd2a805
fffff880`06b1fee8 fffff880`04868ffd : fffff880`0373ac1d fffff880`0384f7ac fffff880`0385d75f fffff880`0384c928 : nvlddmkm+0xccfc90
fffff880`06b1fef0 fffff880`0373ac1d : fffff880`0384f7ac fffff880`0385d75f fffff880`0384c928 fffff880`03845614 : nvlddmkm+0xc57ffd
fffff880`06b1fef8 fffff880`0384f7ac : fffff880`0385d75f fffff880`0384c928 fffff880`03845614 fffff880`03865ba5 : dxgkrnl+0x8dc1d
fffff880`06b1ff00 fffff880`0385d75f : fffff880`0384c928 fffff880`03845614 fffff880`03865ba5 fffff880`03865662 : dxgmms1+0x287ac
fffff880`06b1ff08 fffff880`0384c928 : fffff880`03845614 fffff880`03865ba5 fffff880`03865662 00000000`00000001 : dxgmms1+0x3675f
fffff880`06b1ff10 fffff880`03845614 : fffff880`03865ba5 fffff880`03865662 00000000`00000001 ffff57cb`f2d6374c : dxgmms1+0x25928
fffff880`06b1ff18 fffff880`03865ba5 : fffff880`03865662 00000000`00000001 ffff57cb`f2d6374c fffff880`06b1ff98 : dxgmms1+0x1e614
fffff880`06b1ff20 fffff880`03865662 : 00000000`00000001 ffff57cb`f2d6374c fffff880`06b1ff98 00000000`00000000 : dxgmms1+0x3eba5
fffff880`06b1ff28 00000000`00000001 : ffff57cb`f2d6374c fffff880`06b1ff98 00000000`00000000 fffffa80`0ccc99b8 : dxgmms1+0x3e662
fffff880`06b1ff30 ffff57cb`f2d6374c : fffff880`06b1ff98 00000000`00000000 fffffa80`0ccc99b8 fffffa80`0ccc9790 : 0x1
fffff880`06b1ff38 fffff880`06b1ff98 : 00000000`00000000 fffffa80`0ccc99b8 fffffa80`0ccc9790 fffff880`06b207d0 : 0xffff57cb`f2d6374c
fffff880`06b1ff40 00000000`00000000 : fffffa80`0ccc99b8 fffffa80`0ccc9790 fffff880`06b207d0 00000000`0000000f : 0xfffff880`06b1ff98
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88006b1f4e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88004c02805, The address that the exception occurred at
Arg3: fffff88003deaca8, Exception Record Address
Arg4: fffff88003dea4e0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1358
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6336
Key : Analysis.Init.CPU.mSec
Value: 765
Key : Analysis.Init.Elapsed.mSec
Value: 32290
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88004c02805
BUGCHECK_P3: fffff88003deaca8
BUGCHECK_P4: fffff88003dea4e0
EXCEPTION_RECORD: fffff88003deaca8 -- (.exr 0xfffff88003deaca8)
ExceptionAddress: fffff88004c02805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88003dea4e0 -- (.cxr 0xfffff88003dea4e0)
rax=0000000000000000 rbx=fffffa800c2a36a0 rcx=faa23635bd000000
rdx=8000000000000020 rsi=fffffa800c2a36a0 rdi=0000000000000000
rip=fffff88004c02805 rsp=fffff88003deaee0 rbp=fffffa8008d4eb90
r8=fffff880046fd870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007be9320 r12=000000000000000f r13=fffff88003deb2f8
r14=0000000000000000 r15=fffffa8008bbd000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd2a805:
fffff880`04c02805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80014568370
GetUlongPtrFromAddress: unable to read from fffff80014568488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`03deaee0 00000002`00000000 : 00000000`00000000 ffff6f09`cc393d4d 00000004`00000000 fffffa80`08dc71c0 : nvlddmkm+0xd2a805
fffff880`03deaee8 00000000`00000000 : ffff6f09`cc393d4d 00000004`00000000 fffffa80`08dc71c0 fffff880`02a65180 : 0x00000002`00000000
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88003dea4e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88003d4c808, The address that the exception occurred at
Arg3: fffff88006ac8c78, Exception Record Address
Arg4: fffff88006ac84b0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1405
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 11547
Key : Analysis.Init.CPU.mSec
Value: 718
Key : Analysis.Init.Elapsed.mSec
Value: 26815
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88003d4c808
BUGCHECK_P3: fffff88006ac8c78
BUGCHECK_P4: fffff88006ac84b0
EXCEPTION_RECORD: fffff88006ac8c78 -- (.exr 0xfffff88006ac8c78)
ExceptionAddress: fffff88003d4c808 (nvlddmkm+0x0000000000064808)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000a0
Attempt to read from address 00000000000000a0
CONTEXT: fffff88006ac84b0 -- (.cxr 0xfffff88006ac84b0)
rax=fffff88006ac8ed8 rbx=0000000000000000 rcx=fffffa800a7edcd0
rdx=0000000000010000 rsi=fffffa800a7edcd0 rdi=0000000000000000
rip=fffff88003d4c808 rsp=fffff88006ac8eb0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000840000 r10=000000007fffffff
r11=0000000020010020 r12=0000000000160000 r13=fffff88006ac92f8
r14=0000000000010000 r15=fffffa8008962000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x64808:
fffff880`03d4c808 8b87a0000000 mov eax,dword ptr [rdi+0A0h] ds:002b:00000000`000000a0=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff8007e16e370
GetUlongPtrFromAddress: unable to read from fffff8007e16e488
00000000000000a0
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: 00000000000000a0
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`06ac8eb0 00000000`00160000 : 00000000`00001000 00000000`00000000 00000000`0000000f fffffa80`0a32c7a0 : nvlddmkm+0x64808
fffff880`06ac8eb8 00000000`00001000 : 00000000`00000000 00000000`0000000f fffffa80`0a32c7a0 fffff880`04a12d2a : 0x160000
fffff880`06ac8ec0 00000000`00000000 : 00000000`0000000f fffffa80`0a32c7a0 fffff880`04a12d2a 00000000`00010000 : 0x1000
SYMBOL_NAME: nvlddmkm+64808
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88006ac84b0 ; kb
BUCKET_ID_FUNC_OFFSET: 64808
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88004a1e805, The address that the exception occurred at
Arg3: fffff88006cb2ca8, Exception Record Address
Arg4: fffff88006cb24e0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1687
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 14208
Key : Analysis.Init.CPU.mSec
Value: 812
Key : Analysis.Init.Elapsed.mSec
Value: 26437
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88004a1e805
BUGCHECK_P3: fffff88006cb2ca8
BUGCHECK_P4: fffff88006cb24e0
EXCEPTION_RECORD: fffff88006cb2ca8 -- (.exr 0xfffff88006cb2ca8)
ExceptionAddress: fffff88004a1e805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88006cb24e0 -- (.cxr 0xfffff88006cb24e0)
rax=0000000000000000 rbx=fffffa800b736e20 rcx=40ec49b12adf0000
rdx=8000000000000020 rsi=fffffa800b736e20 rdi=0000000000000000
rip=fffff88004a1e805 rsp=fffff88006cb2ee0 rbp=fffffa8008cf7010
r8=fffff88004519870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007baf360 r12=000000000000000f r13=fffff88006cb32f8
r14=0000000000000000 r15=fffffa80088d4000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0xd2a805:
fffff880`04a1e805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80016d74370
GetUlongPtrFromAddress: unable to read from fffff80016d74488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`06cb2ee0 00000002`00000000 : 00000000`00000000 ffff9845`26f6556d 00000004`00000000 fffffa80`08cf2640 : nvlddmkm+0xd2a805
fffff880`06cb2ee8 00000000`00000000 : ffff9845`26f6556d 00000004`00000000 fffffa80`08cf2640 fffff880`02a65180 : 0x00000002`00000000
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88006cb24e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88004935805, The address that the exception occurred at
Arg3: fffff88003595ca8, Exception Record Address
Arg4: fffff880035954e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1671
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 12382
Key : Analysis.Init.CPU.mSec
Value: 874
Key : Analysis.Init.Elapsed.mSec
Value: 28185
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88004935805
BUGCHECK_P3: fffff88003595ca8
BUGCHECK_P4: fffff880035954e0
EXCEPTION_RECORD: fffff88003595ca8 -- (.exr 0xfffff88003595ca8)
ExceptionAddress: fffff88004935805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff880035954e0 -- (.cxr 0xfffff880035954e0)
rax=0000000000000000 rbx=fffffa800c780cf0 rcx=3acd7e4ab2670000
rdx=8000000000000020 rsi=fffffa800c780cf0 rdi=0000000000000000
rip=fffff88004935805 rsp=fffff88003595ee0 rbp=fffffa8008d92010
r8=fffff88004430870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007c81310 r12=000000000000000f r13=fffff880035962f8
r14=0000000000000000 r15=fffffa80089fa000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd2a805:
fffff880`04935805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80042559370
GetUlongPtrFromAddress: unable to read from fffff80042559488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`03595ee0 fffff880`048dac90 : fffff880`04862ffd fffff880`038e9c1d fffff880`038287ac fffff880`0383675f : nvlddmkm+0xd2a805
fffff880`03595ee8 fffff880`04862ffd : fffff880`038e9c1d fffff880`038287ac fffff880`0383675f fffff880`03825928 : nvlddmkm+0xccfc90
fffff880`03595ef0 fffff880`038e9c1d : fffff880`038287ac fffff880`0383675f fffff880`03825928 fffff880`0381e614 : nvlddmkm+0xc57ffd
fffff880`03595ef8 fffff880`038287ac : fffff880`0383675f fffff880`03825928 fffff880`0381e614 fffff880`0383eba5 : dxgkrnl+0x8dc1d
fffff880`03595f00 fffff880`0383675f : fffff880`03825928 fffff880`0381e614 fffff880`0383eba5 fffff880`0383e662 : dxgmms1+0x287ac
fffff880`03595f08 fffff880`03825928 : fffff880`0381e614 fffff880`0383eba5 fffff880`0383e662 00000000`00000001 : dxgmms1+0x3675f
fffff880`03595f10 fffff880`0381e614 : fffff880`0383eba5 fffff880`0383e662 00000000`00000001 ffffc24d`7d13ec47 : dxgmms1+0x25928
fffff880`03595f18 fffff880`0383eba5 : fffff880`0383e662 00000000`00000001 ffffc24d`7d13ec47 fffff880`03595f98 : dxgmms1+0x1e614
fffff880`03595f20 fffff880`0383e662 : 00000000`00000001 ffffc24d`7d13ec47 fffff880`03595f98 00000000`00000000 : dxgmms1+0x3eba5
fffff880`03595f28 00000000`00000001 : ffffc24d`7d13ec47 fffff880`03595f98 00000000`00000000 fffffa80`0b2a5408 : dxgmms1+0x3e662
fffff880`03595f30 ffffc24d`7d13ec47 : fffff880`03595f98 00000000`00000000 fffffa80`0b2a5408 fffffa80`0b2a51e0 : 0x1
fffff880`03595f38 fffff880`03595f98 : 00000000`00000000 fffffa80`0b2a5408 fffffa80`0b2a51e0 fffff880`035967d0 : 0xffffc24d`7d13ec47
fffff880`03595f40 00000000`00000000 : fffffa80`0b2a5408 fffffa80`0b2a51e0 fffff880`035967d0 00000000`0000000f : 0xfffff880`03595f98
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff880035954e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88004975789, The address that the exception occurred at
Arg3: fffff88006c96ca8, Exception Record Address
Arg4: fffff88006c964e0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1531
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3548
Key : Analysis.Init.CPU.mSec
Value: 890
Key : Analysis.Init.Elapsed.mSec
Value: 36792
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88004975789
BUGCHECK_P3: fffff88006c96ca8
BUGCHECK_P4: fffff88006c964e0
EXCEPTION_RECORD: fffff88006c96ca8 -- (.exr 0xfffff88006c96ca8)
ExceptionAddress: fffff88004975789 (nvlddmkm+0x0000000000d2a789)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88006c964e0 -- (.cxr 0xfffff88006c964e0)
rax=0000000000000000 rbx=fffffa800da27390 rcx=5f4c1a54576a0000
rdx=8000000000000020 rsi=fffffa800da27390 rdi=0000000000000000
rip=fffff88004975789 rsp=fffff88006c96ee0 rbp=fffffa8008c827f0
r8=fffff88004470880 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007bff310 r12=000000000000000f r13=fffff88006c972f8
r14=0000000000000000 r15=fffffa8008b93000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0xd2a789:
fffff880`04975789 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80199b73370
GetUlongPtrFromAddress: unable to read from fffff80199b73488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`06c96ee0 00000000`00010000 : fffffa80`07215010 ffffd048`64772013 00000000`00000000 fffffa80`08cfbc40 : nvlddmkm+0xd2a789
fffff880`06c96ee8 fffffa80`07215010 : ffffd048`64772013 00000000`00000000 fffffa80`08cfbc40 fffff880`009c0180 : 0x10000
fffff880`06c96ef0 ffffd048`64772013 : 00000000`00000000 fffffa80`08cfbc40 fffff880`009c0180 00000000`00000000 : 0xfffffa80`07215010
fffff880`06c96ef8 00000000`00000000 : fffffa80`08cfbc40 fffff880`009c0180 00000000`00000000 fffffa80`0992f3e8 : 0xffffd048`64772013
SYMBOL_NAME: nvlddmkm+d2a789
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88006c964e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a789
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88007024805, The address that the exception occurred at
Arg3: fffff88004c6eca8, Exception Record Address
Arg4: fffff88004c6e4e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1514
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 9616
Key : Analysis.Init.CPU.mSec
Value: 781
Key : Analysis.Init.Elapsed.mSec
Value: 44057
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88007024805
BUGCHECK_P3: fffff88004c6eca8
BUGCHECK_P4: fffff88004c6e4e0
EXCEPTION_RECORD: fffff88004c6eca8 -- (.exr 0xfffff88004c6eca8)
ExceptionAddress: fffff88007024805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88004c6e4e0 -- (.cxr 0xfffff88004c6e4e0)
rax=0000000000000000 rbx=fffffa80074ed8f0 rcx=47bfb1cfa9dd0000
rdx=8000000000000020 rsi=fffffa80074ed8f0 rdi=0000000000000000
rip=fffff88007024805 rsp=fffff88004c6eee0 rbp=fffffa8008c10010
r8=fffff88006b1f870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007aa81e0 r12=000000000000000f r13=fffff88004c6f2f8
r14=0000000000000000 r15=fffffa80088d3000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0xd2a805:
fffff880`07024805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff802a0965370
GetUlongPtrFromAddress: unable to read from fffff802a0965488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`04c6eee0 fffff880`06fc9c90 : fffff880`06f51ffd fffff880`0371ac1d fffff880`036397ac fffff880`0364775f : nvlddmkm+0xd2a805
fffff880`04c6eee8 fffff880`06f51ffd : fffff880`0371ac1d fffff880`036397ac fffff880`0364775f fffff880`03636928 : nvlddmkm+0xccfc90
fffff880`04c6eef0 fffff880`0371ac1d : fffff880`036397ac fffff880`0364775f fffff880`03636928 fffff880`0362f614 : nvlddmkm+0xc57ffd
fffff880`04c6eef8 fffff880`036397ac : fffff880`0364775f fffff880`03636928 fffff880`0362f614 fffff880`0364fba5 : dxgkrnl+0x8dc1d
fffff880`04c6ef00 fffff880`0364775f : fffff880`03636928 fffff880`0362f614 fffff880`0364fba5 fffff880`0364f662 : dxgmms1+0x287ac
fffff880`04c6ef08 fffff880`03636928 : fffff880`0362f614 fffff880`0364fba5 fffff880`0364f662 00000000`00000001 : dxgmms1+0x3675f
fffff880`04c6ef10 fffff880`0362f614 : fffff880`0364fba5 fffff880`0364f662 00000000`00000001 ffffbf3f`b50947fd : dxgmms1+0x25928
fffff880`04c6ef18 fffff880`0364fba5 : fffff880`0364f662 00000000`00000001 ffffbf3f`b50947fd fffff880`04c6ef98 : dxgmms1+0x1e614
fffff880`04c6ef20 fffff880`0364f662 : 00000000`00000001 ffffbf3f`b50947fd fffff880`04c6ef98 00000000`00000000 : dxgmms1+0x3eba5
fffff880`04c6ef28 00000000`00000001 : ffffbf3f`b50947fd fffff880`04c6ef98 00000000`00000000 fffffa80`09ff5568 : dxgmms1+0x3e662
fffff880`04c6ef30 ffffbf3f`b50947fd : fffff880`04c6ef98 00000000`00000000 fffffa80`09ff5568 fffffa80`09ff5340 : 0x1
fffff880`04c6ef38 fffff880`04c6ef98 : 00000000`00000000 fffffa80`09ff5568 fffffa80`09ff5340 fffff880`04c6f7d0 : 0xffffbf3f`b50947fd
fffff880`04c6ef40 00000000`00000000 : fffffa80`09ff5568 fffffa80`09ff5340 fffff880`04c6f7d0 00000000`0000000f : 0xfffff880`04c6ef98
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88004c6e4e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88006ff7789, The address that the exception occurred at
Arg3: fffff880044f8ca8, Exception Record Address
Arg4: fffff880044f84e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1514
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 8734
Key : Analysis.Init.CPU.mSec
Value: 656
Key : Analysis.Init.Elapsed.mSec
Value: 30490
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88006ff7789
BUGCHECK_P3: fffff880044f8ca8
BUGCHECK_P4: fffff880044f84e0
EXCEPTION_RECORD: fffff880044f8ca8 -- (.exr 0xfffff880044f8ca8)
ExceptionAddress: fffff88006ff7789 (nvlddmkm+0x0000000000d2a789)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff880044f84e0 -- (.cxr 0xfffff880044f84e0)
rax=0000000000000000 rbx=fffffa800c13ca70 rcx=3078f1ab8d320000
rdx=8000000000000020 rsi=fffffa800c13ca70 rdi=0000000000000000
rip=fffff88006ff7789 rsp=fffff880044f8ee0 rbp=fffffa8008ce0010
r8=fffff88006af2880 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007bbe310 r12=000000000000000f r13=fffff880044f92f8
r14=0000000000000000 r15=fffffa8008b22000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd2a789:
fffff880`06ff7789 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80166bd4370
GetUlongPtrFromAddress: unable to read from fffff80166bd4488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`044f8ee0 fffff880`06f9cc4c : fffff880`06f24ffd fffff880`036fdc1d fffff880`036287ac fffff880`0363675f : nvlddmkm+0xd2a789
fffff880`044f8ee8 fffff880`06f24ffd : fffff880`036fdc1d fffff880`036287ac fffff880`0363675f fffff880`03625928 : nvlddmkm+0xccfc4c
fffff880`044f8ef0 fffff880`036fdc1d : fffff880`036287ac fffff880`0363675f fffff880`03625928 fffff880`0361e614 : nvlddmkm+0xc57ffd
fffff880`044f8ef8 fffff880`036287ac : fffff880`0363675f fffff880`03625928 fffff880`0361e614 fffff880`0363eba5 : dxgkrnl+0x8dc1d
fffff880`044f8f00 fffff880`0363675f : fffff880`03625928 fffff880`0361e614 fffff880`0363eba5 fffff880`0363e662 : dxgmms1+0x287ac
fffff880`044f8f08 fffff880`03625928 : fffff880`0361e614 fffff880`0363eba5 fffff880`0363e662 00000000`00000001 : dxgmms1+0x3675f
fffff880`044f8f10 fffff880`0361e614 : fffff880`0363eba5 fffff880`0363e662 00000000`00000001 ffffc8f8`f5e40312 : dxgmms1+0x25928
fffff880`044f8f18 fffff880`0363eba5 : fffff880`0363e662 00000000`00000001 ffffc8f8`f5e40312 fffff880`044f8f98 : dxgmms1+0x1e614
fffff880`044f8f20 fffff880`0363e662 : 00000000`00000001 ffffc8f8`f5e40312 fffff880`044f8f98 00000000`00000000 : dxgmms1+0x3eba5
fffff880`044f8f28 00000000`00000001 : ffffc8f8`f5e40312 fffff880`044f8f98 00000000`00000000 fffffa80`0babe8c8 : dxgmms1+0x3e662
fffff880`044f8f30 ffffc8f8`f5e40312 : fffff880`044f8f98 00000000`00000000 fffffa80`0babe8c8 fffffa80`0babe6a0 : 0x1
fffff880`044f8f38 fffff880`044f8f98 : 00000000`00000000 fffffa80`0babe8c8 fffffa80`0babe6a0 fffff880`044f97d0 : 0xffffc8f8`f5e40312
fffff880`044f8f40 00000000`00000000 : fffffa80`0babe8c8 fffffa80`0babe6a0 fffff880`044f97d0 00000000`0000000f : 0xfffff880`044f8f98
SYMBOL_NAME: nvlddmkm+d2a789
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff880044f84e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a789
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff880049d3805, The address that the exception occurred at
Arg3: fffff88006ca5ca8, Exception Record Address
Arg4: fffff88006ca54e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1327
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4369
Key : Analysis.Init.CPU.mSec
Value: 937
Key : Analysis.Init.Elapsed.mSec
Value: 35622
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff880049d3805
BUGCHECK_P3: fffff88006ca5ca8
BUGCHECK_P4: fffff88006ca54e0
EXCEPTION_RECORD: fffff88006ca5ca8 -- (.exr 0xfffff88006ca5ca8)
ExceptionAddress: fffff880049d3805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88006ca54e0 -- (.cxr 0xfffff88006ca54e0)
rax=0000000000000000 rbx=fffffa800be4b990 rcx=c2717396e1af0000
rdx=8000000000000020 rsi=fffffa800be4b990 rdi=0000000000000000
rip=fffff880049d3805 rsp=fffff88006ca5ee0 rbp=fffffa8008d435e0
r8=fffff880044ce870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007c2d310 r12=000000000000000f r13=fffff88006ca62f8
r14=0000000000000000 r15=fffffa8008a0d000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0xd2a805:
fffff880`049d3805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff8016db5b370
GetUlongPtrFromAddress: unable to read from fffff8016db5b488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`06ca5ee0 fffff880`04978c90 : fffff880`04900ffd ffff7f46`273d97e9 fffff880`038767ac fffffa80`08d3d840 : nvlddmkm+0xd2a805
fffff880`06ca5ee8 fffff880`04900ffd : ffff7f46`273d97e9 fffff880`038767ac fffffa80`08d3d840 fffff880`009c0180 : nvlddmkm+0xccfc90
fffff880`06ca5ef0 ffff7f46`273d97e9 : fffff880`038767ac fffffa80`08d3d840 fffff880`009c0180 00000000`00000000 : nvlddmkm+0xc57ffd
fffff880`06ca5ef8 fffff880`038767ac : fffffa80`08d3d840 fffff880`009c0180 00000000`00000000 fffffa80`094f0028 : 0xffff7f46`273d97e9
fffff880`06ca5f00 fffffa80`08d3d840 : fffff880`009c0180 00000000`00000000 fffffa80`094f0028 00000000`00000000 : dxgmms1+0x287ac
fffff880`06ca5f08 fffff880`009c0180 : 00000000`00000000 fffffa80`094f0028 00000000`00000000 00000000`00000000 : 0xfffffa80`08d3d840
fffff880`06ca5f10 00000000`00000000 : fffffa80`094f0028 00000000`00000000 00000000`00000000 fffffa80`08d3d700 : 0xfffff880`009c0180
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88006ca54e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88006fb9789, The address that the exception occurred at
Arg3: fffff880044abca8, Exception Record Address
Arg4: fffff880044ab4e0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1296
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3711
Key : Analysis.Init.CPU.mSec
Value: 749
Key : Analysis.Init.Elapsed.mSec
Value: 36204
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88006fb9789
BUGCHECK_P3: fffff880044abca8
BUGCHECK_P4: fffff880044ab4e0
EXCEPTION_RECORD: fffff880044abca8 -- (.exr 0xfffff880044abca8)
ExceptionAddress: fffff88006fb9789 (nvlddmkm+0x0000000000d2a789)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff880044ab4e0 -- (.cxr 0xfffff880044ab4e0)
rax=0000000000000000 rbx=fffffa800c243510 rcx=213f9e6ed8100000
rdx=8000000000000020 rsi=fffffa800c243510 rdi=0000000000000000
rip=fffff88006fb9789 rsp=fffff880044abee0 rbp=fffffa8008cb1010
r8=fffff88006ab4880 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007c24330 r12=000000000000000f r13=fffff880044ac2f8
r14=0000000000000000 r15=fffffa8008969000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd2a789:
fffff880`06fb9789 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff8017cfdd370
GetUlongPtrFromAddress: unable to read from fffff8017cfdd488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`044abee0 00000002`00000000 : 00000000`00000000 fffffa80`08aea1a8 00000004`00000000 00000000`00000000 : nvlddmkm+0xd2a789
fffff880`044abee8 00000000`00000000 : fffffa80`08aea1a8 00000004`00000000 00000000`00000000 fffff880`044ac000 : 0x00000002`00000000
SYMBOL_NAME: nvlddmkm+d2a789
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff880044ab4e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a789
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff8800515e805, The address that the exception occurred at
Arg3: fffff88006da8ca8, Exception Record Address
Arg4: fffff88006da84e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1842
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 13524
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 28699
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8800515e805
BUGCHECK_P3: fffff88006da8ca8
BUGCHECK_P4: fffff88006da84e0
EXCEPTION_RECORD: fffff88006da8ca8 -- (.exr 0xfffff88006da8ca8)
ExceptionAddress: fffff8800515e805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff88006da84e0 -- (.cxr 0xfffff88006da84e0)
rax=0000000000000000 rbx=fffffa800c0df500 rcx=3c8edfd421450000
rdx=8000000000000020 rsi=fffffa800c0df500 rdi=0000000000000000
rip=fffff8800515e805 rsp=fffff88006da8ee0 rbp=fffffa800907f010
r8=fffff88004c59870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007e2e730 r12=000000000000000f r13=fffff88006da92f8
r14=0000000000000000 r15=fffffa8008bfd000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd2a805:
fffff880`0515e805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff802f1bc5370
GetUlongPtrFromAddress: unable to read from fffff802f1bc5488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`06da8ee0 fffff880`05103c90 : fffff880`0508bffd ffffb2a5`7206a005 fffff880`03c287ac fffffa80`0907a840 : nvlddmkm+0xd2a805
fffff880`06da8ee8 fffff880`0508bffd : ffffb2a5`7206a005 fffff880`03c287ac fffffa80`0907a840 fffff802`f1b65180 : nvlddmkm+0xccfc90
fffff880`06da8ef0 ffffb2a5`7206a005 : fffff880`03c287ac fffffa80`0907a840 fffff802`f1b65180 00000000`00000000 : nvlddmkm+0xc57ffd
fffff880`06da8ef8 fffff880`03c287ac : fffffa80`0907a840 fffff802`f1b65180 00000000`00000000 fffffa80`0a86f3e8 : 0xffffb2a5`7206a005
fffff880`06da8f00 fffffa80`0907a840 : fffff802`f1b65180 00000000`00000000 fffffa80`0a86f3e8 00000000`00000000 : dxgmms1+0x287ac
fffff880`06da8f08 fffff802`f1b65180 : 00000000`00000000 fffffa80`0a86f3e8 00000000`00000000 00000000`00000000 : 0xfffffa80`0907a840
fffff880`06da8f10 00000000`00000000 : fffffa80`0a86f3e8 00000000`00000000 00000000`00000000 fffffa80`0907a700 : nt!KiInitialPCR+0x180
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88006da84e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88006c8a808, The address that the exception occurred at
Arg3: fffff880045b8c78, Exception Record Address
Arg4: fffff880045b84b0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1530
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 12490
Key : Analysis.Init.CPU.mSec
Value: 889
Key : Analysis.Init.Elapsed.mSec
Value: 27234
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88006c8a808
BUGCHECK_P3: fffff880045b8c78
BUGCHECK_P4: fffff880045b84b0
EXCEPTION_RECORD: fffff880045b8c78 -- (.exr 0xfffff880045b8c78)
ExceptionAddress: fffff88006c8a808 (nvlddmkm+0x0000000000064808)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000a0
Attempt to read from address 00000000000000a0
CONTEXT: fffff880045b84b0 -- (.cxr 0xfffff880045b84b0)
rax=fffff880045b8ed8 rbx=0000000000000000 rcx=fffffa800e06a800
rdx=0000000000010000 rsi=fffffa800e06a800 rdi=0000000000000000
rip=fffff88006c8a808 rsp=fffff880045b8eb0 rbp=0000000000000000
r8=0000000000000000 r9=0000000001200000 r10=000000007fffffff
r11=0000000020010020 r12=0000000000300000 r13=fffff880045b92f8
r14=0000000000010000 r15=fffffa8008e52000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x64808:
fffff880`06c8a808 8b87a0000000 mov eax,dword ptr [rdi+0A0h] ds:002b:00000000`000000a0=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80341170370
GetUlongPtrFromAddress: unable to read from fffff80341170488
00000000000000a0
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: 00000000000000a0
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`045b8eb0 00000000`00300000 : 00000000`00001000 00000000`00000000 00000000`0000000f fffffa80`0a8318d0 : nvlddmkm+0x64808
fffff880`045b8eb8 00000000`00001000 : 00000000`00000000 00000000`0000000f fffffa80`0a8318d0 fffff880`07950d2a : 0x300000
fffff880`045b8ec0 00000000`00000000 : 00000000`0000000f fffffa80`0a8318d0 fffff880`07950d2a 00000000`00010000 : 0x1000
SYMBOL_NAME: nvlddmkm+64808
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff880045b84b0 ; kb
BUCKET_ID_FUNC_OFFSET: 64808
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff80067eba3d0, Address of the instruction which caused the BugCheck
Arg3: fffff8800abd2d10, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1405
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7541
Key : Analysis.Init.CPU.mSec
Value: 842
Key : Analysis.Init.Elapsed.mSec
Value: 27529
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff80067eba3d0
BUGCHECK_P3: fffff8800abd2d10
BUGCHECK_P4: 0
CONTEXT: fffff8800abd2d10 -- (.cxr 0xfffff8800abd2d10)
rax=00000000c0000034 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800abd3c01 rsi=fffff901000b9750 rdi=ffffffffc0000034
rip=fffff80067eba3d0 rsp=fffff8800abd3718 rbp=fffff8800abd3820
r8=fffffa80094d1370 r9=fffff8a003b6c580 r10=fffffa8006a2a760
r11=fffff8800abd3700 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000000000000020
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!IoGetRelatedDeviceObject:
fffff800`67eba3d0 488b4110 mov rax,qword ptr [rcx+10h] ds:002b:00000000`00000010=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
STACK_TEXT:
fffff880`0abd3718 fffff960`0009d473 : 00000000`00000000 00000000`00000000 fffff901`000b9750 00000000`00000000 : nt!IoGetRelatedDeviceObject
fffff880`0abd3720 00000000`00000000 : 00000000`00000000 fffff901`000b9750 00000000`00000000 00000000`00000000 : win32k+0x77473
SYMBOL_NAME: win32k+77473
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
STACK_COMMAND: .cxr 0xfffff8800abd2d10 ; kb
BUCKET_ID_FUNC_OFFSET: 77473
FAILURE_BUCKET_ID: 0x3B_c0000005_win32k!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {8ffa81ae-e629-24c5-067f-7d1473d12e2c}
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: fffff8800499d805, The address that the exception occurred at
Arg3: fffff88003395ca8, Exception Record Address
Arg4: fffff880033954e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1499
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 9540
Key : Analysis.Init.CPU.mSec
Value: 952
Key : Analysis.Init.Elapsed.mSec
Value: 30545
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8800499d805
BUGCHECK_P3: fffff88003395ca8
BUGCHECK_P4: fffff880033954e0
EXCEPTION_RECORD: fffff88003395ca8 -- (.exr 0xfffff88003395ca8)
ExceptionAddress: fffff8800499d805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff880033954e0 -- (.cxr 0xfffff880033954e0)
rax=0000000000000000 rbx=fffffa80070951d0 rcx=d08e77d4e2230000
rdx=8000000000000020 rsi=fffffa80070951d0 rdi=0000000000000000
rip=fffff8800499d805 rsp=fffff88003395ee0 rbp=fffffa8008db9010
r8=fffff88004498870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007c11310 r12=000000000000000f r13=fffff880033962f8
r14=0000000000000000 r15=fffffa8008b95000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0xd2a805:
fffff880`0499d805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80360361370
GetUlongPtrFromAddress: unable to read from fffff80360361488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`03395ee0 fffff880`04942c90 : fffff880`048caffd fffff880`03743c1d fffff880`038587ac fffff880`0386675f : nvlddmkm+0xd2a805
fffff880`03395ee8 fffff880`048caffd : fffff880`03743c1d fffff880`038587ac fffff880`0386675f fffff880`03855928 : nvlddmkm+0xccfc90
fffff880`03395ef0 fffff880`03743c1d : fffff880`038587ac fffff880`0386675f fffff880`03855928 fffff880`0384e614 : nvlddmkm+0xc57ffd
fffff880`03395ef8 fffff880`038587ac : fffff880`0386675f fffff880`03855928 fffff880`0384e614 fffff880`0386eba5 : dxgkrnl+0x8dc1d
fffff880`03395f00 fffff880`0386675f : fffff880`03855928 fffff880`0384e614 fffff880`0386eba5 fffff880`0386e662 : dxgmms1+0x287ac
fffff880`03395f08 fffff880`03855928 : fffff880`0384e614 fffff880`0386eba5 fffff880`0386e662 00000000`00000001 : dxgmms1+0x3675f
fffff880`03395f10 fffff880`0384e614 : fffff880`0386eba5 fffff880`0386e662 00000000`00000001 ffff280e`74edbc03 : dxgmms1+0x25928
fffff880`03395f18 fffff880`0386eba5 : fffff880`0386e662 00000000`00000001 ffff280e`74edbc03 fffff880`03395f98 : dxgmms1+0x1e614
fffff880`03395f20 fffff880`0386e662 : 00000000`00000001 ffff280e`74edbc03 fffff880`03395f98 00000000`00000000 : dxgmms1+0x3eba5
fffff880`03395f28 00000000`00000001 : ffff280e`74edbc03 fffff880`03395f98 00000000`00000000 fffffa80`0b5a3238 : dxgmms1+0x3e662
fffff880`03395f30 ffff280e`74edbc03 : fffff880`03395f98 00000000`00000000 fffffa80`0b5a3238 fffffa80`0b5a3010 : 0x1
fffff880`03395f38 fffff880`03395f98 : 00000000`00000000 fffffa80`0b5a3238 fffffa80`0b5a3010 fffff880`033967d0 : 0xffff280e`74edbc03
fffff880`03395f40 00000000`00000000 : fffffa80`0b5a3238 fffffa80`0b5a3010 fffff880`033967d0 00000000`0000000f : 0xfffff880`03395f98
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff880033954e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
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: fffff88004996805, The address that the exception occurred at
Arg3: fffff880067a1ca8, Exception Record Address
Arg4: fffff880067a14e0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 1577
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10799
Key : Analysis.Init.CPU.mSec
Value: 812
Key : Analysis.Init.Elapsed.mSec
Value: 30714
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : WER.OS.Branch
Value: win8_gdr
Key : WER.OS.Timestamp
Value: 2013-04-10T15:05:00Z
Key : WER.OS.Version
Value: 8.0.9200.16581
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88004996805
BUGCHECK_P3: fffff880067a1ca8
BUGCHECK_P4: fffff880067a14e0
EXCEPTION_RECORD: fffff880067a1ca8 -- (.exr 0xfffff880067a1ca8)
ExceptionAddress: fffff88004996805 (nvlddmkm+0x0000000000d2a805)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080
CONTEXT: fffff880067a14e0 -- (.cxr 0xfffff880067a14e0)
rax=0000000000000000 rbx=fffffa800bc16240 rcx=09bba9bc1bf40000
rdx=8000000000000020 rsi=fffffa800bc16240 rdi=0000000000000000
rip=fffff88004996805 rsp=fffff880067a1ee0 rbp=fffffa8008d4c3d0
r8=fffff88004491870 r9=0000000000000008 r10=0000000000000000
r11=fffffa8007ba2010 r12=000000000000000f r13=fffff880067a22f8
r14=0000000000000000 r15=fffffa8008bd4000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd2a805:
fffff880`04996805 498b9e80000000 mov rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800c07c8370
GetUlongPtrFromAddress: unable to read from fffff800c07c8488
0000000000000080
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: 0000000000000080
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`067a1ee0 fffff880`0493bc90 : fffff880`048c3ffd fffff880`036adc1d fffff880`037c27ac fffff880`037d075f : nvlddmkm+0xd2a805
fffff880`067a1ee8 fffff880`048c3ffd : fffff880`036adc1d fffff880`037c27ac fffff880`037d075f fffff880`037bf928 : nvlddmkm+0xccfc90
fffff880`067a1ef0 fffff880`036adc1d : fffff880`037c27ac fffff880`037d075f fffff880`037bf928 fffff880`037b8614 : nvlddmkm+0xc57ffd
fffff880`067a1ef8 fffff880`037c27ac : fffff880`037d075f fffff880`037bf928 fffff880`037b8614 fffff880`037d8ba5 : dxgkrnl+0x8dc1d
fffff880`067a1f00 fffff880`037d075f : fffff880`037bf928 fffff880`037b8614 fffff880`037d8ba5 fffff880`037d8662 : dxgmms1+0x287ac
fffff880`067a1f08 fffff880`037bf928 : fffff880`037b8614 fffff880`037d8ba5 fffff880`037d8662 00000000`00000001 : dxgmms1+0x3675f
fffff880`067a1f10 fffff880`037b8614 : fffff880`037d8ba5 fffff880`037d8662 00000000`00000001 fffff13b`afc605d4 : dxgmms1+0x25928
fffff880`067a1f18 fffff880`037d8ba5 : fffff880`037d8662 00000000`00000001 fffff13b`afc605d4 fffff880`067a1f98 : dxgmms1+0x1e614
fffff880`067a1f20 fffff880`037d8662 : 00000000`00000001 fffff13b`afc605d4 fffff880`067a1f98 00000000`00000000 : dxgmms1+0x3eba5
fffff880`067a1f28 00000000`00000001 : fffff13b`afc605d4 fffff880`067a1f98 00000000`00000000 fffffa80`097e4e48 : dxgmms1+0x3e662
fffff880`067a1f30 fffff13b`afc605d4 : fffff880`067a1f98 00000000`00000000 fffffa80`097e4e48 fffffa80`097e4c20 : 0x1
fffff880`067a1f38 fffff880`067a1f98 : 00000000`00000000 fffffa80`097e4e48 fffffa80`097e4c20 fffff880`067a27d0 : 0xfffff13b`afc605d4
fffff880`067a1f40 00000000`00000000 : fffffa80`097e4e48 fffffa80`097e4c20 fffff880`067a27d0 00000000`0000000f : 0xfffff880`067a1f98
SYMBOL_NAME: nvlddmkm+d2a805
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff880067a14e0 ; kb
BUCKET_ID_FUNC_OFFSET: d2a805
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 8.0.9200.16581
BUILDLAB_STR: win8_gdr
OSPLATFORM_TYPE: x64
OSNAME: Windows 8
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
Followup: MachineOwner
---------
Abi sürücü çökmüş?
KS
KS
EgeMen67
Hectopat
- Katılım
- 5 Nisan 2020
- Mesajlar
- 9
NVIDIA GeForce GTX 1050
Aman ekran kartında donanımsal sıkıntı yoktur inşallah. Çok pahalı şimdi her şey zaten.
Dediğiniz gibi Easy Anti-Cheat'si kaldırdığımdan beri 1 kere bile çökmedi. Çok tuhaf bu uygulamayı aylardır belki de yıllardır çalıştırmıyordum bile.
Son düzenleme:
Benzer konular
- Soru
- Soru
- Çözüldü
- Soru
Technopat Haberler
Yeni konular
-
-
-
-
-
Nothing Headphone (1)'in tasarımı hakkında ne düşünüyorsunuz?- Andreas Rönnberg
- Mesaj: 2
-
-
-
-
-
-
