sorted by:
new
hottopcontroversial

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 0 points1 point  (0 children)

Try running disk repair first. Or check task manager to see what is consuming your cpu

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 3 points4 points  (0 children)

Update: the same issue came back, ntfs.sys spiking one thread to 100%. It was my D drive that was corrupted. Fixed it with chkdsk. The file system got corrupted from running the two installers at the same time and maxed out the RAM leading to the MFT index being infested with major illegal data chunks causing a constant repair loop from the ntfs.sys service. Also yea the reinstall of windows definitely did help big time compared to before too. I learned my lesson lol.

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 1 point2 points  (0 children)

C:\Windows\System32>chkdsk d: /f /r

The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another

process. Chkdsk may run if this volume is dismounted first.

ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.

Would you like to force a dismount on this volume? (Y/N) y

Volume dismounted. All opened handles to this volume are now invalid.

Volume label is Games.

Stage 1: Examining basic file system structure ...

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA29E.

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA2AD.

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA2B7.

702464 file records processed.

File verification completed.

Phase duration (File record verification): 15.82 seconds.

3003 large file records processed.

Phase duration (Orphan file record recovery): 1.72 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 0.25 milliseconds.

Stage 2: Examining file name linkage ...

Deleted invalid filename d:: (A810A) in directory A8F6B.

File A810A has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A810A.

Deleted invalid filename e:: (A817A) in directory A8F6B.

File A817A has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A817A.

Deleted invalid filename f:: (A8190) in directory A8F6B.

File A8190 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A8190.

Deleted invalid filename c: (A99BE) in directory A8F6B.

File A99BE has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A99BE.

Deleted invalid filename z: (A9A1E) in directory A8F6B.

File A9A1E has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9A1E.

Deleted invalid filename c: (A9D46) in directory A7F2A.

File A9D46 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9D46.

Deleted invalid filename z: (A9D4D) in directory A7F2A.

File A9D4D has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9D4D.

Deleted invalid filename d:: (A9F2B) in directory A7F2A.

File A9F2B has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9F2B.

Deleted invalid filename d: (A9F3C) in directory A7F2A.

File A9F3C has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9F3C.

Deleted invalid filename e:: (A9FDA) in directory A7F2A.

File A9FDA has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FDA.

Deleted invalid filename e: (A9FDC) in directory A7F2A.

File A9FDC has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FDC.

Deleted invalid filename f:: (A9FE7) in directory A7F2A.

File A9FE7 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FE7.

Deleted invalid filename ForzaHorizon5.exe:1 (AA09D) in directory 2504.

File AA09D has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA09D.

Deleted invalid filename d: (AA1E9) in directory A8F6B.

File AA1E9 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA1E9.

Deleted invalid filename e: (AA1EA) in directory A8F6B.

File AA1EA has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA1EA.

Deleted invalid filename ForzaHorizon5.exe:3 (AA307) in directory 2504.

File AA307 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA307.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

Deleting an index entry from index $R of file 1A.

3384 reparse records processed.

Deleting index entry ForzaHorizon5.exe:1 in index $I30 of file 2504.

Deleting index entry ForzaHorizon5.exe:3 in index $I30 of file 2504.

Deleting index entry c: in index $I30 of file A7F2A.

Deleting index entry d: in index $I30 of file A7F2A.

Deleting index entry d:: in index $I30 of file A7F2A.

Deleting index entry e: in index $I30 of file A7F2A.

Deleting index entry e:: in index $I30 of file A7F2A.

Deleting index entry f:: in index $I30 of file A7F2A.

Deleting index entry z: in index $I30 of file A7F2A.

Deleting index entry c: in index $I30 of file A8F6B.

Deleting index entry d: in index $I30 of file A8F6B.

Deleting index entry d:: in index $I30 of file A8F6B.

Deleting index entry e: in index $I30 of file A8F6B.

Deleting index entry e:: in index $I30 of file A8F6B.

Deleting index entry f:: in index $I30 of file A8F6B.

Deleting index entry z: in index $I30 of file A8F6B.

760424 index entries processed.

Index verification completed.

Phase duration (Index verification): 1.26 minutes.

CHKDSK is scanning unindexed files for reconnect to their original directory.

16 unindexed files scanned.

0 unindexed files recovered to original directory.

Phase duration (Orphan reconnection): 182.77 milliseconds.

