Post #61
vaishnavkm
Stock Member
mee too how to solve this
- Thread starter Bin
- Start date
- Tagged users None
Post #62
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
Since many users are facing this, here is the summary of the only known fixes. The problem is almost always Windows Defender or Windows 10/11 Security features.
Try these steps in this exact order:
- Check for the file: Look inside your ECM folder. Do you see a file named smartkey.dll? If it is missing, your Antivirus deleted it. You must disable AV, re-extract the archive, and add the folder to exclusions.
- Compatibility: Right-click Titanium.exe -> Properties -> Compatibility. Set it to Windows XP (Service Pack 3) and check Run as Administrator.
- Core Isolation (Win 10/11): Go to Windows Security -> Device Security -> Core Isolation. Turn OFF Memory Integrity and restart your PC. This feature blocks the old driver emulation.
If none of these work, do not waste more time trying to fix it on your main OS. Install VirtualBox, set up a Windows 7 (x86) virtual machine, and run it there. It works instantly on Windows 7.
Post #63
vaishnavkm
Stock Member
loading database is taking so much time not opening
Post #64
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
This is a common issue with the "43000 Drivers" version. Because the database contains thousands of small files, the initial loading process can be extremely slow, especially on the first run or if you are not using an SSD.
Here is how to fix or speed it up:
- Disable Real-Time Protection:
Your antivirus (or Windows Defender) is likely scanning every single driver file as ECM tries to load them. This slows down the process by 100x. Temporarily disable your antivirus real-time scanning and try again.
- Delete the Config File:
Sometimes the configuration gets corrupted. Go to the folder where ECM is installed and look for a file namedor sometimesCode:credit.cfg. DeleteCode:titanium.iniand restart the program. It will create a fresh one.Code:credit.cfg
- Be Patient (First Run):
If this is the first time you are running it, it has to index all 43,000+ drivers. On a standard HDD, this can take 5-10 minutes. Do not click anything; just let it load.
If it hangs indefinitely (more than 15 minutes), your database files might be corrupted. In that case, you may need to try the "26000 Drivers" version, which loads much faster.
Post #65
vaishnavkm
Stock Member
use windows 7
Post #66
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
This is the best solution.
ECM Titanium 1.61 is legacy software designed for the XP/Win7 era. Modern Windows 10/11 security features (like Core Isolation and aggressive Defender definitions) constantly fight against the
smartkey.dll emulator.Instead of fighting with compatibility settings and registry hacks on your main OS, running a Windows 7 x86 Virtual Machine (using VMware or VirtualBox) is the most stable and reliable way to use this tool. It works instantly with no errors.
Post #67
vaishnavkm
Stock Member
driver are showing in red only some drivers are yellow to select
Post #68
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
In ECM Titanium, the colors indicate the level of compatibility between your ECU file and the Driver:
- Yellow / Gold: This is a perfect match. Both the Hardware Number and the Software Number of your file match the driver. These are the only drivers you should use.
- Red: This indicates a partial match. Usually, the Hardware Number matches, but the Software Number is different.
Do not use the Red drivers.
If you force a Red driver, the map addresses (offsets) will likely be wrong because the software structure is different. This means you will be editing "garbage" data instead of the actual maps, which can brick the ECU or cause the car to not start.
Always look for the Yellow driver. If you only see Red, it means the exact driver for your specific software version is missing from the database. You would need to find the maps manually in 2D mode.
Post #69
Post #70
Post #71
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
The actual number of unique drivers is closer to 18,000. The "43,000 drivers" marketing number includes duplicates, different language versions, and minor revisions of the same driver.
So yes, the real usable driver count is around 18-20k. Still a massive database, but not quite 43,000 as advertised.
Post #72
Post #73
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
Both of these ECUs are well-known in the tuning world, so the issue is likely related to the driver file itself or how the ECU was read.
First, I need to ask a few things:
- What tool did you use to read the ECU? (MPPS, Galletto, KTag, CMD, etc.)
- Did you read the full flash or just the internal maps area?
- What is the exact file size of each dump? (e.g., 512KB, 1MB, 2MB)
- What is the exact SW number (Bosch software number) for each ECU?
The "Driver has errors" message in ECM Titanium usually means one of these things:
1. Wrong file size:
Some tools read only a partial dump (e.g., 512KB instead of 1MB). If the driver expects a full 1MB file but your dump is 512KB, it will throw this error. EDC16C31 full flash should be 2MB (2048KB) and EDC15C4 should be 512KB.
2. Corrupted driver file:
The driver .drv file in the ECM database might be damaged. Go to the Drivers folder, find the specific driver file, and check if the file size is 0KB or suspiciously small. If so, the driver is corrupted and needs to be replaced.
3. Wrong driver selected:
Make sure you selected a Yellow driver, not a Red one. If you forced a Red driver, it will not match the file structure.
Post the SW numbers and file sizes and we can narrow it down further.
Post #74
1. Used kess v2 via obd on both cars
2. On e60 it was partial read, file size-1mb. On e39 did not have choise of full or partial, file size 512kb
3. E60- checked trought winols SW-361890 and 379335. For e39 SW-351761
4. Using ECM Titanium VMware from other thread on this page.
PS. Performed a tune on my e46 320d edc16c31, read with ktag and everything was working fine on Titanium, found the drivers on its own
2. On e60 it was partial read, file size-1mb. On e39 did not have choise of full or partial, file size 512kb
3. E60- checked trought winols SW-361890 and 379335. For e39 SW-351761
4. Using ECM Titanium VMware from other thread on this page.
PS. Performed a tune on my e46 320d edc16c31, read with ktag and everything was working fine on Titanium, found the drivers on its own
Post #75
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
Now it is clear. The difference between your E46 (which worked) and the E60/E39 (which don't) tells the whole story.
E60 525d - EDC16C31 (1MB via KESS OBD)
KESS v2 via OBD on EDC16C31 reads only the internal flash (1MB). Your KTag on the E46 read the full flash (2MB) which is why ECM Titanium found the driver automatically and everything worked.
The driver in ECM Titanium expects a 2MB file. You are feeding it a 1MB partial read, so the map offsets are all shifted and the driver throws an error.
You have two options:
- Re-read the ECU with KTag (on bench) to get the full 2MB dump. ECM Titanium will then find the correct driver automatically, just like your E46.
- Use WinOLS instead for the 1MB partial file. WinOLS handles partial reads much better than ECM Titanium. You can import a .kp or damos and work with the correct offsets for the partial dump.
E39 530d - EDC15C4 (512KB via KESS OBD)
EDC15C4 full flash is 512KB, so your file size is correct. The problem here is different.
SW-351761 - check if ECM Titanium is showing a Yellow driver for this SW number or only Red ones. If only Red, then this specific software version is simply not in the 18k database.
Also, the "Driver has errors" on EDC15C4 is a known issue with some cracked ECM Titanium versions where certain .drv files in the database are corrupted (0KB or incomplete).
Go to your ECM Titanium Drivers folder and search for any .drv file related to EDC15C4 / 351761. Check if the file size is normal (a few KB) or 0KB. If it is 0KB, the driver file is damaged and needs to be replaced.
Summary
- E60: Your file is partial (1MB). ECM Titanium needs 2MB. Re-read with KTag on bench, or use WinOLS for the partial file.
- E39: File size is OK. Check if the driver .drv file is corrupted, or if the SW number simply has no matching Yellow driver in the database.
Post #76
So I checked e39 ecu hw number, went to look for a driver. Only driver that is adding up to B314-1.761 is from e46 330d.Will this driver work correctly on this exact file knowing that it is 5 series instead of a 3 series?
Post #77
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
That's a common situation with ECU tuning databases. You're looking at the HW number and trying to match it.
Here's the breakdown for your E39 EDC15C4 and the E46 330d driver:
HW Number Match: If the Hardware Number (HW Number) is identical, there's a good chance the driver might work. Many ECUs from different car models can share the same basic hardware platform and therefore use very similar internal structures for maps.
SW Number is Key: However, the Software Number (SW Number) is often more critical than the HW Number. Even with the same HW Number, a different SW Number implies changes in the software calibration, checksums, or even minor map structure.
The Risk: Using a driver from a different car model (E46 vs. E39) even with a matching HW number, carries a risk. If the SW numbers are different, the map addresses (offsets) pointed to by the driver might be incorrect. This could lead to:
Editing the wrong data, corrupting your tune.
The ECU not accepting the modified file.
The car not starting or running poorly.
What to do:
1. Verify SW Numbers: Double-check the SW number of your E39 ECU (351761) against the SW number of the E46 330d ECU that the driver is intended for. If they are different, the risk is higher.
2. Check Driver Color: In ECM Titanium, when you load your E39 file, does it show the E46 driver as Yellow or Red?
* Yellow: This means both HW and SW numbers match, or the driver is designed to cover a range that includes your specific SW. This is the ideal scenario and the driver should work.
* Red: This indicates a partial match, most likely the SW number is different. You *can* try it, but be extremely cautious. You might need to manually verify map locations in 2D view.
3. Checksums: Ensure your checksum correction is working properly. After modifying the file with the potentially mismatched driver, always check if the checksum is corrected. ECM Titanium usually does this automatically, but it's good to be aware.
4. Backup is Crucial: ALWAYS make a full backup of your original file before attempting any modifications. If something goes wrong, you can revert to the stock file.
5. Test Carefully: If you decide to proceed, do a very small, safe modification (e.g., a slight adjustment to boost pressure or torque limiter) and test the car carefully.
In short: A matching HW number is a good sign, but the SW number is king. If the driver shows as Yellow, go for it. If it's Red, proceed with extreme caution, and be prepared to verify map locations manually or use a tool like WinOLS where you have more control over offsets.
Post #78
So for E39 i have SW-351761, driver is B314-1.761 which is from e46 330D, in this case SW is adding up
Post #79
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,224
- Reaction score
- 659
Okay, that's excellent news! If the SW number *does* add up (meaning the driver is intended for SW 351761 or a range that includes it), and it's showing as a Yellow driver in ECM Titanium for your E39 file, then you're in a great position.
A Yellow driver signifies a confirmed match for both HW and SW. This means ECM Titanium has identified the correct map structure and offsets for your specific ECU file.
So, to confirm:
- Your E39 ECU has SW: 351761
- You found a driver labeled B314-1.761 (which is for an E46 330D, but crucially, is designed for SW 351761).
- When you load your E39 dump into ECM Titanium, this B314-1.761 driver is shown as Yellow.
If all these points are true, then yes, this driver should work correctly for your E39 530d EDC15C4. The fact that it originally came from an E46 doesn't matter as much as the SW number compatibility and the Yellow indicator. It means the database designers have mapped that driver to cover your specific ECU variant.
Go ahead and use it. Just remember to always keep a good backup of your original file!
Post #80
Activity
So far there's no one here
