Премини към съдържанието

rudinoid

Потребител
  • Публикации

    145
  • Регистрация

  • Последно онлайн

Всичко публикувано от rudinoid

  1. След днешния ъпдейт се показват новини долу в стартовата страница. Как да ги изключа?
  2. rudinoid

    Дали цру ще позволи

    Позволявам!!!!
  3. От днес: На версия 7.4 при мен прави така
  4. Да бе ебати, оказа се, че Rudeboy е прав, а аз просто съм имал лош късмет щото 6 от 6 клипа бяха така, но сега като влязох и проверих с друг канал и клипове бе нормално. Мерси
  5. Така изглежда при мене. Трих бисквити, история и тн. и е все така
  6. Имате ли проблем youtube? При мен "прозореца" е по малък отднес...
  7. Аз го правя, както е написано тук и нямам проблеми със смени на подписите и тн. https://www.b-trust.org/web/files/richeditor/filemanager/MS_Outlook_2010_bg.pdf
  8. Откога не сте имали ъпдейт на Операта? При мен вече 3-4 месеца не идва такъв
  9. Много добра схема за чистене на фалшиви 50-ки
  10. След като за 4ти път направих тая "операция" незайно от къде се получи........ Отваря ми го с този адрес. Мерси на всички https://www.google.bg/?gfe_rd=cr&dcr=0&ei=7ae_WaOdBqjd8AfFsa-oCw&gws_rd Сега забелязах че преди да отвори гугле, около 10 сек. върти и ако искам да отворя нов тап отнови ми отваря страницата с тапета
  11. Не ми се получи при мен..? Или него правя както трябва
  12. Добре, как да направя стартовата страница да е гугъл? Това с google search engine го пробвах но не е същото като да ползвам гугъл. Просто не ми показва хубави резултати и предположения като го ползвам
  13. Здравейте, как да направя домашната ми страница да е google, а не показваната от опера с тапетите?
  14. rudinoid

    Какво колело да си избера !

    По принцип повечето хора дето продават от години се занимават само с това и разбират, а имат и правила. И също имат и рейтинг там по който да се ориентира. А в момента обаче няма велосипед като за него но отвреме на време има доста добри
  15. rudinoid

    Какво колело да си избера !

    Да и на цитирания форум виж секцията продавам, освен питането което ще пуснеш
  16. Благодаря. Това всъщност е стар лаптоп и може да мисля за купуване на нов най вероятно. Мерси
  17. Да операта я деинсталирах защото не можеше да се ползва. Логовете: Malwarebytes www.malwarebytes.com -Детайли за регистъра- Дата на сканиране: 27.02.17 г. Час на сканиране: 8:41 Регистърен файл: log.txt Администратор: Да -Информация за софтуера- Версия: 3.0.6.1469 Версия на компонентите: 1.0.50 Актуализирай версията на пакета: 1.0.1368 Лиценз: Изтекъл -Системна информация- OS: Windows 7 Service Pack 1 CPU: x86 Файлова система: NTFS Потребител: Ceci-PC\Ceci -Резюме на сканирането- Тип сканиране: Threat Scan Резултат: Завършено Сканирани обекти: 265537 Изтекло време: 6 мин, 24 сек -Опции за сканиране- Памет: Разрешено Стартиране: Разрешено Файлова система: Разрешено Архиви: Разрешено руткитове: Забранено Евристика: Разрешено PUP: Разрешено PUM: Разрешено -Детайли за сканирането- Процес: 0 (Не бяха открити зловредни елементи) Модул: 0 (Не бяха открити зловредни елементи) Ключ на регистъра: 0 (Не бяха открити зловредни елементи) Стойност на регистъра: 0 (Не бяха открити зловредни елементи) Данни на регистъра: 0 (Не бяха открити зловредни елементи) Поток данни: 0 (Не бяха открити зловредни елементи) Папка: 0 (Не бяха открити зловредни елементи) Файл: 0 (Не бяха открити зловредни елементи) Физически сектор: 0 (Не бяха открити зловредни елементи) (end) Лог от проверката на диска, която направих по 2- рия начин: TimeCreated : 27.2.2017 г. 09:53:46 ч. Message : Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 195072 file records processed. File verification completed. 350 large file records processed. 0 bad file records processed. 2 EA records processed. 31 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 237134 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 195072 file SDs/SIDs processed. Cleaning up 122 unused index entries from index $SII of file 0x9. Cleaning up 122 unused index entries from index $SDH of file 0x9. Cleaning up 122 unused security descriptors. Security descriptor verification completed. 21032 data files processed. CHKDSK is verifying Usn Journal... 34925576 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc0000185 at offset 0x2ea59f000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea59f000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a0000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a0000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a1000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a1000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a2000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a2000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a3000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a3000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a4000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a4000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a5000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a5000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a6000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a6000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a7000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a7000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a8000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a8000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a9000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5a9000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5aa000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5aa000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ab000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ab000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ac000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ac000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ad000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ad000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ae000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ae000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5af000 for 0x1 0000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5af000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b0000 for 0xf 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b0000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b1000 for 0xe 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b1000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b2000 for 0xd 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b2000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b3000 for 0xc 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b3000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b4000 for 0xb 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b4000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b5000 for 0xa 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b5000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b6000 for 0x9 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b6000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b7000 for 0x8 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b7000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b8000 for 0x7 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b8000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b9000 for 0x6 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5b9000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ba000 for 0x5 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5ba000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5bb000 for 0x4 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5bb000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5bc000 for 0x3 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5bc000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5bd000 for 0x2 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5bd000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5be000 for 0x1 000 bytes. Read failure with status 0xc0000185 at offset 0x2ea5be000 for 0x1 000 bytes. Windows replaced bad clusters in file 84405 of name \Users\Ceci\AppData\Roaming\OPERAS~1\OPERAS~1\PREFER~1. 195056 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 9855166 free clusters processed. Free space verification is complete. Adding 32 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 71681998 KB total disk space. 31893060 KB in 104397 files. 69032 KB in 21033 indexes. 128 KB in bad sectors. 299114 KB in use by the system. 65536 KB occupied by the log file. 39420664 KB available on disk. 4096 bytes in each allocation unit. 17920499 total allocation units on disk. 9855166 allocation units available on disk. Internal Info: 00 fa 02 00 01 ea 01 00 fb a8 03 00 00 00 00 00 ................ 7b 00 00 00 1f 00 00 00 00 00 00 00 00 00 00 00 {............... 70 8c 0d 00 50 01 0c 00 f8 18 0c 00 00 00 0c 00 p...P........... Windows has finished checking your disk. Please wait while your computer restarts. TimeCreated : 4.2.2017 г. 20:23:59 ч. Message : Checking file system on C: The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... The segment number 0xbf76 in file 0x1e8 is incorrect. Fixing incorrect information in file record segment 488. The segment number 0xbf77 in file 0x1e9 is incorrect. Fixing incorrect information in file record segment 489. The segment number 0xbf76 in file 0x1ea is incorrect. Fixing incorrect information in file record segment 490. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1ea is already in use. Deleting corrupt attribute record (128, "") from file record segment 490. The segment number 0xbf77 in file 0x1eb is incorrect. Fixing incorrect information in file record segment 491. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0x1eb is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 491. The segment number 0xbf76 in file 0xbe94 is incorrect. Fixing incorrect information in file record segment 48788. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xbe94 is already in use. Deleting corrupt attribute record (128, "") from file record segment 48788. The segment number 0xbf77 in file 0xbe95 is incorrect. Fixing incorrect information in file record segment 48789. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xbe95 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 48789. The segment number 0xbf76 in file 0xbe96 is incorrect. Fixing incorrect information in file record segment 48790. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xbe96 is already in use. Deleting corrupt attribute record (128, "") from file record segment 48790. The segment number 0xbf77 in file 0xbe97 is incorrect. Fixing incorrect information in file record segment 48791. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xbe97 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 48791. The segment number 0xbf76 in file 0xbf6c is incorrect. Fixing incorrect information in file record segment 49004. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xbf6c is already in use. Deleting corrupt attribute record (128, "") from file record segment 49004. The segment number 0xbf77 in file 0xbf6d is incorrect. Fixing incorrect information in file record segment 49005. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xbf6d is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 49005. The segment number 0xbf76 in file 0xbf6e is incorrect. Fixing incorrect information in file record segment 49006. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xbf6e is already in use. Deleting corrupt attribute record (128, "") from file record segment 49006. The segment number 0xbf77 in file 0xbf6f is incorrect. Fixing incorrect information in file record segment 49007. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xbf6f is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 49007. The segment number 0xbf76 in file 0xbf74 is incorrect. Fixing incorrect information in file record segment 49012. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xbf74 is already in use. Deleting corrupt attribute record (128, "") from file record segment 49012. The segment number 0xbf77 in file 0xbf75 is incorrect. Fixing incorrect information in file record segment 49013. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xbf75 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 49013. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xbf76 is already in use. Deleting corrupt attribute record (128, "") from file record segment 49014. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xbf77 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 49015. The segment number 0xbf76 in file 0x12784 is incorrect. Fixing incorrect information in file record segment 75652. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x12784 is already in use. Deleting corrupt attribute record (128, "") from file record segment 75652. The segment number 0xbf77 in file 0x12785 is incorrect. Fixing incorrect information in file record segment 75653. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0x12785 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 75653. The segment number 0xbf76 in file 0x12786 is incorrect. Fixing incorrect information in file record segment 75654. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x12786 is already in use. Deleting corrupt attribute record (128, "") from file record segment 75654. The segment number 0xbf77 in file 0x12787 is incorrect. Fixing incorrect information in file record segment 75655. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0x12787 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 75655. The segment number 0xbf76 in file 0x127b4 is incorrect. Fixing incorrect information in file record segment 75700. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x127b4 is already in use. Deleting corrupt attribute record (128, "") from file record segment 75700. The segment number 0xbf77 in file 0x127b5 is incorrect. Fixing incorrect information in file record segment 75701. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0x127b5 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 75701. The segment number 0xbf76 in file 0x127b6 is incorrect. Fixing incorrect information in file record segment 75702. Attribute record of type 0x80 and instance tag 0x3 is cross linke d starting at 0xa233 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x127b6 is already in use. Deleting corrupt attribute record (128, "") from file record segment 75702. The segment number 0xbf77 in file 0x127b7 is incorrect. Fixing incorrect information in file record segment 75703. Attribute record of type 0xa0 and instance tag 0x4 is cross linke d starting at 0x9457c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0x127b7 is already in use. Deleting corrupt attribute record (160, $I30) from file record segment 75703. 195072 file records processed. File verification completed. 348 large file records processed. 0 bad file records processed. 2 EA records processed. 31 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... The file reference 0x20000000001e9 of index entry Local of index $I30 with parent 0x1d6 is not the same as 0x230000000001e9. Deleting index entry Local in index $I30 of file 470. The file reference 0x20000000001e8 of index entry Media Center Pr ograms of index $I30 with parent 0x1d7 is not the same as 0x670000000001e8. Deleting index entry Media Center Programs in index $I30 of file 471. The file reference 0x20000000001e8 of index entry MEDIAC~1 of ind ex $I30 with parent 0x1d7 is not the same as 0x670000000001e8. Deleting index entry MEDIAC~1 in index $I30 of file 471. The file reference 0x3000000000bf6c of index entry Opera Software of index $I30 with parent 0x1d7 is not the same as 0x6700000000bf6c. Deleting index entry Opera Software in index $I30 of file 471. The file reference 0x3000000000bf6c of index entry OPERAS~1 of in dex $I30 with parent 0x1d7 is not the same as 0x6700000000bf6c. Deleting index entry OPERAS~1 in index $I30 of file 471. The parent 0x2300000000bf77 of index entry opera_installer_201512 05090333.log of index $I30 in file 0xbf7a is incorrect. The expected parent is 0x2300000000 01e9. Deleting index entry opera_installer_20151205090333.log in index $I30 of file 489. The parent 0x2300000000bf77 of index entry opera_installer_201512 05090334.log of index $I30 in file 0xbf84 is incorrect. The expected parent is 0x2300000000 01e9. Deleting index entry opera_installer_20151205090334.log in index $I30 of file 489. The parent 0x2300000000bf77 of index entry opera_installer_201512 05090337.log of index $I30 in file 0xbf85 is incorrect. The expected parent is 0x2300000000 01e9. Deleting index entry opera_installer_20151205090337.log in index $I30 of file 489. The parent 0x2300000000bf77 of index entry OPERA_~1.LOG of index $I30 in file 0xbf7a is incorrect. The expected parent is 0x2300000000 01e9. Deleting index entry OPERA_~1.LOG in index $I30 of file 489. The parent 0x2300000000bf77 of index entry OPERA_~2.LOG of index $I30 in file 0xbf84 is incorrect. The expected parent is 0x2300000000 01e9. Deleting index entry OPERA_~2.LOG in index $I30 of file 489. The parent 0x2300000000bf77 of index entry OPERA_~3.LOG of index $I30 in file 0xbf85 is incorrect. The expected parent is 0x2300000000 01e9. Deleting index entry OPERA_~3.LOG in index $I30 of file 489. The index bitmap for index $I30 in file 0x1eb is invalid or missi ng. Correcting error in index $I30 for file 491. The index bitmap $I30 is present but there is no corresponding index allocation attribute in file 0x1eb. Correcting error in index $I30 for file 491. The down pointer of current index entry with length 0x18 is inval id. 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................ ff ff ff ff ff ff ff ff 28 00 00 00 01 00 00 00 ........(....... 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................ Sorting index $I30 in file 491. The file reference 0x15e00000000bf6f of index entry f_003eb0 of i ndex $I30 with parent 0x4b5 is not the same as 0x2300000000bf6f. Deleting index entry f_003eb0 in index $I30 of file 1205. The file reference 0x5800000000be96 of index entry f_00467a of in dex $I30 with parent 0x4b5 is not the same as 0x6700000000be96. Deleting index entry f_00467a in index $I30 of file 1205. The file reference 0x18800000000bf75 of index entry f1 of index $ I30 with parent 0x8775 is not the same as 0x2300000000bf75. Deleting index entry f1 in index $I30 of file 34677. The file reference 0x3d000000012785 of index entry B912B2C6928A18 B8CD7D50CF08BEA95B_200D7CE383A0B4547950AE0DAC4EF2A4 of index $I30 with parent 0xba95 is not the same as 0x23000000012785. Deleting index entry B912B2C6928A18B8CD7D50CF08BEA95B_200D7CE383A 0B4547950AE0DAC4EF2A4 in index $I30 of file 47765. The file reference 0x3d000000012785 of index entry B960E2~1 of in dex $I30 with parent 0xba95 is not the same as 0x23000000012785. Deleting index entry B960E2~1 in index $I30 of file 47765. The file reference 0x6e0000000127b4 of index entry DCE3BDBF5BDD86 E2AB5B471CB90709B4_D5FE3430D858EEC0702EE96E01AD90B9 of index $I30 with parent 0xba97 is not the same as 0x670000000127b4. Deleting index entry DCE3BDBF5BDD86E2AB5B471CB90709B4_D5FE3430D85 8EEC0702EE96E01AD90B9 in index $I30 of file 47767. The file reference 0x6e0000000127b4 of index entry DCE972~1 of in dex $I30 with parent 0xba97 is not the same as 0x670000000127b4. Deleting index entry DCE972~1 in index $I30 of file 47767. The index bitmap for index $I30 in file 0xbe95 is invalid or miss ing. Correcting error in index $I30 for file 48789. The index bitmap $I30 is present but there is no corresponding index allocation attribute in file 0xbe95. Correcting error in index $I30 for file 48789. The down pointer of current index entry with length 0x18 is inval id. 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................ ff ff ff ff ff ff ff ff ef 86 86 ef d0 6a d0 01 .............j.. 26 eb 96 bd 8b 0b cf 01 5b 17 81 95 65 e2 d0 01 &.......[...e... Sorting index $I30 in file 48789. The index bitmap for index $I30 in file 0xbe97 is invalid or miss ing. Correcting error in index $I30 for file 48791. The index bitmap $I30 is present but there is no corresponding index allocation attribute in file 0xbe97. Correcting error in index $I30 for file 48791. The down pointer of current index entry with length 0x18 is inval id. 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................ ff ff ff ff ff ff ff ff ef 86 86 ef d0 6a d0 01 .............j.. 26 eb 96 bd 8b 0b cf 01 5b 17 81 95 65 e2 d0 01 &.......[...e... Sorting index $I30 in file 48791. The index bitmap for index $I30 in file 0xbf6d is invalid or miss ing. Correcting error in index $I30 for file 49005. The index bitmap $I30 is present but there is no corresponding index allocation attribute in file 0xbf6d. Correcting error in index $I30 for file 49005. The down pointer of current index entry with length 0x18 is inval id. 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................ ff ff ff ff ff ff ff ff ef 86 86 ef d0 6a d0 01 .............j.. 26 eb 96 bd 8b 0b cf 01 5b 17 81 95 65 e2 d0 01 &.......[...e... Sorting index $I30 in file 49005. The index bitmap for index $I30 in file 0xbf6f is invalid or miss ing. Correcting error in index $I30 for file 49007. The index bitmap $I30 is present but there is no corresponding index allocation attribute in file 0xbf6f. Correcting error in index TimeCreated : 12.6.2016 г. 09:08:17 ч. Message : Checking file system on C: The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... Cleaning up instance tags for file 0x100fb. 195072 file records processed. File verification completed. 344 large file records processed. 0 bad file records processed. 2 EA records processed. 31 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 235888 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... 195072 file SDs/SIDs processed. Cleaning up 885 unused index entries from index $SII of file 0x9. Cleaning up 885 unused index entries from index $SDH of file 0x9. Cleaning up 885 unused security descriptors. Security descriptor verification completed. 20409 data files processed. CHKDSK is verifying Usn Journal... 35132552 USN bytes processed. Usn Journal verification completed. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. CHKDSK discovered free space marked as allocated in the volume bi tmap. Windows has made corrections to the file system. 71681998 KB total disk space. 34129128 KB in 94064 files. 66104 KB in 20410 indexes. 0 KB in bad sectors. 299134 KB in use by the system. 65536 KB occupied by the log file. 37187632 KB available on disk. 4096 bytes in each allocation unit. 17920499 total allocation units on disk. 9296908 allocation units available on disk. Internal Info: 00 fa 02 00 35 bf 01 00 7e 5b 03 00 00 00 00 00 ....5...~[...... 58 00 00 00 1f 00 00 00 00 00 00 00 00 00 00 00 X............... 13 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.
  18. Имам проблем с вирус, при опит да отворя опера тя забива и се оправя само с рестарт на компютъра. Сканирах с Malwarebites откри вируси и ги изтри но проблема с и компютъра остана. Нямам антивирусна програма на компютъра между другото. Логове: Когато се опитам да copy paste лога излиза само този линк http://www.geekstogo.com/forum/topic/335081-frst-tutorial-how-to-use-farbar-recovery-scan-tool/ Addition.txt FRST.txt FRST (2).txt
  19. Знаех си че няма да ми отговoрите на въпроса You too
  20. Изсмукано от ваши постове през годините А сега някакъв "факт" по това "обвинение"? Приятен ден
  21. Е как, фактите съм ги написал още в горния пост. Модераторите сега са много по толерантни и тая тема го доказва. Преди щеше да бъде изтрита още след първия пост. Защото е трол тема. Както и мойте постове в нея и теми от последните дни на дръндю, momolord. За това се чудя и къде са старите модове. BTW: Приятен ден
  22. ХАхаааха знаех си, че това ще е реакцията но фактите са налице. Модераторите сега са много толерантни. Чак пък болен мозък Къде и фена Тотнъм и кокомил въобще влизат ли не знам
  23. От 2011 съм регистриран в тоя форум. Направете го тоя човек skalata_73 най после модератор и да се приключва. От години човека виждам напира, въпреки че естествено отрича като го питат . Ето и другия кандидат който не иска да бъде модератор НО видиш ли ако му се даде шанс............ Като стана дума можеби тия потребители незнаят но имаше модератори който не търпяха подобни тъпотии. BTW Къде е iovi?
  24. rudinoid

    Питане относно FIFA17

    Това са глупости. Лаптопа наистина не е за игри обаче тази ще върви на low с 60 фпс. Изпробвано от мен на същия процесор с вградената карта. Обаче дали си заслужава да я купуваш при това положение за мене не.
  • Разглеждащи това в момента   0 потребители

    Няма регистрирани потребители разглеждащи тази страница.

×
×
  • Добави ново...

Информация

Поставихме бисквитки на устройството ви за най-добро потребителско изживяване. Можете да промените настройките си за бисквитки, или в противен случай приемаме, че сте съгласни с нашите Условия за ползване