PC Lagging and jumping CPU Usage after a Format.

Okay, Here is the dckchk log, It's in Polish though, but I think the data is readable anyway.

Nazwa dziennika:Application
Źródło:        Microsoft-Windows-Wininit
Data:          2019-01-28 11:17:30
Identyfikator zdarzenia:1001
Kategoria zadania:Brak
Poziom:        Informacje
Słowa kluczowe:Klasyczny
Użytkownik:    Nie dotyczy
Komputer:      Brzegomputer
Opis:


Sprawdzanie systemu plików na C:
Typ systemu plików to NTFS.

Zaplanowano sprawdzenie dysku.
System Windows sprawdzi teraz dysk.                         

CHKDSK sprawdza pliki (poziom 1 z 5)
  Przetworzone rekordy plików: 200704.                                   

Ukonczono sprawdzanie plików.
  Przetworzone rekordy duzych plików: 413.                            

  Przetworzone rekordy uszkodzonych plików: 0.                      

  Przetworzone rekordy atrybutów rozszerzonych: 0.                  

  Przetworzone rekordy ponownej analizy: 73.                         

CHKDSK sprawdza indeksy (poziom 2 z 5)
  Przetworzone wpisy indeksu: 252898.                                    

Ukonczono weryfikacje indeksów.
  Przeskanowane pliki nieindeksowane: 0.                            

  Odzyskane pliki nieindeksowane: 0.                                

CHKDSK sprawdza deskryptory zabezpieczen (poziom 3 z 5)
  Przetworzone deskryptory zabezpieczen/identyfikatory plików: 200704.   

Oczyszczanie 422 nieuzywanych wpisów w indeksie $SII pliku 0x9.
Oczyszczanie 422 nieuzywanych wpisów w indeksie $SDH pliku 0x9.
Porzadkowanie 422 nieuzywanych deskryptorów zabezpieczen.
Ukonczono sprawdzanie deskryptorów zabezpieczen.
  Przetworzone pliki danych: 26098.                                     

Trwa sprawdzanie dziennika Usn...
  Przetworzone bajty numerów USN: 36590136.                                

Zakonczono sprawdzanie poprawnosci dziennika Usn.
CHKDSK sprawdza dane pliku (poziom 4 z 5)
  Przetworzone pliki: 200688.                                            

Zakonczono sprawdzanie danych pliku.
CHKDSK sprawdza wolne miejsce (etap 5 z 5)
  Przetworzone wolne klastry: 9992689.                                        

Zakonczono sprawdzanie wolnego miejsca na dysku.
CHKDSK wykryl wolne miejsce oznaczone jako przydzielone w
mapie bitowej glównej tabeli plików (MFT).
CHKDSK wykryl wolne miejsce oznaczone jako przydzielone w mapie bitowej woluminu.
System Windows wprowadzil poprawki do systemu plików.

  75673599 KB calkowitego miejsca na dysku.
  35275680 KB w 170318 plikach.
    121056 KB w 26099 indeksach.
         0 KB w uszkodzonych sektorach.
    306103 KB uzywanych przez system.
     65536 KB zajetych przez plik dziennika.
  39970760 KB dostepnych na dysku.

      4096 bajtów w kazdej jednostce alokacji.
  18918399 ogólem jednostek alokacji na dysku.
   9992690 jednostek alokacji dostepnych na dysku.

Informacje wewnetrzne:
00 10 03 00 4d ff 02 00 d3 f1 05 00 00 00 00 00  ....M...........
3f 00 00 00 49 00 00 00 00 00 00 00 00 00 00 00  ?...I...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

System Windows zakonczyl sprawdzanie dysku.
Zaczekaj na ponowne uruchomienie systemu.

Kod XML zdarzenia:
<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="2019-01-28T10:17:30.000000000Z" />
    <EventRecordID>1404</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Brzegomputer</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Sprawdzanie systemu plików na C:
Typ systemu plików to NTFS.

Zaplanowano sprawdzenie dysku.
System Windows sprawdzi teraz dysk.                         

CHKDSK sprawdza pliki (poziom 1 z 5)
  Przetworzone rekordy plików: 200704.                                   

Ukonczono sprawdzanie plików.
  Przetworzone rekordy duzych plików: 413.                            

  Przetworzone rekordy uszkodzonych plików: 0.                      

  Przetworzone rekordy atrybutów rozszerzonych: 0.                  

  Przetworzone rekordy ponownej analizy: 73.                         

