Logo

10 Worst Computer Viruses in history

Computers viruses, worms, ransomware, etc. are kinds of malicious software that no user should take lightly. On several occasions, we have touched upon security steps that each user should take in order to protect its identity and data. Sadly sometimes even when all precautions are taken some malware can still slip through and wreak havoc. Today we are looking at some of the worst or the best, depending on your view that has indeed wreaked plenty of havoc.

viruses10 worst computer viruses in history

In the list of the 10 most famous computer viruses below, we show the costs, dates, reach, and other key facts. First a note about terms: we use the words “virus” and “worm” interchangeably because most readers search for them that way. But there’s a subtle difference that we explain after the list.

1. Mydoom – $38 billion

The worst computer virus outbreak in history, Mydoom caused estimated damage of $38 billion in 2004, but its inflation-adjusted cost is actually $52.2 billion. Also known as Novarg, this malware is technically a “worm,” spread by mass emailing. At one point, the Mydoom virus was responsible for 25% of all emails sent.
Mydoom scraped addresses from infected machines, then sent copies of itself to those addresses. It also roped those infected machines into a web of computers called a botnet that performed distributed denial of service (DDoS) attacks. These attacks were intended to shut down a target website or server.

Mydoom is still around today, generating 1% of all phishing emails. That’s no small feat considering the 3.4 billion phishing emails sent each day. By that figure, Mydoom has taken on a life of its own, infecting enough poorly-protected machines to send 1.2 billion copies of itself per year, 16 years after its creation.
Though a $250,000 reward was offered, the developer of this dangerous computer worm was never caught.
Wondering what makes the world’s most secure computers so safe? See the Tech@Work guide: Upgrade to the World's Most Secure and Manageable PC

2. Sobig – $30 billion

The 2003 Sobig computer virus is actually another worm. It is second only to the Mydoom virus in its scope. The $30 billion figure is a worldwide total, including Canada, the U.K., the U.S., mainland Europe, and Asia. Several versions of the worm were released in quick succession, named Sobig.A through Sobig.F, with Sobig.F being the most damaging.
This cybercriminal program masqueraded as legitimate computer software attached to emails. It disrupted ticketing at Air Canada and interfered with countless other businesses. Despite its widespread damage, the creator of the successful bug was never caught.

3. Klez – $19.8 billion

Klez is a close third on the list of the worst computer viruses ever created. With nearly $20 billion in estimated damages, it infected about 7.2% of all computers in 2001, or 7 million PCs. The Klez worm sent fake emails, spoofed recognized senders and, among other things, attempted to deactivate other viruses.
As with other viruses and worms, Klez was released in several variants. It infected files, copied itself, and spread throughout each victim’s network. It hung around for years, with each version more destructive than the last.
Windows has come a long way since most of the computer viruses on this list hit the web. Thankfully, built-in protection with Microsoft Defender is always on the watch.

4. ILOVEYOU – $15 billion

The year 2000’s ILOVEYOU virus worked by sending a bogus “love letter” that looked like a harmless text file. Like Mydoom, this attacker sent copies of itself to every email address in the infected machine’s contact list. Shortly after its May 4 release, it had spread to more than 10 million PCs.
The virus was created by a college student in the Philippines named Onel de Guzman. Lacking funds, he wrote the virus to steal passwords so he could log into online services he wanted to use for free. He reportedly had no idea how far his creation would spread. This virus is also known as Loveletter.
Need to up your remote work security game before there’s another entry on the list of most deadly computer viruses? See our guide: How to Work Remotely and Securely

5. WannaCry – $4 billion

The 2017 WannaCry computer virus is ransomware, a virus that takes over your computer (or cloud files) and holds them hostage. The WannaCry ransomware ripped through computers in 150 countries, causing massive productivity losses as businesses, hospitals, and government organizations that didn’t pay were forced to rebuild systems from scratch.
The malware raged like wildfire through 200,000 computers worldwide. It stopped when a 22-year-old security researcher in the U.K. found a way to turn it off. Computers with out-of-date operating systems were hit especially hard. That’s why security experts always recommend updating your systems frequently.

Ransomware strikes again

In September 2020, one of the potentially largest computer virus attacks in medical history hit Universal Health Services. The U.S. hospital chain, which has more than 400 locations, was reportedly struck by damaging ransomware. The attack forced the cancellation of surgeries and made healthcare workers switch to paper records.

