Mouse automatically scrolls up or down

Microsoft has been bringing new lock-screen features with every iterative feature release of Windows 10 in order to improve user experience. However, Windows 10 users have different opinions regarding it. Some users are pleased with it while some users simply do not like it. So if you are one of the users who seem to not approve of this feature, read on as this post will be about enabling or disabling the Console Mode sign-in feature in Windows 10. Before you proceed, take note that you will not be able to use your mouse pointer in this Consol Mode login screen and you can only use your keyboard to navigate around various options. You might also want to create a System Restore point just in case. To enable or disable the Console Mode sign-in in your Windows 10 computer, refer to the given steps below. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: Then type in “Regedit” in the field and tap Enter to open the Registry Editor. Step 3: Next, navigate to the following registry path:

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAuthenticationLogonUITestHooks

Step 4: From there, look for a DWORD named “ConsoleMode”. If you don’t see this DWORD, you can just create a new DWORD and name it as “ConsoleMode” and make sure that its base is set to Hexadecimal. Step 5: After that, double click on ConsoleMode and change its value to “0” to disable it and “1” to enable it. Step 6: Now restart your computer to apply the changes made. Like pointed out, you can only use your keyboard when you’re in the Console Mode login window or screen. You can just use the ESC button to go back to the menu while you can utilize the arrow keys so you can go through the options that are mostly vertically arranged and the Enter key to select an option. In the Console Mode, sign-in using the Passwords and PINs worked efficiently.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

What is Runtime Error 216?

Runtime Error 216 is not a common error message like Runtime Error 339. However, it may sometimes occur when starting up the computer if you are using a Windows-based application or using Internet Explorer.

Solution

Download Available to Completely Repair Runtime Error 216

Error Causes

The runtime error 216 error occurs when your computer gets infected with one or more viruses. The most common virus, in this case, is the SubSeven Trojan virus. Once your computer gets infected with a virus(es) it creates a backdoor on your Windows system. This might give hackers access to monitor your PC remotely. This poses a great risk to confidential information and personal data stored on your PC. The hackers can easily monitor your PC, access your private information and misuse it.

Further Information and Manual Repair

If you experience this error message, it is advisable to repair it immediately without any delays; Runtime Error 216 can make your system vulnerable. Here’s what you must do:

• First things first, disconnect the internet connection so that the hacker can’t access your PC.
• Now perform a boot scan through a powerful antivirus.  The antivirus will scan your system for viruses. After the scan is complete, all the disinfected files will appear in the scan report results. You are advised to delete them and click repair to fix the error.
• Remember the antivirus will not scan infected Windows Registry entries, therefore to remove SubSeven.exe Windows Registry entries go to the start menu and type REGEDIT in the search box.
• Click on REGEDIT and select Run as Administrator. Now type the following registry path HKEY_LOCAL_MACHINESoftware. This will help locate SubSeven.exe infected files. Once located, delete all of them and close Windows Registry Editor.

To ensure your computer is completely free from SubSeven Trojan Virus and other possible viruses, it is advisable to remove all the recently installed programs and downloaded applications. This is recommended because sometimes while downloading programs, we tend to download corrupted programs which include viruses. It’s, therefore, best to delete all the programs you’ve installed recently. Secondly, to prevent virus and hacker attacks, you must frequently update your security program by installing a powerful antivirus program. Following the repair guide steps will protect your system from malware. It will also help fix runtime error 216 and ensure your PC is protected from similar threats.

It is no secret that Microsoft is trying to keep Windows relevant and that it is trying to make it as good as possible. A new Windows update will bring some interesting stuff in it which well some like it, some not so much. Among various technical and security updates Microsoft will bring some directly visible to each user.

First

of these features will be File explorer compact mode. This feature is a sort of spacing content in file explorer giving it easier access if you are using a touch screen device. Now, this feature is somewhat strange, and altho I can understand and get behind the logic of this move I am not sure I like it. Lucky for me and others who feel the same this option can be turned off for now.

Second

feature is something I can get behind, improvements for virtual desktops. There is an article on errortools about virtual desktops feature and I really hope you are using it since it is a great feature. Anyway, new update will bring us separate desktop wallpapers for each desktop and we will be able to arrange them in order we like.

Third

thing that I would like to address is animation features. We will have windows slowly fade and resize when opened, minimized, maximized, etc. So far we are unable to tell how this can and will it affect overall system performance. I am sure it will have some impact but hopes are that it will be kept to a minimum. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

In this post, you will be guided on how to import and export the WSL distros in your Windows 10 computer. WSL, also known as Windows Subsystem for Linux, is a compatibility layer needed to run Linux binary executable in Windows 10, as well as the Windows Server 2019. In case you don’t know, when you reinstall or reset Windows 10, all of its configuration data stored with the WSL distros gets deleted. Going back or restoring the configuration can be quite challenging but worry not for Microsoft has already got this covered as you can now import and export the WSL or Windows Subsystem for Linux distros. There are three aspects that you have to deal with when you import or export WSL distros in your Windows 10 computer, such as importing WSL distro, exporting WSL distro, and uninstalling the imported WSL distros. Before you proceed to the instructions provided below, make sure that all your installed distros are updated via Microsoft Store. Once you have this covered, follow the options below.

