Video_driver_init_failure Windows 10

  1. Windows 10 Iso
  2. Video Driver Init Failure Windows 10
  3. Windows 10 Blue Screen Video_driver_init_failure
Error Number:Error 0xB4
Error Name:VIDEO_DRIVER_INIT_FAILURE
Error Description:The VIDEO_DRIVER_INIT_FAILURE bug check has a value of 0x000000B4. This indicates that Windows was unable to enter graphics mode.
Hexadecimal:0x000000B4
Developer:Microsoft Corporation
Software:Windows Operating System
Applies to:Windows XP, Vista, 7, 8, and 10

Symptoms of VIDEO_DRIVER_INIT_FAILURE Blue Screen Errors

A problem has been detcted and Windows has been shut down to prevent damage to your computer. The Video driver failed to initialize. If this is the first time you have seen this Stop error screen. BSOD errors emerge in any version of this operating system including Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP and even Windows 98/95. VIDEODRIVERINITFAILURE: 0x000000B8: ATTEMPTEDSWITCHFROMDPC: 0x000000B9: CHIPSETDETECTEDERROR: 0x000000BA: SESSIONHASVALIDVIEWSONEXIT: 0x000000BB: NETWORKBOOTINITIALIZATION.

  • “VIDEO_DRIVER_INIT_FAILURE” appears and crashes the active program window.
  • 'STOP Error 0xB4: VIDEO_DRIVER_INIT_FAILURE' is displayed.
  • A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file:
  • Your PC frequently crashes with Error 0xB4 when running the same program.
  • “The VIDEO_DRIVER_INIT_FAILURE bug check has a value of 0x000000B4. This indicates that Windows was unable to enter graphics mode.” is displayed.
  • Windows runs sluggishly and responds slowly to mouse or keyboard input.
  • Your computer periodically “freezes” for a few seconds at a time.

In most cases, you will experience VIDEO_DRIVER_INIT_FAILURE blue screen errors after you’ve installed new hardware or software. These VIDEO_DRIVER_INIT_FAILURE blue screens can appear during program installation, while a Microsoft Corporation-related software program (eg. Windows Operating System) is running, while a Windows driver is being loaded, or during Windows startup or shutdown. Keeping track of when and where your STOP error occurs is a critical piece of information in troubleshooting the problem.


Causes of VIDEO_DRIVER_INIT_FAILURE Blue Screen Errors

  • Incorrectly configured, old, or corrupted device drivers. (very common)
  • Corruption in Windows registry from a recent software change (install or uninstall).
  • Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
  • Driver conflict after installing new hardware.
  • Damaged or removed system files after you’ve installed software or drivers related to Windows Operating System.
  • Error 0xB4 blue screen caused by a damaged hard disk.
  • VIDEO_DRIVER_INIT_FAILURE STOP error due to memory (RAM) corruption.

VIDEO_DRIVER_INIT_FAILURE blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues.

Windows

Compatible with Windows 10, 8, 7, Vista, XP and 2000

Windows 10 Iso

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall



Blue Screen Errors Knowledgebase

Article ID:

120558

Article Author:

Last Updated:

Popularity:

star rating here


Optional Offer for WinThruster by Solvusoft
EULA | Privacy Policy | Terms | Uninstall



How To Fix VIDEO_DRIVER_INIT_FAILURE Blue Screen Errors (BugCheck 0xB4)

Below is a list of troubleshooting steps to resolve your VIDEO_DRIVER_INIT_FAILURE problems. These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effort.


Please Note: Click the [ ] image to expand the troubleshooting instructions for each step below. You can also click the [ ] image to hide the instructions as you proceed through each step.

Step 1: Repair Registry Entries Associated with Error 0xB4


Manually editing the Windows registry to remove invalid VIDEO_DRIVER_INIT_FAILURE keys is not recommended unless you are PC service professional. Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating system. In fact, one misplaced comma can prevent your PC from booting entirely!

Because of this risk, we recommend using a registry cleaner to assist with this process. Using a registry cleaner automates the process of finding invalid registry entries, missing file references (like the one causing your VIDEO_DRIVER_INIT_FAILURE error), and broken links within the registry. A backup is automatically created before each scan, with the ability to undo any changes in a single click, protecting you against the possibility of PC damage.

As a Microsoft Silver Partner, we provide software that can assist you in removing these issues:


