Results 1 to 21 of 21
Thread: 35
Hybrid View
-
3rd September 2007 10:30 #1
-
4th September 2007 02:31 #2
. C:\WINDOWS\Minidump , . .
Gigabyte P35-DS3R, E6320 435x7, 2x1gb SuperT T800UX1GC4, SAPPHIRE X1950GT, Seagate 320GB ST3320620AS, Asus 1814BLT, Fortron Bluestorm II 500W, Dell 228WFP
-
4th September 2007 10:18 #3
a + .
http://flex.data.bg/Mini090307-06.dmp
http://pr0x.hit.bg/IntelChipset.log
2 . 1 2 .. .
WoW , ?
-
4th September 2007 10:26 #4
, power setting - change plan settings - change advanced power settings - Hard disk - Turn off hrd disk after - Never (0).
...
-
4th September 2007 13:02 #5
-
4th September 2007 13:16 #6
-
4th September 2007 13:17 #7
, Vista, , . , . , .
Nikon D60, Nikkor AF-S DX 18-55mm, f/3.5-5.6G ED II
-
4th September 2007 14:54 #8
, 1 warning events
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
?
-
5th September 2007 16:42 #9
, , . +sp2 10, . , . + - tcpip.sys.
,
Gigabyte P35-DS3R, E6320 435x7, 2x1gb SuperT T800UX1GC4, SAPPHIRE X1950GT, Seagate 320GB ST3320620AS, Asus 1814BLT, Fortron Bluestorm II 500W, Dell 228WFP
-
5th September 2007 23:05 #10
-
6th September 2007 22:00 #11
windbg.exe debugging windows:
http://support.microsoft.com/kb/824344
dxgkrnl.sys, "DirectX Graphics Kernel". , -.
directx:
http://support.microsoft.com/kb/940105/
. :
http://oca.microsoft.com/en/windiag.asp
, .Gigabyte P35-DS3R, E6320 435x7, 2x1gb SuperT T800UX1GC4, SAPPHIRE X1950GT, Seagate 320GB ST3320620AS, Asus 1814BLT, Fortron Bluestorm II 500W, Dell 228WFP
-
6th September 2007 22:45 #12
-
7th September 2007 01:22 #13
a dxgkrnl.sys BSOD 2 4,
2 . 4Code:Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\V. Stanchev\Desktop\Mini090507-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 2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x82000000 PsLoadedModuleList = 0x82108ab0 Debug session time: Wed Sep 5 00:09:48.915 2007 (GMT+3) System Uptime: 0 days 0:36:58.559 ********************************************************************* * 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 2 *** 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 A, {88c036f4, ff, 0, 821d3e34} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for laPP.sys *** ERROR: Module load completed but symbols could not be loaded for laPP.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : laPP.sys ( laPP+339 ) Followup: MachineOwner ---------
lapp.sys; dxgkrnl.sys win32k.sys
WowLast edited by PROXIMO; 7th September 2007 at 01:32.
-
8th September 2007 15:11 #14
To . 163.11
kCode:*** WARNING: Unable to verify timestamp for ndis.sys *** ERROR: Module load completed but symbols could not be loaded for ndis.sys Probably caused by : tcpip.sys ( tcpip+6b405 ) Followup: MachineOwner
-
8th September 2007 15:49 #15
, , . . , , , . , . . 100 % .
EVGA X299 FTW K|i9-7960X@4.7|4x8 Patriot Viper Steel 4000|GTX 1660 Ti|970 EVO 1 TB|Seasonic Focus GX-1000|Xigmatek Elysium|
Rampage IV Extreme BE|E5-1680v2@4.7|4x4 HyperX 1866|Cougar Aqua 240|GTX 1050 Ti|970 EVO 1/4 TB|CM 850 SilentPro|HAF-X|
-
8th September 2007 20:06 #16
-
8th September 2007 23:08 #17
. .
, . , 24 , . 10 , . , .EVGA X299 FTW K|i9-7960X@4.7|4x8 Patriot Viper Steel 4000|GTX 1660 Ti|970 EVO 1 TB|Seasonic Focus GX-1000|Xigmatek Elysium|
Rampage IV Extreme BE|E5-1680v2@4.7|4x4 HyperX 1866|Cougar Aqua 240|GTX 1050 Ti|970 EVO 1/4 TB|CM 850 SilentPro|HAF-X|
-
9th September 2007 17:26 #18
. BSOD .
2 1 , , .
______
24
Probably caused by : dxgkrnl.sys ( dxgkrnl+238cb )Last edited by PROXIMO; 9th September 2007 at 17:41.
-
9th September 2007 17:56 #19
, , - . .
EVGA X299 FTW K|i9-7960X@4.7|4x8 Patriot Viper Steel 4000|GTX 1660 Ti|970 EVO 1 TB|Seasonic Focus GX-1000|Xigmatek Elysium|
Rampage IV Extreme BE|E5-1680v2@4.7|4x4 HyperX 1866|Cougar Aqua 240|GTX 1050 Ti|970 EVO 1/4 TB|CM 850 SilentPro|HAF-X|
-
9th September 2007 18:03 #20
, / 4 1 1 2 5 , . . Video Card Stability .
( , )
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
edit
Probably caused by : nvlddmkm.sys ( nvlddmkm+517ac )
Last edited by PROXIMO; 9th September 2007 at 19:21.
-
9th September 2007 19:25 #21







Reply With Quote
windwos 10
05.05.23 ., 00:01 in Windows