Здравствуйте, у меня возникла проблема, началось это примерно 2-3 дня назад при просмотре видео через MPC-HomeCinema.1.5.0.2827.x64. Через какие то промежутки времени появляется синий экран. (скрин последнего дампа http://s017.radikal.ru/i441/1112/b6/250bedb0f2cf.jpg). Так же возникали ошибки с файлами L1C62x64.sys, 121111-39234-01.dmp 11.12.2011 14:06:39 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000003`656e7075 00000000`00000002 00000000`00000000 fffff800`03417977 hal.dll hal.dll+4977 x64 C:\Windows\minidump\121111-39234-01.dmp 4 15 7601, ntoskrnl.exe, но дампов к сожалению нет. Скан системы, диагностику памяти, HDD делал - ошибок не обнаружено. Уже всё перепробовал, ничего не помогает. Спасибо.
Вот последний анализ дампа:
Microsoft Windows [Version 6.1.7601]
© Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
C:\Windows\system32>C:\bsod\kfde.cmd C:\windows\minidump\121211-67127-01.dmp -v
"C:\bsod\kfde.cmd" не является внутренней или внешней
командой, исполняемой программой или пакетным файлом.
C:\Windows\system32>C:\bsod\kdfe.cmd C:\windows\minidump\121211-67127-01.dmp -v
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121211-67127-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: srv*C:\symbols*http://msdl.microsoft.com/download/sym
bols
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0341c000 PsLoadedModuleList = 0xfffff800`03661670
Debug session time: Mon Dec 12 21:27:06.669 2011 (GMT+4)
System Uptime: 0 days 2:54:02.121
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8011409010, fffff8800f62c9c8, 0, d}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sy
s
Probably caused by : nvlddmkm.sys ( nvlddmkm+1759c8 )
Followup: MachineOwner
---------
1: kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8011409010, Optional pointer to internal TDR recovery context (TDR_R
ECOVERY_CONTEXT).
Arg2: fffff8800f62c9c8, The pointer into responsible device driver module (e.g.
owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operat
ion.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+1759c8
fffff880`0f62c9c8 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`026069c8 fffff880`048b4000 : 00000000`00000116 fffffa80`11409010 fffff8
80`0f62c9c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`026069d0 fffff880`048b3d87 : fffff880`0f62c9c8 fffffa80`11409010 fffffa
80`0fb4d450 fffffa80`0c2ef010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02606a10 fffff880`0495af07 : fffffa80`11409010 00000000`00000000 fffffa
80`0fb4d450 fffffa80`0c2ef010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`02606a40 fffff880`04984b75 : 00000000`ffffffff 00000000`000a35d5 000000
00`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02606b20 fffff880`049832bb : 00000000`00000102 00000000`00000005 000000
00`000a35d5 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02606b50 fffff880`049562c6 : ffffffff`ff676980 fffffa80`0c2ef010 000000
00`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02606bf0 fffff880`04982e7a : 00000000`00000000 fffffa80`0fb4d450 000000
00`00000080 fffffa80`0c2ef010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02606d00 fffff800`03733fee : 00000000`fffffc32 fffffa80`0c2e6770 fffffa
80`03aea740 fffffa80`0c2e6770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02606d40 fffff800`0348a5e6 : fffff880`033d3180 fffffa80`0c2e6770 fffff8
80`033ddfc0 fffff880`01646384 : nt!PspSystemThreadStartup+0x5a
fffff880`02606d80 00000000`00000000 : fffff880`02607000 fffff880`02601000 fffff8
80`0cfb7b40 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f62c9c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------