Sprzęr:
AMD Phenom II X4 podręcony do 3,7
gtx 560
4gb ram corsair
600w corsair cx
sterowniki zainstalowane prawie najnowsze od grafiki.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`0303de50
Debug session time: Thu Jun 2 14:10:56.110 2011 (GMT+2)
System Uptime: 0 days 1:41:06.827
Page 4009ec too large to be in the dump file.
Page 402f68 too large to be in the dump file.
Page 402fd9 too large to be in the dump file.
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
..Page 400c81 too large to be in the dump file.
.Page 400c8e too large to be in the dump file.
.Page 400ca2 too large to be in the dump file.
.Page 400d00 too large to be in the dump file.
.Page 400e3c too large to be in the dump file.
.Page 400ee0 too large to be in the dump file.
.Page 400eef too large to be in the dump file.
.Page 400f46 too large to be in the dump file.
.Page 400f4f too large to be in the dump file.
.Page 400f59 too large to be in the dump file.
.Page 400f8c too large to be in the dump file.
.Page 400f99 too large to be in the dump file.
.Page 400fae too large to be in the dump file.
.Page 400c00 too large to be in the dump file.
.Page 400fc3 too large to be in the dump file.
.Page 400fca too large to be in the dump file.
.Page 400fda too large to be in the dump file.
.Page 400ff4 too large to be in the dump file.
.Page 400e00 too large to be in the dump file.
.Page 400e2a too large to be in the dump file.
.Page 4010eb too large to be in the dump file.
.Page 401137 too large to be in the dump file.
.Page 401246 too large to be in the dump file.
.Page 40114b too large to be in the dump file.
.Page 401200 too large to be in the dump file.
.Page 401000 too large to be in the dump file.
.Page 40121a too large to be in the dump file.
.Page 40122b too large to be in the dump file.
.Page 4014dc too large to be in the dump file.
.Page 401400 too large to be in the dump file.
.Page 401460 too large to be in the dump file.
.Page 401601 too large to be in the dump file.
.Page 40148b too large to be in the dump file.
.Page 4015ce too large to be in the dump file.
.Page 401073 too large to be in the dump file.
.Page 4015de too large to be in the dump file.
.Page 4015e6 too large to be in the dump file.
.Page 4011a9 too large to be in the dump file.
.Page 4013e9 too large to be in the dump file.
.Page 4015f0 too large to be in the dump file.
.Page 400dc0 too large to be in the dump file.
.Page 4011e3 too large to be in the dump file.
.Page 4018a1 too large to be in the dump file.
.Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at 006d0061`00720067 - NTSTATUS 0xC0000141
Image path too long, possible corrupt data.
Loading unloaded module list
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
...Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.
WARNING: .reload failed, module list may be incomplete
The context is partially valid. Only x86 user-mode context is available.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002e95c0f, 0, ffffffffffffffff}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Page 400eef too large to be in the dump file.
Page 4014dc too large to be in the dump file.
Page 401601 too large to be in the dump file.
Page 4010eb too large to be in the dump file.
Page 401246 too large to be in the dump file.
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Page 4009e8 too large to be in the dump file.
Page 402f64 too large to be in the dump file.
Page 402fd5 too large to be in the dump file.
*************************************************************************
*** ***
*** ***
*** 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlmp.exe ( nt!RtlSubAuthoritySid+10f )
Followup: MachineOwner
---------
32.0: kd:x86> !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: fffff80002e95c0f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Page 400eef too large to be in the dump file.
Page 4014dc too large to be in the dump file.
Page 401601 too large to be in the dump file.
Page 4010eb too large to be in the dump file.
Page 401246 too large to be in the dump file.
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Page 4009e8 too large to be in the dump file.
Page 402f64 too large to be in the dump file.
Page 402fd5 too large to be in the dump file.
*************************************************************************
*** ***
*** ***
*** 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 <symbol_path> 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 <symbol_path> 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: fffff80002e00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!RtlSubAuthoritySid+10f
02e95c0f f00fba6b1000 lock bts dword ptr [ebx+10h],0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffffffffffffff
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000001a7abd0
STACK_TEXT:
05b8fb70 00000000 00000000 00000000 00000000 0x1a7abd0
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!RtlSubAuthoritySid+10f
02e95c0f f00fba6b1000 lock bts dword ptr [ebx+10h],0
SYMBOL_NAME: nt!RtlSubAuthoritySid+10f
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
