P0641 and P0651 concern sensor-reference voltage circuits, commonly identified as reference A and B or numbered reference circuits. They point to a supporting electrical system, not automatically to one named sensor or a failed engine computer. The exact definition and affected circuit must be checked for your vehicle.
When several sensor-related codes appear together, ask whether there is a common electrical cause before approving several replacement parts. Equally, do not assume every group of codes shares one cause. The wiring diagram, recorded faults and actual tests must establish the connection.
Reference voltage is not the battery-voltage reading
A controller can provide a regulated reference used by sensor circuits. Some sensors share a reference supply, so a problem on that shared path can affect more than one reported value. Which sensors belong together varies by vehicle; physical proximity does not prove they share a circuit.
Many service documents describe five-volt reference systems, but that is not a universal test target for every code or application. Mitsubishi's cited 2022 P0641 description uses a different reference-voltage criterion and a specific control-module context. Its example is a warning against transferring a generic voltage number or sensor list onto another engine. Mitsubishi P0641 description
Ask the technician to identify the monitored reference circuit and its intended function. A normal battery reading does not establish that every regulated supply and connected circuit is operating correctly.
Preserve the full pattern
Save all codes, their reporting modules, suffixes and current or historical status before anything is cleared. Include available failure records and the original warning messages. A list reduced to one convenient code can hide the pattern needed to choose the correct diagnostic path.
Describe whether the concern involved reduced power, a no-start, poor shifting or another change in operation. Record the timing of recent wiring, engine, battery or accessory work. Tell the shop if previous testing involved disconnected components, because those events can create a separate trail of fault records.
Do not repeatedly clear the codes to see which one returns first. Ask the technician what was present before testing and which faults appeared during diagnosis. That distinction helps keep the original problem separate from test-induced changes.
A harness fault can look like several different complaints
GM PI1067A covers 2013–2016 Chevrolet Equinox and GMC Terrain vehicles with the 3.6L LFX engine. It describes rare cases of reduced power, poor performance or shifting concerns with P0641 or other faults, caused by wiring rubbing against the engine-controller bracket. The publication notes that the physical fault is unlikely to affect more than one circuit in that particular condition. GM PI1067A
That example matters because multiple driver complaints do not establish multiple failed parts. It does not mean every Equinox reference fault occurs at that bracket, or that one damaged wire always explains every code. Ask where damage was actually found and how the findings relate to the recorded symptoms.
Leave harness access and testing to a technician. Do not pull on wires, pierce insulation or unplug sensors at random to make a warning change.
A software exception requires the complete matching pattern
GM bulletin 16-NA-180, November 2016, covers specified 2016 Chevrolet, Holden and Opel applications with listed engine RPOs. For its software-related reference-voltage concern, all four codes P0641, P0651, P0697 and P06A3 must be stored together. It explicitly sends individual reference codes to normal service-information diagnosis instead. GM bulletin 16-NA-180
For the matched software condition, the bulletin calls for calibration work rather than ECM replacement. That is not a universal reflash recommendation and does not apply just because P0641 or P0651 appears on a scanner. The shop must check vehicle applicability, the entire code group and current software information.
Historical bulletin coverage is also not a promise of current free repair. Ask for separate answers about the technical diagnosis and payment coverage.
What evidence should come before parts
A useful explanation identifies which reference circuit is abnormal, what it supplies on that vehicle, and where testing located the fault. Ask whether the supporting wiring and connections were assessed and what evidence distinguishes a connected-component fault from a controller problem.
If several sensors are recommended, ask for the failed-test evidence for each. A shared supply problem is a reason to investigate their relationship, not a reason to replace every sensor on the circuit. If an ECM is proposed, ask which checks support an internal controller failure rather than an external fault affecting it.
Do not apply battery power to a reference terminal, bridge supplies together, use an improvised test lamp on controller circuits or try to supply your own replacement voltage. These actions can damage electronics. This is a diagnostic discussion guide, not a wiring-isolation procedure.
Safe stopping and verification
If throttle response is unpredictable, power loss prevents safe progress, or the engine stalls, leave traffic as safely as possible and arrange assistance. A no-start vehicle needs assessment rather than repeated cranking. Do not use a restart that temporarily changes symptoms as proof the vehicle is repaired.
After repair, ask how the affected reference circuit and related signals were verified, whether the original complaint was addressed, and which faults remain. Keep the original scan and final report. If the problem was intermittent and could not be reproduced, the report should state that limitation rather than call an unconfirmed part replacement a verified fix.
Frequently asked questions
Does reference A mean bank 1 of the engine?
Do not infer sensor location from that label. Ask for the vehicle's circuit identification; a reference grouping is not a universal cylinder-bank map.
Is replacing the battery the first repair?
Not solely because a voltage-related code exists. Battery and electrical checks may be relevant, but the reference circuit needs its own diagnosis.
Can one code prove the software bulletin applies?
No. The GM example above has a specific vehicle and multi-code pattern. A partial match is not enough to adopt its correction.