System loads BIOS but when loading windows error "C019003f" appears.

[MasterDell]

Hi guys.. I am kind of stumped. I built this rig about 2 months ago and installed an SSD about a month ago. I installed the OS on it. SSD is a crucial M500. So basically all I did today was wired my house with CAT 6 and ditched the cat 5/e. I have been using wireless until today. After all of that, I wanted to try out the CAT 6 and installed the proper drivers for my motherboard. Everything was working fine and for good measures I wanted to restart my computer.

So on the boot of the restart, the BIOS loaded fine and post codes are normal. Once it started to load windows it says "Error C019003F applying update operation 570 of 5815 (Windows Defender)

Motherboard Q-Code is at "A0" which is what it should be at.

OS is Windows 8.1

I am guessing that the SSD is shot. And that is what I am hoping.

 

[Stingerxxx]

If the SSD was shot, most likely you wouldn't be able to get to that point in the boot order. I did a quick google search and found that this error is caused by a file becoming corrupted during the update process. This is an update error, not a SSD error. As such, this simply means that fixing a file will fix the problem.

Possible solutions

Solution 1) Download Hiren's Boot CD and load Mini Windows XP. After this, open the hirens menu that is on the desktop, navigate to the disk menu and select the chkdsk option. A CMD prompt will appear asking you to select the drive. Select the SSD and allow the chkdsk to run. This may or may not fix the problem as the issue is a corrupt file and not a SSD error, but another forum said it would and a user replied that it fixed it for them. So it's worth a shot.

Solution 2) Obtain a WINPE that is designed to repair windows installations and go through the repair process. Some that I use are Paragon (This particular one is a disk that is made from inside of Paragon Hard Disk Manager, it is NOT a free program. It is, however, incredibly useful. Here is the link.) Another is BartPE. I have not used this myself, however it appears to be a powerful PE that is not WinPE but rather a similar environment that has repair options.

Solution 3) Using ANY bootable OS you may be able to replace the corrupt file. From this the .dll file wtsapi32.dll is labelled as the corrupt file that causes this error. Theory states that you would be able to obtain this same .dll from another active, working installation of windows 8.1 and replace the corrupt one with this one. If you do this, make sure to make a copy of the corrupt one as it may not actually be corrupt. This particular solution is virtually risk free, so long as you make the backup. If you replace the .dll and nothing changes, you know that isn't the issue and you can then either leave the transferred one in place or restore the original. Hiren's Boot CD would allow you to do this.

Solution 4) If all else fails, you can reinstall windows using the disk you originally installed it with, or repair the installation using the same disk. Booting from that disk would allow you to do that.

Hope this helps.

 

[MasterDell]

If the SSD was shot, most likely you wouldn't be able to get to that point in the boot order. I did a quick google search and found that this error is caused by a file becoming corrupted during the update process. This is an update error, not a SSD error. As such, this simply means that fixing a file will fix the problem.

Possible solutions

Solution 1) Download Hiren's Boot CD and load Mini Windows XP. After this, open the hirens menu that is on the desktop, navigate to the disk menu and select the chkdsk option. A CMD prompt will appear asking you to select the drive. Select the SSD and allow the chkdsk to run. This may or may not fix the problem as the issue is a corrupt file and not a SSD error, but another forum said it would and a user replied that it fixed it for them. So it's worth a shot.

Solution 2) Obtain a WINPE that is designed to repair windows installations and go through the repair process. Some that I use are Paragon (This particular one is a disk that is made from inside of Paragon Hard Disk Manager, it is NOT a free program. It is, however, incredibly useful. Here is the link.) Another is BartPE. I have not used this myself, however it appears to be a powerful PE that is not WinPE but rather a similar environment that has repair options.

Solution 3) Using ANY bootable OS you may be able to replace the corrupt file. From this the .dll file wtsapi32.dll is labelled as the corrupt file that causes this error. Theory states that you would be able to obtain this same .dll from another active, working installation of windows 8.1 and replace the corrupt one with this one. If you do this, make sure to make a copy of the corrupt one as it may not actually be corrupt. This particular solution is virtually risk free, so long as you make the backup. If you replace the .dll and nothing changes, you know that isn't the issue and you can then either leave the transferred one in place or restore the original. Hiren's Boot CD would allow you to do this.

Solution 4) If all else fails, you can reinstall windows using the disk you originally installed it with, or repair the installation using the same disk. Booting from that disk would allow you to do that.

Hope this helps.

Awesome. Thanks! I will give 1) a shot first and get back to you. May not be for a few hours or even a day until I get to this though

 

[Stingerxxx]

No worries, I'll be hopping on and off like I usually do ^.^