0 Members and 1 Guest are viewing this topic.
Those sort of errors come from broken CPU/Motherboard's
Quote from: EnEsCe on April 04, 2007, 10:08:57 amThose sort of errors come from broken CPU/Motherboard'sI took apart a computer and managed to access the motherboard. You have no idea how much precision is needed to build a properly functioning motherboard, let alone the proccessor that have been embedded in it. Don't try taking apart a computer unless you have anti-static gloves or something anti-static.
Like I tell everyone with computer problems. Hit it with a hammer. If it still doesn't work... hit it harder.
Here is the answer, everyone else is wrong:http://it.slashdot.org/it/07/04/04/1256229.shtmlit is indeed a problem caused by your sound drivers in conflict with Microsoft's hasty patch for the very bad vulnerability going around.If the article linked doesn't suggest anything, then you have no choice other than to wait for an official fixedit: and so you know, that patch was released yesterday. Your computer probably downloaded and installed it overnight since Microsoft released it as an urgent patch.
Is there any problem with kicking? Of course not.Car not starting? Kick it.Refrigerator not running? Kick it.Nose not running? Kick it. (Might result in a nosebleed.)Computer not working as you wanted it to? Kick it.