Здравствуйте, потратил полчаса или более, но так и не нашел где мне задать мой вопрос, даже следуя вышеприведенным советам.
В общем, хотелось бы узнать результат анализа минидампа, так как слишком много инфы в нем, спасибо
Analyzing "C:\Windows\Minidump\091313-21828-01.dmp", please wait... Done.
Didn't find the answer. Try again with '-v' switch.
C:\Users\Docent>kdfe "%systemroot%\Minidump\091313-21828-01.dmp" -v
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091313-21828-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/symbol
s
Executable search path is: srv*c:\symbols *
http://msdl.microsoft.com/download/s
ymbols
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x8341c000 PsLoadedModuleList = 0x8355c230
Debug session time: Fri Sep 13 19:18:12.094 2013 (GMT+9)
System Uptime: 0 days 10:06:38.157
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
......
0: kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c029e14c, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000009d, error status (normally i/o status code)
Arg3: 5632fbe0, current process (virtual address for lock type 3, or PTE)
Arg4: a7853000, virtual address that could not be in-paged (or PTE contents if a
rg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 834b73b2 to 834ee21c
STACK_TEXT:
80ef0b44 834b73b2 0000007a c029e14c c000009d nt!KeBugCheckEx+0x1e
80ef0bac 834c8f6d 80ef0c08 8357c300 80ef0c14 nt!MiWaitForInPageComplete+0x2fa
80ef0c2c 8347cc94 8357c300 a7853000 8756fa00 nt!MiIssueHardFault+0x3b6
80ef0c98 834a886a 00000001 a7853000 00000000 nt!MmAccessFault+0x1fef
80ef0d10 834b478e 8a027238 c029e150 00000000 nt!MiInPageSingleKernelStack+0x16c
80ef0d44 834803af 8a0272ac 80ef0d90 8360452a nt!KiInSwapKernelStacks+0x41
80ef0d50 8360452a 00000000 ad854f8d 00000000 nt!KeSwapProcessOrStack+0x78
80ef0d90 834a5899 83480337 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiWaitForInPageComplete+2fa
834b73b2 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiWaitForInPageComplete+2fa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 51db7a55
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x7a_c000009d_nt!MiWaitForInPageComplete+2fa
BUCKET_ID: 0x7a_c000009d_nt!MiWaitForInPageComplete+2fa
Followup: MachineOwner
---------
quit:
C:\Users\Docent>
