oto co udało mi się znaleźć w pliku minidump
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\Users\krzysiek\Desktop\040815-78437-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\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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03053890
Debug session time: Wed Apr 8 12:13:20.261 2015 (GMT+2)
System Uptime: 0 days 0:01:57.915
*********************************************************************
* 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\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 19, {20, fffffa800b353210, fffffa800b353230, 4020021}
Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
***** 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!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 <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 : tcpip.sys ( tcpip+8cd26 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800b353210, The pool entry we were looking for within the page.
Arg3: fffffa800b353230, The next pool entry.
Arg4: 0000000004020021, (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 <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: tcpip
FAULTING_MODULE: fffff80002e0f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 533f5bd4
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffffa800b353210
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fb8cbe to fffff80002e83ec0
STACK_TEXT:
fffff880`0b91d2e8 fffff800`02fb8cbe : 00000000`00000019 00000000`00000020 fffffa80`0b353210 fffffa80`0b353230 : nt+0x74ec0
fffff880`0b91d2f0 00000000`00000019 : 00000000`00000020 fffffa80`0b353210 fffffa80`0b353230 00000000`04020021 : nt+0x1a9cbe
fffff880`0b91d2f8 00000000`00000020 : fffffa80`0b353210 fffffa80`0b353230 00000000`04020021 fffff880`0168cd26 : 0x19
fffff880`0b91d300 fffffa80`0b353210 : fffffa80`0b353230 00000000`04020021 fffff880`0168cd26 fffffa80`0b353230 : 0x20
fffff880`0b91d308 fffffa80`0b353230 : 00000000`04020021 fffff880`0168cd26 fffffa80`0b353230 fffff880`0b91d3b0 : 0xfffffa80`0b353210
fffff880`0b91d310 00000000`04020021 : fffff880`0168cd26 fffffa80`0b353230 fffff880`0b91d3b0 fffffa80`0a86f430 : 0xfffffa80`0b353230
fffff880`0b91d318 fffff880`0168cd26 : fffffa80`0b353230 fffff880`0b91d3b0 fffffa80`0a86f430 fffff880`016447b8 : 0x4020021
fffff880`0b91d320 fffffa80`0b353230 : fffff880`0b91d3b0 fffffa80`0a86f430 fffff880`016447b8 fffffa80`00000004 : tcpip+0x8cd26
fffff880`0b91d328 fffff880`0b91d3b0 : fffffa80`0a86f430 fffff880`016447b8 fffffa80`00000004 fffffa80`00000011 : 0xfffffa80`0b353230
fffff880`0b91d330 fffffa80`0a86f430 : fffff880`016447b8 fffffa80`00000004 fffffa80`00000011 fffff880`0000b900 : 0xfffff880`0b91d3b0
fffff880`0b91d338 fffff880`016447b8 : fffffa80`00000004 fffffa80`00000011 fffff880`0000b900 00000000`00000002 : 0xfffffa80`0a86f430
fffff880`0b91d340 fffffa80`00000004 : fffffa80`00000011 fffff880`0000b900 00000000`00000002 00000000`00000002 : tcpip+0x447b8
fffff880`0b91d348 fffffa80`00000011 : fffff880`0000b900 00000000`00000002 00000000`00000002 00000000`00000000 : 0xfffffa80`00000004
fffff880`0b91d350 fffff880`0000b900 : 00000000`00000002 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`00000011
fffff880`0b91d358 00000000`00000002 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000006 : 0xfffff880`0000b900
fffff880`0b91d360 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000006 00000000`00000006 : 0x2
fffff880`0b91d368 00000000`00000000 : 00000000`00000000 00000000`00000006 00000000`00000006 fffff880`0176d9a0 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip+8cd26
fffff880`0168cd26 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: tcpip+8cd26
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: tcpip.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800b353210, The pool entry we were looking for within the page.
Arg3: fffffa800b353230, The next pool entry.
Arg4: 0000000004020021, (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 <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: tcpip
FAULTING_MODULE: fffff80002e0f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 533f5bd4
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa800b353210
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fb8cbe to fffff80002e83ec0
STACK_TEXT:
fffff880`0b91d2e8 fffff800`02fb8cbe : 00000000`00000019 00000000`00000020 fffffa80`0b353210 fffffa80`0b353230 : nt+0x74ec0
fffff880`0b91d2f0 00000000`00000019 : 00000000`00000020 fffffa80`0b353210 fffffa80`0b353230 00000000`04020021 : nt+0x1a9cbe
fffff880`0b91d2f8 00000000`00000020 : fffffa80`0b353210 fffffa80`0b353230 00000000`04020021 fffff880`0168cd26 : 0x19
fffff880`0b91d300 fffffa80`0b353210 : fffffa80`0b353230 00000000`04020021 fffff880`0168cd26 fffffa80`0b353230 : 0x20
fffff880`0b91d308 fffffa80`0b353230 : 00000000`04020021 fffff880`0168cd26 fffffa80`0b353230 fffff880`0b91d3b0 : 0xfffffa80`0b353210
fffff880`0b91d310 00000000`04020021 : fffff880`0168cd26 fffffa80`0b353230 fffff880`0b91d3b0 fffffa80`0a86f430 : 0xfffffa80`0b353230
fffff880`0b91d318 fffff880`0168cd26 : fffffa80`0b353230 fffff880`0b91d3b0 fffffa80`0a86f430 fffff880`016447b8 : 0x4020021
fffff880`0b91d320 fffffa80`0b353230 : fffff880`0b91d3b0 fffffa80`0a86f430 fffff880`016447b8 fffffa80`00000004 : tcpip+0x8cd26
fffff880`0b91d328 fffff880`0b91d3b0 : fffffa80`0a86f430 fffff880`016447b8 fffffa80`00000004 fffffa80`00000011 : 0xfffffa80`0b353230
fffff880`0b91d330 fffffa80`0a86f430 : fffff880`016447b8 fffffa80`00000004 fffffa80`00000011 fffff880`0000b900 : 0xfffff880`0b91d3b0
fffff880`0b91d338 fffff880`016447b8 : fffffa80`00000004 fffffa80`00000011 fffff880`0000b900 00000000`00000002 : 0xfffffa80`0a86f430
fffff880`0b91d340 fffffa80`00000004 : fffffa80`00000011 fffff880`0000b900 00000000`00000002 00000000`00000002 : tcpip+0x447b8
fffff880`0b91d348 fffffa80`00000011 : fffff880`0000b900 00000000`00000002 00000000`00000002 00000000`00000000 : 0xfffffa80`00000004
fffff880`0b91d350 fffff880`0000b900 : 00000000`00000002 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`00000011
fffff880`0b91d358 00000000`00000002 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000006 : 0xfffff880`0000b900
fffff880`0b91d360 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000006 00000000`00000006 : 0x2
fffff880`0b91d368 00000000`00000000 : 00000000`00000000 00000000`00000006 00000000`00000006 fffff880`0176d9a0 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip+8cd26
fffff880`0168cd26 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: tcpip+8cd26
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: tcpip.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> lmvm tcpip
start end module name
fffff880`01600000 fffff880`017ff000 tcpip T (no symbols)
Loaded symbol image file: tcpip.sys
Image path: \SystemRoot\System32\drivers\tcpip.sys
Image name: tcpip.sys
Timestamp: Sat Apr 05 03:26:44 2014 (533F5BD4)
CheckSum: 001D5F45
ImageSize: 001FF000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4sprawdzałem ram za pomocą memtest86 i dyski za pomocą hd tune i brak błędów
już nie wiem co mam robić
prosze o pomoc
dziękuje wszystkim za pomoc 
