[mrcnn]

Попробуйте установить драйвера на системную плату ( если они не установлены )
- Попробуйте обновить драйвера на системную плату,
скачав на этой странице: http://ru.asus.com/Motherboards/AMD_...M_LX/#download
Там есть драйвера на чипсет, звук, VGA (видеокарту), LAN, SATA и др.

Системная плата : Asus M5A78L-M LX, интегрированное в системную плату ATI Radeon™ HD 3000 GPU http://ru.asus.com/Motherboards/AMD_...specifications

Страница загрузки драйверов на видеокарту: http://support.asus.com/download/dow...el=M5A78L-M+LX Указываете операционную систему Windows 7 64bit SP1

- Попробуйте обновить DirectX. Страница загрузки: http://www.microsoft.com/ru-ru/downl...ils.aspx?id=35

Windows 7 64bit SP1

060113-13166-01.dmp
1E (c0000005, 0, 8, 0)
ntkrnlmp.exe nt! ?? ::FNODOBFM:: `string'+487d

читать дальше »

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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
+619b2faf02c9de64
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc100
0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880027bd320 -- (.trap 0xfffff880027bd320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000038 rbx=0000000000000000 rcx=fffffa8005562658
rdx=fffffa800553bb58 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff880027bd4b8 rbp=00000000ffffffff
r8=fffff78000000008 r9=0000000000000000 r10=0000000000000000
r11=fffff88003563180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000310f728 to fffff800030c4c00
STACK_TEXT:
fffff880`027bca98 fffff800`0310f728 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`027bcaa0 fffff800`030c4282 : fffff880`027bd278 fffffa80`0553bb40 fffff880`027bd320 fffffa80`05369bc0 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`027bd140 fffff800`030c2dfa : 00000000`00000008 00000000`00000000 00000000`00000000 fffffa80`0553bb40 : nt!KiExceptionDispatch+0xc2
fffff880`027bd320 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`03563180 : nt!KiPageFault+0x23a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+487ed
fffff800`0310f728 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+487ed
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+487ed
BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+487ed
Followup: MachineOwner
---------



This is a side effect of Basic Block Tools optimization (BBT). Using public symbols the debugger will find it hard to get to the right symbol, there is a nice a trick you can use in order to get to the right function.
http://blogs.msdn.com/b/ntdebugging/...he-rescue.aspx http://forum.sysinternals.com/what-i...247_page2.html

060113-13431-01.dmp
1000007e (ffffffffc0000005, fffff88007becfce, fffff880027ff6c8, fffff880027fef20)
atikmdag.sys ( драйвер видеокарты ATI Radeon )

читать дальше »

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: fffff88007becfce, The address that the exception occurred at
Arg3: fffff880027ff6c8, Exception Record Address
Arg4: fffff880027fef20, Context Record Address

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
atikmdag+376fce
fffff880`07becfce 8178083000bebe cmp dword ptr [rax+8],0BEBE0030h
EXCEPTION_RECORD: fffff880027ff6c8 -- (.exr 0xfffff880027ff6c8)
ExceptionAddress: fffff88007becfce (atikmdag+0x0000000000376fce)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880027fef20 -- (.cxr 0xfffff880027fef20)
rax=3ad42c62c37d96c9 rbx=fffff8a01039bf28 rcx=fffff8a00c011978
rdx=fffff880027ff9f0 rsi=fffff8a010399000 rdi=0000000000000230
rip=fffff88007becfce rsp=fffff880027ff908 rbp=00000000000001f7
r8=fffffa800821b420 r9=0000000000000000 r10=fffff88007876000
r11=0000000000000000 r12=fffff8a001037e40 r13=0000000000000230
r14=fffffa800821b420 r15=fffffa8003eaa010
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmdag+0x376fce:
fffff880`07becfce 8178083000bebe cmp dword ptr [rax+8],0BEBE0030h ds:002b:3ad42c62`c37d96d1=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032be100
ffffffffffffffff
FOLLOWUP_IP:
atikmdag+376fce
fffff880`07becfce 8178083000bebe cmp dword ptr [rax+8],0BEBE0030h
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88007c3307f to fffff88007becfce
STACK_TEXT:
fffff880`027ff908 fffff880`07c3307f : 00000000`00000000 00000000`00000001 00000000`00000230 fffffa80`07f96470 : atikmdag+0x376fce
fffff880`027ff910 00000000`00000000 : 00000000`00000001 00000000`00000230 fffffa80`07f96470 fffffa80`03eaa010 : atikmdag+0x3bd07f
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+376fce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ddc6c20
STACK_COMMAND: .cxr 0xfffff880027fef20 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+376fce
BUCKET_ID: X64_0x7E_atikmdag+376fce
Followup: MachineOwner
---------

060213-12729-01.dmp

читать дальше »

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver...tPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89b9025d9, Reserved
Arg2: b3b7465eee0e627b, Reserved
Arg3: fffff880035de540, Failure type dependent information
Arg4: 0000000000000003, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030dac00
STACK_TEXT:
fffff880`037af5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9b9025d9 b3b7465e`ee0e627b fffff880`035de540 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: BAD_STACK
Followup: MachineOwner
---------

060513-12558-01.dmp

dxgmms1.sys (DirectX Graphics MMS)
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

читать дальше »

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: fffff880073d8ec8, The address that the exception occurred at
Arg3: fffff88002b9f6a8, Exception Record Address
Arg4: fffff88002b9ef00, Context Record Address

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`073d8ec8 8b4810 mov ecx,dword ptr [rax+10h]
EXCEPTION_RECORD: fffff88002b9f6a8 -- (.exr 0xfffff88002b9f6a8)
ExceptionAddress: fffff880073d8ec8 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002b9ef00 -- (.cxr 0xfffff88002b9ef00)
rax=00d4104d96004ab9 rbx=fffff8a00e6d13e0 rcx=fffffa80055ea000
rdx=fffffa8004246880 rsi=fffffa80055ea000 rdi=fffffa80055ea000
rip=fffff880073d8ec8 rsp=fffff88002b9f8e0 rbp=fffffa80081f05f0
r8=fffffa80075a5401 r9=0000000000000000 r10=0000000000000000
r11=00000000000002fe r12=fffffa8004246880 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`073d8ec8 8b4810 mov ecx,dword ptr [rax+10h] ds:002b:00d4104d`96004ac9=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ae100
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`073d8ec8 8b4810 mov ecx,dword ptr [rax+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880073d5ff7 to fffff880073d8ec8
STACK_TEXT:
fffff880`02b9f8e0 fffff880`073d5ff7 : 00000000`00000000 fffffa80`0498c1f8 00000000`000000bf 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`02b9f910 fffff880`073f07d9 : 00000000`00000000 fffff8a0`04b6d920 fffffa80`00000000 fffffa80`075a54a0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`02b9fae0 fffff880`073f0514 : fffff800`00b96080 fffff880`073eff00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02b9fcd0 fffff880`073f0012 : 00000000`00000000 fffffa80`07630010 00000000`00000080 fffffa80`05542410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02b9fd00 fffff800`03314ede : 00000000`02379890 fffffa80`0553db50 fffffa80`039ceb30 fffffa80`0553db50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02b9fd40 fffff800`03067906 : fffff800`031f1e80 fffffa80`0553db50 fffff800`031ffcc0 fffff880`03982210 : nt!PspSystemThreadStartup+0x5a
fffff880`02b9fd80 00000000`00000000 : fffff880`02ba0000 fffff880`02b9a000 fffff880`02b9f680 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13
STACK_COMMAND: .cxr 0xfffff88002b9ef00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Followup: MachineOwner
---------