Teknoloji Haberleri
| Merhabalar gecenlerde bir sey basima geldi kulaklikli mikrofon kullaniyorum online oyun oynarken arkadasm benim oynadigim.oyunun sesini nerdeyse benden cok duyuyor bu sistemsel hatayi nereden duzeltebilirim yardmci olabilecek arkadaslara simdiden tesekkurler |
H
Gönderiler
Hakkında
H
10 yıl
0 H
10 yıl
|
benim pc boştayken kitleniyor yada reset atıyor bi süre sonra ısınma problemi yok minidump ta şunlar yazıyordu yardımcı olabilirmisiniz ?? 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 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505 Kernel base = 0xfffff802`8ee19000 PsLoadedModuleList = 0xfffff802`8f0dd990 Debug session time: Wed Sep 9 14:31:08.555 2015 (GMT+3) System Uptime: 0 days 9:48:03.003 ********************************************************************* * 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 ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960002efc10, ffffd00021732e50, 0} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Unable to load image \SystemRoot\System32\drivers\volmgrx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for volmgrx.sys *** ERROR: Module load completed but symbols could not be loaded for volmgrx.sys ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 ( win32k+12bc10 ) Followup: MachineOwner 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 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505 Kernel base = 0xfffff803`ef81b000 PsLoadedModuleList = 0xfffff803`efadf990 Debug session time: Wed Sep 9 18:24:33.151 2015 (GMT+3) System Uptime: 0 days 2:43:01.231 ********************************************************************* * 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 ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff800014de23c, 8, fffff800014de23c, 0} ***** 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+14dca0 ) Followup: MachineOwner |
H
10 yıl
|
Herkese selamlar. Arkadaslarla butun phantom assg. gorevlerini yerine ggetirdim.ama is kutu bulmaya gelince pc kirma noktasina kadar geldim.yabanci forumlarda sitelerde gosterilen resimlerdeki yerlere gittigimde herhangi bir kutu bulamadim elinde guncel harita lokasyonlari olan yada napmam konusunda yardim edebilecek olan varmi ?? Sen bf+pre al 140 lvl ol hersey acik napuon oyunda kutu ariyorariyorum.cok zoruma gidiyor :) |
H
11 yıl
|
dün akşama kadar oynayabildiğim bf4 e girememeye başladığım ya çalışmayı durdurdu diyor yada tam oyuna join olduğumda ilk karşıma gelen haritada kitlenip kalıyor bütün herşeyi yaptım: -oyunu silip tekrar yükledim -oyunu repair yaptım -yazılım güncellemelerini kontrol ettim -punkboster i dirext leri v.s. tekrar yükledim kısacası herşeyi yaptım bu sorunla karşılaşanlar veya çözümü bilenler varsa yardımcı olabilirlermi. saygılar |
H
11 yıl
|
resimde yapabildiğim bu zamana kadarki en iyisi :S millet dediğim gbi bunlar 20 adam öldürerek yapıyor örnek olarak vereyim isteyen olursa resmide var 12 defa vurmuş 16 defa ölmüş 1 |
H
11 yıl
|
Arkadaslar merhaba 300 saat ustu bf4 oynamaktayim bolum icinde yeni yeni 20bin score leri goruyorum oda assault sinifi medic yani benim sorum su ben 100 kusur adam oldurerek 17 binleri zor goruyorum medic atip defibilatorle adam kaldirdigim halde ama adam 15-20 adam oldurerek 25 bin puanlari goruyor her yeri arastirdim video yada yabanci forumlarda bulamadim bu sitenin samimiyetine e ilgisine guvenerek yardimci olabilecek arkadaslardan cevap bekliyorm oyun ici goruntude becerebilrsem yuklicem < Resime gitmek için tıklayın > |
H
14 yıl
|
öncelikle selamlar..benim internetten araştırıpta çözemediğim bi sorun için umarım bana yardımcı olabilirsiniz....win7 kullanıyorum we aynı isimli dosyaları kopyala yapıştır derken bu dosyaları birleştirme işlemi yapıyor....yani klasörleri değiştirmiyor....şöle örnek verebilirim....pes 11 için extreme yamasını indirdim yamanın içindeki konami klasörünü benim belgelerimde konami klasörüyle deiştirmiyor ikisinide birleştiriyor...umarım açıklayıcı olmuştur..lütfen yardımlarını bekliyorum..iyi çalışmalar herkese Paylaş: |
H
14 yıl
|
öncelikle selamlar..benim internetten araştırıpta çözemediğim bi sorun için umarım bana yardımcı olabilirsiniz....win7 kullanıyorum we aynı isimli dosyaları kopyala yapıştır derken bu dosyaları birleştirme işlemi yapıyor....yani klasörleri değiştirmiyor....şöle örnek verebilirim....pes 11 için extreme yamasını indirdim yamanın içindeki konami klasörünü benim belgelerimde konami klasörüyle deiştirmiyor ikisinide birleştiriyor...umarım açıklayıcı olmuştur..lütfen yardımlarını bekliyorum..iyi çalışmalar herkese |
DH Mobil uygulaması ile devam edin.
Mobil tarayıcınız ile mümkün olanların yanı sıra, birçok yeni ve faydalı özelliğe erişin.
Gizle ve güncelleme çıkana kadar tekrar gösterme.