View Full Version : Yet another BSoD

21.12.2003, 14:03
Operating System: Windows 2000 SP4
Burning Software: Nero
Anti-virus Software: AVG 6.0.554
DAEMON Tools Version: 3.43

Updated to 3.43 and got a nasty blue screen at reboot (error: KMODE NOT SUPPORTED -- couldn't log the whole message). Had to boot in Safe Mode in order to manually delete the d343bus and d343port files which prevented my system from starting up. Reverted to 3.41 for now.

21.12.2003, 18:13
Send latest dmp file from C:\winnt\minidump to andareed@daemon-tools.cc

23.12.2003, 04:15
Operating System: Windows 2000 + SP4
Burning Software: Nero Burning ROM
Anti-virus Software: Norton Antivirus 2002
DAEMON Tools Version: 3.43

Daemon tools works fine during first reboot after install.
It will shows the "STOP" screen, at another reboot after install.
The screen shows:
STOP: 0x0000001E (0xC0000005, 0xEB461A59, 0x00000000, 0x00000028)

I have to delete the d343port.sys and d343bus.sys in order
to boot up the system. I don't have minidump for this and
my system is not SMP.

05.01.2004, 17:40
Operating System: Windows 2000 + SP4
Burning Software: Nero 6.3
Anti-virus Software: None
DAEMON Tools Version: 3.43

I also did get this stop/blue screen:

STOP: 0x0000001E (0xC0000005, 0xEB461A59, 0x00000000,0x00000028)

This happend after installing version 3.43.
I'm now back to version 3.41.

Is this fixed in version 3.44 ?

05.01.2004, 17:49
Check with v3.44, if you get BSOD again, mail newest minidump to support@daemon-tools.cc with reference to this thread.

21.01.2004, 20:22
Operating System: Windows 2000 SP4 with nearly all silly stuff from Microsoft installed
Burning Software: Nero (Plextor OEM license)
Anti-virus Software: H+BEDV AntiVir
DAEMON Tools Version: 3.43 stable, 3.44 crashing

STOP: 0x0000001E (0xC0000005, 0xEB461A59, 0x00000000, 0x00000028)

Same here, but with the new 3.44, now downgraded to 3.43 which works. The BSOD only appears when a CD writer is present in the system. I have an USB writer, so testing this is quite easy :wink:
Whenever 3.44 is installed and the writer is recognized by windows the computer crashes while installing the driver. My USB hard drive works quite fine, so it should not be the USB storage driver which causes the crash.

What exactly does this "KMODE_EXCEPTION_NOT_HANDLED" mean?

22.01.2004, 03:24
It means Roxio drivers that you have in system as part of Media Player are buggy.

23.01.2004, 23:17
Seems like you were right, in the last crashes (with 3.43, which ran stable before) Windows told me a driver name - the Roxio DirectCD driver. I read about Roxio in the forum before posting my question, but I did assume that Windows produced the error by itself like usual :?

I searched the Microsoft Knowledge Base and found exactly one entry with this filename, not really describing my problem except for the error message, but it lead to http://softwareupdates.roxio.com/gm/support/5.3.2sp1_up.exe which is small but seems to work for me :D

It would be nice if you could remove DirectCD from a computer with a recent version of Media Player (version 9 has only the rollback option, no "change");
but it seems as if Microsoft and Roxio both are not really interested in that :evil: