MS Mariner, new OS for servers based on Linux

Compare Exchange128 error – What is it

Some Windows 7 and Windows 8.1 users reported experiencing a Compare Exchange128 error when trying to upgrade to Windows 10. The error reads, “You can’t install Windows 10 because your processor doesn’t support CompareExchange128”. In order to upgrade to Windows 10 (64-bit), the CMPXCHG16B instruction must be present. If you receive this error, this mostly means that your CPU doesn’t have the CMPXCHG16B instruction.

Solution

Error Causes

The CompareExchange128 error normally occurs due to two possible reasons:

• CPU lacks CMPXCHG16b Instruction
• Old & Outdated BIOS – Even if your CPU has the CMPXCHG16b instruction, the CompareExchange128 issue can still occur if you have an older BIOS.

Further Information and Manual Repair

One main requirement to upgrade to Windows 10 is for your CPU to have the CMPXCHG16b instruction. You also need the right BIOS version to guarantee a smooth installation. See below on how to manually fix this issue.

NOTE: If you don’t feel confident using the manual methods listed below, it’s highly advisable to get help from an expert technician. If you don’t know someone, you can also use an automated tool to fix this.

Before performing any fixes, try to determine first if the cause of the error is due to your CPU lacking the CMPXCHG16b instruction. You can use a CPU Info tool that provides complete details about your processor, memory, and motherboard. If you’re looking for more in-depth information, you might also try command-line utilities. But, the safest and easiest way to check this is by simply searching online. Try using the search query: <CPU Model> CMPXCHG16b

Method 1 – Update your BIOS

This method will download the latest BIOS from your motherboard’s manufacturer. This makes sure your CPU has the CMPXCHG16b instruction needed to complete the Windows 10 64-bit installation. To update your computer’s BIOS, complete the following steps:

1. Determine first the current BIOS you have on your computer. Open System Information Windows app and type msinfo32 in the search bar. The BIOS version will appear under the processor speed. Record it somewhere.

2. Go to the support page of your motherboard’s manufacturer. Find if there’s any update on the BIOS that you’re currently using. If you find one, download the BIOS update file available. Make sure that you’re looking into the right model and you download all the necessary documentation. Otherwise, the BIOS update might not work.

3. Update your BIOS. Most BIOS update steps are straightforward. Just make sure to follow the steps provided.

Method 2 – Install Windows 10 32-bit version

If updating the BIOS doesn’t work, what you can do is install a 32-bit version of Windows 10 instead of the 64-bit version. Here’s how to do this:

1. Download and install the 32-bit version of Windows you currently have. If you have a Windows 7 64-bit version, get the 32-bit version of Windows 7. The same goes for Windows 8.1. When you do this, you might want to back up your files first. Remember that installing the 32-bit version works like other installations, and could delete some of your files.

2. After installing the 32-bit version, go to Updates and install all the necessary updates. This includes upgrading to Windows 10 if you’re asked to.

3. When you installed the Windows 10 upgrade, you’ll now have the Windows 10, 32-bit version installed. This will be the version activated on Microsoft servers. Despite this, the activated version stored is only applicable to your computer’s hardware, not the version of Windows 10.

4. Download Windows 10, 64-bit version.

5. Prepare an empty DVD or USB flash drive. Use Creation Media software then click the Create Installation Media for Another PC option.

6. Install the 64-bit Windows 10 version you downloaded from Step 4. Make sure not to put anything when you’re asked to input the serial number.

7. Once the installation is complete, you’ll have the 64-bit version of Windows 10.

Method 3 – Buy a new processor/motherboard

If the above two methods don’t work, there’s a great chance that this error occurs because of an outdated processor/motherboard. Your next possible solution is to buy an updated model that’s fully compatible with 64-bit Windows 10.

Method 4 – Download an automated tool

If all else fails, you might want to consider using this powerful automated tool to quickly fix the problem and any other computer-related issues.

If you suddenly noticed that your Onscreen keyboard in Windows 10 has become completely white or transparent for some reason, then you’ve come to the right place as this post will guide you on what you can do to resolve this kind of issue in your computer. As you know, the on-screen keyboard is included in Windows 10 and has an executable file named “osk.exe”. The on-screen keyboard is a part of the Ease of Access feature in Windows 10 which allows users to navigate the computer with the help of the mouse instead of the physical keyboard. However, there are times when you might encounter some issues when using the on-screen keyboard. One of the issues reported recently is that the on-screen keyboard becomes transparent or it only displays the borders but there is no way for you to access it. You also won’t be able to move it from the view completely. To fix this problem, there are several suggestions you can check out. You can try to check the Fade button or run the Windows Touch Keyboard troubleshooter. You can also restart its process in the Task Manager. For more details, refer to each one of the given options below.