Caution: Unless you an advanced PC user, we DO NOT recommend editing the Windows registry manually. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. We do not guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to VIDEO_DRIVER_INIT_FAILURE (eg. Windows Operating System):

  1. Click the Start button.
  2. Type 'command' in the search box... DO NOT hit ENTER yet!
  3. While holding CTRL-Shift on your keyboard, hit ENTER.
  4. You will be prompted with a permission dialog box.
  5. Click Yes.
  6. A black box will open with a blinking cursor.
  7. Type 'regedit' and hit ENTER.
  8. In the Registry Editor, select the Error 0xB4-related key (eg. Windows Operating System) you want to back up.
  9. From the File menu, choose Export.
  10. In the Save In list, select the folder where you want to save the Windows Operating System backup key.
  11. In the File Name box, type a name for your backup file, such as 'Windows Operating System Backup'.
  12. In the Export Range box, be sure that 'Selected branch' is selected.
  13. Click Save.
  14. The file is then saved with a .reg file extension.
  15. You now have a backup of your VIDEO_DRIVER_INIT_FAILURE-related registry entry.

The next steps in manually editing your registry will not be discussed in this article due to the high risk of damaging your system. If you would like to learn more about manual registry editing, please see the links below.


We do not claim any responsibility for the results of the actions taken from the content linked below - complete these tasks at your own risk.

Windows XP
http://www.theeldergeek.com/windows_xp_registry.htm

Windows 7
http://www.theeldergeek.com/windows_7/registry_edits_for_win7.htm

Windows Vista
http://support.microsoft.com/kb/2688326 - LetMeFixItMyselfAlways


Step 2: Conduct a Full Malware Scan of Your PC


There is a chance that your VIDEO_DRIVER_INIT_FAILURE error could be related to a malware infection on your PC. These malicious intruders can damage, corrupt, or even delete Blue Screen Errors-related files. Furthermore, there's a possibility that the 0xB4 error you are experiencing is related to a component of the malicious program itself.


Tip: If you do not already have a malware protection program installed, we highly recommend using Emsisoft Anti-Malware (download here). They offer a malware removal guarantee that is not offered by other security software.


Step 3: Clean Out Your System Junk (Temporary Files and Folders) With Disk Cleanup (cleanmgr)


Over time, your computer accumulates junk files from normal web surfing and computer use. If this junk isn't occasionally cleaned out, it can cause Windows Operating System to respond slowly or provides an VIDEO_DRIVER_INIT_FAILURE error, possibly due to file conflicts or an overloaded hard drive. Cleaning up these temporary files with Disk Cleanup might not only solve your 0xB4 error, but can also dramatically speed up the performance of your PC.


Tip: Although Disk Cleanup is a wonderful built-in tool, it will not completely clean up all of the temporary files on your computer. Other programs that you frequently use such Microsoft Office, Firefox, Chrome, Live Messenger, and hundreds of other programs are not cleaned up with Disk Cleanup (including some Microsoft Corporation programs).


Because of the shortcomings of the Windows Disk Cleanup (cleanmgr) tool, we highly recommend using a specialized hard drive cleanup / privacy protection software to clean up your entire computer.

As a Microsoft Silver Partner, we provide software that can assist you in cleaning up your temporary files:

How to run Disk Cleanup (cleanmgr) (Windows XP, Vista, 7, 8, and 10):

  1. Click the Start button.
  2. Type 'command' in the search box... DO NOT hit ENTER yet!
  3. While holding CTRL-Shift on your keyboard, hit ENTER.
  4. You will be prompted with a permission dialog box.
  5. Click Yes.
  6. A black box will open with a blinking cursor.
  7. Type 'cleanmgr' and hit ENTER.
  8. Disk Cleanup will begin calculating how much occupied disk space you can reclaim.
  9. The Disk Cleanup dialog box will appear with series of checkboxes you can select. In most cases, the 'Temporary Files' category will occupy the most disk space.
  10. Check the boxes of the categories you want to clean and click OK.

Step 4: Update Your PC Device Drivers


VIDEO_DRIVER_INIT_FAILURE errors can be related to corrupt or outdated device drivers. Drivers can work one day, and suddenly stop working the next day, for a variety of reasons. The good news is that you can often update the device driver to fix the Error 0xB4 problem.

Finding the exact driver for your Error 0xB4-related hardware device can be extremely difficult, even directly on the Microsoft Corporation or related manufacturer's website. Even if you are experienced at finding, downloading, and manually updating drivers, the process can still be very time consuming and extremely irritating. Installing the wrong driver, or simply an incompatible version of the right driver, can make your problems even worse.

Because of the time and complexity involved in updating drivers, we highly recommend using a driver update software. A driver update tool ensures that you have correct driver versions for your hardware, and also creates a backup of your current drivers before making any changes. Maintaining a driver backup provides you with the security of knowing that you can rollback any driver to a previous version (if necessary).