Option 1 – Import the WSL distro

• Type “command prompt” in the Start Search and from the search results, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, execute this command: wsl --list –all
• The command you entered will list all the installed WSL distros on your computer. And now it’s time for you to import a WSL distro by executing this command: wsl --import <Name of the distro> <Fill path to save the backup .tar file>

Note: In the given command above, replace “<Name of the distro>” with the name of the distro you want to import and replace “<Fill the path to save the backup .tar file>” with the location where you want to save the .tar file.

Option 2 – Export the WSL distro

• Type “command prompt” in the Start Search and from the search results, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, execute this command to see the list of all the installed WSL distros in your computer: wsl --list –all
• After that, execute this command to export a WSL distro: wsl --export <Name of the distro> <Fill path to save the backup .tar file>

Option 3 – Uninstall the imported WSL distro

• Open Command Prompt with admin privileges.
• Next, execute this command to view the list of all the installed WSL distros: wsl --list –all
• After that, execute this command to uninstall an imported WSL distro: wsl --unregister <Name of the distro>
• Once it’s done, close Command Prompt and restart your computer.

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.

If you suddenly receive an error saying, “Error 105 (net:: ERR NAME NOT RESOLVED): Unable to resolve the server’s DNS address” when browsing the web, then this means that the DNS lookup has failed. This kind of error is one of the most commons ones you can encounter while using the Chrome browser. And since it’s a pretty common error, the solutions for this one are pretty easy as well.

Option 1 – Disable both the Antivirus and Firewall temporarily

There are times when antivirus programs and the firewall blocks a website that they consider to be malicious or even because of false-positive effects. Thus, you need to disable these programs temporarily as it might be the reason why you’re getting the “Error 105 (net:: ERR NAME NOT RESOLVED): Unable to resolve the server’s DNS address” error in Chrome.

Option 2 – Check the Network Cables and restart the router then reconnect

Of course, the next thing you have to do is to check if the network cables connected to your computer or router are properly connected. And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.

Option 3 – Try running the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 4 – Try removing the Proxy

Removing the Proxy might also help you in fixing the ERR_NAME_NOT_RESOLVED error in Chrome. Here’s how you can do it:

• 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 5 – Disable Prefetch in Chrome

In case you don’t know, Google makes use of a prediction service that helps users in completing searches and typing URLs in the address bar. This prediction service uses the already resolve IP address to connect to the website you’ve already visited. Thus, it would be better if you disable it in cases like this one.

• Open Chrome’s Settings.
• Next, go to Privacy and Security then look for “Prefetch”.
• After finding Prefetch, toggle off the “Use a prediction service to help complete searches and URLs typed in the address bar” setting and then restart Chrome.

Option 6 – Flush the DNS, reset Winsock and then reset TCP/IP

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

Option 7 – Try using the Google Public DNS

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8” and “8.8.4.4” and click OK and exit.

Option 8 – Reset Chrome

Resetting Chrome can also help you fix the error. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• 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 the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Microsoft starting as of today will block its Office 365 users if they are using Internet Explorer or early versions of Edge browsers. So if you are using older non Chromium Edge versions of Microsoft browsers you can no longer access Office services until you switch. Now normally I would fully support this kind of decision since Internet explorer is a slow and vulnerable browser and the edge is similar in that regard. The new edge browser is great and it should be used but the issue I have is that Office 365 is not free, it is a premium feature and I am wondering how Microsoft plans to deal with people that have already paid for service but suddenly cannot access it anymore.

This post will walk you through fixing the rtwlane.sys Blue Screen error. This kind of BSOD error belongs under the category of the “DRIVER IRQL NOT LESS OR EQUAL” Stop errors. If you encounter this kind of Stop error then it means that a kernel-mode driver tried to access pageable memory at a process IRQL that was too high. The main issue with the rtwlane.sys Blue Screen error has something to do with the Realtek PCI-E Wireless LAN PCI-E NIC driver. In other words, it has some issues with the wireless card of your computer which is built by Realtek. And since it this error concerns your wireless card, you might also experience some connectivity problems with your computer as the wireless card refuses to find any network connections and even randomly disconnects. To resolve this problem, you need to refer to the given options below.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like rtwlane.sys Blue Screen error. 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 2 – Try to update or rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• 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 Network Adapters and expand it.
• From the list of Network Drivers, look for “Realtek <Model> Wireless LAN 802.11n PCI-E NIC” and then right-click on it and select Update Driver.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If you see any of the following entries under the Network drivers, you might want to download their latest available versions from each one of their manufacturer’s websites.

• Realtek High-Definition (HD) Audio Driver
• Realtek Card Reader Driver
• Realtek Local Area Network (LAN) Driver

On the other hand, if updating the Network driver didn’t help, you can also try to roll back to its previous version.

• Open the Device Manager again and then look for Network Drivers.
• Next, select Realtek <Model> Wireless LAN 802.11n PCI-E NIC from the list of Network Drivers and then 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 Realtek driver.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Netwtw04.sys failed BSOD 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 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

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.

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.