YayMii said:
Schlupi said:
If it's flash player, try reinstalling it? >_>
...read the whole post.
But to summarize:
Reinstalling Flash Player didn't solve the problem. Reinstalling it again didn't solve the problem. Reinstalling WINDOWS didn't solve the problem.
(on a related note, I just installed Windows XP as dualboot, and I'm not having any problems on that side. The problem only happens on Windows 7, even after reinstalling)
Wait, reinstalling windows (assuming this time without SP1) did not solve the problem? Assuming you did NOT install all drivers (if it's a driver issue installing the latest greatest drivers in the same setup you had could make the system crash just as hard of course), that's weird and would indicate a hardware problem. If the problem is there using stock settings, either the board is toast or the ram (at least via probability, had a machine do similar crashes with a failing disk, passing SMART). Seeing the machine you describe (sort of), have you checked your caps for leaking? Back in the day there was a company spewing out bad caps, my K8N-E sadly was one of them. Oh yea and 20 hours of linux, unless the machine is very unstable, sais NOTHING about possible hardware failure due to overclocking. For all you know it's a lucky run, load was low and thus so was Vdrop.
You did remember to turn off cool'n quiet and all other speedsteppings btw right
? /see that was mentioned
Personally had good results with catalyst 9.3 on an AGP board btw. That was using XP.
And seeing as there is something with flash player in there with your last few posts: it sucks. You also say that without any programs installed the machine crashes? That would go with hardware or driver failure bigtime. As for flash, they somehow broke hardware accelerated flash playback, make sure that is disabled (if available).
Oh and if you recently installed new hardware, check your IRQs. Could be, had that problem a few times back in the day with hardware sharing the IRQ not understanding which info was for which hardware
.
My most logical conclusion at this point: You, or windows, upgraded the drivers which are now causing an issue OR you have dead caps. That is unless you have recently started those overclocks and haven't actually run any genuine tests with that XP of yours you just installed.