As a Microsoft Silver Partner, we provide software that can assist you in updating these drivers:


Please Note: Your VIDEO_DRIVER_INIT_FAILURE may not be related to hardware driver problems, but it's always a good idea to ensure all of your PC device drivers are up-to-date to maximize PC performance.


Step 5: Utilize Windows System Restore to 'Undo' Recent System Changes


Windows System Restore allows you to 'go back in time' with your PC to help fix your Error 0xB4 problems. System Restore can return your PC's system files and programs back to a time when everything was working fine. This can potentially help you avoid hours of troubleshooting headaches associated with VIDEO_DRIVER_INIT_FAILURE errors.


Please Note: Using System Restore will not affect your documents, pictures, or other data.

To use System Restore (Windows XP, Vista, 7, 8, and 10):

  1. Click the Start button.
  2. In the search box, type 'System Restore' and hit ENTER.
  3. In the results, click System Restore.
  4. Enter any administrator passwords (if prompted).
  5. Follow the steps in the Wizard to choose a restore point.
  6. Restore your computer.

Step 6: Uninstall and Reinstall the Windows Operating System Program Associated with VIDEO_DRIVER_INIT_FAILURE


If your VIDEO_DRIVER_INIT_FAILURE error is related to a specific program, reinstalling Windows Operating System-related software could be the answer.

Instructions for Windows 7 and Windows Vista:

  1. Open Programs and Features by clicking the Start button.
  2. Click Control Panel on the right side menu.
  3. Click Programs.
  4. Click Programs and Features.
  5. Locate VIDEO_DRIVER_INIT_FAILURE-associated program (eg. Windows Operating System) under the Name column.
  6. Click on the Windows Operating System-associated entry.
  7. Click the Uninstall button on the top menu ribbon.
  8. Follow the on-screen directions to complete the uninstallation of your Error 0xB4-associated program.

Instructions for Windows XP:

  1. Open Programs and Features by clicking the Start button.
  2. Click Control Panel.
  3. Click Add or Remove Programs.
  4. Locate VIDEO_DRIVER_INIT_FAILURE-associated program (eg. Windows Operating System) under the list of Currently Installed Programs.
  5. Click on the Windows Operating System-associated entry.
  6. Click the Remove button on the right side.
  7. Follow the on-screen directions to complete the uninstallation of your Error 0xB4-associated program.

Instructions for Windows 8:

  1. Hover the cursor in the bottom left of the screen to produce the Start Menu image.
  2. Right-Click to bring up the Start Context Menu.
  3. Click Programs and Features.
  4. Locate VIDEO_DRIVER_INIT_FAILURE-associated program (eg. Windows Operating System) under the Name column.
  5. Click on the Windows Operating System-associated entry.
  6. Click the Uninstall/Change on the top menu ribbon.
  7. Follow the on-screen directions to complete the uninstallation of your Error 0xB4-associated program.

After you have successfully uninstalled your VIDEO_DRIVER_INIT_FAILURE-associated program (eg. Windows Operating System), reinstall the program according to the Microsoft Corporation instructions.


Tip: If you are positive that your 0xB4 error is related to a specific Microsoft Corporation program, uninstalling and reinstalling your VIDEO_DRIVER_INIT_FAILURE-related program will likely be the solution to your problem.


Step 7: Run Windows System File Checker ('sfc /scannow')


System File Checker is a handy tool included with Windows that allows you scan for and restore corruptions in Windows system files (including those related to VIDEO_DRIVER_INIT_FAILURE).

To run System File Checker (Windows XP, Vista, 7, 8, and 10):

  1. Click the Start button.
  2. Type 'command' in the search box... DO NOT hit ENTER yet!
  3. While holding CTRL-Shift on your keyboard, hit ENTER.
  4. You will be prompted with a permission dialog box.
  5. Click Yes.
  6. A black box will open with a blinking cursor.
  7. Type 'sfc /scannow' and hit ENTER.
  8. System File Checker will begin scanning for Error 0xB4 and other system file problems (be patient - the system scan may take a while).
  9. Follow the on-screen commands.

Step 8: Install All Available Windows Updates


Microsoft is constantly updating and improving Windows system files that could be associated with VIDEO_DRIVER_INIT_FAILURE. Sometimes resolving your Blue Screen Errors problems may be as simple as updating Windows with the latest Service Pack or other patch that Microsoft releases on an ongoing basis.

To check for Windows Updates (Windows XP, Vista, 7, 8, and 10):

  1. Click the Start button.
  2. Type 'update' into the search box and hit ENTER.
  3. The Windows Update dialog box will appear.
  4. If updates are available, click the Install Updates button.

Step 9: Check for Hard Drive Corruption ('chkdsk /f')


