Critical error start menu isn"t working


In this article

Try our Virtual Agent - It can help you quickly identify & fix common Windows boot issues

If you"re not a support agent or IT professional, you"ll find more helpful information about stop error ("blue screen") messages in Troubleshoot blue screen errors.

Bạn đang xem: Critical error start menu isn"t working

Applies to: Windows 10

What causes stop errors?

A stop error is displayed as a blue screen that contains the name of the faulty driver, such as any of the following example drivers:


There"s no simple explanation for the cause of stop errors (also known as xanh screen errors or bug kiểm tra errors). Many different factors can be involved. However, various studies indicate that stop errors usually aren"t caused by Windows components. Instead, these errors are related khổng lồ malfunctioning hardware drivers or drivers that are installed by third-party software. These drivers include video clip cards, wireless network cards, security programs, và so on.

Our analysis of the root causes of crashes indicates that:

70% are caused by third-party driver code.10% are caused by hardware issues.5% are caused by code.15% have unknown causes, because the memory is too corrupted to analyze.


The root cause of stop errors is never a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a stop error, it is merely exposing the underlying bug which is always in a driver, hardware, or the OS.

General troubleshooting steps

To troubleshoot stop error messages, follow these general steps:

Review the stop error code that you find in the event logs. Search online for the specific stop error codes lớn see whether there are any known issues, resolutions, or workarounds for the problem.

Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. Lớn verify the update status, refer lớn the appropriate update history for your system. For example:

Make sure that the BIOS and firmware are up-to-date.

Run any relevant hardware và memory tests.

Make sure that there"s sufficient không tính tiền space on the hard disk. The exact requirement varies, but we recommend 10-15 percent không lấy phí disk space.

Contact the respective hardware or software vendor khổng lồ update the drivers & applications in the following scenarios:

The error message indicates that a specific driver is causing the problem.You"re seeing an indication of a service that is starting or stopping before the crash occurred. In this situation, determine whether the service behavior is consistent across all instances of the crash.

Memory dump collection

To configure the system for memory dump files, follow these steps:

Select the Taskbar tìm kiếm box, type Advanced system settings, và then press Enter.On the Advanced tab on the System Properties box, select the Settings button that appears in the section Startup và Recovery.In the new window, select the drop-down below the option Write debugging information.Choose Automatic memory dump.Select OK.Restart the computer for the setting to take effect.If the hệ thống is virtualized, disable auto reboot after the memory dump file is created. This disablement lets you take a snapshot of the server in-state and also if the problem recurs.

The memory dump file is saved at the following locations:

Dump tệp tin typeLocation
(none)%SystemRoot%MEMORY.DMP (inactive, or grayed out)
Small memory dump tệp tin (256 kb)%SystemRoot%Minidump
Kernel memory dump file%SystemRoot%MEMORY.DMP
Complete memory dump file%SystemRoot%MEMORY.DMP
Automatic memory dump file%SystemRoot%MEMORY.DMP
Active memory dump file%SystemRoot%MEMORY.DMP

You can use the Crash Dump file Checker (DumpChk) tool to lớn verify that the memory dump files aren"t corrupted or invalid. For more information, see the following video:

For more information on how to use Dumpchk.exe to check your dump files, see the following articles:

Pagefile settings

For more information on pagefile settings, see the following articles:

Memory dump analysis

Finding the root cause of the crash may not be easy. Hardware problems are especially difficult to diagnose because they may cause erratic và unpredictable behavior that can manifest itself in various symptoms.

When a stop error occurs, you should first isolate the problematic components, và then try lớn cause them to trigger the stop error again. If you can replicate the problem, you can usually determine the cause.

You can use the tools such as Windows Software Development Kit (SDK) and symbols to diagnose dump logs. The next section discusses how to lớn use this tool.

Advanced troubleshooting steps


Advanced troubleshooting of crash dumps can be very challenging if you aren"t experienced with programming & internal Windows mechanisms. We have attempted lớn provide a brief insight here into some of the techniques used, including some examples. However, to lớn really be effective at troubleshooting a crash dump, you should spend time becoming familiar with advanced debugging techniques. For a đoạn clip overview, Debugging kernel mode crashes and hangs. Also see the advanced references listed below.

Advanced debugging references

Debugging steps

Locate the memory.dmp tệp tin in your Windows directory on the computer that is crashing, & copy that file to another computer.

Start the install & choose Debugging Tools for Windows. The WinDbg tool is installed.

Go to the File menu và select Symbol file Path to mở cửa the WinDbg tool and set the symbol path.

Select Open Crash Dump, and then mở cửa the memory.dmp file that you copied.


Under Bugcheck Analysis, select !analyze -v. The command !analyze -v is entered in the prompt at the bottom of the page.

