How to Fix the Error 103

This post will guide you in fixing high CPU, Memory, and Disk usage problems caused by NTOSKRNL.exe. NTOSKRNL stands for “NT Operating System Kernel. This file is a kernel image that is responsible for a lot of systems-based processes such as Hardware Virtualization, Process, and Memory. Aside from that, it is also the one that compresses the old pages of memory that reduces the overall amount of memory being used. If you notice that your computer is running slowly and you find that the NTOSKRNL.exe file is hogging your resources such as disk usage, CPU usage as well as memory usage, then read on as this post will guide you in fixing the problem caused by NTOSKRNL.exe. Make use of the options given below to resolve the issues caused by NTOSKRNL.exe. 1] Scan your computer for potential malware There might be a good chance that your computer might be infected with malware. And this malware might be associated with the NTOSKRNL.exe file and hence making it consume a lot of system resources. So, I would really recommend you to make sure that your Antivirus is up to date and then scan your computer with it specifically the C:/Windows/System32 folder because this is the location where the NTOSKRNL.exe file is located.

Option 1 – Put your computer in a Clean Boot State

The first thing you have to do is to put your computer in a Clean Boot State as this can help you in finding any incompatible programs that are causing the problem.

• 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.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

Option 2 – Update or rollback drivers

If the first option 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 3 – Try to run the DISM tool

If the first two options didn’t work, then running the Deployment Imaging and Servicing Management might. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 4 – Try to stop the Runtime Broker process

The RuntimeBroker.exe or the Runtime Broker process is the one that monitors access to Windows APIs to make sure that the apps do not violate the core security of Windows. This process usually leaves a very small footprint. However, there are times when it consumes more resources than it’s supposed to and does not release memory after the work is done that results in a memory leak. As a result, it affects NTOSKRNL.exe which is why you have to stop the Runtime Broker process. To do so, refer to these steps:

• Tap the Ctrl + Shift + Esc to open the Task Manager.
• After opening Task Manager, go to the Processes tab and look for the Runtime Broker process.
• Once you find it, check if it is using more than 15% of your memory. If it is, then you most likely have an issue with an app installed on your computer.
• Select the Runtime Broker process and right-click on it and then click on the End Task option to end its process.

Option 5 – Try to run the Performance Troubleshooter

• Tap the Win + R keys to open the Run dialog box.
• Type “msdt.exe /id PerformanceDiagnostic” in the field and hit Enter to open the Performance troubleshooter.
• Then click on Next to get started. Wait until the process is completed.

Option 6 – Try using the Windows Performance Toolkit

You can also use the Windows Performance Toolkit in finding the root cause of the problem. Just refer to the following steps to use this toolkit.

• Search for “cmd” in the Cortana Search box and click on Command Prompt from the search results to open it.
• Next, type in the command given below or copy and paste it and then hit Enter:

xperf -on latency -stackwalk profile -buffersize 1024 -MaxFile 256 -FileMode Circular && timeout -1 && xperf -d cpuusage.etl

• After executing the command, wait for at least 60 seconds and then check the logs of the Windows Performance toolkit which is stored in a file named cpuusage.etl in the folder located at C:/Windows/System32. From there, you should see a list of all the causes of the System Resources being hogged.

Windows photo viewer was a popular photo viewing application integrated into Windows 7, 8, and 8.1 but in Windows 10 it has been replaced with photos, Microsoft's new application aimed at photo viewing on your desktop. Now if any one of you wonders why should be bringing the old application back to Windows 10 since we have an alternative one, the answer would be resources and speed. The old photo viewer application is lightweight, fast, and reliable, opening the same photo in both photo viewer and in new photos shows us that Microsofts new viewer application takes even three times more RAM, and it's visibly slower in loading times for pictures. Since I am a person who prefers speed and functionality over fancy looks I would be very glad to have the option to bring back a photo viewer. If you have by any chance Windows 10 as an upgrade, bringing back photo viewer is easy as 1,2,3. you just need to open settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done. Sadly if Windows 10 has been installed clean on the system and not as upgrade things are a little bit more complicated but do not worry, stay with us, keep reading and you will get there.

Activating photo viewer

How technically photo viewer is still in the system but not used we will have to make it available again and this we will do by adding some lines in the Windows registry, that being said, open a notepad and paste the following code as it is in it.

---

Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\jpegfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\pngfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open] "MuiVerb"="@photoviewer.dll,-3043" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,36,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-70" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print] "NeverDefault"="" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget] "Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-83" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-71" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\DefaultIcon] @="%SystemRoot%\\System32\\wmphoto.dll,-400" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\DropTarget] "{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities] "ApplicationDescription"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3069" "ApplicationName"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3009" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities\FileAssociations] ".cr2"="PhotoViewer.FileAssoc.Tiff" ".jpg"="PhotoViewer.FileAssoc.Jpeg" ".wdp"="PhotoViewer.FileAssoc.Wdp" ".jfif"="PhotoViewer.FileAssoc.JFIF" ".dib"="PhotoViewer.FileAssoc.Bitmap" ".png"="PhotoViewer.FileAssoc.Png" ".jxr"="PhotoViewer.FileAssoc.Wdp" ".bmp"="PhotoViewer.FileAssoc.Bitmap" ".jpe"="PhotoViewer.FileAssoc.Jpeg" ".jpeg"="PhotoViewer.FileAssoc.Jpeg" ".gif"="PhotoViewer.FileAssoc.Gif" ".tif"="PhotoViewer.FileAssoc.Tiff" ".tiff"="PhotoViewer.FileAssoc.Tiff"

---

Yup, that is a lot of keys and settings but you are almost done. Once you have pasted text into your new notepad document save it but as .REG, you can name it however you want but it has to be .REG extension. Once the file is saved double click on it to merge it into the Windows registry. You might need to turn off UAC for this operation (check our tutorial on this topic) and accept warning messages but once it is done you should now have an old photo viewer as a choice for your default viewing application. All you have to do now is to go to settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done.

Error Code 0x800CCC0E - What is it?

The error code 0x800CCC0E is an Outlook error that appears while using either Microsoft Outlook or Outlook Express. The error message hampers your ability to send and receive emails.

Solution

Error Causes

0x800CCC0E Outlook error code is triggered by multiple reasons including:

• Improper connection with SMTP (Simple Mail Transfer Protocol) server
• Damaged files
• Registry corruption

In most cases, it’s the registry that gets corrupted which leads to the occurrence of 0x800CCC0E error code display. This typically happens when you try to update your Outlook/Outlook Express version. When updating, you need to remove all the software files of the previous Outlook version which includes the registry too. If the files are not removed from the registry, the new version update will often fail. The junk files of the old version are likely to damage and corrupt the registry.

Further Information and Manual Repair

It is advisable to repair the error code 0x800CC0E right away to avoid inconvenience and system failure and fatal crashes which can lead to valuable data loss.

Cause: Improper connection with SMTP (Simple Mail Transfer Protocol) server

Solution: If the cause of the 0x800CCC0E is SMTP server connection failure, then the best way to resolve the error is to reconfigure your email account settings. Make sure that port 25 is being used in the SMTP area. Port 25 is the standard outgoing mail port. If the SMTP setting is on port 25 then another reason for the error 0x800CCC0E can be your anti-virus or firewall software enabled on your PC. Turn it off for a moment and then try sending emails from your Outlook.

Cause: Damaged Files and Registry Corruption

Solution: If the error code is triggered due to registry corruption and file damage, then the best way to resolve it is to download Restoro. Restoro is a safe, efficient, and highly functional inbox cleaner and a system optimizer embedded with numerous powerful utilities designed to repair multiple PC-related errors including the error code 0x800CCC0E when triggered by registry corruption. This cutting inbox cleaner scans your PC entirely and detects all the unnecessary and malicious files saved in your system’s registry like junk files, internet history, invalid entries, and files of the uninstalled programs. These files take up most of the registry disk space thus causing the registry files to get damaged and corrupt and triggering error codes like 0x800CCC0E. With the help of Restoro,  you can easily wipe out all such files from your system in just one click. After scanning for errors all you need to do is click the repair tab to make your registry disk clutter-free. Once the clutter is removed, update the new version of the Outlook/ Outlook Express again on your system and then try sending emails. You’ll see two noticeable differences after repairing your PC with Restoro. One is that you will be able to install the new version and send emails smoothly from your Outlook account without any 0x800CCC0E error pop-ups. And the second difference you’ll see is the change in your PC performance. This tool optimizing your PC speed and reduces boot time. This tool is very simple and easy to use. It has a neat design layout and a user-friendly interface which makes it easy for all levels of users to use Restoro smoothly with zero complexity. In just a few clicks the error message 0x800CCC0E is resolved. What makes this tool a favorite among users is that it does not require any skills or technical know-how. To get started here’s what you need to do:

1. Click here to download Restoro software on your PC
2. Once the download is complete, run it to scan for 0x800CC0E error
3. After the scanning is successfully complete, click on the Repair button to fix the error right away.
4. Then install the new version of Outlook/ Outlook Express again on your system

Magcore.dll Error - What is it?

Magcore.dll is a type of Dynamic Link Library. This file is associated with software developed by ArcSoft, a renowned multimedia application developer. Magcore.dll consists of small programs that help load and run software developed by ArcSoft on your system smoothly. This file virtually comes into function when you use certain audio and video features incorporated in ArcSoft programs for example ArcSoft Media converter. However, you may experience Magcore.dll error code on when this DLL file fails to run and load programs. The error may hamper your ability to access ArcSoft programs on your system and cause you a great deal of inconvenience. Magcore.dll error is often displayed in any one of the following formats:

“The file magcore.dll is missing” “MagCore.dll cannot be found” "Cannot find [PATH]magcore.dll" “This application has failed to start because MagCore.dll was not found. Reinstalling the application may fix the error.”

Solution

Error Causes

This DLL file is known to be prone to errors. MagCore.dll error occurs due to several reasons such as:

• Missing or damaged MagCore.dll file
• Hardware failure
• Viral infection
• Registry issues

If you experience MagCore.dll error on your system, it is advisable to fix it right away. Though it is not fatal, but if you don’t repair it, you may not be able to access practically all ArcSoft programs on your PC.

Further Information and Manual Repair

Here are some of the efficient and easy manual methods to resolve error MagCore.dll on your PC:

Method 1 - Scan and Remove Malware

MagCore.dll error can be triggered by viral or other malware infection. Malware can easily damage DLL files and masquerade as the MagCore.dll file. To resolve, simply download a powerful antivirus on your system. Run it to scan your entire PC for viruses and remove them right away.

Method 2 - Update the Drivers for Hardware Devices

As we mentioned above the error may be related to hardware failure too. In times like these, it is advisable to update the drivers for hardware devices. For example if you try to play a 3D video game and it fails to run showing you MagCore.dll error message, then simply try updating the drivers for your video card. Drivers can be updated in Windows by using a driver update wizard from within Device Manager.

Method 3 - Use System Restore to Undo Recent System Changes

After trying method 1 and 2, if the error code still persists, then it is opt for method 3. Use Windows System Restore utility to undo recent system changes and bring your PC to its normal previous condition before the error occurred. To restore, simply go to the start menu, type System Restore. Now click on System Restore and just pick a point in the past called a restore point to return important Windows files and settings.

Method 4 - Repair the Registry

If the underlying cause of the MagCore.dll error code is related to registry issues, then simply repair the registry. You can fix it manually but it is a little complicated and time-consuming. You may find it difficult if you are not a technical whiz. Nonetheless to resolve and repair it in seconds, download Restoro. This is a powerful and a user-friendly PC Fixer embedded with a registry cleaner and several other highly functional scanners. Run it to scan your entire PC for registry problems. The registry cleaner utility removes all bad and invalid entries, cleans up the registry space, and repairs the damaged files. Click here to download Restoro and repair MagCore.dll error code on your PC.

Microsoft Edge may be about to win a lot of fans by introducing a new feature that it says could prevent one of the most annoying things about being online. A new update to the browser suggests it is looking at a way to block auto-playing videos by default when a user navigates to a website. People spotted a new entry to the Microsoft Edge Canary browser where the company tries out its in-progress updates, that suggests auto-playing videos may have had their day at last. The new addition, for Mac, Windows, and Linux systems, is called “Autoplay Limit Default Setting”, with the description suggesting that Microsoft Edge would set the media autoplay setting to "Limit" as a default - stopping videos from starting up when a user lands on a website. Currently, Edge offers two options for users to control media autoplay - "Allow" (the current default setting), where all videos on a website will play automatically with sound, and "Limit", where media won’t be autoplayed on sites that a user has previously visited. It appears that Microsoft is looking to test the feature in Canary before rolling it out to a wider user base - as blocking autoplaying videos can cause issues for some websites. The same Canary entry also hints at a future "Block" option, which would presumably stop any videos or media from playing when a user lands on a website. However, this feature, which is also listed as being available for Mac, Windows, and Linux systems, doesn't appear to be enabled as yet. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

