Crc error system halted

Uncompessing Linux crc error System Halted Лиди из за чего это может быть и как это исправить? Re: Uncompessing Linux crc error System Halted Ошибка при проверке контрольной суммы архива (скорее всего bz2). Что делать: восстановить файл сжатого образа ядра на диске (или пересобрать и ядро). Re: Re: Uncompessing Linux crc error System Halted […]

Содержание

  1. Uncompessing Linux crc error System Halted
  2. Re: Uncompessing Linux crc error System Halted
  3. Re: Re: Uncompessing Linux crc error System Halted
  4. Re: Uncompessing Linux crc error System Halted
  5. Re: Re: Uncompessing Linux crc error System Halted
  6. Re: Uncompessing Linux crc error System Halted
  7. Re: Uncompessing Linux crc error System Halted
  8. *Sigh* «CRC error — System Halted»
  9. sprite
  10. Dante_Jose_Cuervo
  11. sprite
  12. Dante_Jose_Cuervo
  13. evongugg
  14. WizardOZ

Uncompessing Linux crc error System Halted

Лиди из за чего это может быть и как это исправить?

Re: Uncompessing Linux crc error System Halted

Ошибка при проверке контрольной суммы архива (скорее всего bz2).

Что делать: восстановить файл сжатого образа ядра на диске (или пересобрать и ядро).

Re: Re: Uncompessing Linux crc error System Halted

Я пересобирал ядро несколько раз но ниче не пашет. Как востановить?

Re: Uncompessing Linux crc error System Halted

Что за дистрибутив? Что за ядро?

Модель и возраст харда, положение раздела / (или /boot).

Re: Re: Uncompessing Linux crc error System Halted

Дистрибутива нет. Это lfs. Ядро 2.4.20. Хард сиагейт. Раздел если смотреть из редхада то /mnt/S (/dev/hda6). Кстати если грузиться с дискеты где ядро 2.4.7-10 (дискета от редхада) то все запускается правда нет ни звука не поддержки vfat. Что делать я его столько собирал 🙁

Re: Uncompessing Linux crc error System Halted

>Что делать я его столько собирал 🙁

У меня такое дурное предположение, что это за-за ошибок либо в компилляторе, либо в архиваторе.

Каким компиллятором собираешь и каким рекомендовано собирать данное ядро.

Попробуй взять конфиг ядра от Красной шапочки и пересобрать ядро с ним.

Re: Uncompessing Linux crc error System Halted

Может быть диск сыпится, а ядро ставится на дырявую облясть — поробуй прочекать винт а конфиг ядра не поможет — тут битый bzImage то бишь архив

Источник

*Sigh* «CRC error — System Halted»

sprite

Distinguished

Windows fails to boot and every so oftehn i get this message appearing:

«CRC error — System Halted»

Anyone know what it means ?

Started happening after I took out my PSU and graphics card for a short while (say a day) then replaced them, tried to boot up and got that error message.

Specs as follows:

AMD 3500
Epox EP9NPAJ SLi
1GB Kingston Hyper X
X800XT
160GB HDD

System has been fine for nearly a year now so no idea whats caused this. I’ve run Memtest86 about 3 times in the last month and both RAM modules have passed 2 hours of testing.

Dante_Jose_Cuervo

Distinguished

Windows fails to boot and every so oftehn i get this message appearing:

«CRC error — System Halted»

Anyone know what it means ?

Started happening after I took out my PSU and graphics card for a short while (say a day) then replaced them, tried to boot up and got that error message.

Specs as follows:

AMD 3500
Epox EP9NPAJ SLi
1GB Kingston Hyper X
X800XT
160GB HDD

System has been fine for nearly a year now so no idea whats caused this. I’ve run Memtest86 about 3 times in the last month and both RAM modules have passed 2 hours of testing.

Hmm. that’s odd. You see, CRC means Cyclical Redundancy Check, yet I didn’t know that your RAM or mobo supported CRC. What CRC is, is a type of ECC, or Error Correction Code.

Apparently some data in your system is corrupt.

sprite

Distinguished

Oh joy, could it be a HDD error ?

I did manage to mess up a dual boot of Windows XP and Ubuntu, I had to make the partition which XP was in smaller.

Could that be it ?

Seems odd that it worked fine up till now.

Dante_Jose_Cuervo

Distinguished

Oh joy, could it be a HDD error ?

I did manage to mess up a dual boot of Windows XP and Ubuntu, I had to make the partition which XP was in smaller.

Could that be it ?

Seems odd that it worked fine up till now.

evongugg

Splendid

WizardOZ

Distinguished

Windows fails to boot and every so oftehn i get this message appearing:

«CRC error — System Halted»

Anyone know what it means ?

Started happening after I took out my PSU and graphics card for a short while (say a day) then replaced them, tried to boot up and got that error message.

Specs as follows:

AMD 3500
Epox EP9NPAJ SLi
1GB Kingston Hyper X
X800XT
160GB HDD

System has been fine for nearly a year now so no idea whats caused this. I’ve run Memtest86 about 3 times in the last month and both RAM modules have passed 2 hours of testing.

Appologies for length of post, I am trying to cover all bases here.

Assuming that the following interpretation of what you say you did is correct, I will make the following comments — see below.

As I understand it, you physically removed both your power supply and graphics card from your system and then, after a day or so, physically re-installed the SAME PSU and graphics card in your system. After which you started getting the CRC error message each time you power up and the system fails to boot. My suggestions are based on this interpretation of what you say you did — if this is incorrect and / or incomplete, then you will need to clarify, so that any advice or suggestions made are appropriate.

Anyways, here we go. In the interests of completeness, I will give short derfinitions / explanations as I believe are appropriate. This in no way means that I assume you don’t know what I am talking about, I am just covering all bases.

First: CRC stands for Cyclic Redundancy Check. This is a data transmission integrity check that is commonly used to determine if transmitted data has been corrupted. It is a useful tool, but it can be bypassed. CRC verifications are used in BIOS during booting, during data transmission over phone lines and during file reads from assorted media, including hard disks and CD/DVD-ROMS. It can also be used to verify RAM integrity. If you get a CRC error message it normally indicates that the data was corrupted to begin with, or the data was trashed during transmission. The second condition can occur as a consequence of either original data being NFG OR a problem during communication — which means problems with either the transmisssion process or the wiring. Most frequent case is faulty wiring / cables or connections.

Since you have run Memtest successfully, this indicates that both your BIOS and RAM are OK, as is either your floppy drive or optical drive. It wouldn’t run successfully otherwise. This is good, as it reduces the trouble-shooting targets significantly. It also indicates that your MoBo has not been damaged.

Which leaves three items to look at.

Item one is the hard drive itself.

Item two is your video card driver files.

Item three is your OS installation.

