Расшифровка мини-дампа, после программы WinDbg

Loading Dump File [C:\Windows\Minidump\020815-35875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff801`2b876000 PsLoadedModuleList = 0xfffff801`2bb4c370
Debug session time: Sun Feb 8 22:15:46.478 2015 (UTC + 3:00)
System Uptime: 2 days 0:03:08.126
Loading Kernel Symbols
........................................ .......................
........................................ ........................
........................................ .....................
Loading User Symbols
Loading unloaded module list
............................
**************************************** ***************************************
* *
* Bugcheck Analysis *
* *
**************************************** ***************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff68007fb44a8, b2c000010a043886, fffff68000063c01}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a440 )

Followup: MachineOwner
---------

7: kd> !analyze -v
**************************************** ***************************************
* *
* Bugcheck Analysis *
* *
**************************************** ***************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff68007fb44a8
Arg3: b2c000010a043886
Arg4: fffff68000063c01

Debugging Details:
------------------


BUGCHECK_STR: 0x1a_411

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: livecomm.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8012b9ffaf0 to fffff8012b9c51a0

STACK_TEXT:
ffffd000`2666cdb8 fffff801`2b9ffaf0 : 00000000`0000001a 00000000`00000411 fffff680`07fb44a8 b2c00001`0a043886 : nt!KeBugCheckEx
ffffd000`2666cdc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2a440


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+2a440
fffff801`2b9ffaf0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2a440

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53fe6f2e

FAILURE_BUCKET_ID: X64_0x1a_411_nt!_??_::FNODOBFM::_string_ +2a440

BUCKET_ID: X64_0x1a_411_nt!_??_::FNODOBFM::_string_ +2a440

Followup: MachineOwner
---------

Добавлено через 8 минут
А вчера была другая ошибка:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\020615-31062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff801`5c48a000 PsLoadedModuleList = 0xfffff801`5c760370
Debug session time: Fri Feb 6 16:04:59.278 2015 (UTC + 3:00)
System Uptime: 4 days 8:42:31.925
Loading Kernel Symbols
........................................ .......................
........................................ ........................
........................................ .....................
Loading User Symbols
Loading unloaded module list
........................................ ...
**************************************** ***************************************
* *
* Bugcheck Analysis *
* *
**************************************** ***************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8015c5dbfcf, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+f )

Followup: MachineOwner
---------

4: kd> !analyze -v
**************************************** ***************************************
* *
* Bugcheck Analysis *
* *
**************************************** ***************************************

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

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!KiSwapContext+f
fffff801`5c5dbfcf 0f29742430 movaps xmmword ptr [rsp+30h],xmm6

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: fffff8015c74dd80: Unable to get special pool info
fffff8015c74dd80: Unable to get special pool info
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8015c624aa9 to fffff8015c5d91a0

STACK_TEXT:
ffffd000`229d8598 fffff801`5c624aa9 : 00000000`0000001e ffffffff`c0000005 fffff801`5c5dbfcf 00000000`00000000 : nt!KeBugCheckEx
ffffd000`229d85a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3b3f9


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiSwapContext+f
fffff801`5c5dbfcf 0f29742430 movaps xmmword ptr [rsp+30h],xmm6

SYMBOL_NAME: nt!KiSwapContext+f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53fe6f2e

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiSwapContext+f

BUCKET_ID: X64_0x1E_c0000005_nt!KiSwapContext+f

Followup: MachineOwner
---------

4: kd> lmvm nt
start end module name
fffff801`5c48a000 fffff801`5cc20000 nt (pdb symbols) C:\Program Files\Debugging Tools for Windows (x64)\sym\ntkrnlmp.pdb\E018720B8C414EF79 9EACB23114763921\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\53FE6F2E796000\nt oskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Thu Aug 28 02:52:14 2014 (53FE6F2E)
CheckSum: 007311DE
ImageSize: 00796000
File version: 6.3.9600.17328
Product version: 6.3.9600.17328
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.3.9600.17328
FileVersion: 6.3.9600.17328 (winblue_r3.140827-1500)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.