Код ошибки 0x0000001e 0xffffffffc0000005

Symptoms

A computer that is running an x64-based version of Windows Vista Service Pack 2 (SP2) or of Windows Server 2008 SP2 crashes when you do one of the following:

• Restart the computer

• Restart the computer and then access the computer immediately by using Remote Desktop Protocol (RDP)

When this issue occurs, you receive the following Stop error message:

STOP: 0x0000001E : (ffffffffc0000005, fffff8000253254e, 0, ffffffffffffffff)

KMODE_EXCEPTION_NOT_HANDLED

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

• Windows Vista SP2

• Windows Server 2008 SP2

For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Vista and Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only «Windows Vista» is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows Vista» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

  Version	Product	SR_Level	Service branch
  6.0.600 2. 22xxx	Windows Vista and Windows Server 2008	SP2	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 and for Windows Vista» section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

File name	File version	File size	Date	Time
Ntoskrnl.exe	6.0.6002.22769	4,687,744	02-Jan-2012	19:02

For all supported IA-64–based versions of Windows Server 2008

File name	File version	File size	Date	Time
Ntoskrnl.exe	6.0.6002.22769	9,467,776	02-Jan-2012	18:56

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

File name	Amd64_0008955fda6a61834f47167e4a72a9b2_31bf3856ad364e35_6.0.6002.22769_none_9a392678a881a374.manifest
File version	Not applicable
File size	701
Date (UTC)	02-Jan-2012
Time (UTC)	19:09
File name	Amd64_fddd00871cf4ef8337f014c9b59e896f_31bf3856ad364e35_6.0.6002.22769_none_ca860069f526bf7d.manifest
File version	Not applicable
File size	721
Date (UTC)	02-Jan-2012
Time (UTC)	19:09
File name	Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.22769_none_ca873fff82eceaa0.manifest
File version	Not applicable
File size	17,282
Date (UTC)	02-Jan-2012
Time (UTC)	19:09
File name	Amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.22769_none_e254d7f1fd31f53a.manifest
File version	Not applicable
File size	7,656
Date (UTC)	02-Jan-2012
Time (UTC)	16:42

Additional files for all supported IA-64–based versions of Windows Server 2008

File name	Ia64_a302384169c89db92d7839dbcfc014c4_31bf3856ad364e35_6.0.6002.22769_none_7881185c3989e5d6.manifest
File version	Not applicable
File size	699
Date (UTC)	02-Jan-2012
Time (UTC)	19:09
File name	Ia64_fcf10df18fb062991b33021e50f30ffa_31bf3856ad364e35_6.0.6002.22769_none_59f4ece2752331d6.manifest
File version	Not applicable
File size	719
Date (UTC)	02-Jan-2012
Time (UTC)	19:09
File name	Ia64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.22769_none_6e6a4871ca8d8266.manifest
File version	Not applicable
File size	17,606
Date (UTC)	02-Jan-2012
Time (UTC)	19:09
File name	Ia64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.22769_none_8637e06444d28d00.manifest
File version	Not applicable
File size	7,655
Date (UTC)	02-Jan-2012
Time (UTC)	15:33

Is your screen shows you this blue screen when you installing software or updating the Windows system? Don’ worry, you’re not alone. Many Windows users have reported this 0x0000001E blue screen error. Fortunately, it’s usually not too hard to fix.

Back to normal system

The first thing to do when you meet 0x0000001E error is to restart your computer and make it back to the normal Windows system.
How: Hold your Power button for about 5 seconds to restart your computer.
If you can’t reboot your computer into normal mode in this way, you need to boot into safe mode. After that, restart the computer to see if the system has returned to normal.

Try these fixes:

There’re 7 fixes that have helped many users solve their problems. You don’t have to try them all; just work your way down the list until you find the one that works for you.

1. Check your RAM
2. Roll-back your driver
3. Update your driver
4. Uninstall the newly installed software
5. Repair system files
6. Clear any existed viruses
7. Disable/Uninstall antivirus software
8. Restore from a restore point
9. Reset or reinstall Windows

---

Fix 1: Check your RAM

The reason for this 0x0000001E blue screen error is mostly caused by poor contact, defective or mismatched RAM (Random Access Memory).
You can physically or use the Windows Memory Diagnostics Tool to check your RAM.

