Strange Activation Message (Windows Vista)

Funky_Junk

Limp Gawd
Joined
Oct 1, 2005
Messages
353
I'm using Windows Vista, happy as can be. Yesterday however, I got a strange pop up message saying that I had changed the hardware in my computer and that I would need to reactivate my computer within 2 days to continue using it. This is weird because I have made absolutely no hardware changes within months. Still, I went to the control panel to activate windows, but it says the key is already in use. Whats up?!?!
 
You'll have to phone them to reactivate because you are reactivation again too soon. As for why it is telling you to activate again, it is possible your ram is flaky. I've had this happen to me and also a friend and it was bad ram. Get memtest86 and test the ram.
 
I had a major issue when i was overclocking my processor. It wouldnt boot to windows normally and it stated that my vista copy is invalid....which is not. I have the software right here. After i lowered the clock speed to something more stable, all the messages went away and it never happend again.
 
I do have my computer overclocked, but I've been running Vista for about 6 months without any problems.
I ran Memtest, and although I didnt have time to finish the tests, it found 96 errors. Does that mean I have to get new memory?
 
That means your overclock isnt stable

My overclock has been running stable for over a year and is able to run all sorts of benchmarking tests for hours without crashing, it cant have to do with overclocking can it?
 
How much is the ram overclocked by? You can put a ram divider on the ram in the bios so it isn't overclocked. That's what I do - cpu is overclcocked but ram ins't. And the reason I did that is because I got ram errors when I ran memtest86 when the ram was overclcocked. Stopped overclcocking the ram and no more errors. I know it's best to run the ram in sync with the cpu but it doesn't make that much of a dif by running it async. Test your ram at stock speed and if you get even one error then replace it. If you get no errors then you know you have to stop overclockiong the ram by putting a divider on it.
 
Id try running memtest for 24 hrs to see if it passes, if it doesnt, then some component isnt able to handle the overclock.
 
You'll have to phone them to reactivate because you are reactivation again too soon. As for why it is telling you to activate again, it is possible your ram is flaky. I've had this happen to me and also a friend and it was bad ram. Get memtest86 and test the ram.
It just happened to me, by just adding more ram. I got the same message, and had to reactivate via the phone.
 
Whilst this instance certainly sounds like it might be the overclock contributing, I'd like to point out that in reports like this it's often the stuff remaining unsaid which holds the key to the dilemma, rather than the stuff which is said. Comments such as "I only added a drive" or "I never changed any hardware" can be misleading.

I had a reactivation over the weekend myself. I 'only' replaced a DVD burner in my system!

What that statement doesn't say, of course, is that the new DVD burner was a SATA drive rather than a PATA drive, that I'd run out of SATA ports on my primary onboard SATA controller, enabled a secondary controller in BIOS and connected the new drive up to that, found that it didn't work correctly, stuffed about installing device drivers trying to get it to work, swapped drives around to get the burner on the primary controller and one of my hard drives on the secondary controller.....

Lots of changes in reality, in other words, with components appearing and then being removed, driver letters changing and so on. No wonder activation had a hissy-fit and spat the dummy!

But I only replaced a burner!

People often forget that configuration changes on your system can and sometimes do appear to Windows as 'hardware changes'.
 
If MemTest is erroring, something isn't stable. If the errors go away when you back off to stock, it was the overclock. If they don't, it's the RAM.

Simple.
 
Sometimes just updating a driver can cause this. It's happened to me before.
 
Back
Top