Это первый раз, когда это случилось с моим ноутбуком. Мой ноутбук использует i7 3612QM и 16 ГБ оперативной памяти и никогда не было проблем. Я также использую Windows 7-64 бит. Сегодня я запустил Windows нормально и сразу же, она поставила меня на синий экран с сообщением о дампе памяти. Следующее от минидампа:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091315-243096-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: * Invalid *
Symbol loading may be unreliable without a symbol search path. * Use .symfix to have the debugger choose a symbol path. * After setting your symbol path, use .reload to refresh symbol locations. *
**************************************************************************** Executable search path is:
Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: * using the _NT_SYMBOL_PATH environment variable. * using the -y argument when starting the debugger. * using .sympath and .sympath+ *
********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by:
7601.18939.amd64fre.win7sp1_gdr.150722-0600 Machine Name: Kernel base = 0xfffff8000340b000 PsLoadedModuleList = 0xfffff80003652730 Debug session time: Sun Sep 13 23:43:16.475 2015 (GMT+2) System Uptime: 3 days 20:50:22.350
Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: * using the _NT_SYMBOL_PATH environment variable. * using the -y argument when starting the debugger. * using .sympath and .sympath+ *
********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ........................................................... Loading User Symbols Loading unloaded module list ..................................................
* Bugcheck Analysis *
* Use !analyze -v to get detailed debugging information.
BugCheck 50, {2e294c0, 0, 77bef517, 8}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: * using the _NT_SYMBOL_PATH environment variable. * using the -y argument when starting the debugger. * using .sympath and .sympath+ * Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: * using the _NT_SYMBOL_PATH environment variable. * using the -y argument when starting the debugger. * using .sympath and .sympath+ *
********************************************************************* Probably caused by : ntoskrnl.exe ( nt+735c0 ) Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 0000000002e294c0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: 0000000077bef517, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000008, (reserved)
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols In order for this command to work properly, your symbol path must point to .pdb files that have full type information. Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work. Type referenced: nt!_KPRCB *
Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: * using the _NT_SYMBOL_PATH environment variable. * using the -y argument when starting the debugger. * using .sympath and .sympath+ * Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: * using the _NT_SYMBOL_PATH environment variable. * using the -y argument when starting the debugger. * using .sympath and .sympath+ * ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff8000340b000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 55afca65
READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000000002e294c0
FAULTING_IP: +6087952f04cbdc78 00000000`77bef517 ?? ???
MM_INTERNAL_CODE: 8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800034198a7 to fffff8000347e5c0
STACK_TEXT: fffff8800ea80978 fffff800034198a7 : 0000000000000050 0000000002e294c0 0000000000000000 fffff8800ea80ae0 : nt+0x735c0 fffff8800ea80980 0000000000000050 : 0000000002e294c0 0000000000000000 fffff8800ea80ae0 0000000000000008 : nt+0xe8a7 fffff8800ea80988 0000000002e294c0 : 0000000000000000 fffff8800ea80ae0 0000000000000008 fffff8800ea80ae0 : 0x50 fffff8800ea80990 0000000000000000 : fffff8800ea80ae0 0000000000000008 fffff8800ea80ae0 0000000000000000 : 0x2e294c0
STACK_COMMAND: kb
FOLLOWUP_IP: nt+735c0 fffff800`0347e5c0 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+735c0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
6: kd> lmvm nt start end module name fffff8000340b000 fffff800039f6000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe Image path: \SystemRoot\system32\ntoskrnl.exe Image name: ntoskrnl.exe Timestamp: Wed Jul 22 18:52:53 2015 (55AFCA65) CheckSum: 0055EED3 ImageSize: 005EB000 Translations: 0000.04b0 0000.04e4
0409.04b0 0409.04e4