KonQbenT utworzono 27 grudnia 2009 utworzono 27 grudnia 2009 (edytowane) Witam, Mam problem z GPU bo przynajmniej taki błąd wyświetla mi Windows po ukazaniu się pulpitu. Oto 1-szy błąd z dwóch jakie wyskakują: GPU.exe Assertion failed: m_pNvInit!=NULL&&m_pNvGetGPUCount!=NULL && m_pNvGetGPUName!=NULL && m_pNvGetGPUType!=NULL && m_pNvGetGPUMcmCapacity!=NULL && m_pNvGetGPUClockInfo!=NULL && m_pNvSetGPUClockInfo!=NULL && m_pNvUnInitialize!=NULL,225 A oto druga wiadomość która pokazuję się po wyłączeniu poprzedniej: GPU.exe Abnormal program termination Normalnie by mi to nie przeszkadzało ale podczas grania w jakiekolwiek gry wyświetla mi się niebieski obraz i komputer restartuje się. Coś tam jest napisane Driver_(coś)_(coś)_less dokladnie nie widzę bo komputer za szybko się restartuję Info o kompie, może będzie potrzebne: płyta główna : Asus M4A785T-M procek : AMD Athlon(tm)II X2 245 2.91GHZ grafika : Geforce 9400GT PCI-Express 1024 DDR2 M-RAM: 1024 DDR3 1333 mH System operacyjny : Windows XP Pofessional sp2 Proszę o pomoc jak się pozbyć tego problemu ( Nie umiem sam tego zrobić, a to wygląda dosyć poważnie Z góry thx
b.mazur komentarz 27 grudnia 2009 komentarz 27 grudnia 2009 Ten niebieski obraz to BSOD poczytaj i wykonaj te czynnosci : [url="http://www.forumpc.pl/index.php?showtopic=16074"]http://www.forumpc.pl/index.php?showtopic=16074[/url] [url="http://www.forumpc.pl/index.php?showtopic=68409"]http://www.forumpc.pl/index.php?showtopic=68409[/url]
KonQbenT komentarz 28 grudnia 2009 Autor komentarz 28 grudnia 2009 Zrobiłem jak wyżej napisano - Miałem 5 plików w Minidumpie. Nie wiedziałem który wybrać więc wkleje wszystkie : 1. * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {495e3, 2, 1, f78c6e20} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.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 : usbohci.sys ( usbohci+2e20 ) Followup: MachineOwner --------- 2. * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {0, 1c, 0, 80004fff} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys *** WARNING: Unable to verify timestamp for nv4_disp.dll *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.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: 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 : nv4_disp.dll ( nv4_disp+a3054 ) Followup: MachineOwner --------- 3. * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c000001d, f7004376, f7a07b34, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for CLASSPNP.SYS *** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS *** WARNING: Unable to verify timestamp for atapi.sys *** ERROR: Module load completed but symbols could not be loaded for atapi.sys *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.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 : CLASSPNP.SYS ( CLASSPNP+c70 ) Followup: MachineOwner --------- 4. * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {10, 2, 0, f04e562e} ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : portcls.sys ( portcls+62e ) Followup: MachineOwner --------- 5. * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {0, 0, 0, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for ACPI.sys *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys *** WARNING: Unable to verify timestamp for ASACPI.sys *** ERROR: Module load completed but symbols could not be loaded for ASACPI.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 : ASACPI.sys ( ASACPI+7f0 ) Followup: MachineOwner --------- Ja nie bardzo wiem o co chodzi w tym ale może ktoś mógłby mi wyjaśnić i pomóc a na Blue Screenie jest taki problem : Driver_Irql_not_less_or_equal informacje techniczne: *** STOP: 0x000000D1 (0x0000004c, 0x00000002, 0x00000000, 0xF7864381) *** PartMgr.sys - Address F7864381 base at F7864000, DateStamp 367dc6a7 Proszę o pomoc (
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.