jasiekwroc

Witam od paru dni mam użycie ramu 2/4 gb gdy nie mam prawie zadnych programów włączonych, tutaj screen :

witam mam problem od paru dni z moim google chrome'em, a wiec nawet teraz podczas pisania tego postu musiałem wejsc przez ie bo w chrome nie moglem nic pisac mialem ikone "pisania" zamiast normalnego kursora ale nic sie nie pisało nawet animacja początkowa pisania sie nie wyświetlała, w poczcie tak samo gdy chce napisać email ta sama sytuacja czasem nie wczytuje mi nie których elementów w ogole np jakis obrazkow albo formularzy, próbowałem przeinstalować adobe flash player i jave ale nic nie dało ;/, z góry dziekuje za pomoc ;)

Witam uporałem się dziś z problem brakującego pliku NTLDR ale teraz niestety mam kolejny ,gdy wczytuje mi sie logo asusa a potem boot.ini to komputer nastepnie restartuje i tam bez przerwy do poki nie uruchomie go z bootowanego pendrive, prosze o szybką pomoc.

Witam mam problem z tym dziwnym zjawiskiem a mianowicie akceleracją wsteczną, chodzi o to że zrobiłem już wszystko : OFF w myszce "zwiększ precyzje wskaźnika" MarkC_Windows7_MouseFix - dodany do rejestru w sterownikach off. a nadal w grze mysz skacze i odskakuje czasem Mam Windows 7 64bit , Myszke : Deathadder respawn , Sterowniki : 3.01 , Firmeware 2.41 i podkładka destructor Właściwie to nie wiem czy to wina akceleracji czy windows x64 W grze wygląda to tak że nagle mysz zaczyna skakać na 0.5 cm w górę i w dół po przesuwaniu w linii poziomej dopiero po podniesieniu myszki z podkładki i opuszczeniu jej problem ustępuje, 2 to kursor sam odskakuje w bok.

Witam, mam plan aby kupić destructora ponieważ teraz na QcK moj deathadder na 3500 dpi trochę odskakuję, i teraz właśnie nie wiem czy kupić destructora czy coś innego abym miał płynność przy 3.5G odskakuje * - tzn ze przy 3500 dpi sensor przy robieniu kółek (test sprawdzający) na pulpicie nie chodzi gładko a skacze na lewo/prawo

Witam, mam plan aby kupić destructora ponieważ teraz na QcK moj deathadder na 3500 dpi trochę odskakuję, i teraz właśnie nie wiem czy kupić destructora czy coś innego abym miał płynność przy 3.5G odskakuje * - tzn ze przy 3500 dpi sensor przy robieniu kółek (test sprawdzający) na pulpicie nie chodzi gładko a skacze na lewo/prawo

Witam mam taki problem z moim deathadderem respawn , gdy robię kółko na pulpicie mysz porusza się na lewo/prawo mam ustawione 3500dpi i 500Hz , w fps'ach np. tf2 to naprawe przeszkadza bo nie chodzi płynnie, mam najnowsze sterowniki i firmware , win 7 64 bit , probowałem zmienić dpi, Hz , ustawienia w sterach def.

Witam mam taki problem z moim deathadderem respawn , gdy robię kółko na pulpicie mysz porusza się na lewo/prawo mam ustawione 3500dpi i 500Hz , w fps'ach np. tf2 to naprawe przeszkadza bo nie chodzi płynnie, mam najnowsze sterowniki i firmware , win 7 64 bit , probowałem zmienić dpi, Hz , ustawienia w sterach def.

Witam mam problem z myszka a raczej jej płynnością ruchową , mam myszke Deathadder respawn (wczoraj kupiłem) ustawiłem na 3500 dpi i teraz gdy np w sterownikach razera testuje płynność ruchową (test area) to mysz nie dość że odskakuje to jeszcze nie chodzi płynnie tylko przerywa co robiem : reinstall sterowników (nic) zmiana dpi(już mniej odskakuje ale też) odinstalowanie z portów usb (nic) Windows 7 64 bit. podkładka QcK medium

to samo gram na blacie bo x750 na QcK jeszcze bardziej skacze, na zwykłej kartce to samo

Witam mam problem z myszka USB od 2 dni mam taki dziwny problem gdyż podczas codziennej pracy kursor w losowych momentach o 1cm (0.5mm) przesuwa się w dowolne miejsce,(mam 7 x64) 2 dni temu próbowałem zrobić to : PC Hardware :: Changing Usb Polling Rate To 1000hz Or Lower nie wiem czy to ma jakiś wpływ , próbowałem już zmienić port USB bez skutku.

tak przy grach spec: phenom II 940 oc 3.5 GTX 275 oc RAM 4 GB przez 6 miesięcy chodziło dobrze , niedawno czyściłem komputer od wewnątrz