Problems with all three can lead to CRC errors.

Lets start with a few questions.

1) were you able to remove the PSU without having to dis-assemble your system? Some case / MoBo configurations make it mandatory to physically remove most of the guts of a system to remove the PSU. You didn’t perchance force things when you removed the PSU, did you?

2) If you were able to remove the PSU without dis-assembling your system, and without forcing things, I assume you took appropriate precautions to prevent static electricity damage. I am also assuming that you disconnected all power connections in as gentle a manner as possible — sometimes they get sticky and unco-operative.

3) When you were re-installing components, I assume that static discharge precutions were taken AND that you didn’t overflex the MoBo and any other connections weren’t disturbed, and that you ensured that all cables and connectors were properly seated. This is an accurate assumptin isn’t it?

Assuming that you were able to remove the PSU without dis-assembling the system, that all appropriate static discharge precautions were taken, and that all connections check out you are left with very few checks.

Before doing anything else, check the following:

1) all cables to all drives remain properly connected.

2) your video card is fully and properly seated in its slot, and is stable.

3) every other component is correctly seated and connected.

Most likely is that the video drivers have somehow been corrupted. Try re-booting in «safe mode» and un-installing and then re-installing the video drivers. Very important: If you have the original CD for your video card, start with these drivers, as they are essentially guaranteed to work. Install any updates and patches you may have downloded after you are able to boot successfully using original drivers.

If this doesn’t work, try booting in safe mode and verifying that the OS is not corrupted. It may be necessary to re-install and patch the OS. If this is the case, you may get lucky and not need to re-install your apps. And most drivers, but you should seriously consider re-installing the video drivers.

If this doesn’t work, it may be necessary to reformat and re-install from scratch. Before you do this, you should verify that the drive is working OK. You should also back up any data files you need. I am assuming that you are applying the «one big drive» approach here. If you aren’t, and have partitioned your drive(s) into seperate partitons, you won’t necessarily need to back up your data, but it is still a good idea to do so.

You may want to consider pulling your HD out of your system and connecting it to a buddy’s system that has something like Norton Utilities installed and doing some checks and repairs on it. And then backing up data.

You may want to consider running a very low-level check of your HD — Partition Magic comes to mind here and correcting any errors found.

Источник

Содержание

  1. Uncompessing Linux crc error System Halted
  2. Re: Uncompessing Linux crc error System Halted
  3. Re: Re: Uncompessing Linux crc error System Halted
  4. Re: Uncompessing Linux crc error System Halted
  5. Re: Re: Uncompessing Linux crc error System Halted
  6. Re: Uncompessing Linux crc error System Halted
  7. Re: Uncompessing Linux crc error System Halted
  8. Re: Uncompessing Linux crc error System Halted
  9. Arch Linux
  10. #1 2007-08-21 22:12:10
  11. I can’t boot «crc error» [Solved]
  12. #2 2007-08-21 22:19:36
  13. Re: I can’t boot «crc error» [Solved]
  14. #3 2007-08-21 22:34:02
  15. Re: I can’t boot «crc error» [Solved]
  16. #4 2007-08-21 22:38:41
  17. Re: I can’t boot «crc error» [Solved]
  18. #5 2007-08-21 22:57:55
  19. Re: I can’t boot «crc error» [Solved]
  20. #6 2007-08-21 22:57:59
  21. Re: I can’t boot «crc error» [Solved]
  22. #7 2007-08-21 23:13:13
  23. Re: I can’t boot «crc error» [Solved]
  24. #8 2007-08-21 23:15:58
  25. Re: I can’t boot «crc error» [Solved]
  26. #9 2007-08-21 23:32:44
  27. Re: I can’t boot «crc error» [Solved]
  28. #10 2007-08-22 00:53:00
  29. Re: I can’t boot «crc error» [Solved]
  30. #11 2007-08-22 07:40:09
  31. Re: I can’t boot «crc error» [Solved]
  32. #12 2007-08-22 09:18:43
  33. Re: I can’t boot «crc error» [Solved]
  34. Thread: Uncompression Error. System Halted
  35. Uncompression Error. System Halted
  36. Re: Uncompression Error. System Halted
  37. Re: Uncompression Error. System Halted
  38. Re: Uncompression Error. System Halted
  39. Re: Uncompression Error. System Halted
  40. Re: Uncompression Error. System Halted
  41. Re: Uncompression Error. System Halted
  42. Установка linux mint
  43. Установка linux mint

Uncompessing Linux crc error System Halted

Лиди из за чего это может быть и как это исправить?

Re: Uncompessing Linux crc error System Halted

Ошибка при проверке контрольной суммы архива (скорее всего bz2).

Что делать: восстановить файл сжатого образа ядра на диске (или пересобрать и ядро).

Re: Re: Uncompessing Linux crc error System Halted

Я пересобирал ядро несколько раз но ниче не пашет. Как востановить?

Re: Uncompessing Linux crc error System Halted

Что за дистрибутив? Что за ядро?

Модель и возраст харда, положение раздела / (или /boot).

Re: Re: Uncompessing Linux crc error System Halted

Дистрибутива нет. Это lfs. Ядро 2.4.20. Хард сиагейт. Раздел если смотреть из редхада то /mnt/S (/dev/hda6). Кстати если грузиться с дискеты где ядро 2.4.7-10 (дискета от редхада) то все запускается правда нет ни звука не поддержки vfat. Что делать я его столько собирал 🙁

Re: Uncompessing Linux crc error System Halted

>Что делать я его столько собирал 🙁

У меня такое дурное предположение, что это за-за ошибок либо в компилляторе, либо в архиваторе.

Каким компиллятором собираешь и каким рекомендовано собирать данное ядро.

Попробуй взять конфиг ядра от Красной шапочки и пересобрать ядро с ним.

Re: Uncompessing Linux crc error System Halted

Может быть диск сыпится, а ядро ставится на дырявую облясть — поробуй прочекать винт а конфиг ядра не поможет — тут битый bzImage то бишь архив

Re: Uncompessing Linux crc error System Halted

Источник

Arch Linux

You are not logged in.

#1 2007-08-21 22:12:10

I can’t boot «crc error» [Solved]

I did pacman -Syu minutes ago (around 23:40 CET) it upgraded allot stuff including kernel.
after the reboot the system won’t boot the new kernel including the fallback.

How do i fix this please someone help.

Last edited by decaturguy (2007-08-21 22:54:41)

#2 2007-08-21 22:19:36

Re: I can’t boot «crc error» [Solved]

This issue is currently discussed on #archlinux in IRC.

One possibility to solve this problem is to chroot (or directly boot) into your system with a live cd (or your archlinux install cd) from where you can downgrade the kernel, because it’s a bug in the current i686 kernel.