6. Zeus – $3 billion

The Zeus computer virus is an online theft tool that hit the web in 2007. A whitepaper by Unisys three years later estimated that it was behind 44% of all banking malware attacks. By then, it had breached 88% of all Fortune 500 companies, 2,500 organizations total, and 76,000 computers in 196 countries.
The Zeus botnet was a group of programs that worked together to take over machines for a remote “bot master.” It originated in Eastern Europe and was used to transfer money to secret bank accounts. More than 100 members of the crime ring behind the virus, mostly in the U.S., were arrested in 2010. It’s not as prominent today, but some of the virus’ source code lives on in newer botnet viruses and worms.

Zeus caused documented damage of $100 million. But the real cost in terms of lost productivity, removal, and undocumented theft is undoubtedly much higher. A $3 billion estimate, adjusted for inflation, puts this virus at a cost of $3.7 billion in today’s dollars.

7. Code Red – $2.4 billion

First observed in 2001, the Code Red computer virus was yet another worm that penetrated 975,000 hosts. It displayed the words “Hacked by Chinese!” across infected web pages, and it ran entirely in each machine’s memory. In most cases it left no trace in hard drives or other storage.
Financial costs are pegged at $2.4 billion. The virus attacked websites of infected computers and delivered a distributed denial of service (DDoS) attack on the U.S. White House’s website, www.whitehouse.gov. In fact, the White House had to change its IP address to defend against Cod Red.
Can your printer get a virus? See our cool infographic: The State of Printer Security

8. Slammer – $1.2 billion

The SQL Slammer worm cost an estimated $750 million across 200,000 computer users in 2003. This computer virus randomly selected IP addresses, exploiting vulnerabilities and sending itself on to other machines. It used these victim machines to launch a DDoS attack on several internet hosts, significantly slowing internet traffic.
The Slammer worm hit banks in the U.S. and Canada especially hard, taking ATMs offline in many locations. Customers of Toronto’s Imperial Bank of Commerce found themselves unable to access funds. The attack reared its ugly head again in 2016, launching from IP addresses in Ukraine, China, and Mexico.

9. CryptoLocker – $665 million

Thankfully, ransomware attacks like the 2013 CryptoLocker virus have dipped since their 2017 peak. This malware attacked upwards of 250,000 machines by encrypting their files. It displayed a red ransom note informing users that “your important files encryption produced on this computer.” A payment window accompanied the note.
The virus’ creators used a worm called the Gameover Zeus botnet to make and send copies of the CryptoLocker virus. According to a report by security firm Sophos, the average ransomware attack costs a business $133,000. If we estimate that CryptoLocker hit 5,000 companies, that would put its total cost at $665 million.
Where will cybersecurity go next? See our guide: The Future of Cybersecurity

10. Sasser – $500 million

The Sasser worm was written by a 17-year-old German computer science student named Sven Jaschan. He was arrested at the age of 18 in 2004 after a $250,000 bounty was posted for the computer virus’ creator. A friend of Jaschan’s tipped authorities that the youth had penned not only the Sasser worm but also the damaging Netsky.AC attack.
Jaschan was given a suspended sentence after it was found he was a minor when he wrote the malware. The Sasser worm crashed millions of PCs, and though some reports put damages at $18 billion, the relatively low infection rate suggests a more likely cost of $500 million.
Other notable viruses

The top 10 worst computer viruses above are just the ugly tip of a gargantuan digital iceberg. With a million new malware programs popping up every 3 years, we may miss the forest for a few outstanding trees. Here are just a few more viruses that have wreaked havoc over the years:

Mimail: This worm tried to harvest data from infected machines to launch a string of DDoS attacks, but was relatively easy to remove.

Yaha: Yet another worm with several variants, thought to be the result of a cyber-war between Pakistan and India.

Swen: Written in C++, the Swen computer worm disguised itself to look like a 2003 OS update. Its financial cost has been pegged at $10.4 billion, but not reliably.

Storm Worm: This worm showed up in 2007 and attacked millions of computers with an email about approaching bad weather.

Tanatos/Bugbear: A 2002 keylogger virus that targeted financial institutions and spread to 150 countries.

