Blue screen caused by tdrpm228.sys

Discussion in 'Acronis True Image Product Line' started by schufra, Jul 9, 2009.

Thread Status:
Not open for further replies.
  1. schufra

    schufra Registered Member

    Joined:
    Jul 9, 2009
    Posts:
    1
    Hello Acronis support team,

    I have Acronis True Image Home 2009 (build 9.769) installed on Windows Vista SP2. When inserting a disk into my Iomega ZIP100 drive the system crashes with a blue screen. The analasys of the short dump reveals that tdrpm228.sys, which, as far as I could figure out, is the Acronis driver for Try&Decide, is responsible for the crash.

    Best regards and thank you in advance for your help
     
  2. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello schufra,

    Thank you for using Acronis True Image

    You are right, tdrpm228.sys is Acronis driver. The only thing I can propose is to renew the Iomega Zip drive drivers. If this doesn't help, please contact the respective Iomega support department, maybe, they will be able to make their drive functional.

    Also, you can downgrade build #9796 to a previous build if it worked flawless.

    Thank you.

    --
    Oleg Lee
     
    Last edited: Jul 14, 2009
  3. jbn75

    jbn75 Registered Member

    Joined:
    Jul 21, 2009
    Posts:
    2
    I have the exact same problem if I insert a card into my USB card reader.
     
  4. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello all,

    Thank you for using Acronis True Image Home 2009

    The source of the issue is incompatibility between try and decide feature and service pack 2 of Windows Vista. To solve it disable try and decide service (right-click My Computer -> Manage -> Services -> find Acronis Try and Decide service right click Properties -> Disabled). The crash issue should be fixed but you will not be able to use Try and Decide feature.

    Best regards,
    --
    Dmitry Nikolaev
     
Thread Status:
Not open for further replies.