Dell XPS 8950 Bug Check Codes List
My Dell XPS 8950 I bought primarily for SteamVR started exhibiting bug checks at around six months old. It was eventually fixed under Dell's one-year warranty, but the journey started with an attempt to diagnose it myself. Stressing it with Folding@Home would crash it once roughly every 12-24 hours.
When Windows halts with a bug check, a memory dump file is written to disk for debug purposes. It takes significant expertise to dig through a memory dump file to pinpoint a root cause. However, it's pretty easy to get a general idea of what we are dealing with. We can install Windows debugger (WinDbg) and use its built-in automated analyzer to extract a top-level error code we can then look up online. Over the course of two weeks I ran Folding@Home to build a collection of memory dump files, hoping to find commonalities that might point at a source.
The best case scenario is to have the same bug check code on every dump, occurring in the same operating system component. What I got instead is a list of thirteen codes (appended at the bottom of this post), some more often than others. And even worse, they didn't all happen at the same place in the system but was spread all around. The only vague commonality between them is an invalid memory operation. Sadly, "invalid memory operation" is too broad of a category to tie to a root cause. I became quite discouraged looking over those memory dumps.
I know Dell tech support has a database of bug check codes and a list of diagnostic steps to address each of them. First level support technicians are trained to tell the customer to try each item in turn. Figure a half dozen things they want me to try (probably starting with "please turn off and back on again"...) for each of 13 possible codes means I will have to trudge through a lot of those procedures.
Eventually my support ticket will establish a widespread pattern that escalate my case to more senior support staff who will look at the problem more holistically, but I have to earn it with persistence! I will be spending a lot of time with Dell tech support, starting with their preinstalled troubleshooting tool called SupportAssist.
Bug check codes encountered, with URL of the Microsoft reference page and the first sentence of their explanation pasted in after the code.
- 0x00A IRQL_NOT_LESS_OR_EQUAL This bug check indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at an invalid address while at a raised interrupt request level (IRQL). The cause is typically a bad pointer or a pageability problem. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa--irql-not-less-or-equal
- 0x01A MEMORY_MANAGEMENT The bug check indicates that a severe memory management error occurred. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management
- 0x03B SYSTEM_SERVICE_EXCEPTION This can happen because a NULL pointer dereferenced or a random incorrect address was accessed. This in turn can be caused by memory being freed prematurely, or data structure corruption. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception
- 0x04E PFN_LIST_CORRUPT This indicates that the page frame number (PFN) list is corrupted. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x4e--pfn-list-corrupt
- 0x050 PAGE_FAULT_IN_NONPAGED_AREA This indicates that invalid system memory has been referenced. Typically the memory address is wrong or the memory address is pointing at freed memory. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x50--page-fault-in-nonpaged-area
- 0x07E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This bug check indicates that a system thread generated an exception that the error handler didn't catch. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled
- 0x0D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL This indicates that a kernel-mode driver attempted to access pageable memory while the process IRQL that was too high. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xd1--driver-irql-not-less-or-equal
- 0x0EF CRITICAL_PROCESS_DIED This check happens when the state of the process is corrupted or damaged. When the corruption or damage happens, as these processes are critical to the operation of Windows, a system bug check occurs as the operating system integrity is in question. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died
- 0x109 CRITICAL_STRUCTURE_CORRUPTION This indicates that the kernel has detected critical kernel code or data corruption. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x109---critical-structure-corruption
- 0x124 WHEA_UNCORRECTABLE_ERROR a fatal hardware error has occurred. This bug check uses the error data provided by the Windows Hardware Error Architecture (WHEA). https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error
- 0x139 KERNEL_SECURITY_CHECK_FAILURE This bug check indicates that the kernel has detected the corruption of a critical data structure. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure
- 0x13A KERNEL_MODE_HEAP_CORRUPTION This bug check indicates that the kernel mode heap manager has detected corruption in a heap. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x13a--kernel-mode-heap-corruption
- 0x18B SECURE_KERNEL_ERROR This indicates that the secure kernel has encountered a fatal error. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x18b--secure-kernel-error