Jump to content

Beryl

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Beryl

  1. I won't be able to run that anytime soon, because I'd need an external cd drive. This laptop as a whole is fairly well-used, though, so I would not be surprised if it's getting worn out. I just wanted to be make sure that there isn't anything malware related. Is there anything on the malware scans that I should clean out? I only ran the scans but I didn't take action with them. Thank you so much for you help! I really appreciate it.
  2. Yeah, I had wondered if it was something damaged. The chkdsk finished running, so these were the results: Thanks! Log Name: Application Source: Microsoft-Windows-Wininit Date: 3/1/2017 5:10:37 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Soundwave Description: 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 ... 436736 file records processed. File verification completed. 8766 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 555694 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. Stage 3: Examining security descriptors ... Cleaning up 678 unused index entries from index $SII of file 0x9. Cleaning up 678 unused index entries from index $SDH of file 0x9. Cleaning up 678 unused security descriptors. Security descriptor verification completed. 59480 data files processed. CHKDSK is verifying Usn Journal... 39325024 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... Read failure with status 0xc000009c at offset 0x187677c000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876780000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876781000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876781000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876782000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876782000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876783000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876783000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876784000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876784000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876785000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876785000 for 0x1000 bytes. Windows replaced bad clusters in file 22706 of name \PROGRA~2\CYBERL~1\LABELP~1\Language\Kor\LPRes.dll. Read failure with status 0xc000009c at offset 0x18766d1000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x18766dc000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766dd000 for 0xc000 bytes. Read failure with status 0xc000009c at offset 0x18766dd000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766de000 for 0xb000 bytes. Read failure with status 0xc000009c at offset 0x18766de000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766df000 for 0xa000 bytes. Read failure with status 0xc000009c at offset 0x18766df000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e0000 for 0x9000 bytes. Read failure with status 0xc000009c at offset 0x18766e0000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e1000 for 0x8000 bytes. Read failure with status 0xc000009c at offset 0x18766e1000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e2000 for 0x7000 bytes. Read failure with status 0xc000009c at offset 0x18766e4000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e5000 for 0x4000 bytes. Read failure with status 0xc000009c at offset 0x18766e5000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e6000 for 0x3000 bytes. Read failure with status 0xc000009c at offset 0x18766e6000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e7000 for 0x2000 bytes. Read failure with status 0xc000009c at offset 0x18766e7000 for 0x1000 bytes. Windows replaced bad clusters in file 281577 of name \PROGRA~2\WEBZEN\C9\CHARAC~1\chr_npc\GAJDET~1\N10000~1\N10000~1.CFS. 436720 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 55642219 free clusters processed. Free space verification is complete. Adding 16 bad clusters to the Bad Clusters File. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. No further action is required. 459987967 KB total disk space. 236696772 KB in 292692 files. 202920 KB in 59481 indexes. 64 KB in bad sectors. 519335 KB in use by the system. 65536 KB occupied by the log file. 222568876 KB available on disk. 4096 bytes in each allocation unit. 114996991 total allocation units on disk. 55642219 allocation units available on disk. Internal Info: 00 aa 06 00 b8 5f 05 00 d1 aa 09 00 00 00 00 00 ....._.......... 9b 03 00 00 36 00 00 00 00 00 00 00 00 00 00 00 ....6........... Windows has finished checking your disk. Please wait while your computer restarts. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-03-01T22:10:37.000000000Z" /> <EventRecordID>316551</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Soundwave</Computer> <Security /> </System> <EventData> <Data> 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 ... 436736 file records processed. File verification completed. 8766 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 555694 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. Stage 3: Examining security descriptors ... Cleaning up 678 unused index entries from index $SII of file 0x9. Cleaning up 678 unused index entries from index $SDH of file 0x9. Cleaning up 678 unused security descriptors. Security descriptor verification completed. 59480 data files processed. CHKDSK is verifying Usn Journal... 39325024 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... Read failure with status 0xc000009c at offset 0x187677c000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876780000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876781000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876781000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876782000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876782000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876783000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876783000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876784000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876784000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x1876785000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x1876785000 for 0x1000 bytes. Windows replaced bad clusters in file 22706 of name \PROGRA~2\CYBERL~1\LABELP~1\Language\Kor\LPRes.dll. Read failure with status 0xc000009c at offset 0x18766d1000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0x18766dc000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766dd000 for 0xc000 bytes. Read failure with status 0xc000009c at offset 0x18766dd000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766de000 for 0xb000 bytes. Read failure with status 0xc000009c at offset 0x18766de000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766df000 for 0xa000 bytes. Read failure with status 0xc000009c at offset 0x18766df000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e0000 for 0x9000 bytes. Read failure with status 0xc000009c at offset 0x18766e0000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e1000 for 0x8000 bytes. Read failure with status 0xc000009c at offset 0x18766e1000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e2000 for 0x7000 bytes. Read failure with status 0xc000009c at offset 0x18766e4000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e5000 for 0x4000 bytes. Read failure with status 0xc000009c at offset 0x18766e5000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e6000 for 0x3000 bytes. Read failure with status 0xc000009c at offset 0x18766e6000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0x18766e7000 for 0x2000 bytes. Read failure with status 0xc000009c at offset 0x18766e7000 for 0x1000 bytes. Windows replaced bad clusters in file 281577 of name \PROGRA~2\WEBZEN\C9\CHARAC~1\chr_npc\GAJDET~1\N10000~1\N10000~1.CFS. 436720 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 55642219 free clusters processed. Free space verification is complete. Adding 16 bad clusters to the Bad Clusters File. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. No further action is required. 459987967 KB total disk space. 236696772 KB in 292692 files. 202920 KB in 59481 indexes. 64 KB in bad sectors. 519335 KB in use by the system. 65536 KB occupied by the log file. 222568876 KB available on disk. 4096 bytes in each allocation unit. 114996991 total allocation units on disk. 55642219 allocation units available on disk. Internal Info: 00 aa 06 00 b8 5f 05 00 d1 aa 09 00 00 00 00 00 ....._.......... 9b 03 00 00 36 00 00 00 00 00 00 00 00 00 00 00 ....6........... Windows has finished checking your disk. Please wait while your computer restarts. </Data> </EventData> </Event>
  3. Hi kevin! Thanks so much for responding. I actually no longer have Chrome on my computer, only Firefox and IE (which I haven't used in a couple years now). Here are my FRST logs: FRST_01-03-2017 12.11.34.txt Addition_01-03-2017 12.11.34.txt
  4. I'm not actually certain if I'm infected. I do know that I haven't been able to successfully run either a full system or quick scan with my usual antivirus (Avira) in awhile. Malwarebytes works just fine, but it hasn't detected anything recently. The most troublesome thing with my laptop is the way it freezes up, and I'm forced to hard reboot. I thought it might be a hardware issue, but two days ago I was booted into a temporary user profile. I ended up having to repair a couple corrupted files, then tried to follow up with Microsoft Safety Scanner. The first time I ran this scan, it detected at least 1 problem, but five hours into the scan it suddenly stopped progressing, so I cancelled. After I regained access to my original user profile, I tried to run it a second time. It froze up the same way Avira does whenever I attempt to run a scan. I decided to try adwCleaner to see if maybe it would find anything. I didn't have any problems running it, but it detected more than I expected it to. I'm hesitant to just start tossing things into quarantine without making sure that I'm not accidentally including something that is important. I'd also like to know if there's something else I should do afterwards. Help would be very much appreciated! AdwCleaner[S1].txt
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.