- Katılım
- 9 Ekim 2016
- Mesajlar
- 3.115
- Çözümler
- 10
Ağır yük altında oyun oynarken mavi ekran hatası. Donanımsal mı yazılımsal mı anlayamadım.
Buda ikinci mavi ekranın hatası.
Kod:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80650e2410e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3671
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 33146
Key : Analysis.IO.Other.Mb
Value: 16
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 32
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 14382
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 111422-91765-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80650e2410e
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff806518fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: dwm.exe
STACK_TEXT:
ffff9781`150e62e8 fffff806`5103f495 : 00000000`0000001e ffffffff`c0000005 fffff806`50e2410e 00000000`00000000 : nt!KeBugCheckEx
ffff9781`150e62f0 fffff806`5100d46c : 00000048`041002ff 00000000`00000004 ffff8780`075e4180 fffff806`50f08a09 : nt!KiDispatchException+0x1c8fa5
ffff9781`150e69b0 fffff806`51008a5a : ffff8780`074b6100 ffff8780`074c1440 ffffd989`35d2e080 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffff9781`150e6b90 fffff806`50e2410e : ffffd989`00000000 fffff806`00000000 ffff9904`05288000 00000000`00000000 : nt!KiGeneralProtectionFault+0x31a
ffff9781`150e6d20 fffff806`515b5019 : 00000000`00000004 ffffd989`35d2e080 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0x21e
ffff9781`150e6e00 fffff806`51211eb0 : ffff9781`150e70e0 00000000`00000001 ffffd989`35ca2d30 fffff806`00000000 : nt!ExFreePool+0x9
ffff9781`150e6e30 fffff806`51211aa9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObWaitForMultipleObjects+0x3d0
ffff9781`150e7330 fffff806`5100caf5 : 00000000`00000438 00000000`00000000 ffffd989`35d2e080 00000000`00000000 : nt!NtWaitForMultipleObjects+0x119
ffff9781`150e75c0 fffff806`50ffdeb0 : fffff806`6aa02eed ffff9904`0a7ef180 ffff9904`00000000 ffff9904`0a7ef180 : nt!KiSystemServiceCopyEnd+0x25
ffff9781`150e77c8 fffff806`6aa02eed : ffff9904`0a7ef180 ffff9904`00000000 ffff9904`0a7ef180 00000000`00000000 : nt!KiServiceLinkage
ffff9781`150e77d0 fffff806`6aa19769 : 00000000`00000000 ffffd989`35050be0 ffff9904`0347b3f0 fffff806`6aa0e104 : dxgkrnl!CTokenManager::ProcessTokens+0x1bd
ffff9781`150e7890 fffff806`6aa0e03e : 00000000`00000000 ffff9781`150e7a80 ffff9904`0347b3f0 fffff806`00000002 : dxgkrnl!CTokenManager::TokenThread+0x79
ffff9781`150e78e0 fffff806`5100caf5 : ffffd989`35d2e080 0000027c`c224f008 00000000`00000020 00000000`00000000 : dxgkrnl!NtTokenManagerThread+0x1be
ffff9781`150e7a00 00007ffb`7ce88304 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000a2`445ff818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`7ce88304
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: ZEROED_STACK_AV
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6cece28d-ac4a-3491-48c4-50180756f8a2}
Followup: MachineOwner
---------Buda ikinci mavi ekranın hatası.
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: fffff8056a64321d, The address that the exception occurred at
Arg3: fffff40eea90f6e8, Exception Record Address
Arg4: fffff40eea90ef20, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 3171
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 43278
Key : Analysis.IO.Other.Mb
Value: 8
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 17
Key : Analysis.Init.CPU.mSec
Value: 327
Key : Analysis.Init.Elapsed.mSec
Value: 3652
Key : Analysis.Memory.CommitPeak.Mb
Value: 104
Key : Bugcheck.Code.DumpHeader
Value: 0x1000007e
Key : Bugcheck.Code.Register
Value: 0x7e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 111422-92281-01.dmp
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8056a64321d
BUGCHECK_P3: fffff40eea90f6e8
BUGCHECK_P4: fffff40eea90ef20
EXCEPTION_RECORD: fffff40eea90f6e8 -- (.exr 0xfffff40eea90f6e8)
ExceptionAddress: fffff8056a64321d (nt!EtwpFlushActiveBuffers+0x00000000000002cd)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff40eea90ef20 -- (.cxr 0xfffff40eea90ef20)
rax=00f0000000000000 rbx=0000000000000002 rcx=0000000000000000
rdx=00000009dbc677fc rsi=ffffd40e931d9a40 rdi=fffff40eea90f958
rip=fffff8056a64321d rsp=fffff40eea90f920 rbp=ffffffffffffffff
r8=0000000000000000 r9=0000000000000001 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffff40eea90f950
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050297
nt!EtwpFlushActiveBuffers+0x2cd:
fffff805`6a64321d 488b4810 mov rcx,qword ptr [rax+10h] ds:002b:00f00000`00000010=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff8056acfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff
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: ffffffffffffffff
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff40e`ea90f920 fffff805`6a641e2e : ffffd40e`931d9a40 ffffd40e`931d9a40 00000000`00000000 ffffffff`fffffffd : nt!EtwpFlushActiveBuffers+0x2cd
fffff40e`ea90fa90 fffff805`6a271d25 : ffffffff`fffffffd ffffd40e`8fb2f080 00000000`00000080 fffff805`6a641b80 : nt!EtwpLogger+0x2ae
fffff40e`ea90fb10 fffff805`6a401f08 : ffffa081`30ca7180 ffffd40e`8fb2f080 fffff805`6a271cd0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
fffff40e`ea90fb60 00000000`00000000 : fffff40e`ea910000 fffff40e`ea909000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!EtwpFlushActiveBuffers+2cd
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2251
STACK_COMMAND: .cxr 0xfffff40eea90ef20 ; kb
BUCKET_ID_FUNC_OFFSET: 2cd
FAILURE_BUCKET_ID: AV_nt!EtwpFlushActiveBuffers
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {bd4857fd-c381-e780-0168-d9d444fc8264}
Followup: MachineOwner
Son düzenleme:
