SP3 BSOD with Deamon Tools

This is a discussion about SP3 BSOD with Deamon Tools in the Windows Software category; Happens on my buddy's computer as soon as you load any image with deamon tools BAM!! BSOD the fuct up part is i turned off the auto restart on BSOD and it still restarts and i can't see the BSOD Thist is the only 2k sp3 machine i have used so i don't know if it is the comp or some driver in the system or if it is a ...

Windows Software 5498 This topic was started by ,


data/avatar/default/avatar16.webp

1615 Posts
Location -
Joined 2000-03-25
Happens on my buddy's computer
as soon as you load any image with deamon tools BAM!! BSOD
the fuct up part is i turned off the auto restart on BSOD and it still restarts and i can't see the BSOD
 
Thist is the only 2k sp3 machine i have used so i don't know if it is the comp or some driver in the system or if it is a bug in sp3 itself.
anyways I tried versions 3.16 and 3.17 of deamon tools and both did the same, anyone else get this?

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.

Responses to this topic


data/avatar/default/avatar39.webp

3867 Posts
Location -
Joined 2000-02-04
Nope, 3.17 workin here with XP Pro SP1 and 2K SP3. Also works with just XP and 2K Sp2.

data/avatar/default/avatar16.webp

1615 Posts
Location -
Joined 2000-03-25
OP
yea i thought that it was weird
I saw this happen on one of the XP beta builds a while back
with an older version of DTools but nothing like this since
I am not really woried about it. It is not my computer and the dude doesn't need the program I jsut wanted to use it to put some stuff on there.

data/avatar/default/avatar19.webp

347 Posts
Location United States
Joined 2002-03-21
A few months ago I started getting BSOD whenever I disabled all drives. After uninstalling, rebooting, then reinstalling, the problem was fixed.