If you got an error message saying, “Folder Redirection Failed, Failed to build the list of regular subfolders, Access is Denied” after you configured a new Group Policy Object or GPO which redirects User folders to a new network share or when you click on Reset default location under the Windows File Explorer or Folder Options, then you’ve come to the right place as this post will show you how to resolve this kind of error on your Windows 10 computer. Follow the given options below carefully to fix the “Folder Redirection Failed” error.

Option 1 – Take Ownership of the folder

If you are not able to access the folder could be one of the reasons why you’re getting the “Folder Redirection Failed” error and so you need to take ownership of the folder to resolve the problem. Before you proceed, make sure that your account is an admin account.

• 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.

Option 2 – Try to add Authenticated Users or Domain Computers

Make sure that the Folder Redirection group policy removal option is set to “Redirect the folder back to the user profile location when the policy is removed” when using the Folder Redirection. After that, you have to add Authenticated Users group with the “Read” permissions on the Group Policy Objects or GPOs. And if the Domain computers are part of the group of “Authenticated Users”. Note that by default, the “Authenticated Users” have these permissions on any new Group Policy Objects or GPOs. Once again, you have to add just “Read” permissions and not “Apply Group Policy” for “Authenticated Users”. Furthermore, to fix the “Failed to build the list of regular subfolders” errors, here are some options that could help.

Option a – Try to clear disk space

You might have to check if your disk is running out of space because if it is, then it will fail to create a list abruptly. And so you need to free up some disk space. You can either check on the files manually especially if you tend to keep your files at random places in your disk drive.

Option b – Find the Target route

You need to find the target route of the folder and then restore it if you are getting the “Failed to build the list of regular subdirectories” when you try to relocate the folder to the original location.

Option c – Try to change Ownership/Reset Defaults for all the User folders

If the “Failed to build the list of regular subdirectories” error pops up when you are trying to move a large number of files from one location to another, then you need to change the ownership of the folders as pointed out earlier.

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. 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 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

Error Code 0x80060100

Error Code 0x80060100 is an error that relates to the Windows Update process. It most commonly occurs when the Update process runs and cannot be completed, as the system appears to have necessary files corrupted or absent.

Common symptoms include:

• Inability to begin the Windows Update process
• Inability to complete the Windows Update process

While it can be frustrating when users are not able to complete their necessary updates for Windows 10, there are several solutions that are available to fix the problem at hand. Some of the methods that can be used are simple and accessible, even for beginners, while advanced methods of resolution are also available for users who are more confident in their abilities.

Error Code 0x80060100 appears on Windows 10 and earlier versions of the Windows operating systems. In most cases, the steps to resolve the problem remain the same, regardless of the system on which the error appears. This error code is also related to Error Code 0x800b0100, which appears in similar circumstances.

If the solutions below are not successful in resolving Error Code 0x80060100 on your machine, you may need to get in touch with a qualified repair technician who can assist you in the resolution of the issue at hand. Any repair technician used should be familiar with the needs of the Windows 10 update process.

Solution

Error Causes

The primary cause for the appearance of Error Code 0x80060100 on a Windows machine is that the Update files have had damage to them or are found to have elements missing that are necessary for the completion of the Update process.

Further Information and Manual Repair

If Error Code 0x80060100 has appeared on your Windows operating system as you are attempting to download, install, or run Windows Update, there are several steps that you can take to attempt to resolve the error. Some of these methods require advanced knowledge or skills, so if you are not confident in your ability to undertake the steps below, contact a qualified Windows repair technician to assist you in the process.

Here are the best ways to resolve Error Code 0x80060100:

Method One: Run the Troubleshooter for Windows Update

As you attempt to run the Windows Update process and experience difficulty, there is a tool that will usually appear on the screen called the Windows Update Troubleshooter. This process can scan the files being used for the update process and attempt to fix the errors on its own, retrieving or repairing any damaged files as it comes across them.

In most cases, this step on its own will resolve Error Code 0x80060100 on a computer. However, if you are still unable to run Windows Update after using the Troubleshooter, you may need to run a disk repair tool before proceeding.

Method Two: Restart Your Computer

In some cases, Error Code 0x80060100 can be resolved simply by restarting the computer that is affected by the error. Even if this step is not successful on its own, restarting after each of the other methods can allow necessary changes to take place and refresh the progress of the Windows Update process.

