Windows Photo Viewer can’t display picture

If you are trying to connect to the internet using a Wi-Fi, Ethernet, or a Wi-Fi connection and you suddenly encounter Error 633, then read on as this post will guide you on how you can fix this problem in your Windows 10 computer. According to users who encountered the same problem, when they try to connect to the internet, an error pops up that states, “The modem or other connecting device is either already in use or not appropriately configured”. This error is the VPN Error 633 which indicates that the modem is malfunctioning due to some broken configuration. It is possible that this broken configuration is caused by the WAN Miniport device which is associated with your preferred VPN protocol. It could also be due to the TCP port that’s required for the VPN connection to work might be used by another application. There are instances when Error 622 could occur when there are multiple internet connections set up on one device or when the communication port is exploited by another program. It could also occur when the affected modem is not bound to one specific device. Thus, any model and computer can be affected by this problem. The first and basic thing you can do to fix the VPN Error 633 is to turn off or unplug the modem your computer is using and then plug it back in to see if the problem is fixed. If not, then there are several other potential fixes you need to check out to resolve the problem. You can try the suggestions provided below and see if any of them help.

Option 1 – Run the Network Adapter Troubleshooter

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

Option 2 – Try to explicitly reserve the TCP port

The next thing you can do to fix the error is to reserve the TCP port explicitly and to do that, follow the steps below.

• Tap the Win + R keys to pull up the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters
• After that, follow the path New > Multi-String Value on the edit menu and rename the multi-string value as “ReservedPorts” and then double click on it.
• Now in the value data of ReservedPorts, input “1723-1723” and click OK to save the changes made.
• Close the Registry Editor and restart your PC. Once your computer has restarted, check if the VPN Error 633 is fixed or not.

Option 3 – Try to use the netstat command

• In the Windows Start Search, type “cmd” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, type this command and hit Enter: netstat –aon
• After that, the output will be displayed and from there, look for the process ID or PID of any program that uses the TCP port 1723 on your computer.
• Next, type this next command and hit Enter: taskkill /PID PID /F
• Once the command has been executed, the concerned program will be forced to close and the TCP port 1723 will be freed up. Keep in mind that the taskkill command ends the process corresponds to the process ID number and the given command above, “/F” option is used to end the program’s process forcefully.
• Now restart your computer and after that, the concerned program should start using a TCP port other than 1723 which leaves the TCP port 1723 free for your internet device to use.

Option 4 – Remove any irrelevant internet device programs

You could also try removing any irrelevant device programs since it is possible that any of these programs could be the one that’s causing the modem to malfunction. These irrelevant programs could be an internet booster or third-party tools that comes with the modem and so on. These programs are not necessarily needed for your modem to function. Thus, if you want to fix the VPN Error 633, you can try uninstalling them and see if it fixed the error.

Option 5 – Update the Network Adapter drivers

You might also want to update the Network Adapter drivers by following these steps:

• 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.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand them.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing the VPN Error 633, 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. To reinstall the network adapter driver, refer to these steps:

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

The GeForce Experience on graphics card manufactured by NVIDIA is an advantage for users who loves gaming as it makes enhances users’ gaming experience. However, there are times when it may also encounter some problems. One of the problems users may encounter is the error code 0x0001. This kind of error occurs when users open the NVIDIA GeForce Experience utility. Here’s the full content of the error message:

“Something went wrong, try rebooting your PC and then launch GeForce Experience, ERROR CODE: 0x0001.”

Errors like this one diminish the overall experience of users due to the fact that when this error occurs, the NVIDIA GeForce experience wouldn’t even start which renders its features useless. There are several potential fixes you can check out to resolve this error but before you check them out, you can try to restart your computer first and then open the NVIDIA GeForce Experience once again, if you still encounter the error, then you need to check the NVIDIA Display Driver Services or update your NVIDIA display drivers or switch to the BETA release. You could also try to install and reinstall the NVIDIA display drivers or perform System Restore and see if it helps. For detailed instructions, follow the given options below.

Option 1 – Try to check the NVIDIA Display driver services

• Tap the Win + R keys to open Run and then type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the following NVIDIA services and make sure that their Startup types are as follows:
  • NVIDIA Display Container LS – Automatic
  • NVIDIA NetworkService Container – Manual
  • NVIDIA LocalSystem Container – Automatic
  • NVIDIA LocalSystem Container – Automatic
  • NVIDIA GeForce Experience Service – Automatic (Delayed Start)
  • NVIDIA Geforce Experience Backend Service – Automatic (Delayed Start)
  • NVIDIA Telemetry Container service – Automatic
