Soluții

Fix ‘CPU and Disk 100% Usage’ on Windows 11

• Data 10/08/2021
• Autor Stefan Anghel
• -4
• 497

Your CPU or Disk usage staying at 100% can have several different causes, but there are only a handful of culprits that are confirmed to cause this type of behavior on Windows 11. Here’s a list of scenarios that are known to cause unreasonably high Disk & CPU usage on the latest operating system released by Microsoft:

Now that we went over every potential cause that has the potential of keeping your CPU and Disk at 100% usage on Windows 11, let’s go over a couple of fixes that other Windows 11 users have successfully used to alleviate the problem:

Disable Windows Search

Just as with Windows 10, the number one culprit that likely produces these 100% disk usage issues is the search function. Apparently, the way the search function is designed to always index and keep track of new file entries will end up hogging all the system resources on low-end PCs – This affects both the CPU and traditional HDDs.

If the search function is indeed to blame for this particular issue and you’re actively using it, you’re not going to like the resolution. As of now, the only reliable way of stopping file indexing (caused by Windows Search) from hogging all your system resources is to disable the function altogether.

This is done via the Services screen – You’ll need to start by stopping the status of the service prior to modifying the Startup type.

IMPORTANT: Doing this modification essentially means that you’re giving up on the search function on Windows 11. Your operating system will no longer spend time automatically indexing the files that are stored on your PC. This might fix your disk usage problems, but it will also prevent you from using Windows Search again.

If you understand what this modification will do to your operating system and you are ready to enforce this modification, follow the steps below:

1. Start by pressing Windows key + R key to open up a Run prompt. At the dedicated prompt that just appeared, type ‘services.msc’ inside the text box and press Enter to open up the Services screen.
   

2. Once you’re inside the Services screen, move over to the right-hand side section of the page and scroll down through the list of services until you locate Windows Search.
3. When you see it, right-click on it and click on Properties from the dedicated context menu.
   

4. Inside the Properties screen of Windows Search, start by accessing the General tab using the ribbon menu at the top.
5. Next, check the Service status and see if it’s currently Running – If it’s set to Running, click on the Stop button below and wait until the service is stopped in its tracks.
6. After the Windows Search service is finally stopped, change the Status type above from Automatic (Delayed Start) to Disabled.
   

7. Once the Windows Search service has been stopped, open Task Manager (Ctrl + Shift + Esc) and see if the Disk and CPU usage has gone down.

If the problem is still persisting, move down to the next potential fix below.

Disable Superfetch (Sysmain)

If you already tried disabling Windows Search or you aren’t ready to enforce this compromise, one additional likely culprit that might hogg all your system resources and keep your CPU and Disk usage at 100% is Superfetch (Sysmain).

Note: The purpose of this service is to increase the performance of your operating system by preloading apps you frequently use into RAM before you need to use them.

While this sounds great in theory and works beautifully on medium & high-end PCs, the same cannot be said for low-end configurations – If you are using a PC with limited RAM (with low frequencies), Sysmain will only make things worse because it will switch the burden from your RAM to VRAM (virtual memory hosted on your HDD or SSD).

This will most likely keep your Disk usage at 100% as your PC struggles to pre-load your most frequently used apps. If you find yourself in this situation and you wish to alleviate the problem, the only tradeoff you can make is to prevent Sysmain from pre-loading your apps – This will serve the purpose of freeing up your system resources (especially your Disk Usage).

You can disable Sysmain via the Services screen. You’ll need to stop it first before modifying the Startup behavior.

1. Open up a Run dialog box by pressing Windows key + R. Inside the newly appeared dialog box, type ‘services.msc’ and hit Enter to open up the Services screen.
   

   Note: If you are prompted by the User Account Control window, you’ll need to accept admin rights by clicking Yes.

2. Inside the Services screen, use the menu on the right-hand side to find SysMain.
3. When you find the correct service, right-click on it and click on Properties from the menu at hand.
   