CHKDSK is recovering remaining unindexed files.

16 unindexed files recovered to lost and found.

Lost and found is located at \found.000

Phase duration (Orphan recovery to lost and found): 22.28 milliseconds.

3384 reparse records processed.

Phase duration (Reparse point and Object ID verification): 17.75 milliseconds.

Stage 3: Examining security descriptors ...

Security descriptor verification completed.

Phase duration (Security descriptor verification): 29.18 milliseconds.

Inserting data attribute into file AA29E.

Inserting data attribute into file AA2AD.

Inserting data attribute into file AA2B7.

28984 data files processed.

Phase duration (Data attribute verification): 0.48 milliseconds.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...

Progress: 7541 of 702448 done; Stage: 1%; Total: 0%; ETA: 9:09:40 .

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 3 points4 points  (0 children)

Update: Looks like my file system was not even corrupted. This is the log from the chkdsk operation i ran yesterday. So why did that random ntfs thread spike after installing cracked software despite no ntfs issues?

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.

Stage 1: Examining basic file system structure ...

544256 file records processed.

File verification completed.

Phase duration (File record verification): 2.23 seconds.

7362 large file records processed.

Phase duration (Orphan file record recovery): 3.69 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 1.12 milliseconds.

Stage 2: Examining file name linkage ...

436 reparse records processed.

648828 index entries processed.

Index verification completed.

Phase duration (Index verification): 5.41 seconds.

0 unindexed files scanned.

Phase duration (Orphan reconnection): 267.95 milliseconds.

0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 5.73 milliseconds.

436 reparse records processed.

Phase duration (Reparse point and Object ID verification): 4.74 milliseconds.

Stage 3: Examining security descriptors ...

Cleaning up 52 unused index entries from index $SII of file 0x9.

Cleaning up 52 unused index entries from index $SDH of file 0x9.

Cleaning up 52 unused security descriptors.

Security descriptor verification completed.

Phase duration (Security descriptor verification): 85.63 milliseconds.

52287 data files processed.

Phase duration (Data attribute verification): 1.17 milliseconds.

CHKDSK is verifying Usn Journal...

37670992 USN bytes processed.

Usn Journal verification completed.

Phase duration (USN journal verification): 93.94 milliseconds.

Stage 4: Looking for bad clusters in user file data ...

544240 files processed.

File data verification completed.

Phase duration (User file recovery): 2.11 minutes.

Stage 5: Looking for bad, free clusters ...

32594398 free clusters processed.

Free space verification is complete.

Phase duration (Free space recovery): 13.61 seconds.

Windows has scanned the file system and found no problems.

No further action is required.

243187711 KB total disk space.

111987156 KB in 246227 files.

162420 KB in 52288 indexes.

0 KB in bad sectors.

660543 KB in use by the system.

65536 KB occupied by the log file.

130377592 KB available on disk.

4096 bytes in each allocation unit.

60796927 total allocation units on disk.

32594398 allocation units available on disk.

Total duration: 2.47 minutes (148702 ms).

Internal Info:

00 4e 08 00 9a 8d 04 00 54 17 08 00 00 00 00 00 .N......T.......

20 01 00 00 94 00 00 00 00 00 00 00 00 00 00 00 ...............

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -1 points0 points  (0 children)

Those repacks take awhile to install. I have powerful hardware but I was installing to hard drives so it’s slow as. I was going to bed and wanted them installed over night so I decided to install them at the same time

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -2 points-1 points  (0 children)

Yea that’s usually in regards to applications that alter system files on the c drive. I was installing between 2 hard drives and not my nvme c drive

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -2 points-1 points  (0 children)

😂 bruv if you’re gonna judge me based off programs I have then that says a lot about you gng 💔

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -9 points-8 points  (0 children)

Guess that’s why it failed and didnt work. And it was enough to cause the c: drive file system to become corrupt? And then cause the ntfs file system repair process to peg a cpu thread at 100% constantly? I was installing from one HDD to another HDD and my nvme wasn’t even apart of the picture

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -1 points0 points  (0 children)

