hello first time posting in these forums sorry if ive posted in wrong area.
im looking at 2 problems here firstly. BSOD under OS
secondly- these crashes have 'seemingly corrupted HDD. cannot use windows disk because of blue screening soon after language input screen (first interactive screen)
after swapping my motherboard out for a new one and reinstalling windows almost a year ago. its been Blue screening.
usually happens AFTER ive stressed the computer by playing a game or a program(which it will do as long as i want)
then if i close program and leave it on desktop it will blue screen. its been this way for months its usable but frustrating if it crashes on shutdown and corrupts harddrive which it has atm.
i saw an increase in stability for a day or so when i let the motherboard BIOS automatic tune settings under its OC tuner Utility. but crashed eventually and corrupted the harddrive it now wont get past the language input screen while booting from windows disk so i cant repair it!!!
i suspect my BIOS settings are not set correctly. as i have been using them set to Auto ever since i installed this mobo the ASUS M4A87TD EVO
system specs are:
AMD phenom x 4 960t 3.0ghz
mobo- asus M4A87TD EVO
RAM - Corsair CMX8GX3M4A1333C9 4x 2gb (8gb)
PSU - Corsair TX 750w ---------also tested with Corsair 550w
HDD - Hitachi HDS721050CLA362 ATA Device 500GB
DVD rw - (not sure on brand or model)
GPU - ASUS EAH 6950 DCII 2gb ---------also tested with EAH 3540
Windows 7 64 bit home premium
already done much if not all hardware and stress testing. all hardware passes tests
memtest 86+ passed
Hitachi HDD diagnostic passed
windoes mem diag passed
prime 95 and furmark ran for hours no problem (untill i close the program lol)
mobo BIOS updated to latest 2001 ver.
hardware seems OK
Video drivers have been extensively tested also. and relacement graphics cards and power supplies have been tested
i remain confident it is the BIOS settings but i have no way of knowing what im doing in the department
how can i get windows to boot from the disk to run repair
then i can look at this underlying problem