A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » Processors » Overclocking AMD Processors
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Dead CPU? (Newb Alert)



 
 
Thread Tools Display Modes
  #1  
Old September 28th 03, 01:35 PM
-= debully =-
external usenet poster
 
Posts: n/a
Default Dead CPU? (Newb Alert)

Was having trouble getting my new bits to run at anything over 700Mhz, most
of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to keep it
all in sync.
Now it wont post at all and I fear I've fried the CPU?

TIA


  #2  
Old September 28th 03, 02:14 PM
Peter van der Goes
external usenet poster
 
Posts: n/a
Default


"-= debully =-" wrote in message
.. .
Was having trouble getting my new bits to run at anything over 700Mhz,

most
of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to keep

it
all in sync.
Now it wont post at all and I fear I've fried the CPU?

TIA


Oh, you'll need to get you motherboard manual and read up on resetting your
CMOS to restore BIOS defaults, so your PC will boot again. Be sure to remove
*all* power from your PC when you do this.


  #3  
Old September 28th 03, 02:15 PM
Peter van der Goes
external usenet poster
 
Posts: n/a
Default


"-= debully =-" wrote in message
.. .
Was having trouble getting my new bits to run at anything over 700Mhz,

most
of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to keep

it
all in sync.
Now it wont post at all and I fear I've fried the CPU?

TIA


You have PC2700 RAM, not PC3200. PC2700 memory is spec'd to run at 166MHz
(333 DDR). You need PC3200 to run at 200MHz (400 DDR). Set the memory speed
back to 166MHz.
Let the CPU defaults take effect. Your Barton defaults to 11x166, so use
defaults until you are *sure* your system is operating properly.
I won't go into how wrong 18x100 is, and why. I do suggest you do a lot more
reading before attempting any more overclocking.


  #4  
Old September 28th 03, 03:10 PM
Ben Pope
external usenet poster
 
Posts: n/a
Default

-= debully =- wrote:
Was having trouble getting my new bits to run at anything over 700Mhz,
most of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to keep
it all in sync.


Why 18*100?

The defaults are 11*166MHz

And since when does 100=200?

And since when do you expect your 166MHz rated memory run at 200MHz?

Now it wont post at all and I fear I've fried the CPU?


I'm not surprised.

Clear cmos.

Set the CPU to 166MHz * 11

Memory at 100% and the rest of the timings appropriately.

Better still, let everything set itself to the default values instead of
thinking you know better.

Ben
--
I'm not just a number. To many, I'm known as a String...


  #5  
Old September 28th 03, 04:25 PM
-= debully =-
external usenet poster
 
Posts: n/a
Default


"-= debully =-" wrote in message
.. .
Was having trouble getting my new bits to run at anything over 700Mhz,

most
of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to keep

it
all in sync.
Now it wont post at all and I fear I've fried the CPU?

TIA



Yup its fried...resetting CMOS did nowt.
Went out and got another CPU (XP2000) and now everything's running as it
should - even with memory at 333.

I think that the Barton 2500 and the a7v8x-x have issues.


  #6  
Old September 28th 03, 04:46 PM
Bugman
external usenet poster
 
Posts: n/a
Default


"-=3D debully =3D-" wrote in message =
.. .
=20
"-=3D debully =3D-" wrote in message
.. .
Was having trouble getting my new bits to run at anything over =

700Mhz,
most
of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to =

keep
it
all in sync.
Now it wont post at all and I fear I've fried the CPU?

TIA


=20
Yup its fried...resetting CMOS did nowt.
Went out and got another CPU (XP2000) and now everything's running as =

it
should - even with memory at 333.
=20
I think that the Barton 2500 and the a7v8x-x have issues.
=20

I think it had issues with you trying to run it with those settings.
  #7  
Old September 28th 03, 05:07 PM
Peter van der Goes
external usenet poster
 
Posts: n/a
Default


"-= debully =-" wrote in message
.. .

"-= debully =-" wrote in message
.. .
Yup its fried...resetting CMOS did nowt.
Went out and got another CPU (XP2000) and now everything's running as it
should - even with memory at 333.

I think that the Barton 2500 and the a7v8x-x have issues.


No, you have knowledge issues. I have to wonder if that XP2500+ is really
fried. Care to describe *exactly* what steps you took to clear cmos?
Your comment "even with memory at 333" reveals a lack of understanding.
Earlier, you reported trying to run your PC2700 memory at 200MHz (400 DDR),
and were told that your memory is rated for 166MHz (333 DDR). Now that
you're running it in spec, of course it works!
The Barton has no issues with your motherboard. You may want to put in the
hands of someone experienced with AMD for a test before you throw it away.


  #8  
Old September 28th 03, 07:47 PM
Ben Pope
external usenet poster
 
Posts: n/a
Default

-= debully =- wrote:
Yup its fried...resetting CMOS did nowt.
Went out and got another CPU (XP2000) and now everything's running as it
should - even with memory at 333.


New CPU - default settings... boots up again.

Try the old CPU - I suspect it will work.

I think that the Barton 2500 and the a7v8x-x have issues.



Nah. Not as a rule.

Ben
--
I'm not just a number. To many, I'm known as a String...


  #9  
Old September 29th 03, 12:19 AM
rstlne
external usenet poster
 
Posts: n/a
Default

Yup its fried...resetting CMOS did nowt.
Went out and got another CPU (XP2000) and now everything's running as it
should - even with memory at 333.

I think that the Barton 2500 and the a7v8x-x have issues.


Yea
They have issues with newbies who try to make them run too fast, so they
decided to work together, and **** you out of 90 quid
heh



  #10  
Old September 29th 03, 05:37 AM
callsignviper
external usenet poster
 
Posts: n/a
Default


"-= debully =-" wrote in message
.. .
Was having trouble getting my new bits to run at anything over 700Mhz,

most
of the time its wouldn't post.

Asus A7v8x-x (bios v6)
Barton xp2500
Crucial 2700 512Mb cl 2.5

Thought I'd try settings of 18/100 clock multiplier and 200memory to keep

it
all in sync.
Now it wont post at all and I fear I've fried the CPU?



R.......T....F.....M!!!!!

Read The Fine Manual

Note: I am definitely NOT thinking Fine!


--
callsignviper

The truth is out there. You just have to look in the right places and ask
the right questions.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Dead PSU under warrenty, should I ship the mb? James General 7 September 20th 04 01:56 PM
Dead Computer BrianXZ General 13 August 2nd 04 09:21 AM
current/voltage peak: HD & PD drive dead ~misfit~ General 7 May 15th 04 08:21 PM
Wanted: Dead Hard Drives Captain Overclocking AMD Processors 0 December 19th 03 08:20 PM


All times are GMT +1. The time now is 09:03 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.