Method Three: Use the DISM Tool

This method requires some skill and knowledge of your operating system. To use this tool, follow the steps below:

• Step One: From the right side of the screen, use your mouse to swipe inward and select the “Search” option.
• Step Two: When the search box appears, enter in the words “command prompt".
• Step Three: From the results that appear, right-click on the “Command Prompt” option, then choose the option to “Run as Administrator.” An administrator password may be required at this point.
• Step Four: In the window that comes up, enter in the following words, hitting the “Enter” key after each:
  • Dism.exe /online /cleanup-image /scanhealth
  • Dism.exe /online /cleanup-image /restorehealth
• Step Five: Type in “exit” to close the prompt window and hit the Enter key.
• Step Six: Attempt to run the Windows 10 Update process again, restarting your computer as needed beforehand.

If the methods above are not successful in the resolution of Error Code 0x80060100, a qualified Windows repair technician may be able to assist you.

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

If you receive the error code 0xc000014C while you boot up your computer, then this post might be of help. This kind of error usually points to the Registry of your computer that might be corrupted. As a result, the operating system was not able to read the BCD file and throws the 0xc000014C error. The error code 0xc000014C is triggered when your computer encounters an error in the first booting sector. You might receive any of these error messages:

“Info: An error occurred while attempting to read the boot configuration data.” with File: as “BootBCD” “File: Windowssystem32configsystem Info: Windows failed to load because the system registry file is missing or is corrupt” “Info: The Boot Configuration Data for your PC is missing or contains errors.”

To fix the error code 0xc000014C when booting your computer, you can check out the suggestions provided below.

Option 1 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.

Option 2 – Try to rebuild the BCD files

You can also try rebuilding the BCD files to resolve error 0xc000014C for corrupted Boot Configuration Data

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 3 – Try restoring the default and uncorrupt Registry Values

This option is a bit tricky as you have to be sure about what you are doing here. However, if you are not sure, you might want to seek out a technician to fix the problem for you. But if you can handle it, then carefully follow the steps below.

• You have to first physically remove the hard drive of the computer that’s not booting up. You can refer to it as Hard drive 1 and Computer 1, respectively.
• After that, you need to have another computer which you can refer to as Computer 2, and refer to its hard drive as Hard drive 2. Make sure that this second computer is working properly.
• Next, you have to attach Hard drive 1 to Computer 2 with the Hard drive 2 attached as well.
• After that, boot Computer 2 from Hard drive 2 where Hard drive 1 will act as the second storage unit.
• Then navigate to the following location in the System Partition of the Hard drive 2.

C:/Windows/System32/config/RegBack

• From there, you have to replace all the files. Once you’re done, shut down your computer and then take out the Hard drive 1 from Computer 2 and put it back to Computer 1 as the only hard drive.
• Now boot your computer normally and check if the problem is fixed.

Users are reporting that randomly their screen will just go black for a second and come back. When this happens, it usually distorts any video currently on the screen; sometimes, they can resume working on the PC normally. However, when they view the event logs, they see the error message Display driver nvlddmkm stopped responding and has successfully recovered. In this article, we will address solutions to this issue and how to not have it again.

1. Remove Aura iCUE plugin (applies to only ASUS motherboards)

   Some PC users discovered that iCue adds an Aura plugin for ASUS MOBOs. That, combined with EVGA Precision X1, was causing the error it seems – this was determined when the screen would turn off and on when opening EVGA x1 software. In this case, the issue was resolved by removing the Aura iCUE plugins.

2. Change Power Management mode

   Right-click the battery icon on the notification area on the right of the Taskbar. Select Power Options. In the Power Options window, locate your current Power Plan. Select High performance, if that’s not your current power plan. Now, click on Change plan settings next to it. Now click on Change advanced power settings. Expand PCI Express section. Expand Link State Power Management. Now set power saving to Off for both On battery and Plugged in state. This would fix any issues caused by the low power of the video card. Click Apply > OK to save changes.

3. Update graphics driver

   Go into device manager Expand display adapter section Right-click on adapter Click on update driver Reboot

4. Rollback graphics driver

   Go into device manager Expand display adapter section Right-click on adapter Click on Roll back driver Reboot

5. Uninstall and reinstall graphics card driver

   Go into device manager Expand display adapter section Right-click on adapter Click on Uninstall device Reboot

6. Replace the graphics card

   If everything else failed, replace the graphic card