Razer unveils their first internal PC hardware

Page Fault in Non-Paged Area is a blue screen error usually happening with faulty drivers but it can come from different issues like faulty RAM. In this short article, we will cover usual ways on how to approach and solve this error.

Solving Page fault in Non-Paged Area

Rollback using system restore

Simple and easy solution, roll back to the previous system restore point where Windows was stable and working.

Fix Page Fault in Non-Paged Area using device manager

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on device manager
3. Find a device with a question mark and right-click on it
4. Click on the rollback driver button

Fix via command prompt

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on command prompt (admin)
3. Inside command prompt type in SFC / scannow and press ENTER
4. Wait for the process to be finished and then reboot the PC

Fix via DISM tool

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on command prompt (admin)
3. Inside command prompt type in DISM /Online /Cleanup-image /Restorehealth and press ENTER
4. Wait for the process to be finished and then reboot the PC

Page fault in Non-Paged Area via a dedicated tool

Sometimes manual and provided solutions just simply cannot cut it because the issue is triggered also with something else and not just a single issue. Use DRIVERFIX to fix this specific issue with a single click.

The Local Security Authority Subsystem Service or LSASS.exe is a process in the Windows operating system that is valuable as it enforces the security policy on the computer. Every time you log in to the Windows Server, the LSASS.exe is the one that handles the password changes and creates the access tokens while updating the security log. However, it is also frequently targeted by malware and is often imitated. The original location of this file is at “C:/Windows/System32” so if you open the Task Manager and notice that a process with a similar name has a different location then it is definitely a threat and is exploiting the security of your computer. To resolve issues related to LSASS.exe, here are some fixes that could help.

Option 1 – Use the Performance Monitor’s Active Directory Data Collector

Note that this option will only work on the recent Windows server versions. Refer to the steps below to use the Performance Monitor’s Active Directory Data Collector set on your computer.

• Tap the WINKEY + R button to open the Run dialog box.
• Then type “Perfmon.msc” in the field and hit Enter to open the Performance Monitor and from there open the Server Manager.
• Next, navigate to Diagnostics > Reliability and Performance > Data Collector Sets > System from the left side of the navigation bar.
• Then right-click on “Active Directory Diagnostics” and select Start from the context menu. This will take about 5 minutes or 300 seconds depending on the performance capabilities of your hardware to gather the data required and then take some more time to compile a report from the gathered data. Note that these timings are dependent on one another.
• After the report is compiled, you can find it under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics. The report will contain all the information as well as conclusions. However, it does not mean that it will also contain the exact cause of the problem with LSASS.exe. Nevertheless, it should help you in fixing the problem.

Option 2 – Try to run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why the LSASS.exe file is having some issues. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Now restart your computer and see if the problem is fixed or not.

Option 3 – Put your computer in a Clean Boot State

If none of the options given above helped, you can try putting your computer in a Clean Boot State as this can help you in finding any incompatible programs that’s 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.

Toolbar.Dll is one of the most destructive software you will encounter on your Personal Computer. For every report out there you read about threats to your Windows PC, a significant number speak about Toolbar.Dll. Technically, this is non-essential to the functioning of your computer yet poses great dangers to your computer's security. It can cause massive destruction if not properly resolved.

Solution

Error Causes

As suggested below, the sources of Toolbar.Dll are many and broad: a) Misconfigured System: Nothing causes this malfunction on your own Computer a lot more than having a misconfigured system. You ought to anticipate this malfunction and repair the situation before it gets worse. Especially if you have Toolbar.Dll files on your computer. More often than not the situation can only get worse. b) Broken Windows OS File: the 2nd trigger of Toolbar.Dll, and that is linked to the primary aforementioned one, is a broken Windows OS file. Fix it as soon as you realize its existence. c) Installation Issues: If you poorly install Windows on your PC, you generate a loophole by which Toolbar.Dll malfunction might appear. You essentially provide a massive possibility to the Toolbar.dll error to affect your Computer, if you neglect to finish an install or uninstall procedure. d) Removing Programs and Hardware Incorrectly: When you decide to remove programs and hardware, you need to exercise caution. Should you be rash with this specific procedure, you raise the odds of striking the Toolbar.Dll malfunction on your Personal Computer. e) Incorrect Shut-Down: unless you want to strike this malfunction, ensure that you shut down your Computer procedurally. Regardless of what hurry you might be in, always power down your computer correctly.

Further Information and Manual Repair

In the event you strike the Toolbar.Dll malfunction on your Personal Computer, you shouldn't get frightened. But, prior to starting considering of ways that to fix this malfunction, you should look for the signs, to be able to recognize it. The malfunction exists in your Computer in circumstances where software programs can't load properly. The situation might be repaired in numerous methods, as revealed below:

• Switch on your computer, and log in as the superuser/admin. Next, select All Programs, subsequently go to Accessories. Under Accessories, choose System Tools. Click on System Restore from the menu.
• A fresh window will appear. In the new window, find the choice designated "Restore My Pc To An Earlier Time", before you click next.
• Search for the newest System Restore update from "On This List, Click a Restore Point" before you click Next once more.
• Pick Next when a verification window appears on the screen. After the complete procedure is done, reboot the pc and the Toolbar.Dll malfunction will soon be no further.

Each of the measures suggested previously, are for advanced pc users. You must obtain the very best software on the web to eliminate this malfunction, in case you are a non-techie. Alternately, contact a tech to help fixing the problem.

The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

1. Click on the Windows icon and go to settings.
2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
3. Choose Advance Option
4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

1. Open the Microsoft Edge browser.
2. Type in about: flags on the Address (URL) bar.
3. Under Networking, uncheck the Enable TCP Fast Open.
4. Close your Microsoft Edge browser and open a new one.

Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.

1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
2. A drop-down menu will show up, click on Command Prompt which is the first on the list.
3. Type in the code ipconfig /flushdns and press enter.
4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
5. Exit the CMD by typing exit and press enter.

The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.

BIOS is software that is running in a chip located on your motherboard, you can enter BIOS usually by hitting DEL once the computer is turned ON but this sometimes varies and it depends solely on the motherboard manufacturer. Inside BIOS you can configure your computer components and set up some other important things including passwords for BIOS itself or for the entire system. Password itself is meant to protect access to BIOS from other non-technical users or to prevent access to the system from other people if for example computer is in one household and you would like to be the only one having access to it. However, passwords can be forgotten, and sometimes you can even purchase a second-hand computer with a password on it. In this guide, we will lead you through ways on how to remove your BIOS password so you can regain access to your BIOS settings.

1. Use Manufacturers master password

   Most motherboard manufacturers have built-in a couple of master passwords for BIOS access. If your motherboard has one you can easily find it on the manufacturer's website. Use the master password and remove other passwords inside BIOS, save and exit.

2. Remove CMOS battery

   If you could not find the manufacturer's master password or your motherboard model does not have one remove the CMOS battery to reset BIOS. Note that this method will reset the whole BIOS not only the password. Open on side of your computer casing and locate the round battery on it, do not worry, there is only one battery so you can not make mistake. Remove the battery and leave it outside for around 20 to 30 minutes then place it back as it was, CMOS is reset now and you can access BIOS.

3. Reset BIOS via jumper

   If you want to remove only the password and do not touch other BIOS setting you can locate the BIOS password reset jumper. How the location of this jumper and position is different from the motherboard to motherboard we can not cover them all here and it is advisable to read the manual or find information on the official manufacturer's website.

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Error 1753 - What is it?

Error 1753 is an RPC endpoint mapper error code. This code is typically displayed as "EPT_S_NOT_REGISTERED" or sometimes as the hexadecimal value 0x6D9.  Error 1735 indicates that there are no more endpoints available from the endpoint mapper. To understand this better, basically, RPC is an inter-process communication (IPC) method. This is used by clients and servers for communication purposes. RPC is used by programs to execute programs on a server computer. The perfect example of this is Microsoft Outlook. You communicate with Microsoft Exchange Server using RPC. This enables you to send and receive emails. When you use Microsoft Outlook to send emails, your computer sends a message to the server computer in an obscure coding. The server responds to your computer with another message that contains the results of the executed program. This is all being carried at the backend of the running program. Integral to this is the endpoint. The endpoint includes the name, port, or a group of ports on a computer that is monitored by the server for incoming client requests. This is a network-specific address to be precise. The endpoint mapper is the part of the RPC subsystem that is responsible for dynamically assigning endpoints to the server. When this function fails it leads to error 1753 message display. It shows that RPC service is not available.

Solution

Error Causes

The error code 1753 indicating RPC endpoint mapper service failure is triggered due to multiple reasons. These include:

• Windows registry damage and corruption
• Malfunctioning of the hardware
• Spyware intrusion or viral infections
• Device driver conflicts

Further Information and Manual Repair

This error code may cause a great deal of inconvenience to execute programs that are dependent on the server. It can lower your productivity and performance. To avoid the hassle, it is advisable to repair the error 1753 immediately. The best way to resolve this error 1753 in seconds is to download Restoro. By using this repair tool, you can fix the error right away for free without paying hundreds of dollars to a professional expert. Restoro is a new and innovative PC fixer integrated with an automated algorithm and intuitive technology that enables users to sit back and relax while Restoro runs on the system and detects all PC-related issues in the shortest time. In just a few clicks you can resolve even the mightiest PC issues like the error code 1753 RPC endpoint mapper problem and resume back to the program in no time.