brain0 is already about to fix this in a new package release.

Last edited by harlekin (2007-08-21 22:27:53)

Hail to the thief!

#3 2007-08-21 22:34:02

Re: I can’t boot «crc error» [Solved]

please someone post how to guide with archlinux install cd.

#4 2007-08-21 22:38:41

Re: I can’t boot «crc error» [Solved]

Those articles may be helpful though not up to date.
If you have troubles with them, post and I’ll post a complete how to.

You can also insert your archlinux installation cd and enter:
arch root=/dev/sda3

whereas /dev/sda3 is your / (root) partition. This will boot your root partition with the installation cd’s kernel.

Hail to the thief!

#5 2007-08-21 22:57:55

Re: I can’t boot «crc error» [Solved]

Thanks again

Solved using this guide:

I just had this problem and fixed it by.

boot with another linux CD (arch install disk will work)

Mount the partition that contains your Arch install.

enter the mounted directory and type

Pick a kernel that is older. and

pacman -U kernel26.

Fixed my system.

This sort of thing seems to happen a lot. although this is the first time in about 4 kernel updates.

#6 2007-08-21 22:57:59

Re: I can’t boot «crc error» [Solved]

Harlekin, would you recommend doing an IngnorePkg=kernel26 in pacman.conf for now, since this seems to be happening for everyone upgrading?

#7 2007-08-21 23:13:13

Re: I can’t boot «crc error» [Solved]

It seems as if only i686 systems are affected by this bug. So if you’re running x86_64 arch, you should be fine without worrying.

If you’re running i686, adding the kernel to IgnorePkg may be an option until the new kernel package is released / available for your mirror.
As brain0 already updated the kernel package, I’d simply wait with a system upgrade until your mirror is sync’ed.

Hail to the thief!

#8 2007-08-21 23:15:58

Re: I can’t boot «crc error» [Solved]

Ok.
And please give us back the Harley Quinn av. Please!

#9 2007-08-21 23:32:44

Re: I can’t boot «crc error» [Solved]

Ok.
And please give us back the Harley Quinn av. Please! 😀

But. but Nyuu is *a lot* more cute! )’:

Last edited by harlekin (2007-08-21 23:33:18)

Hail to the thief!

#10 2007-08-22 00:53:00

Re: I can’t boot «crc error» [Solved]

happened to me, too.

https://www.skatox.com/blog -> Visit my blog about (Linux, Hacking, Open Source, Web Development, Windows, Mac Os X, Internet and more. )

#11 2007-08-22 07:40:09

Re: I can’t boot «crc error» [Solved]

Thanks again

Solved using this guide:

I managed to solve it with this guide as well

#12 2007-08-22 09:18:43

Re: I can’t boot «crc error» [Solved]

First post here, so my question is probably caused by not knowing the history of Arch well enough.

This thread is labeled «solved», but others are still open, so my question is:

— both kernel26-2.6.22.4-2.1 and kernel26-2.6.22.4-2 gives a «crc erro» — maybe not for all users but for quite many — so are we expecting a new updated one, or the above will stay until it will eventually be updated for other reasons?

I’ve no problem, because I had the install CD and could easily roll back to the kernel26.2.6.22.3-1. I’m not questioning anything (I’m very pleased with Arch which so far is exactly what I searched for), I’m just interested in how these matters usually work regarding Arch.

Last edited by KimTjik (2007-08-22 09:19:24)

Источник

Thread: Uncompression Error. System Halted

Thread Tools
Display

Uncompression Error. System Halted

Hi all. I have installed PuppyLinux & Ubuntu on laptops. I am now trying xubuntu on my oldest laptop, a Toshiba Satellite S1800-700. but am have trouble running from the DVD image. I get the GRUB menu and when I choose a a linux option I then get ‘Uncompression Error. System Halted’ and then have to turn off. The laptop is running 256 RAM & has winMe installed. I have checked other Linux live CD/DVDs that I used in other laptops & I get same error. can anyone help.

Re: Uncompression Error. System Halted

I’d say that’s probably because you don’t have enough RAM to run the live environment.

The system requirements for 12.04 recommend at least 512MB of RAM, and if I remember right at least 384MB is required to sue the live-CD. You might have better luck using Lubuntu, or doing the install with the Alternate CD (or with Minimal Install CD and then adding some lightweight desktop afterwards).

Last edited by mcduck; August 21st, 2012 at 01:48 PM .

Re: Uncompression Error. System Halted

You could replicate the same effect by installing Ubuntu Minimal, then adding openbox.
I wouldn’t expect the PC to be capable of running something as heavy as firefox though. Maybe opera or even chrome.

Re: Uncompression Error. System Halted

Okay. I managed to get Lubuntu to install using the Alternate Install CD. it did everything it was supposed to and completed the installation process without falling over or reporting any errors. GRUB installed fine. Problem I now have is that it hangs on boot-up with the LUBUNTU logo and the dots underneath. and goes no further. Any ideas. Or am I flogging a dead horse. Should I try an older LUBUNTU release. (I could not get Crunchbang to load at all, or WattOS). Is this a memory issue? Or a graphics issue that is preventing it from loading? It did run WinMe fine before I attempted this, but this has now been wiped with the Lubuntu install.

Re: Uncompression Error. System Halted

Or should I try the MiniOS install of Lubuntu or would that be a world of pain for no gain.

Re: Uncompression Error. System Halted

Sorted — running WaryPuppyLinux and the laptop runs now.

Re: Uncompression Error. System Halted

I tried to install Ubuntu with the Wubi Installer.

Rebooting, I got the «Uncompression Error. System Halted» message.

The problem was: The harddisk was adjusted to «compress to save space» as I could see in Windows Explorer. (properties of harddisk). This affected also the Ubuntu folder on the harddisk. After I unchecked «compression» for the Ubuntu folder in Windows Explorer, I could restart and landed at the «Bash promt». Then I installed Ubuntu with Wubi installer again, and it worked (because Windows did not compressed the Ubuntu folder on the harddisk).

Источник

Установка linux mint

Здравствуйте! Сейчас стоит kali linux. Я решил установить linux mint. Скачал iso образ linux mint kde 64-bit с официального сайта, записал его на флешку. Загрузил ноут с флешки, появилось меню установки пингвина, выбираю «start linux mint», а он выводит: uncompression error. system halted. Пробовал гуглить, пишут проблема с жестким диском, либо с флешкой. Ну с HDD точно нет проблем, так как я пишу это сообщение с kali linux. С флешкой тоже. Помогите, пожалуйста, кто чем сможет. Заранее спасибо.

Сейчас стоит kali linux.
я пишу это сообщение с kali linux

О, еще один. Хоть ты может расскажешь, зачем они вам?

По сабжу — образ проверь по хэшу.

