***Hardware malfunction***system has halted

G

Guest

My computer totally stops functioning and a gray screen appears saying:
“***Hardware malfunction*** Contact hardware vendor for support *** system
has halted ***â€
I put this computer together and had no problems until I installed XP. When
it locks it also makes whatever sound it had when it locks. Is there a way to
see what is causing the lock? I’ve tried the troubleshooting
FAQ on the software and got nowhere. When it locks it locks I’ve found no
way to continue other then killing the power to the motherboard and
restarting. There is no rhyme or reason to the lock no common timing or
software or hardware.
Thank You

Update:
After searching around found I have a Item under "other device",
PCI simple communication controller.
I have tried finding a driver for this but have no clue what it is, all my
PCI cards devices are accounted for.
I think it must be something on the motherboard
(133MHZ PIII MICRO ATX MOTHERBOARD WITH FLIP-CHIP SUPPORT)
, but have no clue what. Is
there a way to look up the hardware id that I found under the details tab in
the device properties.
I’m hoping this is the problem and not another one.
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6&REV_20
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6
PCI\VEN_13F6&DEV_0211&CC_078000
PCI\VEN_13F6&DEV_0211&CC_078000
 
A

Alan Smith

Lord Kurgun said:
My computer totally stops functioning and a gray screen appears saying:
"***Hardware malfunction*** Contact hardware vendor for support *** system
has halted ***"
I put this computer together and had no problems until I installed XP.
When
it locks it also makes whatever sound it had when it locks. Is there a way
to
see what is causing the lock? I've tried the troubleshooting
FAQ on the software and got nowhere. When it locks it locks I've found no
way to continue other then killing the power to the motherboard and
restarting. There is no rhyme or reason to the lock no common timing or
software or hardware.
Thank You

Update:
After searching around found I have a Item under "other device",
PCI simple communication controller.
I have tried finding a driver for this but have no clue what it is, all my
PCI cards devices are accounted for.
I think it must be something on the motherboard
(133MHZ PIII MICRO ATX MOTHERBOARD WITH FLIP-CHIP SUPPORT)
, but have no clue what. Is
there a way to look up the hardware id that I found under the details tab
in
the device properties.
I'm hoping this is the problem and not another one.
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6&REV_20
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6
PCI\VEN_13F6&DEV_0211&CC_078000
PCI\VEN_13F6&DEV_0211&CC_078000

And have you done what it asked? What does it say on the motherboard makers
website? Have you emailed them if you can't find help? Does their site say
it is compatible with XP? Are there drivers to download and install?
 
G

Guest

Lord Kurgun said:
My computer totally stops functioning and a gray screen appears saying:
“***Hardware malfunction*** Contact hardware vendor for support *** system
has halted ***â€
I put this computer together and had no problems until I installed XP. When
it locks it also makes whatever sound it had when it locks. Is there a way to
see what is causing the lock? I’ve tried the troubleshooting
FAQ on the software and got nowhere. When it locks it locks I’ve found no
way to continue other then killing the power to the motherboard and
restarting. There is no rhyme or reason to the lock no common timing or
software or hardware.
Thank You

Update:
After searching around found I have a Item under "other device",
PCI simple communication controller.
I have tried finding a driver for this but have no clue what it is, all my
PCI cards devices are accounted for.
I think it must be something on the motherboard
(133MHZ PIII MICRO ATX MOTHERBOARD WITH FLIP-CHIP SUPPORT)
, but have no clue what. Is
there a way to look up the hardware id that I found under the details tab in
the device properties.
I’m hoping this is the problem and not another one.
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6&REV_20
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6
PCI\VEN_13F6&DEV_0211&CC_078000
PCI\VEN_13F6&DEV_0211&CC_078000
I have tried to isolate the hardware malfunction, The only thing that is left
is my mother board: PCChips M758LMR, My memory 2 256 PC133 cards and my hard
drive a brand new memorex 120Gig drive.
The only non-signed driver is for my onboard modem but the card itself has
been removed from its pins as part of the trouble shooting process. I did
check the manufacturers web site and they admit that the modem driver is not
signed but they assure the board owners that the drivers have been tested and
work. This PC and all its parts worked fine with Windows ME, I’ve only had
problems since I installed XP Home.
I’ve also wiped the hard drive and started fresh.
 
S

S. Taylor

Since you put your computer together, yourself, you should have the
cd-rom it came with. Try run checking for patchs and updates that are XP
oriented.

Then check thier website and the chipset manufacturer's website for
additional patches.
 
G

Guest

I have done all that already, I’ve also replaced the harddrive connector
ribbon and am a subscriber to
Drivers. com. still no luck. I’ve also jumpered out the modem and it’s
still doing the same thing.
To reiterate It did not do this before I installed Xp.
 
S

S. Taylor

I only suggested that, because i had similar problem last month, when i
upgraded to xp from 98se.
The Device manager claimed that everything was working perfectly, but msinfo
claimed several
pci devices where NOT functioning at all and my usb controllers where
running in 1.1 mode.
In my case i have an an ECS N2U400-A motherboard.
And even I thought everything was ok, i still had to install drivers i didnt
think i needed.

And as i'm typing i realize, that my 1st post should have suggested you do
the same thing i did ......
Run the System Information Tool (Start | All Programs | Accessories | System
Tools | System Info).
IN the left pane, expand the Components tree and select Problem Devices.

This should tell what hardware devices windows knows it is having problems
with.
Take that info and check the appropriate manufacturer's support site for for
any info/patches or the such, for anything that may address the issue or
email them directly
 
S

S. Taylor

You can also double click an item in the device manager to view its
properties window.
Go to the Details Tab and select Bus Relations in the drop down menu.

Review this info for installed hardware untill you find which ones have the
vendor id that you're trying to track down.
Since the ID's start with PCI, i'd suggest you check PCI items on the System
Devices tree.

All these items are controlled by the chipset.
For example i use an Elite Group motherboard with Nvidia chipset,
so i use Nvidia's NForce2 WHQL drivers.

Because you were using an earlier version of windows, the drivers you had
installed
were for that version if windows.
After upgrading to XP, you would have install new drivers made specifically
for XP

The cd-rom that came with your motherboard probably only has IDE and USB
update drivers,
you also have to check the motherboard manufacturer's website and the
chipset providers
website for update that are for xp.

In the post i replied to you said
After searching around found I have a Item under "other device",
PCI simple communication controller.

This device is not using the correct drivers and MAY be the source of your
problem,
but you must get the correct drivers installed to rule it out.
They can be found on the websites of either the Chipset Manufacturer or the
Motherboard Manufacturer.

PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6&REV_20
PCI\VEN_13F6&DEV_0211&SUBSYS_021113F6
PCI\VEN_13F6&DEV_0211&CC_078000
PCI\VEN_13F6&DEV_0211&CC_078000
These are hardware/vendor id's for you systems pci devices
(the ones built into the motherboard and PCI based cards you installed)
Unless you're certain one of the above devices is causing your crashes,
the only way i know of to trouble shoot is too remove all hardware from
your computer, except for your video card and hardrive(s), and try to
replicate the crash.
Oh and go into your bios and disable all built-in hardware, such as sound,
lan, etc.

If you get no crashes under these conditions, re-install 1 device and try
again, to replicate the crash.
Continue until you crash, then suspect the most recently re-installed
device.

As a side note agp video cards also use a PCI\xxxxxxxxx.... ID number too.
 
G

Guest

I disabled the last of my onboard items including: Sound, LAN, and Modem but
I didn’t unplug the cables to these items. The only things left is the
motherboard, 2 memory cards, hard drive, power supply and monitor. I figure
the next thing is to pull one of the memory cards at a time and disconnect
all the power cables. If one of these don’t work I figure I’m SOOL because
when I Installed XP I converted the hard drive from FAT 32 to the NT
configuration. I noticed you had mentioned about the old drivers when you
upgrade, The second time I installed I formatted the drive installed XP and
the only use of an older disk was to verify a prior operating system. After
XP was fully installed and updated I went to my system and installed the
drivers that XP didn’t. I then joined Drivers.com, which updated all drivers
that weren’t new.
The only driver that came up as not XP signed was my modem driver, XP would
not let me install it. When the XP kept “HALTing†I installed the driver
after checking out PC Chips website. The web site admitted that the modem
driver was not signed but claim they have tested the driver with XP and it is
ok to use it with XP.
Thank you
Mike
 
C

Chuck

