AHG Posted March 9 Report Share Posted March 9 So I just scanned my car as I normally do from time to time (got the OBDeleven 3 so I just leave it connected) Not sure if I saw it previously, and if I did I probably deleted it, but, the new app scans fast and gives you a summary of the error codes with prioritization, so I notices today I have a code in the Brake Booster module saying the below: Has anyone here get it on a mk8 before ? If so, is it software, low current, harness malfunction, or actual "go to the shop" kind of trouble? I did scan it right after parking the car after driving it for 10min (after it being static for ver a week), and I am parked on a slight down slope (very slight but noticeable) if that matters. The web and its agents (e.g. Gemini) say it can be one of five things, starting from nothing all the way to the riders of the apocalypse, so not very helpful. Quote Link to comment Share on other sites More sharing options...
dv52 Posted March 9 Report Share Posted March 9 @AHG: Hi. Hmm...... whilst it's always prudent to look for the "riders of the apocalypse" in any DTC (Diagnostic Trouble Code) - I suspect the 4 x horsemen from the Book of Revelation are mercifully absent in this instance!! 😉 First: if you haven't already done so, I suggest that you activate the Freeze-frame facility against your OBD11 account - it will display much more information about the car's environment whenever a DTC is registered in fault memory - read HERE. OK, look at last entry in your screenshot - notice "Priority 6". This is VW's assessment of the importance of this DTC and it speaks volumes about your legitimate concerns!! I apologize if you already know this stuff - but VAG define a hierarchy of importance to most faults. It's a reverse protocol - meaning the highest priority DTC has the lowest number. A very summary explanation of the Priority listing is : Number Meaning 0 Undefined by manufacturer. 1 The fault has a strong influence on drivability, immediate stop is required. 2 The fault requires an immediate service appointment. 3 The fault doesn't require an immediate service appointment, but it should be corrected with the next service appointment. 4 The fault recommends an action to be taken, otherwise drivability might be affected. 5 The fault has no influence on drivability. 6 The fault has a long term influence on drivability. 7 The fault has an influence on the comfort functions, but doesn't influence the car's drivability. 8 General Note Your rating is "6", so certainly NOT urgent, but still worthy of surveillance - notice fault Status = static (i.e. not intermittent) !! Don Quote Link to comment Share on other sites More sharing options...
AHG Posted March 9 Author Report Share Posted March 9 Is static better or worse ? I think I saw fixed or active as the problematic one Intermittent as the occurrence dependent one And static as the passive one meaning it’s a background thing that’s always there and is not evolving But that’s just my logic 🙂 also, how come 6 is worse than 5 if the scale is meant to be going down in priority ? Quote Link to comment Share on other sites More sharing options...
AHG Posted March 9 Author Report Share Posted March 9 Will this help ? Quote Link to comment Share on other sites More sharing options...
dv52 Posted March 10 Report Share Posted March 10 On 10/03/2026 at 08:51, AHG said: Is static better or worse ? I think I saw fixed or active as the problematic one Intermittent as the occurrence dependent one And static as the passive one meaning it’s a background thing that’s always there and is not evolving But that’s just my logic 🙂 also, how come 6 is worse than 5 if the scale is meant to be going down in priority ? Hmm.......... "better, or worse"? The question is like asking whether blond hair colour is better or worse than auburn hair? The answer to the question is ALL about perspective and from a diagnostic point-of-view - a "static" DTC is more preferable than an "intermittent" error because it's stable. This means that the problem is likely to remain active during the fault-finding phase of the diagnostic process. As I'm sure you will agree - chasing intermittent faults that have a propensity to disappear is a real PITA! An "active" DTC means that there is a problem that is currently affecting the vehicle These DTCs will not clear until you fix the issue - and if they do clear, they will most likely return (unless the fault was triggered due to a glitch). Fix the problem, and the status of these codes will change from "active", at which point you can clear them. A "passive" DTCs indicates an issue that occurred previously but are not a problem when the SCAN report was generated (meaning when module fault memory was polled). There are lots of reasons why a DTC changes state - but "passive" DTCs can provide diagnostic intelligence of past errors or intermittent problems that may have been temporarily corrected but could return. As for your question about Priority "6" versus "5" - I have to claim the Nuremberg defense! 😉 I thieved the table in my reply from the VCDS site and it's clear that the descriptors have been summarized from what I suspect was originally a more fulsome set-of-words. So, in the same way that the Nazis in Nuremberg claimed that they were only following orders - my answer is that I just copied-and-pasted the table that was provided by more knowledgeable folk on the Ross-Tech mother-ship! And yes, I'm well aware that the Nuremberg defense was NOT successful in the war-trials! That said - maybe the distinction between the two categories is the period? The time frame for Priority 6 is the future - perhaps the time frame for Priority 5 is now? If I'm correct and if the word "now" is added to the Priority 5 descriptor - it makes more sense (I think). Regarding your freeze-frame screenshot - the date time stamp and the "Malfunction frequency counter" number is interesting. If I assume that you haven't cleared this error-code previously - can you remember what this car was doing on the 9th March at 18:18 hrs? In the alternative that you have previously cleared this error-code - maybe look through the entries in the History facility that is stored against your OBD11 account and determine the past trajectory of this fault Don Quote Link to comment Share on other sites More sharing options...
AHG Posted March 11 Author Report Share Posted March 11 1 hour ago, dv52 said: If I assume that you haven't cleared this error-code previously - can you remember what this car was doing on the 9th March at 18:18 hrs? In the alternative that you have previously cleared this error-code - maybe look through the entries in the History facility that is stored against your OBD11 account and determine the past trajectory of this fault So apparently I do have “freeze frame” sleeved in the settings, but I don’t know where it goes to and how to find it. I was either parking the car or sat parked and started scanning the car on Mar9 at 18:18, this I know for sure. My tracker app shows me the engine was running but my speed was 0 and I was at home. My first scan was time stamped 1’:19:54 so I assume I was already parked and fiddling with my phone, or just pulling the handbrake. As per the code, I found it in the history circa mid-2023. Intermittent. Didn trims it again, but I’m not sure it wasn’t there, as I saw two other booster module codes in the 2023 scan I frequently see and clear, but are intermittent and google made me believe they are meaningless (for some reason they don’t show in the history again, although I know they reappear). See pic below. A. Can’t it be just current fluctuations or some parking brake (hand-brake) “handshake” issue with gearbox ? (I usually just turn the engine off and expect the leaking brake to do what it does). B. Is unlearning meaning that I need 40 clean restarts for the code to go away ? C. Can’t it be a OBDeleven over-sensitivity thing ? My shop showed me several time som the Tiguan that not every code on the OBDeleven mew s a code on theIR VAS (OR ODIS). Quote Link to comment Share on other sites More sharing options...
dv52 Posted March 11 Report Share Posted March 11 @AHG : my comments to your sentences below: "So apparently I do have “freeze frame” sleeved in the settings, but I don’t know where it goes to and how to find it." Yes indeed, it would appear so -well done you! But you don't need to "find it" - in a very real sense, it finds you! Freeze-frame data is captured by the car's modules as part of the standard OBDii protocol if the fault has certain characteristics. Freeze-frame sits in the module's fault memory and it is extracted when you SCAN the car. The data is stored against your OBD11 account on OBD11's central servers in Lithuania. Whether freeze-frame data is included in your actual SCAN report depends on whether you have activated the facility. I have absolutely no idea why OBD11 switches-OFF freeze-frame as default - it makes no sense to me why anyone trying to understand error codes would not want to access freeze-frame data. VCDS has freeze-frame switched-ON as default -much more sensible!! For your questions "A" and "C": A C11876 -F6 error is entirely new to me - so thanks for providing a new learning opportunity (which I always relish). My quick search on the electric internet and a brief chat with my new best friend (AI) suggests that this fault-code is specific to the MKC1 integrated brake system in the Golf mk8 which is notoriously sensitive to pressure‑build plausibility checks. My understanding is that whenever the Brake booster module in a Golf mk8 under-goes a self-test, or the module detects a "driver initiated brake event" - a comparison-check is made between the actual hydraulic pressure rise in the brake circuit and the expected value as calculated by the algorithm in an internal braking model. If there is a discrepancy between the two numbers -the C11876 error-code is generated and the "F6" part provides further diagnostic intelligence about the particular error-event. So, the MKC1 booster on a Golf mk8 apparently performs these pressure-checks routinely. If the pressure ramp build-up is a tad outside tolerance, the tendency of the Brake booster module is to spit-the-dummy and log this fault-code - even if braking feels perfect for the driver. Again from my quick research - the likely cause of the error is often: • Slightly aerated fluid • Micro‑bubbles after recent service • Temperature‑dependent viscosity changes • A momentary deviation in the booster’s internal pressure model And some websites say that early Mk8 software (2020–2022 especially) had overly sensitive brake pressure modelling.- many cars log this code permanently, even after updates, with the following symptoms: • No warning on the dash • Perfect brake feel • Fault cannot be cleared (returns immediately) Which is exactly your observations - I think So, bottom-line: if there is NO evidence of at least one of the symptoms below: • Hard brake pedal • Hissing from booster • ABS/ESC lights appearing on the Dash • Longer stopping distance • Additional brake system DTCs (pressure sensor, pump, travel sensor) then the fault is almost certainly benign! Note: this hypothesis is based purely on my limited and very rudimentary research!!! Don PS: as for your question "Is unlearning meaning that I need 40 clean restarts for the code to go away?" - the answer is basically "yes". However, what you call "clean starts" is a strictly defined term in the language of OBDii speak. In essence, a recurrence of the same error-code is assessed during successive driving events known as "drive-cycles" - each of which must have a predetermined set of driving conditions to qualify as a suitable test-environment. So a "clean start" is NOT just ignition/engine -ON! A very rough equivalent of a drive-cycle is a short trip in moderate urban traffic. You can read about the specific conditions in a drive-cycle HERE Quote Link to comment Share on other sites More sharing options...
AHG Posted March 12 Author Report Share Posted March 12 Got it, or at least most of it, thank you very much. I do have freeze frame activated in my app. It was so by default so maybe they listened to you 🙂 I don’t have any change I could feel the braking process feels natural to me Had I not scanned the car I’d never know I don’t think I had brake fluid changes since 2024 Last service was July 2025 So that should not be a reason for it It is relatively colder here recently, so maybe brake fluid is becoming more viscous, but the only other record I have of it previously was when the car was about a year old, in July (so not cold). The only other thing I can think about is that the car stood for about a week, before the Mar9 drive I took, so maybe that affected it a bit, but the timestamp was at the end of that drive, just when I was finished parking (maybe it’s a parking brake thing). I cleared the code back in Mar9 (couldn’t trait 40 days) and scanned it yesterday (Mar 11) and I did get it again So maybe it is a good sign Perhaps just a weak battery due to it sitting for a while That can happen when I travel so may be the reason for it in 2023 I will try the check process you (or someone else) suggested (engine off, pump the brake pedal until it hardens, start engine and see if it yields a bit), and hopefully that would play out as it should. If it does, I’ll leave it at that and maybe ask for a diagnostic scan during my next service (in the summer. Brake fluid should be replaced then, it’ll be end of year 4). I do know there are many issues that only show up on OBDeleven but not a real problem. I know ODIS gets updated and readjusted for over-sensitivities, adding conditions for a error code to be flagged on its user interface, so it may ignore a code I can see on OBDeleven (happened to me with the Tiguan, having air quality sensor code, that did not show up in the scan, and the shop told me they know it was throwing codes for no reasons, so VW added conditions for it to be reported). Thank you for your great and profound explanations as always You are truly a fountain of knowledge (not only information) and I deeply appreciate it Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.