1) Plug your RAM in and out to make sure it has been installed properly and steadily.
Clean your RAM if it’s dusty. And don’t forget the RAM slot.

2) Reboot your computer to check whether the problem exists.
If not, use the Windows Memory Diagnostics Tool to check for any memory problems.

3) On your keyboard, press the Windows logo key + R together to open the Run box.

4) Type “mdsched.exe” and click OK.

5) Click Restart now and check for problems.

The result can lead to two situations:

A: You RAM has no problem. Then move to the next method.

B: The test result indicated that the computer is suffering from a bad memory. You should replace your RAM with a new one.
Then restart your computer and check to see the blue screen will appear or not.

Fix 2: Roll-back your driver

Sometimes the latest version of the device driver doesn’t work properly on your system and starts interfering with the computer’s normal start-up process.
If this is the cause of the 0x0000001E error, simply roll back your driver to the previous version to resolve the issue.

In the steps below, we use the graphics driver as an example to demonstrate. You can follow the steps to roll back the driver you think needs to be rolled back.

1) On your keyboard, press the Windows logo key and R together to invoke the Run box.

2) Type “devmgmt.msc” and click OK.

3) In the Device Manager, click the Display adapters, then right-click on your display device software and click Properties.

4) Under the Driver tab, click Roll Back Driver, then follow the on-screen instructions to finish the process.

Note: If the Roll Back Driver option grayed out, you can download a previous driver from the manufacturer’s website and install it on your PC, or try the Method 3.

5) Restart your computer, and see if the blue screen error is fixed or not.

Fix 3: Update your driver

If the roll-back driver does not resolve this issue, you may have used the wrong driver or an outdated driver.
There are two ways you can get the right drivers: manually or automatically.

Manual driver update – You can update your driver manually by going to the manufacturer’s website, and searching for the most recent correct driver. Be sure to choose only drivers that are compatible with your Windows version.

Automatic driver update – If you don’t have the time, patience or computer skills to update your video and monitor drivers manually, you can, instead, do it automatically with Driver Easy. Driver Easy will automatically recognize your system and find the correct drivers for your device, and your Windows version, and it will download and install them correctly:

1) Download and install Driver Easy.

2) Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.

3) Click the Update button next to the selected driver to automatically download the correct version of that driver, then you can manually install it (you can do this with the FREE version).

Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system. (This requires the Pro version which comes with full support and a 30-day money back guarantee. You’ll be prompted to upgrade when you click Update All.)

4) Restart your computer and check the blue screen problem is fixed or not.

Fix 4: Uninstall the newly installed software

Sometimes the third-party software that is not compatible with your system can cause the blue screen error. Uninstalling the newly installed software will resolve this issue.
In the steps below, we use the GALAX GAMER RGB as an example to demonstrate. You can follow the steps to uninstall the newly installed software on your computer.

1)  Click the Windows start button (if you hide the search field), type “control panel” in the search box, and click Control Panel.

2) Choose to view by Category and then click Uninstall a program.

3) Find your newly installed program. Right-click on it and click Uninstall.

4) Follow the on-screen instructions and restart your computer to check the blue screen will appear or not.

Fix 5: Repair system files

When the system files were broken or corrupted, it may cause the Stop: 0x0000001E Blue Screen Error. There are 2 ways to scan and repair system files:

• Option 1- Automatically (Recommended)
  Use a repair tool to check various areas in your computer to determine the cause of Windows common issues. It will deal with issues related to system errors, critical system files and find the right fix for you.
• Option 2 – Manually
  System File Checker is a built-in tool to check for corrupt, damaged system files and manage to restore them if there’re any. However, this tool can only diagnose major system files, and won’t deal with damaged DLL, Windows Registry key, etc.

Option 1 – Automatically (Recommended)

Fortect is a computer repair software that can diagnose problems on your computer and fix them immediately.

It is tailored to your specific system and is working in a private and automatic way. It will first check hardware-related issues to identify problems, and then security issues, and finally it detects programs that crash, missing system files. Once complete, it will find a solution to your specific problem.

1. Download and install Fortect.
2. Open Fortect and click Yes to run a free scan of your PC.
   
3. Fortect will scan your computer thoroughly. This may take a few minutes.
   
4. Once done, you’ll see a detailed report of all the issues on your PC. To fix them automatically, click START REPAIR. This requires you to purchase the full version. But don’t worry. If Fortect doesn’t solve the issue, you can request a refund within 60 days.
   