кало-линупс! Ты чего хочешь-то?

Просто, когда у меня была убунта или дебиан, я никак не мог поставить metasploit. Либо я ставил, но он работал криво. А тут он изначально установлен, и работает без багов

Я только что попробовал запустить на другом ПК, выдает ту же ошибку=>проблема либо в образе, либо во флешке?

проблема либо в образе, либо во флешке

Именно. Там в главном меню где-то есть пункт «Проверить диск», поюзай его.

убунта или дебиан, я никак не мог поставить metasploit

Минт — кривая убунта.

поставь OpenSUSE на флешку! И проверь! На офсайте суси есть много образов и прог для записи флешки!

А он ещё существует? Вроде была новость о сворачивании kde сборок минта.

Я устанавливаю Linux с СDR (DVDR) дисков. При записи дисков в K3b обязательно делаю проверку свежезаписанных дисков.

Источник

Установка linux mint

Здравствуйте! Сейчас стоит kali linux. Я решил установить linux mint. Скачал iso образ linux mint kde 64-bit с официального сайта, записал его на флешку. Загрузил ноут с флешки, появилось меню установки пингвина, выбираю «start linux mint», а он выводит: uncompression error. system halted. Пробовал гуглить, пишут проблема с жестким диском, либо с флешкой. Ну с HDD точно нет проблем, так как я пишу это сообщение с kali linux. С флешкой тоже. Помогите, пожалуйста, кто чем сможет. Заранее спасибо.

Сейчас стоит kali linux.
я пишу это сообщение с kali linux

О, еще один. Хоть ты может расскажешь, зачем они вам?

По сабжу — образ проверь по хэшу.

кало-линупс! Ты чего хочешь-то?

Просто, когда у меня была убунта или дебиан, я никак не мог поставить metasploit. Либо я ставил, но он работал криво. А тут он изначально установлен, и работает без багов

Я только что попробовал запустить на другом ПК, выдает ту же ошибку=>проблема либо в образе, либо во флешке?

проблема либо в образе, либо во флешке

Именно. Там в главном меню где-то есть пункт «Проверить диск», поюзай его.

убунта или дебиан, я никак не мог поставить metasploit

Минт — кривая убунта.

поставь OpenSUSE на флешку! И проверь! На офсайте суси есть много образов и прог для записи флешки!

А он ещё существует? Вроде была новость о сворачивании kde сборок минта.

Я устанавливаю Linux с СDR (DVDR) дисков. При записи дисков в K3b обязательно делаю проверку свежезаписанных дисков.

Источник

View previous topic :: View next topic  
Author Message
McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Mon Jun 17, 2002 8:47 pm    Post subject: crc error — SYSTEM HALTED Reply with quote

Sup everybody. I’ve been getting this error ever since I got my new computer (dually AMD MP system on a Tyan Tiger MPX board). Does ANYBODY have any idea how to fix it or what is causing it? Basically, it happens about 50% of the time right after the kernel gets loaded, and the system immediately halts. The other 50% of the time I boot into Gentoo and everything works 100% fine (great job on the audigy drivers, btw).

I’ve been researching this on LNO for a while, but have come up with no answers yet. At first I thought it was a hardware issue, but my drives are all fine, I checked and tested them thoroughly. I also thought it was a cable issue (switched them out to normal ATA66/100 cables), and it still didn’t fix it. I’ve also played around with the kernel about a million times, and searched Google extensively but found nothing (except possibly hardware issues, which I don’t believe is so).

So basically… have any of you guys experienced this problem? I am thinking it is either a motherboard BIOS issue (I am waiting for the new BIOS to come out, it’s still in beta-stage), or a kernel driver issue with the motherboard chipset or with the Promise ATA133 controller (I tried installing it 2x, once as onboard IDE and once on the Promise ATA133 card, same thing with both installs). Please help, as it is rather annoying to only be able to boot into Linux 50% of the time (as opposed to windows’ 99% [heh, notice it’s not 100%…] ), and I could really use some Gentoo-specific help here from y’all Gentoo-experts :D.

One last thing, I have tried it with both vanilla and gentoo-source kernels.
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Mon Jun 17, 2002 8:50 pm    Post subject: Reply with quote

If you’re getting a CRC error on boot from the kernel — and it’s sporadic == it is almost certainly a hardware issue. Your hard drive might be going bad, you might have a bad cable, your mobo could be having issues, a lower chunk of your RAM might be flaky, etc. If the same data comes up with two different CRCs, then something is wrong.
Back to top

View user's profile Send private message

fghellar
Bodhisattva
Bodhisattva

Joined: 10 Apr 2002
Posts: 856
Location: Porto Alegre, BR

PostPosted: Mon Jun 17, 2002 8:51 pm    Post subject: Reply with quote

Have you tried to test your memory? This is a good tool for it: http://www.teresaudio.com/memtest86/.
_________________
| www.gentoo.org | www.tldp.org | www.google.com |
Back to top

View user's profile Send private message

fghellar
Bodhisattva
Bodhisattva

Joined: 10 Apr 2002
Posts: 856
Location: Porto Alegre, BR

PostPosted: Mon Jun 17, 2002 8:55 pm    Post subject: Reply with quote

delta407 wrote:
If you’re getting a CRC error on boot from the kernel — and it’s sporadic == it is almost certainly a hardware issue.



I agree. I also had some bad experiences when I upgraded my system: http://forums.viaarena.com/messageview.cfm?catid=18&threadid=11805
_________________
| www.gentoo.org | www.tldp.org | www.google.com |

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Mon Jun 17, 2002 9:06 pm    Post subject: Reply with quote

fghellar wrote:
Have you tried to test your memory? This is a good tool for it: http://www.teresaudio.com/memtest86/.

Thank you, I will test it tonight.
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Mon Jun 17, 2002 9:07 pm    Post subject: Reply with quote

delta407 wrote:
If you’re getting a CRC error on boot from the kernel — and it’s sporadic == it is almost certainly a hardware issue. Your hard drive might be going bad, you might have a bad cable, your mobo could be having issues, a lower chunk of your RAM might be flaky, etc. If the same data comes up with two different CRCs, then something is wrong.

Hrm, what do you mean by the same data coming up with 2 different CRCs? Is there a way to check? (it doesn’t end up in any of my logs when I get the crc error)
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Mon Jun 17, 2002 9:10 pm    Post subject: Reply with quote

fghellar wrote:
delta407 wrote:
If you’re getting a CRC error on boot from the kernel — and it’s sporadic == it is almost certainly a hardware issue.



I agree. I also had some bad experiences when I upgraded my system: http://forums.viaarena.com/messageview.cfm?catid=18&threadid=11805