A detailed bug kiểm tra analysis appears.


Scroll down lớn the STACK_TEXT section. There will be rows of numbers with each row followed by a colon and some text. That text should tell you what DLL is causing the crash. If applicable, it also says what service is crashing the DLL.

There are many possible causes of a bug kiểm tra and each case is unique. In the example provided above, the important lines that can be identified from the STACK_TEXT are 20, 21, và 22:

1 : nt!KeBugCheckEx2 : nt!PspCatchCriticalBreak+0xff3 : nt!PspTerminateAllThreads+0x1134cf4 : nt!PspTerminateProcess+0xe05 : nt!NtTerminateProcess+0xa96 : nt!KiSystemServiceCopyEnd+0x137 : nt!KiServiceLinkage8 : nt!KiDispatchException+0x1107fe9 : nt!KiFastFailDispatch+0xe410 : nt!KiRaiseSecurityCheckFailure+0x3d311 : ntdll!RtlpHpFreeWithExceptionProtection$filt$0+0x4412 : ntdll!_C_specific_handler+0x9613 : ntdll!RtlpExecuteHandlerForException+0xd14 : ntdll!RtlDispatchException+0x35815 : ntdll!KiUserExceptionDispatch+0x2e16 : ntdll!RtlpHpVsContextFree+0x11e17 : ntdll!RtlpHpFreeHeap+0x48c18 : ntdll!RtlpHpFreeWithExceptionProtection+0xda19 : ntdll!RtlFreeHeap+0x24a20 : FWPolicyIOMgr!FwBinariesFree+0xa7c221 : mpssvc!FwMoneisDiagEdpPolicyUpdate+0x1584f22 : mpssvc!FwEdpMonUpdate+0x6c23 : ntdll!RtlpWnfWalkUserSubscriptionList+0x29b24 : ntdll!RtlpWnfProcessCurrentDescriptor+0x10525 : ntdll!RtlpWnfNotificationThread+0x8026 : ntdll!TppExecuteWaitCallback+0xe127 : ntdll!TppWorkerThread+0x8d028 : KERNEL32!BaseThreadInitThunk+0x1429 : ntdll!RtlUserThreadStart+0x21This issue is because of the mpssvc service, which is a component of the Windows Firewall. The problem was repaired by disabling the firewall temporarily and then resetting firewall policies.

Xem thêm: Giải Ảo Về Iptv Là Gì ? (Gợi Ý: Tv Của Bạn Sẽ Không Bao Giờ Giống Nhau)

For more examples, see Debugging examples.

Video resources

The following videos illustrate various troubleshooting techniques for analyzing dump files.

Advanced troubleshooting using Driver Verifier

We estimate that about 75 percent of all stop errors are caused by faulty drivers. The Driver Verifier tool provides several methods to help you troubleshoot. These include running drivers in an isolated memory pool (without sharing memory with other components), generating extreme memory pressure, và validating parameters. If the tool encounters errors in the execution of driver code, it proactively creates an exception. It can then further examine that part of the code.


Driver Verifier consumes lots of CPU và can slow down the computer significantly. You may also experience additional crashes. Verifier disables faulty drivers after a stop error occurs, and continues to vì this until you can successfully restart the system and access the desktop. You can also expect to see several dump files created.

Don"t try lớn verify all the drivers at one time. This kích hoạt can degrade performance & make the system unusable. It also limits the effectiveness of the tool.

Use the following guidelines when you use Driver Verifier:

Test any "suspicious" drivers. For example, drivers that were recently updated or that are known lớn be problematic.If you continue to lớn experience non-analyzable crashes, try enabling verification on all third-party and unsigned drivers.Enable concurrent verification on groups of 10-20 drivers.Additionally, if the computer can"t boot into the desktop because of Driver Verifier, you can disable the tool by starting in Safe mode. This solution is because the tool can"t run in Safe mode.

For more information, see Driver Verifier.

Common Windows stop errors

This section doesn"t contain a các mục of all error codes, but since many error codes have the same potential resolutions, your best bet is to follow the steps below lớn troubleshoot your error.

The following sections list general troubleshooting procedures for common stop error codes.


Stop error code 0x00000141, or 0x00000117

Contact the vendor of the listed display driver khổng lồ get an appropriate update for that driver.


Stop error code 0x0000000D1

Apply the latest updates for the driver by applying the latest cumulative updates for the system through the Update Catalog website. Update an outdated network driver. Virtualized VMware systems often run "Intel(R) PRO/1000 MT Network Connection" (e1g6032e.sys). You can tải về this driver from the Intel tải về Drivers & Software website. Contact the hardware vendor to lớn update the network driver for a resolution. For VMware systems, use the VMware integrated network driver instead of Intel"s e1g6032e.sys. For example, use VMware types VMXNET, VMXNET2, or VMXNET3.


