A Simple Guide to Fixing Error Code 0x80070424

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.

JavaScript Void 0 Error - What is it?

JavaScript is a computer programming language used to make a website work smoothly with the internet. It helps to display visual effects, animations, and other web page functions. You may come across the JavaScript Void (0) error message when there is a problem in loading JavaScript from a web page or the internet browser.

Error Causes

JavaScript Void (0) error is triggered by multiple reasons such as:

• It can be due to a simple random Windows application glitch.
• You are visiting an unsafe website that contains malware
• JavaScript’s web browser implementation  is broken due to poor program installation
• Active X controls, Java applets, and active scripting, the key components of JavaScript are disabled
• Registry issues like invalid or misconfigured registry keys

Further Information and Manual Repair

For JavaScript Void (0) error-free web surfing, it is advisable to repair the issue without any delays. Let’s take a look at different methods to resolve this error on your system.

Cause: Simple Random Glitch

Solution: If the cause for the JavaScript Void 0 error is a simple glitch, then it is advisable to restart your system and then run the program again.

Cause: JavaScript’s web browser implementation is broken

Solution: If you experience the JavaScript Void 0 error message after the installation of the new browser on your system, then poor installation of the program or program conflict is most likely to be the deep-rooted cause of this error code. To resolve it, uninstall the program and undo the recent changes.

Cause: Active X controls, Java applets, and active scripting, the key components of JavaScript are disabled

Solution: You should know that components including Active X controls, Java applets, and active scripting are all essential to JavaScript in order to make your browsers run properly. If these are disabled, you may come across the JavaScript Void (0). To fix it open your browser and select the Tools tab. Then click the options button and select content. Here check the ‘enable JavaScript’ check box and click Ok to enable these components.

Cause:  Registry Issues

Solution: If after performing all the solutions discussed above, you still come across JavaScript Void (0) error code, then you should know that the problem is bigger than what you expected. It triggers registry issues. Either the cause of the error is misconfigured or invalid registry keys. To reconfigure the registry keys setting may be a challenging task and complex if you are not a computer programmer.

DirectX encountered unrecoverable error usually face gamers when they try to star certain game. In this guide, we will help you to get over it and solve the issue. Follow steps in this guide one after another since they go from most simple ones to complex ones so following is advised in order not to waste a ton of time and resources doing wrong tasks.

1. Check your game page and your DirectX

   The first and most common thing that can cause this type of error is when your installed DirectX is not the same version that the game requires. Check the game store page to see system requirements and write down which DirectX version it requires in order to run. Then press ⊞ WINDOWS + R to bring run dialog and type in it DXDIAG and press ENTER DX diagnostic window will pop up and at the bottom, you can find which DirectX version is installed on your system. If versions are different, install the required DirectX version and run the game.

2. Update or reinstall GPU drivers

   DirectX can get corrupted via bad driver update, in order to fix this, reinstall or update your Graphic drivers to the latest version from the official manufacturers' website.

3. Set custom scaling to 100

   Go into Windows settings and set custom Display scaling to a value of 100, sign out, and then sign back in.

4. Delete registry key

   Note that you should do this as the last option and be very careful since you can crash whole Windows in this way. Press ⊞ WINDOWS + R to open the run dialog and type RegEdit in it to open the registry editor. Find this key: ComputerHKEY_CLASSES_ROOTPROTOCOLSFiltertext/XML and delete it from the registry, you might want to do a backup of the registry first, just in case.

In the Windows ecosystem, MS Surface laptops are among the best laptops on the market, they are regarded as equivalent to Apple MAC laptops but for Windows. Microsoft Fall 2022 Event will be held on October 12th at 10 AM. The event itself will be held right before it kicks off its annual, developer-focused Ignite event in Seattle from that same day through October 14.

This event is the first in-person event that Microsoft has held since the beginning of the pandemic. We expect the launch of the Surface Pro 9 and the Surface Laptop 5, and maybe Surface Studio 3 as well. There are also some rumors about products themselves like choices between an ARM or x86 CPU but nothing is confirmed so far, we can just wait and see.