Hrm, I am thinking it’s a memory issue. However, I should note that windows never has any problems. Well, then again… it pauses every once in a while for the ECC, but it almost always recovers from it (even in the middle of a game)
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Mon Jun 17, 2002 9:10 pm    Post subject: Reply with quote

Your error indicated that the CRC computed from the read-from-disk data was different than the CRC that was stored in it, meaning that something didn’t compute right somehwere along the line. Plus, it changes, because it sometimes comes up correctly (matching the stored CRC). The kernel, as stored on disk, is being read or acted upon in two different ways — randomly — which just screams to me of a hardware issue. Something is running too hot/too fast/too hard/too long or is simply not working. I would say to check your hard drive, RAM, and CPU; definitely stop overclocking if you are.
Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Mon Jun 17, 2002 9:21 pm    Post subject: Reply with quote

delta407 wrote:
Your error indicated that the CRC computed from the read-from-disk data was different than the CRC that was stored in it, meaning that something didn’t compute right somehwere along the line. Plus, it changes, because it sometimes comes up correctly (matching the stored CRC). The kernel, as stored on disk, is being read or acted upon in two different ways — randomly — which just screams to me of a hardware issue. Something is running too hot/too fast/too hard/too long or is simply not working. I would say to check your hard drive, RAM, and CPU; definitely stop overclocking if you are.

I am definitely not overclocking, as it tends to break things, and I don’t really need that much more speed. I am testing the RAM tonight, and have also tested the hard drives (and cables) extensively. If the RAM turns out to be okay, the only thing left will be the CPU. How on earth would I test it? The system almost NEVER crashes, and is very stable, WHEN I actually get into linux, that is. Maybe it’s an SMP issue? No clue…
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Mon Jun 17, 2002 9:57 pm    Post subject: Reply with quote

As far as the CPU goes, you could either try each CPU separately in another computer (that doesn’t have any issues) and try stressing it (like doing sixteen concurrent kernel compiles from a RAM disk… or something). Or, (and this is less reliable,) you could try each CPU individually.

Do you have problems booting, say, the Gentoo install CD?

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Mon Jun 17, 2002 10:14 pm    Post subject: Reply with quote

delta407 wrote:
As far as the CPU goes, you could either try each CPU separately in another computer (that doesn’t have any issues) and try stressing it (like doing sixteen concurrent kernel compiles from a RAM disk… or something). Or, (and this is less reliable,) you could try each CPU individually.

Do you have problems booting, say, the Gentoo install CD?

The install CD? Never any problems. And I have done like sixteen concurrent kernel compiles (tho not from a RAM disk, so er, nevermind, hehe). I also wish I had the $$$ to test it in another system, too.

Oh, one thing I should mention. I «feel» that the system boots up more often in non-fb mode (versus me using the vga=791 line in lilo.conf) and that I get into linux more often. Though it is only a very rough generalization. It’s not like I sat there with pen & paper & counted (usually I am just very happy to be in linux, so I stay, hehe). I am using a GF4 Ti4600, so who knows, maybe it’s that nVidia & AMD incompatibility thingy.
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Mon Jun 17, 2002 11:11 pm    Post subject: Reply with quote

If you haven’t had any issues with the install CD (why not do a half dozen reboots or so just to make sure :D), then it’s most likely hard-drive related. Could be the cable, but that’s doubtful; your disk could be failing.

Try getting md5sums of your /boot directory; i.e. mount -o ro /dev/BOOT /boot; md5sum —binary `find /boot -type f` and comparing them across reboots, both from the local disk and from the CD. You should be able to see then if the hard drive is returning the data correctly.

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Mon Jun 17, 2002 11:32 pm    Post subject: Reply with quote

Oh, also, to get a number that represents your entire /boot partition over multiple passes, run the following at a bash prompt:

Code:
for ((i=1; i <= 100 ; i++)); do echo -n «Pass $i… «; mount /boot; md5sum —binary `find /boot -type f` | md5sum; umount /boot; done

It will print something like the following:

Code:
# for ((i=1; i <= 100 ; i++)); do echo -n «Pass $i… » ;mount /boot; md5sum —binary `find /boot -type f` | md5sum; umount /boot; done

Pass 1… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 2… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 3… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 4… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 5… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 6… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 7… 7588bfd7fc9a378012368ed4252f54f5  —

It’ll really thrash your hard drive about but will a) give you a nice stress test and b) give you a quick and easy visual check that your boot partition is in order. My advice would be to run it once within Gentoo and once off the install CD and compare sums. If the numbers turn up different in sequential passes, you know you have a problem.

Back to top

View user's profile Send private message

arkane
l33t
l33t

Joined: 30 Apr 2002
Posts: 918
Location: Phoenix, AZ

PostPosted: Tue Jun 18, 2002 1:09 am    Post subject: Reply with quote

delta407 wrote:
Oh, also, to get a number that represents your entire /boot partition over multiple passes, run the following at a bash prompt:

Code:
for ((i=1; i <= 100 ; i++)); do echo -n «Pass $i… «; mount /boot; md5sum —binary `find /boot -type f` | md5sum; umount /boot; done

It will print something like the following:

Code:
# for ((i=1; i <= 100 ; i++)); do echo -n «Pass $i… » ;mount /boot; md5sum —binary `find /boot -type f` | md5sum; umount /boot; done

Pass 1… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 2… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 3… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 4… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 5… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 6… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 7… 7588bfd7fc9a378012368ed4252f54f5  —

It’ll really thrash your hard drive about but will a) give you a nice stress test and b) give you a quick and easy visual check that your boot partition is in order. My advice would be to run it once within Gentoo and once off the install CD and compare sums. If the numbers turn up different in sequential passes, you know you have a problem.

That’s a cool little test, you should put that into the tips and tricks section.

I just ran it on my drive to make sure, and it definately works.



Dan

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Tue Jun 18, 2002 1:15 am    Post subject: Reply with quote

arkane wrote:
That’s a cool little test, you should put that into the tips and tricks section.

I just ran it on my drive to make sure, and it definately works.

Well, that’s actually the hard way. It checks each of the individual files separately, and tends to stress things more (which is probably what we want in this case). You can md5 the whole partition like this:

Code:
dd if=/dev/hda1 2>/dev/null | md5sum

But, that’s just one sequential read of the whole partition (which is less error-prone, but we want to find errors), so if it’s got a lot of free space you’ll run into problems.

Also, make sure it’s unmounted, or bad things might happen…

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Tue Jun 18, 2002 5:14 am    Post subject: Reply with quote

delta407 wrote:
If you haven’t had any issues with the install CD (why not do a half dozen reboots or so just to make sure :D), then it’s most likely hard-drive related. Could be the cable, but that’s doubtful; your disk could be failing.