While most storage-related, 0xB4 blue screen errors are caused by problems with your hard disk drivers or storage controllers, in some cases these BSODs can be attributed to hard drive corruption.

Over time, your PC can develop errors on the hard disk drive due to repeated, unintended misuse. Improper shut downs, “hard closing” programs, corrupt or incomplete installation of software (eg. Windows Operating System), Microsoft Corporation hardware failure, and power outages can corrupt your file system and stored data. As a result, you may experience blue screen errors associated with VIDEO_DRIVER_INIT_FAILURE.

Microsoft has included a convenient utility called “chkdsk” (“Check Disk”) to scan and repair hard disk corruption. If the previous troubleshooting steps did not resolve your 0xB4 STOP error, running “chkdsk” may uncover and repair the cause of your BSOD.

How to run “chkdsk” (Windows XP, Vista, 7, 8, and 10):

  1. Click the Start button.
  2. Type 'command' in the search box... DO NOT hit ENTER yet!
  3. While holding CTRL-Shift on your keyboard, hit ENTER.
  4. You will be prompted with a permission dialog box.
  5. Click Yes.
  6. A black box will open with a blinking cursor.
  7. Type 'chkdsk /f' and hit ENTER.
  8. 'chkdsk' will begin scanning for hard disk corruption that could be causing 0xB4 STOP errors.
  9. Follow the on-screen commands.

Complete list of “chkdsk” commands (Advanced PC users only):

  1. /F – Scans and fixes errors on the disk.
  2. /V – Displays every file name in each directory as the disk is scanned.
    • FAT/FAT32 Drive: This will display the full path and name of every file on the disk.
    • NTFS Drive: Displays cleanup messages.
  3. /R – This command locates bad sectors and recovers readable information (assumes /F).
  4. /L:size (NTFS only) – This command changes the log file size to the specified number of kilobytes. It will display the current size if size is not specified.
  5. /X – If necessary, it forces the volume to dismount first. All opened handles to the volume would then be invalid (assumes /F).
  6. /I (NTFS only) - Performs a less rigorous check of index entries.
  7. /C (NTFS only) - Skips checking of cycles inside the folder structure.
  8. /B (NTFS only) - Re-evaluates bad hard disk clusters on the volume (assumes /F).

Step 10: Test Your Memory (RAM) for Corruption


Sometimes hardware-related VIDEO_DRIVER_INIT_FAILURE blue screen errors can be due to memory (RAM) corruption. If you are experiencing random computer reboots, receiving “beep” codes on startup, or other computer crashes (in addition to 0xB4 BSOD errors), it is likely that your memory could be corrupt. In fact, nearly 10% of application crashes in Windows are due to memory corruption.

If you have just added new memory to the computer, we recommend temporarily removing it to make sure it is not the cause of your VIDEO_DRIVER_INIT_FAILURE error. If this action resolves your BSOD, this will be the source of your problem, and therefore your new memory is either incompatible or bad. If that is the case, you will then need to replace your new memory modules.

If you haven’t added any new memory, the next step is to perform a diagnostic test on your computer’s existing memory. A memory test will scan for hard memory failures and intermittent errors, either of which could be causing your 0xB4 blue screen of death.

Although later versions of Windows include the Windows Memory Diagnostic Tool, I highly recommend using Memtest86 instead. Memtest86 is a BIOS-based memory testing software, unlike other testing programs that must run within Windows. The benefit is that it allows you to test ALL of your memory for VIDEO_DRIVER_INIT_FAILURE errors, while other programs cannot test the section of memory occupied by the software itself, the operating system, and any other running programs.

How to run Memtest86 to scan for memory corruption causing 0xB4 STOP errors:

  1. Grab an unused USB flash drive and connect it to your PC.
  2. Download the Windows MemTest86 USB image.
  3. Right click on the image file, and select the 'Extract to Here' option. Extract the file folder anywhere you can get to easily (eg. your Desktop).
  4. Inside the extracted folder, run the included imageUSB tool, and choose your plugged in USB drive to turn into a bootable drive. CAUTION: this action will erase all data on the USB drive.
  5. Memtest86 will now be installed on your USB and you are ready to test for the possible source of VIDEO_DRIVER_INIT_FAILURE errors.
  6. Restart your PC with the USB drive installed.
  7. Memtest86 will begin testing for memory corruption.
  8. Follow the on-screen commands.

If all of the above steps were unsuccessful, and Memtest86 finds memory corruption, it highly likely that your VIDEO_DRIVER_INIT_FAILURE blue screen error is due to bad memory. If this is the case, you will need to replace the bad memory to resolve your 0xB4 BSODs.

