Setting up an FTP Server in Windows

Error Code 0xC1900101, 0x30018? - What is it?

Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:

We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.

0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.

Solution

Error Causes

In attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:

• Incompatible hardware or driver
• Incompatible security programs or antivirus or incompatible utility software
• A device driver possibly stopped responding to setup.exe while on the installation process.

In some cases, you might be opened to other error messages when attempting to update to Windows 10, including error code 8007002c.

Further Information and Manual Repair

In fixing issues related to error codes, it is best to employ manual repair methods. Using these methods helps users pinpoint the root causes of the issue and apply solutions permanently to fix the issues. While most manual repair methods can be done by every Windows user, even those without technical abilities, there are certain cases where help from a Windows professional is needed. If you’re not up to facing risks in implementing manual methods yourself, consider getting help from a professional Windows technician or you can use a powerful automated tool. In fixing Error Code 0xC1900101-0x30018, you can repeat the same steps used for 0xc000021a (Method One) or you can try doing the following:

• Disable or uninstall your Antivirus program before proceeding to upgrade the system
• Ensure that the machine name is simple (having at least 8 characters) with no special characters like hyphens or dashes.
• Restart the device a few times then try again.
• Disable General USB Devices such as the Smart Card Reader.
• If you use an SCSI hard disk, ensure that you have available drivers you can use for your storage such as a thumb drive and make sure that it is connected. During the Windows 10 setup, select the Custom Advanced Option and use the Load Driver command to be able to load the suitable driver for the SCSI drive. If this fails, try switching to an IDE-based hard disk.
• You can now perform a clean boot. Restart your device then try again.
• If you are using the .ISO file for upgrading the system, you need to disconnect from the Internet first before proceeding to the setup. If you are connected to Wi-Fi or by Ethernet (LAN), make sure to disable both connections then you can proceed to set up again.
• If you’re performing the update through Windows Update, once the download reaches 100%, disconnect from the Internet, and then proceed with the installation.

NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.

• Switch to a local account if the device is connected to a domain.
• Disconnect all external devices attached to the computer such as gaming controllers, printers, or USB keys.

If you’re using Windows Update in installing Windows 10, you can implement the following:

1. Open the Command Prompt window by pressing Windows Key + X. Select Command Prompt (Admin) from the menu.
2. Stop the BITS, Cryptographic, MSI Installer, and the Windows Update Services. In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

3. Rename the Catroot2 and SoftwareDistribution In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

                        ren

C:WindowsSoftwareDistribution SoftwareDistribution.old

                          ren

C:WindowsSystem32catroot2 Catroot2.old

4. Restart the BITS, Cryptographic, MSI Installer, and the Windows Update Services. In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

5. Type Exit in the Command Prompt then close the Command Prompt window then restart the computer.

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

Error Code 0x80070057 - What is it?

Error 0x80070057 is a typical Windows 7 error code. It may occur when you try to back up files by using Windows Backup on Windows 7 and the backup fails.  The error message is often displayed as the following:

“An internal error has occurred: The parameter is incorrect: (0x80070057)”

Besides this, you may also experience this error message when you format a hard disk drive to install Windows 7.

Solution

Error Causes

The error 0x8007005 occurs due to multiple reasons. However, the most common causes for this error code include:

• The partition that is reserved for the system is damaged
• Misconfigured registry keys
• Misconfigured decimal symbol settings

Further Information and Manual Repair

Here are some of the best and easy DIY methods to resolve the error 0x80070057 on your PC.

Solution 1: Change the Decimal Symbol Setting

As mentioned above the error 0x80070057 sometimes can be triggered by misconfigured decimal symbol settings. Therefore, try changing the settings to fix the problem. The error is likely to occur if the decimal symbol is not set to ‘.’ (dot). This is common in languages and locales other than English such as German. Here’s what you need to do to change the decimal symbol setting:

• First, open the Control Panel, click the clock, then language, and then region.
• Now click the formats tab and go to the additional settings menu.
• Here you will find the decimal symbol field, now type "." (dot) and then click OK twice.
• After that, you must restart your PC to activate the changes.

