Hi. Just to try to help the other guy with a similar problem in another topic. Yesterday i've had the same problem described by someone else. While cleaning a customer computer, i've used kaspersky tdsskiller to clean a tdl4 infected mbr. After that the symptons where the same as reported by the other guy (computer bsod after some seconds with a stop 0x8e, could boot fine in safe mode, but any changes with msconfig where lost after reboot, and in my case, while the computer said it was generating a memory.dmp, no new dump as found.) Spend the afternoon disabling services & drivers with msdart, and was getting nowhere. Tried bootrec Fixmbr/fixboot, slaved the hdd to another machine and run kaspersky AV on it and nothing as found.
Almost at that point of giving up and starting rebuilding the machine from scratch, started to think for a minute and realized that the problems started after tdsskiller repaired/rebuild the mbr. So, i've used testdisk to write a new mbr, run windows startup repair, and then the machine was booting and running fine in 5 minutes again. My conclusion (may be wrong, i wish i've saved the tdsskiller mbr before generating a new one with testdisk), there is something wrong with the way tdsskiller fixes the mbr.
just my 2 cents
Edited by Orange Blossom, 21 October 2010 - 03:56 PM.
Move to AV forum. ~ OB