Odvirování PC, zrychlení počítače, vzdálená pomoc prostřednictvím služby neslape.cz

soustavné poškozování dat na přenosném mediu

Moderátor: Moderátoři

Pravidla fóra
Jednotlivé thready budou po vyřešení uzamčeny. Stejně tak ty, které budou nečinné déle než 14 dní: http://forum.viry.cz/viewtopic.php?f=12&t=123975 . Děkujeme za pochopení.
Zpráva
Autor
jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#76 Příspěvek od jirkamm »

V TC951 v Rklik také není CRC.

Uživatelský avatar
JaRon
Moderátor
Moderátor
Příspěvky: 13797
Registrován: 29 bře 2005 13:39
Bydliště: BB-SK

Re: soustavné poškozování dat na přenosném mediu

#77 Příspěvek od JaRon »

JaRon píše:v TC nemas Files - Verify checksums :???:
FRST |ADWCleaner |MBAM |CCleaner |Avenger |AVPTool

V prípade spokojnosti je možné podporiť fórum
https://platba.viry.cz/payment/

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#78 Příspěvek od jirkamm »

Buď tam není nebo nevím jak se k němu dopracovat.
Přílohy
TC.png
TC.png (15.77 KiB) Zobrazeno 462 x

Uživatelský avatar
JaRon
Moderátor
Moderátor
Příspěvky: 13797
Registrován: 29 bře 2005 13:39
Bydliště: BB-SK

Re: soustavné poškozování dat na přenosném mediu

#79 Příspěvek od JaRon »

v total cmd v hornej liste by malo byt files a naspodu Verify chk
FRST |ADWCleaner |MBAM |CCleaner |Avenger |AVPTool

V prípade spokojnosti je možné podporiť fórum
https://platba.viry.cz/payment/

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#80 Příspěvek od jirkamm »

Já to furt hledal v Rklik.

Ano tam CRC je. Tak až narazím na poškozený soubor tak to hned vyzkouším.

Díky jirka

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#81 Příspěvek od jirkamm »

Ok. Našel jsem poškozený soubor .pdf
Tváří se, že je stejně velký ale nejde otevřít.

U poškozeného souboru je CRC:
; Generated by WIN-SFV32 v1.0
; (Compatible: Total Commander 6.55)
Voucher-19228994.pdf 4213074E

A u čitelného souboru je CRC:
; Generated by WIN-SFV32 v1.0
; (Compatible: Total Commander 6.55)
Voucher-19228994.pdf 33B791F8

Co se z toho dá vyčíst krom toho , že má jiný součet?

Takto to vypadá v TC při srovnání podle obsahu.

Díky jirka
Přílohy
CRC.jpg
CRC.jpg (242.25 KiB) Zobrazeno 448 x

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#82 Příspěvek od jirkamm »

Ahoj.

Jsem zpět.

Opět poškozená data. A opět se poškodili na PC dilna.

Některé soubory jsou nulové a to i soubory, které používám jen pro čtení. Před týdnem mi přišli poštou, já je uložil na disk a pak jen četl.
Některé soubory mají totožnou velikost jako okopírované v záloze. Záloha přečíst jde ale originál nepřečtu.

Opět poškozená databáze pošty.

Bože - co s tím. Už jsem z toho fakt na prášky.

Díky jirka

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#83 Příspěvek od jirkamm »

Jel jsem do dílny a našel toto:

Kód: Vybrat vše

Název protokolu:Application
Zdroj:         VSS
Datum:         04.05.2020 14:53:04
ID události:   8194
Kategorie úlohy:Není
Úroveň:        Chyba
Klíčová slova: Klasické nastavení
Uživatel:      Není k dispozici
Počítač:       CAMprace
Popis:
Chyba služby Stínová kopie svazků: Při dotazu na rozhraní IVssWriterCallback došlo k neočekávané chybě. hr = 0x80070005, Přístup byl odepřen.
. To je často způsobeno nesprávným nastavením zabezpečení v modulu pro zápis nebo žadateli. 

Operace:
   Shromažďování dat modulu pro zápis

Kontext:
   ID třídy modulu pro zápis: {e8132975-6f93-4464-a53e-1050253ae220}
   Název modulu pro zápis: System Writer
   ID instance modulu pro zápis: {018dc389-1078-4160-b17d-f05371cd7674}