Solution 2: Create a New Partition and Reinstall Windows 7

If the error 0x80070057 is linked to partition damage, then this method is the best way to resolve it. Here’s what you need to do:

• Insert the Windows 7 DVD and start the installation.
• Select your language preference to install. Here you will see a screen of the Microsoft License Agreement. Click on the I accept option to proceed with the installation process.

Then click next.

• Choose a custom advance option and select the Disk O partition 1 option.
• Once selected, click delete. When you do this you will be prompted if you want to confirm the deletion, click OK to continue.
• Now repeat the same however now select Disk O partition 2.

Delete this partition as well. Now click New to create a new partition. Here define the disk size and then click apply. Please note, the size of the default value is the maximum size of the disk. After doing so, select disk 0 partition 2 and then click the formatting tab. Once the formatting is complete, click next to continue Now you will be able to complete the installation of Windows 7 on your PC without any problem.

Solution 3: Add a Registry Key Value

If the underlying cause of the error 0x80070057 is a registry issue, then it is serious as such issues can put your PC at serious risks like system failure, crash, and data loss. To resolve this error and add a registry key value here’s what you need to do: Go to the start menu and type Regedit.exe in the search bar and then press enter. Locate and click the following registry sub-key: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftSystem. Once you locate it, now go to the edit menu and point to new, and then click DWORD Value. After that, type CopyFileBufferedSynchronousIo and press enter again. Right-click now on the text you just typed and then click Modify. In the Value data box, type 1 and then click ok and exit the registry editor. This will fix the error on a temporary basis but not permanently. However, a long-term solution is to clean and repair the registry.

Solution 4: Restoro

The registry gets cluttered with unnecessary and redundant files like junk files, cookies, internet history, and bad registry keys. If these are not removed timely, they can damage the registry and corrupt DLL files. It often leads to disk fragmentation (disk partition) too. To remove these files immediately, clean and restore the registry and repair the corrupt files, it is advisable to download Restoro.

Why Restoro

• This is an advanced and highly functional Registry Cleaner. It is deployed with a cutting-edge and intuitive algorithm that scans your entire PC to detect all registry issues in seconds. It cleans the cluttered disk and restores the registry back to normal.
• It is safe, bug-free, and efficient. This software is easy to use and compatible with all Windows versions.
• In addition to this, it is also deployed with several other powerful utilities like an antivirus that detects all malicious software and removes them right away. It also functions as a system optimizer and boosts the speed of your PC significantly.

Click here to download Restoro and resolve error 0x80070057 now!

Device drivers are needed in order for the hardware and software to communicate in an operating system. Some of these drivers are digitally signed. These kinds of drivers are drivers that are signed by their issuing authority in a way that the end-user or any third party won’t be able to modify them. And there are times when you encounter an error that says, “Windows requires a digitally signed driver” when you try to install or update device drivers. Driver Signing is the process of associating a digital signature with a driver package. Digital signatures are used in Windows device installations to verify the identity of the vendor providing the driver packages as well as to verify the integrity of the driver packages. All the drivers you usually install on your PC from Windows Update, Original Equipment Manufacturers, or some other third-party driver download software and so on must be verified digitally by Microsoft through the digital signature. A digital signature is an electronic security mark that verifies the publisher for the driver and all the relevant information related to it. That’s why Windows won’t run a driver if it isn’t certified by Microsoft, be it a 32-bit or 64-bit system – this is called the Driver Signature Enforcement. The only Kernel-mode drivers that Windows 10 will load are the ones that are digitally signed by the Dev Portal. However, the changes only affect the new installations of the operating system with Secure Boot on while the non-upgraded fresh installations would require drivers that are signed by Microsoft. The “Windows requires a digitally signed driver” error indicates that the driver you are trying to update or install hasn’t been signed digitally by the issuing authority, preventing you from installing or updating it. To resolve this issue, you can try to update the drivers directly from the manufacturer’s site. You could also disable driver signing via Group Policy Editor.