For additional help, Corsair has a great video tutorial on how to run Memtest86:

http://www2.corsair.com/training/how_to_memtest/6

Step 11: Perform a Clean Installation of Windows


Caution: We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve Error 0xB4 problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. If you are not currently backing up your data, you need to do so immediately (download a highly-recommended backup solution [MyPCBackup.com Download]) to protect yourself from permanent data loss.

This step is your final option in trying to resolve your VIDEO_DRIVER_INIT_FAILURE issue. Reinstalling Windows will erase everything from your hard drive, allowing you to start again with a fresh system. Furthermore, a clean install of Windows will also quickly clean out any and all 'junk' that has accumulated over the normal usage of your computer.


Please Note: If 0xB4 errors still persist after a clean install of Windows, your Blue Screen Errors problem MUST be hardware related. If that is the case, then it is likely you will need to replace the associated hardware causing the 0xB4 error.


Recommendation:Scan your PC for computer errors.Video_driver_init_failure[Download WinThruster - Product by Solvusoft]

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall


Operating System Information

VIDEO_DRIVER_INIT_FAILURE error messages can occur in any of the following Microsoft Windows operating systems:

  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Vista
  • Windows XP
  • Windows ME
  • Windows 2000

Are You Still Experiencing Error 0xB4 (VIDEO_DRIVER_INIT_FAILURE) Issues?

Please reach out to us anytime on social media for more help:


Recommendation:Scan your PC for computer errors.[Download WinThruster - Product by Solvusoft]

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall

About The Author:Jay Geater is the President and CEO of Solvusoft Corporation, a global software company focused on providing innovative utility software. He is a lifelong computer geek and loves everything related to computers, software, and new technology.


Browse Errors in Alphabetical Order:

Video Driver Init Failure Windows 10

A “blue screen of death” is the name for a critical Windows OS error that interrupts the work of a computer completely. BSOD errors emerge in any version of this operating system including Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP and even Windows 98/95.

As such type of error only allows restarting the computer, troubleshooting may be a difficult task. Fortunately, every STOP error has a hexadecimal code you can use to find a solution to your problem.

Windows 10 Blue Screen Video_driver_init_failure