Kód XML události:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8194</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-05-04T12:53:04.104031800Z" />
    <EventRecordID>16687</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CAMprace</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0x80070005, Přístup byl odepřen.
</Data>
    <Data>

Operace:
   Shromažďování dat modulu pro zápis

Kontext:
   ID třídy modulu pro zápis: {e8132975-6f93-4464-a53e-1050253ae220}
   Název modulu pro zápis: System Writer
   ID instance modulu pro zápis: {018dc389-1078-4160-b17d-f05371cd7674}</Data>
    <Binary>2D20436F64653A20575254575254494330303030313238372D2043616C6C3A20575254575254494330303030313234312D205049443A202030303030343335322D205449443A202030303030343835322D20434D443A2020433A5C57494E444F57535C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202D70202D732043727970745376632D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
  </EventData>
</Event>
a hned po ní:

Kód: Vybrat vše

Název protokolu:Application
Zdroj:         ESENT
Datum:         04.05.2020 14:56:52
ID události:   455
Kategorie úlohy:Protokolování a zotavení
Úroveň:        Chyba
Klíčová slova: Klasické nastavení
Uživatel:      Není k dispozici
Počítač:       CAMprace
Popis:
svchost (9636,R,98) TILEREPOSITORYS-1-5-18: Při otevírání souboru protokolu C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log došlo k chybě -1023 (0xfffffc01).
Kód XML události:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">455</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-05-04T12:56:52.003502900Z" />
    <EventRecordID>16689</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CAMprace</Computer>
    <Security />
  </System>
  <EventData>
    <Data>svchost</Data>
    <Data>9636,R,98</Data>
    <Data>TILEREPOSITORYS-1-5-18: </Data>
    <Data>C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log</Data>
    <Data>-1023 (0xfffffc01)</Data>
  </EventData>
</Event>
To je čas kdy jsem vypínal PC.
Poslední záznam před úplným vypnutím je ve 14:57:12.

Není chyba v tom?

Díky jirka

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#84 Příspěvek od jirkamm »

Další postřehy.

Navečer jsem při práci na PC doma vytvořil (nebo uložil) několik souborů (cca 15).
Několikrát jsem kontroloval jestli jestli uložené soubory nemají nulovou velikost.
Všechny byli v pořádku.
Cca 30min po posledním uložení (při surfování na netu) mi Cobian nahlásil, že nemůže zálohovat tři soubory. Jde o tři záložní soubory, které si můj sw vytváří jako automatickou zálohu. Za soubor přidá ".~10~" jako desátá záloha.
Opět jsem zkontroloval jestli nějaký soubor není nulový. Opět vše ok.
Tak jsem šel Rklik na disk/Vlastnosti/Nástroje/Kontrola chyb kde to hlásilo chybu.
Dal jsem opravit.
To se napoprvé nepodařilo. Psalo cosi, že to nejde ale uklikal jsem to. Oprava proběhla v pořádku.
V protokolech systému Windows/Aplikace naskákali chyby.
A některé soubory, které jsem vytvořil nebo uložil při práci najednou měli velikost nula.
Byli tam i soubory vytvořené dopoledne na PC dilna.
Evidentně se jim nelíbila oprava disku.
Na disku se vytvořili dva adresáře "found.000 a found.001" s atributem "hs", do kterých se ale nedostanu.

Netuším co si o tom mám myslet. Nejraději bych to vše zahodil a utekl.
Samozřejmě "pošta" je poškozená.
Ostatní soubory se mi podařilo obnovit ze zálohy, která proběhla 10min. před tím.

Zde je výpis událostí. Upravil jsem cesty k souborům. Kvůli GDPR.

Díky moc jirka

Kód: Vybrat vše

Úroveň	Datum a čas	Zdroj	ID události	Kategorie úlohy
Informace	06.05.2020 0:07:21	Chkdsk	26214	Není	"Chkdsk was executed in read/write mode.  

Checking file system on H:
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is Data.

