Results are grouped by useful content—not by paid placement or guessed parts. Describe the symptom naturally; IAR recognizes common alternate wording while keeping exact codes and vehicle details precise.
Your available vehicle context is included where the destination supports it. AI guidance stays separate from verified IAR source records.
Emissions systems control combustion byproducts and fuel vapor while monitoring performance. A code reports what a monitor detected; it does not automatically name the part that caused the result.
System guideThe fuel system stores and meters fuel under controlled conditions. A no-start, lean code, odor, or hesitation can involve supply, command, air measurement, electrical control, mechanical condition, or vapor management.
System guideThe cooling system moves heat away from the engine and releases it through controlled coolant flow and airflow. Overheating demands immediate safety judgment before diagnosis.
System guideHVAC comfort depends on airflow, heat exchange, temperature control, doors, sensors, and—for air conditioning—a sealed refrigerant system. Warm air alone does not identify a failed compressor.
System guideTreat gasoline or diesel odor as a safety signal first, then separate a liquid leak, vapor-system concern, refueling spill, exhaust odor, and cabin-source issue without running the vehicle beside an active leak.
professional recommendedClassify smoke or a burning smell by location, color, timing, and nearby systems before attempting another drive or touching a hot component.
intermediateCabin heat complaints can come from engine temperature, coolant level/circulation, airflow, blend-door/control operation, or an electric heat source on some vehicles.
intermediateWater inside the cabin after rain, washing, or HVAC use can come from drains, seals, glass, body openings, or condensation. Locate the path before removing trim or blaming a coolant leak.
intermediateA wheel that locks, a brake that stays applied, or a vehicle that pulls with heat or odor can become a control and fire hazard. Stop driving and separate friction, hydraulic, parking-brake, mechanical, and control evidence with the exact vehicle procedure.
professional recommendedTreat overheating as a stop-and-assess condition, then separate coolant loss, airflow, circulation, control, and combustion concerns.
professional recommendedUse scan data and operating patterns to separate ignition, mixture, air, fuel, mechanical, mount, and control concerns.
intermediateTreat active hot coolant loss as a burn and overheating hazard, then inspect the cooled system to separate external leakage, cap/sealing concerns, trapped air, and possible internal loss.
intermediateGrinding or scraping during braking can indicate friction-material, hardware, rotor/drum, shield, bearing, or debris concerns. Braking performance and heat determine whether the vehicle should be driven at all.
professional recommendedA fuel-economy complaint is meaningful only after establishing a repeatable baseline and separating normal operating changes from engine, emissions, tire, brake-drag, drivetrain, or temperature-control faults.
intermediateAn EVAP code identifies a monitored vapor-control condition, but the useful next test depends on whether the evidence points to a leak/sealing fault, purge-flow fault, electrical circuit fault, or an incomplete monitor.
intermediateA restricted filter can reduce airflow, but blower, door, and evaporator conditions can also matter.
Verify vehicle intervalThe control system reached a rich-condition diagnostic threshold for Bank 1. The data does not by itself prove an injector, fuel-pressure, MAF sensor, or oxygen-sensor failure.
Generic codeThe control system reached a rich-condition diagnostic threshold for Bank 2. The data does not by itself prove an injector, fuel-pressure, MAF sensor, or oxygen-sensor failure.
Generic codeThe catalyst monitor determined that Bank 1 oxygen-storage performance was below its calibrated threshold. The code alone does not prove the converter is the original cause.
Generic codeThe catalyst monitor determined that Bank 2 oxygen-storage performance was below its calibrated threshold. The code alone does not prove the converter is the original cause.
Generic codeThe generic EVAP monitor reported a system-level malfunction. The code identifies the monitored emissions system, not a failed cap, valve, hose, canister, sensor, or other specific part.
Generic codeThe generic EVAP monitor detected purge-flow behavior outside its expected strategy. The code does not prove the purge valve itself is failed; the flow path, sealing, sensing, electrical control, and vehicle-specific monitor conditions still have to be tested.
Generic codeThe control system reached a lean-condition diagnostic threshold for Bank 1. The data does not by itself prove a vacuum leak, MAF sensor, or fuel pump.
Generic codeThe control system reached a lean-condition diagnostic threshold for Bank 2. The data does not by itself prove a vacuum leak, MAF sensor, oxygen sensor, or fuel-delivery failure.
Generic codeThe EVAP monitor detected a small-leak or sealing condition. The code does not identify the physical leak location or prove which component failed.
Generic codeThe EVAP monitor detected a very small leak or inability to maintain the expected seal. The code does not identify the leak location or prove a specific valve, cap, hose, or canister failed.
Generic codeThe EVAP monitor detected a large-leak or inability-to-seal condition. It does not identify where the leak or control fault is located.
Generic codeThe engine did not reach the expected temperature behavior under the monitor’s conditions. The thermostat is one possibility, not the only one.
Generic codeThe control module detected a malfunction in the mass-or-volume-air-flow circuit. The code does not by itself identify the sensor, wiring, intake path, power/ground, or control module as the cause.
Generic codeThe measured or modeled airflow was outside the expected relationship. The code does not automatically mean the MAF sensor itself failed.
Generic codeThe control module detected a mass-or-volume-air-flow circuit signal in a low range for its monitoring strategy. The code does not by itself prove a MAF sensor, wiring, connector, intake path, power/ground, or control module is the cause.
Generic codeThe control module detected a mass-or-volume-air-flow circuit signal in a high range for its monitoring strategy. The code does not by itself prove a MAF sensor, wiring, connector, intake path, power/ground, or control module is the cause.
Generic codeIAR does not passively record this search. Save feedback only if you want a local note that you can export later for editorial planning. VIN-like vehicle identifiers are redacted before local save.