If you suddenly encountered an error that says, “The Task image is corrupt or has been tampered with”, along with an error code of 0x80041321, read on as this post will guide you on what you can do to resolve this problem in your Windows 10 computer. According to security experts, this kind of error has something to do with a corrupt scheduled backup task wherein each time the task service plans to execute a task, it validates a few things. And if it finds any issue with the integrity or corruption in the registry, it will mark those tasks as corrupt and throws the error 0x80041321. There are several options you can check out to fix the problem. You can try using the Registry Editor to edit and fix the corrupted tasks or you could also delete the schedule keys or the WindowsBackup file, as well as try deleting the task from the Task Scheduler or refresh the User_Feed_Synchronization. But before you of these potential fixes, make sure that you check every option and verify if it’s not associated or trying to run a file which it should not. In addition, make sure that you create a System Restore point as well so that you can undo any changes you will be making if anything goes wrong. Once you have these things covered, refer to each one of the options provided below.

Option 1 – Try to use the Registry Editor to edit and fix corrupted tasks

The first thing you can do to fix the problem is to edit those tasks via Registry Editor, as well as fix the corrupted ones in System32. Before you proceed, keep in mind that since you are dealing with the Backup triggered by the Task Scheduler, you can find the entries for the tasks in different locations. You can find the Task Scheduler at Task Scheduler Library > Microsoft > Windows > Windows Backup, whereas, you can find it in this path in the Registry Editor, HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Schedule WindowsBackup AutomaticBackup. On the other hand, you can find the Windows System folder at C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup. You need to ensure that the name of the task name is the same as everywhere and take note of the name. Once you have these covered, follow the steps below.

• Tap the Win + R keys to open Run and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTreeMicrosoftWindowsWindowsBackup
• From there, take note of the GUID value in the ID entry of the task under the AutomaticBackup and Windows Backup Monitor folder.
• After that, you have to remove the task registry entries related to the ID from these locations
  • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
  • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
  • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• Once done, you have to create a temporary copy of the corrupted task file by going to this location: C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup
• From there, look for the AutomaticBackup and Windows Backup Monitor tasks and copy them to a location where you can keep them safe.
• Next, you have to fix the corrupted task by deleting it from this location: C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup
• After that, you have to recreate the task by going to Task Scheduler > Microsoft > Windows> Windows Backup.
• Now click on the Action menu and on Import task and navigate to the backup files and import them.
• Once you’ve created the tasks, run them manually and see if the error is now fixed.

Option 2 – Try to delete the Schedule keys in the Registry

• Launch the Registry Editor and go to this key: HKLMSOFTWAREMicrosoftWindows NTCurrent VersionSchedule
• From there, delete all of its sub-keys.
• Once done, exit the Registry Editor and check if the Backup Tasks are now working.

Option 3 – Try to remove the WindowsBackup file

The next thing you can do to fix the problem is to remove the WindowsBackup file if the first two options didn’t work. It is possible that the problem has something to do with corrupted Task files. The task files are XML files that include parameters, programs to use, and many more. If any of these files end up getting corrupted, the task scheduler will have trouble running it and will throw the “The Task image is corrupt or has been tampered with” error.

• To delete it, go to C:WindowsSystem32TasksMicrosoftWindowsWindowsBackup.
• From this location, get rid of all the files. You could also these files via Command Prompt using the DEL command.
• Once done, go to the Backup and Restore in the Control Panel and set up the Windows Backup again.

Option 4 – Try to delete the task from the Task Scheduler

If you don’t want to delete the files from Windows Explorer, you can delete them instead via Task Scheduler.

• Open the Task Scheduler and go to Task Schedule LibraryMicrosoftWindowsWindowsBackup.
• From there, delete both of the tasks and set up Windows Backup again.
• Once done, go to the Task Manager and run the AutomaticBackup task again and see if it works.

Option 5 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
• After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
• Click on the “RUN” option and select the “Restart the Service” option.
• And click on the “After Second Failure” option and then select the “Restart-Service” option again.
• Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
• Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 6 – Try refreshing the User_Feed_Synchronization

According to security experts, enabling and disabling the User Feed sync also known as the User_Feed_Synchronization task can help resolve the problem.

• Tap the Win + X keys and select the PowerShell (admin) option from the menu.
• Next, type the “msfeedssync disable” command and tap Enter.
• Repeat the same process but this time run the “msfeedssync enable” command.

