This article provides information how to repair the Windows Blue Screen error "STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP".
If you have a Windows blue screen error STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP, you may be able to gain some basic information on the code alone. Refer to the Microsoft Support documentation on the Blue Screen. Troubleshooting from the Microsoft support site is re-published here for your convenience:
- Test the RAM in the computer by running the diagnostic software that is provided by the computer manufacturer.
- Replace any RAM that is reported as bad.
- Make sure that all the RAM in the computer is the same speed.
- Try removing or swapping out controllers, cards, or other peripherals.
- Try a different motherboard on the computer.
Included below are generic troubleshooting steps. Not every Blue Screen requires an Operating System reinstall. In fact most can be repaired. These steps are not specific to the actual code and may not be necessary for every Blue Screen error. Research other documentation like the Microsoft Answers blog.
To isolate the cause, run PSA/ePSA diagnostics.
For detailed instructions on running PSA/ePSA diagnostics, refer to Dell Knowledge Base Article: Run Built-In Diagnostics for Your System.
- If diagnostics fail, access the Dell Interactive Support Agent and search the error codes to determine which part is causing the error.
- If diagnostics pass, identify when the Windows Blue Screen occurs.
- Pre-boot: To determine a faulty part, isolate the memory by connecting 1 module at a time, and isolate the hard disk by connecting a known good hard disk to the system until the faulty part is discovered.
- Pre-logon: Boot into Safe Mode and disable all Startup entries. Isolate 1 Startup entry at a time until you find the causing agent.
- Intermittent / post logon: Collect the minidump files by navigating to C:\windows\minidump and analyzing the minidump files using a tool called BlueScreenView developed by Nirsoft. You can also use Windbg and use the link to Dell.com to set up the debug. Identify the causing agent and reinstall the appropriate driver or application. If the issue still persists, it may be necessary to perform a windows reinstallation.