Looper

a moze lepiej jakiegos epoxa ?? slyszalem ze maja najwieksze wozliwosci oc a ja chce to pod oc kupic

Witam chcę rozbudować kompa i zaczynam od wymiany MOBO, RAMu i Procka. Procka już wybrałem, ale wybierzcie mi z tego co jest poniżej najlepsza plyte i ram do niego. PROCESOR AMD SEMPRON 2300+/333 SOCA BOX PŁYTY: ASUS A7N8X-VM GIGABYTE KT600 SATA AGP X8 ASUS A7V600-F GIGABYTE 7VAX KT400 AGPX8 GIGABYTE 7VT880-RZ ALBO ZNAJDZCIE MI JAKAS LEPSZA NA ALLEGRO DO 170 zł. RAM: GoodRam 256/400 DDR 70 zł Kingston 256/ 400 DDR 75 zł

mialem wczesniej ta karte tak nagle te bluescreeny zaczely wyskakiwac...:( system byl pare razy juz karta reinstalowany i bylo ok ...teraz jak juz sa bluescreeny to 3 razy reinstalowalem i dalej to samo

to samo :(

yhy tylko gdzie to opylic ten zlom i na ile to wycenic ?? a jakies konkretne propozycje czegos na amd ??

Witam! Dysponuję sprzętem jak z podpisu i 350 zł. Teraz pytanie najważniejsze - co wymienić za te pieniądze a co podkręcać żeby uzyskać jak największą wydajność i stabilność z tego starocia??

Witam ! Mam problem z ciągłymi bluescreenami ! Poniżej załączam minidumpy ! Aha, zaznaczam ze plik tiaclxn.sys to plik sterownika od karty radiowej i nie moge znalezc nowszych, jakby cos to prosze o pomoc - karta to PLANET WL-8305. MINIDUMPY: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {ee657645, 2, 0, 804dc80d} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image Ntfs.sys, Win32 error 2 *** 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 *** *** *** ************************************************************************* Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {6c626174, 2, 0, f82c04fb} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image psched.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for psched.sys *** ERROR: Module load completed but symbols could not be loaded for psched.sys Unable to load image tcpip.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.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 *** *** *** ************************************************************************* Probably caused by : tiacxln.sys ( tiacxln+14fb ) Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, cd4, 746c7573, 815af008} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd unable to get nt!MiSessionPoolStart unable to get nt!MiSessionPoolEnd ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_POOL_TRACKER_BIG_PAGES *** *** *** ************************************************************************* Cannot get _POOL_TRACKER_BIG_PAGES type size ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_POOL_TRACKER_BIG_PAGES *** *** *** ************************************************************************* Cannot get _POOL_TRACKER_BIG_PAGES type size Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, 81384000, 81384860, b0c732f} ***** 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 *** *** *** ************************************************************************* unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd unable to get nt!MiSessionPoolStart unable to get nt!MiSessionPoolEnd ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_POOL_TRACKER_BIG_PAGES *** *** *** ************************************************************************* Cannot get _POOL_TRACKER_BIG_PAGES type size Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {a9b23227, 2, 0, f6bc54fb} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image psched.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for psched.sys *** ERROR: Module load completed but symbols could not be loaded for psched.sys Unable to load image tcpip.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.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 *** *** *** ************************************************************************* Probably caused by : tiacxln.sys ( tiacxln+14fb ) Followup: MachineOwner ---------

witam ! musisz zapisac instalke w jakims folderze na innej partycji niz systemowa i z poziomu wiersza polecen wejsc w ten folder i uruchomic setup.exe ;] pozdr!