Stop error code 0x000000050

If a driver is identified in the stop error message, liên hệ the manufacturer for an update. If no updates are available, disable the driver, & monitor the system for stability. Run chkdsk /f /r to detect and repair disk errors. Restart the system before the disk scan begins on a system partition. Contact the manufacturer for any diagnostic tools that they may provide for the hard disk subsystem. Try to lớn reinstall any application or service that was recently installed or updated. It"s possible that the crash was triggered while the system was starting applications & reading the registry for preference settings. Reinstalling the application can fix corrupted registry keys. If the problem persists, và you have run a recent system state backup, try khổng lồ restore the registry hives from the backup.


Stop error code c000021a Fatal System Error The Windows SubSystem system process terminated unexpectedly with a status of 0xc0000005. The system has been shut down.

Use the System file Checker tool khổng lồ repair missing or corrupted system files. The System tệp tin Checker lets users scan for corruptions in Windows system files & restore corrupted files. For more information, see Use the System tệp tin Checker tool.


Stop error code 0x000000024

This stop error is commonly caused by corruption in the NTFS tệp tin system or bad blocks (sectors) on the hard disk. Corrupted drivers for hard disks (SATA or IDE) can also adversely affect the system"s ability lớn read & write khổng lồ disk. Run any hardware diagnostics that are provided by the manufacturer of the storage subsystem. Use the scan disk tool lớn verify that there are no tệp tin system errors. To vị this step, right-click the drive that you want khổng lồ scan, select Properties, select Tools, và then select the check now button. Update the NTFS file system driver (Ntfs.sys). Apply the latest cumulative updates for the current operating system that"s experiencing the problem.


Stop error code 0x0000001E

If a driver is identified in the stop error message, disable or remove that driver. Disable or remove any drivers or services that were recently added.

If the error occurs during the startup sequence, & the system partition is formatted by using the NTFS file system, you might be able lớn use safe mode to disable the driver in Device Manager. To disable the driver, follow these steps:

Go khổng lồ Settings > Update & security > Recovery.Under Advanced startup, select Restart now.After your PC restarts to lớn the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.After the computer restarts, you"ll see a list of options. Press 4 or F4 to start the computer in safe mode. If you intend khổng lồ use the internet while in safe mode, press 5 or F5 for the Safe Mode with Networking option.


Stop error code 0x00000133

This stop error code is caused by a faulty driver that doesn"t complete its work within the allotted time frame in certain conditions. Lớn help mitigate this error, collect the memory dump file from the system, and then use the Windows Debugger to find the faulty driver. If a driver is identified in the stop error message, disable the driver to isolate the problem. Kiểm tra with the manufacturer for driver updates. Kiểm tra the system log in event Viewer for other error messages that might help identify the device or driver that"s causing stop error 0x133. Verify that any new hardware that"s installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications. If Windows Debugger is installed, and you have access to lớn public symbols, you can load the c:windowsmemory.dmp tệp tin into the debugger. Then refer to lớn Determining the source of Bug kiểm tra 0x133 (DPC_WATCHDOG_VIOLATION) errors on Windows vps 2012 to find the problematic driver from the memory dump.


Stop error code 0x0000009E

This stop error indicates that a user-mode health kiểm tra failed in a way that prevents graceful shutdown. Windows restores critical services by restarting or enabling application failover to other servers. The Clustering Service incorporates a detection mechanism that may detect unresponsiveness in user-mode components.

This stop error usually occurs in a clustered environment, và the indicated faulty driver is RHS.exe. Kiểm tra the sự kiện logs for any storage failures to lớn identify the failing process. Try khổng lồ update the component or process that"s indicated in the event logs. You should see the following sự kiện recorded:

Event ID: 4870Source: User mode health monitoring has detected that the system isn"t being responsive. The Failover cluster virtual adapter has lost liên hệ with the Cluster server process with a process ID "%1", for "%2" seconds. Recovery action is taken. Reviews the Cluster logs lớn identify the process and investigate which items might cause the process lớn hang.

For more information, see "0x0000009E" Stop error on cluster nodes in a Windows Server-based multi-node failover cluster environment Also, see the following clip What to do if a 9E occurs.

Xem thêm: Dđặc Điểm Là Gì ? Phân Biệt Giữa Đặc Điểm, Đặc Trưng Và Đặc Tính?

Debugging examples

Example 1

This bug kiểm tra is caused by a driver hang during upgrade, resulting in a bug check D1 in NDIS.sys, which is a driver. The IMAGE_NAME tells you the faulting driver, but since this driver is s driver, it can"t be replaced or removed. The resolution method is khổng lồ disable the network device in device manager & try the tăng cấp again.