Sircam: A computer worm from 2001 that used counterfeit emails with the subject line, “I send you this file in order to have your advice.”

Explorezip: This worm used fake emails to spread to every machine on thousands of local networks.

Melissa: The most dangerous computer virus in 1999, Melissa sent copies of itself that looked like NSFW pics. The U.S. FBI estimated cleanup and repair costs at $80 million.

Flashback: A Mac-only virus, Flashback infected over 600,000 Macs in 2012 and even infected Apple’s home base in Cupertino, Calif. In 2020, there’s now more malware on Macs than on PCs.

Conficker: This 2009 virus still infects many legacy systems and could do significant damage if it ever activates.

Stuxnet: This worm is reported to have destroyed Iranian nuclear centrifuges by sending damaging instructions.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Quick Fix Guide for Stop Code 0x0000008e

What Is STOP Code 0x0000008e

The STOP Code 0x0000008E is essentially an error code that is displayed on the STOP message. This STOP message is also commonly known as Blue Screen of Death or BSOD for short. When this error occurs, usually messages like, “STOP: 0x0000008E” or “KERNEL_MODE_EXCEPTION_NOT_HANDLED” are displayed to the user.

Solution

Download Available to Completely Repair Error 0x0000008e

Restoro box imageError Causes

These errors are commonly caused by failures of memory hardware. However, viruses, hardware failures or issues with the device drivers may also trigger them. If this error code appears but Windows is successfully able to recover from it, then the message ‘Windows has recovered from an unexpected shutdown’ is displayed to the users. Regardless of what causes these errors, it is of paramount importance that counteractive measures are taken as soon as the error appears.

Further Information and Manual Repair

While this error can be removed in many ways, the most effective ones are listed below as follows.
  • The screen might be a fluke. Restart your system; the blue screen that appears to you may not be what it seems.
  • Have you just modified or installed new hardware or driver? If yes, it is highly likely that the change you have made has triggered the error. If this is the case, it is strongly recommended that you revert back to the original settings and check whether the blue screen appears again or not. If it does, you can fix it by reconfiguring or removing the hardware you have recently installed. You can perform System Restore or you can go back to the previous versions if you have installed a new driver.
  • To keep this error from occurring in the future, it is strongly advised that you test your RAM. Damaged memory or one that’s unable to perform in the usual manner is often the reason this error occurs.
  • Ensure appropriate installation of your system memory. If you have installed memory in a way other than advised by your memory manufacturer that it may lead to STOP 0x0000008E error or other problems.
  • Misconfigured or over-clocked memory settings can cause STOP 0x0000008E errors as well. To remedy this situation, it is best advised to return the BIOS settings to their default level.
  • If you haven’t updated your Windows, apply all the updates you come across. Patches and service packs specifically address such issues.
Read More
Fix DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
If you suddenly encounter the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error on your Windows 10 computer along with the error codes, 0x000000D5, 0xb10BBD9E, 0x0D82DA24, 0Xfecd479D, 0x779827CB then read on as this post will provide you some troubleshooting tips that could help you resolve the BSOD error. Getting this kind of BSOD error means that a driver has referenced memory that was freed earlier and it could also mean that the Driver Verifier Special Pool option has caught the driver accessing memory which was freed earlier. Follow the given options below to fix the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error.

Option 1 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.
  • Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
  • After that, select the option “Create custom settings”.
  • Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
  • Next, select the option “Select driver names from a list” option.
  • Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
  • Then click on the Finish button.
  • Open Command Prompt as administrator and execute this command – verifier /querysettings
  • The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
  • Open the Command Prompt as admin again and run this command – verifier /reset
  • The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 2 – Try updating SSD firmware

If you have installed SSD on your computer recently and you have started getting the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error since then you may have to update the SSD firmware. To fix this, you can download the Intel Solid-State Drive Toolbox from the official website. This toolbox is compatible with Windows 10 and Windows 7 and later versions.

Option 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.

Option 5 – Try to reinstall or update device drivers of recently installed hardware

If the first few options didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers and right-click on them to open the Properties.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 6 – Try disabling Hardware Acceleration