Option 1 – Update the device drivers directly from the manufacturer’s site

The reason why you’re getting the “Windows requires a digitally signed driver” error in the first place is that you might have downloaded the drivers from external media. It could also be that the drivers didn’t update for some time now and the issuing authority changed its policies. Thus, you can try to update the drivers straight from the manufacturer’s website and install them. If this option didn’t work, then you’ll have to disable the driver signing or its recognition in Windows 10. Keep in mind that doing so is not advisable if you have to use the concerned driver.

Option 2 – Disable driver signing via Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• After that, navigate to this policy setting: User configuration > Administrative templates > System > Driver installation
• Next, double click on the “Code signing for device drivers” entry located on the right pane to open its properties where you’ll see the following description:

“This setting determines how the system responds when a user tries to install device driver files that are not digitally signed. It establishes the least secure response permitted on the systems of users in the group. Users can use the System in Control Panel to select a more secure setting, but when this setting is enabled, the system does not implement any setting less secure than the one the setting established. When you enable this setting, use the drop-down box to specify the desired response. “Ignore” directs the system to proceed with the installation even if it includes unsigned files. “Warn” notifies the user that files are not digitally signed and lets the user decide whether to stop or to proceed with the installation and whether to permit unsigned files to be installed. “Warn” is the default. “Block” directs the system to refuse to install unsigned files. As a result, the installation stops, and none of the files in the driver package are installed. To change driver file security without specifying a setting, use System in Control Panel. Right-click My Computer, click Properties, click the Hardware tab, and then click the Driver Signing button.”

• Now select the radio button for “Enabled” and select Ignore from the drop-down menu under “When Windows detects a driver file without a digital signature”.
• Then click on the Apply and OK buttons to save the changes made. This will get rid of the “Windows requires a digitally signed driver” error but take note that this will also make your system less secure.

If you receive an error message that says, “Entry point not found, The procedure entry point could not be located in the dynamic link library” on your Windows 10 PC, then you will find this post useful for this will provide you some potential fixes to fix the error. This kind of error can occur if a program fails to locate the DLL library that it needs in order to run. It can also occur if the library is not in the specified directory in the path or if the DLL file has gone missing or has become corrupted. To fix the “The procedure entry point could not be located in the dynamic link library” error, check out the following options given below.

Option 1 – Try to reinstall the program

The first thing you can do to resolve the error is to uninstall the program that throws the error and download its latest version from its official site and then install it again.

Option 2 – Run System File Checker scan

If reinstalling the program 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 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.

 Reboot your computer.

Option 3 – Try checking the details in the Event Viewer

The Event Viewer can also help you resolve the error as it contains detailed information about the error that could help you pinpoint its root cause and resolve it.

Option 4 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 5 – Try to replace the DLL file with a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 6– Try to scan your computer using Windows Defender

It is also possible that the DLL file might be infected with malware or virus which could explain why you’re getting the error. Thus, you have to scan your computer using security programs like Windows Defender.

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

Error Code 80240020 – What is it?

Users who receive Error Code 80240020 when attempting to install and/or upgrade to Microsoft Windows 10, are receiving the error because the Windows 10 installation folder is either corrupted or unfinished. As a result of this error code, your download and the subsequent update will not process correctly. Users who receive this code do not have to do anything specific, as it might mean that they are attempting to update before their system is ready. These users can simply wait for their computer to prompt them for the update, and then follow the on-screen instructions for the update. However, if a user is seriously wanting to update to Microsoft Windows 10 prior to the prompt, there are ways around error code 80240020. Common symptoms include:

• A dialog box appears with the Error Code 80240020
• Microsoft Windows 10 upgrade is unsuccessful or freezes in the process of updating and displays the error code message.

Solution

Error Causes

This error is only caused by one type of issue, and that is unfinished or corrupted files being present in the Windows 10 installation folder.

• Files that are unfinished in the Windows 10 installation folder are a result of the download not processing correctly, therefore the update is not successful because your computer does not have the files that it needs.
• Files that are corrupted in the Windows 10 installation folder are a result of either a faulty download or preexisting corrupted files that need to be purged.

