PDA

View Full Version : BSOD ** Hardware Failure call vendor for support ** system has halted **



GAR
04-30-2007, 10:29 AM
Hey, my system is PRIME 95 stable for 8hours, passes memtest for 3 hours, every stability test i throw at it its stable, but i get these random BSOD's that says ** Hardware Failure ** system has halted, call your vendor for support, i returned my first evga because of this, now my second one is doing the same thing, any ideas on why this would happen, my system is stable, but these random BSOD's.

this is how its written

*** Hardware Malfunction
Call your vendor for support
*** system has halted **

Any help would be apreciated thanks alot.

Leeghoofd
04-30-2007, 12:32 PM
I wouldn't say ya system is stable then :) try to run the ram at normal speeds 5-5-5-15 and see what gives, then try to give the cpu a bit more Vcore, seems low to me ( but if that is whats needed excellent)... my systems also passed Orthos, folding home for hours, once shut down It would return into windows with the message your system has recovered from a sytem failure or give weird and slow loading in explorer,.. adding a bit more CPU VTT solved all my probs , though orthos and co were megastable it behaved erratic....

mezcal
04-30-2007, 12:50 PM
Be interesting to know which particular vendor it would like you to call.

Anything in event viewer?

Leeghoofd
04-30-2007, 01:02 PM
Prolly will be directed to Bill Gates' office telling him he needs to upgrade to Vista because he has a DX10 card :)

GAR
04-30-2007, 01:10 PM
OK, so i was able to duplicate the issue, i get the BSOD while running dual SUPER PI 32M, i get the BSOD, now i found something else that is related to this issue, is the FSB VTT voltage, anything lower than 1.4 i get the BSOD while loading windows, very weird......i have the FSB VTT voltage to 1.5 now, i am running super PI 32M while i type, ill see if it comes up again, but im guessing it has something to do with the FSB VTT voltage.

GAR
04-30-2007, 01:33 PM
Ok so Super PI dual 32M passed no BSOD, so i just have to use it and see if it happens during everyday use.

Leeghoofd
04-30-2007, 01:38 PM
Well GAR my system would reboot at 400mhz FSB with CPU VTT below 1.4 need 1.45 to keep it from rebooting... it's a good combo of voltage settings that needs to be found , this drives so many users mad...

GAR
04-30-2007, 07:37 PM
Well GAR my system would reboot at 400mhz FSB with CPU VTT below 1.4 need 1.45 to keep it from rebooting... it's a good combo of voltage settings that needs to be found , this drives so many users mad...

Yeah big time.

Mad_Man
05-01-2007, 12:49 AM
I had very similar problem. system stable but sometimes it would just loose power or bsod. after many hours of tryies and errors i figured what helped...
Fan placed at raid array of two hdds. weird

mvbbfla
01-21-2008, 09:09 PM
Hello:

I recently encountered the same issue with a Pentium 3 Dell desktop that would give a BSOD that said hardware failure please contact vendor for support and that was all that was listed and the system was halted. I looked into this more and found that the problem occured when opening Microsoft Office that had been loaded on the system I think it was Office XP but everytime I opened this program the BSOD would appear. I looked at the display properties in the control panel and noticed that my graphics card was older and only supported two resolutions which were high and low and 16 bit graphics so I unistalled the graphics card and installed a new one in the AGP slot and then rebooted and installed the drivers and software and then adjusted the resolution to 32 bit and a better size for the monitor and this solved the problem. I put in a Nvidia Gforce AGP card that had a vga connector and installed the software. Just thought this might help but I also have found that some software programs like Office need higher video capability and the resolution should be bumped up to 32bit and adjusted to allow the program to work but the Office application doesn't indicate this it just goes to a ambigouos BSOD without much other info.

T2k
01-22-2008, 01:46 PM
Hey GAR,

I feel your pain - I'm having somewhat similar issue: lockups in 2 minutes (best case scenario) then it takes 2 mins worth of continuous ClrCMOS/reset/power off/power cable off/back/reset/clrCMOS/reset-cycle until it finally botts up again - only to crap out within a minute (usually in 20-30 seconds)... never seen anything like this.

All this when everything on default, of course, no OC whatsoever.

Any thoughts...? :(

T2k
01-22-2008, 02:03 PM
PS: I'm running latest BIOS v907...