You might want to disable Hardware Acceleration system-wide or for a particular program like Google Chrome and see if it resolves the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error
Read More
Moving Taskbar to second monitor in Windows
If you are using a multi-monitor, then you might find it quite useful. It helps many users with their work and brings more productivity. And over the past few years, Windows has managed to offer one of the excellent multi-monitor features where users can plug in an additional monitor and access their work or use their computer seamlessly on both displays. This is really handy, especially for users who are graphic designers, gamers, and other professionals who have to use a larger screen for their work. One of the biggest inconveniences for users who use multi-monitor is that the Taskbar is switched on, on both displays, by default. This default arrangement is most likely to cause clutter on the second display. So if you are one of these users who find such a thing annoying, then you will find this post useful for you as we will walk you through how you can move the Taskbar to a second monitor. To get started, follow the instructions laid out below. Step 1: The first thing you have to do is right-click on the Taskbar. Step 2: Next, uncheck the “Lock the taskbar” option. Step 3: After that, click and hold the taskbar and drag it to the second monitor. Step 4: Once done, click the mouse button on the place where you want to place the taskbar. Step 5: Now right-click on the “Lock the taskbar” option to lock the taskbar. Once you’re done carrying out the steps given above, there are Advanced Options you can explore. This array of advanced options are offered by Windows 10 to fine-tune the multi-monitor experience of users. For instance, you have the option to choose to show the taskbar on an active screen only or combine the buttons on other taskbars. It would be better if you try out different variations and stick with the best one. In addition, you could also move the taskbar from one display to another.
Read More
Cortana is Not Connecting to the Internet
Recently, a number of Windows 10 users reported that they were not able to use Cortana properly because it wasn’t able to connect to the internet. According to these users, Cortana won’t connect to the internet even when their internet connection is stable. According to security experts, this issue is confirmed to occur only with Microsoft accounts. This problem might have something to do with a proxy server that interferes with Cortana. There were reports that this issue was caused by a proxy that was filtering the network connection which also happens to interfere with Cortana’s ability to adapt search results and queries based on the user’s location. It could also be caused by some glitch in the home network or your Microsoft account information is inconsistent or your Microsoft account has to be verified. Here are some suggestions that could help fix the connection issue in Cortana, just start with the first one and work your way down until you encounter an option that fixes the problem.

Option 1 – Restart or reset your modem or router

The first thing you can try is restarting or resetting your modem or router. All you have to do is unplug the power cable of the modem and then plug it back in after a few seconds. You could also use the reset button of the modem at the back if it is one. But before you press the reset button, keep in mind that it will erase all the connection credentials and it will be set back to its default settings. After rebooting the network, you can restart your computer to force your modem or router to reassign an IP address to your computer.

Option 2 – Restart Cortana

Restarting Cortana can help you resolve the issue.
  • To restart Cortana, open the Task Manager, right-click on Cortana and select the “End process” option.
  • Then go to the File tab and select “Run new task”.
  • After that, type in “cortana.exe” and press Enter to restart the process.

Option 3 – Try to remove Proxy

Removing the Proxy might also help you in fixing the connection issue in Cortana. Here’s how you can do it:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
  • After that, go to the Connections tab and select the LAN settings.
  • From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
  • Now click the OK and the Apply buttons.
  • Restart your PC.
Note: If you are using a third-party proxy service, you have to disable it.

Option 4 – Open another app that uses a Microsoft account

This might seem like an odd fix, however, a couple of users tried doing this and it worked for them as it allowed Cortana to connect to the internet again. In this option, you just have to launch another app that uses your Microsoft account information in the same way as Cortana, for instance, the Store app. Once you open the app, a prompt should appear along with a dialog box that allows you to update your Microsoft account with the information required. After that, restart your computer and check if Cortana is now able to connect to the internet or not.

Option 5 – Verify your Microsoft account

In some cases, Cortana might not be able to connect to the internet because your Microsoft account is no longer verified. This usually happens when you use a two-step authentication system with your Microsoft account. To verify it, just open Settings and click on Accounts. After that, check if you have a Verify hyperlink under your Microsoft account or not then click on Verify. Afterward, follow the next on-screen prompts to verify your Microsoft account. Once your account is verified, restart your computer.

Option 6 – Reset Cortana settings

  • Open Cortana and go to the Settings section where you’ll see the “Turning off Cortana clears what Cortana knows on this device, but won’t delete anything from the Notebook. After Cortana is off, you can decide what you’d like to do with anything still stored in the cloud” option. Turn this option off.
  • Restart your PC.
  • After your computer boots, launch Cortana again and check.
