[IRQL NOT LESS OR EQUAL] Your PC suddenly crashes showing a disturbing blue screen (BSOD) with an error message? This is because Windows has encountered a serious problem. Here’s what you need to know to find its cause and fix the system.
You are watching : how to fix blue screen windows 10
Your PC suddenly crashes showing a disturbing blue screen (BSOD) with a error message ? This is because Windows has encountered a serious problem. Here’s what you need to know to find its cause and fix the system.
Blue Screen of Death, Blue Screen of Death (or BSOD, its English acronym), fatal error… This is how PC users talk about the dreaded situation: the complete crash of Windows. The one that happens suddenly, that blocks all action and loses everything! Because the system then leaves no choice: Windows stops abruptly by stealthily displaying the famous blue screen with a mysterious message before restarting the computer. No time to save documents being processed in open applications: just hope that their automatic saving mechanisms will allow you to recover a recent version of documents on the next launch…
The blue screen, its color and its messages change from time to time, as the system updates. In preview versions of Windows 11, for example, Microsoft displayed it in black, before returning to blue. Likewise, if you signed up for the Windows Insider Program to find out what’s coming to Windows before everyone else, that infamous blue screen may be green! But for the vast majority of users, it currently looks like this in Windows 10 and 11:
Frequent in the 90s, blue screens are now quite rare, Microsoft having significantly improved the stability of Windows over the versions so that system processes are not or little impacted by the crashes of other programs. The appearance of a blue screen is still possible with the latest versions of Windows.
This practical sheet offers you different ways to understand the origin of the problem and solve it. One chance: Often after a BSOD, Windows will reboot normally and you have the option to scan the PC and attempt a repair. Better to act without too much delay because a new crash can occur at any time. In the worst case, Windows refuses to launch. There are again several solutions to repair Windows or reinstall it. We, of course, cover all of these eventualities!
Why Windows displays a blue screen?
Contrary to what you might think at first glance, if Windows displays the famous blue screen, it means that it hasn’t completely lost its touch. The BSOD appears when the operating system detects that an unexpected and serious event has corrupted data and code in memory, or compromised computer security. In short, since he can no longer function normally, he voluntarily prefers to stop as a precaution, to avoid more serious damage.
According to Microsoft, based on various studies, Windows is rarely responsible for blue screens, which are mainly caused by third-party programs. Most often, these are drivers, software used to control hardware components and devices (video card, wireless network chip, etc.) or sensitive applications designed by others editors, in particular security solutions (antivirus, firewall, etc.). Unlike “classic” applications, each of which runs in a protected space of RAM so as not to risk destabilizing Windows and other applications, all of this software operates at the lowest levels of the system, by modifying or replacing certain critical system functions. Here’s how the crashes break down, according to Microsoft:
- 70% is due to third-party drivers (graphics, CPU, or peripheral driver);
- 10% is due to hardware (damaged RAM, for example);
- 5% are due to Microsoft code (bugs in Windows or some of its components);
- 15% are of unknown cause.
How to identify the cause of a blue screen?
When it appears, the Windows blue screen sometimes displays a code to help you locate the source of the problem, sometimes embellished with a QR code in recent versions of the system, even, in the best of cases case, the name of the software that caused a crash. This information is valuable, because it makes it possible to more or less precisely identify the origin of the problem and therefore to find a solution more or less easily.
Thus, if a piece of software is flagged as faulty, you should update or uninstall it first, as soon as Windows starts normally. In addition, to reduce the risk of a new blue screen, consider unplugging all unnecessary peripherals from the PC before restarting, especially if the crash follows the installation of new hardware that you have just connected to your PC.
Sometimes it is quite simple to understand the origin of the fatal error, when it follows a recent event:
- the installation of a new application (including security software) or a new hardware driver;
- more generally, the installation of new hardware or software;
- a Windows (KBxxxxxx) or driver update via Windows Update that is found to be buggy or incompatible;
- too many applications open simultaneously (an overload that leads to a performance crash and hover);
- insufficient free disk space (Microsoft recommends always leaving a minimum of 10-15% free disk space for a PC to function properly),
But other causes of crashes are sometimes less obvious to diagnose:
- a hardware failure involving, for example, the RAM or the disk on which the system is installed,
- the action of a malicious program.
Our different sections will help you discover the origin of the system crash, and the associated solutions.
And if you have absolutely no idea of the cause of the problem, or if you simply want to confirm it, use the Windows Reliability Monitor, a little-known tool integrated as standard in the Microsoft system which precisely allows you to analyze a posteriori which causes a crash, thanks to a timestamped event report. Consult our practical sheet to find out how to use this amazing control tool – which is only useful for monitoring, however, without fixing anything.
How to use the error code (Stop Code) of a blue screen?
When a blue screen occurs, it is always a good idea to note the stop code (also called Stop Code) when it is displayed by Windows. This code tells you what the problem is and lets you search the web. Beware, the blue screen is stealthy and appears without warning! You usually only have a few seconds to write this code down or take a picture of the screen with your smartphone. It also happens that the name of the offending driver program appears just below. Some crashes, alas, don’t provide a stop code or the name of the driver that caused the crash, making it more difficult – but not impossible – to fix the problem.
- If you haven’t had time to write down or photograph the information shown in the blue screen, see Analyze a memory dump after a BSOD.
- If shown on the blue screen, the stop code is either an English phrase such as CRITICAL_PROCESS_DIED or a hex code in the form 0x0000003B. Here are some other common codes: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL, VIDEO_TDR_TIMEOUT_DETECTED, PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_SERVICE_EXCEPTION, DPC_WATCHDOG_VIOLATION (see full list of messages and codes at the end of this article).
- A search for this error code on the web, for example on Microsoft’s online technical support, or in a search engine like Google or Bing, will enlighten you on the possible causes of the crash, and how to fix it. ‘remediate. Often by uninstalling or updating the offending program.
- If the crash occurs right after the installation of software or hardware and its driver, or after a Windows update, check for conscience the meaning of the code as shown below, then proceed to this step to return to an earlier situation.
- With your usual web browser, go toMicrosoft Technical Support, type the error code in the input field and perform a search.
- Hopefully, the list of results will point you to what to do or a help page to consult.
- If not, search for the error code in a Google, Bing, DuckDuckGo or Qwant search engine. In the list of Web pages corresponding to your request, favor those on Microsoft sites. If none match, try the web pages of technical sites and support forums, on CommentÇaMarche or other sites in French.
- Of course, if the blue screen tells you the name of the offending driver, do a web search, followed by the word BSOD, for example, to see how other Internet users got away with it.
- In the Google results list, also use the date of update indicated for most pages. Newer pages have a better chance of providing you with relevant information.
- If this search does not bring you a relevant solution, refer to the section Repair Windows using Microsoft’s online wizard.
In some cases, the blue screen of Windows also displays a QR Code (illustration below), which you can photograph with your smartphone and which will send you to the website mentioned in full in the blue screen.
- If you want to photograph the QR Code to go directly to the Microsoft help page: open the Camera app on your Android smartphone or iPhone, aim at the screen of the computer as if you wanted to photograph it, the app detects a QR Code and offers to send you back to the website. Touch the message to view the website in your browser. Nothing obliges you to take such a photo of the QR Code, you can simply type the address indicated in your Internet browser!
- If you do not use the photographed QR Code: on the offending computer after restarting, or on another computer, or on a smartphone or touch pad, in the Internet browser (Chrome, Safari, Edge, Firefox… ), go to the Stop Codes page on the Microsoft support site or type the following address: https://windows.com/stopcode .
- Microsoft will always direct you to a short, easy-to-verify web address on one of its sites, such as windows.com/blablabla or microsoft.com/blablabla.
How to fix Windows after blue screen with Microsoft online assistant?
Microsoft’s Mini Online Assistant can be found at https://windows.com/stopcode. You can view this web page on the computer that produced the blue screen, if Windows agrees to restart, or on another computer, or even on your Apple or Android phone or tablet. The manipulations will of course be carried out on the PC that has crashed.
At the bottom of this Resolve Blue Screen Errors page, follow the instructions by answering the question in Step 1: When did- did you get the error? – yes, it is very familiar…
Note that the English/French translation of this web page is confusing: in step 1, when Microsoft Assistant talks about an update, it means “an update of Windows”, not your other software or your peripheral drivers (printer, webcam, etc.). Similarly, when the assistant then mentions “your device” or “your peripheral”, understand “your computer”.
If in step 1 you choose “After installing an update”, the page wizard https://windows.com/stopcode< /span> will explain:
If in step 1 you choose “While using my device”, the page wizard https://windows.com/stopcode will explain:
- How to restart Windows in safe mode, with or without network support. You can also refer to our fact sheet Restart in safe mode, which is much more complete.
- How to view the list of installed applications in Windows and uninstall software, such as antivirus or security software. Also refer to our practical sheet Delete an application in Windows.
- How to restore, disable or uninstall drivers. Also refer to our more comprehensive how-to sheet: Windows drivers, how to update drivers, which explains in particular how to revert to an old version of a device driver .
If the blue screen occurs shortly after installing new hardware or software, or updating a device driver, for example, you’re probably at fault. If you can access Windows again after a reboot, follow these steps.
- Our practical sheet Windows drivers, how to update drivers explains in particular how to obtain the latest version of a driver, or on the contrary how to revert to the previous version of ‘a device driver.
- If you want to uninstall a driver, open Windows Device Manager by right-clicking on the Start menu…
- … In Device Manager, right-click the driver and choose Uninstall Device.
- You can also turn to a utility to install on your computer, such as DriversCloud.com, which checks online all the drivers installed on your hard drive in order to update, if necessary.
- On the web, DriversCloud.com also offers you an analysis of BSOD blue screens to help pinpoint the causes.
- Finally, it is possible that the manufacturer of your computer has updated certain drivers and system software, for example the Bios/UEFI of the PC’s motherboard, programs whose update is not offered to you by the previous methods. Go to the manufacturer’s website, section Support or Assistance, indicate the exact reference of your computer and check if there are software and drivers to download.< /li>
- The manufacturer sometimes tells you the urgency of the update, like here on the Dell site, and will give you instructions to update your PC anyway.
During the occurrence of a blue screen, if you have not modified the default Windows settings, the system copies all or part of the contents of the computer’s RAM to a file on the hard disk. computer at the time of the crash. This file is called a memory dump. It helps computer scientists understand the causes of a crash when writing programs. But you don’t need to be an expert to extract useful information from this dump, in particular the error code (stop code) generated by Windows, and perhaps even the name of the faulty driver.
- After restarting the computer, download a version of the BlueScreenView software at the bottom of this page. For example this version, which does not require installation: just unzip the zip file and run the program BlueScreenView.exe.
- If both panels of BlueScreenView do not display any information, in a Windows File Explorer window, navigate to the C:\Windows folder and locate the MEMORY file .DMP. Drag it to the top panel of the BlueScreenView app (in the area showing Dump File).
- The Bug Check String column tells you the error code for each crash referenced in the top list. The Caused By Driver column possibly tells you the name of the driver that caused the crash. But there may not be one like in the example below, or the memory dump may wrongly mention the driver ntoskrnl.exe (in this case< strong>, ignore it).
- If you select a crash from the top list, the bottom panel will in some cases show you the names of the affected files and drivers. You can also right-click on a crash and choose Google Search – Bug Check+Driver. In a tab of your web browser, Google then lists the pages corresponding to this error code and to the possible driver mentioned.
A full hard drive or SSD that prevents Windows from working properly, damaged sectors that make it impossible to read system files… your computer’s storage can also be the cause of the crash and screen blue.
- To check if the hard drive has enough free space, open File Explorer and look at the gauge of drive C, which most likely has Windows installed. If this gauge is not blue, and a fortiori red, it means that disk space is low. Refer to this how-to to free up Windows disk space.
- If you suspect a damaged disk, see our how-to scan and repair your disks with ChkDsk.
If the error code alerts you to a hardware problem that could be related to the RAM of the PC, of the type MEMORY_MANAGEMENT, here is how to run a test of the RAM or RAM (Random Access Memory) with the tool provided by Windows, after restarting the PC.
If the tool tells you that there are indeed errors, you will have to replace the memory modules of the computer – if they are not soldered directly on the motherboard… – following the advice of the technical support of the manufacturer of your laptop or desktop PC.
- If after the blue screen, Windows restarts: In the lower left corner of the screen, click the magnifying glass or the Start menu and type Windows Memory Diagnostic. Click on this proposition when it appears as a Best bet proposition.
- A window will appear giving you two options: choose Restart now.
- If, after the blue screen, Windows does not restart properly: bring up the Windows Recovery Screen using one of the methods explained in this sheet. Then choose the option Troubleshoot, then Advanced Options, then Command Prompt.
- In the black window that appears, type mdsched and press the Enter key.
- If Windows was running, it closes. Then the PC restarts and Windows Memory Diagnostic starts…
- It will let you know after a few minutes if a problem has been detected.
- If Windows restarts, you can also watch for a message in the lower right corner of the screen.
- If you haven’t had time to see this message,type the two keys Win+R anywhere in Windows, then enter eventvwr and press OK.
- The Event Viewer appears. Left-click Windows Logs > System. Locate the source MemoryDiagnostics-Results in the list and read the memory test result below.
A malicious program may be causing your computer to crash. There are many solutions online or to install on your PC to scan RAM and disks for viruses. Here is a simple method with the program provided by Microsoft.
- This how-to sheet tells you how to remove malware and adware in Windows with the Microsoft Safety Scanner tool.
Whether Windows displays a blue or all black or all white screen – it doesn’t matter what color – if the crash recurs regularly, you will need to find a solution! In the case of a black or white screen, other avenues should be explored.
- On the Web, a Microsoft wizard asks you some questions and offers you many solutions following the PC freezes with a black screen or a white screen.
- Also refer to our practical sheet to find solutions when your PC displays a black screen.
If, despite your best efforts, the blue screens follow one another without you finding the cause, a restoration, an update or a complete reinstallation of Windows is required. Gradually test the following different solutions, which will not all have the same effect depending on the actual cause of the crsh. From experience, we have already encountered inexplicable blue screens on new and up-to-date PCs: the only effective technique was to reinstall Windows 10 from scratch, reformatting the system disk – and thus erasing all its contents after backing up personal files . Everything worked perfectly afterwards, without ever seeing the slightest blue screen again. Proof that the problems came from the applications installed as standard by the manufacturers (bloatware as they are called).
The complete list of Windows stop-codes
Error messages and stop codes that appear on Windows blue screens are taken from a large inventory made by Microsoft which you can find on this page. Here is the complete list, organized in alphabetical order of the messages, with their specific stop code. Click a message title to view Microsoft documentation for the error.
ERROR MESSAGE
STOP CODE
ABNORMAL_RESET_DETECTED
0x00000147
ACPI_BIOS_ERROR
0x000000A5
ACPI_BIOS_FATAL_ERROR
0x000000E0
ACPI_DRIVER_INTERNAL
0x000000A3
ACTIVE_EX_WORKER_THREAD_TERMINATION
0x000000E9
AGP_GART_CORRUPTION
0x00000105
AGP_ILLEGALLY_REPROGRAMMED
0x00000106
AGP_INTERNAL
0x00000115
AGP_INVALID_ACCESS
0x00000104
APC_INDEX_MISMATCH
0x00000001
APP_TAGGING_INITIALIZATION_FAILED
0x0000010A
ASSIGN_DRIVE_LETTERS_FAILED
0x00000072
ATDISK_DRIVER_INTERNAL
0x00000042
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
0x000000FC
ATTEMPTED_SWITCH_FROM_DPC
0x000000B8
ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
0x0000011C
ATTEMPTED_WRITE_TO_READONLY_MEMORY
0x000000BE
BAD_EXHANDLE
0x000000A7
BAD_OBJECT_HEADER
0x00000189
BAD_POOL_CALLER
0x000000C2
BAD_POOL_HEADER
0x00000019
BAD_SYSTEM_CONFIG_INFO
0x00000074
BC_BLUETOOTH_VERIFIER_FAULT
0x00000BFE
BC_BTHMINI_VERIFIER_FAULT
0x00000BFF
BGI_DETECTED_VIOLATION
0x000000B1
BITLOCKER_FATAL_ERROR
0x00000120
BOUND_IMAGE_UNSUPPORTED
0x00000097
BUGCODE_ID_DRIVER
0x000000D2
BUGCODE_NDIS_DRIVER
0x0000007C
BUGCODE_USB_DRIVER
0x000000FE
BUGCODE_USB3_DRIVER
0x00000144
CACHE_INITIALIZATION_FAILED
0x00000066
CACHE_MANAGER
0x00000034
CANCEL_STATE_IN_COMPLETED_IRP
0x00000048
CANNOT_WRITE_CONFIGURATION
0x00000075
CDFS_FILE_SYSTEM
0x00000026
CHIPSET_DETECTED_ERROR
0x000000B9
CID_HANDLE_CREATION
0x00000016
CID_HANDLE_DELETION
0x00000017
CLOCK_WATCHDOG_TIMEOUT
0x00000101
CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG
0x00000171
CNSS_FILE_SYSTEM_FILTER
0x000000A4
CONFIG_INITIALIZATION_FAILED
0x00000067
CONFIG_LIST_FAILED
0x00000073
COREMSG_INTERNAL_ERROR
0x00000174
COREMSGCALL_INTERNAL_ERROR
0x00000173
CORRUPT_ACCESS_TOKEN
0x00000028
CPI_FIRMWARE_WATCHDOG_TIMEOUT
0x000001D0
CREATE_DELETE_LOCK_NOT_LOCKED
0x00000014
CRITICAL_INITIALIZATION_FAILURE
0x0000013D
CRITICAL_OBJECT_TERMINATION
0x000000F4
CRITICAL_PROCESS_DIED
0x000000EF
CRITICAL_SERVICE_FAILED
0x0000005A
CRITICAL_STRUCTURE_CORRUPTION
0x00000109
CRYPTO_LIBRARY_INTERNAL_ERROR
0x00000170
CRYPTO_SELF_TEST_FAILURE
0x00000123
DATA_BUS_ERROR
0x0000002E
DATA_COHERENCY_EXCEPTION
0x00000055
DEREF_UNKNOWN_LOGON_SESSION
0x00000046
DEVICE_QUEUE_NOT_BUSY
0x00000002
DEVICE_REFERENCE_COUNT_NOT_ZERO
0x00000036
DFS_FILE_SYSTEM
0x00000082
DIRTY_MAPPED_PAGES_CONGESTION
0x000000EB
DIRTY_NOWRITE_PAGES_CONGESTION
0x000000FD
DISORDERLY_SHUTDOWN
0x000000F3
DMA_COMMON_BUFFER_VECTOR_ERROR
0x000001DC
DPC_WATCHDOG_TIMEOUT
0x00000102
DPC_WATCHDOG_VIOLATION
0x00000133
DRIVE_EXTENDER
0x00000134
DRIVER_CAUGHT_MODIFYING_FREED_POOL
0x000000C6
DRIVER_CORRUPTED_EXPOOL
0x000000C5
DRIVER_CORRUPTED_MMPOOL
0x000000D0
DRIVER_CORRUPTED_SYSPTES
0x000000DB
DRIVER_INVALID_STACK_ACCESS
0x000000DC
DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000D1
DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
0x000000CB
DRIVER_OVERRAN_STACK_BUFFER
0x000000F7
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000D6
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D5
DRIVER_PNP_WATCHDOG
0x000001D5
DRIVER_PORTION_MUST_BE_NONPAGED
0x000000D3
DRIVER_POWER_STATE_FAILURE
0x0000009F
DRIVER_RETURNED_HOLDING_CANCEL_LOCK
0x0000011BDRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
0x000000F9
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
0x000000CE
DRIVER_UNMAPPING_INVALID_VIEW
0x000000D7
DRIVER_USED_EXCESSIVE_PTES
0x000000D8
DRIVER_VERIFIER_DETECTED_VIOLATION
0x000000C4
DRIVER_VERIFIER_DMA_VIOLATION
0x000000E6
DRIVER_VERIFIER_IOMANAGER_VIOLATION
0x000000C9
DRIVER_VIOLATION
0x00000121
DYNAMIC_ADD_PROCESSOR_MISMATCH
0x00000130
EFS_FATAL_ERROR
0x000001D7
ELAM_DRIVER_DETECTED_FATAL_ERROR
0x00000178
EM_INITIALIZATION_FAILURE
0x0000011A
EMPTY_THREAD_REAPER_LIST
0x00000013
END_OF_NT_EVALUATION_PERIOD
0x00000098
ERESOURCE_INVALID_RELEASE
0x0000016E
EVENT_TRACING_FATAL_ERROR
0x0000011D
EXCEPTION_SCOPE_INVALID
0x0000014D
EXFAT_FILE_SYSTEM
0x0000012C
FAST_ERESOURCE_PRECONDITION_VIOLATION
0x000001C6
FAT_FILE_SYSTEM
0x00000023
FATAL_ABNORMAL_RESET_ERROR
0x0000014C
FATAL_UNHANDLED_HARD_ERROR
0x0000004C
FAULTY_HARDWARE_CORRUPTED_PAGE
0x0000012B
FILE_INITIALIZATION_FAILED
0x00000068
FILE_SYSTEM
0x00000022
FLOPPY_INTERNAL_ERROR
0x00000037
FLTMGR_FILE_SYSTEM
0x000000F5
FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION
0x0000010C
FTDISK_INTERNAL_ERROR
0x00000058
GPIO_CONTROLLER_DRIVER_ERROR
0x00000138
HAL_BLOCKED_PROCESSOR_INTERNAL_ERROR
0x000001DA
HAL_ILLEGAL_IOMMU_PAGE_FAULT
0x00000159
HAL_INITIALIZATION_FAILED
0x0000005C
HAL_IOMMU_INTERNAL_ERROR
0x000001D9
HAL_MEMORY_ALLOCATION
0x000000AC
HAL1_INITIALIZATION_FAILED
0x00000061
HARDWARE_INTERRUPT_STORM
0x000000F2
HARDWARE_WATCHDOG_TIMEOUT
0x000001CF
HTTP_DRIVER_CORRUPTED
0x000000FA
HYPERGUARD_VIOLATION
0x0000018C
HYPERVISOR_ERROR
0x00020001
ILLEGAL_IOMMU_PAGE_FAULT
0x00000158
IMPERSONATING_WORKER_THREAD
0x000000DF
INACCESSIBLE_BOOT_DEVICE
0x0000007B
INCONSISTENT_IRP
0x0000002A
INSTALL_MORE_MEMORY
0x0000007D
INSTRUCTION_BUS_ERROR
0x0000002F
INSTRUCTION_COHERENCY_EXCEPTION
0x00000056
INSUFFICIENT_SYSTEM_MAP_REGS
0x00000045
INTERNAL_POWER_ERROR
0x000000A0
INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003D
INTERRUPT_UNWIND_ATTEMPTED
0x0000003C
INVALID_AFFINITY_SET
0x00000003
INVALID_CALLBACK_STACK_ADDRESS
0x000001CD
INVALID_CANCEL_OF_FILE_OPEN
0x000000E8
INVALID_DATA_ACCESS_TRAP
0x00000004
INVALID_DRIVER_HANDLE
0x0000011F
INVALID_EXTENDED_PROCESSOR_STATE
0x00000131
INVALID_FLOATING_POINT_STATE
0x000000E7
INVALID_HIBERNATED_STATE
0x000000BD
INVALID_IO_BOOST_STATE
0x0000013C
INVALID_KERNEL_HANDLE
0x00000093
INVALID_KERNEL_STACK_ADDRESS
0x000001CEINVALID_MDL_RANGE
0x0000012E
INVALID_PROCESS_ATTACH_ATTEMPT
0x00000005
INVALID_PROCESS_DETACH_ATTEMPT
0x00000006
INVALID_PUSH_LOCK_FLAGS
0x00000152
INVALID_REGION_OR_SEGMENT
0x00000099
INVALID_RUNDOWN_PROTECTION_FLAGS
0x0000016C
INVALID_SILO_DETACH
0x000001CB
INVALID_SLOT_ALLOCATOR_FLAGS
0x0000016D
INVALID_SOFTWARE_INTERRUPT
0x00000007
INVALID_WORK_QUEUE_ITEM
0x00000096
IO1_INITIALIZATION_FAILED
0x00000069
IPI_WATCHDOG_TIMEOUT
0x000001DB
IRQL_GT_ZERO_AT_SYSTEM_SERVICE
0x0000004A
IRQL_NOT_DISPATCH_LEVEL
0x00000008
IRQL_NOT_GREATER_OR_EQUAL
0x00000009
IRQL_NOT_LESS_OR_EQUAL
0x0000000A
IRQL_UNEXPECTED_VALUE
0x000000C8
KERNEL_APC_PENDING_DURING_EXIT
0x00000020
KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
0x00000162
KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
0x00000192
KERNEL_DATA_INPAGE_ERROR
0x0000007A
KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION
0x00000153
KERNEL_MODE_EXCEPTION_NOT_HANDLED
0x0000008E
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0x1000008E
KERNEL_MODE_HEAP_CORRUPTION
0x0000013A
KERNEL_PARTITION_REFERENCE_VIOLATION
0x0000018E
KERNEL_SECURITY_CHECK_FAILURE
0x00000139
KERNEL_STACK_INPAGE_ERROR
0x00000077
KERNEL_STACK_LOCKED_AT_EXIT
0x00000094
KERNEL_STORAGE_SLOT_IN_USE
0x00000199
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION
0x00000157
KERNEL_WMI_INTERNAL
0x0000014A
KMODE_EXCEPTION_NOT_HANDLED
0x0000001E
LAST_CHANCE_CALLED_FROM_KMODE
0x00000015
LM_SERVER_INTERNAL_ERROR
0x00000054
LOADER_BLOCK_MISMATCH
0x00000100
LOADER_ROLLBACK_DETECTED
0x00000196
LOCKED_PAGES_TRACKER_CORRUPTION
0x000000D9
LPC_INITIALIZATION_FAILED
0x0000006A
MACHINE_CHECK_EXCEPTION
0x0000009C
MAILSLOT_FILE_SYSTEM
0x00000052
MANUALLY_INITIATED_CRASH
0x000000E2
MANUALLY_INITIATED_CRASH1
0xDEADDEAD
MANUALLY_INITIATED_POWER_BUTTON_HOLD
0x000001C8
MAXIMUM_WAIT_OBJECTS_EXCEEDED
0x0000000C
MBR_CHECKSUM_MISMATCH
0x0000008B
MEMORY_IMAGE_CORRUPT
0x000000A2
MEMORY_MANAGEMENT
0x0000001A
MEMORY1_INITIALIZATION_FAILED
0x00000065
MICROCODE_REVISION_MISMATCH
0x0000017E
MISMATCHED_HAL
0x00000079
MSRPC_STATE_VIOLATION
0x00000112
MUI_NO_VALID_SYSTEM_LANGUAGE
0x0000012A
MULTIPLE_IRP_COMPLETE_REQUESTS
0x00000044
MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
0x0000003E
MUP_FILE_SYSTEM
0x00000103
MUST_SUCCEED_POOL_EMPTY
0x00000041
MUTEX_ALREADY_OWNED
0x000000BF
MUTEX_LEVEL_NUMBER_VIOLATION
0x0000000D
NDIS_INTERNAL_ERROR
0x0000004F
NETIO_INVALID_POOL_CALLER
0x00000126
NETWORK_BOOT_DUPLICATE_ADDRESS
0x000000BC
NETWORK_BOOT_INITIALIZATION_FAILED
0x000000BB
NMI_HARDWARE_FAILURE
0x00000080
NMR_INVALID_STATE
0x00000125
NO_BOOT_DEVICE
0x00000053
NO_EXCEPTION_HANDLING_SUPPORT
0x0000000B
NO_MORE_IRP_STACK_LOCATIONS
0x00000035
NO_MORE_SYSTEM_PTES
0x0000003F
NO_PAGES_AVAILABLE
0x0000004D
NO_SPIN_LOCK_AVAILABLE
0x0000001D
NO_SUCH_PARTITION
0x00000043
NO_USER_MODE_CONTEXT
0x0000000E
NPFS_FILE_SYSTEM
0x00000025
NTFS_FILE_SYSTEM
0x00000024
OBJECT_INITIALIZATION_FAILED
0x0000005E
OBJECT1_INITIALIZATION_FAILED
0x00000062
OS_DATA_TAMPERING
0x00000155
PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000CD
PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CC
PAGE_FAULT_IN_NONPAGED_AREA
0x00000050
PAGE_FAULT_WITH_INTERRUPTS_OFF
0x00000049
PAGE_NOT_ZERO
0x00000127
PANIC_STACK_SWITCH
0x0000002B
PASSIVE_INTERRUPT_ERROR
0x0000013B
PCI_BUS_DRIVER_INTERNAL
0x000000A1
PCI_VERIFIER_DETECTED_VIOLATION
0x000000F6
PDC_WATCHDOG_TIMEOUT
0x0000014F
PF_DETECTED_CORRUPTION
0x00000191
PFN_LIST_CORRUPT
0x0000004E
PFN_REFERENCE_COUNT
0x0000001C
PFN_SHARE_COUNT
0x0000001B
PHASE0_EXCEPTION
0x00000078
PHASE0_INITIALIZATION_FAILED
0x00000031
PHASE1_INITIALIZATION_FAILED
0x00000032
PINBALL_FILE_SYSTEM
0x00000059
PNP_DETECTED_FATAL_ERROR
0x000000CA
POOL_CORRUPTION_IN_FILE_AREA
0x000000DE
PORT_DRIVER_INTERNAL
0x0000002C
PP0_INITIALIZATION_FAILED
0x0000008F
PP1_INITIALIZATION_FAILED
0x00000090
PROCESS_HAS_LOCKED_PAGES
0x00000076
PROCESS_INITIALIZATION_FAILED
0x00000060
PROCESS1_INITIALIZATION_FAILED
0x0000006B
PROCESSOR_DRIVER_INTERNAL
0x00000143
PROFILER_CONFIGURATION_ILLEGAL
0x0000017B
QUOTA_UNDERFLOW
0x00000021
RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F8
RDR_FILE_SYSTEM
0x00000027
RECURSIVE_NMI
0x00000111
REF_UNKNOWN_LOGON_SESSION
0x00000047
REFERENCE_BY_POINTER
0x00000018
REFMON_INITIALIZATION_FAILED
0x0000006C
REFS_FILE_SYSTEM
0x00000149
REGISTRY_ERROR
0x00000051
REGISTRY_FILTER_DRIVER_EXCEPTION
0x00000135
RESERVE_QUEUE_OVERFLOW
0x000000FF
RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
0x0000010F
RESOURCE_NOT_OWNED
0x000000E3
RESOURCE_OWNER_POINTER_INVALID
0x00000132
SCSI_DISK_DRIVER_INTERNAL
0x0000002D
SCSI_VERIFIER_DETECTED_VIOLATION
0x000000F1
SDBUS_INTERNAL_ERROR
0x0000015A
SECURE_BOOT_VIOLATION
0x00000145
SECURE_FAULT_UNHANDLED
0x0000018D
SECURE_KERNEL_ERROR
0x0000018B
SECURITY_INITIALIZATION_FAILED
0x0000005F
SECURITY_SYSTEM
0x00000029SECURITY1_INITIALIZATION_FAILED
0x00000063
SERIAL_DRIVER_INTERNAL
0x00000038
SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
0x000000EC
SESSION_HAS_VALID_VIEWS_ON_EXIT
0x000000BA
SESSION1_INITIALIZATION_FAILED
0x0000006D
SESSION2_INITIALIZATION_FAILED
0x0000006E
SESSION3_INITIALIZATION_FAILED
0x0000006F
SESSION4_INITIALIZATION_FAILED
0x00000070
SESSION5_INITIALIZATION_FAILED
0x00000071
SET_ENV_VAR_FAILED
0x0000005B
SET_OF_INVALID_CONTEXT
0x00000030
SETUP_FAILURE
0x00000085
SHARED_RESOURCE_CONV_ERROR
0x0000001F
SOC_CRITICAL_DEVICE_REMOVED
0x0000014E
SOC_SUBSYSTEM_FAILURE
0x0000014B
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
0x000000C1
SPIN_LOCK_ALREADY_OWNED
0x0000000F
SPIN_LOCK_INIT_FAILURE
0x00000081
SPIN_LOCK_NOT_OWNED
0x00000010
STATUS_CANNOT_LOAD_REGISTRY_FILE
0xC0000218
STATUS_IMAGE_CHECKSUM_MISMATCH
0xC0000221
STORAGE_DEVICE_ABNORMALITY_DETECTED
0x00000140
STORAGE_MINIPORT_ERROR
0x000000F0
STORE_DATA_STRUCTURE_CORRUPTION
0x000001C7
STREAMS_INTERNAL_ERROR
0x0000004B
SYMBOLIC_INITIALIZATION_FAILED
0x00000064
SYNTHETIC_WATCHDOG_TIMEOUT
0x000001CA
SYSTEM_EXIT_OWNED_MUTEX
0x00000039
SYSTEM_LICENSE_VIOLATION
0x0000009A
SYSTEM_PTE_MISUSE
0x000000DA
SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
0x000000D4
SYSTEM_SERVICE_EXCEPTION
0x0000003B
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
0x0000007E
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x1000007E
SYSTEM_UNWIND_PREVIOUS_USER
0x0000003A
TARGET_MDL_TOO_SMALL
0x00000040
TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK
0x00000150
TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
0x000000CF
THIRD_PARTY_FILE_SYSTEM_FAILURE
0x00000108
THREAD_NOT_MUTEX_OWNER
0x00000011
THREAD_STUCK_IN_DEVICE_DRIVER
0x000000EA
THREAD_STUCK_IN_DEVICE_DRIVER_M
0x100000EA
THREAD_TERMINATE_HELD_MUTEX
0x4000008A
TIMER_OR_DPC_INVALID
0x000000C7
TOO_MANY_RECURSIVE_FAULTS
0x0000011E
TRAP_CAUSE_UNKNOWN
0x00000012
TTM_FATAL_ERROR
0x0000019B
TTM_WATCHDOG_TIMEOUT
0x000001A0
UCMUCSI_FAILURE
0x000001D8
UDFS_FILE_SYSTEM
0x0000009B
UNEXPECTED_INITIALIZATION_CALL
0x00000033
UNEXPECTED_KERNEL_MODE_TRAP
0x0000007F
UNEXPECTED_KERNEL_MODE_TRAP_M
0x1000007F
UNEXPECTED_STORE_EXCEPTION
0x00000154
UNMOUNTABLE_BOOT_VOLUME
0x000000ED
UNSUPPORTED_INSTRUCTION_MODE
0x00000151
UNSUPPORTED_PROCESSOR
0x0000005D
UP_DRIVER_ON_MP_SYSTEM
0x00000092
USER_MODE_HEALTH_MONITOR
0x0000009E
VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE
0x00000136
VHD_BOOT_INITIALIZATION_FAILED
0x0000012F
VIDEO_DRIVER_DEBUG_REPORT_REQUEST
0x000000ADVIDEO_DRIVER_INIT_FAILURE
0x000000B4
VIDEO_DWMINIT_TIMEOUT_FALLBACK_BDD
0x00000187
VIDEO_DXGKRNL_FATAL_ERROR
0x00000113
VIDEO_MEMORY_MANAGEMENT_INTERNAL
0x0000010E
VIDEO_SCHEDULER_INTERNAL_ERROR
0x00000119
VIDEO_SHADOW_DRIVER_FATAL_ERROR
0x00000114
VIDEO_TDR_FAILURE
0x00000116
VIDEO_TDR_TIMEOUT_DETECTED
0x00000117
VOLSNAP_OVERLAPPED_TABLE_ACCESS
0x0000012D
WDF_VIOLATION
0x0000010D
WFP_INVALID_OPERATION
0x000001D3
WHEA_INTERNAL_ERROR
0x00000122
WIN32K_ATOMIC_CHECK_FAILURE
0x00000160
WIN32K_CALLOUT_WATCHDOG_BUGCHECK
0x000001A2
WIN32K_HANDLE_MANAGER
0x00000137
WIN32K_POWER_WATCHDOG_TIMEOUT
0x0000019C
WIN32K_SECURITY_FAILURE
0x00000197
WINLOGON_FATAL_ERROR
0xC000021A
WORKER_INVALID
0x000000E4
WORKER_THREAD_INVALID_STATE
0x000001D2
WORKER_THREAD_RETURNED_AT_BAD_IRQL
0x000000E1
WORKER_THREAD_RETURNED_WHILE_ATTACHED_TO_SILO
0x0000019A
WORKER_THREAD_RETURNED_WITH_BAD_IO_PRIORITY
0x00000128
WORKER_THREAD_RETURNED_WITH_BAD_PAGING_IO_PRIORITY
0x00000129
WORKER_THREAD_RETURNED_WITH_NON_DEFAULT_WORKLOAD_CLASS
0x000001D6
WORKER_THREAD_RETURNED_WITH_SYSTEM_PAGE_PRIORITY_ACTIVE
0x0000015B
WORKER_THREAD_TEST_CONDITION
0x00000163
XBOX_ERACTRL_CS_TIMEOUT
0x00000356
XNS_INTERNAL_ERROR
0x00000057
See more information related to the topic how to fix windows 10 blue screen
How To FIX a Blue Screen on Windows 10
- Author: Tech YES City
- Post date: 2018-09-21
- Ratings: 4 ⭐ ( 9692 ratings )
- Match search results: Ever wondered how to fix those annoying blue screens in windows 10!? Well today I have some different kind of fixes that can help with those annoying BSODs. Here is a look at the top 5 Weird problems I have incurred.
Get Lastpass and never forget your passwords again! http://bit.ly/2xseXTe
Today I go through the top 5 weirdest problems I have when it comes to blue screens or BSODs with relation to Microsoft windows 10. How I fix them can be different to others, because this is not a generic guide but more some of the ‘weirder’ problems you maybe encounter:
Time Table:
1st Problem – 0:31 – Undervolted default settings
2nd Problem – 3:11 – Hibernation Mode and Low C-States not being supported
3rd Problem – 4:46 – Faulty or incompatible Memory Modules
4th Problem – 6:02 – Hardware Incompatibility
5th Prroblem – 7:40 – Faulty or Underwhelming Power SupplyCheck out Britec09’s Guide on memtest86 here: https://www.youtube.com/watch?v=1rELrucWAMY
Stay up to date with the latest updates here:
Twitter – https://www.twitter.com/techyescity
Instagram – https://www.instagram.com/techyescity
Discord – https://www.discord.gg/MGkHeDXFor a $1 a month you can help support the channel directly & gain access to an uncut special monthly live: http://www.patreon.com/techyescity
Check out my Video Editing PC Here – http://amzn.to/2oFKlrb
————————————————————————————————-
Music Provided by either: monstercat, chukibeats, epidemicsound, vlognocopyright or bassrebels
howtofixbsod top5weirdestcomputerproblems bluescreenofdeath
How To Fix A Windows 10 Blue Screen?
- Author: www.programatium.com
- Ratings: 4 ⭐ ( 4629 ratings )
- Match search results:
Windows 10 Blue Screen of Death – You Can Quickly Fix It
- Author: www.partitionwizard.com
- Ratings: 5 ⭐ ( 8618 ratings )
- Match search results: Want to Fix Windows 10 Blue Screen of Death Error? Here are step-by-step tutorials. Just choose most proper one and try them out.
Troubleshoot blue screen errors
- Author: support.microsoft.com
- Ratings: 3 ⭐ ( 8290 ratings )
- Match search results:
Fix: BSOD ( Bluescreen of Death) Errors Windows 10
- Author: answers.microsoft.com
- Ratings: 4 ⭐ ( 3218 ratings )
- Match search results: This is applicable for Windows 10 PC in any build which cannot boot or go to Desktop Screen (Laptop/Desktop) Common Bluescreen Error : BSOD error codes: 0x0000000A This BSOD means that Microsoft
Fix Guide of Recovery Blue Screen on Windows 10
- Author: www.diskpart.com
- Ratings: 3 ⭐ ( 1675 ratings )
- Match search results: Here’s a fix guide of recovery blue screen on Windows 10 to provide suitable solutions for users to repair different blue screen errors.
How to troubleshoot and fix Windows 10 blue screen errors
- Author: www.windowscentral.com
- Ratings: 4 ⭐ ( 7878 ratings )
- Match search results: In this guide, we’ll show you several ways to troubleshoot and resolve the Blue Screen of Death (BSOD) error on a computer running the latest version of Windows 10.
See more articles in this category: Computer tips