Stage 1: Examining basic file system structure ...
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x583f3 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xecf1 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0xECF1.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x306ef7d for possibly 0x1f2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xedd6 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0xEDD6.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x322a74 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xede7 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0xEDE7.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x130a158 for possibly 0xe18 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10ba9 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10BA9.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x1616c46 for possibly 0x4c9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10bb2 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10BB2.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3198be9 for possibly 0x1d3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10bc3 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10BC3.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x322a6c for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10c31 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10C31.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6d1 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x10c71 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10C71.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x8195f0 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10d02 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D02.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3197548 for possibly 0x10e clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10d06 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D06.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1617140 for possibly 0xb clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x10d20 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D20.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3196fe5 for possibly 0x10c clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10d2d is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D2D.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x31970f4 for possibly 0x81 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10d34 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D34.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3197656 for possibly 0x10d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10d35 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D35.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3197175 for possibly 0x7d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10d36 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D36.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x322a78 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x10d3c is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10D3C.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x583f0 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x187e8 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x187E8.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x583f2 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1b7d6 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1B7D6.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x322451 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1fe92 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FE92.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x322452 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1fe95 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FE95.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x322453 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1fe98 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FE98.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x2f3e0d0 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1fea8 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEA8.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x2109394 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1feb8 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEB8.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x2109395 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1febb is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEBB.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b4 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1fee3 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEE3.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b5 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1fee6 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEE6.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b6 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1fee9 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEE9.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b7 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1feef is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEEF.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6bc for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1fef2 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEF2.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6bd for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1fef3 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEF3.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6be for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1fef6 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEF6.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x30fe42d for possibly 0xaf clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1fef8 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEF8.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x308b6bf for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x1fefb is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEFB.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6d0 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1fefe is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FEFE.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x2f3e0e0 for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1ff09 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x1FF09.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6c4 for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2002c is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x2002C.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6cb for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x20162 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20162.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x31f8af8 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x2016f is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x2016F.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8af9 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x20172 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20172.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x31f8afa for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x20175 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20175.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8afb for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x20178 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20178.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x31f8b00 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x2017b is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x2017B.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8b01 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2017e is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x2017E.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x31f8b02 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0x20181 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20181.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8b03 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x20184 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20184.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x325ad78 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0x20187 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20187.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x325ad79 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2018a is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x2018A.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x325ad7a for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0x20190 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20190.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x325ad7b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x20195 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x20195.
  135680 file records processed.                                                        

File verification completed.
  6 large file records processed.                                   

  0 bad file records processed.                                     


Stage 2: Examining file name linkage ...
Multiple object id index entries in file 0x19
point to the same file 0x10cfb.
Deleting an index entry from index $O of file 19.
Multiple object id index entries in file 0x19
point to the same file 0x10d06.
Deleting an index entry from index $O of file 19.
The object id in index entry in file 0x19 is incorrect.
The entry points to file 0x10cfb.
57 d6 97 36 a1 8e ea 11 90 24 4c cc 6a b7 95 50  W֗6¡Žê.$L.j·•P
----------------------------------------------------------------------
51 78 50 d4 2b 8e ea 11 93 0e d8 cb 8a 1d 82 0d  QxPÔ+Žê.“.Ø.Š.‚.
Deleting an index entry from index $O of file 19.
The object id in index entry in file 0x19 is incorrect.
The entry points to file 0x10d06.
5e d9 97 36 a1 8e ea 11 90 24 4c cc 6a b7 95 50  ^.—6¡Žê.$L.j·•P
----------------------------------------------------------------------
c1 78 50 d4 2b 8e ea 11 93 0e d8 cb 8a 1d 82 0d  .xPÔ+Žê.“.Ø."
Informace	06.05.2020 0:07:01	Windows Error Reporting	1001	Není	"Chybný blok 1976341822256079947, typ 5
Název události: RADAR_PRE_LEAK_64
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: dllhost.exe
P2: 10.0.18362.1
P3: 10.0.18363.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Připojené soubory:
\\?\C:\Users\model\AppData\Local\Temp\RDRE227.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE228.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE248.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE256.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE276.tmp.txt

Tyto soubory mohou být k dispozici zde:


Symbol analýzy: 
Opětovné hledání řešení: 0
ID hlášení: fed71a26-bfbc-41b1-9b17-dc22ba2fe8b5
Stav hlášení: 268435456
Zakódovaný interval: db14cf413a7e99c8bb6d606a8e52644b
GUID souboru CAB: 0"
Informace	06.05.2020 0:07:00	Chkdsk	26226	Není	"Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on H:
Volume label is Data.

