raporty z minidumpa
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011712-15802-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d52810
Debug session time: Tue Jan 17 20:02:34.100 2012 (GMT+1)
System Uptime: 0 days 0:14:27.364
*********************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\usbohci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbohci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 1, 918e8a66}
*
Probably caused by : usbohci.sys ( usbohci+2a66 )
Followup: MachineOwner
Kod: Zaznacz cały
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {874d7b20, 8707f188, 87071850, 1}
Probably caused by : ati2cqag.dll ( ati2cqag+3c6c0 )
Followup: MachineOwner
---------