I assume you checked for any BIOS updates-- Next, BIOS has an area used by
windows. This might need to be cleared by a BIOS update utility, or your
BIOS may have the ability to clear it from the bios menu (EBID? EBD?) (I've
forgotten the name of the area that stores the data in BIOS!)
This was a problem that occurred in the early days of XP, and occurred with
some motherboards and BIOS combos.
 
S

S. Taylor

While reading more of the several thousand messeges on this ng, I found
,
by David Candy, to "Needle in a haystack".
In case you can't access that post i'll post it as a response to this post.
His post explains how to use Verifier to make a logfile of such crashes and
ways of fetting info on them.
Of course, you'll need to re-install your hardware, so the crashes occure.

The cable connecting your built in hardware to external devices, don't need
to be disconnected. Once disabled in bios, windows won't detect them
and thier drivers shouldn't be loading.

The post I mentioned above includes a link to a memory tester you can use
instead of switching out memory chips.


If you want to continue manuel troubleshooting , read on:
You didnt mention whether you checked the System Information Tool for any
listings under Problem Devices.
Doing so requires that all your hardware be installed/enabled, to see if XP
can detect the problem for you.

You should now only have an minmal system (hdd, video, motherboard, cpu,
ram, keyboard & mouse),
Has the crash re-ccured?
Are you putting your computer to same use, as close as you can, to the
conditions that the crash happened under?
If none have occured and your confident that the current hardware in use
ain't the culprit, Plug back in 1 device that you removed.
Or re-enable 1 onboard device in bios.
In windows, make sure it's detected by the Device manager and that no
conflicts are listed.
Check the System Information Tool to see if XP lists it as a problem device.
Then put your computer to use and try to cause the crash.
When your confident no crashes will occure, repat the above steps,
re-installing devices ONE AT A TIME and check thier
status in the Device Manager and System Information Tool.

When the crashes do happen again, suspect the most recently re-install
device.
Disable or uninstall said device and verify that the crashes did not occure
without it installed.
Then re-install the suspect device and wait for the crashes.
Once you have a verfied suspect, Uninstall it's drivers via the hardware
manager (if Add/Remove Prgrams has no entries for it, that is) and try
letting XP redetect it and install any drivers it has from the xp cd.
If it has none, then look for XP drivers for it from the Vendor's website
only.
If you had drivers for from a 3rd party website (such as drivers.com), you
should suspect them as the problem.
If you were using one from the vendor's website , try using an earlier
driver and contact the vendor to get help from them.
It could be that, no matter what they claim, that device may not be as xp
compatible as they'd like you to believe.


Now, if you are getting the crashes with just minimal hardware installed,
then you need to troubleshoot these items:
Memory
HDD
keyboard
Mouse
Video Card
Motherboard
I dont believe the monitor is your problem, but could be wrong

Use the memory tester David Candy mentions in his post, mentioned above.

Your HDD can be checked by using the diagnostic tools provided by it's
manufacturer,
that either came with it when you bought it, or from thier website.
If there are none available for your hdd, can use one of the tools mentioned
in many posts in this ng, to make and install
an image your new hdd onto your old hdd. The use the old hdd, to see if the
crashes occure.

I doubt the keyboard or mouse are your problem, but it's possible,especially
if they're usb devices.
Try usisng ps/2 devices, if you are.

Troubleshoot the video by using or borrowing a backup card.
Keep in mind that many (if not most) modern video cards have drivers that
load even if you change cards.
So you have uninstall the cards drivers to troubleshoot it.
If you're using and ATI or NVIDIA based video card, then make sure you're
using thier universal drivers
instead of the video card manufacturer's drivers.
If you are, then try an ealier version, especially with Nvidia's.

Troubleshoot the motherboard last, it's more difficult to do so.
If you're confident nothing else is responsible.....
Did you're crashes occure before or after you updated the chipset drivers?
Have you Updated the bios?
Did the motherboard's vendor have chipset updates?
(sometimes a devices manufacturer's drivers are more reliable then the
chipset vendor's are)
Did you install the separate chipset drivers?
( I.E. The usb & ide drivers on the cd or from the manufacturer, then the
chipset update from thier website)
I've had problems in the past from ide updates or using udma, have you tried
uninstall the ide update or disabling udma (If possible with xp)?

If, with a minimal system, the crashes occure when you're using alternate
hdd, video card, etc.
then suspect the motherboard.

Then you have 2 choices.
1) Do a clean re-install of XP.
If you're using an XP Upgrade cd, don't install the previous version of
windows,
it's possible that the XP cd had better drivers that it didnt use,
because the original os already had them.
Just keep the older windows cd handy for eula verifaction.