If you have encountered the “Windows Cannot Find a System Image on This Computer” error while you are trying to restore a system image, then read on as this post will guide you in resolving this problem. A system image is basically a backup of your whole data in the system. For instance, it can be the backup data of your hard disk or the whole hard disk itself, or one of the volumes. This is really useful in some cases like when you are not able to get back into your system for some reason or when your system has been corrupted. In such cases, you can utilize this feature and get going safe and sound. However, not all things go the way as expected like when you make a system image of a drive for instance, or use that backup to restore data and you suddenly encounter the “Windows Cannot Find a System Image on This Computer” error. This kind of error occurs due to a number of reasons but worry not for your data is safe and you can fix this error easily. This error is most likely triggered by changing the name of the “WindowsImageBackup” folder. Renaming this folder will certainly be an issue since it is the one that stores all your data. Aside from renaming the WindowsImageBackup folder, renaming the sub-folders can also cause this error which means that renaming the sub-folders of the WindowsImageBackup folder can trigger the error. To fix this error, here are some suggestions that might help:

Option 1 – Try putting the WindowsImageBackup folder in the Root directory

Windows will have issues finding the WindowsImageBackup folder if it isn’t in the root directory of the drive so if it is not there, the “Windows Cannot Find a System Image on This Computer” error will pop up. When a folder is in a root directory, it means that it shouldn’t be stored within a folder but in the main directory instead.  Thus, you need to put the WindowsImageBackup folder in the root directory to fix the error.

Option 2 – Don’t add any sub-folders in the WindowsImageBackup folder

Another cause of the error is when you add sub-folders in the WindowsImage Backup folder. Adding any sub-folders in this folder will only trigger the error so you should leave the folder as it is and you must not make any modifications to it. So if you have added sub-folders in it, make sure to remove them right away.

Option 3 – Make sure that there is one system image per USB drive

The error can also appear if you’ve stored multiple images inside a single USB drive as it could confuse Windows and will trigger the “Windows Cannot Find a System Image on This Computer” error. Note that storing system images of different volumes of your hard disk in a single USB will prevent you from restoring your data.

Option 4 – Try renaming the System Image folder

If you’ve just changed the name of the System Image folder after you store it on a USB stick or other external device, then it’s no wonder why you’re getting the “Windows Cannot Find a System Image on This Computer” error. Windows search for the default name, “WindowsImage Backup” folder when restoring your data so if it is not able to find it, it throws up this error instead. To fix the error, you need to change the folder back to its default name which is “WindowsImageBackup”.

Option 5 – Check the WindowsImageBackup sub-folders

As mentioned earlier, renaming sub-folders in the WindowsImageBackup folder can trigger the error so if you have renamed sub-folders in this folder, you need to change them back to their default names so that you can restore your data peacefully.

If you were trying to install a program on your Windows 10 computer but encounter an error instead that says, “Error 1310, Error writing to file: <PATH>, Verify that you have access to that directory” then read on as this post will guide you on how you can fix it. This kind is a fairly common type of error encountered by many Windows users. You can get this error when you try to install certain programs like Excel, AutoCAD, Adobe Photoshop, and some other Adobe products on Windows. One of the most likely causes for this error is that the required files or location is already used by some other software which means that Windows finds that you are trying to overwrite a software that is already installed. Aside from that, it could also occur if the program installer does not have access to write to that directory. To fix Error 1310, here are some potential fixes that could help.

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 Clean Now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix Error 1310.

Option 2 – Reinstall the program in a Clean Boot State

You can also troubleshoot Error 1310 in a Clean Boot state. It could be that there are some third-party applications in your computer that's preventing the program from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the program again.

Option 3 – Try to unregister and re-register the Windows Installer Module

• Tap the Win + R keys to open the Run dialog box.
• Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
• Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
• Now restart your computer and see if un-registering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Take ownership of the location where you want to install the app

The next thing you can try to do is to take ownership of the particular folder as this worked for some users who experienced the same problem. But before you do that, you have to create a System Restore Point first, once that’s done, proceed to the given steps below.

• First, locate the concerned folder and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.
• Finally, try to install the application again.

There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error. There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:

• Open any Office app.
• Then click on File and look for your name located in the top-right portion.
• Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.

• Open Windows settings and click the Apps and Features option.
• Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
• This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.

Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.

