Jump to content
  • Who's Online   0 Members, 0 Anonymous, 13 Guests (See full list)

    • There are no registered users currently online
  • 0

EMC9 XP DLACDBHM Dell


RWE

Question

I allowed the Dell tool to upgrade Roxio 9;

allowed divx codec 6 to upgrade itself.

Now boot fails bluescreen with DLACDBHM.sys driver, even after I uninstall divx.

No restore points are available.

Suggestions?

 

(I see lots of discussion about Vista incompatibilities with EMC9...)

 

XP Home SP2

Dell Inspiron 300m

DRIVER_IRQL_NOT_LESS_OR_EQUAL; stop 0xD1 (0x0, 0x2, 0x1, 0xBADFAD40); DLABDBHM.SYS, addr BADFAD40, base BADFAD00, datestamp 44D0169E

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

Cannot uninstall.

In Safe Mode, attempts to uninstall Drag to Disc (or attempts to use msconfig to boot with the non-MS services off) fail; the former says software configuration prohibited by policy. (This is XP Home, so I can't edit policy.)

Checking the event log, I see events where microsoft authentication package is getting unknown-user for my login (which is an administrator, according to the Users control panel).

Which doesn't look good. I hope I'm missing something, but it appears that something's damaged in the security mechanisms so I won't be able to do administrator stuff like the above. As I recall, loggin on safe mode as administrator did the same thing; will verify that now.

 

If administrator safe-mode is also unable to uninstall, will there be any alternative to reinstalling the OS from scratch?

I do have network access; is there a replacement dlacdbhm.sys that would undo the problem (perhaps caused by roxio-vs-divx use of the folder/filename for different drivers)?

Link to comment
Share on other sites

Try adding a new administrator account and see of that fixes the permissions policy - it does sound as if something is flaky in the OS if you can't uninstall D2D

 

You could try manually deleting all roxio folders (including the hidden ones in Documents and Settings\Username\Aplication data) and running the Microsoft Installer CleanUp Utility but I'm not sure that would work given the problem

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...