Try getting md5sums of your /boot directory; i.e. mount -o ro /dev/BOOT /boot; md5sum —binary `find /boot -type f` and comparing them across reboots, both from the local disk and from the CD. You should be able to see then if the hard drive is returning the data correctly.

Okay.. I will try your «little» test :) But one quick question. Why is it that if I can boot the install CD’s kernel fine but not my own, then it’s a HD issue? Why wouldn’t that be a «misconfigured» kernel issue?
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Tue Jun 18, 2002 5:16 am    Post subject: Reply with quote

If it was misconfigured, it would either work 100% of the time or fail 100% of the time. Sometimes working and sometimes not, without changing the input data, is a very good sign of a hardware issue.
Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Tue Jun 18, 2002 5:30 am    Post subject: Reply with quote

delta407 wrote:
Oh, also, to get a number that represents your entire /boot partition over multiple passes, run the following at a bash prompt:

Code:
for ((i=1; i <= 100 ; i++)); do echo -n «Pass $i… «; mount /boot; md5sum —binary `find /boot -type f` | md5sum; umount /boot; done

It will print something like the following:

Code:
# for ((i=1; i <= 100 ; i++)); do echo -n «Pass $i… » ;mount /boot; md5sum —binary `find /boot -type f` | md5sum; umount /boot; done

Pass 1… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 2… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 3… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 4… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 5… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 6… 7588bfd7fc9a378012368ed4252f54f5  —

Pass 7… 7588bfd7fc9a378012368ed4252f54f5  —

It’ll really thrash your hard drive about but will a) give you a nice stress test and b) give you a quick and easy visual check that your boot partition is in order. My advice would be to run it once within Gentoo and once off the install CD and compare sums. If the numbers turn up different in sequential passes, you know you have a problem.

ahhh….. that’s NOT an apostrophe.. it’s the thing next to the 1… :)

btw, I get different results with the for-loop (for blah blah blah) than with the:

dd if=/dev/hde1 2> /dev/null | md5sum

but.. both are consistent across the board with themselves. It seems like, tho, that everytime I do it I get different results… weird
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Tue Jun 18, 2002 5:35 am    Post subject: Reply with quote

The find-related loop should be different than the dd | md5sum.

Quote:
It seems like, tho, that everytime I do it I get different results… weird

You mean that the command loops are internally consistent (i.e. between passes) but not consistent between runs (i.e. rebooting or whatever and running the loop again)?

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Tue Jun 18, 2002 5:45 am    Post subject: Reply with quote

Well, I’m going to bed, but here: trust the big long for loop thing, because if you md5 the whole partition, you’ll also sum the journal and mount count and whatnot which can and probably will change when you run the big loop.

So, if the big loop at any time ever produces a different number — across passes, retries, or reboots — then something is definitely wrong, and it’s likely your hard drive. You should get the same number booted from Gentoo as you would booted from the rescue disk, as long as the partition is always mounted read-only.

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Tue Jun 18, 2002 5:48 am    Post subject: Reply with quote

delta407 wrote:
The find-related loop should be different than the dd | md5sum.

Quote:
It seems like, tho, that everytime I do it I get different results… weird

You mean that the command loops are internally consistent (i.e. between passes) but not consistent between runs (i.e. rebooting or whatever and running the loop again)?

Wow, it’s great being able to get help @ 1 am :)

What I mean, is that, when I ran the dd if= and then the big for -loop, and then I ran the dd if= again, I would get diff. results for the dd if= test. For loop test always stayed the same, though.

I am running memtest86 right now, seeing if I can find something wrong with my RAM. Overall, I bet it’s just some archaic incompatability with my mobo’s BIOS and the kernel.
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Tue Jun 18, 2002 5:55 am    Post subject: Reply with quote

delta407 wrote:
Well, I’m going to bed, but here: trust the big long for loop thing, because if you md5 the whole partition, you’ll also sum the journal and mount count and whatnot which can and probably will change when you run the big loop.

So, if the big loop at any time ever produces a different number — across passes, retries, or reboots — then something is definitely wrong, and it’s likely your hard drive. You should get the same number booted from Gentoo as you would booted from the rescue disk, as long as the partition is always mounted read-only.

Yeah, I’m going to bed too. Thanks a lot for the help.

Thanks for clearing up the diff. between the two tests. Tomorrow evening I will test out the md5 for loop test whilst booting off of the install CD. I think the HD & cables are fine, tho.

BTW, how are you supposed to mount /boot? I am using defaults 1 1, or should it be defaults 1 2 or defaults 0 0 ?? Prolly doesn’t even make a difference, oh well. I bet it’s that weird AMD incompatibility thing with NVidia cards or something like that, ‘cuz I dont’ get crc errors as OFTEN when I’m not using fb. (because the only way I can tell it’s a crc error is when I’m not in fb mode, ‘cuz when I am all I get is a blank screen)
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

delta407
Bodhisattva
Bodhisattva

Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL

PostPosted: Tue Jun 18, 2002 6:02 am    Post subject: Reply with quote

I have /boot set to noauto (don’t mount on boot) and 1 1.

As far as framebuffer support goes, if the kernel is giving you CRC errors, that (AFAIK) happens before pretty much anything else, including initializing framebuffer stuff.

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Tue Jun 18, 2002 4:49 pm    Post subject: Reply with quote

delta407 wrote:
I have /boot set to noauto (don’t mount on boot) and 1 1.

As far as framebuffer support goes, if the kernel is giving you CRC errors, that (AFAIK) happens before pretty much anything else, including initializing framebuffer stuff.

er, well, I meant that I can’t see what kind of error it is when I use framebuffer mode because it never pops up. Screen changes for fb mode, but nothing comes on the screen :) I only found out (a week ago?) that they were crc errors after I turned off fb mode.

Update: I ran memtest86 just fine last night when I went to bed, but that was with ECC off. After I turned it on, I started getting a few ECC errors (which were corrected, according to the test). But get this.. this is an excerpt from Crucial about my motherboard:

«The Tiger MPX supports non-registered DDR SDRAM in the first 2 memory sockets only (DIMM1 and DIMM2, as labeled on the motherboard). Registered DIMMs are supported in all sockets. »

So…. maybe it just doesn’t like that configuration. I will try memtest86 on a different DIMM slot tonight and see how things work. But either way, either the mobo has some BIOS issues/quirks or I need new RAM (and I think there is where my troubles lie) :)
_________________
McManus

—-

Linux user #267375 — http://counter.li.org

Back to top

View user's profile Send private message

McManus
Apprentice
Apprentice

Joined: 10 Apr 2002
Posts: 176
Location: Austin, TX

PostPosted: Wed Jun 19, 2002 4:04 am    Post subject: Reply with quote

okay, I really think my memory is bad. When I run memtest86 I get errors at failing address 00000000000 (I guess the very first location). *sigh* I have bought new RAM, and am going to get the old one RMA’d
_________________
McManus

