Official GIGABYTE Forum

Questions about GIGABYTE products => Motherboards with AMD processors => Topic started by: knightrider56 on November 17, 2010, 12:38:03 am

Title: cant load new OS on a new C drive after crash
Post by: knightrider56 on November 17, 2010, 12:38:03 am
I had my C drive crash and when I tried to reload xp pro sp2,    I get to a certain point and get the Blue Screen of Death. error occured and  windows has stopped to keep from damaging you machine,   yada yada yada.     So I went out and got a new  WD 500 gig replacement hd and a copy of Win XP  Pro x64  sp 2 and  tried to start from scratch.  I get to about the same spot and  bang   the   blue screen again.    Am I missing something ?   Do I need to reset the  bios  or something on my  mother   board  before I can go forward   or  is it something  else   stoping me.    cant be a virus.   new  HD and new   OS.     help  ???      ??? 

  i have the AMD 7 series utility dvd  it that will help       My set up si   a   AMD AM2/3 socket   board  that  supports  64 bit  os.    i have another  copy  of the  same  board  running     windows 7  in another machine.    in both  i am using    the  AMD AM2  tri-core  2.8Ghz  chip   non overclocked.
and the  board has   dual  bios..     I am running 4 gig of memory in the   machine that wont   let me   load   the OS.

any suggestions  please
Title: Re: cant load new OS on a new C drive after crash
Post by: Wonderwrench on November 17, 2010, 03:52:12 am
Definitely sounds like a hardware problem. Have you tested the memory to make sure its was not the cause of all your problems? Get Memtest here http://www.memtest.org/ Check to make sure your CPU is not overheating, fan spinning, heat sink properly mounted and free if dust? If you can rule out the above do you have another power supply you can try.

Bill
Title: Re: cant load new OS on a new C drive after crash
Post by: Dark Mantis on November 17, 2010, 09:35:43 am
You didn't explain what happened to the HDD and why the crash happened, but assuming that it was just a faulty hard drive I would advise you to try doing a full clearing of the CMOS and loading Optimised BIOS Defaults and see if if that clearsa the problem. If not I would suggest clearing the DMI data also.
Title: Re: cant load new OS on a new C drive after crash
Post by: knightrider56 on November 18, 2010, 12:36:23 am
You didn't explain what happened to the HDD and why the crash happened, but assuming that it was just a faulty hard drive I would advise you to try doing a full clearing of the CMOS and loading Optimised BIOS Defaults and see if if that clearsa the problem. If not I would suggest clearing the DMI data also.

Is clearing the  CMOS  fairly straight forward?    I  have never done this.  is there a  step by step  set of  instructions  somewhere  i can access so i dont  mess it up ?     Where do i find the DMI  data.    im not much of a software guy  but i can follow instructions.    Thanks..

Title: Re: cant load new OS on a new C drive after crash
Post by: CanUK on November 18, 2010, 07:03:07 am
I do not know about the CMOS, but you can also try downloading memtest86+ and boot from that.  Do a couple cycles to determine if you memory is bad.
Title: Re: cant load new OS on a new C drive after crash
Post by: absic on November 18, 2010, 08:12:23 am
Clearing CMOS is actually quite simple and you can find detailed steps of the procedure here: http://forum.giga-byte.co.uk/index.php/topic,2286.0.html
Title: Re: cant load new OS on a new C drive after crash
Post by: Dark Mantis on November 18, 2010, 01:27:06 pm
I do not know about the CMOS, but you can also try downloading memtest86+ and boot from that.  Do a couple cycles to determine if you memory is bad.

Just to add an addendum to what CanUK has said it is better to run Memtest86+ on the modules one stick at a time and do at least ten loops on each.
Title: Re: cant load new OS on a new C drive after crash
Post by: knightrider56 on November 18, 2010, 11:38:37 pm
I do not know about the CMOS, but you can also try downloading memtest86+ and boot from that.  Do a couple cycles to determine if you memory is bad.

Just to add an addendum to what CanUK has said it is better to run Memtest86+ on the modules one stick at a time and do at least ten loops on each.

hey thanks.   im  hoping its not my  cpu  going bad on me.   i will try  your suggestions tonight.     thanks again...