Completely Uninstall and Remove Flash

If you encounter the CLOCK_WATCHDOG_TIMEOUT Blue Screen of Death error while using your Windows 10 computer then it is most likely caused by a specified processor which is not processing interrupts. This occurs when the processor is deadlocked or nonresponsive. Specifically, this kind of Stop error occurs when the processor is having a hard time with the cooperation of its threads and cores. The threads are the tasks performed by cores and some cores can have many threads at the same time. And this is where the problem begins – one thread is waiting for an adequate response from another thread or one kernel is waiting for a response from another kernel and those responses are not coming. In other words, when the processor is unable to continue the processing of tasks since its resources are occupied and are interdependent to get free, such a state is called Deadlock. The CLOCK WATCHDOG TIMEOUT bug check has a value of 0x00000101 which means that an expected clock interrupt on a secondary processor, in a multiprocessor system, was not received within the allocated interval. To troubleshoot the problem, you can check out the possible fixes provided below but before you proceed, make sure that you boot your computer into Safe Mode with Networking only.

Option 1 – Undo or disable overclocking if you have overclocked your system

• Go to the Start Menu and open Settings.
• Next, select Update and Security and go to the Recover tab.
• From there, click on Restart now in Advanced startup. This will restart your computer.
• Once you’re in the Advanced startup, go to Troubleshoot and then select the Advanced Options.
• From there, select the UEFU Firmware Settings.
• Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
• From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
• Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
• Start your computer normally and check if the CLOCK_WATCHDOG_TIMEOUT 0x00000101 error is now fixed.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the CLOCK_WATCHDOG_TIMEOUT 0x00000101 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 mdsched.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.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the CLOCK_WATCHDOG_TIMEOUT 0x00000101 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 4 – 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 CLOCK_WATCHDOG_TIMEOUT 0x00000101. 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.

Option 5 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the CLOCK_WATCHDOG_TIMEOUT Blue Screen error.

Option 6 – Troubleshoot the BSOD error in Clean Boot State

You can also troubleshoot the Blue Screen error in a Clean Boot state. There are times when third-party applications cause BSOD errors. 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 to 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.

Option 7 – Try to update the BIOS

Updating the BIOS can help you fix the CLOCK_WATCHDOG_TIMEOUT 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.

If you are browsing the internet using the Google Chrome browser in your Windows 10 computer but you suddenly encounter an error message that states, “ERR_ICAN_NAME_COLLISION”, read on as this post will walk you through in fixing the problem. Here’s the full content of the error message:

“The site can’t be reached, This site on the company, organization, or school intranet has the same URL as an external website. Try contacting your system administrator. ERR ICAN NAME COLLISION.”

This kind of error is caused by an error in a private namespace or a random redirection to an incorrect proxy server. There are several ways to fix this error. You can try to check the integrity of the Hosts file or check the proxy. You could also try to use the Registry Editor and apply some tweaks or remove any conflicting browser extensions or flush the DNS cache, as well as run a malware scan.

Option 1 – Try to check the integrity of the Hosts file

To check the integrity of the Hosts file, refer to the following steps:

• You have to navigate to this path inside File Explorer: C:/Windows/System32/driversetc
• After that, look for a file named “Hosts” and right-click on it, and open it with the Notepad app.
• Next, make sure that you write the block URLs in your computer in the list and then save the file.

Note: There are times when you are logged in with administrator credentials and you may receive an error message. In such case, type “notepad” in the Start Search and right-click on Notepad from the search results, and then select the “Run as administrator” option. After that, open the Hosts file and make the necessary changes and save it.

Option 2 – Try to check the Proxy server

There are some users who reported that they’ve fixed the problem after they’ve disabled the use of a proxy server using the built-in way. Follow the steps below to disable the proxy server.

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 3 – Try to use the Registry Editor

Before you apply some registry tweaks, make sure that you create a System Restore point. Once you have that covered, follow these steps:

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and tap Enter to open the Registry Editor.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParametersDataBasePath
• Look for the default key and double click on it and make sure that its Value data is set as “C:/Windows/System32/driversetc”.
• Now exit the Registry Editor and restart your computer to apply the changes made

Option 4 – Flush the DNS cache

You could also try to flush the DNS cache to fix the “ERR_ICAN_NAME_COLLISION” error. All you have to do is open Command Prompt as an administrator and then execute each one of the following commands sequentially to flush the DNS cache:

• ipconfig/release
• ipconfig/renew
• ipconfig/flushdns

Option 5 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Note: If removing the browser extensions or toolbars didn’t work, you can also try to reset your Google Chrome browser.

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Option 6 – Run a malware scan using Windows Defender

