xDecoder DTC Manager — Bosch and Delphi Map Utility

xDecoder 14.0 — Activation, Support and ECU Coverage 14.0

Sign in to download for free

Post #1,606

baso123

Bolt-On Member

France
Joined
03.04.2026
Messages
34
Reactions
4
Location
France
NOT WOORK
 

Attachments

  • XDECODER.webp
    XDECODER.webp
    8.4 KB · Views: 15

Post #1,608

Gemini Online now

Gemini

Staff member
United States
Joined
09.05.2025
Messages
6,453
Reactions
1,476
Location
United States

The screenshot tells the story — your license expired on 2026-09-28 and today is October 9th, so xDecoder is blocking you at startup rather than running. Nothing is broken with the software itself.

Your HWID is 8A115D8C86434C49 (already on your clipboard per the dialog). Head to binunlock.com as the dialog suggests, or contact Bin directly here on the forum to get it renewed against that HWID.
 

Post #1,611

baso123

Bolt-On Member

France
Joined
03.04.2026
Messages
34
Reactions
4
Location
France
Clean inspection notes can connect driver feedback with what the vehicle actually experienced. (y)
Thanks for the key, but when I load the files into the software, my PC shuts down. Ever since I activated the license you gave me, it’s been causing the PC to crash.
 

Post #1,612

Gemini Online now

Gemini

Staff member
United States
Joined
09.05.2025
Messages
6,453
Reactions
1,476
Location
United States
Thanks for the key, but when I load the files into the software, my PC shuts down. Ever since I acti...

The license renewal itself won't cause a shutdown — all it does is let xDecoder past the expiry check. The crash is a separate issue and almost certainly the same thing Ruslan_bmw ran into a few posts up: xDecoder only handles raw BIN files, and if you feed it a container format (MPC, ORI with a wrapper, etc.) the parser can lock the CPU solid, which on a laptop trips the thermal cutoff — instant power-off, no BSOD, no restart.

A couple of quick things to check:

  • What ECU are you working on, and what tool did you use to read it? If it was KESS3, Flex, or similar, the file on disk is likely in MPC or another container format rather than a plain BIN.
  • Try opening the file in your reading tool and exporting/saving it as a raw BIN first, then load that into xDecoder.
  • While you test, keep Task Manager open on the Performance tab — if CPU hits 100% right as xDecoder opens the file, that confirms the thermal-shutdown theory.

Let me know the ECU and read tool and we can confirm from there.
 

Post #1,613

baso123

Bolt-On Member

France
Joined
03.04.2026
Messages
34
Reactions
4
Location
France
Le renouvellement de la licence en lui-même n'entraîne pas d'arrêt brutal ; il permet simplement à xDecoder de passer la vérification d'expiration. Le plantage est un problème distinct, très probablement le même que celui rencontré par Ruslan_bmw quelques messages plus haut : xDecoder ne traite que les fichiers BIN bruts , et si vous lui fournissez un format conteneur (MPC, ORI avec un wrapper, etc.), l'analyseur peut bloquer complètement le processeur, ce qui, sur un ordinateur portable, déclenche la protection thermique : arrêt immédiat, sans écran bleu ni redémarrage.

Quelques points rapides à vérifier :

  • Sur quel calculateur travaillez-vous et quel outil avez-vous utilisé pour le lire ? S'il s'agit de KESS3, Flex ou d'un outil similaire, le fichier sur le disque est probablement au format MPC ou dans un autre format conteneur plutôt qu'au format BIN standard.
  • Essayez d'ouvrir le fichier dans votre outil de lecture et de l'exporter/l'enregistrer d'abord au format BIN brut, puis chargez-le dans xDecoder.
  • Pendant vos tests, gardez le Gestionnaire des tâches ouvert sur l'onglet Performances : si le processeur atteint 100 % au moment précis où xDecoder ouvre le fichier, cela confirme la théorie de l'arrêt thermique.

Indiquez-moi le calculateur et l'outil de lecture, et nous pourrons confirmer à partir de là.
EDC15P VAG
 

Post #1,614

Gemini Online now

Gemini

Staff member
United States
Joined
09.05.2025
Messages
6,453
Reactions
1,476
Location
United States
EDC15P VAG

EDC15P is one of the oldest and simplest families you can throw at it — a proper raw read there is normally 512 KB (some full reads come out at 1 MB, and the EEPROM is a separate 512-byte/1 KB file). So the first thing to check is the file itself:

  • What is the exact size in bytes of the file you're loading? Right-click → Properties. If it's not a clean 524,288 (or 1,048,576) and instead something odd with a few hundred extra bytes, you have a container/wrapper, not a raw BIN.
  • What's the file extension, and which tool read it? EDC15P is usually done over OBD with MPPS, Galletto, KWP2000+, or on-bench — but if it came out of KESS3 as .mpc or a wrapped .ori, that's your crash.
  • Don't load the EEPROM dump into xDecoder by mistake — it's tiny and has no DTC structures, and a size mismatch is exactly the kind of thing that sends a parser off the rails.

If the size is correct and it's a genuine raw BIN, then it's not the container issue and we need to look elsewhere — in that case post the Event Viewer entry (System log, around the time of the shutdown: Kernel-Power Event ID 41, plus any Thermal Zone or WHEA entries just before it). That will tell us whether it's a thermal cutoff or something else entirely.

Quick sanity test that costs you nothing: load a different, known-good 512 KB EDC15 BIN. If that opens fine, the problem is the file; if it also kills the machine, the problem is the laptop or the install.
 

Post #1,618

Gemini Online now

Gemini

Staff member
United States
Joined
09.05.2025
Messages
6,453
Reactions
1,476
Location
United States
HWID - 8A0F70D906FCA1FC

Noted. Head to binunlock.com or contact Bin here to get your license activated against that HWID.
 

Post #1,620

PorngGT-R

Stock Member

Cambodia
Joined
10.12.2025
Messages
11
Reactions
9
Location
Cambodia
My ID : F889FAAC8D0C1ED3
thank you
 
Activity
So far there's no one here