Once XP is installed, check the Device Manager for unknown devices
and install thier drivers, only use drivers from devices manufacturer's
(or chipset's) website.
Only update hardware drivers for devices that Xp didn't recognize.
If there are unknown devices listed that are on the motherboard, install
thier updates from it's cd only.
If you don't see an entry for usb 2.0 devices and the motherboard is usb
2.0 compatible, then install the usb
drivers from the cd, but not the ide drivers.

If any devices remain unknown, then go to the website for the vendor.
Stay away from any 3rd party driver resources, thier drivers could've
been the problem.

If any of the Motherboard has hardware that remains unknown
or it has devices listed the System Information Tool as a Problem
Device, and it's enabled in bios,
then re-download, drivers for that device, don't get any drivers for
devices, that are
detected and have drivers loaded for them, even if they're old drivers.

Once you get XP running with minimal hardware driver updates, try and
get the crashes to re-occure.
If it does, then it'd probably be easier to just replace the problem
device.
If it doesn't then i wouldn't install any more hardware updates for
devices that are working.
IF you fell you need to, then install them one at a time and see if
these crashes begin again.

If your not using some of the motherboard's onboard devices then keep
them disabled.
(I.E. disable the modem if you have broadband, or the lan if you use
dialup and aint using a home network)


2) There's a very good chance the problem is physical and not software. You
probably a vistim of badtiming.
A device could have just be going bad, right when you decide to upgrade
or had already gone bad,
your earlier os didn't detect that.
Just replace the device you finnally decide is the problem.

If you come to the conclusion that your motherboard is the culprit and you
decide to replace.
Then from my experiences i'd suggest you try a Giga-Byte board, ive never
had problems with them and like thier dual bios.
Use a motherboard, whether or not you use a Giga-byte board, that uses the
NVidia or AMD chipsets (aka NorthBridge and SouthBridge chipset),
if, you're using an intel cpu, then you may want to look for an intel
chipset instead of amd)
In the past I've had very bad experiences with other chipsets, and so only
suggest the above.

But you can and should checkout sites such as www.tomshardware.com and
checkout diffeerent motherboard's
before buying one.
And make sure then one you get is xp certified ( Search Help & Support on
the suject (xp compatible hardware) or search microsoft's site for the
Windows Logo Program)

If none of what I've written helps you resolve your problem, I'm very sorry,
but there's no other suggestions i can make
and someone else will have to try and help you.

Good Luck
 
S

S. Taylor

This was posted by David Candy in respnse to "needle in a haystack"

I'm sorry about the delay, my isp decide to change thier email servers
address
today .....*sigh*



Type verifier in Start Run, follow the wizard but choose All Drivers. This
will slow down your computer and cause more blue screen crashes but will
pinpoint what is causing the crash (if the original error message didn't).
Once you fix it you rerun verifier and turn it off.

If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).


You will be creating a crash dump file in c:\windows\minidump every blue
screen. Make sure you are set to record minidumps (Small Memory Dumps) -
type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read
it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @
mvps.org. Don't send me lots of them. Just the one from your last crash
after you turn verifier on. And only one per mail.

You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful
for searching, but NTStatus codes are (plus you can look them up here
http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).
 
G

Guest

Thank you for your help.
No luck so far.
Just purchased a new mother board and video card.
With any luck (none so far) that will fix it.
If not I know it’s the hard drive or the memory.
That’s all that’s left.
I’ll post the results
Thanks Again
Mike
 
G

Guest

Problem Solved
After many peoples Helped, I was able to discount what it wasn’t and
Guess what was the problem. It would be nice if before XP halted it diagnosed
And told you why it was halting.
Thank you all for your help.
Mike
 
G

Guest

Hi S,
The answer is precisely Unknown.
In general it had something to do with the motherboard,
As only the removal of that stopped the problem.
No other hardware has been changed and every: wire, card
And drive has been removed or disconnected during previous
Diagnostic testing.

I suppose it could be P.F.M. but I doubt it. ; )
Thanks Again
Mike
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top