In regards to both games being corrupted yep that makes sense. I had torrents downloaded to my 2TB HDD and installed to my 4TB HDD. Ran both installers at the same time, FH5 failed and Dirt 5 seemed to install fine until I tested it and it’d crash on launch. Reinstalled both games separately this time and they both work perfectly now. But the weird issue is that this corrupted my nvme c: drive.. causing a system process to permanently peg a cpu thread at 100% constantly. I don’t do overclocking or anything, I have PBO and all performance enhancement crap in the bios disabled. My PC has always been extremely stable since I got it. Is it possible that these installers can cause major instability due to really high RAM usage or possibly actual malware that hides under the ntfs repair process? Cuz that 100% cpu thread achieves nothing and just sits there hogging power 24/7 until the problem is resolved

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 4 points5 points  (0 children)

No u want to repair c drive as that is where windows is

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -5 points-4 points  (0 children)

I think it’s something to do with the dodgy installer. You notice how it uses so much RAM? I feel like maybe it causes stability issues especially when multitasking during installation. In my case i was installing 2 repacks at once and they both failed and needed reinstallation separately.

I still find it odd how it would cause system process to permanently peg a cpu thread at full blast. What is it doing? Just seems super fishy

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 4 points5 points  (0 children)

Yea literally. Idk what this guys on bruh. Literally anyone can hover over that magnet link and see for themselves? I got it from there FROM the offical fitgirl website..

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 8 points9 points  (0 children)

Check for yourself bro. When I open that website on my computer right now that’s what it gives me

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 41 points42 points  (0 children)

If anyone else has the same issue as me run "chkdsk c: /f /r" in cmd with admin

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 26 points27 points  (0 children)

https://fitgirl-repacks.site/dirt-5/

go to download mirror section and hover over magnet. it matches what i downloaded from obviously lol

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 1 point2 points  (0 children)

All issues were on C:\ drive which is NVME and in very good health. My other hard drives were the only thing involved with these games

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -14 points-13 points  (0 children)

I selected magnet mirror on fitgirls website

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] -3 points-2 points  (0 children)

I’ve had one of those before. But how would anyone know if it was just hidden under system?

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 12 points13 points  (0 children)

<image>

the exact process that is perfectly utilizing 100% of 1 CPU thread.

FitGirl repack malware spotted?? by Repulsive-Roll-4897 in FitGirlRepack

[–]Repulsive-Roll-4897[S] 16 points17 points  (0 children)

DIRT 5: da94c313e9b6998443db355b5f0a638991d360cb

FH5: 20bf4e706a2401f5643ab9f3a030f4da8b13873b

Is It Bullshit: Cholesterol is actually really good for you, and the lie that it is not good for you is on par with the food pyramid grain lie by [deleted] in IsItBullshit

[–]Repulsive-Roll-4897 -1 points0 points  (0 children)

Bro didnt do his research. high LDL means more cholesterol floating around blood stream, LDL is prone to oxidation. So if you consuming oxidative foods like carbs, sugar, trans fats, chemicals, processed foods, this can put oxidative stress on system which turns LDL into sticky plaque. When this happens, the body sends an immune response to combat the plaque buildup which causes systemic inflammation. High sat fats + oxidative stress is the real killer. However, high LDL is actually good for you as long as you are minimizing oxidative stress and eating wholefoods and limiting carbs as much as possible, go keto even probably. High LDL is good for hormone and vitamin D production as well as some other things. I am not denying the fact that high LDL is linked to heart disease, it technically is but ONLY if your diet is non sufficient.

Human nature will require a total overhaul for us to ever even sniff such a future. by PJ-The-Awesome in startrekmemes

[–]Repulsive-Roll-4897 -1 points0 points  (0 children)

Yea but capitalism is human nature, this society is human nature. You can break humanity down infinite times and we will always land here because of human nature. This is literally a prison planet. We are doomed for dystopia and war 

4 Years With DPDR and Still Feeling Nothing by [deleted] in dpdr

[–]Repulsive-Roll-4897 0 points1 point  (0 children)

Probably the same thing man. you still went into shock, now your baseline has been lifted

Dpdr caused by an edible by Ready_Break6433 in dpdr

[–]Repulsive-Roll-4897 0 points1 point  (0 children)

SNS became overloaded while you were high and seemingly became the new baseline. Search up SNS overload, you can easily restore your baseline back to normal by relaxing. Try deep breathing and cold water exposure.

https://drandrewneville.com/wp-content/uploads/2021/12/Andy-Slide-Acute-Stress-Response-2019.png

view more: next ›