Operating systems now give users a feature that allows them to create separate partitions out of HDD or SSD-based storage in order to store data in an organized manner. This small yet powerful feature has always been supported by Microsoft. However, there are times when users might fill up on some particular very soon. This may result in the lack of space for that partition which makes the entire process of using PCs slower since there is a large chunk of files that has to be indexed in a smaller partition. If you are one of the users experiencing this dilemma, you need to either delete the other partitions to allocate their storage to the partition that is short on storage or simply recreate the partition so that all the useless data will be deleted and you can start afresh with the overflowing partition. In this post, you will be guided on how you can delete any storage partition from your Windows 10 PC via Disk Management, Command Prompt as well as Windows PowerShell.

Option 1 – Delete storage partition via Disk Management

This is one of the simplest ways you can use to delete a storage partition. Go to the WinX Menu and from there, open Disk Management and then select the Drive you want to get rid of, right-click on it and then select Delete Volume.

Option 2 – Delete storage partition via Command Prompt

• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also type in “cmd” in the Cortana search box and right-click on the Command Prompt icon and then select the “Run as Administrator” option from the context menu.
• Once you have Command Prompt pulled up as admin, type in and enter this command – diskpart
• After entering this command, the Diskpart Utility will start. Diskpart Utility is a command line-based utility just like Command Prompt but it will get a UAC Prompt after you invoke it so you have to click Yes for the UAC Prompt.
• After that, type in list volume and tap Enter to see the list of all the partitions created on your PC. This includes both types of partitions that are visible to a normal user in the File Explorer as well as the ones that are created by Windows 10 by default which helps it in storing the boot files and other essential system files.
• You should see a list of all the partitions made on your computer. Select the partition you want to delete by its Unique Identification number as Volume X where X denotes the Unique Identification Number.
• Next, type in the select volume number command and hit Enter to select the desired volume.
• Then delete the volume you’ve selected and type in the delete volume command and hit Enter to delete the volume you just selected and convert it into unallocated space.

Option 3 – Delete storage partition via Windows PowerShell

• Start by tapping the Win + X keys or simply right click on the Start button and select Windows PowerShell (Admin) or you could also type in “windows powershell” in the Cortana search box and right-click on the Windows PowerShell icon and select the “Run as administrator” option.
• Once you’ve opened the Windows PowerShell, type in the Get-Volume command and hit Enter to get a list of all the partitions on your PC.
• Next, select the drive letter you want to delete and then type in the Remove-Partition –DriveLetter command and hit Enter to delete the selected partition. Note that you need to replace the drive letter with the letter of the partition you want to get rid of.
• After that, it will ask you for confirmation. Just hit the Y key for Yes or hit the A key to say Yes to All. This will delete all the partition you’ve selected and will move them in as unallocated space.

And that’s how you delete a Drive Partition or Volume in Windows 10. Note that you should only follow the last two options given in case the Disk Management is not able to fulfill the user requirements.

Repair Error 2032

What is Error 2032?

Error 2032 is a Windows stream error. The error is generated when running applications like Flash. It shows that the application is unable to request ads from server.

Error Causes

The error 2032 is triggered due to multiple reasons including:

• The URL cannot be located or is blocked
• HTTP Service is not found
• Incorrect proxy settings
• Automatic cookies handling
• Corrupt Flash Player
• Viral infection
• Registry issues

Further Information and Manual Repair

Here are some easy and best do it yourself methods to resolve the error 2032 on your system:

Fix the Proxy Settings

To do this, first, go to the start menu and press RUN, type regedit in the RUN box and press enter. Now from the left-hand panel of the registry path open: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings. Now double click the proxyenable string and replace its value with 0. After that, right-click on proxy server and select delete option. Then exit Regedit and restart your PC to activate changes.

Verify the URL

Sometimes the error 2032 may be generated due to wrong or incorrect URL in the HTTP Service URL property. So, verify your URL and look for typos. Specifying the correct URL can fix the error right away.

Check Cookies Handling

Automatic cookies handling can also trigger this error code. Therefore, to resolve the error, it is advisable to disable automatic cookies handling. This can be done by launching your web browser. Go to tools and then press the privacy tab. Now click on the advance tab from settings and un-check override automatic cookie handling. To confirm changes press OK.

Uninstall and then Reinstall the Flash Player

It is possible your Flash Player is corrupt. Therefore, another way to fix error 2032 is to uninstall the Flash Player and then reinstall it on your system.

Scan for Viruses

Programs usually get corrupted due to two reasons, viruses or registry issues. Therefore, to remove viruses on your PC, download and run an antivirus program.

Clean and Restore Registry

