Win7 64, gigabyte mb. Won't start up anymore.

Ok i did some further things to try and eliminate the issue. i unplugged the hdd to make sure its not that making the noise on start up. turns out its not thank god and im now pretty sure its the gpu. it does it for about a min on start up and only when the computer has been off for some time.

is it safe to say the gpu has kicked the bucket? considering i still have no signal and cant see anything, plus ive been running it for about 2 years on a 32" hd screen and use my computer for 3d modelling as well as games a lot.

also, whats the best way for me to get files from my hdd, one of those sata usb connectors maybe?

thanks, any help is really appreciated

Hi, sorry for late reply, been trying to sort stuff out regarding the problem lol.

• I checked all cables, etc everything seems fine.
• I tried to use the 2 molex to 1 pci-e instead to make sure it wasn't a duff pci-e, but no luck
• I managed to get a caddy, and all is safe on the harddrive :)
• I connected speakers/headphones and hear nothing, and im pretty sure i have no internal mobo speaker....damn it
  

• i went to a pc store and they kindly tested my gpu in a tower, however they only plugged one pci-e external power into it (my gpu needs 2). But it still powered up.....and no signal, which is what i hoped as i can say it's the gpu. Or maybe not? must i have both pci-e slots plugged in?

Ok so i've found someone who said they will test it for me once again in a few days (lets hope he has more power cables this time). presuming we test it properly and still no signal, shall i just go ahead and order a new gpu?


---------------------------------------------------------------------------------



Furthermore, if its not the gpu and i need to test other things, like taking the mobo bat out for a while to reset the cmos, then i figure i will want put it back to its overclocked settings it came with.


to do this, must ram be overclocked with the cpu? I'm quite curious about this in general.



I found these settings from someone who basically has the same build and oc as me do they look ok assuming i need to redo the overclocking in bios and is there anything else missing in the screens?
http://dl.dropbox.com/u/7618572/Tita...erclock_01.jpg
http://dl.dropbox.com/u/7618572/Tita...erclock_02.jpg
http://dl.dropbox.com/u/7618572/Tita...erclock_03.jpg


Thanks again, sorry for the long text lol

Ok im back again, with good news.

firsty i was being a complete dumbass....basically when i reseeded the ram, i didnt push it hard enough, on the account that i pushed it pretty dam hard and it did not slot in....so i thought maybe im not meant to push it this hard as i didnt want to break anything. So i just put the clips up and assumed thats how its done. So i was being too careful haha.

anyways, i figured i should push harder just incase and it popped in correctly.

now i have signal...and windows booted up normally.

However i reset the cmos bat before, so i went to bios and reset the date to now....booted up windows and it remembered all my overclocked settings??

How has this happened even though i reset the cmos? i didnt load any optimized defaults either lol

also, apart from backing up. is there anything else i could do now in regards to what initially happened (the system crashing at startup) and constantly rebooting

Thanks all for time in helping me out though i really appreciate it

Yea i think the bios settings must have something to do with the date. upon first boot i left them, windows loaded and thought the date was 2009, the cpu was not overclocked either (factory settings in effect i guess). I restarted and changed the bios date to now, and it seems to have automatically loaded the oc settings.

I'll take a note of them anyhow, as i may put the cpu back to normal speeds to prolong the life, although 2.6 oc'd to 3.4 idol temp 45c isn't too heavy for now.

Think i'll back up properly now too lol.

Dave76 said:

If you are still having crashes and reboots we can look into it further, hopefully seating the RAM will solve this.
Let us know if your system is stable.

Everything seems to be running now thanks, I've done a chkdsk in cmd and had no errors. I don't wanna get too excited though so i'll see how things go over the next few days.

thanks again guys:)