CHKDSK sprawdza indeksy (poziom 2 z 5)
  Przetworzone wpisy indeksu: 252898.                                    

Ukonczono weryfikacje indeksów.
  Przeskanowane pliki nieindeksowane: 0.                            

  Odzyskane pliki nieindeksowane: 0.                                

CHKDSK sprawdza deskryptory zabezpieczen (poziom 3 z 5)
  Przetworzone deskryptory zabezpieczen/identyfikatory plików: 200704.   

Oczyszczanie 422 nieuzywanych wpisów w indeksie $SII pliku 0x9.
Oczyszczanie 422 nieuzywanych wpisów w indeksie $SDH pliku 0x9.
Porzadkowanie 422 nieuzywanych deskryptorów zabezpieczen.
Ukonczono sprawdzanie deskryptorów zabezpieczen.
  Przetworzone pliki danych: 26098.                                     

Trwa sprawdzanie dziennika Usn...
  Przetworzone bajty numerów USN: 36590136.                                

Zakonczono sprawdzanie poprawnosci dziennika Usn.
CHKDSK sprawdza dane pliku (poziom 4 z 5)
  Przetworzone pliki: 200688.                                            

Zakonczono sprawdzanie danych pliku.
CHKDSK sprawdza wolne miejsce (etap 5 z 5)
  Przetworzone wolne klastry: 9992689.                                        

Zakonczono sprawdzanie wolnego miejsca na dysku.
CHKDSK wykryl wolne miejsce oznaczone jako przydzielone w
mapie bitowej glównej tabeli plików (MFT).
CHKDSK wykryl wolne miejsce oznaczone jako przydzielone w mapie bitowej woluminu.
System Windows wprowadzil poprawki do systemu plików.

  75673599 KB calkowitego miejsca na dysku.
  35275680 KB w 170318 plikach.
    121056 KB w 26099 indeksach.
         0 KB w uszkodzonych sektorach.
    306103 KB uzywanych przez system.
     65536 KB zajetych przez plik dziennika.
  39970760 KB dostepnych na dysku.

      4096 bajtów w kazdej jednostce alokacji.
  18918399 ogólem jednostek alokacji na dysku.
   9992690 jednostek alokacji dostepnych na dysku.

Informacje wewnetrzne:
00 10 03 00 4d ff 02 00 d3 f1 05 00 00 00 00 00  ....M...........
3f 00 00 00 49 00 00 00 00 00 00 00 00 00 00 00  ?...I...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

System Windows zakonczyl sprawdzanie dysku.
Zaczekaj na ponowne uruchomienie systemu.
</Data>
  </EventData>
</Event>

 

I've also uninstalled avast completely using the avastclear tool. It didn't change anything. So Avast's back on my PC.
I've once again cleaned from dust PCI-E port, and RAM ports. Again nothing has changed.

I think it's mainly the GPU's fault. But im not sure what exactly is wrong. I will reinstall drivers, but firstly, I'll do a research on the driver version i have installed. Maybe it's faulty.?
 

Per Google Translate:

Log name: Application
Source: Microsoft-Windows-Wininit
Date: 2019-01-28 11:17:30
Event ID: 1001
Task category: None
Level: Information
Keywords: Classic
User: Not applicable
Computer: Computer board
Description:

Checking the file system on C:  The file system type is NTFS.
A disk check is planned.
Windows will now check the disk.

CHKDSK checks files (level 1 of 5)      Processed file records: 200704.

File checking completed.

  Records processed for large files: 413.
  Records of damaged files processed: 0.
  Extended attribute records processed: 0.
  Processed re-analysis records: 73.

CHKDSK checks indexes (level 2 of 5)
  Processed index entries: 252898.
Index verification has been completed.
  Scanned files not indexed: 0.
  Recovered non-indexed files: 0.

CHKDSK checks security descriptors (level 3 from 5)
  Processed security descriptors / file identifiers: 200704.
Clean up 422 unused entries in the $ SII index of 0x9.
Cleans 422 unused entries in the $ SDH index of 0x9.
Sorting 422 unused security descriptors.
The checking of security descriptors has been completed.
  Processed data files: 26098.

The Usn log check is in progress ...
  Processed bytes of USN numbers: 36590136.
The validation of the Usn journal has been completed.
 