• Next, double click on each one of the services and go to Properties. Here, check if the service is running. If it’s not, just click on the Start button. On the other hand, if they’re already running, just click on Stop and then click on Start again.

Option 2 – Try to update the NVIDIA Display drivers

You can also try updating the NVIDIA display drivers as it might help in fixing the error. To update them, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next type in “dxdiag” in the field and click OK or hit Enter to open the DirectX Diagnostic Tool.
• From there, you can see what type of NVIDIA graphics card that your system is on.
• Take note of your graphics card information and then look for the best drivers for your operating system. Once you’ve downloaded and installed the file, restart your PC.

Note: If you want to try out the beta release of the NVIDIA display drivers, click on this link. Beware though that the beta software is unstable and buggy and may cause some different bugs.

Option 3 – Try to roll back the driver to the previous version

If updating the NVIDIA display drivers didn’t work for you, then it’s time to roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh.

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the NVIDIA Drivers and expand it.
• Next, select the driver entries that are labeled appropriately.
• Then select each one of them and double click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the NVIDIA Drivers.
• Now restart your computer to successfully apply the changes made.

Option 4 – Try to run System Restore

You could also run System Restore as it might help fix the error code 0x0001 in NVIDIA GeForce Experience.

• 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 then check if the error code 0x0001 in GeForce Experience is now fixed.

Option 5 – Do a clean install on the NVIDIA driver

• Before you do a clean install on the NVIDIA driver, you have to download the latest version of the Display Driver first.
• Boot your Windows 10 PC into Safe Mode.
• After that, double click on the executable file of the Display Driver Uninstaller to run and install it.
• After the installation, open the program. Once you do, you should see the following window on your screen:
• In the program window, click on the “Clean and restart” button.
• After your PC has rebooted, download the NVIDIA drivers.
• Then select your Product Type, Product Series, Product, Operating System, and Language appropriate for your hardware specifications as well as personal requirements.
• Next, click on Search to display the latest available driver as per the information you entered.
• And click on Agree and Download to start downloading the latest driver executable file.
• Run the executable file after you finished downloading the latest driver executable file and then select Custom and click on Next.
• Afterward, select “Clean Install” and proceed. Doing so would install the latest driver on your PC.
• Restart your PC and check if the error’s now fixed. If not, you can try installing an older version of the driver instead.

If you are trying to connect an external device to your computer but you suddenly encounter an error that says, “Device requires further installation”, then you’ve come to the right place as this post will guide you on how exactly you can fix this error. In most cases, USB sticks, headphones, speakers, and other external devices, install drivers automatically once you connect them to your computer which means that the drivers are downloaded and installed in the system as soon as the external device is plugged in. However, if the driver has become corrupted or outdated, you might encounter an error like the

“Device requires further installation”

Aside from corrupted or outdated drivers, the error could also be caused by pending updates, an incorrect version of the Intel PROSet Wireless driver, or checking the wrong event. Whatever the cause is, this post will provide you with some potential fixes that can help you resolve the problem. But before you troubleshoot the problem, ensure that your Windows 10 computer is updated to its latest version and you must also not forget to check that you’re checking the correct event on the Event Viewer. Once you have these things covered, proceed to the instructions below.

Option 1 – Try to update the device drivers to the latest version

One of the most likely root causes of the “Device requires further installation” error is either outdated or corrupted drivers in your computer. This kind of problem is more common on several devices like scanners and printers for which the drivers are provided with them.

• 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 any outdated device drivers and click on each one of them.
• After that, 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.

Note: You also opt to download the latest versions of the device drivers directly from the website of the manufacturer. Once you’ve downloaded them, you can install them into your computer right away and then try connecting the external device again. On the other hand, you can also try to reinstall the device drivers.

Option 2 – Try to install the latest version of the Intel PROSet Wireless driver

A lot of users who experience the problem reported that their wireless driver wasn’t also working properly and it was then found that it was caused by the outdated Intel PROSet wireless driver. Thus, to fix the problem, you need to install the latest version of this driver from the intel.com website and install it on your computer. When you download the driver, make sure that your computer is running an Intel system and then download the correct driver depending on whether your computer is a 64-bit system or a 32-bit one.

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.

When we get ourselves a new USB stick, new hard drive, or any storage device not including optical drives they are usually preformatted and ready to be used out of the box. However, reformating them has several benefits and while we are reformatting we can choose in which file system format we want the memory to be formatted. In this article, we will compare and explore 3 typical and standard format options you can get while formating a new media in Windows 10.