Until your system is ready to download the new Microsoft Windows 10 upgrade, you will be unable to install the upgrade. As stated, you have the option of waiting for your system to prompt you to download (which means that your system has made the necessary changes to its own files and is ready for the upgrade), or you can use the following steps to correct the issue yourself.

Further Information and Manual Repair

Users and Microsoft Tech Support personnel have discovered three methods to correct error code 80240020. Each of these methods should be attempted by someone who is comfortable with computer software and programs. Anyone who is not comfortable with software should either contact Microsoft Support or wait for their computer to prompt them for the Microsoft Windows 10 upgrade.

Method 1:

1. Back up the Registry of your operating system.
2. Find the Registry Key: [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateOSUpgrade]
3. Note: this Registry Key should already exist, if it does not exist, create it.
4. Create a brand new DWORD Value that is named AllowOsUpdate
5. Set the Value to 0x00000001.
6. Close and reopen your Control Panel.
7. Restart the Microsoft Windows 10 upgrade.

Method 2:

1. Download the Microsoft Windows 10 ISO (installation device) from the following website: http://www.microsoft.com/en-us/software-download/windows10
2. Users must select the appropriate ISO, either 32 bit or 64 bit, depending upon their individual computer.
3. Extract the ISO file to a separate USB device or burn the program to a compact disc.
4. Run the Microsoft Windows 10 upgrade directly from the software that you have thus created.

Method 3:

1. Access the files on your computer via MY COMPUTER
2. Under the C: drive, access the WINDOWS folder
3. Select the SOFTWARE DISTRIBUTION folder, followed by the DOWNLOAD folder.
4. Delete any files within this download folder.
5. If you are unable to delete these files, open the command prompt (CMD) as the administrator, and type “net stop wuauserv” into the CMD prompt window. Press ENTER. This should allow you to delete the files from step 4.
6. Once the files are deleted, open and run the CMD as the administrator and type “wuauclt.exe /updatenow”. Press ENTER.
7. Access the WINDOWS UPDATE folder from your control panel, the update and download should resume without further interference from the user.

As with any other error codes, if the above methods do not rectify the issue, it may be necessary to download and install a powerful automated tool to rectify error code 80240020.

In any Windows operating system, Safe Mode is definitely a special environment used for troubleshooting issues as well as system diagnostics. Safe Mode allows you to remove any malware in your computer and troubleshoot issues that can’t be fixed when you’re in desktop mode. This is why Microsoft made sure that the Safe Mode option is not available directly and can only be accessed by pressing function keys such as F2, F8 (depends on what PC you are using) or via MSConfig. To make it easier for you to access Safe Mode, this post will guide you on how you can add Safe Mode to the Boot Menu options in Windows 10. As you know, Windows 10 now has Advanced Startup options that allow you to boot directly into Safe Mode without having to restart your PC and then tapping the special key a couple of times. However, if you really have to always use Safe Mode, it’s best to add it in the Boot Menu options. To do that, simply follow the steps below.

• Select Command Prompt (Admin) option from the WinX menu to open Command Prompt with administrator privileges.
• After opening Command Prompt, type the bcdedit /copy {current} /d "Safe Mode" command and hit Enter.
• Once the command is executed, you will see a message saying, “The entry was successfully copied to {74a93982-9486-11e8-99df-00270e0f0e59}”. This message indicates that Safe Mode was successfully added in the Boot menu option which means that you can now directly access it and boot your Windows 10 PC in that mode.

To check if Safe Mode was really added in the Boot menu options, you have to open Msconfig. From there, you will also have to use it to configure the boot settings for the Safe Mode entry. To do so, follow the given steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “MSConfig” in the field and click OK.
• Next, go to the Boot tab and find the Safe Mode option which should be located under the default Windows 10 mode.
• Afterward, you need to select the Sage boot option and Minimal. You also have to select the Make all boot settings permanent option.
• Make sure to increase the timeout to at least 10 seconds which will ensure that the menu does not disappear right away.