na modecomie od kumpla to samo sie dzieje, odkurzylem kompa i nic to nie dalo :( system byl juz 2 razy reinstalowany od kiesy zaczal sie problem ale i tak zalaczam log z hijacka : Logfile of HijackThis v1.99.1 Scan saved at 09:58:00, on 2005-06-12 Platform: Windows XP Dodatek SP. 1 (WinNT 5.01.2600) MSIE: Internet Explorer v6.00 SP1 (6.00.2800.1106) Running processes: C:\WINDOWS\System32\smss.exe C:\WINDOWS\system32\services.exe C:\WINDOWS\system32\lsass.exe C:\WINDOWS\system32\svchost.exe C:\WINDOWS\System32\svchost.exe C:\WINDOWS\system32\LEXBCES.EXE C:\WINDOWS\system32\spoolsv.exe C:\WINDOWS\system32\LEXPPS.EXE C:\Program Files\Netropa\Multimedia Keyboard\nhksrv.exe C:\WINDOWS\Explorer.EXE C:\WINDOWS\System32\nvsvc32.exe C:\Program Files\22M WLAN Adapter\WLANMON.exe C:\Program Files\Netropa\Multimedia Keyboard\TrayMon.exe C:\Program Files\Netropa\Onscreen Display\OSD.exe C:\Program Files\Mozilla Firefox\firefox.exe C:\Program Files\WinRAR\WinRAR.exe C:\DOCUME~1\Kokon\USTAWI~1\Temp\Rar$EX00.871\HijackThis.exe O20 - Winlogon Notify: drct16 - C:\WINDOWS\SYSTEM32\drct16.dll O23 - Service: LexBce Server (LexBceS) - Lexmark International, Inc. - C:\WINDOWS\system32\LEXBCES.EXE O23 - Service: Netropa NHK Server (nhksrv) - Unknown owner - C:\Program Files\Netropa\Multimedia Keyboard\nhksrv.exe O23 - Service: NVIDIA Display Driver Service (NVSvc) - NVIDIA Corporation - C:\WINDOWS\System32\nvsvc32.exe Proszę o pomoc !!!

prawie za kazdym razem wyskakuje inny - nic nie zmienialem i nnie przepinalem :. wszystko jak bylo ... w ktoryms z wyzszych postow sa raporty z 3 roznych minidumpów .....różnych wyskakujacych bluskrinów jest jeszcze wiecej

to teraz juz dokonalem wszystkich czynnosci podanych przez kolegow i dalej problem sie powtarza wyniki moich pomiarow napiec zasilacza : MIERZENIA DOKONYWAŁEM NA OBCIĄŻENIU Prime95 i defragmentatorem dysków "5v" molex - napięcie mojego zasilacza waha się 4.97 - 4.99 "12v" molex - napięcie mojego zasilacza waha się 12.34 - 12.36 wtyczka ATX "3.3v" - napięcie mojego zasilacza waha się 3.43 - 3.44 CO teraz mam począć ?? już nie mogę wytrzymać z tymi cholernymi bluscreenami :sad:

zrobilem wszystkie te czynnosci oprocz mierzenia napiec zasilacza - problem dalej wystepuje, jak przy pomocy miernika zmierzyc napiecia zasilacza i jakie powinny byc ??

juz wiem czemu resety - mam wlaczone w panelu sterowania itd itp. - wutomatycznie resetuj komputer w razie awarii - teraz mi zamiast reseta sie wywala bluscreen. zaraz dam na forum raport z debugging toolsa . juz są - raporty z 3 bugów :P NAJNOWSZY RAPORT :::: - Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini060905-03.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 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 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30 Debug session time: Thu Jun 9 17:56:51.046 2005 (GMT+2) System Uptime: 0 days 0:10:51.634 ********************************************************************* * 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 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 unloaded module list ............ Loading User Symbols Unable to load image win32k.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {fffffff0, 0, 8057fa73, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Probably caused by : win32k.sys ( win32k+264b0 ) Followup: MachineOwner --------- RAPORT Z POPRZEDNIEGO BUGA : Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini060905-02.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 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 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30 Debug session time: Thu Jun 9 17:43:15.681 2005 (GMT+2) System Uptime: 0 days 2:08:47.270 ********************************************************************* * 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 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 unloaded module list .................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C5, {4, 2, 1, 8053d5af} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner --------- RAPORT Z JESZCZE WCZESNIEJSzEGO BUGA : Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini060605-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 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 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30 Debug session time: Mon Jun 6 18:22:25.770 2005 (GMT+2) System Uptime: 0 days 1:18:56.350 ********************************************************************* * 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 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 unloaded module list .......... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 804fa31b, f5a9182c, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. PROSZĘ o pomoc i rozszyfrowanie. Muszę to naprawić bo już z tym dłuzej nie wytrzymam.

problem w tym ze nie jest krecony a temperatury takie jak zawsze w normie CPU 30 stopni itp.

Witam ! Mam problem. Otóż od mniej więcej 1,5 miesiąca komputer co jakiś czas po prostu sam się resetuje. Jest to strasznie denerwujące. Nie mogę zostawić sprzętu na noc żeby coś ściągać bo co parę minut się resetuje :( Przeinstalowałem system - bez rezultatu. Wypiąłęm kabelek od resetu na MOBO - bez rezultatu. Przełożyłem karty do innych slotów PCI - bez rezultatu. Nie wiem co mam robić. Pomóżcie mi proszę. Co może być przyczyną i jak zlikwidować usterkę ?