One of the most important User Interface elements in a Windows 10 operating system is the Start Menu. Not too long ago, Microsoft has added some new features and redesigned the Start Menu a couple of times as well. Thus, it is not uncommon for Windows 10 users to use several monitors. That’s why in this post, you will be guided on how you can move the Start Menu to your second monitor in Windows 10. There are a lot of advantages in using more than one monitor like a better and widescreen as well as help in improving and increasing productivity. Usually, the Start Menu and the taskbar is present in the original monitor only. In most cases, it helps users in moving the Start Menu to the second monitor and helps users in segregating tasks, and uses separate monitors for each kind of task. There are two simple steps to move the Start Menu to the second monitor. You have the option to unlock and drag the taskbar, as well as make adjustments in the settings. To get started, refer to each one of the following options to move the Start Menu to the second monitor.

Option 1 – Move the second monitor by unlocking and dragging the taskbar

The first option you can try to move the Start Menu to the second display is to simply unlock and then drag the taskbar. To do so, follow these steps:

• First, click on the Taskbar and unlock it.
• Next, uncheck the Lock the taskbar feature in the menu of the Taskbar Settings. This will free the taskbar so you can move or drag it around.
• After that, push the Start Menu to the furthermost corner of the screen and then transfer it to the second monitor.

Option 2 – Move the second monitor using the keyboard

• The first thing you have to do is to tap the Windows key to open the Start Menu.
• Next, close the Start Menu by tapping the Esc key.
• After that, the controls will shift back to the taskbar.
• Now open the context menu of the taskbar by tapping the Alt + space bar together. This will move the Start Menu to the second monitor.

Option 3 – Move the Start Menu to the second monitor via Settings

If you find that the Taskbar is moving to the wrong monitor automatically or if the program does not start on the same monitor as the taskbar, then you can try this option.

• Click on Start first and click Run.
• Then type “desk.cpl” in the field and click OK.
• Alternatively, you could also right-click on the desktop and select the Screen Resolution option from the drop-down menu.
• After that, click on the monitor that you want to use as the primary monitor and select the checkbox labeled “Make this my main display”.
• Once done, you have to choose the “Show desktop” on only 1 from the drop-down menu of Multiple displays.
• Now click the Keep Changes option and select the Extend these displays from the Multiple displays drop-down menu and then click on the Apply button to save the changes made.
• Afterward, click the Keep changes option once the dialog box pops up.

What Is Error 1713?

Error 1713 is essentially a programming error. It has specifically been designed in Microsoft applications. This is intended to allow customers to continue using the appropriate setup tool. The error can be quite annoying and is used by manufacturers to determine what caused the error so that counteractive methods can be employed. The number 1713 is simply the hexadecimal code that informs where the instruction was loaded when the error occurred.

Solution

Error Causes

As far as the causes of Error 1713 are in question, the primary cause is damaged, misconfigured, or corrupt windows system files. There are several other factors that lead to the occurrence of Error 1713. For instance, if the applications or hardware on your system has been improperly deleted, installed, or uninstalled, Error 1713 will occur. Similarly, Error 1713 is triggered when the computer has recovered from an attack by some virus, spyware, malware, or adware only recently. This attack corrupts the file and so the error appears. Incorrect system shutdown can also be blamed for this error. All the scenarios listed above actually damages the registry entries in Windows system files. The corrupt or damaged files will then lead to improperly linked or missing information. It goes without saying that such problems will keep the applications from performing in the desired manner and this makes it even more crucial to fix this error as soon as it appears.

Further Information and Manual Repair

Two of the most useful workarounds for Error 1713 are listed below.

• This solution is for advanced users. Restart your computer. Log on to it as the admin in the safe mode. Now go to the Start button and follow this path All Programs-> Accessories-> System Tools->System Restore. Now an option will appear asking you to ‘Restore your computer to an earlier time’. Select it. This option will actually appear in a new window. Click Next. A list of restore points will be displayed to you. Select the most recent restore point before the occurrence of the error and press Next. Now click on the Next button that appears in the confirmation window. Restart your computer as soon as the restoration is finished.
• This solution is for novice users. Download a 1713 repair utility available online. Install this program and use it to scan your system. After the scan is complete, click on repair to fix the error.