Note: In similar steps as above, you can add the Safe Mode with Networking and Safe Mode with Command Prompt entries as well. Just simply select “Network” for Safe Mode with Networking and “Alternate Shell” for Safe Mode with Command Prompt. Once you’re done adding any of them, click on Apply and restart your PC. In addition, if you wish to remove the entry, you just have to open MSConfig again and select the entry you want to remove, and then click Delete.

Sometimes, some applications after they are installed will put their shortcut in the context menu (right-click on desktop) for easy access, most of the time these are some system tied applications like AMD and Nvidia control panels or archives like WinRAR or 7ZIP but it can happen even for some usual application to do this.

There are some applications that you use frequently and they could be worth putting in the context menu, if you want to avoid clutter on the desktop or in the taskbar this is the third place that you should consider placing shortcuts.

Doing this will require some playing and tweaking in the Windows registry editor so be careful when editing the registry since bad entries can lead to system crash or instability. Follow step-by-step instructions.

Adding apps to the context menu in the registry

Creating entry

Open the registry editor by searching Regedit and pressing enter than inside of the registry editor search for the next key:

HKEY_CLASSES_ROOT\Directory\Background\shell

Select shell and right-click on it, hover over New and in the submenu click on Key. In the next step, you need to name a key, this name will be the thing that will be shown in the context menu when you right-click on a desktop so type in the name that you would like or the name of the application that you wish to add to the menu.

If you wish you can even add a keyboard shortcut to launch this specific application. To do this select entry that you have created and edit the default value, inside the edit string in the Value data field type first & and after that key that you would like as a shortcut. Now after right click if you hit your shortcut key app will be launched right away.

Adding command

The next task is to create a command key that will actually hold the command to launch the application. Right-click on the entry that you have created, hover over New, and click on Key.

Next, you’ll need to create the command key that will actually hold the command used to launch the application. Right-click on the new Notepad key, and then choose New \ Key from the menu. Name this key 'command', all in lower case and without hyphens.

Now in order to finish setting the launcher, you need the full path of the file that you would like to run. Locate your file in file explorer or in another tool and copy its path by SHIFT + right-clicking on the file itself and choosing copy as path option.

Now click on the command key and double click on the default key on right to edit it, inside the field value data paste your path to executable. close and save the registry and you are done.

Portable small Bluetooth speakers are nothing new on the market, most of the time they have given the opportunity for music listening during picnics and walks in nature and also replaced some car speaker systems. The latest star in small portable speakers in JBL Clip 4, small in size, waterproof, and with an incredible high-quality sound.

Performance and quality

Out of the box and after first look speaker looks great, it has excellent design and is very intuitive to work with. Everything is laid out logically and you can start using it right away without reading instructions.

The sound quality is surprisingly very good and clear. I must say I have not expected this clarity and power from a speaker of this size. The volume range is also incredibly good and will fill most needs even on small picnics outdoors where you can hear it loud enough. One thing to mention is that even on their loudness levels sound is still clear without distortion which, to be honest, is to be expected from someone like JBL.

Where you can take JBL Clip 4

You can take it where ever you want, Its size and clip make it perfect for beach and pool trips. Speaker is waterproof and gas IP67 rating, meaning that sand and dirt will not affect it either. Do not take this speaker to your diving adventures since that will break it but a depth around 1 meter underwater should be safe. After your trip do not forget to wash Clip 4 with clean water so all dirt, salt, and other stuff are properly cleaned for longer life of the device.

How long it will play?

JBL claims that the battery will last 10 hours of continuous play. Note that this is meant probably on the largest volume setting so when you use it on lower settings battery is lasting longer. Playing of course on low volumes will extend playback time even longer but here we come at one feature that I do not like, there is no indication of any kind how much battery is left in the speaker, the only indication is a red light when the battery is almost empty which means you could be outside at that point and did not know that low battery was there in the first place when you were packing. Some battery indication would be a great addon.

More stability for JBL Clip 4

