I beleive I have found the problem here. At least on my pc, If I go into bios and disable security on the MBR, Bootskin works. Once the skin is changed then I can re-enable the security and it works fine. Some bios list it as "Virus Warning" in the advanced options.

My first post I know but I had to comment on my experience with this problem.

Anytime!

I came here to find an answer to the problem with the BSOD... and I found that all the answers were like the one from Seabass. It's easy to see why BootSkin might get canned with this kind of problem. Users shouldn't have to change their bios to run the program, it could be dangerous if the end user doesn't know exactly what they're doing in there. However, I have yet to see a PC with the security option enabled by default, I suppose it could be on in some manufactured PC's like HP, Dell... Compaqs, who knows? (I build my own PC's) Newer motherboards have this option set to off by default and manufacturers instructions say to enable it once you have the operating system installed. This isnt the first time I've had this problem, I get it when there is a new service pack installed as well. So I always remember to turn it off prior to reboot.

When I got the BSOD after installing BootSkin and changing to one of the supplied skins... ACK! BSOD!! I managed to get in xp by selecting the startup option "Last known good configuration" Which restored the default bootscreen.

I had to think a second and it occurred to me that the bios is protecting the MBR from Viruses and any changes to it would be seen by BIOS as an attack, which then halts the system. Well, incidentally XP has the bootscreen as part of the main system... why? Who knows? Seems a bit needless for that to be a part of the core of the system as its only a graphic. So we can't blame BootSkin for the problem, it works fine now. Just a bit of a pain to have to go through this to get it to work.

This solution may not solve everyones problem either.

GOOD LUCK!!

Okay now I get to eat my hat with no mustard.

Went to reboot and voila... another BSOD. This must be something to do with DEP in XP. (what I am using +SP3)  I rebooted the first time without a hitch. Now I get another BSOD... uninstalled/.

:?

EDIT: If this many are having this many problems.... it should be removed from the site. Will test the DEP theory and report here.

EDIT2: Well well well.... DEP only allows .exe's to be added to the exception lists.... a new problem. I'll try the BootSkin.exe added to DEP but... the vidstub.sys is located in the system32/drivers directory.... hmmmm

will see.

EDIT3: OKAY!!... i'm in the ballpark!! With DEP set to "Turn on DEP for all programs and services except those I select:" Then added BootSkin.exe to exceptions... all is well WITH my BIOS set to security disabled on the MBR with 3 restarts in-a-row. Now I'll try with "Virus Protection" on. (more to come).......

EDIT4: Okay i'm all done here, my next reboot without MBR security on crashed to BSOD. I'm done... even with DEP allowing BootSkin.exe, did not help... UNINSTALLING and writing this one off.

GOOD LUCK!!

Sorry to hear it didn't work out for you. Many users have reported that since SP3 Bootskin is having troubles.