It seems that Microsoft is going to offer subscription and sales of individual office applications in the Windows Store. The office package will still be available as a package but for the first time, we will get single applications as standalone ones available for purchase. This is a very interesting decision by Microsoft and I fully support it, this time users will be able to pay less and to choose only applications that they need instead of paying for the whole package and not using it.

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.

The Event Viewer in the Windows operating system is used to troubleshoot any computer issues. It is one of the most useful tools that keep logs of both security and system events. It also monitors for both software and hardware problems in the computer. This tool is the only one with amazing features that maintain logs about everything that’s going on in the computer system. It keeps track of all the information to the point where going over them will take a lot of time. Luckily, the Event Viewer tool now allows users to create custom views where you can set the filters and sort the data recorded to limit the information details to only what you’re interested in seeing. For instance, if you want to troubleshoot with one hard drive, you can just create a special custom view to display only the hard drive warnings in the security logs. This will save you hassle and time. Take note that the logs in the Event Viewer are divided into two main categories namely the Window logs and the Application and Services logs. You can just set the filter to the logs by their event id, specific date, and many other events when you have to troubleshoot some problem in your computer. So if you are trying to troubleshoot a problem in your Windows 10 computer and you’re checking the Event Viewer, read on as this post will guide you in creating custom event views in the Event Viewer. To get started, refer to the instructions given below. Step 1: Go to the Start menu and in the search box, type “event viewer” and then click on Event Viewer from the search results to open it. Step 2: After opening Event Viewer, click on Custom Views located in the left pane of the window. Step 3: Next, click on the Administrative events under the Custom View to create special log views. Step 4: Then on the right side of the window, click on Create Custom View to open the Create Custom View window. Step 5: There is a logged drop-down list under Filter. From there, you have the option to choose an appropriate predefined time or use a custom time range for your Custom log views. Step 6: After that, select an appropriate event level for your custom view. You have fine entry-level options to choose from such as critical event level, error, warning, information and verbose.

• Critical – select this if you want to see the events that require your immediate attention in the custom view.
• Error – select this if you want your Event Viewer to display the events that are less critical but hints at the problems.
• Warning – select this event-level if you want to see the event with the potential problem but may not bound to happen.
• Verbose – select this if you want to see detailed information about all the events.

Step 7: After you’ve selected the event level, you now have to select how you want the events to be filtered. They can either be filtered By the log or By the source.

• By the log – you can select two options called Windows log and, Application and Service logs. The Windows logs allow you to filter the logs created during events like setup, security, applications, and system events. While the Application and Service logs filter the log created by the installed applications in your system.
• By the source – select this if you want your Custom View to search for information in event sources. It allows you to view events in detail for various applications and devices.

Note: You have the option to further customize the event logs with more filters like Event IDs, task category, keywords, User, and Computer. Using these additional filters, you can choose to filter the events in the special views by specifying event id numbers in the Event IDs, entering predefined Windows words in the Keyword, specify the user accounts in the User field, as well as choose the system from the server to maintain logs in the Computer field. Step 8: Once you’re done customizing the log filter, click on OK to apply the changes made. Step 9: After that, a Save Filter should be displayed in the Custom View window. Just enter the Custom View name and select the Event Viewer folder where you want to save the Custom view. The folder name should be Custom View by default. And if you want, you can also create your own folder if you want your custom views to be visible to all the system users. Step 10: Next, check all the Users box located in the lower corner of the window and then click the OK button after you’re done. You should now see the customized filter you just created on the left side of the window. Just click on it to check your filtered events in the center of the Event Viewer window. And for you to save the custom view logs, simply right-click on the Custom views you created and then click on Save All Events in the Custom View As from the drop-down menu. Then put a name on the file and select the appropriate location where you want to save the logs and click on the Save button. Note that the log file is saved with the “.EVTX” file extension and when you double click on it, it will open the file in the Event Viewer.

What is Error Code 29?