It is possible that your computer is infected with malware which could be why you’re getting the “ERR_ICAN_NAME_COLLISION” error. 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.

One of the most critical processes in the Windows 10 operating system is the Explorer.exe. And there are times when you might encounter an error that says, “System call failed”. You can encounter this error when you try to launch File Explorer, and in such case when the File Explorer does not work, it could cause issues in accessing folders and files on your computer. This kind of error pops up when the explorer.exe system file has become corrupted or if there is some process that interferes with its smooth functioning. To fix this error, you can try to restart the explorer.exe process, run both the System File Checker scan and DISM tool. You could also put your computer in a Clean Boot State or uninstall any programs you’ve installed recently. For more details, follow each one of the given suggestions below.

Option 1 – Try to restart the Explorer.exe process

The first thing you can do is try to restart the Explorer.exe process. To do so, refer to these steps:

• First, right-click on the Taskbar and select the Task Manager.
• Next, expand the Task Manager window to see all the active processes.
• From there, look for the Windows Explorer process, right-click on it and select Restart.
• After that, check if the error is now fixed.

Option 2 – Run System File Checker scan

If restarting the explorer.exe process didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in this command: sfc /SCANFILE=c:windowsexplorer.exe

Note: If you are using a 64-bit Windows operating system, enter the “sfc /SCANFILE=C:WindowsSysWow64explorer.exe” command instead.

• Wait until the process is completed and then restart your computer.

Option 3 – Run the DISM tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “System call failed” error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

Option 4 – Try running the Check Disk utility

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk c: /f /r
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 5 – Put your computer in a Clean Boot State

As pointed out, there are some instances that some conflicting programs installed in your computer might be the one that triggers the “System call failed” error to appear when you try to open File Explorer. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• 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.)
• Once your computer has restarted in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 6 – Try to uninstall the programs you’ve installed recently

In case you don’t know, freeware software packages aren’t always free as some of them could contain malicious software that can cause serious damage to your computer. Thus, if you have installed a program recently prior to getting the “System call failed” error, then you have to uninstall that program.

• Tap the Win + R keys to open the Run dialog box.
• Then type “appwiz.cpl” in the field and tap Enter to open the Programs and Features in Control Panel.
• Next, arrange the list of installed programs in the order of the installation date.
• After that, look for the problematic program and right-click on it, and then select Uninstall.
• Once the process is done, restart your computer and see if the error is fixed.

What is Error Code 0xC004C003?

Error code 0xC004C003 has to do with activating Windows 10 after a clean install. This problem has been a frequent nuisance to users trying to update from Windows 7 or 8.1 following the invite path they got from Microsoft.

Solution

Error Causes

There are several problems that may have caused error code 0xC004C003. The most common of them are:

• The product key entered was invalid, and cannot be used to activate the new OS.
• The user followed the proper installation procedure, but the Windows update servers were too busy to handle the activation at that moment.
• The free upgrade invitation was followed but after the reinstallation, the copy of Windows 10 was still not activated.
• The user tried to perform a full clean install of Windows 10 instead of upgrading from Windows to Windows 10

Further Information and Manual Repair

A lot of solving error code 0xC004C003 has to do with the method in which the user has tried to update the system. If one decided to try and update the program before being invited to do so by the update manager, he must wait. Unfortunately, if one chooses to do it on his own and download a clean install, he was never given a product code to authenticate the process. There are two options to address error code 0xC004C003 — either restore to the previous Windows Operating System or call Microsoft (or visit their Website) and purchase a product key. The Windows update servers are very busy. There are lots of Microsoft users around the world, and the servers are doing their best to get to each and every one of the users as fast as possible, but they can only move at a certain speed. Your best bet is to sit back and wait a while. But what if you were invited, and properly downloaded Windows 10, then decided to do a clean install? It is advised that one do not try to enter Windows 7 or 8.1 serial code as this will not work. However, unlike the problem above, these users will NOT need to purchase a product key. According to Microsoft Support Staff, the installation servers are also very jammed because of the high numbers of installations going on right now. No matter what posts you may read, the key IS genuine, and it is NOT blocked, broken, or invalid. To check if Windows has been properly activated, open the Command Window. Make sure you are logged into an administrator profile; otherwise this check will not work. Type in “slmgr.vbs/ato” and click Enter and then wait. While waiting, the command will check on the status of the activation. Windows Script Host will open and show whether or not it is activated. A lot of users have reported that the activation did not work for the first few times. However they later reported after some more attempts, no issue was found in the way the operating system updated and that the activation process went smoothly. This is most likely due to the overload on the Windows Update servers, so bear with Microsoft. Users have reported that when trying to correct error code 0xC004C003, they have followed the upgrade path and then been told by Microsoft that the key was invalid and they had to purchase a new one. If the upgrade path provided by Windows 7 and Windows 8.1 is correctly followed then there is nothing to worry about Just wait a while and try it again. If there are prolonged issues, speak with a technician by visiting the Microsoft website and contacting the help center by calling the number provided. Give them all relevant information and they will be sure to help accordingly. The best solution to fix error code 0xC004C003 is to wait. In essence, the user will be waiting to reenter the same product key. According to Microsoft, and many user posts found online, it is recommended to wait a while and then try to activate again. This seemed to be an answer to most users' problems, and seem to work just fine. If the problem persists, take it to a windows repair technician to have it sorted out. If that does not work, use a powerful automated tool to fix the problem.