4. In the SystMain Properties screen, select the General tab from the menu at the top, then Stop the service using the dedicated button under Service status.
5. Next, change the Startup type to Disabled before clicking on Apply to enforce the changes and make them permanent.
   

6. Once Sysmain has been effectively stopped, press Ctrl + Shift + Esc to open Task Manager and check if the Disk usage has gone down.

If the problem is still not yet fixed, follow the next method below for a different way of lowering your Disk usage on Windows 11.

Disable Native Command Queuing for your SATA AHCI Controller

If the first two methods were not effective in your case, let’s turn our attention to your SATA AHCI Controller driver and investigate either a built-in feature (Native Command Queuing) is not actually making your HDD perform worse than it should on Windows 11.

As it turns out, Windows 11 is quite inefficient at allowing HDDs to use native Command Queuing and this failure often results in the drive being stuck at 100%, rendering the PC in a prolonged frozen state. Fortunately, you can fix this issue by doing some Registry Modifications to your SATA AHCI Controller driver so that Native Command Queuing is disabled – This will make your disk drive slightly slower, but it will likely solve any underlying disk usage problem on Windows 10.

Important: This method is only recommended for PC configurations using traditional HDDs. We haven’t been able to confirm this particular issue occurring with SSDs and Ultrafast SSDs.

Follow the instructions below to disable native command queuing for your SATA AHCI Controller in order to bring down the disk usage on your Windows 11 computer:

1. Press Windows key + R to open up a Run dialog box. Next, type ‘devmgmt.msc’ inside the dialog box that’s currently on screen and hit Enter to open up Device Manager. If you see the User Account Control window, grant administrative access by clicking on the Yes box.
   

2. Once you’re inside Device Manager, scroll down through the list of devices and expand the drop-down menu associated with IDE ATA / ATAPI controllers.
3. Next, right-click on your Standard SATA AHCI Controller driver and choose Properties from the context menu that just appeared.
   

   Note: If you’re using a dedicated driver for your ATA / ATAPI controllers, the name of your controller might be different. For example, the name for Intel controller drivers is Intel(R) xxx Series Chipset Family SATA AHCI Controller.

4. Once you’re inside the Properties screen, select the Details tab at the top, then change the drop-down menu of Property to Device Instance path.
5. Next, right-click directly on the path under Value and hit Copy from the context menu.
   

6. Now that you have the correct path safely copied onto your clipboard, press Windows key + R key to open up a dialog box. Next, type ‘regedit’ and hit Ctrl + Shift + Enter to open up the Registry Editor with admin access.
   

7. When you see the User Account Control prompt, click Yes to grant admin access.
8. Once you’re inside the Registry Editor, use the navigation at the top to land in the following location:

   Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI

   Note: You can either navigate to this location yourself or you can paste the location directly into the navigation bar to get there instantly.

9. Once you’re inside the correct location, go to the navigation bar at the top, select the last part (PCI) and paste the path that you currently copied to your clipboard at step 5.
   

10. With the pat successfully pasted, hit Enter, then move back to the left-hand side many and expand the Device Parameters key.
11. Next, expand the Interrupt Management key and select the MessageSignaledInterruptProperties key.
    

12. Next, move over to the right-hand section of Registry Editor and double-click on MSISupported.
13. Next, set the Base of MSISupported to Hexadecimal, then set the Value data to 0 to effectively disable native command queuing.
14. Finally, close Registry Editor and restart your computer in order to allow the changes to take effect.
15. After your computer boots back up, open up Task Manager (Ctrl + Shift + Esc) and see if the resource usage has gone down.

Windows 10 Stuck on “Repairing Disk Errors”

• Data 10/08/2021
• Autor Stefan Anghel
• -9
• 547

The ‘Repairing disk errors‘ screen is often associated with a systemic corruption issue a hardware issue or a software conflict that’s affecting the booting sequence. This screen typically appears after an unexpected system BSOD crash.

We’ve managed to identify a series of common scenarios that might be the end cause of this stuck screen. Check out a few potential scenarios that might cause this behavior:

To simplify things for you, we’ve created a couple of sub-guides that will hopefully help you get to the bottom of the ‘Repairing disk errors‘ screen:

The iusb3xhc.sys blue screen error

• Data 10/08/2021
• Autor Stefan Anghel
• 13
• 444

The blue screen of death or BSOD is always an unwelcome sight. BSODs appear when Microsoft Windows encounters a critical error from which it can’t recover, usually the result of low-level software (or drivers) crashing or faulty hardware.

Blue screens are generally caused by problems with your computer’s hardware or issues with their hardware driver software. Sometimes, they can be caused by issues with low-level software running in the Windows kernel. Regular apps usually won’t be able to cause blue screens. If an app crashes, it will do so without taking the operating system out with it. A blue screen occurs when Windows encounters a “STOP Error.” This critical failure causes Windows to crash and stop working. The only thing Windows can do at that point is to restart the PC. This can lead to data loss, as programs don’t have a chance to save their open data.

When a blue screen occurs, Windows automatically creates a “minidump” file that contains information about the crash and saves it to your disk. You can view information about these minidumps to help identify the cause of the blue screen.

Blue screens also look a bit different, depending on what version of Windows you’re running. In Windows 7 and previous versions, the blue screen looked much like a terminal screen, displaying all manner of information. In Windows 8 and 10, blue screens are much simpler. That’s really not as big a deal as it sounds, though. Even in previous versions, blue screens tended to go by fast enough that reading that information was difficult, anyway. And there are easier ways to get all the details you need for troubleshooting.

What is causing the iusb3xhc.sys BSOD crashes?

We investigated this particular issue by looking at various user reports and the repair strategies that are commonly being used to fix this particular error message. As it turns out, there are multiple causes that could lead to a BSOD of this kind. Here’s a shortlist of potential culprits that can cause constant iusb3xhc.sys blue screens:

Corrupted / Incompatible USB Host Controller drivers – As it turns out, this particular issue can also occur due to a corrupted or incompatible Host USB Controller driver. If this scenario is applicable, you should be able to resolve the issue by uninstalling the Host USB controller drivers via Device Manager and reinstalling them at the next system startup.

Intel Chipset drivers are not installed – Missing Intel Chipsets can also be a potential cause for this issue – especially if you’re using a motherboard that is designed to work with these drivers. In this case, you should be able to resolve the issue by using the Intel Support Assistant utility to install the missing firmware.

System file corruption – System file corruption is another possible cause that might lead to unexpected BSOD crashes related to the iusb3xhc.sys file. If this scenario is applicable to your particular case, you can resolve the issue by fixing the corrupted system file with a utility like DISM or SFC.

Overprotective security suite – Judging from various user reports, this particular issue can also be caused by an AV or firewall that is interfering with the host controller driver. In most cases, Karsperksly is singled out as a culprit capable of quarantining a dependency of the Host controller driver. In this case, you can resolve the issue by uninstalling the 3rd party security suite and removing any remnant files.

Cached memory issue – Another possibility is that you’re dealing with badly cached data regarding the usage of your memory. If this scenario is applicable, you will be able to resolve the issue simply by opening the case of your unit and taking out the CMOS battery.

4 comenzi CMD de retea utile

• Data 10/08/2021
• Autor razvan martes
• 1
• 777

1.Netstat

Comanda netstat ne ajuta sa verificam ce porturi TCP sau UDP sunt deschise pe calculatorul nostru.

2.Ipconfig /all

Aceasta comanda ne ajuta sa vedem toate informatiile din reteaua noastra +mac-ul dispozitivului.

3.Ipconfig /release si ipconfig /renew
ipconfig /release – aceasta comanda face ca adaptorul de retea sa execute comanda disable/enable
ipconfig /renew –  este comanda care ii cere dhcp-ului (Dynamic Host Configuration Protocol) din router un alt ip pentru calculatorul nostru.

 
4.ping

Ping-ul trimite un pachet catre o destinatie si astepta raspuns, cu aceasta comanda putem verifica daca avem pierderi in retea.