Link to home
Start Free TrialLog in
Avatar of NSSUK
NSSUKFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Restarted Server 2008 and now hangs on crcdisk.sys on boot

I done a fresh install of Server 2008 last week (on a HP Prolian ML350) and it's been running fine up until this morning when users reported the network was down.

Locally on server I could move the mouse but that was it, I had to do a hard reset. It booted up fine. I then installed one critical MS patch from automatic updates (I did not get the number) and installed the two following hotfixes: 961775 and 959816. I could not find aything in the events as to why it froze. There was an 'unknown device' in device manager, I disabled it. I then rebooted, it shut down gracefully but now it will not start up!

It gets to the scrolly bar, loading devices, In safe mode it stops at crcdisk.sys.

I have done some reseach however the majority of crcsisk.sys issues occur during the first insttallation and are caused by RAID or SATA/SCSI drivers.
Avatar of NSSUK
NSSUK
Flag of United Kingdom of Great Britain and Northern Ireland image

ASKER

I have also removed the DVD, SCSI card and backup drive to eliminate them.
ASKER CERTIFIED SOLUTION
Avatar of NSSUK
NSSUK
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of acronyms
acronyms

Thanks for letting the forum know of your fix. Had exactly the same issue and executed a rapid fix.
Thanks alos found useful
I had same error/symptom...System would boot hang on the Microsoft Green Bar i.e.:

               Microsoft
             [|||||||||||||          ]

Except that bar was empty as in no progess bars.  Tried SAFE mode next and got CCDISK.SYS as last mounted driver before hanging indefinately.  Hence found my way to this "solution".

I could not boot up to the recovery disk (setup dvd) as I got the same error symptoms in recovery mode of seperate Windows Server 2008 DVD. So after much thinking and on a hunch I disabled in the motherboard BIOS the Floppy Controller, SATA and PATA/IDE controllers and then did a reboot and I could get into the original OS fine (used Last Known Good Configuration).  Could also get into SAFE MODE too without hanging on CRCDISK.SYS.  I had seperate HDD's on ADAPTEC RAID controller though.  So doing this I basically disabled my Floppy and 2 x DVD drives (one each on PATA/IDE and SATA).
Logged in...Ran Windows Update...No Updates found...No Recent Updates...:-(
Rebooted went into BIOS and changed to enable SATA controller (one DVD is on each controller type)..System Booted fine into Windows Server 2008 (not R2 but with Hyper-V role enabled) with usable DVD.
Rebooted went into BIOS and changed to enable PATA controller (second DVD is on this controller)..System had same symptons as we started with.
Conclusion PATA controller (on Motherboard) or DVD Drive hardware has gone bad.
We dont really need the second PATA DVD so I disabled again and rebooted.  Alternatively I could replace the IDE DVD with a SATA DVD and I guess it would work.
I'm not replacing the motherboard or old DVD jdrive ust for an old tech PATA/IDE DVD drive.
Hope this helps others!


I also solved the issue.

I had this on a Delll Poweredge 2950

Turned out to be a ROM B battery on the raid controller was logging an event code to the system.
Problem was that the error logging used up all the memory on the card (100's of log entries).

Simply going in to the RAID Manager (was control+E during BIOS startup) and clearing the event log fixed the issue.

I'm assuming that while Windows was loading it was trying to write something and there was no room on the Controller's memory.

Hi NSSUK, do u know which hotfix was it? i am having the same issue
I too had this problem with a 2008 R2 Server.  Restoring the registry files resolved this issue for me.  Much information about this problem but this one hit the nail on the head.
sorry to necro post, but I had this same problem and the SSD had failed.  Recovering from a backup was my only choice.

Found this by running chckdsk and it was unable to copy logs, error 50, etc.  All the other normal things kept pointing to a failed boot drive.