LEMON Manuals: Even more car manuals for everyone
Home >> Chevrolet >> 2002 >> Blazer 4D Utility, 4WD, Part Time >> Repair and Diagnosis >> External Pages >> Different car >> Section 250 (Engine Controls Self-Diagnostics - 2.2L) >> Diagnostic Tests >> DTC P0336: Crankshaft Position Sensor Performance >> Diagnostic Procedure

Diagnostic Procedure

WARNING: This page is about a different car, the 2003 Pontiac Sunfire, 2003 Pontiac Grand Am, 2003 Oldsmobile Alero, and 2003 Chevrolet Cavalier. However, it is still accessible from the selected car via links, so may be relevant.
  1. Perform diagnostic system check - engine controls. See DIAGNOSTIC SYSTEM CHECK - ENGINE CONTROLS  under SELF-DIAGNOSTIC SYSTEM. After performing diagnostic system check - engine controls, go to next step.
  2. Attempt to start the engine. Does the engine start and run? If yes, go to next step. If no, go to NO-START DIAGNOSIS in BASIC DIAGNOSTIC PROCEDURES - 2.2L ALERO, CAVALIER, GRAND AM & SUNFIRE article.
  3. Observe the Freeze Frame/Failure Records data for this DTC. Turn ignition switch to OFF position for 30 seconds. Start the engine. Operate the vehicle within the Conditions for Running the DTC or as close to the Freeze Frame/Failure Records data observed. See CONDITIONS FOR RUNNING DTC . Does the DTC fail this ignition? If yes, go to next step. If no, go to step  5.
    4. WARNING: To prevent physical injury, avoid contact with moving parts and hot surfaces while working around a running engine.
  4. With engine running, wiggle PCM and CKP harness connectors and related circuits while listening for the engine to stumble. Does the engine stumble? If yes, go to step  6. If no, go to step  7.
  5. Operate any non-engine related electronic component on the vehicle. Observe the MED. RESOLUTION RESYNC COUNTER using the scan tool. Does the Med. Resolution Resync Counter on the scan tool increment while operating any non-engine related electronic components? If yes, go to step  9. If no, go to step  4.
  6. Turn ignition switch to OFF position. Check for an intermittent and for a poor connection at the connector that caused the engine to stumble. After repair, go to step  14.
  7. Did the MIL illuminate in step  3? If yes, go to next step. If no, go to step DIAGNOSTIC AIDS .
  8. Turn ignition switch to OFF position. Check for rubbed-through wire insulation or for pinched wiring in the PCM or CKP sensor circuits. Repair wiring as necessary. Did you complete the repair? If yes, go to step  14. If no, go to step  10.
  9. Turn ignition switch to OFF position. Repair circuitry of the malfunctioning or interfering component. Move any wiring that is causing the interference away from the CKP wiring harness. After repair, go to step  14.
  10. Replace CKP sensor. Visually inspect CKP sensor for the following conditions:
    • Any physical damage.
    • A loose or improper installation.
    • Any wiring routed too closely to the secondary ignition components.

    Did you find and correct the condition? If yes, go to step  14. If no, go to next step.

  11. Visually inspect the CKP reluctor wheel for damage or looseness. Did you find and correct the condition? If yes, go to step  14. If no, go to next step.
  12. Replace the CKP sensor. Idle the engine for 5 minutes or until the MIL illuminates. Did the MIL illuminate? If yes, go to next step. If no, go to step  14.
  13. Replace PCM. Perform PCM relearn procedure. See POWERTRAIN CONTROL MODULE REPROGRAMMING  under PROGRAMMING. After replacing PCM, idle the engine for 5 minutes or until the MIL illuminates. Did the MIL illuminate? If yes, go to DIAGNOSTIC AIDS . If no, go to next step.
  14. Using scan tool, clear the DTCs. Turn ignition switch to OFF position for 30 seconds. Start the engine. Operate the vehicle within the Conditions for Running the DTC. See CONDITIONS FOR RUNNING DTC . Did the DTC fail this ignition? If yes, go to step  2. If no, go to next step.
  15. Using a scan tool, observe CAPTURE INFO. Does the scan tool display any DTCs that you have not diagnosed? If yes, see DIAGNOSTIC TROUBLE CODE DEFINITIONS . If no, system is okay at this time.
scientia non olet · About LEMON Manuals