—-

Linux user #267375 — http://counter.li.org
Back to top

View user's profile Send private message

Display posts from previous:   

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Official Flavours Support
  • Hardware
  • [ubuntu] System hang at —> CRC Error — System Halted

  1. [SOLVED] System hang at —> CRC Error — System Halted

    Hello

    I was using Kubuntu Desktop 8.10 doing Remote Desktop viewing my Ubuntu Server 8.10 (with Ubuntu Desktop GUI), right after i closed the connection at Kubuntu, the ubuntu pop up a message «blah blah Crashed», and i ended up hard reset the system. After this, system hangs at » CRC Error — System Halted» everytime when i try to boot into desktop.

    At first i thought it was desktop corrupted, so i pressed «ESC» the Grub there and select «Recovery Mode», but the system still hangs at «CRC Error». So i was thinking it was the time to reinstall and when i tried to run «Kubuntu Desktop 8.10 without installing» option at system boot up, suprisingly it is still «CRC Error — System Halted».

    What’s wrong with it?? What should i do? Is it possible fix it without reinstall the system, because i have configured it as a Web server and FTP server, and this took me for 2 weeks for figured out how to configure them.

    Best regards,
    Grey08

    Last edited by Grey08; March 29th, 2009 at 12:06 PM.


  2. Ok, I have solved the problem.

    After Googled with CRC Error, i learned that, It is not only Hard disk would cause this problem, the other possibilities are:
    1.Overheating problem
    2.BAD RAM
    3.HDD cable is losen (slightly losen would cause that too)
    4.BAD HDD
    5.Improper shutdown

    I have run memtest86 and it has nothing error, and when i opened my case i found that my RAM wasn’t plugged in tight, so i guess this is the problem.


  3. Re: System hang at —> CRC Error — System Halted


  4. Re: System hang at —> CRC Error — System Halted

    Quote Originally Posted by Grey08
    View Post

    Ok, I have solved the problem.

    After Googled with CRC Error, i learned that, It is not only Hard disk would cause this problem, the other possibilities are:
    1.Overheating problem
    2.BAD RAM
    3.HDD cable is losen (slightly losen would cause that too)
    4.BAD HDD
    5.Improper shutdown

    I have run memtest86 and it has nothing error, and when i opened my case i found that my RAM wasn’t plugged in tight, so i guess this is the problem.

    from experience i can tell you that the hdd is much more probable than the ram
    to check the ram you can use memtest from just every linux livecd, i would recommend to let it make at least two passes…
    for the hdd side, you could take a look on the manufacture’s web site and see if there are any check tools listed there
    hope this helps…


Bookmarks

Bookmarks


Posting Permissions

  • Печать

Страницы: [1]   Вниз

Тема: Ran out of input data.  (Прочитано 928 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
Viglim

При загрузке компа сразу после Starting up… появляется
 ran out of input data
— System halted
При загрузке в рековери мод или с ливцд тоже самое. При загрузке с виндовых ливцд комп просто ребутится.
Что это может быть, или это проблемы с железом?


Gr33nGroove

У девушки на компе с линухом было тоже самое. Ребут — и всё ок.
В вашем случае…. Попробуйте выткнуть-воткнуть все кабели в компе.


Оффлайн
Viglim

Пробовал, не помогает. Ни ребут, не перевтыкание.


Оффлайн
sciko

При загрузке компа сразу после Starting up… появляется
 ran out of input data
— System halted

Это ядро не сумело загрузиться.

Что это может быть, или это проблемы с железом?

Может быть. Озвучь его.


rapidsp

Ни один лайвцд не грузицца??? с дискеты… с флешки…
Однозначно железо…
Если несколько планок память — откинуть поочереди…
Если есть некритичные PCI платы, cdrom, hdd — откидывать поочереди…
Попробовать обнулить BIOS.


Оффлайн
Viglim

Мать Gygabite GA-7VR
Проц AMD Athlon XP 1300+ что ещё надо? 
Сейчас перезагрузил, он начал грузится, и написал кучу буквоцифр. В конце- kernel panic — not syncing: Attemped to kill the idle task!


Пользователь решил продолжить мысль 13 Октября 2009, 15:02:47:


Начал пробовать втыкать-вытыкать. После вытыка одной из плашек, так же, при загргрузке говорит
crc error
— System halted

« Последнее редактирование: 13 Октября 2009, 15:02:47 от Viglim »


Gr33nGroove

Попробуй вытащить винт и загрузиться с LiveCD


Оффлайн
Xepec

Да вообще все вытащи, оставь одну планку памяти (которую потом, если не получится можно менять на другие, или в другие гнезда втыкать), сидюк  и видео, если оно не на борту. Остильное все вытаскиваешь (ide, pci и.т.д.).   И грузись с лайва.


Оффлайн
Viglim

Так и сделал, но ни с чего серьёзного загрузится не получилось, либо kernel panic либо crc error либо I/O error лйбо ребут либо молчаливое зависание. Один раз загрузился с досовой дискетки… Может с процом пр облемы, как это можно проверить?


rapidsp

Может с процом пр облемы, как это можно проверить?

Менять проц … как еще.


  • Печать

Страницы: [1]   Вверх



Apr 9, 2004



315



0



18,780

0


  • #1

Windows fails to boot and every so oftehn i get this message appearing:

«CRC error — System Halted»

Anyone know what it means ?

Started happening after I took out my PSU and graphics card for a short while (say a day) then replaced them, tried to boot up and got that error message.

Specs as follows:

AMD 3500
Epox EP9NPAJ SLi
1GB Kingston Hyper X
X800XT
160GB HDD

System has been fine for nearly a year now so no idea whats caused this. I’ve run Memtest86 about 3 times in the last month and both RAM modules have passed 2 hours of testing.

Dante_Jose_Cuervo



May 9, 2006



867



0



18,990

2


  • #2

Windows fails to boot and every so oftehn i get this message appearing:

«CRC error — System Halted»

Anyone know what it means ?

Started happening after I took out my PSU and graphics card for a short while (say a day) then replaced them, tried to boot up and got that error message.

Specs as follows:

AMD 3500
Epox EP9NPAJ SLi
1GB Kingston Hyper X
X800XT
160GB HDD

System has been fine for nearly a year now so no idea whats caused this. I’ve run Memtest86 about 3 times in the last month and both RAM modules have passed 2 hours of testing.

Hmm…. that’s odd. You see, CRC means Cyclical Redundancy Check, yet I didn’t know that your RAM or mobo supported CRC. What CRC is, is a type of ECC, or Error Correction Code.

Apparently some data in your system is corrupt.



Apr 9, 2004



315



0



18,780

0


  • #3

Oh joy, could it be a HDD error ?

I did manage to mess up a dual boot of Windows XP and Ubuntu, I had to make the partition which XP was in smaller.

Could that be it ?

Seems odd that it worked fine up till now.

Dante_Jose_Cuervo



May 9, 2006



867



0



18,990

2


  • #4

Oh joy, could it be a HDD error ?

I did manage to mess up a dual boot of Windows XP and Ubuntu, I had to make the partition which XP was in smaller.

Could that be it ?

Seems odd that it worked fine up till now.

Hmm… that’s odd, making that partition smaller shouldn’t have corrupted the data. Wait… how big was the XP partition and how much did you shrink it down to?

evongugg



Jul 6, 2006



8,044



3



31,165

129


  • #5

I would try clearing the Bios.
You might want to flash to the latest version also.



Sep 23, 2006



250



0



18,780

0


  • #6

Windows fails to boot and every so oftehn i get this message appearing:

«CRC error — System Halted»

Anyone know what it means ?

Started happening after I took out my PSU and graphics card for a short while (say a day) then replaced them, tried to boot up and got that error message.

Specs as follows:

AMD 3500
Epox EP9NPAJ SLi
1GB Kingston Hyper X
X800XT
160GB HDD

System has been fine for nearly a year now so no idea whats caused this. I’ve run Memtest86 about 3 times in the last month and both RAM modules have passed 2 hours of testing.

Appologies for length of post, I am trying to cover all bases here.

Assuming that the following interpretation of what you say you did is correct, I will make the following comments — see below.

As I understand it, you physically removed both your power supply and graphics card from your system and then, after a day or so, physically re-installed the SAME PSU and graphics card in your system. After which you started getting the CRC error message each time you power up and the system fails to boot. My suggestions are based on this interpretation of what you say you did — if this is incorrect and / or incomplete, then you will need to clarify, so that any advice or suggestions made are appropriate.

Anyways, here we go. In the interests of completeness, I will give short derfinitions / explanations as I believe are appropriate. This in no way means that I assume you don’t know what I am talking about, I am just covering all bases.

First: CRC stands for Cyclic Redundancy Check. This is a data transmission integrity check that is commonly used to determine if transmitted data has been corrupted. It is a useful tool, but it can be bypassed. CRC verifications are used in BIOS during booting, during data transmission over phone lines and during file reads from assorted media, including hard disks and CD/DVD-ROMS. It can also be used to verify RAM integrity. If you get a CRC error message it normally indicates that the data was corrupted to begin with, or the data was trashed during transmission. The second condition can occur as a consequence of either original data being NFG OR a problem during communication — which means problems with either the transmisssion process or the wiring. Most frequent case is faulty wiring / cables or connections.

Since you have run Memtest successfully, this indicates that both your BIOS and RAM are OK, as is either your floppy drive or optical drive. It wouldn’t run successfully otherwise. This is good, as it reduces the trouble-shooting targets significantly. It also indicates that your MoBo has not been damaged.

Which leaves three items to look at.

Item one is the hard drive itself.

Item two is your video card driver files.

Item three is your OS installation.

Problems with all three can lead to CRC errors.

Lets start with a few questions.

1) were you able to remove the PSU without having to dis-assemble your system? Some case / MoBo configurations make it mandatory to physically remove most of the guts of a system to remove the PSU. You didn’t perchance force things when you removed the PSU, did you?

