The answer is Windows Debugging Tools (WinDbg), which you use to open the .dmp file and analyze memory dump files to identify faulty drivers. This tool is correct because it performs post-mortem debugging by parsing the crash dump data, allowing you to examine the stack trace and loaded module list to pinpoint the specific driver or module that triggered the IRQL_NOT_LESS_OR_EQUAL stop code. On the CompTIA A+ Core 2 220-1202 exam, this scenario tests your understanding of how to diagnose blue screen errors using built-in Windows tools, often contrasting WinDbg with simpler utilities like Event Viewer or the Blue Screen View tool—a common trap is assuming Event Viewer provides the same driver-level detail. A solid memory tip is to remember that WinDbg is for “deep dive” debugging of dump files, while Event Viewer is for a high-level error summary; think “Dump = Debug” to recall that WinDbg is your go-to for analyzing memory dump files.
220-1202 Windows OS Features and Tools Practice Question
This 220-1202 practice question tests your understanding of windows os features and tools. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A Windows 10 workstation is experiencing random blue screen errors with the stop code 'IRQL_NOT_LESS_OR_EQUAL'. You suspect a faulty driver. You need to analyze the memory dump files to identify the offending driver. Which built-in tool should you use to view the dump file?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Windows Debugging Tools (WinDbg) – open the .dmp file.
WinDbg (Windows Debugging Tools) is the correct built-in tool for analyzing memory dump (.dmp) files. It can parse crash dump data and identify the specific driver or module that caused the IRQL_NOT_LESS_OR_EQUAL stop code by examining the stack trace and loaded module list. This is the standard approach for post-mortem debugging of blue screen errors.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Event Viewer (eventvwr.msc) – filter by System logs with level 'Error'.
Why it's wrong here
Event Viewer shows error events but does not analyze memory dump files; it may show related events but not the dump itself.
✗
Performance Monitor (perfmon.msc) – add a Data Collector Set for crash dumps.
Why it's wrong here
Performance Monitor tracks performance counters, not crash dump analysis.
✗
Windows Memory Diagnostic (mdsched.exe) – run a memory test.
Why it's wrong here
This tool tests physical RAM for errors, but it does not analyze existing dump files.
✓
Windows Debugging Tools (WinDbg) – open the .dmp file.
Why this is correct
WinDbg is designed to debug crash dumps and can identify the driver causing the stop error.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the distinction between tools that record crash events (Event Viewer) versus tools that analyze the actual dump data (WinDbg), leading candidates to mistakenly choose Event Viewer because they see 'Error' logs related to the crash.
Trap categories for this question
Command / output trap
Event Viewer shows error events but does not analyze memory dump files; it may show related events but not the dump itself.
Detailed technical explanation
How to think about this question
When a Windows system crashes with a stop code like IRQL_NOT_LESS_OR_EQUAL, the kernel writes a memory dump file (e.g., C:\Windows\MEMORY.DMP or a minidump in %SystemRoot%\Minidump). WinDbg loads this file and uses the Microsoft Symbol Server to resolve function names and driver modules. The !analyze -v command in WinDbg automatically highlights the faulting driver by examining the trap frame and stack trace, often pinpointing the exact .sys file responsible.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the 220-1202 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 220-1202 question in full detail.
Windows OS Features and Tools — This question tests Windows OS Features and Tools — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Windows Debugging Tools (WinDbg) – open the .dmp file. — WinDbg (Windows Debugging Tools) is the correct built-in tool for analyzing memory dump (.dmp) files. It can parse crash dump data and identify the specific driver or module that caused the IRQL_NOT_LESS_OR_EQUAL stop code by examining the stack trace and loaded module list. This is the standard approach for post-mortem debugging of blue screen errors.
What should I do if I get this 220-1202 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 220-1202 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1202 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.