Witam,
Przy otwarzaniu .mkv na TV komputer po ok. 30 min dostaje BSODa. Problem dotyczy hardware lub co gorsza boje się, że dysk już dostaje zadyszki i blisko mu śmierci 
proszę o pomoc wklejam zrzuty z minidump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17118.x86fre.win7_gdr.120830-0334
Machine Name:
Kernel base = 0x82a1a000 PsLoadedModuleList = 0x82b62810
Debug session time: Thu Jan 3 21:33:23.172 2013 (GMT+1)
System Uptime: 0 days 1:26:00.076
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {f362, 4, 0, 9519f200}
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.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+197200 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000f362, memory referenced
Arg2: 00000004, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 9519f200, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b82718
Unable to read MiSystemVaType memory at 82b62160
0000f362
CURRENT_IRQL: 4
FAULTING_IP:
nvlddmkm+197200
9519f200 395808 cmp dword ptr [eax+8],ebx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: mencoder.exe
TRAP_FRAME: 87f37a48 -- (.trap 0xffffffff87f37a48)
ErrCode = 00000000
eax=0000f35a ebx=00000017 ecx=00000000 edx=00000008 esi=0000f35a edi=00000002
eip=9519f200 esp=87f37abc ebp=87f37ac4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nvlddmkm+0x197200:
9519f200 395808 cmp dword ptr [eax+8],ebx ds:0023:0000f362=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 9519f200 to 82a5facb
STACK_TEXT:
87f37a48 9519f200 badb0d00 00000008 00000000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
87f37ac4 9519f21b 0000f35a 00000017 00000002 nvlddmkm+0x197200
87f37ae8 9519f21b 840ab440 00000017 00000002 nvlddmkm+0x19721b
87f37b0c 95257a8a 848a0000 00000017 00000002 nvlddmkm+0x19721b
87f37b30 95153706 848a0000 00000017 00000001 nvlddmkm+0x24fa8a
87f37b84 95153349 86334000 018a0000 00000001 nvlddmkm+0x14b706
87f37ba4 951584a1 86334000 00000000 848b32b0 nvlddmkm+0x14b349
87f37c68 9515360a 86334000 958361c8 85cab000 nvlddmkm+0x1504a1
87f37c80 950bf56a 85a8c008 85cabbec 85cab000 nvlddmkm+0x14b60a
87f37c9c 950c2201 00000000 9509f345 958361c8 nvlddmkm+0xb756a
87f37cd0 951104ef 950f6bf0 00000000 858b2a20 nvlddmkm+0xba201
87f37ce4 95a7d8ec 85cab000 00000000 87f37d08 nvlddmkm+0x1084ef
87f37cf4 95a8ec38 85eb8780 85a77020 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
87f37d08 82a58a6d 85eb8780 85a77020 87f37d34 dxgkrnl!DpiFdoLineInterruptRoutine+0x12
87f37d08 00bc5c6c 85eb8780 85a77020 87f37d34 nt!KiInterruptDispatch+0x6d
00bc5c50 00000000 00000000 00000000 00000000 0xbc5c6c
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+197200
9519f200 395808 cmp dword ptr [eax+8],ebx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nvlddmkm+197200
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 506b2f5b
FAILURE_BUCKET_ID: 0xD1_nvlddmkm+197200
BUCKET_ID: 0xD1_nvlddmkm+197200
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17118.x86fre.win7_gdr.120830-0334
Machine Name:
Kernel base = 0x82a39000 PsLoadedModuleList = 0x82b81810
Debug session time: Thu Jan 3 22:37:02.223 2013 (GMT+1)
System Uptime: 0 days 1:02:18.002
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8d863bf, 8abcda24, 0}
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
Probably caused by : partmgr.sys ( partmgr!PmReadWrite+112 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 08d863bf, The address that the exception occurred at
Arg3: 8abcda24, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
+31
08d863bf ?? ???
TRAP_FRAME: 8abcda24 -- (.trap 0xffffffff8abcda24)
ErrCode = 00000010
eax=00000103 ebx=858a1910 ecx=851cd918 edx=00000000 esi=858a1910 edi=8567bd80
eip=08d863bf esp=8abcda98 ebp=8abcda9c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
08d863bf ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8567a5d8 to 08d863bf
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8abcda94 8567a5d8 8abcdab4 82a74747 8567a5d8 0x8d863bf
8abcda9c 82a74747 8567a5d8 858a1910 858a1a50 0x8567a5d8
8abcdab4 888cb230 ba2d0000 858a1910 858a1910 nt!IofCallDriver+0x63
8abcdac8 888cb2e5 8567bd80 858a1a34 8567bcc8 partmgr!PmReadWrite+0x112
8abcdadc 82a74747 8567bcc8 858a1910 856830e8 partmgr!PmGlobalDispatch+0x1d
8abcdaf4 888dc9ae 858a1910 85683030 00000002 nt!IofCallDriver+0x63
8abcdb10 82a74747 85683030 858a1910 858a1910 volmgr!VmReadWrite+0x1a8
8abcdb28 88d51475 8568dd38 8abcdb50 88d51548 nt!IofCallDriver+0x63
8abcdb34 88d51548 8568dd38 858a1910 82afb626 fvevol+0x1475
8abcdb50 88d51759 8568dd38 858a1901 858a1a98 fvevol+0x1548
8abcdb80 88d517a9 8568dc80 858a1910 8abcdba8 fvevol+0x1759
8abcdb90 82a74747 8568dc80 858a1910 856894fc fvevol+0x17a9
8abcdba8 88d2f76e 856894a0 858a1910 00000003 nt!IofCallDriver+0x63
8abcdc88 88d2f8a5 856894a0 858a1910 00000000 rdyboost!SmdProcessReadWrite+0xa14
8abcdca8 82a74747 856894a0 858a1910 858a1ae0 rdyboost!SmdDispatchReadWrite+0xcb
8abcdcc0 88faafd9 8abcdd28 8568e5a8 848d04c0 nt!IofCallDriver+0x63
8abcdce8 88fab2fd 0068e5a8 858a1910 8abcdd10 volsnap!VolsnapWriteFilter+0x265
8abcdcf8 82a74747 8568e5a8 858a1910 8ab0f500 volsnap!VolSnapWrite+0x21
8abcdd10 88a2799f 8ab0f460 8abcdd34 82aa859e nt!IofCallDriver+0x63
8abcdd1c 82aa859e 8ab0f500 00000000 ffffffff Ntfs!NtfsStorageDriverCallout+0x14
8abcdd1c 82aa8695 8ab0f500 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
8ab0f470 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31
STACK_COMMAND: kb
FOLLOWUP_IP:
partmgr!PmReadWrite+112
888cb230 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: partmgr!PmReadWrite+112
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: partmgr
IMAGE_NAME: partmgr.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f641a99
FAILURE_BUCKET_ID: 0x8E_partmgr!PmReadWrite+112
BUCKET_ID: 0x8E_partmgr!PmReadWrite+112
Followup: MachineOwner
---------