Option 1 – Try to check the Fade button

The first thing you can do is to check the Fade button on the on-screen keyboard. You can find it at the bottom right corner of the keyboard. If it is enabled, then it’s probably the reason why your on-screen keyboard is transparent as it lets it fade in the background. Thus, you have to disable it to resolve the problem.

Option 2 – Try to run the Windows Touch Keyboard troubleshooter

The next option you can check out is running the Windows Touch Keyboard troubleshooter. This troubleshooter will help you identify the problem and would fix them automatically.

Option 3 – Try to restart the process of the on-screen keyboard via Task Manager

The next thing you can do is to restart the on-screen keyboard’s process in the Task Manager. Just follow the steps below.

• First, tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and look for the option that says, “Accessibility On-screen Keyboard”.
• Once you found it, click on the drop-down arrow next to it and right click on the “On-screen Keyboard” option, and select End task to end its process.
• After that, tap the Win + R keys to launch the Run utility and type “osk.exe” in the field, and then hit Enter to open the on-screen keyboard.

The ntkrnlmp.exe file is a file associated with the Windows operating system’s NT Kernel and other system processes. It is also related to the “CRITICAL PROCESS DIED” error. So if you encounter a Blue Screen of Death error that’s related to this file, then you’ve come to the right place as this post will guide you in fixing the ntkrnlmp.exe Blue Screen error. This kind of Blue Screen error might be caused by the file getting corrupted or infected with some malware. Aside from these causes, the error might also be due to the corruption and malfunction of the graphics card drivers. Before you troubleshoot the problem, you might want to try performing System Restore especially if you tend to create a System Restore point every now and then. Performing System Restore could help you resolve the ntkrnlmp.exe Stop error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap 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, then proceed to the given options below.

Option 1 – Disable the C-states and EIST in the BIOS

The first thing you can do is try to disable the C-states and EIST in the BIOS. To do that, refer to the steps given below.

• Go to the BIOS and from there look for an option named CPU Configuration which can usually be found under the Advanced menu.
• Next, look for CPU Power Management and under that section, disable both the “Intel EIST” and “Intel C-state” options.
• After you disable them, save the changes you’ve made and exit the BIOS.
• Now restart your computer and check if the ntkrnlmp.exe BSOD error is now fixed.

Option 2 – Try to update, rollback or disable drivers

If the first option didn’t help in fixing the ntkrnlmp.exe Blue Screen error the next thing you can do is to roll back, or update, or disable device drivers in your computer. 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 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the ntkrnlmp.exe Blue Screen error you need to use the Driver Verifier Manager:

• 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 4 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ntkrnlmp.exe. 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.

If you are using UEFI and you encountered an error message that says, “Selected boot image did not authenticate”, then read on as this post will show you what to do it fix it. This kind of error indicates that UEFI is having an issue in figuring out if the boot image has tampered with. UEFI offers Secure Boot and if the boot image seems to be invalid, you won’t be allowed to boot into your computer. Aside from that, it could be that you may be using endpoint encryption and the software can’t validate the certificate. To fix the “Selected boot image did not authenticate” error in UEFI, you need to first check if the error has given any reference to any software that you might have for encryption. If it has, then you need to disable the Encryption tool to resolve the problem. In addition, you could also try to disable Secure Boot or perform Startup Repair in case the disabling Encryption tool didn’t work. For more details, make sure to use each one of the options provided below as a reference.

Option 1 – Try to disable the Encryption tool

The first thing you can do to fix the “Selected boot image did not authenticate” error is to disable the Encryption tool. Many users reported that some encryption tools like the ESET Endpoint Encryption won’t let them boot into the computer if the system manufacturer does not include the correct certifications as a part of the UEFI BIOS. And since there is no way to bypass this, you have to disable Secure Boot in order for you to boot into your computer.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 3 – Try to run the Automatic Repair Utility

If disabling Secure Boot did not fix the problem, you might also want to run the Automatic Repair utility in fixing the error. To do so, follow the steps below.

• You can start by booting into the Advanced Recovery Mode.
• After that, select Troubleshoot > Startup Repair.
• Next, follow the on-screen instructions that appear on the screen and finish the Automatic Repair process.
• Now check if the block is gone once the reboot is completed.

