Trusted Platform Module (Tddl.dll) Problem - Crashing Laptop

[mbressman]

I recently received a T43p that I was going to swap for my current T42p. I did not have time to start from scratch, so thought I could save myself a lot of time by simply pulling out the HD in the T42p and putting it in the T43p. After having to upgrade the firmware on the HD, things seem to have gone well (I obviously knew I would have to install new drivers for some of the changed hardware), but I'm experiencing a problem with the NSC/Winbond Trusted Platform Module (TPM) drivers/software. Everytime I attempt to install, it asks for the tddl.dll file and then immediately freezes when apparently attempting to install this file. I've tried with the most up-to-date drivers on IBM/Lenovo's site, and it still occurs. I was told to try download the new chipset, and when attempting to do that, it just prompts me for this file eventually and then freezes again. Anyone have any advice on how I can fix this problem? I'd be happy to offer further information if needed. Thanks for the help!

Marc

[mbressman]

I think I've figured out some more information after some research. Apparently, the type of HAL my OS has installed is affecting this. In the new hard drive that came with the T43p, the HAL type is ACPI Uniprocessor, but in the old hard drive from the T42p, the HAL type is Advanced Configuration and Power Interface (ACPI). It seems that these two different HAL types affect IRQ and this is causing the problem with the TPM driver. I don't know how to really resolve this, or even if any of this makes sense completely...but am just posting some more information so that I can hopefully get some help from someone out there.

Is it possible to change the HAL type to ACPI Uniprocessor without having to reinstall the OS? Would this solve the TPM (and any other hidden) problems?

I've heard that this issue can apparently be resolved by manually setting the TPM to IRQ 11 ( http://www.msfn.org/board/lofiversion/i ... 34227.html ) ... does this make sense...is it worth trying?

[moore101]

We had this problem when getting our T40-42 image working on T43 systems. Honestly we had no valid reason for the TMP chip so the device is just set to disabled in device manager.

When going to the T60's the HAL from the T40-43 would not work. There is a company called acronishttp://www.acronis.com that has a product called True Image with universal restore and it has the ability to image a system then some how modify it so when it downloads to another computer the HAL is configured automatically for the new system. This solved the BSOD we were getting on the T60 systems and also let windows see the 2nd core of the core duo processors.

Good luck!

[courtneydidit]

Yes I have this problem too, on a R52. What happenned is that the HAL was accidentally replaced by the Standard PC one. When I restored the original ACPI HAL, every hardware piece was automatically updated by XP in Device Manager and working fine, except this TPM thing. Truth is the TPM chip appears to be an experimental technology and they should not put this in a computer mainboard !

When attempting to update manually the TPM driver, it freezes the machine. After a bit of research, I decided that this TPM thing was not worth reinstalling because I need to disable it now that I know it exists !

This chip is a way to uniquely identify your computer in computer networks that support the protocol and is nothing else than an attempt by major corporations to introduce piracy counter-measures universally. Meaning at some point in time you will need to enable the chip to access some resources and services and at that point it will be too late...

Fixing the driver matters, but once it's done, the chip should be disabled to protect your privacy and that of others.

That being said thanks for the IRQ 11 idea I will try it and get back to you guys with my results...