Pages: 1 2

 

2007-07-25 08:31:01
max
Vela Incident
+1,652|7041|NYC / Hamburg

theknuck wrote:

max wrote:

theknuck wrote:


it ran fine at 2.4.  then i tried 2.5 and bam, stopped dead in tracks.   i'm thinking my ram is holding me back.
drop the divider. Keep your ram running close to 200 MHz

Try this guide to help OCing.
what is your divider at and what kind of ram do you have and what are your settings?
up to 250HTTx10 multi I run 1:1, after that I drop it to 5:6 (DDR-333) which would give me headroom to about 3.2 GHz. I have DDR-500 (250MHz) memory though which you can actually push up into 265MHz  terrain.

full specs in sig
once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot  xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.
2007-07-26 20:04:50
{C4C}Phoenix
Member
+8|6838

theknuck wrote:

Ha, thanks for all the help fellas.  even though i'm ok on the homefront, a simple reformat is all i needed.  if someone could tell me how oc'ing your computer has any affect on your os then i'm all ears.  either way i'm up an and running again.  i think i'll leave the oc'ing to the pros.  besides, i'll be upgrading soon.  i'll be leaving karma in a minute.
What probably happened was when you OC'd your PC something "might" (and I say MIGHT!!!!) have knocked out a sector on your Hard Drive.  This is vital because "MAYBE" that sector contained information needed for the registry to load up.  That's why the BSOD at startup.  And also Safe Mode wouldn't work. 

BSOD are alot of time due to hardware failure calls usually the Hard Drive but also could be memory.  I knew it was not any of these things because you stated that everything looked fine in the BIOS screen (which came up clean).  If there was a problem with hardware you would have seen something wrong in the BIOS.

I am a Level 2 computer tech for a major company and see these types of issues all the time.  Sometimes Windows just goes crazy (thanks for the job Bill) and knocks sectors out (usually due to heat issues).

I've seen plenty of loads go bad in 7 years and nothing is wrong with the hardware or drivers.  A reload usually fixed the issue.   

I'm glad my advice help because I usually don't post tech help on forum sites (unless it's within my clan) because there is always some joker that thinks he knows everything about everything in regards to PC's and trys to belittle people that are just trying to help.
2007-07-29 06:12:46
Scorpion0x17
can detect anyone's visible post count...
+691|7239|Cambridge (UK)

{C4C}Phoenix wrote:

theknuck wrote:

Ha, thanks for all the help fellas.  even though i'm ok on the homefront, a simple reformat is all i needed.  if someone could tell me how oc'ing your computer has any affect on your os then i'm all ears.  either way i'm up an and running again.  i think i'll leave the oc'ing to the pros.  besides, i'll be upgrading soon.  i'll be leaving karma in a minute.
What probably happened was when you OC'd your PC something "might" (and I say MIGHT!!!!) have knocked out a sector on your Hard Drive.  This is vital because "MAYBE" that sector contained information needed for the registry to load up.  That's why the BSOD at startup.  And also Safe Mode wouldn't work. 

BSOD are alot of time due to hardware failure calls usually the Hard Drive but also could be memory.  I knew it was not any of these things because you stated that everything looked fine in the BIOS screen (which came up clean).  If there was a problem with hardware you would have seen something wrong in the BIOS.

I am a Level 2 computer tech for a major company and see these types of issues all the time.  Sometimes Windows just goes crazy (thanks for the job Bill) and knocks sectors out (usually due to heat issues).

I've seen plenty of loads go bad in 7 years and nothing is wrong with the hardware or drivers.  A reload usually fixed the issue.   

I'm glad my advice help because I usually don't post tech help on forum sites (unless it's within my clan) because there is always some joker that thinks he knows everything about everything in regards to PC's and trys to belittle people that are just trying to help.
Indeed. Good call. I personally would have put money on it being hardware, but, if you hadn't've already suggested it, it was next up on my list, once I'd ascertained that the 'swap-out-the-potentially-faulty-component-and-see' option wasn't available.

 

Pages: 1 2

Board footer

Privacy Policy - © 2025 Jeff Minard