Read More
How to Fix dxgmms2.sys BSOD in Windows
The dxgmms2.sys file is a system driver file in Windows that is associated with the Graphics Rendering capabilities of a computer. However, this file is known to cause various Blue Screen of Death errors. Some of the culprits for these errors include issues with RAM, hard disk issues, corrupted drivers, and incompatible firmware. Despite its many causes, fixing this issue is quite straightforward so it should be easier for you to fix it. Here are some of the Blue Screen errors related to the dxgmms2.sys file:
  • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • SYSTEM_SERVICE_EXCEPTION
  • KMODE EXCEPTION NOT HANDLED
  • PAGE FAULT IN A NONPAGED AREA
  • IRQL NOT LESS OR EQUAL
If you have recently created a System Restore point prior to getting the dxgmms2.sys Blue Screen error, then you need to perform System Restore first before you further troubleshoot the problem as it might help in resolving the Blue Screen error. Refer to the steps below to perform System Restore.
  • First, press the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Reinstall the Graphics Card drivers

  • Tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. From there, look for the Graphics Card drivers listed under Display Adapters.
  • Right-click on each one of the Graphics Card drivers and select Uninstall device and then follow the next on-screen instructions given to uninstall the driver.
  • Now reboot your computer. During this time, your system will automatically reinstall the Graphics card drivers.
Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it. After that, you could also check if there’s a new update of the game you’re getting the issue of the black bar.

Option 2 – Try running the DirectX Diagnostic Tool

Since the dxgmms2.sys Stop error has something to do with the DirectX Graphics APIs, you can run the DirectX Diagnostic tool to resolve the problem.

Option 3 – Try updating or re-installing DirectX

If the DirectX Diagnostic tool didn’t work, you can try to update or reinstall DirectX instead. This can help in fixing the problem because when you reinstall or update DirectX, it will replace the incompatible or corrupted components of DirectX from your computer.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the Blue Screen error related to the dxgmms2.sys file but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version on your computer.
  • Now restart your computer to apply the changes made.

Option 5 – Use some registry tweaks

  • Tap the Win + R keys to launch the Run utility.
  • Then type “Regedit” in the field and hit Enter to open the Registry Editor.
  • Next, navigate to this registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlGraphicsDrivers
  • From there, right-click on the right-side panel and click on New > DWORD (32-bit) Value.
  • Then set the name of the new DWORD to “TdrDelay”.
  • After that, use the next set of instructions and select the one for the Windows version you are using.

32-bit Windows:

  • Choose the DWORD (32-bit) value.
  • Then type in “TdrDelay” as the name and hit Enter.
  • After that, double click on TdrDelay and add “10” as its value and click OK. This will set the response time for your GPU to be 10 seconds.

64-bit Windows:

  • Select the QWORD (64-bit) value.
  • Next, type in “TdrDelay” as the name and hit Enter.
  • Double click on TdrDelay and type in “10” as its value data and click OK.
  • Restart your computer to apply the changes made.

Option 6 – Disable the Sleep Functionality

You might also want to disable the Sleep Functionality as it could be the reason why you’re getting the Blue Screen error. There are times when the graphics card’s drivers are being used in the background and if the display goes to sleep and is awakened, it may cause a Blue Screen error. To fix it, you can prevent your computer from going into Sleep mode.

Option 7 – Try to run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that might help you fix any Blue Screen errors related to the dxgmms2.sys file. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.
Read More
Fix Windows Update Error 0x80244007
Getting errors while trying to update your Windows 10 computer is not an uncommon occurrence. Although some of them are easy to fix, there are others that need a lot of time and research in order to resolve. One of these tough Windows Update errors is Error 0x80244007. This kind of Windows Update error halts the process of Windows Update and a simple system restart won’t help much to fix it. When you encounter this Windows Update error, you will see a description that says, “SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes”. One of the main causes of such an error is that Windows was not able to renew the cookies for Windows Update. To fix this error, here are some suggestions that might be useful.

