What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
“Faulting application name” is not a diagnosis. It is a field in a Windows Application Error record, usually Event ID 1000, that identifies the executable that crashed. Event ID 1001 may appear with it and contains Windows Error Reporting details. The record also lists a faulting module, exception code, offset, process ID, file paths and report ID. Use those details to identify the failing process and choose the next test; do not delete a DLL or reinstall Windows solely because one file is named.
For a game crash, start with updates and a time-line of recent changes. If the crash repeats, collect a dump with Windows Error Reporting LocalDumps. Page heap and WinDbg can then show whether the executable, a plug-in, a driver interaction or memory corruption is responsible.
As an Amazon Associate I earn from qualifying purchases.
What “Faulting application name” means
Open Event Viewer and you may see an Application Error entry whose details begin with labels such as Faulting application name, Faulting module name and Exception code. The first label is simply the name of the executable Windows observed crashing—for example, a game’s launcher or main process. It does not identify the underlying bug.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Microsoft describes repeated Event ID 1000 and Event ID 1001 entries in the Application log as an application-crashing behavior. Event ID 1000 is the crash record itself. Event ID 1001 is associated Windows Error Reporting information when reporting is enabled. A single event can be transient; a pattern that occurs every launch, after a particular level, or at the same point in play is more useful diagnostically.
#1 Best Overall
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
Where to find the record
- Press
Win, typeEvent Viewer, and open it. - Choose Windows Logs > Application.
- Use Filter Current Log… and enter
1000under Event IDs. Search for a nearby 1001 entry as well. - Open an event and use the General and Details tabs. Copy the values before changing anything.
How to read every important field
| Field | What it tells you | What it cannot prove |
|---|---|---|
| Faulting application name | The executable process that terminated. | That the executable itself contains the original defect. |
| Application version | The version running when the crash occurred. | That updating will definitely fix the crash. |
| Faulting module name | The module in which Windows reported the exception. | That this file caused the corruption. |
| Module version | The version of that DLL or executable at the time. | That the module is unsafe or should be deleted. |
| Exception code | A category for the failure, such as access denial, access violation or heap corruption. | A complete root-cause analysis without context or a dump. |
| Fault offset | The offset inside the reported module where the exception was recorded. | A source-code line by itself. |
| Process ID | Identifies the process instance that crashed. | Which earlier process or component corrupted its memory. |
| Application and module paths | The exact files Windows loaded. | That a file at that path is the only component involved. |
| Report ID | Associates the event with Windows Error Reporting data. | A repair instruction. |
Save the event as text or take a screenshot that includes the timestamp. The time is essential when matching a crash with a game update, graphics-driver change, plug-in installation or antivirus event.
Is the faulting module the bad file?
Not automatically. Microsoft notes that commonly used Windows modules such as ntdll.dll, kernel32.dll and kernelbase.dll often appear as the faulting module. These libraries participate in many ordinary process operations. If another component damaged memory earlier, Windows may not detect the damage until one of these libraries later touches the damaged data. The named system DLL can therefore be the victim rather than the source.
The same caution applies to a third-party DLL. A module name is a lead: check its path, version and relationship to the game, overlay, anti-cheat component, plug-in or driver. Do not download a replacement DLL from an unofficial site, overwrite a Windows DLL, or remove a file solely because Event ID 1000 names it. Those actions can create a second problem and destroy evidence.
First-line triage for a game crash
Basic triage is appropriate when you need a quick answer and the crash is not yet reproducible. It provides limited evidence, but it is low-risk and low-disruption.
- Record the event. Copy the executable name and version, module and version, exception code, offset, process ID, paths, report ID and timestamp.
- Update Windows. Install pending operating-system updates, restart, and test the same action again. Note the update date in your timeline.
- Update the game. Confirm that the affected title and its launcher are current. If the game has a repair or file-verification function, use that vendor-provided function rather than deleting random files.
- Check security software. Bring antivirus definitions and the antivirus application up to date. If the vendor documents an exclusion required for the game, apply only that necessary, narrowly scoped exclusion; do not broadly disable protection.
- Correlate recent changes. Compare the event time with a graphics driver, Windows update, overlay, mod, plug-in, capture tool or configuration change. Temporarily return one changed component at a time to its prior state and retest.
- Reproduce safely. Use the shortest repeatable action—launch, load a save, open a menu or join a match. Avoid repeatedly stressing a system if it is overheating, losing power or showing disk errors.
If the game stops crashing after one controlled change, keep that change documented and restore components one at a time. If the event continues with no clear trigger, move to dump-based diagnostics instead of guessing from the module name.
Basic triage versus dump-based diagnostics
| Approach | Evidence depth | Skill and disruption | Best escalation target |
|---|---|---|---|
| Updates, timeline and controlled retest | Shows when and under what conditions the crash occurs. | Low technical skill; usually little disruption. | Game support when a current build still fails. |
| WER LocalDumps | Captures process state at the crash for later analysis. | Moderate setup; uses disk space and may require permissions. | The publisher of a third-party game or executable. |
| GFlags page heap plus WinDbg | Can expose heap corruption closer to where it is introduced. | Advanced; can change process behavior and should be temporary. | An experienced vendor engineer or Microsoft Support for a Microsoft executable. |
Collect a crash dump with WER LocalDumps
Windows Error Reporting LocalDumps can be configured for one executable so a full dump is written when that process crashes. Microsoft’s example configuration stores up to 10 full dumps in a folder you choose. A dump can be large, so select a folder with adequate free space and restrict access because it may contain game data, account names or other process memory.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Configure a per-executable dump
- Create a folder such as
C:CrashDumpsGameName. Ensure the account running the game can write to it. - Open
regeditas an administrator and navigate toHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsWindows Error ReportingLocalDumps. - Create a subkey whose name exactly matches the crashing executable, including
.exe. - Inside that subkey, create
DumpFolderas an expandable string value pointing to the dump folder,DumpCountas a DWORD that limits retained files (Microsoft’s example uses 10), andDumpTypeas a DWORD set to2for a full dump. - Close Registry Editor, restart the game, and reproduce the crash once. Check the folder for a newly created
.dmpfile and note its timestamp.
Configure the key for the executable that actually appears in Event ID 1000. A launcher may remain running while a separate game executable crashes; placing the key under the launcher name will not capture the game process.
Protect and remove the collection setting
Copy the dump to a secure location before sending it. After collection, remove the executable’s LocalDumps subkey (or disable the values) so every future crash does not consume storage. Do not leave full dumps enabled indefinitely on a shared computer.
Use page heap when heap corruption is suspected
Exception code 0xc0000374 indicates STATUS_HEAP_CORRUPTION. In that situation, Microsoft’s recommended escalation path is GFlags page heap for the affected executable, followed by a dump analysis in WinDbg. Page heap changes allocation behavior so invalid heap use is more likely to be caught near the operation that caused it. Because it can increase memory use and alter timing, apply it only for a controlled test.
- Install the Windows debugging tools that include GFlags and WinDbg.
- Enable page heap for the exact executable name with GFlags. Use the full executable name, not a shortcut or launcher label.
- Restart the process completely; a running process does not adopt the setting until it starts again.
- Reproduce the crash while watching the configured dump folder. Record which build, save file and plug-ins were active.
- Open the resulting dump in WinDbg and run the
!analyzeextension. Review the exception, thread, stack and loaded modules rather than treating one line as conclusive. - Disable page heap after the test and remove the LocalDumps registry key when you no longer need it.
A dump is evidence for a vendor, not a guarantee that a player can identify the bug alone. A game publisher can match the call stack and module versions against its own symbols and known defects.
Exception codes: useful clues, not final diagnoses
| Code | Meaning | Practical implication |
|---|---|---|
0xc0000022 |
STATUS_ACCESS_DENIED |
Investigate permissions, security software and the resource the process was trying to access. The event alone does not identify which access was denied. |
0xc0000005 |
STATUS_ACCESS_VIOLATION |
Consider invalid memory access, a damaged module, an incompatible plug-in or earlier corruption. A dump is needed for persistent failures. |
0xc0000374 |
STATUS_HEAP_CORRUPTION |
Use the temporary page-heap and dump workflow when the crash can be reproduced. |
Codes narrow the investigation but are not a complete diagnosis without the failing context. The same code can result from different components, so avoid selecting a repair solely from the hexadecimal value.
Should you run SFC, DISM or reinstall the game?
When an app repair or reinstall is reasonable
Use the game’s built-in repair or verification first when only one title fails, the event points to that title’s executable or a title-specific module, and the problem began after an interrupted update or damaged installation. Reinstalling is more disruptive than verification and does not fix an external overlay, driver, security product or recurring Windows problem. Preserve saves and configuration according to the game publisher’s instructions before removing the installation.
Rank #3
- WINDOWS 11 | STABLE PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 system, this laptop delivers stable performance for everyday computing tasks. It supports web browsing, online learning, document editing, email communication, and basic office work with optimized power efficiency, providing a practical and reliable experience for essential daily use for daily use.
- 15.6” FHD IPS DISPLAY: Features a 15.6-inch Full HD IPS display with narrow bezels, offering wider viewing angles and clearer image details compared to standard panels. The improved screen-to-body ratio enhances visual experience for study, reading, document work, and video playback, making it suitable for both productivity and entertainment use.
- 4GB DDR4 + 128GB eMMC STORAGE: Equipped with 4GB DDR4 memory and 128GB eMMC storage for everyday basics such as browsing, documents, email, and online learning platforms. The built-in TF card slot supports storage expansion up to 1TB, giving you more flexibility for files, photos, videos, and daily documents. TF card not included.
- CONNECTIVITY & PORTS: Includes 1× TF card slot, 2× USB 3.2 Gen1 ports, and 2× full-featured Type-C ports (USB 3.2 Gen1). The Type-C ports support data transfer, charging, and video output, enabling flexible connection with external devices such as monitors, storage, and peripherals for daily work and study use.
- LIGHTWEIGHT DESIGN | ONLINE COMMUNICATION: Designed with a slim, portable profile, this laptop is easy to carry for school, commuting, and travel. A built-in 1MP front camera supports online classes, video meetings, remote communication, and everyday conferencing. The 3300mAh battery works with the low-power system design to support practical daily use, while thermal optimization helps maintain quieter operation during extended tasks.
When system-file repair deserves consideration
Event ID 1000 by itself does not establish that Windows component files are damaged, so SFC or DISM should not be an automatic ritual after every game crash. Consider system repair when several unrelated applications fail, Windows components also report errors, or other evidence points to operating-system corruption. Run the supported Windows repair procedure for your edition, restart, and retest the original reproduction case. If only one game continues to fail while other applications are stable, return attention to the game and its add-ons rather than repeating system repair.
Who should analyze the dump?
Third-party game or tool
Send the dump, Event ID 1000 text, Event ID 1001 details if present, exact application version, Windows version, reproduction steps and a list of recent changes to the publisher or vendor of the crashing executable. Follow its privacy and upload instructions; a full dump can contain sensitive in-memory data.
Microsoft first-party executable
If the faulting application is a Microsoft executable and the failure persists after current updates and controlled testing, contact Microsoft Support. Include the same event fields and dump information. Ownership matters because only the component owner can interpret private symbols, source context and build-specific defects.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Common scenarios and the safest next move
- The game crashes once after an update: record the event, restart, verify the game update and check for a matching driver or overlay change before deeper diagnostics.
- Every launch produces Event ID 1000 with a Windows DLL: do not replace the DLL. Update Windows and the game, check antivirus activity, then collect a dump if reproducible.
- Crashes occur only with a mod, plug-in or overlay: reproduce with that component disabled, one change at a time. If the crash disappears, provide the component owner with the event and reproduction details.
- Several unrelated programs crash with different modules: treat the pattern as broader than one game. Check Windows and security-software state and consider system-level support.
- The event includes
0xc0000374: use temporary page heap and WinDbg rather than guessing from the named DLL.
Cleanup and records that make support effective
Keep one folder containing the event text, dump timestamp, executable version, Windows build, reproduction steps and a timeline of changes. Label each dump with the date and build. Remove temporary GFlags settings and LocalDumps keys after collection, and delete copies you no longer need. This prevents stale diagnostic settings from changing later tests and limits exposure of process memory.
Bottom line
“Faulting application name” tells you which process stopped, while Event ID 1000 records the crash and Event ID 1001 supplies related Windows Error Reporting data. The faulting module is a clue, not proof that the named file is defective. Start with current Windows, game and antivirus software and a controlled timeline. For a repeatable failure, capture a per-executable dump; use page heap and WinDbg for suspected heap corruption. Give third-party dumps to the game vendor and Microsoft-process dumps to Microsoft Support.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