Also, clean the registry. Congratulations, you have just fixed Error 2032 in Windows 10 all by yourself. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily. Now that’s how you fix Error 2032 in Windows 10 on a computer. On the other hand, if your computer is going through some system-related issues that have to get fixed, there is a one-click solution known as Restoro you could check out to resolve them. This program is a useful tool that could repair corrupted registries and optimize your PC’s overall performance. Aside from that, it also cleans out your computer for any junk or corrupted files that help you eliminate any unwanted files from your system. This is basically a solution that’s within your grasp with just a click. It’s easy to use as it is user-friendly. For a complete set of instructions in downloading and using it, refer to the steps below Perform a full system scan using Restoro. To do so, follow the instructions below.

1. 1. 1. Download and install Restoro from the official site.
      2. Once the installation process is completed, run Restoro to perform a full system scan.
      3. After the scan is completed click the “Start Repair” button.

If you are using Windows PowerShell and it suddenly throws an error message saying, “File cannot be loaded because running scripts is disabled on this system”, then read on as this post will guide you on how you can fix this issue your Windows 10 computer. This kind of error in PowerShell is most likely due to the fact that your user account does not have the required permissions to execute the script. Although this does not mean that you need to have administrator-level permissions as it could also indicate that you have to be unrestricted to run these types of PowerShell scripts or cmdlets. Thus, to fix the error and carry out the task, you have to set the execution policy to be unrestricted. And to do that, you need to use the steps provided below as a reference. Step 1: To get started, you have to check what policies are set for the individual user groups on your computer by tapping the Win + X key combination or by right-clicking on the Start button and clicking on Windows PowerShell (Admin). You can also search for PowerShell in the Start Search and then right-click on Windows PowerShell and select Run as administrator. Step 2: If a User Account Control or UAC prompt appears, just click Yes to proceed. Once you’ve pulled up Windows PowerShell, type the following command to get the List of Execution Policy for all the scopes on your computer.

Get-ExecutionPolicy –List

Step 3: After you execute the command, it will give you a list of the User Groups as well as their Execution Policy status, and under the Scope column, look for “LocalMachine”. Once you find its Execution Policy you will notice that it’s either set to Undefined or Restricted. Step 4: Now that you’ve determined the Execution Policy, you need to set it to Unrestricted if it is set to Restricted. To do that, you have to enter the following command in the very same PowerShell window.

Set-ExecutionPolicy Unrestricted

Step 5: After you execute the command, you will see a message that asks for various permissions for which you either have to tap Y to say Yes to each one of the messages individually or tap the A key to say Yes to all the messages to once. However, if the command throws another error, you can just force the Execution Policy to change by executing the following command.

Set-ExecutionPolicy Unrestricted -Force

Step 6: Once you’re done, it will finally set the Execution Policy for the Windows PowerShell scripts as well as cmdlets to be Unrestricted and fix the “File cannot be loaded because running scripts is disabled on this system” error.

The solution to Error Code 36

Error Code 36 – What is it?

This is a common Device Manager Error Code that users encounter. It is commonly found on all Windows 2000 and later versions of Windows operating systems. Error Code 36 is usually prompted by the following message:

"This device is requesting a PCI interrupt but is configured for an ISA interrupt (or vice versa). Please use the computer's system setup program to reconfigure the interrupt for this device. (Code 36)"

Solution

Error Causes

Error Code 36 occurs when there is a failure in IRQ translation due to your Windows operating system getting corrupted. This is caused due to a number of triggers, such as:

• An excess of startup entries
• Errors in registries
• RAM or hardware failure
• Excessive unnecessary installed programs
• Malware or spyware

When programs are removed excessively, some programs are not removed completely and create problems in your computer’s registry.

Also, due to the presence of malware and spyware and other causes mentioned above, your computer registry builds up errors with the time that leads to slowing your PC, time lags, and even result in crashes and freezes.

Error Code 36 can cause internal and external components to malfunction or experience time lags such as DVD drive or printer and hence can severely affect your entire PC.

Further Information and Manual Repair

Error Code 36 is a severe PC error and any attempt at fixing the error must be approached with extreme caution for your PC to start functioning properly again. Here are two methods to fixing your PC.

Method 1 – Change IRQ reservation settings

Changing the IRQ reservation settings is the best way you can rely on to fix the error code. You can do this by changing the BIOS settings of your PC.

The BIOS stands for ‘Basic Input/Output System’ and is the program of your PC’s microprocessor that allows your PC to boot after you switch it on.