CHKDSK checks file data (level 4 of 5)
  Processed files: 200688.
The data check of the file has been completed.
 

CHKDSK checks the vacancy (step 5 of 5)
  Processed free clusters: 9992689.
The disk space check has been completed.
CHKDSK detected a free space marked as allocated in
bitmap of the main file table (MFT).
CHKDSK detected a free space marked as allocated in the bitmap of the volume.
Windows has made corrections to the file system.

  75673599 KB of total disk space.
  35275680 KB in 170318 files.
    12,106 KB in 26099 indexes.
         0 KB in damaged sectors.
    306,103 KB used by the system.
     65536 KB occupied by the log file.
  39970760 KB available on disk.

      4096 bytes in each allocation unit.
  18918399 overall disk allocation units.
   9992690 allocation units available on disk.

Internal information:
00 10 03 00 4d ff 02 00 d3 f1 05 00 00 00 00 00 .... M ...........
3f 00 00 00 49 00 00 00 00 00 00 00 00 00 00? ... I ...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking the disk.
Wait for the system to restart.

Event XML code:
<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 = "2019-01-28T10: 17: 30.000000000Z" />
    <EventRecordID> 1404 </ EventRecordID>
    <Correlation />
    <Execution ProcessID = "0" ThreadID = "0" />
    <Channel> Application </ Channel>
    <Computer> Brzegomputer </ Computer>
    <Security />
  </ System>
  <EVENTDATE>
    <Date>

Checking the file system on C:
The file system type is NTFS.

A disk check is planned.
Windows will now check the disk.

CHKDSK checks files (level 1 of 5)
  Processed file records: 200704.
File checking completed.
  Records processed for large files: 413.
  Records of damaged files processed: 0.
  Extended attribute records processed: 0.
  Processed re-analysis records: 73.

CHKDSK checks indexes (level 2 of 5)
  Processed index entries: 252898.
Index verification has been completed.
  Scanned files not indexed: 0.
  Recovered non-indexed files: 0.

CHKDSK checks security descriptors (level 3 from 5)
  Processed security descriptors / file identifiers: 200704.
Clean up 422 unused entries in the $ SII index of 0x9.
Cleans 422 unused entries in the $ SDH index of 0x9.
Sorting 422 unused security descriptors.
The checking of security descriptors has been completed.
  Processed data files: 26098.

Louis

Edited by hamluis, 28 January 2019 - 06:55 AM.

Is it possible that my PC just doesn't like x64 Windows?
Maybe I just should go back to Windows 7 32 bit, just as i had pre-format.

With formatting again, there is one problem though. I'm suprised I haven't mention it earlier, it might be a very important information.
Before The first format, My PC [Especially in Games] Sometimes, always minimum once per game, started to lag.

The lag included FPS drops, Keyboard and Mouse input delay (around 5 second delay on everything. Even if i pressed the caps-lock key, the light signalising it's on on the keyboard would light up after the delay as well). The lag lasted for around ~30 seconds, and then it stopped. When it stopped, I could hear randomly 3-5 beeps from my USB speakers/headphones [NOT motherboard's speaker], the beeps sounded like morse code, they weren't high pitched like sticky keys or anything, and after the beeps ended, the lag has passed.

It always appeared for example. In League of Legends, Once per match. not more, not less here. I wanted to fix this issue, so I've done the following:

-I've Updated my Graphics Card Drivers, (also tried with older ones, no avail)
-Checked my Ram if everything's okay,
-Checked my Graphics Card if everything's okay
-Scanned for malware with Avast & Malwarebytes
-Cleaned my PC with CCleaner
-Defragmentated my Harddrive
-Disabled every program running in the background
-Checked Processes in Task Manager if there's something that shouldn't be there
-Reinstalled Keyboard & Mouse Drivers
-Restored System to the time before this issue happened for the first time.
-Changed my Antivirus Software to AVG (before the change it was Avast)
-Changed my Mouse and Keyboard
-Changed the Battery on my Motherboard
-Checked my BIOS settings
-Reinstalled and Repaired the Game.