Why Restoro

It is efficient and user-friendly. Restoro can be used by users of all levels so even if this is your first experience using a repair tool, you don’t have to worry. To operate it, you don’t have to be a computer programmer or have sound technical expertise. It is simple and very easy to use. The layout is simple and neat complimented nicely with easy navigation and a sophisticated user interface. Restoro is a high and multi-functional error tool embedded with powerful, performance-driven, and value-adding utilities, all in one. So, whether the error code 1753 is triggered due to a viral infection on your system or registry corruption, you don’t have to look for different tools to resolve the error, simply run Restoro to fix the issue right away. Restoro includes a dynamic registry cleaner that detects all registry issues and wipes out the clutter from the hard disk like junk files, internet history, and invalid entries which is by the way the number cause for registry corruption leading to error 1753. It clears up disk space and RAM and repairs the misconfigured system files and corrupt registry in seconds thus resolving error 1753. Restoro also functions as a system optimizer thus boosting the speed and performance of your PC massively and reducing boot time. In addition to this, it also has a backup feature.  This tool is embedded for safety purposes. This feature enables you to create backup files on your PC before you start system repair. This helps you recover data in the event of data loss during system repair. To get started:

• Click here to download and install Restoro on your system
• After installation, run it to scan for errors like 1753
• Now press the repair tab to resolve

Windows 10 has a UWP app for its Camera that you can use to take pictures and videos. However, if you suddenly encounter an error code 0xa00f4243 while using the Camera UWP app, then you’ve come to the right place as this post will provide some potential fixes that you can use to fix the problem. This kind of error could be due to an outdated or corrupted driver or a third-party program. When this error appears on the Camera UWP app, you will see the following error message:

“Close other apps. It looks as though another app is already using the camera. If you need it, here’s the error code: 0xA00F4243 (0xC00D3704)”

To fix the error code: 0xA00F4243 (0xC00D3704) in the Camera UWP app, you can try to run the Windows Store Apps troubleshooter or reset the Camera app or update or reinstall the driver or apply some tweaks in the Registry Editor. In addition, you can also try checking the Windows Services or run the System File Checker.

Option 1 – Try to run the Windows Store Apps troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the Camera UWP app error code: 0xA00F4243 (0xC00D3704). This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. 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 2 – Try to reset the Camera app to fix

As pointed out earlier, you can also reset the Camera app to fix the error. To do so, follow the steps below.

• The first thing you have to do is go to the My Pictures folder under the C: drive of the File Explorer and then delete the Camera Roll folder.
• Once you’re done, right-click on an empty area on your screen and create a new folder and name it “Camera Roll”.
• Then from the Start menu open the Settings app and select System.
• From there, navigate to the Apps and features section.
• Now go to Camera and click on the Advanced Options and click the Reset button.

Option 3 – Try to reinstall the drivers for the Camera app

You might want to reinstall the Camera drivers as it could resolve the problem. To do so, refer to these steps:

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc  into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the driver listed under the Camera section and then, right-click on each entry of the device drivers and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Option 4 – Try to use the Registry Editor

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindows Media FoundationPlatform
• Here, look for a DWORD named “EnableFrameServerMode” and if you can’t see it, just create a new DWORD by right-clicking on any empty space.
• Then select New > DWORD (32-bit) Value and name it as “EnableFrameServerMode”.
• Double click on the newly created DWORD and set its Value data to “0” and click on OK.
• Restart your computer and see if it fixes the Camera UWP app error code: 0xA00F4243 (0xC00D3704).

Option 5 – Try checking the Windows Services

Note that this option only applies to computers with Intel Hardware for the Camera.

• Tap the Win + R keys to open the Run dialog box and type “services.msc” and hit Enter to open the Services Manager.
• Next, look for the “Intel(R) RealSense(TM) Depth” service from the list of services and double click on it to open its Properties.
• After that, change its Startup Type to “Automatic” and make sure it’s running and then click on the Apply and OK buttons to save the changes made.
• Restart your computer and check if the problem has been resolved.

Option 6 – Try running System File Checker or SFC scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your PC.

The win32kfull.sys file is one of the kernel-mode device drivers in your Windows 10 operating system. In case you don’t know, there are two kinds of device drivers – the first ones are the normal drivers that communicate between your hardware and the operating system while the second ones are the kernel-mode drivers. The latter is necessary for booting your OS. And there are times when you encounter the win32kfull.sys error while booting your PC. Here’s the full context of the win32kfull.sys error:

“SYSTEM_SERVICE_EXCEPTION (win32kbase.sys) APC_INDEX_MIXMATCH PAGE_FAULT_IN_NONPAGED_AREA”

This error could be caused by corrupted or outdated drivers with incomplete files or it could be caused by some driver or software installed on your computer. To fix this error, here are some troubleshooting options you need to check out.

Option 1 – Try updating all the Drivers

As pointed out, the win32kfull.sys error can be due to outdated or corrupted drivers that are not compatible with your hardware. These drivers include but are not limited to display, network, sound, hard drive, and more. If you are not able to access the internet, you can just manually download the update using another PC. To update your drivers, here’s what you need to do:

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it. After that, you could also check if there’s a new update of the game you’re getting the issue of the black bar.

Option 2 – Identify and uninstall problematic programs by putting your PC in a Clean Boot State

One of the main causes of BSOD errors like win32kfull.sys is a problematic program that could clash with your existing operating system as well as computer architecture. There are tons of programs that are either incompatible or conflict with the existing drivers or software in your system. To identify such programs, you need to put your PC in a Clean Boot state. How? Follow these steps:

• 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” checkbox 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” checkbox.
• 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 putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps are given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.

Once you have identified the program causing the problem, uninstall it right away from your Control Panel.

Option 3 – Perform an SFC scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the win32kfull.sys error. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

File Transfer Protocol Server, also known as FTP Server, is a private or public service that can host files that can be accessed both locally and globally. It is a quick, flexible and seamless service that allows you to store any kind of files depending on the total size of the server. If you’ve always found an FTP server useful, then the good thing is you can now create your FTP server since Windows 10 now allows it. You can host this server locally and later on make it globally available via the internet. So if you are planning to set up an FTP server on your Windows 10 computer, read on as this post will guide you on how to do so.

To set up the FTP server, you need to configure it first and then configure the Windows Firewall for the connections to go through. For more details, refer to the following steps:

Step 1: You need to configure the FTP server on Windows 10.

• In the Search box, type in “Turn Windows Features On or Off” to search for it.
• Then click on the appropriate result which will open a mini window.
• From this mini window, scroll down to the list and expand “Internet Information Services where you have to expand the FTP Server section.
• Next, select all the checkboxes to enable all the entries under FTP Server and then click the OK button to apply the changes made.
• And now, since your computer is now allowed to host an FTP server, you need to configure it. To do so, type “Internet Information Services (IIS) Manager” in the Search box and click on the appropriate entry.
• Next, right-click on Sites under the navigation bar of Connections and select Add FTP Site. This will open a new window where you have to input some information about your FTP hosting.
• Now enter the details and click on Next.
• Upon clicking Next, you will be prompted to give some authentication details. Enter the following details in the screenshot below.
• Now click on Finish. After that, you will get an FTP Server being hosted on your Windows 10 PC.

And now that you’ve successfully configured the FTP Server, the next thing you have to do is to allow connections from and to the FTP server. Refer to the next step below. Step 2: Configure the Windows Firewall for FTP connections to pass-through

• In the Start Search, type “Allow an app or feature through Windows Firewall” and click on the related search result which will open a window with all the settings.
• From there, click on the Change Settings button. This will display a list where you have to mark all the checkboxes for the FTP server to enable them in both the Private and Public configurations.
• After that, click OK. This will allow you access to the FTP server on your local network.

The Blue Screen of Death error or BSOD is definitely not an issue to face on your computer. Many users, if not all, have already experienced this headache at least once. One of these BSOD errors is the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error. The bug check error code for this is 0x000000FC and is usually caused by outdated or faulty drivers. In some cases, it could also be caused by an error in the Random Access Memory or RAM. This kind of error in the RAM might be physical, based on drivers, or even some kind of unwanted malware. So basically there are lots of possibilities why this particular BSOD error pops up. If you are currently facing this BSOD error, read on and carefully follow the suggestions given below but before you do that, make sure to create a System Restore point just in case something goes wrong. This way, you can always undo those changes using the System Restore point. Once you have that covered, proceed to the options given below to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error.

Option 1 – Try updating Windows 10 with all the security patches and updates

You might be able to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error by simply updating your Windows 10 computer with all the security patches and updates. To do so, go to Settings then proceed to the Windows Update section > Update & Security > Windows Update, and then click on the Check for Updates option. After you do that, it will automatically find and install all the latest security patches and feature updates from Microsoft.

Option 2 – Try updating all your drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To fix the problem, you need to update all your drivers. Follow the steps below to update your drivers.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 3 – Try running a Memory Check using Windows Memory Diagnostic

As mentioned, this error might be caused by some issues in the memory. To resolve it, you need to run the Memory Check on your Windows 10 PC. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 4 – Try using the System File Checker via Command Prompt

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.