witam
Mam problem ze sformatowaniem dysku!
Kupiłem dysk HDD Samsung 160GB SATA i mam partycję systemową na .
30gb a pozostała część dysku została wolna i niesformatowana.
Chce sformatować sobie ją ale przy okazji cały dysk więc razem z partycją systemową. Więc wkładam płytkę z windowsem do napędu i gdy pisze że naciśnięcie klawisza spowoduje rozruch z CD. Więc naciskam spację…
Wtedy pokazuje się tło i ładują sie wszystkie pliki. Po załadowaniu instalator chce przejść dalej, ale pojawia się niebieskie tło z jakimiś napisami i wyłącza się komputer… A co za tym idzie nie mam możliwości sformatowania dysku…
Wiem że możecie mi pomóc, bo macie duże pojęcie o komputerach i że potrzebujecie kod który jesyt obok napisu STOP w tym błedzie. Więc podaję to co pisze i licze na waszą wiedzę i pomoc z waszej strony…
*** STOP: 0x0000007E (0xC0000005,0xF853D0BF,0xF8989208,0xF8988F08)
*** pci.sys-Address F853D0BF base at F8536000,DateStamp 3b7d855c
to było to co przepisałem…
Proszę o pomoc
sniper00
(sniper00)
19 Styczeń 2007 17:43
#2
a twoja płyta główna obsługiwała dyski tej wielkości? może update bios`u by pomogło…napisz jaki masz sprzęt…bo sama wielkość dysku wiele nie mówi…
Na paru innych forach czytałem o tym problemie. W tamtych przypadkach pomogła zmiana płyty instalacyjnej na inną lub oryginalną kopię. Czy twoja wersja win xp jest legalna?
moja płyta główna to MSI K9NU NEO-V M1697 AM2
Jest to nowa płyta wiec raczej mam pewnoiść że obsługuje takie dyski…
Próbowałem na mojej oryginalnej oraz pożyczałem kopie od kumpli i nic!! A moze to być spowodowane uszkodzeniem pamięci??
therock
(Rob O)
19 Styczeń 2007 20:22
#5
podales winie sterowniki do sata (F6 na poczatku instalki) ? bo bez nie rozpozna hdd sata.
nie wciskalem F6 bo do tego momentu już nie doszłem!! Zaraz pojawia się ten błąd!!
Joan
(Joan Sunshine)
19 Styczeń 2007 22:21
#7
Spróbuj najpierw podmienić pci.sys via konsola odzyskiwania.
expand X:\i386\pci.sy_ c:\windows\system32\drivers
X - litera cd-rom.
Przeczytaj to: KLIK i wklej zawartość pliku minidump
posiadam 12 minidumpów!! ;/
nie wiem czy to nie za duzo;/
bede wklejal po kolei…
myślę ż mi pomożecie…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Tue Nov 21 15:59:22.765 2006 (GMT+1) System Uptime: 0 days 0:27:48.343 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, a2ab6850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner
następny
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Tue Nov 21 16:01:43.734 2006 (GMT+1) System Uptime: 0 days 0:01:40.312 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, a37d0850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
następny
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Tue Nov 21 16:01:43.734 2006 (GMT+1) System Uptime: 0 days 0:01:40.312 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, a37d0850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
następny
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Tue Nov 21 16:01:43.734 2006 (GMT+1) System Uptime: 0 days 0:01:40.312 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, a37d0850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Wed Nov 22 13:57:50.687 2006 (GMT+1) System Uptime: 0 days 0:52:13.276 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, 9c659850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Wed Nov 22 14:06:01.687 2006 (GMT+1) System Uptime: 0 days 0:04:16.265 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, a55a0850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Thu Nov 23 16:12:59.000 2006 (GMT+1) System Uptime: 0 days 3:11:02.600 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, f8743850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Sat Nov 25 11:05:36.656 2006 (GMT+1) System Uptime: 0 days 2:17:35.235 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, 9cd42850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Sat Nov 25 11:07:24.093 2006 (GMT+1) System Uptime: 0 days 0:01:28.671 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, aacbf850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Sat Nov 25 12:24:58.968 2006 (GMT+1) System Uptime: 0 days 0:21:42.560 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, 9c72a850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Sat Nov 25 12:35:01.453 2006 (GMT+1) System Uptime: 0 days 0:07:23.031 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, 9fcca850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
nast…
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Sat Nov 25 12:42:25.656 2006 (GMT+1) System Uptime: 0 days 0:05:45.234 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image 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 … Unable to load image ati3duag.dll, Win32 error 2 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfc77846, aae46850, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : ati3duag.dll ( ati3duag+1ec846 ) Followup: MachineOwner ---------
To sa te pliki co wyskakują
Myślę że mi pomożecie…
Pozdrawiam
Złączono Posty : 20.01.2007 (Sob) 14:17
pisze w tych bledach cos z ati… wiec myslalem ze są złe stery od karty…
Więc zainstalowałem najnowsze i dalej nie moge formatowac…
Może mi ktoś pomóc!!
Błagam
jch-root
(jch-root)
20 Styczeń 2007 21:38
#9
Może zworki na dysku masz źle poustawiane, jeśli masz jeden dysk to powinien być ustawiony jako MASTER (MA), podłączony do SATA 0 i najlepiej wyłączyć RAID w biosie (jeśli jest włączony). Karta graficzna nie ma tu nic do rzeczy.
Ponadto na tej stronce jest “NVIDIA M1697 Chipset Driver”
Jak ściągniesz i rozpakujesz “NVIDIA_M1697_2K_XP.zip” znajdziesz tam folder FLOPPY. Przekopiuj pliki dla Twojego systemu operacyjnego na dyskietkę i zaraz po odpaleniu płytki z windowsem wciśnij F6, pisałeś że nie dochodzisz do momentu monitu wciśnięcia F6 - jest on na samym początku.
robert9990
(Robert99 90)
21 Styczeń 2007 11:01
#10
a to gdy będę włączał ponownie windowsa i nacisne spację aby czytał z płyty to ma by włożona dyskietka z tym skopiowanym plikiem??
Złączono Posty : 21.01.2007 (Nie) 12:08
a nie jest to do kart geForce??
ja mam Radeona…
Pomóżcie…
Piwollo
(Piwollo)
21 Styczeń 2007 11:20
#11
Tak, to jest do kart ATI.
Możę pamięć RAM, źle leży w budzie?
robert9990
(Robert99 90)
21 Styczeń 2007 11:24
#12
sprawdziłem wszystko…Pamięc dobrze leży, a może znasz jakis inny powód??
jch-root
(jch-root)
21 Styczeń 2007 12:12
#13
“NVIDIA M1697 Chipset Driver” ,a nie video driver. Twoja płyta jest na “chipsecie” NVIDII i to nie ma nic wspólnego z kartą graficzną!
TAK
robert9990
(Robert99 90)
21 Styczeń 2007 13:46
#14
Niestety nic to nie daje…
Robiłem już wszystko co napisalście a bluescreen dalej wyskakuje…
Co jeszcze może byc przyczyną??
jch-root
(jch-root)
21 Styczeń 2007 14:38
#15
A dobrze nagrałeś te sterowniki na dyskietkę? Przeczytaj dokładnie instrukcję! Zawsze możesz użyć innych narzędzi do formatowania dysku np. KLIK
marek624
(Ferdek31)
21 Styczeń 2007 15:40
#16
a SP 2 masz zainstalowanego? O ile dobrze zrozumiałem na tych 30 GB masz zainstalowany xp?
Złączono Posty : 21.01.2007 (Nie) 16:43
zobacz tu: http://support.microsoft.com/kb/839641/en-us
robert9990
(Robert99 90)
21 Styczeń 2007 19:49
#17
tak, napewno dobrze te sterowniki skopiowałem.
Na 30gb mam zainstalowanego win xp, a 130gb zostało wolne niesformatowane i chciałbym to sformatowac, bo tam bym umieszczał wszystkie większe pliki…
Pomocy…
Złączono Posty : 21.01.2007 (Nie) 20:51
no niby to jest to ale nie rozumiem po angielsku i nie wiem co tam pisze… może ktoś pomoże??
marek624
(Ferdek31)
21 Styczeń 2007 19:58
#18
tam pisze, że powodem takiego błędu może być brak dodatku SP2
robert9990
(Robert99 90)
21 Styczeń 2007 20:29
#19
a skad mam ten dodatek wziąc?? Z jakiejś strony pobrac?? Bo nie mam pojęcia…
szymoo2
(Szymoo)
21 Styczeń 2007 20:47
#20
sp2 można pobrać ze strony microsoftu sp2
Ale tu chodzi o to aby podczas instalacji win xp był już zintegrowany z sp2
instrukcja klik
bądź
klik
Złączono Posty : 21.01.2007 (Nie) 22:09
A i jeszcze Tu jest
http://forum.dobreprogramy.pl/viewtopic.php?t=111531 jak zintegrowac
xp z sp2