Driver Verifier is a built-in tool in Windows 10 that monitors device drivers on your computer, if it detects issues with drivers, it will attempt to fix the issue. If you are encountering Blue Screen for a Driver and after running Driver Verifier you get another with message DRIVER_VERIFIER_DETECTED_VIOLATION ten follow this article step by step in order to solve it. There is a chance that you will maybe even have to do this in safe mode, if that is your case, login into safe mode and proceed, otherwise proceed normally.

1. Update Device Drivers

   the most common issue with the blue screen is old Drivers, in most cases, graphical drivers, update all Drivers with the latest versions and see if this will resolve the issue.

2. Stop or uninstall Virtualization software

   Virtua machine software is a great way to have a safe environment and to experiment while preserving your Windows installation intact, however sometimes due to the nature of these applications they can be a case for blue screen errors. Stop virtualization software to see if it will remove the issue. If that is the case, try another virtualization application

3. Disable Driver Verifier

   Press ⊞ WINDOWS + X to open the secret menu Click on Command Prompt (admin) Inside command prompt type: verifier and press ENTER Select the Delete existing settings radio button Click Finish Reboot your computer

4. Reset Driver Verifier

   Press ⊞ WINDOWS + X to open the secret menu Click on Command Prompt (admin) Inside command prompt type: verifier /reset and press ENTER Reboot your computer

5. Use system restore

   Rollback Windows to the previous state where everything was working fine.

Windows 11 has come a long way from its infant stage. Today it is incredibly good and stable operating system that also looks good and modern. Unfortunately, fancy animations and good graphics come with a price, in this case, slower performance on some little older and weaker computers.

Animations itself which include also fading effects can sometimes feel slugging and laggy and have a general overall feeling of delay. For a more old-school instant experience, you can turn off animations.

In order to turn animations inside Windows 11 follow this simple guide:

First thing is to open Settings by pressing Windows + i key combination or you could open Start and in the search box type in Settings and then click on its icon.

Once inside settings on the left side find Accessibility and click on it to select it. Once it is selected on the right side choose Visual effects. Inside the visual effects section click on the switch next to Animation effects to OFF. You can also turn off transparency effects in this section if you wish if you have an older GPU in order to speed it up a little.

That is all you need to do, settings will be automatically saved and all animations will be turned off for a quicker and more responsive feeling when working inside W11

Call of Duty is a fun and good game, a great time killer with a squad of friends, however sometimes the game crashes, and fun is interrupted. In this guide, we will address and solve this unpleasant issue.

1. Scan game files

   inside launcher choose options and under them, choose scan and repair game files This process can take 5-30 minutes, as the game is 60GB large. This will look through all your game files and make sure they’re all valid and that none are corrupted, which may cause crashes. When it’s complete, you’ll get a notification that the game is now playable. Try again and see if your crashes continue.

2. Update drivers

   Keeping drivers updated is crucial for the game to run smoothly, GPU drivers are possibly important. Go to your GPU manufacturer's website and get the latest drivers.

3. Lower graphic settings

   Intensive graphic requirements can overload GPU and cause crashes, try lowering details in-game and see if this will fix the issue.

4. Disable overlays

   If you’re using a program like Discordthat has an overlay, you’ll want to disable it as it may be causing the graphic error

If you encounter an error message saying, “The ordinal xxx could not be located in the dynamic link library C:/Program Files (x86)/Microsoft VS Code Insiderscode – insiders.exe“ and you see a reference of a missing DLL file, then this indicates that the software is trying to locate the related DLL file, however, it is missing, hence the error. The error mentioned “Ordinal” which refers to the order of a number mathematically, e.g. 1st, 2nd, etc. And in this error message, the ordinal is referring to an Xth file of an XX.DLL file which is missing which is why you’re getting this kind of error. When you get this particular error, it means that your computer is missing the Microsoft Visual C++ Redistributable program. As per the error message, XXX is a number that in turn is the Ordinal. There is also another common error related to Ordinal which says, “The ordinal 12404 could not be located in the dynamic link library mfc90u.dl”. The error message could be referring to any DLL in the message. And since all these DLL files are part of the package, the error changes quite a bit as the Visual Studio looks for that DLL file. To fix this error, here are some suggestions that might be of help.

Option 1 – Try installing Microsoft Visual C++ Redistributable

As pointed out earlier, the error pops up when the Microsoft Visual C++ Redistributable program is missing on your computer. Thus, you need to download it from the official website of Microsoft. Once you’ve downloaded the Microsoft Visual C++ Feature Pack Redistributable Package, install it and then check if the error is now fixed.