What Does 0x8007045D Error Code Mean?

The 0x8007045D error code is an I/O (input and output) error that is associated with the registry. It indicates that the Windows operating system has become overloaded with invalid system references in the registry. This may prevent you from executing reading and writing to and from devices successfully.

Error Causes

Registry is the main database of your PC. This portion of your computer saves all the activities that you perform on your PC including the junk files, temporary internet files, invalid entries, bad registry keys, and more. This clutters the hard disk. If the unnecessary files are not removed from the registry, it may lead to I/O errors like 0x8007045D. On the hard drive, some parts of the drive may fail to function. If this is not fixed on the time it may lead to serious disk damage and registry corruption eventually resulting in system failure. System failure can make you lose all the valuable data saved on your system for good.

How to Fix the Error Code 0x8007045D?

Error codes on your PC are like warnings. These codes indicate that your PC has some issue. Therefore ignoring it is not wise. To spare yourself from such serious PC damages, it is advisable to take correct measures timely instead of prolonging and making the situation go from bad to worse.

I must admit that I am a big Western Digital fan, I have been using their hard drives really long time and I must admit that I am very happy with their products. Sometimes they could be a little more expensive than other drives on market but security and performance are on their side. If you ever wanted to purchase Western Digital or WD hard drives or you are considering getting one, no doubt that you have come across their color cryptic line of products. 1TB Hard drive can come in 6 different colors in your search products query and if you are not familiar with the WD color coding of hard drives you might be a little lost as to which one is right for you and what are the differences. This article is made to explain exactly that, what are WD colors representing so you can choose the right one for your needs. Western Digital has decided to use color codes in order to mark their series of disks which means that each color represents different hard drive series and it is made and aimed for different use, we are going to explore in detail each series below:

WD BLUE

Blue series is all around typical hard drive made and meant for daily use in desktop computers for all kinds of tasks. You can use it in casual gaming or for storage, its purpose is tailored for all-around casual daily users.

WD RED

WD Red HDD is designed for NAS and RAID systems. Its purpose is to be turned 24/7 who ever need access to it. Get this series if you need to have constant access to files or if you need a reliable RAID hard drive.

WD GREEN

Green series of the hard drive is manufactured for low power consumption and for storage, they are meant to be used for storage and not accessed regularly.

WD PURPLE

Purple line of hard drive products is designed solely for video surveillance systems. Instead of having a preference on reading data like WD RED, the PURPLE series is given preference on writing, constant writing to be more precise.

WD BLACK

The black series is made for an external storage medium with high performance. Due to the high performance, WD Black hard drives are much popular among photo editors and high-end gamers.

WD GOLD

WD Gold HDD provides a long-term cold storage medium. Therefore, this series of Western Digital hard drives are suitable for data centers. These hard drives can handle many sophisticated systems simultaneously and work well with different servers That's it, I hope that you have now a more clear understanding of the WD color-coding of its hard drive series. As always thank you for reading and I hope you will have a great day. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

There is various Blue Screen of Death errors that you can encounter as you use your Windows 10 computer and some of these Stop errors have something to do with the win32kbase.sys file. This post will guide you in fixing the BSOD errors related to the win32kbase.sys file.

• A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: Win32kbase.sys.
• Your PC ran into a problem and needs to restart. If you would like to know more, you can search online later for this error: win32kbase.sys.
• SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)
• STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – win32kbase.sys
• STOP 0x0000001E:

KMODE_EXCEPTION_NOT_HANDLED – win32kbase.sys

• STOP 0×00000050:

PAGE_FAULT_IN_NONPAGED_AREA – win32kbase.sys

