Windows BSODs while loading...

blackllotus

Golden Member
May 30, 2005
1,875
0
0
Windows starts loading fine whenever I start up my computer, but after a few seconds a BSOD flashes (I can't read it) and then it restarts (this is Windows XP Pro w/ Service Pack 2). It won't start up in Safe Mode either. It displays "Press ESC to stop loading stpd.sys". Pressing ESC has the same effect as not doing anything at all, the computer just restarts.

Now I did some research and found that the error, which is actually a driver error, is caused by a bug in Daemon Tools (its software for cd-drive emulation). All the sources I've found say to delete sptd.sys, but I can't figure out a way to do that without Windows. I would like to be able to delete the file without having to reinstall windows, but my boot cds are crappy. Linux can only read the ntfs file system, not write to it and the same appears to be true with DrDOS. I use an OEM version of Windows (I built the computer), so theres no "restore to factory state" or anything like that that comes on a Dell or w/e.

If worst comes to worst I can either reinstall Windows on the same partition, or, preferably, I can install windows again on a separate partition/drive, delete stpd.sys from there, and then load up my old Windows. However, I'm wondering if anybody knows of any software that can be created into a bootable cd and can read/write to an ntfs file system. I found this for Linux that I could potentially use (I don't know if its safe), but I'm curious if anyone knows of any other programs. I know its going to take longer searching and asking around for various solutions instead of just reinstalling Windows, but I want to find a fast solution that I can use in the future as well.
 

jackwhitter

Golden Member
Dec 15, 2000
1,048
0
0
Ultimate boot cd has experimental write support for writing to ntfs. knoppix may also have write support (not 100% sure). also, a win xp boot disk can drop you to the recovery console and delete from there. i'd recommend the recovery console.
 

phios

Member
Mar 14, 2004
147
0
0
Ok, hold up on the Linux thing for a second. You should be able to put your OEM XP disk into the computer, boot from the disk, and then get to command prompt via the "Recover XP" selection (I cannot remember the exact way of getting to the command prompt with the XP disk, but I've done it many times). From there, you login via your admin password and it will let you access the harddrive. You can then go and delete files to your hearts content. (Just like the above poster mentioned)

Phios
 

blackllotus

Golden Member
May 30, 2005
1,875
0
0
Recover XP gets directory enumeration errors while reading the drive, however NTFSDos and TestDisk both can read the drive perfectly. The problem is they can't edit or delete anything. I found this program NTFSDos Pro that supposedly has r/w access to ntfs drives, so I'm going to try that.
 

sieistganzfett

Senior member
Mar 2, 2005
588
0
0
make a bartpe cd, it will allow you to delete the file, you need to get to an xp pc, create the bootable cd using an xp cd, http://www.nu2.nu/pebuilder/ will list out how. its really nice to use. another thing you can do is use an xp or 2k cd to boot up the pc, then use the "recovery console" option for a DOS like enviroment that can let you delete the file.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
All of that is a lot of work.

Easier is simply to boot from the XP CD, boot into recovery console (hit F10 after you've let it boot for 5 minutes or so and it's at the first blue screen with white text), then log in (key in the admin password), and then you can go into the directory in question (probably c:\windows\system32\drivers) and delete that file or replace it with another version (copied via floppy disk).
 

corkyg

Elite Member | Peripherals
Super Moderator
Mar 4, 2000
27,370
240
106
For a really good study and tutorial on analyzing BSODs, get a copy of the September 2006 issue of Maximum PC" and turn to page 42. It has specific examples of common BSOD messages and a good crash course on how to use XP's EventViewer to determine the cause.
 

blackllotus

Golden Member
May 30, 2005
1,875
0
0
Originally posted by: dclive
Easier is simply to boot from the XP CD, boot into recovery console (hit F10 after you've let it boot for 5 minutes or so and it's at the first blue screen with white text), then log in (key in the admin password), and then you can go into the directory in question (probably c:\windows\system32\drivers) and delete that file or replace it with another version (copied via floppy disk).

I already said that didn't work.

Originally posted by: sieistganzfett
make a bartpe cd, it will allow you to delete the file, you need to get to an xp pc, create the bootable cd using an xp cd, http://www.nu2.nu/pebuilder/ will list out how. its really nice to use. another thing you can do is use an xp or 2k cd to boot up the pc, then use the "recovery console" option for a DOS like enviroment that can let you delete the file.

I tried Bart, it didn't work. A43 File Manager BSOD's and the command prompt couldn't find the directory.

Tomorrow when my friend gets home from a vacation I'm going to take my hard drive out and hook it up to his computer and try to delete the file from his version of windows. Until then I'm stuck with an old imac.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Originally posted by: blackllotus
Originally posted by: dclive
Easier is simply to boot from the XP CD, boot into recovery console (hit F10 after you've let it boot for 5 minutes or so and it's at the first blue screen with white text), then log in (key in the admin password), and then you can go into the directory in question (probably c:\windows\system32\drivers) and delete that file or replace it with another version (copied via floppy disk).

I already said that didn't work.

__

Reading above, I can't find it, unless you were talking about the recovery console when you wrote something about "Recover XP".

Did you do a chkdsk /p c: while in recovery console?