Caution needs to be exercised before changing the BIOS settings of your PC. This is because every PC’s BIOS version differs from another and any wrong attempt to change the settings may make matters worse.

It is therefore recommended to refer to hardware documentation that you received with your PC or motherboard and check for the model number and details of your PC’s motherboard.

Only after you have checked and confirmed all the details, should you use the specific BIOS settings required to configure your IRQ reservations?

Method 2 – Install DriverFIX

Error Code 36 isn’t an easy error to remove.

While changing the BIOS settings can work to restore your PC, it may create a whole lot of inconvenience for finding the time and effort to check the hardware documentation details and attempting to change the specific settings and especially, if your PC does not support the options to change IRQ reservations.

Given the high risks of fixing such an error, you can also install software that enables you to fix your slow PC at the click of a few buttons.

Programs such as DriverFIX can enable you to download and replace your outdated drivers with new updated ones without you having to look for them. It will detect which drivers to download based on your PC’s motherboard version from the program’s database and can get rid of error code 36.

Click here to download DriverFIX and remove error code 36 and any other type of Device Manager error from your PC.

KMODE_EXCEPTION_NOT_HANDLED seems to be connected primarily to a third-party driver, e1d65x64.sys associated with the Intel(R) Gigabit adapter, NIC/Wired network NDIS (Network Driver Interface Specification) 6.x driver. Error is known to produce the dreaded blue screen of death or BSOD. Most usually error is connected with gaming on Windows 10 computer and it manifests itself during gaming sessions. If you are unlucky and you are faced with this unfortunate error we will be happy to try to help you and present with tips and tricks in order for you to find a solution for it. Before you proceed with the provided solutions, be sure you have sufficient disk space on the Windows drive, run Disk Cleanup and then run CHKDSK.

1) Run the Blue Screen Online Troubleshooter

Open Control Panel, change the view setting to icons. Click Troubleshooting, and click “View all” in the tasks pane. Click “Blue Screen”. This opens the Blue Screen Troubleshooter.

2) Run Driver Verifier

1. Start a Command Prompt window by selecting Run as an administrator, and type verifier to open Driver Verifier Manager.
2. Select Create standard settings (the default task), and select Next. You can also choose to Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
3. Under Select what drivers to verify, choose one of the selection schemes described in the following table.

   Driver verifier table:

   Option	Recommended use
   Automatically select unsigned drivers	Useful for testing on computers that are running versions of Windows that do not require signed drivers.
   Automatically select drivers built for older versions of Windows	Useful for testing driver compatibility with newer versions of Windows.
   Automatically select all drivers installed on this computer	Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system. This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
   Select driver names from a list	In most cases, you will want to specify which drivers to test. Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.

4. If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
5. Select Finish, and then restart the computer.

3) Update network device drivers

Go to the official Intel website and try to find newer versions of drivers, if there are none perhaps you will need to revert back to the previous version.

4) Scan memory for issues

Run a memory test on your system, sometimes these errors can be traced back to a faulty RAM bank.

5) Stop over-clocking your PC

If you have overclocked your PC please reverse it back to its original state and see if that would solve the issue

6) Perform System Restore to the previous restore point

If none of the previous solutions have bared fruit, roll back to a previous restore point and that should solve the issue.

Computer upgrades are the most common and most efficient ones. RAM upgrade is one of the easiest ones you can do and the most common ones but even as simple an upgrade as this one can cause certain issues. If you are experiencing error 0164, memory size decreased after RAM upgrade we are offering you solutions on how to fix this particular error and get your computer back in working order.

1. Change BIOS settings

   Enter your motherboard BIOS (usually by pressing the del key on startup) Load BIOS defaults Save changes and exit If the Error 0164: Memory size decreased issue persists even after loading setup defaults, then it must be configured manually inside the BIOS.

2. Clear CMOS

   Follow the instructions precisely:
   • Turn off all peripheral devices connected to the computer.
   • Disconnect the power cord from the AC power source.
   • Remove the computer cover.
   • Find the battery on the board. The battery may be in a horizontal or vertical battery holder or connected to an onboard header with a wire.
   If the battery is in a holder, note the orientation of the + and – on the battery. With a medium flat-blade screwdriver, gently pry the battery-free from its connector. If the battery is connected to an onboard header with a wire, disconnect the wire from the onboard header.
   • Wait one hour, then reconnect the battery.
   • Put the computer cover back on.
   • Plug the computer and all devices back in.
   • Power on the computer.