korzi

******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1E, {ffffffffc0000005, fffff80002bab0a2, 0, ffffffffffffffff}***** 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 ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** 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+3440a2 )Followup: MachineOwner--------- ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 50, {fffff6ba80036970, 0, fffff8000285d5f3, 5}Could not read faulting driver nameProbably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+468 )Followup: MachineOwn ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck BE, {fffff6fb40003fd8, d00000489f9025, fffff88007781780, b}***** 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 ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** 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+71f00 )Followup: MachineOwner--------- Sprzet Karta Graficzna : Asus GeForce GTX 260 GL+ 896MB DDR3 Procesor : Intel Core 2 Duo E7400 + BOX Płyta Główna : ASRock TurboTwins2000 Zasilacz : OCZ 500W StealthXStream Pamięć : OCZ 4GB (2x2GB) 1333MHz CL9 Gold Dysk Twardy : Western Digital Black 320GB 7200rpm 16MB cache SATAII Napęd : LG GH22NS50 SATA Obudowa : Logic B21 Oprogramowanie : Windows 7 Ultimate x64 Temperatury OK

a co myslicie o Cooler Master Elite 310 ??? Witam mam zamiar kupic chłodzenie do procesora e7400 moja płyta ASROCK P45TurboTwins2000 mam do wydania 150 zł

opłaca się kupić taką bude ???

do 200 zł

Witam mam zamiar kupić obudowę za w miarę rozsądne pieniądze. Sprzęt GTX 260 Asus Core 2 Duo E7400 ASRock TurboTwins2000 OCZ 500W Ram Ocz 2x2Gb 1333 320gb WD Naped LG

Witam Sprzet GTX 260 Asus Core 2 Duo E7400 ASRock TurboTwins2000 Zasilacz Modecom Premium 500W Ram Ocz 2x2Gb 1333 2 x 320gb WD Naped LG 2 x wentylatory Podczas gry po 10 minutach gra nie odpowiada i wyskakuje blue screen z nfts.sys , win32k.sys i wiele innych po przesiadce z win7 na Viste to samo. Wydaje mi sie ze posiadam za slaby zasilacz :rolleyes:

ustawiłem i działa dzieki stary :D

a to może byc przez zasilacz bo posiadam Modecom 500w Sprzet Karta Graficzna GTX 260 Procesor C2D E7400 RAM 2x2 OCz HD 320gb WD Płyta Główna AsRock TurboTwins2000 bo słyszałem ze karta wymaga min 550w ale ja mam 64 bitowy i te dostepne pokazuje mi od wczoraj

Posiadam tego asusa i jest głośny i się troche grzeje ale jest wydajny POLECAM tez miałem ten dylemat i nie żałuje .

Witam mam problem z bluescreenamu chyba 3 inne 1 Had pool header a 2 win32k.sys i 3 nie pamietam co zrobic acha i co znaczy ze 3.19 gb ram mam dostepne

nie 1500

bo kumpel mi sprzedał komputer ale z zepsuty zasilaczem

GTX 260 zdecydowanie

Core @ Duo E7400 Ocz 4 gb Ram Gtx 260 AsRock TurboTwins 2000 zasilacz Modecom 500W

Dosyc dobry komp 4 gb ram jaki Windows

A to co podałem jest złe ???

Jaki zasilacz do tego sprzetu GTX 260 Asus Core 2 Duo E7400 ASRock TurboTwins2000 Ram Ocz 2x2Gb 1333 zastanawiam sie nad tym mam ok 220 zl http://www.agito.pl/zasilacze/ocz-stealthx...w.0.344704.html