FAT32

The oldest one on the list, coming all the way from DOS days. Great for devices that need to be plugged in different operating systems and for USB flash drives. Its advantages are compatibility with all major operating systems and little memory usage comparing to other ones. However, the file system is limited to file sizes of the maximum capacity of 4GB and partitions can not exceed more than 32GB.

NTFS

First introduced in Windows NT this file system offered slower performance than FAT32 and somewhat limited usability but the main advantages were more stability and fewer errors. Its main advantages are support for files larger than 4GB and partitions larger than 32GB along with the ability for on the file encryption, main disadvantage would be limited operating system usage, NTFS can not be used on systems that work on FAT32 like MS-DOS for example or older versions of Windows. The best usage for this file system is in internal hard disk drives and system drives.

exFAT

New kid on the block, well at least from the perspective of the previous 2. exFAT offers unlimited file sizes and unlimited partition sizes but at a price that is even more limiting than NTFS. Some Linux distributions will require a driver to be installed in order to see the exFAT partition. The best use is in storage, in external hard drives. That's it, 3 major file systems, we hope that you have managed to learn something new today, and remember to drop by tomorrow for more articles about advice, tips, tricks, and troubleshooting.

If by any chance your search result in Windows is misleading, missing, or incorrect then it is a high probability that your search index is out of date. To repair this issue follow this guide step by step. Please take note that rebuilding the whole search index can take a long time on some systems depending on the size of the index itself, CPU speed, HD speed, etc. Sometimes it can take even hours on large drives. First, press ⊞ WINDOWS + R to open the run dialog and type in it Control panel to open the control panel. Once you are in the control panel, switch your view to large icons and locate Indexing options. Inside indexing options, click on advanced. In advanced options click on the rebuild and confirm. Leave your computer to finish and your searches should be working fine now.

Recently, a number of users reported that they were not able to use the “Run as administrator” context menu option when they tried using it or opening a program with administrator privilege. If you are one of these users facing this problem, then you’ve come to the right place as this post will guide you in fixing this issue. At the time of writing, it isn’t clear what the cause of the issue is but there are potential fixes you can try to fix the problem. You can try turning on the User Account Control or clean up the Context Menu items change the Group Membership. On the other hand, you can also perform both SFC and DISM scans via Command Prompt or troubleshoot the problem in a clean boot state as it is possible that some third-party programs are the ones that are causing the problem. You could also run an anti-malware scan using Windows Defender or your antivirus program.

Option 1 – Try to turn on the User Account Control

When you open a program with administrator privilege, the User Account Control or UAC prompt will pop up asking you to confirm the permission. However, if you have disabled the User Account Control by mistake or some malware has disabled it, then it’s no wonder why the “Run as administrator” option is not working. Thus, you need to check if UAC is turned on or not. All you have to do is go to the User Account Control settings.

Option 2 – Try changing the Group Membership

• First, you need to sign in with your administrator account or ask your administrator to sign in for you. So if you only have a Standard User account, you have to add that account to the Administrators group.
• In the taskbar search box, type “netplwiz” and check the search results.
• From there, select your user account and click the Properties button.
• After that, go to the Group Membership tab and select Administrator.
• Now click on the Apply and OK buttons to save the changes made and then sign in to your computer again and see if the “Run as administrator” option is working or not.

Option 3 – Try to create a new Administrator User account

If you have a standard account, you can try creating a new account but this time, you create an administrator user account and then see if you can now use the Run as administrator option or not. Note that you have to sign in with your main account before you can create an admin account.

Option 4 – Run the DISM tool

You can run the DISM tool as well to help fix the problem with the “Run as administrator” option. 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 5 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the problem with the “Run as administrator” option on your Windows 10 computer. 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. 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 and hit Enter.

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.

• Once done, restart your computer.

Option 6 – Put your computer in a Clean Boot State

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

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

Option 7 – Try scanning your computer using Windows Defender

As mentioned, if your computer was recently infected with some malware, it is possible that the malware changed the User Account Control settings which is why you’re not able to use the Run as administrator option. Thus, you need to scan your computer using Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

Error 1310 is a fairly common type of error encountered by Windows users. Error 1310 usually generates while a user is attempting to install Adobe Photoshop or some Adobe product on Windows. The message displayed to the user usually states: ‘Error 1310. Error writing to file. Verify you have access to that directory’. Once the error message appears, the installation process will be terminated.

Solution

Error Causes

