Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


computer cuts out

  • Please log in to reply
2 replies to this topic

#1 helpme1


  • Members
  • 7 posts
  • Local time:09:59 AM

Posted 01 May 2005 - 05:08 PM

hi guys every now and again my comuter goes to a blue screen and says

***hardware malfunction
call your hardware vendor for support
***this system has halted

can anybody please help me out as its doing my fruit in :thumbsup:

thanks guys :flowers:

BC AdBot (Login to Remove)


#2 Rimmer


  • Members
  • 2,159 posts
  • Location:near Sydney, Australia
  • Local time:12:59 AM

Posted 01 May 2005 - 08:11 PM

Here's some basic stuff to begin with, follow these instructions then we'll look at more specific tests:

(These instructions apply to Windows ME and XP, other versions may not have the functions described)
  • Clean your internet cache and temporary files:
    Click Start and Run then type in cleanmgr this will start the windows disk cleanup tool.
    Tick the boxes beside Temporary internet Files, Recycle Bin and Temporary Files then click OK

  • Boot in Safe Mode and do a scandisk with the 'Thorough' and 'Fix' options checked.
    If you are not sure how to boot in Safe Mode there is a tutorial here:
    Safe Mode
    How to find scandisk:
    Start>My Computer. Right click the C: drive then Properties>Tools tab, click on Check Now

  • When that's finished do a defrag.
    Start > Programs > Accessories > System Tools > Disk Defragmenter
    They will take some time but at least you will know your hard drive is working correctly and tidied up.

  • Reboot and see if there's any improvement.

  • Check how much free space you have on your hard drive.
    Start>My Computer click once on your C: drive and look in the Details box on the left.
Scandisk will have checked your hard drive which is a major hardware component, you can also download a memory checker MemTest86 from here: http://www.memtest86.com/

Create the bootable floppy and let the tests run at least overnight. If all is well that means your RAM is OK.

Get back to us with a bit more information about the hardware in your system and the results of these tests and we'll go further.

Soltek QBIC, Pentium 4 3.0GHz, 512MB RAM, 200GB SATA HDD, ATI Radeon 9600XT 256MB, Netgear 54Mb/s WAP, ridiculously expensive Satellite Broadband
Windows XP Home SP2, Trend Micro Internet Security, Firefox, Thunderbird, AdAwareSE, Spybot S&D, SpywareBlaster, A-squared Free, Ewido Security Suite.

#3 Winnipeg


  • Members
  • 33 posts
  • Local time:10:59 AM

Posted 03 May 2005 - 10:56 AM

During the Windows boot process, the computer may stop responding (hang) and the following error message may appear:
*** Hardware Malfunction
Call your hardware vendor for support
*** The system has halted ***
Windows can display only basic error messages regarding hardware malfunctions and this can make troubleshooting equipment issues difficult. Most equipment problems are centered around the motherboard, RAM on a motherboard or adapter card, or the cache memory on a motherboard or adapter card. To troubleshoot basic hardware problems, do one (or more) of the following:
Remove any extra memory modules you may have in the computer leaving only the least amount required for the computer to start and run Windows. In many cases, this will be either 16 MB or 32 MB, depending on your computer. Restart the computer to see if the error messages you received early still persist.

If the error does not reappear, the issue is isolated to one or more of the RAM modules removed from the computer. Continue to remove and replace the minimum amount of RAM required with the memory modules you removed earlier. If the error returns, you have isolated the individual memory module responsible for the problem. This process may require you to restart your computer several times to pinpoint the specific memory module that is not working correctly
Replace the defective RAM module.
Remove any adapter cards that are not required to start the computer and run Windows.

In many cases, you can start your computer with only the drive subsystem controller and video adapter card. If the error message does not appear, one of the adapter cards that you removed is the source of the problem. Reinstall each adapter separately, restarting after each card is installed, to see if the error returns. If the error does not return after reinserting all the adapter cards, it is possible that one of the adapter cards needed to be reseated. After you computer is running again, monitor the computer for an agreed upon period of time to make sure that the error does not return.
If resetting the adapters did not solve the issue, you may be required to replace the adapter that is causing the error.
Verify that you have installed the latest revisions for your computer's BIOS or firmware configuration software. Go into the bios and set load Fail safe defaults or Bios defaults, disable any antivirus protection inside the bios, and set Plug and Play OS to NO

The type of hardware your computer uses and the motherboard design determines what part of your computer's firmware can actually be updated. Various manufacturers will also provide different diagnostic tools for troubleshooting this issue.
Update the BIOS, firmware, and/or EISA configuration.

NOTE: If all three options fail to isolate or resolve the issue, the problem can be narrowed down to the motherboard, drive subsystem controller, hard drive, or the video adapter. Advanced RAID or other caching controllers can have RAM and/or processor chips that could also be the problem. If the simplest configuration contains one of these advanced adapters, additional troubleshooting or diagnostic software may be required (possibly using duplicate hardware) to resolve the problem.

Winnipeg :thumbsup:

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users