Witam od niedawna bluescreeny zdarzają się coraz cześciej, oto przykład 6 miesięcy chodził dobrze(po oc) a tu nagle myśle że to chyba wadliwe oprogramowanie z Windows Update tutaj czyt. Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\081410-20420-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50 Debug session time: Sat Aug 14 18:31:01.705 2010 (GMT+2) System Uptime: 0 days 8:13:17.719 ********************************************************************* * 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 ......... *** WARNING: Unable to verify timestamp for hal.dll *** ERROR: Module load completed but symbols could not be loaded for hal.dll ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8004b3e028, b674c000, 135} ***** 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!_WHEA_ERROR_RECORD_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!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PSHED.dll *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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!_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 : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa8004b3e028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000b674c000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value. 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!_WHEA_ERROR_RECORD_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!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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!_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. FAULTING_MODULE: fffff80002c59000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff800`00ba8ac8 fffff800`02c22903 : 00000000`00000124 00000000`00000000 fffffa80`04b3e028 00000000`b674c000 : nt+0x70740 fffff800`00ba8ad0 00000000`00000124 : 00000000`00000000 fffffa80`04b3e028 00000000`b674c000 00000000`00000135 : hal+0x12903 fffff800`00ba8ad8 00000000`00000000 : fffffa80`04b3e028 00000000`b674c000 00000000`00000135 fffffa80`04bcb010 : 0x124 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 0: kd> !analyze -v ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa8004b3e028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000b674c000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value. 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!_WHEA_ERROR_RECORD_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!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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: pshed!_WHEA_ERROR_RECORD_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!_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. FAULTING_MODULE: fffff80002c59000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff800`00ba8ac8 fffff800`02c22903 : 00000000`00000124 00000000`00000000 fffffa80`04b3e028 00000000`b674c000 : nt+0x70740 fffff800`00ba8ad0 00000000`00000124 : 00000000`00000000 fffffa80`04b3e028 00000000`b674c000 00000000`00000135 : hal+0x12903 fffff800`00ba8ad8 00000000`00000000 : fffffa80`04b3e028 00000000`b674c000 00000000`00000135 fffffa80`04bcb010 : 0x124 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner

Witam mam problem z gta 4 gdy gram single czy multi mam co jakiś czas taką zwieche ekranu na 0,5 s np. jak jade autem czy szybko biegne mam najnowsze patche, probowalem tez contigiem, nie chodzi tu o fps bo mam stałe 60

działa poprawnie ale niestety mam wtedy lag myszy (mouse lag)

Witam mam problem z klatkami (fps) na t240hd w grach np kiedy mi spada do 80-100 fps to wygląda to jak 30-20 a w innych grach gdzie jest 50-60 to wyglada jak 20-30 slyszalem ze to jest od duzego monitora, czy jest jakis fix na to ?

raczej tam szybkiej odp się nie doczekam...

Witam mam problem z grą TF2 fps są w niej słabe na moim sprzęcie nie powinno spadac ponizej 100, a jak wychodze na środek mapy i jest strzelanka to mam ok 50-40 fps mam gtx 275 OC, phenom II 940 3,5 , T240HD (1920x1200) i 4GB ram windows 7 64 bit mam AA x2 reszta na full mam też specialne komendy typu : refresh, 32bit , itp. CnQ off

Witam mam problem z grą TF2 fps są w niej słabe na moim sprzęcie nie powinno spadac ponizej 100, a jak wychodze na środek mapy i jest strzelanka to mam ok 50-40 fps mam gtx 275 OC, phenom II 940 3,5 , T240HD (1920x1200) i 4GB ram windows 7 64 bit mam AA x2 reszta na full mam też specialne komendy typu : refresh, 32bit , itp. CnQ off

team fortress 2

nic konkretnego napisali tam dlatego odświeżyłem ten temat

potrojne buforowanie on max prerendered frames jest na 0 nadal to samo pc: gtx 275 oc phenom II 940 oc ram 4gb

Witam. Wiec teraz tak... powiem w skrocie bo nie chce mi sie rozpisywac. jak wlacze vsynca obraz jest naprawde ok - miodzio ALE MAM "pływajaca mysz" tzn mouse smoothnes i nie da sie jej normalnie kontrolowac. jak wylacze vsync mysz chodzi tak jak powinna ale szarpie mi obraz TAK CZY SIAK NIE DA SIE GRAC. wiec pytanie jak sobie poradzic z tym tarciem ekranu z vsync OFF. Sterowniki nvidi mam najnowsze 257.21 pc dobry monitor t240hd

Witam mam problem z zmianą częstotliwość odświeżania mam 59HZ domyślnie wiem że może mieć max 75 max, moge tylko zmienić (lista wyboru) na 60HZ ale i tak się nie zmienia ponieważ jak zmieniam na 60 , wchodzę ponownie w opcje a tu nadal 59 HZ mam najnowsze sterowniki nvidii screen z pulpitu : Imageshack - beztytuuapa.jpg screen z rivatuner : Imageshack - beztytuu2uo.jpg

Witam mam problemy w 7 1.Po włączeniu systemu tak może co drugi raz ikony się przestawiają i gadżety w prawy górny rogu 2.Po włączeniu systemu myszka wychodzi poza prawy bok ekranu dopiero po włączeniu prawym przyciskiem myszki "Panel Sterowania NVidia" ekran mignie raz i juz jest normalnie 3.Po włączeniu systemu czasem mam brak sygnału na monitorze "Samsung T240HD" karta graf. "GTX 275 Gigabyte" płyta główna "GA-MA790X-UD4 Gigabyte" Tutaj dołączam screen z ustawieniami : http://img20.imageshack.us/img20/5381/screenxk.png