The clip itself has been improved from the previous Clip 3 model, it is wider, it goes all the way around the casing, and feels overall better and more stable. Since the clip is now all around casing this means a wider opening can be made making it fit around stuff Clip 3 was not able to.

Conclusion

All in all, Clip 4 is an incredible speaker and one that would highly recommend, the price goes around 79 USD but it can be found even as low as 50 USD on discounts and promotions and if you manage to get one at that price it is a great buy. Sound is good, portability is great, dirt and waterproof are excellent and battery life is really good.

One of the common causes of Blue Screen of Death or BSOD errors is system driver files due to varying reasons. So if you encounter a Stop error caused by some system driver files such as isapnp.sys, gv3.sys, storahci.sys, or myfault.sys, on your Windows 10 PC, then this post should help you fix the problem. These system driver files are associated with different error codes. The isapnp.sys file is related to the following error codes:

• SYSTEM SERVICE EXCEPTION
• PAGE FAULT IN A NONPAGED AREA
• KERNEL DATA INPAGE
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED.

While the gv3.sys file is related to the following BSOD error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

On the other hand, the storahci.sys file is related to these error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

And the myfault.sys file is associated with this error code: SYSTEM SERVICE EXCEPTION. Although this system driver file causes different kinds of Blue Screen errors, some of their potential fixes are quite the same so you need not carry out tons of troubleshooting steps. But before you troubleshoot the problem, you might want to check out System Restore first, especially if you create a System Restore point from time to time. To perform System Restore, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first and boot your computer into Safe Mode.

Option 1 – Use the System Configuration utility

Note that this first fix is only applicable for Blue Screen errors associated with the myfault.sys file.

• In the Cortana Search box, type “MSConfig” and click on the “System Configuration” entry to open it.
• After opening System Configuration, go to the Processes tab.
• Then scroll down and look for the “Digital Line Detection” process and disable it.
• Now restart your computer and check if the Stop error is fixed or not.

Option 2 – Try to update, rollback or disable related device drivers

Incompatible and outdated drivers can also cause computer malfunctioning or crashing as well as Blue Screen errors. To fix that, you can update, roll back or disable the device drivers in your computer.

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• After opening the Device Manager, from the list of device drivers, look for the “WIN ISA Bus Driver” if you are facing a Stop error related to the isapnp.sys file. While you have to look for the Sony Recovery CDs PCG-Z1RAP Series device drivers if you face a Stop error concerning the gv3.sys file. For the storahci.sys, on the other hand, look for any outdated drivers and update them.
• To update or roll back or disable these drivers, just right-click on each one of them, and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the Blue Screen error.

Option 3 – Use System File Checker

One of the built-in tools in Windows that you can use to fix Blue Screen errors is the System File Checker. This built-in command utility can help you restore corrupted or missing files as well as replace bad and corrupted system files. Chances are, any of the aforementioned system driver files might be corrupted so to fix them, use System File Checker.

• First, right-click on the Start button and click on the “Command Prompt (Admin) option.
• Next, type in the sfc /scannow command and hit Enter to execute it.

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.

• Now restart your computer.

Option 4 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors. You can find it in Settings, under the 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.

When performing a Windows Backup to the NAS device (backup to a network share) that is running Samba, fails with an error message The backup failed, The version does not support this version of the file format (0xC03A0005). The problem occurs because of a conflict with the VHD file that is created by Windows Backup and is mounted during the process. There are three types of VHD files:

1. Fixed,
2. Expandable
3. Differencing

If the VHD file is a sparse file that is not supported by the native VHD driver, the mounting will fail, and you will get this error. An example VHD file is one that keeps expanding depending on the backup size. The problem occurs only in the case of  File Level backup (file/folders in a volume) but not on the block level backup as the vhd file is never mounted. However, in the case of File Level Backup, the vhd is mounted, created by Windows Backup, which does not support the mounting of sparse files.

The solution is to use Strict Allocate: option in the smb.conf file

Login to SMB using SSH. Open the configuration file using the VI editor located at /etc/samba/smb.conf. If the option is not there, you can manually add strict allocate = yes which will make sure there are no sparse file that is created.