One of the worst problems users can encounter on their computers is Blue Screen of Death errors as some of them are quite hard to fix. One of them is the “The driver detected a controller error” Blue Screen error. It could be followed by “DeviceIdeIdeport0 OR”, “on deviceharddisk0dr0”, or “DR3” or the name of the drive or port that’s causing the problem. If you are one of the users who encountered this error, then the suggestions provided in this post would definitely help you in fixing the problem.
Option 1 – Try to disconnect and reconnect all hardware and cables
A lot of users reported that they were able to fix the problem by disconnecting and reconnecting cables and hardware like scanners, printers, cameras can help in fixing the problem. In addition, you can also boot your computer in a Clean Boot State so that you can find the problematic hardware by hit and trial method. Refer to the steps below to do so:
- 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.)
Option 2 – Update the device drivers
Updating the outdated device drivers in your computer can also help in fixing 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 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.
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 running the Blue Screen Troubleshooter
You might also want to run the Blue Screen troubleshooter. It is one of the built-in tools in Windows 10 that helps users in fixing system issues including Blue Screen errors. 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.
Option 5 – Try running the Memory Diagnostic Tool
The Memory Diagnostic tool in windows can help resolve the “The driver detected a controller error” 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.
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 6 – Replace your motherboard
If your computer is still under warranty, you should consider replacing your computer’s motherboard in case the options given above failed to work in fixing the Blue Screen error.
Error Causes
From the Device Manager choose the troublesome device and right-click on it, choose properties.
Device properties floating Window will appear.
Click on the top tab which says, Driver. From the Driver tab, click on Roll Back Driver.
Note that if the device is working properly, the Roll Back Driver button will be greyed out and you will not be able to click on it meaning that chosen device is not the issue. If the device is not working properly and you can click on Roll Back driver, do it, choose the previous version, and reboot your computer.
You can use this method to get back to the previous driver version for any device that is causing issues in your computer. 
The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved. 
Interesting information has come out from Microsoft, Windows 11 dark theme will include a different sound theme from its standard light one.
When in dark mode on Windows 11, the system sounds generally become softer, and they echo a bit, creating a more soothing experience that matches the overall look and feel of the dark mode. Flipping back to light mode brings the system sounds back to their normal level.
However, even though the light model has slightly louder sounds than the dark mode, Microsoft has taken great care to make sure the audio is more soothing, according to a report from CNBC.
The designers of Windows 11 took inspiration from an approach called calm technology. Microsoft’s Christian Koehn and Diego Baca wrote about calm technology in a post on Medium. In it, they said, “Windows 11 facilitates this through foundational experiences that feel familiar, soften formerly intimidating UI, and increase emotional connection.”
According to a Microsoft spokesperson in a statement to CNBC, “The new sounds have a much rounder wavelength, making them softer so that they can still alert/notify you, but without being overwhelming.” 