Code 29 is a Device Manager error commonly seen whenever a hardware device driver reports a problem. This error code indicates that the resources needed for operation are not available.

The computer hardware basically requires drivers to interface with the operating system. Drivers comprise multiple components and are supplemented with other resources provided by the BIOS (a physical chip on the motherboard).

The BIOS contains a set of basic input and output instructions for the computer system to boot, load drivers, and more.

Its firmware provides resources that drivers require to interface with other essential components. However, when the firmware fails to provide the requested resources, the device drivers stop functioning; this results in error codes like code 29.

Error code 29 is usually displayed in the following format:

“This device is disabled because the firmware of the device did not give it the required resources” Code 29

Solution

Error Causes

Error code 29 may be triggered due to several reasons. These include:

• Outdated drivers
• Corrupted drivers
• BIOS misconfiguration
• The device firmware is corrupt
• Previous attempt to update the driver failed

To avoid inconvenience and to ensure your computer keeps working at its optimal pace, it is recommended that you repair error code 29 on your PC immediately. Delay may limit you from using certain hardware attached to your system properly.

Further Information and Manual Repair

To repair error code 29, you don’t have to hire a professional and spend hundreds of dollars. Here are some quick and effective DIY methods that you can try to resolve this issue in minutes even if you don’t have any technical background.

Method 1 - Reboot Your PC

Sometimes, error codes like code 29 may pop up on your computer screen due to some temporary glitch with the hardware. Rebooting can resolve the issue easily.

Therefore, before you do anything, try restarting your PC. It could be all you need to repair code 29. However, if the error code continues to persist, try the other methods given below.

Method 2 - Clear the CMOS

This may sound technical but it isn’t. To begin, with CMOS is an acronym for Complimentary Metal Oxide Semiconductor.

It is a term that is used to describe motherboard memory that contains the BIOS settings. Clearing CMOS helps reset the BIOS settings to their default manufacturer levels. It’s easy to do and is an effective troubleshooting step to resolve error code 29.

To do this, simply:

1. Enter the BIOS setup utility  by restarting your PC
2. Watch for an entering setup message
3. Enter the BIOS access key. Usually, the key is F2 or F12. However, the key may differ from manufacturer to manufacturer. You may want to check the manufacturer’s website first to find out the BIOS access key before you restart your PC.
4. ‘Reset BIOS settings’ to their default factory levels.

Method 3 - Enable the Device in the BIOS

Error code 29 may appear if a device is disabled. In such a scenario, simply follow the same steps as discussed in method 2, and in the advanced BIOS settings, look for disabled devices.

Enable the devices in the BIOS so that you use them easily.

This will hopefully resolve the issue. If it doesn’t, then this means the error code 29 is caused by either corrupted or outdated drivers. Try method 4 to resolve this issue successfully.

Method 4 - Identify the Problematic Device Drivers and Update them

Whether the error code 29 is caused by a misconfigured, corrupted, or outdated driver, simply update the new driver version to resolve. When doing it manually, you will first have to find and identify the problematic device drivers in the Device Manager.

You can access the Device Manager by going to the start menu and then simply typing Device Manager in the search bar.

Access the Device Manager and the properties to identify problematic drivers. Problematic drivers are normally displayed with a yellow exclamation mark.

Once you have spotted problematic drivers, simply update new drivers to resolve them. Though there is nothing technical about it but it may be time-consuming.

Method 5 - Install Driver Assist to Update Drivers Automatically and Regularly

A good alternative to manual driver update is DriverFIX. Simply download and install DriverFIX on your PC to update all problematic drivers in seconds. This is a cutting-edge program designed to resolve all kinds of device driver problems.

It is user-friendly and compatible with all Windows versions.

The intelligent programming system deployed inside this software program enables it to identify and detect all problem drivers automatically thereby sparing you from the hassle.

Furthermore, it also matches the drivers with the latest and compatible versions and updates them on a regular basis.

It takes the guesswork out of finding misconfigured and corrupted drivers and fixes driver-related problems and error codes like code 29 right away.

Click here to download DriverFIX to repair Device Manager error code 29 on your system without any hassle.