crcdisk.sys causing boot delay.
- I've got a WD External Hard Drive and whenever it's plugged in Windows Vista takes at least 3 minutes to boot up, without the External Drive plugged in it takes around 35 seconds. I do not have this problem with Windows XP.
I booted up in safe mode to see which driver was causing the boot delay and it's crcdisk.sys. What can I do about this? I'd rather not unplugged my external drive every time I want to boot Windows Vista. What can I do?
Thanks
Answers
Hi Rackers,
I performed some research about this issue, and noticed that most of those problems are related to West Digital external hard drives. So I would like to suggest that you contacting West Digital support for further investigation:
Also, just for your reference, we have an update rollup for USB components, which may also be helpful and you can install it when contacting West Digital:
Cumulative update rollup for USB core components in Windows Vista
http://support.microsoft.com/?kbid=941600Hope it helps.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
All Replies
It's not the CRCDISK.SYS file that gets you stuck. The safe mode shows which file was loaded SUCESSFULLY. So it's the next file that halts the system.
Which one is it?
Duno. In my case the system wouldn't even go past CRCDISK.SYS.
- You're right, it's not crcdisk.sys, I don't know what's causing it. All I know is that my external Western Digital hard drive is causing a boot delay. When it's unplugged the boot delay doesn't occur.
Hi Rackers,
I performed some research about this issue, and noticed that most of those problems are related to West Digital external hard drives. So I would like to suggest that you contacting West Digital support for further investigation:
Also, just for your reference, we have an update rollup for USB components, which may also be helpful and you can install it when contacting West Digital:
Cumulative update rollup for USB core components in Windows Vista
http://support.microsoft.com/?kbid=941600Hope it helps.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support- Thanks, I'll be sure to try that update.
I also contacted WD on the 2/10/08, they have yet to reply to me which is sort of giving me the idea that they have no idea what is causing the issue and wont attempt to help me. I hope I'm wrong as I'd like this issue to be fixed.
Thanks again for your help/suggestions. Hi Rackers,
Thanks for your understanding.
Also I will keep an eye on this issue. If there are any related information, I will post here.
Have a nice day
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support- Hi,
Just to let you know I tried the update below:
Cumulative update rollup for USB core components in Windows Vista
It said the update did not apply to my system, I'm running Service Pack 1 RTM. I'm guessing it's already apart of the service pack? Hi Rackers,
Yes, it had been included in SP1.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community SupportGuo-Zhen Wang, I am really hoping that your expertise can help me here.
I am having a very simular issue to the one in this thread. Ever since I got a Wester Digital External Drive, and connected it via USB, my computer has been having problems with hibernation.
The hard drive only connects when Windows is on a fresh boot. Sounds a lot like the issue discussed in KB941600 that you linked to. However, this is not the least of my worries...
I no longer have the hard drive connected. (I only had it connected for 1 day) but a new problem with hibernation has started, and has happened now twice in the last month.
Both times, when I went to hibernate my computer (HP dv9550t with Vista Home Premium "Gold") my hard drive (internal, not the WD external) started to make a read/write sound in a very exact pattern. That pattern would repeat a few times, and then the hard drive would just stop, and Windows would be frozen.
Restarting Windows would then fail. The first time round a month or so back, Windows would only be started and logged in for a few moments before this would happen again, (meaing the hard drive sound and then a frozen Windows.) It eventually took me starting the computer in Windows Recovery Mode (via F8) and trying to use System Restore, but it failed. I then went back into Recovery Mode and used command prompt to run chkdsk /f restarting my computer, and letting it run. After that, Windows was still not working correctly, however System Restore (via Windows Recovery Mode) was now working, and I used an older restore point to fix Windows.
Now for the part that I hope you can help me with: Do you know what caused this? Was it the Western Digital? Was it the USB flaw that you mentioned above? Was it the Wester Digital activating the USB flaw?
Also, will update KB941600 be of any help here? I looked, and it does not appear to have been issued to my computer as an automatic update, even though my computer is up to date as of 3/9/08. Should I try installing the update?
Do you have any suggestions on how to correct what damage was done by the this... event? I am defragging now, and will run check disc again later, but I don't know if that will be enough.
Guo-Zhen Wang, PLEASE HELP.
Hi,
According to your description, I think it more like a hard drive problem but not a USB issue.
I would suggest that perform a chkdisk first. Also, there is a KB article had refered to this situation, for your reference:
A Windows Vista-based computer stops responding when you resume the computer from hibernation
http://support.microsoft.com/default.aspx?scid=kb;EN-US;928135By the way, as the new report issue you mentioned is different from the one discussed in this current thread (which is a hibernation issue), we'd recommend that you start up a new thread for it. We generally focus on one topic in one thread because in this way it will be better for other community members to participate in the discussion, and to search/find specific answers more efficiently in the future.
Hope it helps.
- Hi there,
I found this thread by searching for crcdisk.sys, which when attempting to boot safe mode, is the last file to load successfully. I do not have any external hard drive installed. The only wire connected to the laptop is the power cable.
The first reboot after installing SP1, and the machine no longer boots. In regular mode, the Vista logo appears and the green "loading" indicator flashes across the screen like normal, but the machine sits there. After 60 minutes, I finally shut it off and same issue. I shut it off after only a minute and tried safe mode. crcdisk.sys is that last file to load and then it hangs.
Hope you can help!!
Tim Hi Tim,
As the new report issue you mentioned is different from the one discussed in this current thread (which is a can not startup issue), we'd recommend that you start up a new thread for it. We generally focus on one
topic in one thread because in this way it will be better for other community members to participate in the discussion, and to search/find specific answers more efficiently in the future.
Thanks.
An interesting twist.
I recently began to experience the system locking for a few seconds to a minute and then found my SATA drive (via a PCI card) was missing in My Computer.
I rebooted but found that it hung. This was reported as CRCDISK.SYS so putting two and two together, and reading the forums, decided that my SATA drive was dead or that something new had stuffed it.
Something new?
While leaving the machine hung, I surfed the forums. My machine kicked in! Able to get on, I set bootlogging in msconfig and then I rolled back to a System Restore point previous to a Windows Update to fix a Windows Explorer crash - a Realtek driver update.
Interestingly, my SATA drive (S) popped up its AutoPlay screen while restoring!! So something has "unblocked" it.
Reboot was fine and all is well. Now, the next driver in the bootlog, ntbtlog.txt, is Tunnel.sys - which sounds very networky.
Crcdisk.sys or Redherring.sys?
Well, I wrote too soon, as my immediate reaction was to kick off a backup (which uses the very SATA drive I talk about) and Robocopy stopped with a CRC error on this drive. The machine hung completely. Event viewer shows an issue on a harddisk "DR2" and a reboot has shown that the problem is back again. 3 mins to boot.
My problem is that Windows logic tells me that Tunnel.sys has an issue, and why did my drive kick in during a rollback of a network update?
But conventional wisdom is saying that there's a clear problem with the disk/SATA controller. CRCDISK and a disk issue is a coincidence?
Is Vista just paying homage to Windows 98 with a good old fashioned conflict?
Why has this just started happening?
And why is CRCDISK the topic of the moment on the forums?
Why don't I stop writing not-very-helpful questions on Technet, solve the problem and just tell everyone the answer?
Probably because I'll end up sticking the SATA kit in my server where it'll probably work and get on with the rest of my life.
Hi LukeSkywalker,
According to your description, I think the issue may due to the hard drive is not working correctly. May be it got some corrupt blocks on it which may caused some system file corrupt. After go back to the restore point, the damaged system file comes back again but still broke after a while.
I would like to suggest that run the command: chkdsk /f to full scan the hard drive at first. And if possible, please go to your hard drive manufactor for their specific diagnostic tool and run it as a test.
Also, considering the new issue you reported is not the same as the original post. We'd recommend that open a new thread for it, then we can concentrate on your issue there.
Hope it helps.
Hi GZ,
Thanks for taking the time to reply. The thread is the same as the original in that my machine takes around 3 mins to boot and this occurs with CRCDISK as the last item logged to console during this time. And its hard disk related.
Currently, I can't chkdsk the drive as its missing in Windows. My post was to point out the apparent discrepancy between the troubleshooting logic that CRCDISK has loaded successfully (it logs this) and yet it appears to be the source of the issue. I reckon that CRCDISK does load succesfully, albeit on another thread. The main loader thread reports the success but joins a wait queue for the CRCDISK thread to return, yet the CRCDISK halts for a while. The Vista logging should be recoded to reflect this incomplete wait state.
I also write here because many people will reach this page from google or live.com (or yahoo, bless 'em) while searching for answers, whereas in your life, you see this page as merely part of many that you deal with daily.
What's a shame is that a bad block on an auxiliary (non system) drive can lead to such a failure of Windows.
Thanks, Luke
- I think you misunderstand how the reporting works. If you see that CRCDISK finished, and then you see a long delay, the delay is occuring on the file that runs directly AFTER CRCDISK, not CRCDISK its self.
As far as your disk error, why don't you boot from CD and do it that way, or plug the disc into another Windows maching and have that one run the check? The delay is not caused by Tunnel.sys, that's an unrelated driver. If you look at all the forums you'll see that HDD issues are stopping on CRCDISK, even the driver name says it all. As a software developer, I can tell you that the driver has loaded (indicated in the log) and begun its tasks which then lock up the machine.
A bad block on an auxiliary drive should not be causing the grief that it is evidentally causing for so many people. There's a bug here.
By-the-way, chkdsk, when I've been able to run it, shows nothing. I can't see a way to fix this without fitting the h/w to another machine - that's a real flaw.
Windows is locking up all over with the controller enabled and this has begun happening since the apparent bad block (logged randomly in Event Viewer).
It could be a problem with my controller driver versus Windows, but many people are reporting similar symptoms across a range of h/w configurations, which indicates that the QFE team need to get a patch out.
Luke
- Hi,
I have the exact same issue. I am using a western digital My Book Home.
I found some people here that also have this problem. I would surely like to know where the problem lies and what the solution might be.
Regards,
Mike I would like to add that this issue does not occur when booting linux (used Fedora and Ubuntu).
M.
Please refer to microsoft support article #952139
"When you restart a computer that is running Windows Vista or Windows Server 2008, and a volume on the hard disk is corrupted, a black screen is displayed, or the system stops responding"... http://support.microsoft.com/kb/952139/en-us
I am having a similar issue & I am downloading/trying out the hotfix along with the other solution they have reccomended.
My issue is this; after a clean installation & full update to SP1 of windows vista ultimate on a 120GB Internal WD IDE hard disk, I plugged in my 750GB SeaGate Internal IDE Hard Disk I use for storage, & the system will not boot, it will occasionally reach the green loading bar after which I am given a black screen without a mouse cursor that stays indefinitally (tried leaving it there for 2 days to see if it might kick in & boot but it did not).
I then proceeded to remove the 750GB IDE hard drive and boot vista on the 120GB WD drive alone, & vista boots up perfectly fine & runs beautifully. There were no hardware events in the event viewer to note.
After this, I proceeded to use a linux based "system rescue CD" (that uses the ntfs-3g driver) to boot "linux rescue cd" live from the cdrom with the cdrom set to master & the SeaGate 750GB Disk slaved to the cdrom on the same channel.
Using the linux "system rescue CD" I ran gparted (open gparted, let it find the ntfs partition, right click on it, select check & it will check for errors/repair). Then I ran ntfsfix through command prompt in linux rescue cd (open command prompt, type: "ntfsfix /dev/sda" or whatever drive mapping the rescue cd assigned to the problem drive) & this found a problem with the NTFS journal file & repaired it. Following this, again in the "system rescue CD" I ran TestDisk (the absolute, best data recovery & hard disk/MFT/MBR/NTFS/Partition repair utility without a doubt! give it a try!). Run testdisk by typing "testdisk" in the "system rescue CD" command prompt, select options--advanced/expert mode to yes, ESC to go to previous screen, Utillitys, repair MFT/MBR, ETC.
Testdisk Repaired the MFT from the Backup etc. Drive still would not boot as SLAVE in windows vista, this entire time testdisk, along with ubuntu linux, FREEBSD 7, System Rescue CD, & Windows XP were able to mount, view & read/write/execute all files on this DISK without any problem what so ever, BEFORE AND AFTER TRYING ALL OF THESE STEPS.
I will now proceed to try this hotfix, if it does not solve this issue, I plan to slave it in windows XP, copy the data over, format the drive, and remove Windows XP, along with Windows VISTA from our 1000+ Client Office Network for Ubuntu Linux Running the mock Aero Window Manager & GNOME theme w/ crossover office & cancel our support accounts along with all afilliations with MS, I doubt our employees will even notice the difference, slack faster boot times & increased system stabillity. Our building was entirely Open Source powered/ubuntu linux & PCBSD prior to switching over to Vista, this issue along with a ridiculous amount of other issues has lead our I.T Team to seriously reconsider our actions of late.
Good Luck to you all,
Gary E Maurizi Jr,
C.E.O,
Other Records, Inc.
System Rescue CD can be found at the following U.R.L: http://www.sysresccd.org/Main_Page
I am having similar problems. How do you run chkdsk /f when the computer will not boot in the first place. I can't even get it into safe mode.
- Assuming you haven't destroyed your Vista DVD or lost it, you may run chkdsk /f from the command prompt in the WindowsPE environment on the DVD.
| Windows 7 Ultimate x64 Build 7201| AMD Turion 64x2 | Dell Inspiron 1501 | Mozilla Firefox 3.5.2 |