Option 1 – Clear up temporary or junk files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.
  • Open Setting > System > Storage from the WinX Menu.
  • From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
  • Next, find a link that says “Free Up Space” and click it to open.
  • After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
    • Windows Upgrade Log Files
    • The system created Windows Error Reporting Files
    • Thumbnails
    • Temporary Internet Files
    • Previous Windows Installation Files
    • Delivery Optimisation Files
    • DirectX Shader Cache
  • Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
  • Now go to the “Free Up Space Now” section and click the Clear Now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix the Windows Update error 0x80244007.

Option 2 – Try running the Windows Update troubleshooter

Windows 10 have various troubleshooters that can help you resolve many system issues. So if you’re dealing with Windows Update errors like Error 0x80244007, you can run the Windows Update troubleshooter to resolve it. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Try to reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:
  • Open Command Prompt with admin privileges.
  • After that, type each one of the following commands and hit Enter after you key in one after the other.
    • net stop wuauserv
    • net stop cryptsvc
    • net stop bits
    • net stop msiserver
Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS and MSI Installer.
  • After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below and don’t forget to hit Enter after you type one command after the other.
    • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
    • ren C:WindowsSystem32catroot2 Catroot2.old
  • Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
    • net start wuauserv
    • net start cryptsvc
    • net start bits
    • net start msiserver
  • Close Command Prompt and reboot your PC.
Read More
How to Fix Windows 10 Error Code 0xc004fc03

Error Code 0xc004fc03 – What is it?

Error code 0xc004fc03 occurs when Windows users fail to activate their Windows operating system due to a networking problem. The error code’s common symptoms include the following:

  • Inability to activate Windows 10 operating system
  • Message box with error code 0xc004fc03

Solution

Restoro box imageError Causes

Error code 0xc004fc03 in Windows 10 usually occurs due to issues related to a Windows user’s network. Your computer may be having problems connecting to the Internet or your firewall may be blocking or interrupting your device’s ability to activate Windows 10. In some cases, users may simply need to wait a day or two to reattempt to activate their system using a valid product key, as there may be an issue with the Windows activation servers.  Failure to promptly fix this error code might result in other Windows 10 error messages, such as error code 0xc004f034.

Further Information and Manual Repair

To rectify the error code, Windows 10 users will need to perform manual repair procedures that fix the underlying problems causing error code 0xc004fc03. These procedures may include reconnecting to one’s network, checking your firewall settings, or activating your Windows operating system via phone. The manual repair methods are simple and do not require technical knowledge of the Windows operating system. If your attempts at manually repairing this error code fail, however, you may need to try a few other procedures.

Method One: Verify Internet Connection

To check your Internet connection, you’ll need to access the Network & Internet tab in Windows 10. Follow the instructions below to access this tab and fix Internet connectivity issues if they are preventing you from activating Windows on your machine.

  • Step one: Click the Start button and select Settings
  • Step two: Select Network & Internet
  • Step three: Click the Status section of the Network & Internet tab

If your status shows that you are not connected to a network, you will need to fix your connection. Simply use the Network Troubleshooter to troubleshoot your connection. You will be able to activate your copy of Windows once your connectivity issues are resolved.

If, however, the problem persists and error code 0xc004fc03 occurs during the activation process, this simply means that the existence of the error code is not due to connectivity or networking problems. In such a case, move to the next manual repair method listed below and follow the exact instructions given.

Method Two: Check Firewall Settings

Windows Firewall protects your PC from hackers, worms, and other malicious programs. However, in some cases, it may result in error codes like error code 0xc004fc03. If your firewall is interfering with the Windows 10 activation, you’ll be able to rectify the problem by simply adjusting your settings. Follow the steps below to check – and adjust if necessary – your Windows Firewall settings.

  • Step one: Click search bar and type firewall
  • Step two: Select Windows Firewall
  • Step three: Select Turn Windows Firewall on or off

In some cases, Windows users may not be able to adjust settings within the Windows Firewall tab, as your firewall settings may be controlled by a third party antivirus software. If this is the case, open the antivirus software and turn off the firewall if the software does not prevent you from making such changes to its settings.

Note, however, that you will need to readjust the settings as soon as you activate your version of Windows 10. This is due to the fact that turning off your firewall settings permanently may lead to exposure to worms and other malicious programs.

Method Three: Activate Windows by Phone

