I've read the stickies, my problem doesn't seem to be covered in them.
I just built a new system and had it up and running fine for a good 5 hours or so, then while installing my DVD drive software and uninstalling the DVD "PowerDVD" program it had just installed (doubt this could be the culprit, but this was what I was doing when it occurred), I got a BSD and now every attempt to start up the machine gives me continuous long beeps. The BSD said something about an error with graphics drivers. According to my mobo manual, continuous long beeps means the GPU is not seated properly. My GPU is integrated I have tried using a PCI-E GPU also, tried removing the second stick of memory, and everything inside my machine seems to be seated properly. The system is as follows:
No I couldn't because nothing happened when I turned on my machine other than the continuous long post beeps. However, I found out that my mobo manual wasn't correct because when I tried every memory configuration I could, I finally got the thing to boot up properly. One of my chips is bad. Nothing at all wrong with my GPU. And even if I mistook long beeps for short ones, short beeps means power failure. Darned manual ><
...now to figure out if continuing to mess with my old version of Windows XP from the old Dell is worth the trouble (Dell recovery disc). Lots of blue screens (generic text with no actual error codes) and apparently the Windows Updater is problematic. On top of all that I somehow managed to get that OLD issue from XP/Win2000 that would repeatedly give you 59 seconds before shutting down =( If I can't figure out the remedy for that thing I guess I'll just buy Win7.
A restore disc would be restoring the drivers as well. This would be problematic obviously. Find a unmodified XP pro or home disc (whatever the license was for) and use that to install and just use the code. One word of warning though, I tried using a XP home SP3 with some old codes I had and apparently they phased out the ability to see them, so you should try with older SP's if that happens.
Of course, if you're relying on the restore disc for the code I think that plan of attack is SOL. (unless it works well enough for you to run one of those key finder things. I used one to find out that the code on my vista laptop isn't the same as the code on the sticker of that laptop...)
Yeah, I'm honestly hoping this is the problem for me right now (it makes sense if it is) so simply buying a retail OS should fix it for me. After all, it appears I have no problems with the hardware itself after identifying the bad memory chip. I need to change out my main system with Win7 (using beta atm) anyway, really hoping that if it DOESN'T fix this new computer I can still use the Win7 OS and code with my i7 system =( I guess i'll see.