While there are different conditions that may trigger this error, most likely, they are generated because of the lack of privileges a user has on a Windows log-on. When this happens, the operating system doesn’t allow the user to access the installation files. Another reason Error 1310 may occur is that often users attempt to log on to the system and choose the ‘Only for me’ option rather than the recommended ‘Anyone who uses this computer’. Because of this reason, the data is locked for all the other users. Since Error 1310 can easily disrupt your workflow on the system and may also lead to annoying consequences, it is best advised to treat it as quickly as possible.

Further Information and Manual Repair

There are different solutions to resolve these errors that are briefly listed below as follows.

• First and foremost, restart the installation by logging onto your computer from the administrator account. This error will most likely disappear because there is often a lack of privileges that will trigger it. When you will log on from the admin account, you will have access privileges and such errors will be rectified.
• Fix any corrupt system files that exist on your system. If the file resides in the Windows directory, this error will be generated. Check if any of your system files are corrupt or damaged. If yes, make sure you repair and return them back to their original position.
• This error is sometimes caused because of incorrect registry entries. If the setup program shows errors, it is possible that it is because the system is having problems retrieving data stored in the system registry.
• Another way, this error can be avoided is to run the setup in compatibility mode. Compatibility issues are a common occurrence. However, when an installation is performed in the compatibility mode, one can easily steer clear of such errors.

Implement any of the solutions listed above and protect your system against Error 1310.

One of the smoother things that Microsoft did with the Windows 10 operating system is to separate Cortana from Search. This means that Cortana is strictly now a voice assistant and many users have seen it coming since not everyone uses Cortana. In addition, it also paved the way for other virtual assistants like Alexa to get on board with Windows 10. And now in the newly released Windows 10 v1903, Windows has brought the Voice Activation under Privacy. In this post, you will be guided on how to perform the Voice Activation troubleshooting on your Windows 10 computer. To use Voice Activation in Windows 10, follow, in the Start Search, type “voice activation” and click on “Voice activation privacy settings” listed in the search results. And from there, you can choose to allow apps to use Microphone, like listen in the background as well as select which app can access it. Each time enabled voice assistants continue to listen via microphone for the voice keyword, the app will activate itself for the keyword and will react depending on what you ask it. So if you are using a voice assistant and it didn’t respond when you speak the keyword, just go to Settings > Privacy > Voice Activation and follow these steps:

Option 1: Check the App permission to use the voice activation feature.

You have to make sure that the toggle button for the Voice activation feature is turned on globally. It can be found under the “Allow apps to use voice activation” section. You also have to ensure that the microphone is available for apps that use this feature.

Option 2: Voice activation is not working under the lock screen.

If you tend to use the voice assistant even when your computer is locked, Microsoft has a specific setting that you have to turn on. You need to make sure that the toggle button for the “Allow apps to use voice activation when this device is locked” option is turned on. However, keep in mind that the voice assistants are not locked to only recognize your voice as they also answer to anyone who will use the voice keyword.

Option 3: Check the individual permissions of apps.

If the voice assistant is not working, you have to check each one of the apps’ permissions for voice keyword, and the option to work under locked condition works.

Option 4: Run the Microphone troubleshooter.

If you’ve verified that the settings are in place, then you have to run the Microphone troubleshooter by simply going to Settings > Privacy > Microphone. From there, make sure that the toggle button for the following options is turned on:

• Allow apps to access your microphone
• Enable microphone access for the voice assistant

And if it’s a desktop app, you have to enable the toggle on at the end.

This post will help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen issue with an error code 0x000000BE. If you encounter this kind of BSOD error when you try to boot into your Windows 10 computer, note that there are various possible causes for this error. It could be caused by an error with a device driver, hardware issues, or some error in the BIOS of your computer. The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error with a bug check of 0x000000BE appears when a driver tries to write a read-only memory segment. You’ll be able to see the name of the driver in the Blue Screen error if the driver that’s causing the error can be identified. You can also see it in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In most cases, this kind of error is usually caused by various files such as iusb3hub.sys, ntkrnlpa exe or vhdmp.sys, ntoskrnl.exe, ntfs.sys, dxgkrnl.sys, tcpip.sys, atikmdag.sys, and win32k.sys. There are several possible fixes you can try to fix this issue but the main issue lies within booting into Windows since the error occurs as soon as you boot into your Windows 10 computer. Refer to each one of the options provided below to resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error.

Option 1 – Try to rollback, update or disable drivers

The first thing you can do to fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error is to roll back, or update, or disable 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 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 4 – Try disabling BIOS Memory Options

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

Option 5 – Try running the Blue Screen Troubleshooter

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