Activation of Windows via phone is another option for individuals experiencing error code 0xc004fc03. The activate by phone option in the Update & Security tab will be available once you fail to activate Windows 10. To complete this manual repair method, follow the steps below.

  • Step one: Select Settings
  • Step two: Click Update & security
  • Step three: Select Activate by phone
  • Step four: Follow the instructions provided thereafter.

This is one of the most effective ways to fix error code 0xc004fc03. If the issue persists, however, you can proceed to the last resort.

Method Four: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

Read More
Ventoy software review

There is a lot of software on the market today, but from time to time we discover something extraordinary and unique worth sharing and today we have a threat for you. Ventoy is a tool that will help you with system reinstallations and system maintenance once and for all.

If you are a computer user that has multiple operating systems or you are installing and maintaining different hardware via different OS there is a high chance that you have multiple USB sticks with different operating systems on them.

Now the problem with that is that there are probably too many unlabeled sticks around or you do not have enough so you keep making system USBs depending on which one you might need.

ventoy

Ventoy solves all of these problems by letting you have as many operating systems images as your USB has capacity. The only thing you need to do is get the software here: https://www.ventoy.net/en/index.html and make a USB with it, then you can freely just copy your ISO images onto the USB and once it is inserted into the computer you will be given a menu to choose which one you would like to start with, simple as that.

Features

  • 100% open source (license)
  • Very simple to use (Get started)
  • Fast (limited only by the speed of copying the iso file)
  • Can be installed in USB/Local Disk/SSD/NVMe/SD Card
  • Directly boot from ISO/WIM/IMG/VHD(x)/EFI files, no extraction needed
  • Support to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk Notes
  • No need to be continuous in disk for ISO/WIM/IMG/VHD(x)/EFI files
  • Both MBR and GPT partition styles are supported
  • x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI, MIPS64EL UEFI supported
  • IA32/x86_64 UEFI Secure Boot supported Notes
  • Linux Persistence supported Notes
  • Windows auto installation supported Notes
  • Linux auto installation supported Notes
  • Variables Expansion supported for Windows/Linux auto-installation script Notes
  • FAT32/exFAT/NTFS/UDF/XFS/Ext2(3)(4) supported for main partition
  • ISO files larger than 4GB supported
  • Menu alias, Menu tip message supported
  • Password protect supported
  • Native boot menu style for Legacy & UEFI
  • Most types of OS supported, 1000+ iso files tested
  • Linux vDisk(vhd/vdi/raw...) boot solution Notes
  • Not only boot but also complete the installation process
  • Menu dynamically switchable between ListView and TreeView mode Notes
  • "Ventoy Compatible" concept
  • Plugin Framework and GUI plugin configurator
  • Injection of files into runtime environment
  • Boot configuration file dynamically replacement
  • Highly customizable theme and menu style
  • USB drive write-protected support
  • USB normal use unaffected
  • Data nondestructive during a version upgrade
  • No need to update Ventoy when a new distro is released
Read More
Google docs crush with repeating a word

A newfound bug in Google docs is causing it to crush and upon reopening it will crush again making it very difficult to re-access your document. The bug is manifested when a series of the same word is typed into a document and Show grammar suggestion is turned on.

google doc bug

How was it found

A Google Docs user, Pat Needham brought up the issue on Google Docs Editors Help forum.

"I've only tried in Google Chrome, with documents from three separate Google accounts (personal, G Suite Basic, and work one which might be enterprise). All three experience this same issue".

"It's case-sensitive. So trying with 'and. and. And. and. And.' doesn't cause it to crash."

While Needham publicly reported the bug, it appears that the issue was discovered by Eliza Callahan who was writing a poem novel for her novel using Google Docs.

Needham's findings have also been confirmed by other users running Firefox 99.0.1

Another user, Sergii Dymchenko, said strings like "But. But. But. But. But." triggered the same response. Some also noticed putting any of the terms like "Also, Therefore, And, Anyway, But, Who, Why, Besides, However," in the same format achieved the outcome.

A YCombinator HackerNews reader suspected the cause to be the "Show grammar suggestion" option in Google Docs.

A Google spokesperson confirmed the presence of the issue adding, "we're aware of this issue and the team is working on a fix."

How to recover your document

First thing first, turn off Show grammar suggestions so you do not run into issue by accident. In order to turn it off go to Tools and then into Spelling and grammar and untick Show grammar suggestions.

