Almost certainly time for a new battery - you're lucky you don't have a UK GT Four as it would have fried the alarm system as well. Cost me £350 to replace the battery and the entire alarm system when mine died.
I'd definitely go with the better graphics card like Th3D0n says. i5 is not a weak CPU in any way, and the graphics card will make a much bigger difference. You'd have a lot of trouble maxing out the CPU but no trouble at all maxing out a £150 graphics card.
I get similar interference in an Antec 300 at work, but my venerable P180 at home has no interference at all with an EX58-UD5. I think it's just the shielding on the cables, coupled with different graphics cards.
You could try a homemade fix of aluminium foil - make sure to cover the foil in...
I had a similar problem with my UD5 only detecting 4GB out of 6GB.
Main things you could try:
1) Remove all RAM except for one stick in DIMM1_1 and see if it boots. If it does, add a stick at a time making sure to reinsert the RAM firmly, rebooting each time you add a stick. This worked...
I had a similar problem on first setting up my UD5 / 920 system. The BIOS was reading 4096MB with all 3 OCZ 12800 modules installed. I read these threads and some similar ones on other forums with a bit of a sinking feeling and thought I'd need to take it all to pieces again to figure out the...
Are you sure there actually were broken pins? If it was also a socket 939 winchester as in your sig, there are a number of pin 'spaces' which are not used in socket 939.
Pics:
http://techreport.com/reviews/2004q2/athlon64-3800/index.x?pg=1
Well, back to the drawing board for me as it's just happened again, guess I haven't cured it after all. Perhaps I shouldn't have talked about it.
I recommend reading the thread linked in my post above, there is a fair amount of good advice there. Different things work for different people...
I found, regardless of what 'people on the internet' claim, that it was perfectly possible to roll back to the MS IDE drivers from the device manager - although I accept that maybe what XP says has happened and what has actually happened may differ a bit ;)
Personally I had the same symptoms and it was connected to the disk subsystem - either a faulty IDE driver, faulty motherboard or faulty HD. Now this was on a different, Intel, system quite a while back, and the pausing was caused by Windows falling back to PIO mode due to too many errors on...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.