kobyll utworzono 7 sierpnia 2008 utworzono 7 sierpnia 2008 Witam Moj zestaw to: E2160 1,8@3,0 Msi Neo2 FIR P35 bios v1.6 ustawienia standardowe optymalne GeForce 8800GT 512MB Palit Patriot LLK 2x2GB 800MHz 2,2V 4-4-4-12-32-12-12-12 Dysk 320GB WD Caviar WD3200AAKS SATA II 16MB CACHE DVD-REC PIONEEr DVR-215BK Technisat TT-Budget s-3200 DVB-S2 Creative Audigy 2 ZS GOLD @ audigy 4 softmod Komputer ogolnie działa bez zarzutu ale tylko na filmach oraz internecie, jak włacze gre to pogram moze 10-15 minut i blue screen "IRQL NOT LESS OR EQUAL" i reset Dopiero co zmieniłem pamieci z OCZ Platinum rev.2 na których było to samo. Nowe pamieci srawdzone memtestem i wszystko OK. Zasilanie tez srawdzone pod obciażeniem wszystkie napiecia OK 12V-12,3V 5V-5,15V 3,3V- 3,4V Dysk również sprawdzony. Zero BAD-ow. Windows SP2 zaden przerabiany typu "windows MX" czy inny, czysty Windws XP SP2. Prosze o sprawdzenie loga: koncowka Probably caused by : ntoskrnl.exe ( nt+1e6f8 ) całość Loading Dump File [C:\WINDOWS\minidump\Mini080708-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 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.exeWindows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0Debug session time: Thu Aug 7 17:07:24.843 2008 (GMT+2)System Uptime: 0 days 0:26:28.591********************************************************************** 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 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.exeLoading Kernel Symbols................................................................................................................................Loading User SymbolsLoading unloaded module list.............******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000000A, {c0031c34, 2, 0, 804f56f8}***** Kernel symbols are WRONG. Please fix symbols to do analysis.*** WARNING: Unable to verify timestamp for Ntfs.sys*** ERROR: Module load completed but symbols could not be loaded for Ntfs.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 ****** ******************************************************************************* WARNING: Unable to verify timestamp for fltMgr.sys*** ERROR: Module load completed but symbols could not be loaded for fltMgr.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 ****** ************************************************************************************************************************************************** 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 : ntoskrnl.exe ( nt+1e6f8 )Followup: MachineOwner---------
Mateusz J. komentarz 7 sierpnia 2008 komentarz 7 sierpnia 2008 Poczytaj: http://www.forumpc.pl/index.php?showtopic=59932 W podanym temacie chodzi o ten sam plik co u Ciebie, czyli ntoskrnl.exe.
kobyll komentarz 7 sierpnia 2008 Autor komentarz 7 sierpnia 2008 Poczytaj: http://www.forumpc.pl/index.php?showtopic=59932W podanym temacie chodzi o ten sam plik co u Ciebie, czyli ntoskrnl.exe. Wgrałem najnowsze sterowniki do graficznej 175.19_geforce_winxp_32bit_international_whql oraz nowego DirectX z aug_2008 potem autopatchera najnowszego zrobilem aktualizacje windowsa xp i nic a teraz wyskoczylo takie cos jeszcze Probably caused by : nv4_disp.dll ( nv4_disp+1a7097 )
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.