В описание проблемы толком ничего нет, вот возможные варианты на эту ошибку, нужны логи
* неисправность процессора;
* чрезмерный разгон;
* недостаточная мощность или неисправность блока питания;
* недостаточное напряжение на процессоре (корректируется в настройках BIOS, особенно в случае разгона);
* неисправность материнской платы (например, опухшие конденсаторы в схеме питания процессора);
* несовместимость процессора/памяти/материнской платы (на всякий случай можно обновить BIOS).
В журналах ничего особенного, проблема аппаратная это факт, у меня подозрения, что это произошло после обновления системы. Вот сделал анализ дампа:
C:\>"C:\Program Files\Debugging Tools for Windows (x86)\dumpchk.exe" -y C:\WINDO
WS\Symbols C:\win.dmp
Loading dump file C:\win.dmp
Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\win.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:\WINDOWS\Symbols'
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image 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.ex
e
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01a06000 PsLoadedModuleList = 0xfffff800`01c43e50
Debug session time: Fri Feb 18 21:15:01.285 2011 (GMT+7)
System Uptime: 29 days 20:38:37.463
Unable to load image 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.ex
e
Loading Kernel Symbols
..............................................Unable to load image Unknown_Modul
e_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007230028, fe000000, 1009f}
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : hardware
Followup: MachineOwner
---------
----- 64 bit Kernel Mini Dump Analysis
DUMP_HEADER64:
MajorVersion 0000000f
MinorVersion 00001db0
KdSecondaryVersion 00000000
DirectoryTableBase 00000000`00187000
PfnDataBase fffff800`01cae220
PsLoadedModuleList fffff800`01c43e50
PsActiveProcessHead fffff800`01c25b30
MachineImageType 00008664
NumberProcessors 00000008
BugCheckCode 00000124
BugCheckParameter1 00000000`00000000
BugCheckParameter2 fffffa80`07230028
BugCheckParameter3 00000000`fe000000
BugCheckParameter4 00000000`0001009f
KdDebuggerDataBlock fffff800`01bef070
ProductType 00000002
SuiteMask 00000110
WriterStatus 00000002
MiniDumpFields 00000cff
TRIAGE_DUMP64:
ServicePackBuild 00000000
SizeOfDump 00040000
ValidOffset 0003fffc
ContextOffset 00000348
ExceptionOffset 00000f00
MmOffset 00002080
UnloadedDriversOffset 000020d0
PrcbOffset 000020d8
ProcessOffset 00006dd8
ThreadOffset 000072a8
CallStackOffset 00007740
SizeOfCallStack 000003b0
DriverListOffset 00007e30
DriverCount 0000002f
StringPoolOffset 000098a0
StringPoolSize 00000578
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack fffff800`01926c50
BStoreOffset 00000000
SizeOfBStore 00000000
LimitOfBStore 00000000`00000000
DebuggerDataOffset 00007af0
DebuggerDataSize 00000340
DataBlocksOffset 00009e18
DataBlocksCount 0000000d
fffff800`01c442e0 - fffff800`01c4437b at offset 00009ee8
fffff800`01c2c0ec - fffff800`01c2c0ef at offset 00009f84
fffff800`01c2c0e8 - fffff800`01c2c0eb at offset 00009f88
fffff800`01bb5880 - fffff800`01bb597f at offset 00009f8c
fffffa80`07230000 - fffffa80`07230fff at offset 0000a08c
fffff800`01c7ac60 - fffff800`01c7ac63 at offset 0000b08c
fffff800`01c7a860 - fffff800`01c7a88f at offset 0000b090
fffff800`01cae074 - fffff800`01cae077 at offset 0000b0c0
fffff800`01cae068 - fffff800`01cae06b at offset 0000b0c4
fffff800`01926000 - fffff800`01926fff at offset 0000b0c8
fffffa80`07189000 - fffffa80`07189fff at offset 0000c0c8
fffff800`0200a000 - fffff800`0200afff at offset 0000d0c8
fffff800`01a13000 - fffff800`01a13fff at offset 0000e0c8
Max offset f0c8, 30f38 from end of file
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01a06000 PsLoadedModuleList = 0xfffff800`01c43e50
Debug session time: Fri Feb 18 21:15:01.285 2011 (GMT+7)
System Uptime: 29 days 20:38:37.463
start end module name
fffff800`01951000 fffff800`0195b000 kdcom Tue Jul 14 09:31:07 2009 (4A5BDF
DB)
fffff800`01a06000 fffff800`01fe2000 nt Sat Jun 19 12:16:41 2010 (4C1C44
A9)
fffff800`01fe2000 fffff800`0202b000 hal Tue Jul 14 09:27:36 2009 (4A5BDF
08)
fffff880`00c00000 fffff880`00cc0000 CI unavailable (00000000)
fffff880`00cda000 fffff880`00d1e000 mcupdate unavailable (00000000)
fffff880`00d1e000 fffff880`00d32000 PSHED unavailable (00000000)
fffff880`00d32000 fffff880`00d90000 CLFS unavailable (00000000)
fffff880`00dab000 fffff880`00dd5000 ataport unavailable (00000000)
fffff880`00e00000 fffff880`00e60000 NETIO unavailable (00000000)
fffff880`00e60000 fffff880`00e70000 PCIIDEX unavailable (00000000)
fffff880`00e7e000 fffff880`00f70000 NDIS unavailable (00000000)
fffff880`00f70000 fffff880`00fce000 msrpc unavailable (00000000)
fffff880`00fce000 fffff880`00fe8000 mountmgr unavailable (00000000)
fffff880`00fe8000 fffff880`00fff000 HpSAMD unavailable (00000000)
fffff880`01000000 fffff880`01033000 pci unavailable (00000000)
fffff880`01033000 fffff880`01040000 vdrvroot unavailable (00000000)
fffff880`01040000 fffff880`01055000 partmgr unavailable (00000000)
fffff880`01055000 fffff880`0106a000 volmgr unavailable (00000000)
fffff880`0106a000 fffff880`010c6000 volmgrx unavailable (00000000)
fffff880`010c6000 fffff880`010cd000 pciide unavailable (00000000)
fffff880`010d4000 fffff880`01178000 Wdf01000 unavailable (00000000)
fffff880`01178000 fffff880`01187000 WDFLDR unavailable (00000000)
fffff880`01187000 fffff880`011de000 ACPI unavailable (00000000)
fffff880`011de000 fffff880`011e7000 WMILIB unavailable (00000000)
fffff880`011e7000 fffff880`011f1000 msisadrv unavailable (00000000)
fffff880`011f1000 fffff880`011fa000 atapi unavailable (00000000)
fffff880`01200000 fffff880`01273000 cng unavailable (00000000)
fffff880`01273000 fffff880`0129e000 ksecpkg unavailable (00000000)
fffff880`0129e000 fffff880`012e8000 fwpkclnt unavailable (00000000)
fffff880`012ee000 fffff880`01350000 storport unavailable (00000000)
fffff880`01350000 fffff880`01369000 HpCISSs2 unavailable (00000000)
fffff880`01369000 fffff880`01374000 amdxata unavailable (00000000)
fffff880`01374000 fffff880`013c0000 fltmgr unavailable (00000000)
fffff880`013c0000 fffff880`013d5000 dfsrro unavailable (00000000)
fffff880`01400000 fffff880`01411000 pcw unavailable (00000000)
fffff880`01411000 fffff880`0141b000 Fs_Rec unavailable (00000000)
fffff880`0141b000 fffff880`0142b000 vmstorfl unavailable (00000000)
fffff880`01441000 fffff880`015e4000 Ntfs unavailable (00000000)
fffff880`015e4000 fffff880`015fe000 ksecdd unavailable (00000000)
fffff880`01600000 fffff880`017fd000 tcpip unavailable (00000000)
fffff880`0183c000 fffff880`01888000 volsnap unavailable (00000000)
fffff880`01888000 fffff880`01890000 spldr unavailable (00000000)
fffff880`01890000 fffff880`018a2000 mup unavailable (00000000)
fffff880`018a2000 fffff880`018ab000 hwpolicy unavailable (00000000)
fffff880`018ab000 fffff880`018c1000 disk unavailable (00000000)
fffff880`018c1000 fffff880`018f1000 CLASSPNP unavailable (00000000)
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007230028, fe000000, 1009f}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : hardware
Followup: MachineOwner
---------
Finished dump check
