it is a different a different drive. it has only 80 gb but that is enough for my windows x32 and some programs only. The drive with my x64 version of windows 7 is 1 TB.. Is it neccesary to erase my whole 1 TB HD or can i just erase the windows 7 x64 partition on that drive?
Given the nature of your error I would advise that you erase the entire drive, but obviously that is not possible.
You can use killdisk to erase just partitions (see here: Active@ KillDisk Partitions)
Note that there are no guarantees in life, so I would advise that you back up your crucial files that you would sorely miss, just in case something goes wrong with the partition erase.
Regards,
Reventon
You do not run kill disk from within the operating system.
Burn the ISO to a CD/DVD (or the DOS exe to a pendrive) and change your boot priority in BIOS to boot from that.
It does not matter what Operating System you use to burn the ISO to the CD, so you can do it on your stable 32 bit OS.
Regards,
Reventon
Ok, I bought myself an external HD and made a backup of everything. Disconnected the SSD drive and swiped and killed the 1TB disk. After reinstalling windows 7 x64 pro the first thing I saw was the message that explorer stopped working. It did'nt work out, sadly. I have the idea that all this is related to: memory problems (I ran memtest86 a few times) processor problems (my Q9650 works fine with win7 x86) of my mainboard (maybe its to old, I have the latest firmware, bios and drivers installed) Do you have any suggestions left? :) besides buying a new pc
A few questions:
- How did you install 7 x64 (via DVD? Pen drive? from original install media?)
- And is it legitimate?
Because, with the error appearing straight after you installed the OS (but not with the x86 OS) there must be something wrong with the installation process.
I installed it from a legitimate dvd. I also have the x64 home premium edition on a legitimate dvd but is giving me the same problems as the pro edition. I tried both my dvd drives for installation. Those are the same I used for my x86 version..
The question i asked myself many times is why I don't have those problems on x86? And is there a way to figure out which peace of hardware is causing my crashes? My memory, processor or mainboard?
Unfortunately, when it comes to problems like this it's pretty much trial-and-error. When any hardware subsystem fails like this, the software has a difficult time ascertaining what went wrong. Exception handling, particularly of failed hardware components, is extremely difficult. When hardware fails, the "platform" underneath the software just fails. It's like trying to diagnose a mechanical problem with a car when the road comes out from under it. There's nothing wrong with the car, the platform failed.
I used to have testers here at the company that just couldn't grasp this. They'd get a bad component in their system and keep coming at the development team over problems that had nothing to do with the software. I finally coined a phrase "You can't fix hardware with software". If you have two completely separate versions of the software and both fail after installation you have a hardware problem.
That's why I suggested that you either replace the motherboard, or the memory. It can get expensive to do so, though, compared with just buying another machine. By the time you've tracked it down you might have spent as much as you would have to just replace the thing. Back in the "golden" old days when I was building systems, there were pieces and parts for everything. Everything now is so tightly integrated that swapping sections out isn't easy any more. By that I don't mean access to the machines isn't easy, I mean that there's less separate plug-in components to try replacing. Practically everything we used to replace when troubleshooting a system is now surface-mount technology.
Sorry I couldn't be of any better help here man ... it's a hard pill to swallow sometimes. It looks like you have a bad system. As I said ... try replacing memory, motherboard or both. It might even be something as obscure as your power supply. Sometimes, if the power is marginal the system fails in a way that doesn't make sense.
-Max
Quote
So it didn't work