poeg

Likely needs a repair install is all which will also let you identify bad hives (it doesn't see the original windows install to make the repair) and you can then decide if backing the lot up and going in fresh is what you need to do.

Its easy to do, worked the last 60 or so times I did it for my clients the last one being yesterday and only requires that you grab your hardware IDs from the device manager. Change the SATA to an ata compatable setting or if your bios is that restrictive …

Don't forget to check your thumbdrive for contamination also. Its likely you'll get 2 positives from it if its what I just finished removing. Also saw a bogus ctfmon that wasn't able to be identified as such until scanning from safe mode with Malwarebytes and Superantispyware.

Check chipset heatsink with digital thermometer match to mainboard health section's reading. A few degrees is OK anything larger is poor contact.

I assume you have the latency set as something both sets can use? Also, why on earth would you retain the 2x256 with 2GB? Thinking you are gaining something not offset by the possibility of a mismatch which will show up clearly when the used addresses reach your 512 and …