Loading IAR content
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.
Inspect condition and sealing; replacement intervals depend on vehicle and environment.
Verify vehicle intervalUse the exact oil specification, quantity, filter, interval, and reset procedure for the vehicle.
Verify vehicle intervalA restricted filter can reduce airflow, but blower, door, and evaporator conditions can also matter.
Verify vehicle intervalCoolant chemistry, concentration, capacity, fill, and bleed procedure vary by vehicle.
Verify vehicle intervalInterval and replacement scope are engine-specific; failure can cause severe damage on some designs.
Verify vehicle intervalA clean general workflow for inspecting and replacing a serviceable engine air filter without introducing debris or creating an intake leak.
beginnerA general cabin-filter replacement workflow that protects trim, wiring, airflow direction, and the HVAC case.
beginnerA safety-first overview of an oil and filter service with strict boundaries around support, oil specification, capacity, drain hardware, and level verification.
intermediateClassify whether the engine stalls at idle, under load, during deceleration, immediately after starting, or with a broader electrical power loss before choosing a test path.
intermediateTreat overheating as a stop-and-assess condition, then separate coolant loss, airflow, circulation, control, and combustion concerns.
professional recommendedUse operating conditions, code context, cylinder patterns, and targeted tests to separate ignition, fuel, air, mechanical, and control causes.
intermediateClassify an engine noise by when it occurs, where it is heard, and what warnings or operating changes accompany it before choosing a safe inspection path.
professional recommendedSeparate true transmission slip or shift flare from engine power loss, traction-control intervention, clutch concerns, and normal ratio changes before condemning a transmission.
professional recommendedSeparate airflow, control, compressor-command, heat-rejection, refrigerant-circuit, and electrical concerns without venting refrigerant or guessing a charge.
professional recommendedUse lamp behavior, symptoms, code status, freeze frame, readiness, and system tests to understand what the vehicle detected without treating a code as a parts order.
beginnerSeparate fuel, spark, compression, timing, and security-system faults with a test-first process.
IntermediateLocate and classify an oil leak, check the immediate safety clues, and separate a visible external leak from oil consumption or another fluid.
General guidanceFirst determine whether the engine cannot make power, the transmission is not transferring it, or a chassis/control system is limiting torque.
intermediateCabin heat complaints can come from engine temperature, coolant level/circulation, airflow, blend-door/control operation, or an electric heat source on some vehicles.
intermediateAn oil-pressure warning can represent actual lubrication-pressure loss or an electrical/sensor reporting fault. Because real pressure loss can damage an engine quickly, operation safety comes before diagnosis.
professional recommendedUse the first starting split—cranks or does not crank—to choose the correct electrical, authorization, fuel, ignition, or mechanical diagnostic path.
beginnerSeparate airflow, temperature, humidity, glass, control-door, blower, and cooling-system evidence before driving in conditions where the windshield cannot stay clear.
intermediateUse code data and targeted tests to distinguish ignition, fuel, air, and mechanical causes.
IntermediateThe engine does not rotate when starting. Separate battery, cable, starter-control, interlock, security, and starter faults before replacing anything.
intermediateUse scan data and operating patterns to separate ignition, mixture, air, fuel, mechanical, mount, and control concerns.
intermediateUse load, speed, engine rpm, gear, and steering input to separate axle, CV-joint, driveshaft, mount, wheel/tire, transmission, and engine-performance causes.
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.
intermediateA 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.
intermediateA soft, spongy, low, or sinking pedal can reflect hydraulic leakage or air, master-cylinder or control faults, mechanical adjustment or flex, and other foundation-brake concerns. Braking safety comes before diagnosis.
professional recommendedClassify an unfamiliar vehicle noise by location, timing, speed, load, and safety evidence before choosing a system-specific inspection path.
intermediateClassify smoke or a burning smell by location, color, timing, and nearby systems before attempting another drive or touching a hot component.
intermediateReduced braking, unusually long stopping, or a vehicle that will not stop normally is a stop-driving condition. Secure the vehicle first, then separate hydraulic, assist, friction, mechanical, and control-system evidence with qualified service information.
professional recommendedTreat 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 recommendedThe control module detected intake-air-temperature sensor behavior outside its expected range or relationship. The code does not by itself prove the sensor, wiring, connector, intake condition, or control module is the cause.
Generic codeThe control module detected an intake-air-temperature sensor signal in a low range for its monitoring strategy. The code does not by itself prove the sensor, wiring, connector, intake condition, or control module is the cause.
Generic codeThe control module detected an intake-air-temperature sensor signal in a high range for its monitoring strategy. The code does not by itself prove the sensor, wiring, connector, intake condition, or control module is the cause.
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 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 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 coolant-temperature sensor behavior outside the expected range or performance relationship. The code does not by itself prove the sensor, wiring, connector, actual engine temperature, or control strategy as the cause.
Generic codeThe control module detected a coolant-temperature sensor circuit signal in a low range for the vehicle’s monitoring strategy. The code does not by itself prove the sensor, wiring, connector, or engine temperature is the cause.
Generic codeThe control module detected a coolant-temperature sensor circuit signal in a high range for the vehicle’s monitoring strategy. The code does not by itself prove the sensor, wiring, connector, or engine temperature is the cause.
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 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 control module detected cooling-system temperature behavior outside its expected performance range. The code does not by itself identify a thermostat, coolant-temperature sensor, fan, coolant level, radiator, water pump, or other failed part.
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 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 module detected a misfire pattern associated with cylinder 1. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 2. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 3. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 4. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 5. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 6. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 7. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 8. It does not identify the failed component.
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 DTC identifies a purge-control valve circuit condition. It does not prove the purge valve itself is mechanically or electrically failed; wiring, connectors, power/ground, driver control, and exact circuit design must be tested.
Generic codeThe generic DTC identifies an open-circuit condition in the purge-control valve circuit. It narrows the electrical fault type, but it still does not prove the purge valve itself is the failed part.
Generic codeThe generic DTC identifies a short-circuit condition in the purge-control valve circuit. It does not establish whether the short is in the device, harness, connector, supply/control path, or module driver.
Generic codeThe generic DTC identifies a vent-control circuit malfunction. It does not identify whether the fault is the vent device, wiring, connector, power/ground, control driver, or another exact-vehicle circuit condition.
Generic codeThe generic DTC identifies an open-circuit condition in the EVAP vent-control circuit. It does not prove the vent valve or solenoid itself is failed.
Generic codeThe generic DTC identifies a short-circuit condition in the EVAP vent-control circuit. It does not identify the exact location of the short or prove the vent device itself is the cause.
Generic codeThe generic DTC identifies a malfunction in the EVAP vent valve or solenoid control circuit. It is a circuit-level finding, not proof that the vent valve or solenoid should be replaced.
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 turns stored fuel energy into controlled torque. Good diagnosis separates a combustion problem from a mechanical, control, mounting, or support-system problem before parts are removed.
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 guideThe starting system must authorize the request and deliver high current long enough to rotate the engine. A no-crank condition is different from an engine that cranks normally but does not run.
System guideA transmission changes the relationship between engine or motor speed and wheel speed. Shift concerns can originate in fluid condition, controls, sensors, engine operation, mounts, driveline parts, or internal wear.
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 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 engine or emissions control system has detected a condition that should be investigated. The lamp alone does not identify a failed part.
Assess promptlyThe engine or cooling system is reporting excessive temperature or a related protection condition. The warning does not identify whether the cause is coolant loss, airflow, circulation, control, or internal leakage.
Stop and assessIAR 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.