The Pro version of Fortect comes with 24/7 technical support. If you need any assistance, please contact Fortect support:
Email: support@fortect.com

Option 2 – Manually

1) On your keyboard, press the Windows logo key and R key at the same time to invoke the Run box.

2) Type cmd and press Shift+Ctrl+Enter together on your keyboard to open Command Prompt in the administrator mode.

Note: Do NOT click OK or just press the Enter key as that won’t allow you to open Command Prompt in the administrator mode.

3) Type sfc /scannow (or copy-paste) and press Enter. Then wait for the verification is 100% complete.

4) Restart your computer to check the blue screen issue is fixed or not.

If the result indicates there are broken files but SFC can’t fix them, you can turn to Deployment Image Servicing and Management (DISM) Tool for deeper examination and repair.

Fix 6: Clear any existed viruses

The 0x0000001E Blue Screen Error could also be caused by a virus attack.
So run your antivirus software to do a security scan and clear existed viruses or malware. Be sure that your anti-virus software has been updated to the latest version.

Fix 7: Disable/Uninstall antivirus software

The 0x0000001E blue screen error may also be caused by the conflict between your antivirus software and the system. Therefore, disabling or uninstalling the antivirus software and then restarting your computer can help you solve the error.

If this method resolves the problem, you can install another antivirus software to protect your computer. But if you are fond of the old one, contact the vendor of your antivirus software and ask them for advice.

IMPORTANT: Be extra careful in using the Internet after uninstalling/disabling your antivirus software.

Fix 8: Restore from a restore point

If you can’t figure out which software or driver caused this blue screen error and your computer was fine a few days ago, you can restore your system back to a previous restore point.
This will roll back all the device drivers and software updates to the condition when you created the restore point.

Note: System restore will affect system files but won’t affect your personal files. Some of the files stored on your system may get overwritten by the previous files. So it is recommended to perform a backup before performing the system restore process.

1) On your keyboard, press the Windows logo key + Pause together, then click System protection.

2) Click System Restore.

3) Click Next and it will open the below window.
Choose a restore point where the Windows didn’t show any errors. Then follow the on-screen instructions to finish the process.

4) Restart your computer to check the blue screen will appear or not.

Fix 9: Reset or reinstall Windows

If all else fails, you may have to reset Windows, or maybe even reinstall it together. We all know reinstalling will delete all the data on your hard drive, you have to back up all your important files before doing it.
However, with Fortect, there’s no need for lengthy back-ups, support phone calls, or risk to your personal data. It can reset Windows to the state exactly when it was just installed without affecting third-party software.

But treat these options as a last resort, because they both take quite a long time.

---

We hope you find these techniques useful. You’re welcome to leave comments and questions below.

Здравствуйте!

Проблема BSOD замечена в следующем…Например комп работает весь день, вечером выключаю его, а при включении выдаёт ошибку STOP: 0x0000001E(0xFFFFFFFFc0000005,0xFFFFFA800AACBAF0,0x0000000000000000,0x0000000000000038). Это длится уже на протяжении месяца. Оперативку проверял, ошибку не выдает. Дорогие друзья! Посоветуйте, помогите советом. P.S. Заранее благодарен. Инфа о компе прикреплена…

Здравствуйте!

Проблема BSOD замечена в следующем…Например комп работает весь день, вечером выключаю его, а при включении выдаёт ошибку STOP: 0x0000001E(0xFFFFFFFFc0000005,0xFFFFFA800AACBAF0,0x0000000000000000,0x0000000000000038). Это длится уже на протяжении месяца. Оперативку проверял, ошибку не выдает. Дорогие друзья! Посоветуйте, помогите советом. P.S. Заранее благодарен. Инфа о компе прикреплена…

Здравствуйте!

Проблема BSOD замечена в следующем…Например комп работает весь день, вечером выключаю его, а при включении выдаёт ошибку STOP: 0x0000001E(0xFFFFFFFFc0000005,0xFFFFFA800AACBAF0,0x0000000000000000,0x0000000000000038). Это длится уже на протяжении месяца. Оперативку проверял, ошибку не выдает. Дорогие друзья! Посоветуйте, помогите советом. P.S. Заранее благодарен. Инфа о компе прикреплена…