2) If you were able to remove the PSU without dis-assembling your system, and without forcing things, I assume you took appropriate precautions to prevent static electricity damage. I am also assuming that you disconnected all power connections in as gentle a manner as possible — sometimes they get sticky and unco-operative.

3) When you were re-installing components, I assume that static discharge precutions were taken AND that you didn’t overflex the MoBo and any other connections weren’t disturbed, and that you ensured that all cables and connectors were properly seated. This is an accurate assumptin isn’t it?

Assuming that you were able to remove the PSU without dis-assembling the system, that all appropriate static discharge precautions were taken, and that all connections check out you are left with very few checks.

Before doing anything else, check the following:

1) all cables to all drives remain properly connected.

2) your video card is fully and properly seated in its slot, and is stable.

3) every other component is correctly seated and connected.

Most likely is that the video drivers have somehow been corrupted. Try re-booting in «safe mode» and un-installing and then re-installing the video drivers. Very important: If you have the original CD for your video card, start with these drivers, as they are essentially guaranteed to work. Install any updates and patches you may have downloded after you are able to boot successfully using original drivers.

If this doesn’t work, try booting in safe mode and verifying that the OS is not corrupted. It may be necessary to re-install and patch the OS. If this is the case, you may get lucky and not need to re-install your apps. And most drivers, but you should seriously consider re-installing the video drivers.

If this doesn’t work, it may be necessary to reformat and re-install from scratch. Before you do this, you should verify that the drive is working OK. You should also back up any data files you need. I am assuming that you are applying the «one big drive» approach here. If you aren’t, and have partitioned your drive(s) into seperate partitons, you won’t necessarily need to back up your data, but it is still a good idea to do so.

You may want to consider pulling your HD out of your system and connecting it to a buddy’s system that has something like Norton Utilities installed and doing some checks and repairs on it. And then backing up data.

You may want to consider running a very low-level check of your HD — Partition Magic comes to mind here and correcting any errors found.

Hope this helps.



Apr 9, 2004



315



0



18,780

0


  • #7

A BIOS flash seemed to fix it. :)

Thanks for all the replies.

Thread starter Similar threads Forum Replies Date

H

Question Windows 10 USB bootable boot very slow after automatic repair error Systems 2 Feb 2, 2023

D

Question Please help. Getting BSODs and crashes that don’t allow the system to POST. Systems 3 Feb 1, 2023

W

Question New Build first boot up error «New CPU Installed fTPM NV Corrupted» Systems 5 Jan 29, 2023

Pezlar

[SOLVED] Enabling XMP — GPU error 43 Systems 6 Jan 27, 2023

V

Question Beep error while PC boot Systems 2 Jan 27, 2023

Bad Harambe

Question PC boot loop ? Systems 5 Jan 24, 2023

R

Question I’m having several issues with my PC Systems 14 Jan 23, 2023

testeras

Question Pc bluescreen during Windows recovery process Systems 6 Jan 21, 2023

Varg7

Question Friend getting random PC restarts during gaming. Followed by these error messages. Systems 1 Jan 20, 2023

WhiteNoize55

Question Game/Computer freezes, then CPU usage drops to 6/7% ? Systems 0 Jan 19, 2023

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions
  • Topics

Понравилась статья? Поделить с друзьями:
  • Crc error count ssd samsung
  • Crc error cisco
  • Crc error bit
  • Crc error alarm notification
  • Createfilea failed during opening disk tsclient error 2 сбербанк