The microcode update did not make any difference for Tom, and apparently was present for Kyle.
The reason that timing loops in Windows were able to make the OS fail, was because system software directly accesses the hardware. User code does not have this ability, so different all different frequencies should be equally as robust at running a particular piece of software.
They used to make DOS games which were not playable at higher frequencies because the game ran too fast, but this didn't cause them to crash.
Scumbria
I'm not a Device Engineer, and I gather from many of your previous posts, neither are you. If Kyle has sent back his 1.13GHz, that intel will apply the strip back process, peel the layers back one by one, and then we'll know.
I am however, familiar with the Wafer Sort, and Final Test area, as well as Burn-In, because that's where I started out. That's why, I'm having difficulty believing something so obvious, could have gotten by, on a design that is over a year old. I would almost go so far as to say "unbelieveable".
I just have an issue when people say a microprocessor is bad, because a piece of freeware crashes. And it makes me very suspicious that Mr. Pabst is unwilling to send his back.
Yes, Yes, I know...... It's all a conspiracy, to make Tom a scapegoat of intel.... baloney. Kyle doesn't seem to think so. But that really tells me something about these two people, and it should tell you something too.
SemiconEng |