After none of these worked, I decided to do a Format, (Beginning of this Topic)
I formatted the HDD Deleting the Partitions, Formating them and Installing a Clean OS.
My last OS version was Windows 7 x86 [32bit] for some time I've noticed that more and more things stop supporting x86 Operating systems, so i decided to go on with a fresh installment of x64.
I've installed it, installed the Graphic drivers [Somehow all the other drivers were already installed, i guess windows installed them automatically, beacuse i didn't disconnect Ethernet cable from the PC durning the installation], antivirus [AVG then because I had in the back of my head that Avast might had caused those issues] and the Game itself.
Very soon I would notice that the PC after the change from x86 to x64 is running extremely slow compared to how it worked pre-format. [Remember here that the format was only because i wanted to get rid of the input delay & beep issues]
Despite the FPS being 3 times lower than before i formatted, I decided to try out if the issue has stopped. To my suprise, it hadn't.
I was around 15 minutes into the game, The input delay repeated again, and very soon I would hear this annoying morse code.
I thought maybe the installation was faulty, that would explain the PC being Laggy, The input lag not going away, and pre-installed drivers, so i formatted again, installing Windows 7 x64 once again.

This time, I've decided to download more drivers than just the GPU one. I've installed the Chipset drivers and the GPU driver. After Installing all the updates with windows update, The PC was still very slow. Maybe there's some malware that sneaked into my pc after i installed the OS... -So I scanned my PC with CCleaner, Avast and Malwarebytes, those programs haven't found anything that could be wrong. I've checked settings in my BIOS once again, everything's okay in there, and I've also checked windows' power management. I set the power to "High performance" The PC was still slow even after that.
By checking in-game from time to time if my Framerate has fixed, or the slowness of the pc has passed, I've noticed that the Morse-code-input delay issue has passed, it hadn't occured after my second format. But the slowness of my PC remained.

I was looking for help with that second issue, and that's how I ended up on this forum.

I'm really scared of formatting again, because I'm not sure if the Input Delay Beep issue won't come back after that.
Solving it is already Half the success, but I'm starting to think more and more, that the issue of slowness of my PC is installing x64 Windows 7 on Dell Optiplex 755. Maybe it's uncompatible, maybe i have too slow RAM for that, and Maybe [In My opinion most likely] The 64 bit versions of my applications (Discord, League of Legends, Avast) Use More RAM to function normally, naturally slowing down my PC.

Should I reinstall back to 32bit Windows 7? I'm afraid I'll be risking the coming back of the input issue if i do so.
Thank you in advance for answer for this one, You've helped me so much already.
 

hamluis:

Correct me if I'm wrong, but I don't see anything serious in that chkdsk log. No bad sectors, no mutliple read attempts.

Inin:

Have you tried changing to another keyboard and mouse? I'm wondering if the beeping could be a dying keyboard. I'm also not clear when the beeping occurred, exactly.

Have you reset the machine to hardware (BIOS) defaults?

Do you by any chance, have XBOX software or updates installed?

When you say you tested the RAM, using what tool, for how long, and what were the results?

Luis: I'm wondering if he should try booting from a live disc of some sort and completely wipe all partitions from above, and do destructive formats, in case there is some malware there. What do you think? I'm growing short of ideas other than this.

Also, the symptoms are similar to the Prime95 Skylake bug. Intel claimed that only applied when calculating Prime numbers. Should we assume it doesn't apply here.

Edited by Shplad, 28 January 2019 - 10:34 AM.

Inin:How is the computer working now? If not much has changed, I suggest you go ahead with my above suggstion to uninstal Avast with the manual tool and reboot at least once or twice.

The computer's working exactly the same. I've done as you said, and nothing changed at all.

i also posted a wall of text adding some more information i've forgot to say earlier, and a possible solution to all of this

Hi,

Launch Task Manager (press Ctrl + Shift + Esc on your keyboard). What are the "CPU", "Memory" and "Disk" percentages?

Can't find Disk's percentage, by CPU is ~7%, Memory stays at 66%

Click on the memory percentage to sort the list from most memory usage to least memory usage. Which program/process is using the most memory? (at the top)

Firefox and Discord, and from non-open programs, it's "nvcontainer.exe"

Inin:

You need to work with us completely. I'm not sure why you put Avast back on right away, and you also put Discord on. How do we know Discord isn't the problem? Have you uninstalled Discord and rebooted?

Inin:

Are your Windows x32 and X64 both from the same media, or two different media?

Luis: What do you think about it being a possible Intel Skylake Prime95 bug? A log of people swear that comes up with any kind of heavy load, and not just Primes.

The only things left I can think of to check are:

1. Try a different Windows source media

