פורסם 2010 בספטמבר 715 שנים שלום,אשמח אם מישהו יוכל לפענח לי את מקור הבעיה (קובץ מצורף) שגורם למסכים כחולים טורדניים.תודה מראש.[attachment deleted by admin]
פורסם 2010 בספטמבר 1115 שנים Loading unloaded module list ......... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880045cb7ac, fffff88002135788, fffff88002134ff0} Probably caused by : hardware ( CODE_ADDRESS_MISMATCH ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff880045cb7ac, The address that the exception occurred at Arg3: fffff88002135788, Exception Record Address Arg4: fffff88002134ff0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec fffff880`045cb7ac 488b11 mov rdx,[rcx] EXCEPTION_RECORD: fffff88002135788 -- (.exr fffff88002135788) ExceptionAddress: fffff880045cb7ac (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000fec) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000080000000 Attempt to read from address 0000000080000000 CONTEXT: fffff88002134ff0 -- (.cxr fffff88002134ff0) rax=0000000000000000 rbx=0000000000000000 rcx=0000000080000000 rdx=fffff8a009dc4010 rsi=fffff8a009dc4010 rdi=0000000000000000 rip=fffff880045cb7ac rsp=fffff880021359c0 rbp=fffffa800518f000 r8=0000000000001000 r9=0000000000000000 r10=0000000000000001 r11=fffff8a009dc4118 r12=0000000000000000 r13=0000000000000001 r14=fffffa80050dc530 r15=fffff8a009dc4118 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec: fffff880`045cb7ac 488b11 mov rdx,[rcx] ds:002b:0000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". READ_ADDRESS: GetUlongFromAddress: unable to read from fffff80002cb10e0 fffff80002c30a40: Unable to get special pool info fffff80002c30a40: Unable to get special pool info 0000000080000000 BUGCHECK_STR: 0x7E EXCEPTION_DOESNOT_MATCH_CODE: This indicates a hardware error. Instruction at fffff880045cb7ac does not read/write to 0000000080000000 LAST_CONTROL_TRANSFER: from fffff880045bb25d to fffff880045cb7ac STACK_TEXT: fffff880`021359c0 fffff880`045bb25d : fffffa80`050dc530 fffff8a0`09dc4010 fffffa80`054e0500 fffffa80`0518f000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec fffff880`02135b30 fffff880`045b6358 : fffffa80`058c9710 00000000`00000080 00000000`00000000 fffff880`02135ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d fffff880`02135c50 fffff880`045d416d : fffffa80`00000000 fffffa80`048d6010 00000000`0000000f fffff880`045d5f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c fffff880`02135ca0 fffff880`045d33f8 : fffff880`009eaec0 fffffa80`037f3860 00000000`00000000 fffffa80`048d6010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`02135cd0 fffff880`045d2e96 : 00000000`00000000 fffffa80`037f3860 00000000`00000080 fffffa80`048d6010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`02135d00 fffff800`02d1dc06 : 00000000`033feee0 fffffa80`048d5a10 fffffa80`036a8450 fffffa80`048d5a10 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`02135d40 fffff800`02a57c26 : fffff880`009e6180 fffffa80`048d5a10 fffff880`009f0f40 6c72506f`6865652b : nt!PspSystemThreadStartup+0x5a fffff880`02135d80 00000000`00000000 : fffff880`02136000 fffff880`02130000 fffff880`02135690 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_NAME: CODE_ADDRESS_MISMATCH FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr fffff88002134ff0 ; kb FAILURE_BUCKET_ID: X64_0x7E_CODE_ADDRESS_MISMATCH BUCKET_ID: X64_0x7E_CODE_ADDRESS_MISMATCH Followup: MachineOwner --------- לא ברור לי בדיוק מה מקור הבעיה. אני בעצמי אשמח לדעת
ארכיון
דיון זה הועבר לארכיון ולא ניתן להוסיף בו תגובות חדשות.