Stage 1: Examining basic file system structure ...
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x583f3 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\Záloha_material.cdr <0x6a,0xecf1>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x306ef7d for possibly 0x1f2 clusters.
    Found corrupt basic file structure for ""\__history\19_046_4mm a.stc.~9~ <0x136,0xedd6>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x322a74 for possibly 0x4 clusters.
    Found corrupt basic file structure for ""\Záloha_material.cdr <0x1b,0xede7>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x130a158 for possibly 0xe18 clusters.
    Found corrupt basic file structure for ""\__history\19_046_6mm a.stc.~10~ <0x8,0x10ba9>""
        ... queued for offline repair.
    Found 0x6 clusters allocated to file ""\__history\19_046_6mm a.stc.~12~ <0x7,0x10baa>"" at offset ""0x4e3"" marked as free
        ... repaired online.
    Found 0x3 clusters allocated to file ""\__history\19_046_6mm a.stc.~12~ <0x7,0x10baa>"" at offset ""0x4f6"" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file ""\__history\19_046_6mm a.stc.~12~ <0x7,0x10baa>"" at offset ""0x505"" marked as free
        ... repaired online.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x1616c46 for possibly 0x4c9 clusters.
    Found corrupt basic file structure for ""\__history\19_046_6mm b.stc.~7~ <0x9,0x10bb2>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3198be9 for possibly 0x1d3 clusters.
    Found corrupt basic file structure for ""\__history\19_046_4mm a.stc.~7~ <0x8,0x10bc3>""
        ... queued for offline repair.
    Found 0x21a clusters allocated to file ""\__history\19_046_4mm a.stc.~10~ <0x6,0x10bdf>"" at offset ""0"" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file ""\19_046_5mm FR4 a.stc <0x7,0x10c1a>"" at offset ""0"" marked as free
        ... repaired online.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x322a6c for possibly 0x4 clusters.
    Found corrupt basic file structure for ""\19_046_5mm a 01.dxf <0xa,0x10c31>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6d1 for possibly 0x3 clusters.
    Found corrupt basic file structure for ""\posta\Logs\WM Tracing 2020-05-05_09-26-07.log <0x4,0x10c71>""
        ... queued for offline repair.
    Found 0x469 clusters allocated to file ""\zaloha\zaloha rucni kopie dat\__history\19_046_6mm b.stc.~2~ <0x3,0x10c84>"" at offset ""0"" marked as free
        ... repaired online.
    Found 0x4c1 clusters allocated to file ""\zaloha\zaloha rucni kopie dat\__history\19_046_6mm b.stc.~3~ <0x3,0x10c85>"" at offset ""0"" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file ""\posta\Logs\WM Tracing 2020-05-05_09-26-07.log <0x3,0x10cf8>"" at offset ""0"" marked as free
        ... repaired online.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x8195f0 for possibly 0x3 clusters.
    Found corrupt basic file structure for ""<0x5,0x10d02>""
        ... repaired online.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3197548 for possibly 0x10e clusters.
    Found corrupt basic file structure for ""\dcam\pracovni\leos\ramecky\19_046\19_046_R07\19_046_pripravek.stc <0x7,0x10d06>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1617140 for possibly 0xb clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\cislice\02 b.png <0x6,0x10d20>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3196fe5 for possibly 0x10c clusters.
    Found corrupt basic file structure for ""\__history\19_046_D401 pripravek.stc.~3~ <0x4,0x10d2d>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x31970f4 for possibly 0x81 clusters.
    Found corrupt basic file structure for ""\19_046_D401 pripravek.stc <0x4,0x10d34>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3197656 for possibly 0x10d clusters.
    Found corrupt basic file structure for ""\__history\19_046_D429 pripravek.stc.~1~ <0x5,0x10d35>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3197175 for possibly 0x7d clusters.
    Found corrupt basic file structure for ""\19_046_D429 pripravek.stc <0x4,0x10d36>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x322a78 for possibly 0x2 clusters.
    Found corrupt basic file structure for ""\19_046_R07 sverak.dxf <0x7,0x10d3c>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x583f0 for possibly 0x2 clusters.
    Found corrupt basic file structure for ""\NC Programy\frezovani\01.ngc <0x1,0x187e8>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x583f2 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\material.cdr <0x2,0x1b7d6>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x322451 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\16d88c22-8bc8-479e-a211-3ac33772ab3b\88c51ea1-7ca3-43cf-b42c-95978b18decf\attachments.dat-wal <0x1,0x1fe92>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x322452 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\16d88c22-8bc8-479e-a211-3ac33772ab3b\88c51ea1-7ca3-43cf-b42c-95978b18decf\contact_data.dat-wal <0x1,0x1fe95>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x322453 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\16d88c22-8bc8-479e-a211-3ac33772ab3b\88c51ea1-7ca3-43cf-b42c-95978b18decf\contact_index.dat-wal <0x1,0x1fe98>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x2f3e0d0 for possibly 0x10 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\16d88c22-8bc8-479e-a211-3ac33772ab3b\8b857339-da12-40c1-944d-a47fa64b650f\contact_data.dat-wal <0x1,0x1fea8>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x2109394 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\43e18b06-24bb-4e0f-8b5c-b75521332def\event_index.dat-wal <0x1,0x1feb8>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x2109395 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\43e18b06-24bb-4e0f-8b5c-b75521332def\folders.dat-wal <0x1,0x1febb>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b4 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Archive\mail_index.dat-wal <0x1,0x1fee3>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b5 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\categories.dat-wal <0x1,0x1fee6>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b6 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\certificates.dat-wal <0x1,0x1fee9>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6b7 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\attachments.dat-wal <0x1,0x1feef>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6bc for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\contact_data.dat-wal <0x1,0x1fef2>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6bd for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\contact_index.dat <0x1,0x1fef3>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6be for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\conversations.dat <0x1,0x1fef6>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x30fe42d for possibly 0xaf clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\conversations.dat-wal <0x1,0x1fef8>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x308b6bf for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\event_data.dat-wal <0x1,0x1fefb>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6d0 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\event_index.dat-wal <0x1,0x1fefe>""
        ... queued for offline repair.
    Found 0x302 clusters allocated to file ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\mail_data.dat <0x1,0x1ff02>"" at offset ""0xfa2a0"" marked as free
        ... repaired online.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x2f3e0e0 for possibly 0x8 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Local Folders\mail_index.dat <0x1,0x1ff09>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x308b6c4 for possibly 0x7 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Logs\sqlite.log <0x1,0x2002c>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x308b6cb for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\rules.dat-wal <0x1,0x20162>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x31f8af8 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\conversations.dat-wal <0x1,0x2016f>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8af9 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\event_data.dat-wal <0x1,0x20172>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x31f8afa for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\event_index.dat-wal <0x1,0x20175>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8afb for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\folders.dat-wal <0x1,0x20178>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x31f8b00 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\mail_data.dat-wal <0x1,0x2017b>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8b01 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\mail_fti.dat-wal <0x1,0x2017e>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x31f8b02 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\mail_index.dat-wal <0x1,0x20181>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x31f8b03 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\task_data.dat-wal <0x1,0x20184>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x325ad78 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\task_index.dat-wal <0x1,0x20187>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x325ad79 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\Search Folders\timezones.dat-wal <0x1,0x2018a>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x325ad7a for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\snippets.dat-wal <0x1,0x20190>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x325ad7b for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\posta\templates.dat-wal <0x1,0x20195>""
        ... queued for offline repair.
    Found 0x1 clusters allocated to file ""\zaloha\zaloha rucni kopie dat\posta\widgets.dat <0x1,0x20196>"" at offset ""0"" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file ""\z"