CodeMessage0x00000001APC_INDEX_MISMATCH0x00000002DEVICE_QUEUE_NOT_BUSY0x00000003INVALID_AFFINITY_SET0x00000004INVALID_DATA_ACCESS_TRAP0x00000005INVALID_PROCESS_ATTACH_ATTEMPT0x00000006INVALID_PROCESS_DETACH_ATTEMPT0x00000007INVALID_SOFTWARE_INTERRUPT0x00000008IRQL_NOT_DISPATCH_LEVEL0x00000009IRQL_NOT_GREATER_OR_EQUAL0x0000000AIRQL_NOT_LESS_OR_EQUAL0x0000000BNO_EXCEPTION_HANDLING_SUPPORT0x0000000CMAXIMUM_WAIT_OBJECTS_EXCEEDED0x0000000DMUTEX_LEVEL_NUMBER_VIOLATION0x0000000ENO_USER_MODE_CONTEXT0x0000000FSPIN_LOCK_ALREADY_OWNED0x00000010SPIN_LOCK_NOT_OWNED0x00000011THREAD_NOT_MUTEX_OWNER0x00000012TRAP_CAUSE_UNKNOWN0x00000013EMPTY_THREAD_REAPER_LIST0x00000014CREATE_DELETE_LOCK_NOT_LOCKED0x00000015LAST_CHANCE_CALLED_FROM_KMODE0x00000016CID_HANDLE_CREATION0x00000017CID_HANDLE_DELETION0x00000018REFERENCE_BY_POINTER0x00000019BAD_POOL_HEADER0x0000001AMEMORY_MANAGEMENT0x0000001BPFN_SHARE_COUNT0x0000001CPFN_REFERENCE_COUNT0x0000001DNO_SPIN_LOCK_AVAILABLE0x0000001EKMODE_EXCEPTION_NOT_HANDLED0x0000001FSHARED_RESOURCE_CONV_ERROR0x00000020KERNEL_APC_PENDING_DURING_EXIT0x00000021QUOTA_UNDERFLOW0x00000022FILE_SYSTEM0x00000023FAT_FILE_SYSTEM0x00000024NTFS_FILE_SYSTEM0x00000025NPFS_FILE_SYSTEM0x00000026CDFS_FILE_SYSTEM0x00000027RDR_FILE_SYSTEM0x00000028CORRUPT_ACCESS_TOKEN0x00000029SECURITY_SYSTEM0x0000002AINCONSISTENT_IRP0x0000002BPANIC_STACK_SWITCH0x0000002CPORT_DRIVER_INTERNAL0x0000002DSCSI_DISK_DRIVER_INTERNAL0x0000002EDATA_BUS_ERROR0x0000002FINSTRUCTION_BUS_ERROR0x00000030SET_OF_INVALID_CONTEXT0x00000031PHASE0_INITIALIZATION_FAILED0x00000032PHASE1_INITIALIZATION_FAILED0x00000033UNEXPECTED_INITIALIZATION_CALL0x00000034CACHE_MANAGER0x00000035NO_MORE_IRP_STACK_LOCATIONS0x00000036DEVICE_REFERENCE_COUNT_NOT_ZERO0x00000037FLOPPY_INTERNAL_ERROR0x00000038SERIAL_DRIVER_INTERNAL0x00000039SYSTEM_EXIT_OWNED_MUTEX0x0000003ASYSTEM_UNWIND_PREVIOUS_USER0x0000003BSYSTEM_SERVICE_EXCEPTION0x0000003CINTERRUPT_UNWIND_ATTEMPTED0x0000003DINTERRUPT_EXCEPTION_NOT_HANDLED0x0000003EMULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED0x0000003FNO_MORE_SYSTEM_PTES0x00000040TARGET_MDL_TOO_SMALL0x00000041MUST_SUCCEED_POOL_EMPTY0x00000042ATDISK_DRIVER_INTERNAL0x00000043NO_SUCH_PARTITION0x00000044MULTIPLE_IRP_COMPLETE_REQUESTS0x00000045INSUFFICIENT_SYSTEM_MAP_REGS0x00000046DEREF_UNKNOWN_LOGON_SESSION0x00000047REF_UNKNOWN_LOGON_SESSION0x00000048CANCEL_STATE_IN_COMPLETED_IRP0x00000049PAGE_FAULT_WITH_INTERRUPTS_OFF0x0000004AIRQL_GT_ZERO_AT_SYSTEM_SERVICE0x0000004BSTREAMS_INTERNAL_ERROR0x0000004CFATAL_UNHANDLED_HARD_ERROR0x0000004DNO_PAGES_AVAILABLE0x0000004EPFN_LIST_CORRUPT0x0000004FNDIS_INTERNAL_ERROR0x00000050PAGE_FAULT_IN_NONPAGED_AREA0x00000051REGISTRY_ERROR0x00000052MAILSLOT_FILE_SYSTEM0x00000053NO_BOOT_DEVICE0x00000054LM_SERVER_INTERNAL_ERROR0x00000055DATA_COHERENCY_EXCEPTION0x00000056INSTRUCTION_COHERENCY_EXCEPTION0x00000057XNS_INTERNAL_ERROR0x00000058FTDISK_INTERNAL_ERROR0x00000059PINBALL_FILE_SYSTEM0x0000005ACRITICAL_SERVICE_FAILED0x0000005BSET_ENV_VAR_FAILED0x0000005CHAL_INITIALIZATION_FAILED0x0000005DUNSUPPORTED_PROCESSOR0x0000005EOBJECT_INITIALIZATION_FAILED0x0000005FSECURITY_INITIALIZATION_FAILED0x00000060PROCESS_INITIALIZATION_FAILED0x00000061HAL1_INITIALIZATION_FAILED0x00000062OBJECT1_INITIALIZATION_FAILED0x00000063SECURITY1_INITIALIZATION_FAILED0x00000064SYMBOLIC_INITIALIZATION_FAILED0x00000065MEMORY1_INITIALIZATION_FAILED0x00000066CACHE_INITIALIZATION_FAILED0x00000067CONFIG_INITIALIZATION_FAILED0x00000068FILE_INITIALIZATION_FAILED0x00000069IO1_INITIALIZATION_FAILED0x0000006ALPC_INITIALIZATION_FAILED0x0000006BPROCESS1_INITIALIZATION_FAILED0x0000006CREFMON_INITIALIZATION_FAILED0x0000006DSESSION1_INITIALIZATION_FAILED0x0000006ESESSION2_INITIALIZATION_FAILED0x0000006FSESSION3_INITIALIZATION_FAILED0x00000070SESSION4_INITIALIZATION_FAILED0x00000071SESSION5_INITIALIZATION_FAILED0x00000072ASSIGN_DRIVE_LETTERS_FAILED0x00000073CONFIG_LIST_FAILED0x00000074BAD_SYSTEM_CONFIG_INFO0x00000075CANNOT_WRITE_CONFIGURATION0x00000076PROCESS_HAS_LOCKED_PAGES0x00000077KERNEL_STACK_INPAGE_ERROR0x00000078PHASE0_EXCEPTION0x00000079MISMATCHED_HAL0x0000007AKERNEL_DATA_INPAGE_ERROR0x0000007BINACCESSIBLE_BOOT_DEVICE0x0000007CBUGCODE_NDIS_DRIVER0x0000007DINSTALL_MORE_MEMORY0x0000007ESYSTEM_THREAD_EXCEPTION_NOT_HANDLED0x0000007FUNEXPECTED_KERNEL_MODE_TRAP0x00000080NMI_HARDWARE_FAILURE0x00000081SPIN_LOCK_INIT_FAILURE0x00000082DFS_FILE_SYSTEM0x00000083OFS_FILE_SYSTEM0x00000084RECOM_DRIVER0x00000085SETUP_FAILURE0x0000008BMBR_CHECKSUM_MISMATCH0x0000008EKERNEL_MODE_EXCEPTION_NOT_HANDLED0x0000008FPP0_INITIALIZATION_FAILED0x00000090PP1_INITIALIZATION_FAILED0x00000091WIN32K_INIT_OR_RIT_FAILURE0x00000092UP_DRIVER_ON_MP_SYSTEM0x00000093INVALID_KERNEL_HANDLE0x00000094KERNEL_STACK_LOCKED_AT_EXIT0x00000095PNP_INTERNAL_ERROR0x00000096INVALID_WORK_QUEUE_ITEM0x00000097BOUND_IMAGE_UNSUPPORTED0x00000098END_OF_NT_EVALUATION_PERIOD0x00000099INVALID_REGION_OR_SEGMENT0x0000009ASYSTEM_LICENSE_VIOLATION0x0000009BUDFS_FILE_SYSTEM0x0000009CMACHINE_CHECK_EXCEPTION0x0000009EUSER_MODE_HEALTH_MONITOR0x0000009FDRIVER_POWER_STATE_FAILURE0x000000A0INTERNAL_POWER_ERROR0x000000A1PCI_BUS_DRIVER_INTERNAL0x000000A2MEMORY_IMAGE_CORRUPT0x000000A3ACPI_DRIVER_INTERNAL0x000000A4CNSS_FILE_SYSTEM_FILTER0x000000A5ACPI_BIOS_ERROR0x000000A7BAD_EXHANDLE0x000000ABSESSION_HAS_VALID_POOL_ON_EXIT0x000000ACHAL_MEMORY_ALLOCATION0x000000ADVIDEO_DRIVER_DEBUG_REPORT_REQUEST0x000000B4VIDEO_DRIVER_INIT_FAILURE0x000000B8ATTEMPTED_SWITCH_FROM_DPC0x000000B9CHIPSET_DETECTED_ERROR0x000000BASESSION_HAS_VALID_VIEWS_ON_EXIT0x000000BBNETWORK_BOOT_INITIALIZATION_FAILED0x000000BCNETWORK_BOOT_DUPLICATE_ADDRESS0x000000BEATTEMPTED_WRITE_TO_READONLY_MEMORY0x000000BFMUTEX_ALREADY_OWNED0x000000C1SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION0x000000C2BAD_POOL_CALLER0x000000C4DRIVER_VERIFIER_DETECTED_VIOLATION0x000000C5DRIVER_CORRUPTED_EXPOOL0x000000C6DRIVER_CAUGHT_MODIFYING_FREED_POOL0x000000C7TIMER_OR_DPC_INVALID0x000000C8IRQL_UNEXPECTED_VALUE0x000000C9DRIVER_VERIFIER_IOMANAGER_VIOLATION0x000000CAPNP_DETECTED_FATAL_ERROR0x000000CBDRIVER_LEFT_LOCKED_PAGES_IN_PROCESS0x000000CCPAGE_FAULT_IN_FREED_SPECIAL_POOL0x000000CDPAGE_FAULT_BEYOND_END_OF_ALLOCATION0x000000CEDRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS0x000000CFTERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE0x000000D0DRIVER_CORRUPTED_MMPOOL0x000000D1DRIVER_IRQL_NOT_LESS_OR_EQUAL0x000000D2BUGCODE_ID_DRIVER0x000000D3DRIVER_PORTION_MUST_BE_NONPAGED0x000000D4SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD0x000000D5DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL0x000000D6DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION0x000000D7DRIVER_UNMAPPING_INVALID_VIEW0x000000D8DRIVER_USED_EXCESSIVE_PTES0x000000D9LOCKED_PAGES_TRACKER_CORRUPTION0x000000DASYSTEM_PTE_MISUSE0x000000DBDRIVER_CORRUPTED_SYSPTES0x000000DCDRIVER_INVALID_STACK_ACCESS0x000000DEPOOL_CORRUPTION_IN_FILE_AREA0x000000DFIMPERSONATING_WORKER_THREAD0x000000E0ACPI_BIOS_FATAL_ERROR0x000000E1WORKER_THREAD_RETURNED_AT_BAD_IRQL0x000000E2MANUALLY_INITIATED_CRASH0x000000E3RESOURCE_NOT_OWNED0x000000E4WORKER_INVALID0x000000E6DRIVER_VERIFIER_DMA_VIOLATION0x000000E7INVALID_FLOATING_POINT_STATE0x000000E8INVALID_CANCEL_OF_FILE_OPEN0x000000E9ACTIVE_EX_WORKER_THREAD_TERMINATION0x000000EATHREAD_STUCK_IN_DEVICE_DRIVER0x000000EBDIRTY_MAPPED_PAGES_CONGESTION0x000000ECSESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT0x000000EDUNMOUNTABLE_BOOT_VOLUME0x000000EFCRITICAL_PROCESS_DIED0x000000F1SCSI_VERIFIER_DETECTED_VIOLATION0x000000F3DISORDERLY_SHUTDOWN0x000000F4CRITICAL_OBJECT_TERMINATION0x000000F5FLTMGR_FILE_SYSTEM0x000000F6PCI_VERIFIER_DETECTED_VIOLATION0x000000F7DRIVER_OVERRAN_STACK_BUFFER0x000000F8RAMDISK_BOOT_INITIALIZATION_FAILED0x000000F9DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN0x000000FAHTTP_DRIVER_CORRUPTED0x000000FCATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY0x000000FDDIRTY_NOWRITE_PAGES_CONGESTION0x000000FEBUGCODE_USB_DRIVER0x000000FFRESERVE_QUEUE_OVERFLOW0x00000100LOADER_BLOCK_MISMATCH0x00000101CLOCK_WATCHDOG_TIMEOUT0x00000103MUP_FILE_SYSTEM0x00000104AGP_INVALID_ACCESS0x00000105AGP_GART_CORRUPTION0x00000106AGP_ILLEGALLY_REPROGRAMMED0x00000108THIRD_PARTY_FILE_SYSTEM_FAILURE0x00000109CRITICAL_STRUCTURE_CORRUPTION0x0000010AAPP_TAGGING_INITIALIZATION_FAILED0x0000010CFSRTL_EXTRA_CREATE_PARAMETER_VIOLATION0x0000010DWDF_VIOLATION0x0000010EVIDEO_MEMORY_MANAGEMENT_INTERNAL0x0000010FRESOURCE_MANAGER_EXCEPTION_NOT_HANDLED0x00000111RECURSIVE_NMI0x00000112MSRPC_STATE_VIOLATION0x00000113VIDEO_DXGKRNL_FATAL_ERROR0x00000114VIDEO_SHADOW_DRIVER_FATAL_ERROR0x00000115AGP_INTERNAL0x00000116VIDEO_TDR_ ERROR0x00000117VIDEO_TDR_TIMEOUT_DETECTED0x00000119VIDEO_SCHEDULER_INTERNAL_ERROR0x0000011AEM_INITIALIZATION_FAILURE0x0000011BDRIVER_RETURNED_HOLDING_CANCEL_LOCK0x0000011CATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE0x0000011DEVENT_TRACING_FATAL_ERROR0x00000121DRIVER_VIOLATION0x00000122WHEA_INTERNAL_ERROR0x00000124WHEA_UNCORRECTABLE_ERROR0x00000127PAGE_NOT_ZERO0x0000012BFAULTY_HARDWARE_CORRUPTED_PAGE0x0000012CEXFAT_FILE_SYSTEM0x00000133DPC_WATCHDOG_VIOLATION0x00000138GPIO_CONTROLLER_DRIVER_ERROR0x00000139KERNEL_SECURITY_CHECK_FAILURE0x00000144BUGCODE_USB3_DRIVER0x0000014BSOC_SUBSYSTEM_FAILURE0x1000007ESYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M0x1000007FUNEXPECTED_KERNEL_MODE_TRAP_M0x1000008EKERNEL_MODE_EXCEPTION_NOT_HANDLED_M0x100000EATHREAD_STUCK_IN_DEVICE_DRIVER_M0xC0000218STATUS_CANNOT_LOAD_REGISTRY_FILE0xC000021ASTATUS_SYSTEM_PROCESS_TERMINATED0xC0000221STATUS_IMAGE_CHECKSUM_MISMATCH0xDEADDEADMANUALLY_INITIATED_CRASH1