Option 2 – Try to install OpenSSL

If you encounter the same error message but it points out that the LIBEAY32.DLL file is missing, then you have to install OpenSSL. In such a case, you will see the following error message:

“Ordinal not found. The Ordinal [Xxxx] could not be located in the Dynamic Link Library Libeay32.dll.”

 Make sure that when you install OpenSSL, you do it into the Windows system directory since the Libeay32.dll file is related to security.

Option 3 – Try to check Windows Updates

There are instances when Microsoft rolls out the framework and related updates via Windows Updates. It could be that an update related to DLL is still pending which is why you need to check Windows Updates. To do so, go to Settings > Update and Security and from there check if there is any pending update. If there is, you need to install that update and then restart your computer if needed.

Although the UWP platform is still new, it is working efficiently and significantly and it’s apparent that Microsoft is betting big on it. It helps developers in building applications for Windows 10 that are more modern and beautiful as well as responsive with the help of the .NET Core and XAML. However, all things considered, it still isn’t perfect and it could still encounter some errors. One of these errors is the Windows.UI.Xaml.Markup.XamlParseException UWP app error. This particular error can occur to any Universal Windows Platform or UWP application and according to security experts, it is due to some XAML parsing error. To fix this error, you can try to reinstall the faulty program or check its privacy settings. You can also run both the Program Compatibility and Windows Store Apps troubleshooters as well as run System Restore. For more information, check out the given options below.

Option 1 – Try to reinstall the faulty application

If you encounter this error in an application that is not a system-related one, then you can just uninstall it from the Windows 10 Settings app and then reinstall it again from the Microsoft Store. On the other hand, if it is a system application like the Camera or Calculator app, you can just uninstall and reinstall it using a PowerShell script.

Option 2 – Try to check the Privacy Settings of the concerned app

You might also want to check if all the Privacy Settings required for a certain application are configured properly as it could also cause issues like the Windows.UI.Xaml.Markup.XamlParseException UWP app error.

Option 3 – Try to run the Program Compatibility Troubleshooter

You might also want to run the Program Compatibility Troubleshooter. This built-in troubleshooter is available in the Windows Update & Security section. From there, select Troubleshoot. This will find a list of programs for you and since you have already downloaded the driver files, just click on Not Listed located at the top of the program list. After that, browse and select the driver files and then let the program do its job. In addition, you can try to run the Windows Store apps troubleshooter as it can also help you resolve the problem.

Option 4 – Run System Restore

If you have recently made changes in your computer’s settings, you could also run System Restore to fix the Windows.UI.Xaml.Markup.XamlParseException UWP app error. How? Refer to these steps:

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

Browsing the internet doesn’t always go smoothly, you might encounter ads, pop-ups, viruses, malware, and even errors. In this post, we’ll walk you through how you can fix the 502 Bad Gateway error that you might encounter in browsing the internet. This kind of error suggests the server which is the one that’s acting as a gateway to facilitate in taking your request to the server and bring some response back has received an invalid response or even no response at all. It could be that the connection is broken or that there is an issue on the server-side that returns an invalid response. Even though the 502 Bad Gateway error is a server-related error, there are still a few things you can try that might help resolve it, if tapping the Ctrl + F5 keys does not resolve the problem. Keep in mind that it doesn’t matter what website you open as this error can appear on any website. To resolve the problem, you need to follow the options prepared below.

Option 1 – Check the network cable connections and restart your router

As with other connection problems, this is the most basic thing to do before you try other troubleshooting options because the root cause of the problem might be as simple as a cable not connected properly or a router that just needs to be restarted. Thus, checking the network cable connection to see if there is anything out of order can help as well as restarting your router.

Option 2 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns– type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Change the DNS

Changing the DNS server for your network can also help you fix the 502 Bad Gateway error. You can use a public DNS like the Google Public DNS, Open DNS, Yandex DNS, Comodo Secure DNS, and many more. All you have to do is to override the default DNS settings on your PC so that you can specify which DNS server is used as well as which IP address should be used for a specific domain.

Option 4 – Try updating the Network Adapter Driver

Follow the steps below to update your Network Adapter Driver:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• From there, expand the list of all the network drives and update each one of them.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 5 – Try a Network Reset

When all else fails, you might have to consider resetting your entire network settings. Simply follow the steps below to do so.

• Click on the Start button and then click on the gear-like icon for Settings to open it.
• Next, select Network and Internet.
• Then scroll down and look for “Network Reset” – click on it and then click on the Reset now button.