Informace	06.05.2020 0:06:43	Chkdsk	26227	Není	"Chkdsk was executed in spotfix mode on a read-write volume.  

Checking file system on H:
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is Data.

Examining 5 corruption records ...

Record 1 of 5: Corrupt File ""\zaloha\zaloha rucni kopie dat\Záloha_material.cdr <0x6a,0xecf1>"" ... no corruption found.

Record 2 of 5: Corrupt File ""\__history\19_046_4mm a.stc.~9~ <0x136,0xedd6>"" ... no corruption found.

Record 3 of 5: Corrupt File ""\Záloha_material.cdr <0x1b,0xede7>"" ... no corruption found.

Record 4 of 5: Corrupt File ""\__history\19_046_6mm a.stc.~10~ <0x8,0x10ba9>"" ... no corruption found.

Record 5 of 5: 1 clusters allocated to file ""\__history\19_046_6mm a.stc.~12~ <0x7,0x10baa>"" at offset ""0x4d8000"" are marked as free ... corruption found and fixed.

5 corruption records processed in 0.1 seconds.

Windows has fixed all previously identified issues with this drive.
No further action is required.
"
Informace	06.05.2020 0:05:32	Chkdsk	26226	Není	"Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on H:
Volume label is Data.

Stage 1: Examining basic file system structure ...
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x583f3 for possibly 0x1 clusters.
    Found corrupt basic file structure for ""\zaloha\zaloha rucni kopie dat\Záloha_material.cdr <0x6a,0xecf1>""
        ... queued for offline repair.
    Found 0x3 clusters allocated to file ""\19_046_4mm a.stc <0x9,0xedca>"" at offset ""0x10c"" marked as free
        ... repaired online.
    Found 0xd clusters allocated to file ""\19_046_4mm a.stc <0x9,0xedca>"" at offset ""0x20d"" marked as free
        ... repaired online.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x306ef7d for possibly 0x1f2 clusters.
    Found corrupt basic file structure for ""\__history\19_046_4mm a.stc.~9~ <0x136,0xedd6>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x322a74 for possibly 0x4 clusters.
    Found corrupt basic file structure for ""\Záloha_material.cdr <0x1b,0xede7>""
        ... queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x130a158 for possibly 0xe18 clusters.
    Found corrupt basic file structure for ""\__history\19_046_6mm a.stc.~10~ <0x8,0x10ba9>""
        ... queued for offline repair.
    Found 0x1 clusters allocated to file ""\__history\19_046_6mm a.stc.~12~ <0x7,0x10baa>"" at offset ""0x4d8"" marked as free
