george k said:
...took the HDD off connected it as an external HDD to another computer,scaned it for errors,it showed that no Errors where found,i checked the ram using memtest and it didn't found any errors....
Some things people often don't know:
1) "memtest" does not
test ALL the RAM. There is a small section of critical RAM at the beginning of the primary RAM module that is used to load and run memtest. That section (something like 100KB) cannot
be tested. So, if something is wrong with that part of the RAM module, it may later show up as an unpredictable problem when running under an OS like Windows or Linux. If you are using a single RAM module, there is nothing you can do to test that section of RAM using memtest. However, if you have 2 modules, you can swap the positions of the RAM modules so that the primary slot RAM that was running memtest is now in the non-primary slot and that section CAN now be tested.
However, you also need to be aware that "memtest" will only test 32bit systems (up to ~4GB). If you have more than 4GB installed you need to use "memtest86+
". While memtest is running, watch the progress of the testing and make sure it shows that it tests all the way to total amount of RAM you have installed. For example, if you have 8GB installed (e.g. 2x4GB RAM modules) and memtest shows it only tests up through about 4GB, then the second RAM module is not being tested.
2) "scanning" a disk for errors using a tool like "chkdsk" or similar only checks the filestructure...so-called "metadata". It does NOT check the content of the files, which may
be corrupt or even "missing" and could cause unpredictable problems when they are actually loaded and running. There could also be a virus that must be scanned for using a self-booting CD/DVD. An anti-virus program that runs under Windows may not detect certain malware because the malware "fools" it or even disables the anti-malware program.
So, if you have not tried this, you need to re-install Windows 7 from the very beginning
preferably using Microsoft supplied CDs/DVDs and then see what happens. You may even have to try using a different HDD or even use a partition manager tool. Several freeware programs are available, if memory is working right I think freeware PartedMagic (qparted) is one of them that can rewrite base drive information like the MFT (Master File Table).
3) Also, when you are having problems and nothing else works, it is a good idea to clear or "reset" your BIOS CMOS every time you try to boot. Follow the instructions
in your user manual as doing this incorrectly on some motherboards can physically damage the motherboard. For example
, on one of my motherboards I MUST turn-off the PSU using either using the rear PSU switch or by pulling out the AC plug and wait a minute before performing the "reset" procedure (which involved temporarily shorting two pins on a specific jumper block). Just using the front-panel switch is not enough.
edit to add:
BTW, given that you said it froze one time while in the BIOS Settings (which means the HDD is not yet involved that particular instance), I tend to suspect the RAM subsystem
(which includes the RAM modules, the CPU, the memory controller (if separate), etc. This is why it was #1 on the list.
Please also note that if you are trying to run RAM above 1333MHz on certain motherboards it may not work properly without your experimenting
with changes to various voltages, clock speeds, and or multipliers. For example, if you are trying to run DDR3-1600 RAM at 1600MHz you may
have to change CPU voltage, Northbridge voltage, RAM voltage, specific RAM timing values, etc. In addition, you need to make sure your motherboard actually supports running RAM at higher speeds...and it may
not support RAM certain models of RAM modules. See http://www.hardwareanalysis.com/content/topic/77413/?o=20#592907
Alternatively, you can manually set all your BIOS Settings for voltage and timings to default
or "automatic" which should
make the settings conform to running the RAM at the globally supported speed (e.g. 1333MHz). But, keep in mind that even then, SOME
RAM modules either don't provide the right "SPD" information to BIOS or are not supported on a given motherboard and so BIOS may
be unable to automatically set things up properly.