Vista freezes on boot at crcdisk.sys


Recommended Posts

Yesterday my notebook froze and I did a forced shutdown. When I restarted it, windows froze at the startup progress bar. I attempted to start in Safemode, but it froze at crcdisk.sys.

I tried disabling my various hardware devices in the bios, and eventually came to the conclusion that the cause of the problem is my Intel 3945 wireless card. If I disable this card, windows boots properly. As soon as I enable it, windows fails to boot.

I'm thinking it is a driver issue, but I can't uninstall the driver because it doesn't appear in the Device Manger if the hardware is disabled and I can't get into windows if it is enabled. Any suggestions?

Thanks,

Adam

Link to comment
https://www.neowin.net/forum/topic/607761-vista-freezes-on-boot-at-crcdisksys/
Share on other sites

Yesterday my notebook froze and I did a forced shutdown. When I restarted it, windows froze at the startup progress bar. I attempted to start in Safemode, but it froze at crcdisk.sys.

I tried disabling my various hardware devices in the bios, and eventually came to the conclusion that the cause of the problem is my Intel 3945 wireless card. If I disable this card, windows boots properly. As soon as I enable it, windows fails to boot.

I'm thinking it is a driver issue, but I can't uninstall the driver because it doesn't appear in the Device Manger if the hardware is disabled and I can't get into windows if it is enabled. Any suggestions?

Thanks,

Adam

http://search.microsoft.com/results.aspx?m...p;q=crcdisk.sys

That happen to me, but it takes only some seconds, after that it keeps loading other files and then start.

How much did you wait?

I've waited up to an hour.

Ok, that sounds like some corruption in the File System, have you tried to choose Last Know Good Configuration?

P.S.: You can boot into Windows, run CheckDisk or in the Boot Menu choose Directory Services Restore, or something like that.

Ok, that sounds like some corruption in the File System, have you tried to choose Last Know Good Configuration?

P.S.: You can boot into Windows, run CheckDisk or in the Boot Menu choose Directory Services Restore, or something like that.

I've tried "last known good configuration" with no success. Also tried Chkdisk and SpinRite and neither found disk problems. I also tried a repair using the Windows CD, but that too found no problems.

I still believe it is a driver or hardware issue with the Intel Wireless card because disabling it resolves the problem. I just don't know how to uninstall the driver if the device is disabled.

I still believe it is a driver or hardware issue with the Intel Wireless card because disabling it resolves the problem. I just don't know how to uninstall the driver if the device is disabled.

To uninstall the driver go to Add/Remove, Start Menu Folder for the driver (if there's any) or go to device manager, now right lick on the device and select uninstall, that should be enough...

To uninstall the driver go to Add/Remove, Start Menu Folder for the driver (if there's any) or go to device manager, now right lick on the device and select uninstall, that should be enough...

Driver does not appear in Add/Remove programs.

The device also does not appear in Device manager because I have disabled it in the bios, but as I mentioned before, if I enable it in the bios, Windows won't start. And that's my catch 22 situation...

If you press F8 right after POST, there should be an option to enable boot logging. Do that, and when it hangs, reboot off a CD into another OS, UBCD for example, and find (I think) boot.txt. It should list what loaded when Windows was starting. The last entry should be the problem-causing file. If it looks like a driver file, navigate to the Windows/system32 folder and rename it (don't delete it!).

Oh, have you tried the startup repair option? If you haven't, boot from your Vista DVD (hopefully your laptop came with a plain OS DVD), and there should be an option to repair, under the "Install now" button. Click that, choose your installation folder, and the Startup Repair option will check for various problems.

Driver does not appear in Add/Remove programs.

The device also does not appear in Device manager because I have disabled it in the bios, but as I mentioned before, if I enable it in the bios, Windows won't start. And that's my catch 22 situation...

Sorry, i've only understand that you disabled it through the BIOS.

Well, you can manually delete the driver files, however you need to know what files are.

Go to: C:\WINDOWS\System32\Drivers

now look at files description (put explorer in details view and add the needed tabs), then move the files to a new folder, then go to C:\WINDOWS\Inf and search files by name, based on the name of the driver files (eg, iw.sys -- iw.inf etc)

This is something hard to explain trough messages, lol.

See if there's an update for your BIOS.

P.S.: You need that device?

Problem just started out of nowhere. I didn't install any OS updates, drives, or software.

I will try the boot logging suggestion. I did try startup repair, but it didn't find any problems.

Yes, I do need the device, because without it I can't use wireless.

I believe the problem is a hardware issue. I reformatted the hard drive, then tried to reinstall Windows. The install would not start if my wireless card was enabled. I disabled the card and was able to install Windows. But still when I enable the wireless card, windows fails to boot.

I guess I will purchase a new internal wireless card. Thanks for all your suggestions.

  • 3 weeks later...

Well I replaced the wireless card and it did not resolve the problem. The only thing I can think of now is a faulty motherboard.

But I don't want to spend a couple hundred dollars for a new board unless I'm sure it's the problem.

The system passes all the tests when I use the Dell Diagnostics CD.

Any other suggestions?

One other thing to note is that I tried to boot off an Ubuntu 7.10 LiveCD and it also froze during boot, so I'm sure it's a hardware and not OS issue.

  • 3 months later...

Im not sure if you're still having problems, but I encountered the issue today and during the boot I enabled loading non signed drivers in the F8 menu. Booted right up. This is on Vista Ultimate 64 bit edition, shouldn't matter but I did want to mention that. Hope it helps.

  • 1 year later...

I am having this same problem, my wife was right clicking icons in the task bar and shutting them off, and screen went funky, so she rebooted the system, and this happened. i dont know what to do, i cant get into windows at all, through safe mode,last known, anything, it just hangs on the progress bar, or the crc file if i try safe mode.

  • 1 month later...

I'm having this same issue on a Toshiba Satellite A305-S6872.. I've read a couple of suggestion but I need neowin's help.

It's just a brand new install of windows xp home basic 32-bit. Fully updated through automatic updates and it stopped working suddenly. THe person claims that she didn't install anything new, and from what i've read this seems to happen a lot.

things that i will try:

-re installing vista and disabling automatic updates automatically

-disabling hibernation

-update bios if needed

- install drivers from manufactures website (not automatic updates)

- just install security updates

http://social.technet.microsoft.com/forums...b-3e1811899ce6/

here they're talking about renaming or deleting some files but I don't completely understand the instructions... please help guys. :)

what do you guys think?

  • 1 month later...
Yesterday my notebook froze and I did a forced shutdown. When I restarted it, windows froze at the startup progress bar. I attempted to start in Safemode, but it froze at crcdisk.sys.

I tried disabling my various hardware devices in the bios, and eventually came to the conclusion that the cause of the problem is my Intel 3945 wireless card. If I disable this card, windows boots properly. As soon as I enable it, windows fails to boot.

I'm thinking it is a driver issue, but I can't uninstall the driver because it doesn't appear in the Device Manger if the hardware is disabled and I can't get into windows if it is enabled. Any suggestions?

Thanks,

Adam

~<Snip>~

Edited by Andrew-DB
Please do not condone piracy on this board.
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!