(Are your source media for x32 and x64 different or the same?)

2. Nuke drives from above

3. Check voltages of PSU.

Inin: Have you checked the voltages of your power supply, either with something like HWMonitor or in the hardware setup

(if you machine shows that)? An unstable power supply might explain some of this, though it would usually result in other symptoms

as well.

5. If all else failed, I'd try a diff. CPU, to make sure the Skylake bug wasn't involved here.

Edited by Shplad, 28 January 2019 - 10:56 AM.

Have you tried changing to another keyboard and mouse? I'm wondering if the beeping could be a dying keyboard. I'm also not clear when the beeping occurred, exactly.

-Changed my Mouse and Keyboard

Yes, i did.
And also the beeping was at random. once per match in League of Legends. I couldn't predict when it was going to happen, i just knew it will.
 

Have you reset the machine to hardware (BIOS) defaults?

 

 

Do you by any chance, have XBOX software or updates installed?

 

 

When you say you tested the RAM, using what tool, for how long, and what were the results?

BIOS : Yes, I've tried, With the default settings the pc wouldn't boot, so i had to change some [I told yesterday about those 4 RAID/something things.]

XBOX: Nope, I don't

RAM: I meant i checked it manually, If they're plugged in the pc well, if the ports are dusty etc.
 

Also, the symptoms are similar to the Prime95 Skylake bug. Intel claimed that only applied when calculating Prime numbers. Should we assume it doesn't apply here.

The issue wasn't freezing of the pc, just a really big input delay, slowdown of the pc and framerate followed by the morse-code like beeping.

Also, After the second format, The one im using my pc on right now, The issue has stopped. I think on going back to 32bit, to fix the pc slowness issue, but im afrait the input delay will come back.

Have you tried changing to another keyboard and mouse? I'm wondering if the beeping could be a dying keyboard. I'm also not clear when the beeping occurred, exactly.

-Changed my Mouse and Keyboard

Yes, i did.
And also the beeping was at random. once per match in League of Legends. I couldn't predict when it was going to happen, i just knew it will.
 

Have you reset the machine to hardware (BIOS) defaults?

 

 

Do you by any chance, have XBOX software or updates installed?

 

 

When you say you tested the RAM, using what tool, for how long, and what were the results?

BIOS : Yes, I've tried, With the default settings the pc wouldn't boot, so i had to change some [I told yesterday about those 4 RAID/something things.]

XBOX: Nope, I don't

RAM: I meant i checked it manually, If they're plugged in the pc well, if the ports are dusty etc.
 

Also, the symptoms are similar to the Prime95 Skylake bug. Intel claimed that only applied when calculating Prime numbers. Should we assume it doesn't apply here.

The issue wasn't freezing of the pc, just a really big input delay, slowdown of the pc and framerate followed by the morse-code like beeping.

Also, After the second format, The one im using my pc on right now, The issue has stopped. I think on going back to 32bit, to fix the pc slowness issue, but im afrait the input delay will come back.

Inin:

 

You need to work with us completely. I'm not sure why you put Avast back on right away, and you also put Discord on. How do we know Discord isn't the problem? Have you uninstalled Discord and rebooted?

I haven't put discord right away. The PC was slow already just after the boot after the format, it didn't become slow after i've installed something. Without discord, the speed was the same.

I got avast back so soon because i wasn't able to enable windows defender at all, it didn't let me, and without the avast, the performance hasn't changed at all too.
 

Inin:

 

Are your Windows x32 and X64 both from the same media, or two different media?

Same media.
 

 

The only things left I can think of to check are:

 

1. Try a different Windows source media

2. Nuke drives from above

3. Diff. keyboard and mouse

4. Check voltages of PSU.

 

Inin: Have you checked the voltages of your power supply, either with something like HWMonitor or in the hardware setup

(if you machine shows that)? An unstable power supply might explain some of this, though it would usually result in other symptoms

as well.

 

5. If all else failed, I'd try a diff. CPU, to make sure the Skylake bug wasn't involved here.

1. I will try to get one and boot it from a flash drive if i decide for a format, I added a lot and said that im not sure about doing that
2. ???
3. Done already, didn't work at first. Also as I said, after the second format the beep issue has passed.
4. I haven't. I'm not sure where is it in HWMonitor.
5. Are you comparing the Skylake bug to the Beep issue, or my overall slowdown of my pc? I'm not sure.