Ironworks Gaming Forum - View Single Post

shamrock_uk · 06-05-2006, 02:27 PM

Oh, the monitor problem may be more serious then - that's just exactly what my old CRT likes doing now and then

I'm a bit stumped to be honest...I don't see how your computer has been affected by the storm, yet it seems entirely too coincidental! You've even got the thing surge protected, so even if somehow your mains was a bit funny when you plugged it in, it shouldn't be affected.

All the same, going on the assumption that it has been affected by the storm, I'd still be inclined to check your memory again in case it's been the casualty. 17 passes is a little excessive though

Try one pass if you have 20 minutes...if nothing else it'll help eliminate one cause.

The only other memory I can imagine that error refers to is that on the motherboard itself, but most of that's ROM IIRC and if it was your CMOS that has been fried, I wouldn't expect it to boot some of the time but not others.

Beyond that, I'm afraid I'm at a loss. Perhaps Hive or someone else with more experience will be able to give a different solution.

Just a thought - what happens when you do a hard reset (ie with the physical reboot button) after the freeze - can you get into Windows after that or do you have to turn it all off?

06-05-2006, 02:27 PM	#4
shamrock_uk Dracolich Join Date: January 24, 2004 Location: UK Age: 42 Posts: 3,092	Oh, the monitor problem may be more serious then - that's just exactly what my old CRT likes doing now and then I'm a bit stumped to be honest...I don't see how your computer has been affected by the storm, yet it seems entirely too coincidental! You've even got the thing surge protected, so even if somehow your mains was a bit funny when you plugged it in, it shouldn't be affected. All the same, going on the assumption that it has been affected by the storm, I'd still be inclined to check your memory again in case it's been the casualty. 17 passes is a little excessive though Try one pass if you have 20 minutes...if nothing else it'll help eliminate one cause. The only other memory I can imagine that error refers to is that on the motherboard itself, but most of that's ROM IIRC and if it was your CMOS that has been fried, I wouldn't expect it to boot some of the time but not others. Beyond that, I'm afraid I'm at a loss. Perhaps Hive or someone else with more experience will be able to give a different solution. Just a thought - what happens when you do a hard reset (ie with the physical reboot button) after the freeze - can you get into Windows after that or do you have to turn it all off?