""Chkdsk /scan"" is restarting due to stale information about crosslinks.

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xecf1 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0xECF1.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xedd6 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0xEDD6.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0xede7 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0xEDE7.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x10ba9 is already in use.
Deleting corrupt attribute record (0x80, """")
from file record segment 0x10BA9.
""Chkdsk /scan"" is restarting due to stale information about crosslinks.
An unspecified error occurred (6672737374727563 56c).
"
Informace	06.05.2020 0:03:33	Chkdsk	26228	Není	"Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume6
Volume label is Data.

Examining 1 corruption record ...

Record 1 of 1: Corrupt File ""<0x9,0x10ba9>"" ... no corruption found.

1 corruption record processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
"
Informace	05.05.2020 23:44:21	Microsoft-Windows-Security-SPP	16384	Není	Restartování služby Ochrana softwaru bylo úspěšně naplánováno na 2120-04-11T21:44:21Z. Důvod: RulesEngine
Chyba	05.05.2020 23:44:03	VSS	8194	Není	"Chyba služby Stínová kopie svazků: Při dotazu na rozhraní IVssWriterCallback došlo k neočekávané chybě. hr = 0x80070005, Přístup byl odepřen.
. To je často způsobeno nesprávným nastavením zabezpečení v modulu pro zápis nebo žadateli. 

Operace:
   Shromažďování dat modulu pro zápis

Kontext:
   ID třídy modulu pro zápis: {e8132975-6f93-4464-a53e-1050253ae220}
   Název modulu pro zápis: System Writer
   ID instance modulu pro zápis: {069e0eb8-b97d-4204-b050-00b86ce507c4}"

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#85 Příspěvek od jirkamm »

A pokračování.
Dnes mi to poškodilo cca 450 různých souborů z různého období.
Nic moc.

jirkamm
Návštěvník
Návštěvník
Příspěvky: 223
Registrován: 07 led 2012 01:04
Bydliště: Pardubice
Kontaktovat uživatele:

Re: soustavné poškozování dat na přenosném mediu

#86 Příspěvek od jirkamm »

:oops: :oops: :oops:
U obou PC jsem měl nastavené "Rychlé spuštění".
Což si myslím, že vysvětluje mnohé.
Ani jsem netušil, že tam taková nějaká volba je.
Škoda - 2 roky (trápení) v háji.
Jestli je to skutečně příčina mých potíží tak už nevím. Asi je čas na důchod.
:oops: :oops: :oops:

Odpovědět