What I'm asking is, what was the error that was made back then when Intel started the Pentium processors series and what did they do to correct the error that was made?
206904
Intel had an error in the microcode on Pentiums up to 100 Mhz that made incorrect calculations for certain numbers when performing division.  When this error was discovered by a math professor (I believe from University of Virginia) and widely publicized, Intel offered to replace anyone who had a defective chip with one where the microcode had been corrected.  One good discussion of the problem in more detail is linked below.
478634
intel does not make the motherboard, got to http://www.tigerdirect.com and find what you need there. you can also call then 24/7 at 1-800-800-8300 and they can walk you thru the process.\n\n-Doc-
315521
It sounds to me like the system may have suffered from a static electric discharge or some kind of elctricity has passed through the processor. I know this because the pins are black and it is usually cause from electrical burns from some source of electricity. You could have left the computer on during a lighting storm or you could have experienced a power surge or brownout or spike in your house. Now this does not happen immediately but over time it can cause internal parts to become like that.
126531
Well, they weren't making motherboards 40-60 years ago, but what you need to do is find out which processor they want (or you think they should have), then you'll know which socket you are dealing with.  However, I wouldn't recommend you try to build your own computer, if you didn't even realize that there are over 10 different sockets on the market right now.
474943
Sounds like it could be a RAM problem is the RAM new? have you used it in another system? try moving it about and if you have memtest loaded in your bios run that for a couple of passes and see if you get any errors. post back or email me the results
484078
i am looking for technical report about intel dual core processor ...  \nhi, here are some websites links with enough technical report on them .http://www.wisegeek.com/what-is-a-dual-core-processor..\n \nhow can i write a technical report about developing sowftware of ...  \n...said the application has some weaknesses about the known situation. a report should include the above 4 issues. in order to do this, the ...
543064
He would have damaged them when he took the processor out to put it in the new motherboard or the one he was working on. They are damaged when they do not seat the chip set right and attempt to force it. They owe you some money.\n-NmD!
207090
CPU\n\nAlso known as a processor or microprocessor the CPU was first developed by Intel in 1974 and is short for Central Processing Unit. The computer CPU is responsible for handling all instructions and calculation it receives from other hardware components in the computer and software programs running on the computer. Below is a graphic example of what the Intel Pentium processor looked like.
645394
I thnk your BIOS corrupted or dead. It may be cause by the upgrade of the wrong BIOS or actually the BIOS chip hardware is failture.\n\nThere are few ways you may do:\n1) If you have a EPROM writer, you can buy a cheap BIOS from Large computer hardware store and burn a BIOS.\n2) If you have a spare same machine. You can take out the BIOS chip and put it into the one that has problem\n3) In the worst case, you have to replace a mother board\n\nGood luck\n\nd10v01b
613750
top notch equipment there...\n\none thing, now is a really bad time to be building systems. intel's conroes are coming out next month and they beat amd's processors by a rather large margin. also, amd released socket am2, however, it yields very little performance boost which will hopefully be changed in their next modifications.\n\nbut if u must have a new system now...i don't see what's wrong with that layout.
54604
You know this topic is too extensive to cover here. \n\nThere is some good reference material covering both types of processors here: http://ourworld.compuserve.com/homepages/r_harvey/doc_cpu.htm \n\nIn Pentium class processors, there also model-specific registers  http://ourworld.compuserve.com/homepages/r_harvey/doc_cpu.htm
30318
A few things... 1) The chip may be defective 2)The mother board in your computer doesn't support 512MB sticks.\n\nDoes the system start up when the chip is installed? If it does you could use a program like MemtestX86+ to test each chip.   \nYou may also want to check compaq's website for any bios updates that may help the computer.  \n\nFinally, PNY's memory configurator is a nice help for figuring out what your system can handle.  It will give you details about the motherboard, like how much ram is supported, bus speeds, cpu speeds, etc... Granted they will recommend PNY memory products, but their product model numbers give away the specific type of memory they are e.g. PC100, PC133, etc..
98474
Certainly. Any code can connect with other systems incorrectly (blatantly or subtly) and when a new version is released, may or may not have the same wrong connections. Some video chip vendors have not been (are not) very forthcoming about the control interfaces to their chips. And sometimes about best practices in using them. They regard it as proprietary information and not for release to just anyone trying to use the chip. Software written for these chips is more likely to do something the chip doesn't like, or to not do something the chip requires, than software from folks who actually know what the chip is supposed to do. These problems sometimes shows up in the display or interfere with the game being run. \n\nExcept when there is a defect in a standard specification (inconsistent use of the same API point, for instance), these are all bugs. \n\nSome bugs cause gross failures. Crashes, data loss, and that dramatic stuff. Other bugs lead to memory leaks, or buffer overflows or soem such. The software (and the system) continues to work for a while, but becomes more and more likely to fail in some obvious way. This last might be called a decrease in stability, I suppose. \n\nAs for the bug history of an implementation of OpenGL, see the developer Web site. Most keep a log of modifications to the released software, maintain a bug reporting mechanism,  and so on. These constitute a sort of record of actual bugs in various versions of the software and the fixes applied thereto, but include a certain amount of pilot error and confusion by those reporting as well.
199271
You installed it incorrectly.  It’s bad and you should return it.  A setting in BIOS isn’t correct.
483829
Under the System Information area it will say the maker and code name to your board, then you can vivsit the website and get system diagnostics for you board, if it is a Intel P4 and less than 18 months old it could be.\n\nWrite down the infomation, I found my board info and was able to reassess my memory configuration.
231272
If you upgrade from a pentium 3 to a pentium 4  but didn't to a fresh install of windows you should definitly update your screencard, sound card and motherboard drivers.\n\nYour next option might be to make sure that your current ram is 100% compatible with your motherboard and also make certain that there are no problems with your ram.\n\nAlso turn off automatic restarts in XP, so that you can see what information is displayed when the error occurs. To disable autoimatic restarting in windows XP goto control panel (instructions are for the classic view). Open SYSTEM and CLICK on the ADVANCED tab. under the section STARTUP AND RECOVERY click the SETTINGS button. Uncheck the combo box labeled AUTOMATICALLY RESTART in the SYSTEM FAILURE section.\n\nAfter that if you recieve a blue screen you can record the information there. If will also tell you where the minidump is stored, you can contact me and i'll give you my email adress so you can send me the minidump for debuging. EDIT: the blue screen should give you an indication of where to start looking for the problem, i.e. what driver it could be.\n\nIf you dont see a blue screen upon restarting it's more likely a hardware problem. this could be due to a underpower system, faulty power supply, corrupted ram or some other hardware major hardware problem. \n\nTo check the ram goto http://www.memtest86.com or if you have a linux boot cd lying around it might give you the option to run memtest from it.
343026
Here's a link to their technical support.  See if it explains your error.\n-MM