Now, if you already have a document that has been crushed, fear not because there is a workaround to access it. For some strange reason this bug does not manifest on Google Docs mobile app, so you can open the crushed document in the mobile app, delete words that have caused the bug and reopen the document on your desktop.

Until Google comes up with the solution this is currently the only way to address the issue.

Read More
Fix Kernel Power Blue Screen in Windows
To function properly and as intended, Windows 10 depends on a number of resources and software components. Even with a simple task as powering the machine, there are already several smaller software components supporting it. However, if any of these resources or components experience issues, it will affect the overall function of the computer. One of the errors reported is the Kernel Power Blue Screen error which is triggered by the Windows Kernel that mostly comes with a Windows Kernel Event ID 41 error. This kind of error can turn off and reboot the computer randomly. Here’s an example of a Bugcheck code entry with the same event:
 “EventData BugcheckCode 159 BugcheckParameter1 0x3 BugcheckParameter2 0xfffffa80029c5060 BugcheckParameter3 0xfffff8000403d518 BugcheckParameter4 0xfffffa800208c010 SleepInProgress false PowerButtonTimestamp 0Converts to 0x9f (0x3, 0xfffffa80029c5060, 0xfffff8000403d518, 0xfffffa800208c010)”
This kind of BSOD error is caused by an issue with the Power Supply components in both the software and hardware parts of your computer. In such cases, if your computer is stuck in a reboot loop, you need to troubleshoot the problem via Safe Mode or in the Advanced Startup options screen.

Option 1 – Try disabling Overclocking

If you have enabled Overclocking, you might have to disable it as some users reported that the Kernel-Power Blue Screen error started to appear right after overclocking. To disable it, follow the steps below.
  • Go to the Start Menu and open Settings.
  • Next, select Update and Security and go to the Recover tab.
  • From there, click on Restart now in Advanced startup. This will restart your computer.
  • Once you’re in the Advanced startup, go to Troubleshoot and then select Advanced Options.
  • From there, select the UEFU Firmware Settings.
  • Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
  • From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
  • Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
  • Start your computer normally and check if the Kernel-Power Blue Screen error is now fixed.

Option 2 – Try to run the Power troubleshooter

The next thing you can do is to run the Power troubleshooter. To do so, follow these steps:
  • Go to Settings and navigate to Update & Security > Troubleshoot.
  • After that, look for the “Power” option from the given list of built-in troubleshooters and click on it.
  • Next, click on the “Run the troubleshooter” button to run the Power troubleshooter.
  • Once the troubleshooter is done identifying the problems, follow the next on-screen instructions to resolve the problem.
Note: You could also try to run the Blue Screen troubleshooter to fix the Kernel-Power BSOD error. You can find it under the same page as the Power troubleshooter.

Option 3 – Try to replace the Power Supply Unit

You could also try to consider physically replacing the Power Supply Unit or PSU of your computer and see if that helps or not.

Option 4 – Run the Windows Memory Diagnostic tool

Since this error could be caused by some issues in the memory, you can try running the Windows Memory Diagnostic tool and see if it helps.
  • Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 5 – Try to check physically check your RAM

In this option, you have to check your RAM physically especially if you tend to use multiple physical RAMs on your computer so it can be quite tricky and technical. You have to check first if they are of the same frequency and then verify if the chip is compatible or not. You also have to check if the sockets are attached using some adapter or non-recommended apparatus as it can cause some problems while giving performance hit to your computer.

Option 6 – Try to update the BIOS

Updating the BIOS can help you fix the Kernel-Power BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version on your computer.
  • Now restart your computer to apply the changes made.
Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Option 7 – Disable Fast Start-up

If you want your computer to boot faster, then you might have enabled Fast Start-up. This feature is ideal for computers that are using a hard disk drive. However, turning on this feature also means that when the computer boots, it might lag some drivers that are loaded when it initially boots up. Thus, it might be the potential cause of the Kernel-Power BSOD error. Thus, you need to disable Fast Start-up. To do that, follow these steps:
  • Boot your PC into Safe Mode.
  • Then tap the Win + R keys to open the Run dialog box.
  • Next, type in “control” to open Control Panel.
  • After that, select Hardware and Sound and click on Power Options.
  • Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
  • Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
  • Now restart your PC for the changes to take effect and then check if the problem’s fixed afterward.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status