Windows won't start, BSoD flashes but no dump file

osholt said:

Hi, I'm in a bit of a sticky predicament.

A couple of hours ago I started up my PC and as normal it got to the bit just before the animated Windows flag appeared but this is where it all goes pear shaped.

The first red glimmer of the flag appears and then a BSoD that lasts less than a 1/4 of a second.

I booted up in Mac to find the dump file but no dice, there wasn't one.

I tried using startup repare but that did nothing and even stated that it couldn't fix the problem. I tried doing a system restore from the installation disk but apparently there are no restore points!!?!?!

The only thing I managed to extrapalate from Startup repair is that the problem has something to do with corrupt drivers.

I tried booting my PC with nothing plugged into it and still no luck same problem, I have a backup of all the files but I have to reinstate them manually from my Mac Timemachine backup so I have that as a last resort.

The only major thing I did before Windows wouldn't start was create a 5 disk RAID configuration in the Mac partition (all external USB) but I can't see how that would do anything, I didn't touch the partition Windows is on.

I have yet to try safe mode but have tried every other repair feature on the install disk.

If anyone has any expierience/ advice/ help they want to share I will most humbley appreciate it.

Oli

You are in a dificult situation. I would first try safe mode (F8) to see if it boots. If it does than it is probably a video driver. If not it might be the raid driver.

Let us know

Ken

Hello,

Do you know that it is ClassPNP.sys rather than the next file to load because often in Safe Mode the drivers loaded are listed, rather than the drivers being loaded if you see what I mean. What I am saying is that it may not be ClassPNP.sys but the next file that would appear on the list, the one you never see.

Richard

niemiro said:

Hello,

Do you know that it is ClassPNP.sys rather than the next file to load because often in Safe Mode the drivers loaded are listed, rather than the drivers being loaded if you see what I mean. What I am saying is that it may not be ClassPNP.sys but the next file that would appear on the list, the one you never see.

Richard

Good point, I will look into it.

Oli

Hello,

On Vista at least (and probably 7), the next driver to load after ClassPNP.SYS is crcdisk.sys which may fit.

Richard

niemiro said:

Hello,

On Vista at least (and probably 7), the next driver to load after ClassPNP.SYS is crcdisk.sys which may fit.

Richard

I've just replaced the crcdsik.sys file and I am about to start up Windows.

Fingers crossed.

Oli

Unfortunately it didn't work, it still stops and the BSoD comes up even after replacing the files.

Anyone got any other ideas?

Oli

Hello,

Replacing the file is not always the answer. I still think this is your best bet.

I had the crcdisk.sys boot problem and it was probably caused by Windows Update installing an older version of my IDE drivers than the ones found on my manufacturers website. I used my bootable CD of Windows XP, ran a check disk and the laptop restarted fine!! I must be one of the lucky ones. My system is a Dell Vostro 1000, 2Gb Ram, Vista Home Basic.

Although this might have worked for me, it probably wont work for many people. I've spent some time looking into this problem and so I have included 5 other solutions here that other people have used to their success, I haven't tried them yet but i hope they help someone:

1)
Goto the following folders and delete the following files
C:\windows\system32\drivers\pcmcia.sys*
C:\windows\system32\drivers\1394bus.sys
C:\windows\system32\drivers\ohci1394.sys
C:\windows\system32\driverstore\filerepository\pcmcia.infblablabla*
C:\windows\system32\driverstore\filerepository\1394.infblablabla
C:\windows\system32\driverstore\filerepository\sdbus.infblablabla*
C:\windows\inf\sdbus.inf*
C:\windows\inf\sdbus.PNF*

2)
Restart your computer and choose to edit boot options. You will see a screen which shows default windows boot options: /noexecute=optin. After optin, add /debug command and press esc. (There needs to be a space between optin and /debug.)

3)
Disable USB keyboard support in the BIOS(Only do this if you are not reliant on a USB Keyboard, otherwise you will lose the use of your USB Keyboard, either use a PS2 keyboard or have a Usb to PS2 converter Handy)

4)
Find and delete the following files
delete sptd.sys
delete sptd.sy
delete sptd.sys
delete sptd.sys

5)
Goto a command prompt and run the following commands
cd \windows
del *pcmcia*.* /s/p
del *1394*.* /s/p

Good luck to you all and many thanks to everyone who contributes help online :->

James

And read this very long thread which summarises most of the solutions: Initial Boot after intall fails on crcdisk.sys

Richard

osholt,

This seems to be a common problem and mostly resolved by reinstalling windows. However, a couple of solutions seem to have worked for some people.

1) One is to use the XP version of classpnp.sys to replace the existing classpnp.sys. You'll have to google for it or extract from a cd or from an xp installation.

2) The other is to get classpnp.sys to a USB stick from the same Windows version. Then burn Ubuntu on a DVD. Boot from the DVD. Browse to C:\windows\system32\drivers. Rename your classpnp.sys to classpnpold.sys and place the classpnp.sys on the usb stick there. Reboot.