The win32kbase.sys file is a Windows operating system Base Win32 Kernel Driver file located in the System32 folder so if it ends up getting corrupted or if it went missing, your computer will throw up Blue Screen error. To fix BSOD errors that have something to do with the win32kbase.sys file, here are some possible fixes that could help. Worry not for these possible fixes are not complicated.

Option 1 – Run the Check Disk or CHDSK utility

One of the first things you can try to resolve the win32kbase.sys Blue Screen error is running the CHKDSK utility. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f C:

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

Option 2 – Run SFC or System File Checker 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.

 Restart your PC.

Option 3 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the win32kbase.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing Blue Screen errors related to the win32kbase.sys file. It can be found in 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 getting this error even if STEAM.EXE is present on your system then follow the easy guide to solve the issue.

1. Scan your system for malware

   Scan your complete system for viruses and other malware. If all the scans come negative then move to the next step.

2. Disable your anti-virus software

   Some anti-virus and anti-malware software can detect steam as a potential threat and block it. Turn off your protection software and try to run Steam once all your protection is disabled. If this works you will need to either place Steam in the applications exception list or to move to another protection software.

3. Remove administrator privileges from steam client

   Right-click on steam.exe and choose properties, go to the compatibility tab, and uncheck run this program as administrator. Try to run Steam again.

4. Delete Steam registry value

   If everything else failed try deleting the registry value for steam. Open registry editor and locate key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options Double click on Image File Execution, find steam on left, right-click on it, and choose delete. Save and exit the registry editor.

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.

If you suddenly get a message telling you that “Your Windows license will expire soon, You need to activate Windows in Settings” on your Windows 10 computer but you know that your Windows 10 is already activated. Worry not for this post will help you get rid of that error message right away. Before you get started, make sure that you have the Windows product key with you. If you don’t, you can get it by running the following command in an elevated Command Prompt:

wmic path SoftwareLicensingService get OA3xOriginalProductKey

Take note of the product key and then proceed to the options given below.

Option 1 – Try activating Windows 10 again or use another product key

• If you’re sure that you have the correct product key, click the Go to the Settings button.
• After that, click the Activate button once again.
• If you have another license key, you can also use that as well, just simply click on the Change product key.
• Then enter the new product key and click on Activate. That should fix the problem, if it doesn’t, refer to the next option below.

Option 2 – Try to reset the licensing status

• Click the Start button and then type “cmd” in the Search box and then tap Ctrl + Shift + Enter to open an elevated Command Prompt.
• Next, type the “slmgr –rearm” and hit Enter to reset the licensing status.
• Restart your computer and check if the error is now gone or not.

Option 3 – Try uninstalling the product key and re-enter it once more.

• The first thing you have to do to uninstall the product key is to know the Activation ID of your Windows installation. To do so, open an elevated Command Prompt and type this command, and hit Enter – vbs /dlv
• After you enter the command, you should see the licensing status and Activation ID. And to get all the Activation IDs of all the installed Windows versions, key in this command and hit Enter – vbs /dlv all

Note: The “/dlv” parameter will give you the license information for the installed operating system.

• After you enter the second command, you should see a Windows Script Host window with all the Windows licensing and activation status. Take note of the Activation ID.
• Next, in the same elevated Command Prompt, type this command – slmgr /upk <Activation ID>

Note: In the third given command, “/upk” stands for “uninstall product key”. This parameter uninstalls the product key of the current Windows edition.

• Restart your PC. After that, your computer will be in an unlicensed state so you need to re-enter the product key again.

Option 4 – Try rebuilding the Tokens.dat file.

The issue might be caused by a corrupted Tokens.dat file. The Tokens.dat file is a digitally signed file that stores most of the Windows Activation files so if it is corrupted then no wonder you’re having activation issues. To rebuild the Tokens.dat file, refer to these steps:

• From the WinX Menu, open an elevated Command Prompt.
• After opening Command Prompt, you need to type each one of the following commands and after you type each command, hit Enter.
  • net stop sppsvc
  • cd %windir%ServiceProfilesLocalServiceAppDataLocalMicrosoftWSLicense
  • ren tokens.dat tokens.bar
  • net start sppsvc
  • exe %windir%system32slmgr.vbs /rilc
• Now restart your computer.

Option 5 – Try running the Windows 10 Activation Troubleshooter

• Go to Settings and then select Activation.
• After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

Option 6 – Try activating Windows 10 via mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.

• In the Start Search box, type in “Slui 4” and tap Enter.
• Next, select your country and click on Next.
• Keep the window open and call the toll-free number of the country you’re from.
• Afterward, a confirmation ID should be given by the automated system which you must take a note of.
• Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.