Jump to content

TRWeiss1

Members
  • Posts

    120
  • Joined

  • Last visited

About TRWeiss1

  • Birthday 04/11/1982

Gaming

  • Xfire
    TRWeiss1

Profile Information

  • Gender
    Male
  • Location
    NY
  • Interests
    Cars and Computers

TRWeiss1's Achievements

Newbie

Newbie (1/14)

  1. Some more details... CPU/NB Freq - 2424 HT Link Speed - 2424 CPU Spread Spectrum - Auto EPU Power Saving Mode - Disabled (all power saving crap disabled including APM) DRAM Timing/Driving Control - Left alone CPU Load Line Calibration - High (Have Xtreme, but haven't tried that) CPU/NB Load Line Calibration - High CPU Current Capability - Auto CPU/NB Current Capability - Auto CPU Power Phase Control - Extreme CPU Voltage Frequency - Auto CPU Power Duty Control - T. Probe Thermal CPU Manual Voltage - 1.48v CPU/NB Manual Voltage - 1.30v CPU VDDA Voltage - 2.50v DRAM Voltage - 1.65v NB Voltage - 1.20v NB HT Voltage - 1.30v MB 1.8v Voltage - 1.80v
  2. Ok, so I'm wondering what are the most common causes of core failures (0, 1, 2, etc) on OCCT? I'm running an FX-8350 @ 4.86 with a Vcore of 1.48v and a TT Water 2.0 Pro, and it'll hit core errors within 2 minutes of OCCT. I tried bringing the core voltage up to 1.50v, but I still get the same errors (and I can't see needing more voltage than that for < 5GHz). Mobo is an ASUS M5A99X, and I can provide any/all other settings. What am I missing here? I'd really like to get the system stable at this clock speed, then take it over 5.0 since I KNOW it has the ability. Any intelligent input would be much appreciated! Thanks. See next post for more details.
  3. Tbh, me neither... But it does make sense, and I thought it was a bit odd that it was reporting exactly half of what it was rated for.
  4. From Thermaltake... "Hello, Thank you for contacting Thermaltake Customer Service. The reason why you are seeing a lower RPM reading is because of the design of the pump coinciding with the sensors of the motherboard. All motherboard fan headers are capable of reading single pulse signals for communication in order to monitor speed. The pump in the water 2.0 unit uses a dual pulse signal which means the motherboard will report the true RPM reading in half. So your pump is actually maxing out at 3000RPM if the reading is 1500RPM." Phew, looks like I'm fine.
  5. So as the title states, I'm wondering why my new TT Water 2.0 Pro is only running at 1450 RPMs. It doesn't matter which fan connector I plug it into on the mobo (right now have it connected to CPU_Fan), or whether it's connected directly to the PSU. I have an ASUS M5A99X mobo. I've not updated the BIOS because it tells me its an "invalid ROM file" when I try to update it, so maybe the original BIOS is causing the issue. Help on flashing that would be much appreciated as well, if anyone has experience with this board. But yeah, from everything I've read the Water 2.0 Pro pump is supposed to run at 2800 RPMs, not 1450. And naturally I would assume that this is affecting cooling. Please help! Thanks in advance!
  6. ^Exactly, and thank you for confirming that.
  7. Erm.... There's absolutely NO WAY the following pic could be correct, right? Let me preface this pic with the fact that this chip has been running for days now, nonstop, and I've NEVER seen it get over 61 deg C... Then a random spike up past 120?! Gotta be a false reading, no? There's no way the chip would spike that high at 1.48v, then come back down that quick, would it?? I'm thinking (or hoping) speedfan had a moment where it lost its marbles, or just got bad data from the temperature sensor... Reference => http://i291.photobucket.com/albums/ll302/TRWeiss1/Spike.jpg A larger pic. => http://i291.photobucket.com/albums/ll302/TRWeiss1/Spike_Large.jpg
  8. Haha yep, I think you did! My question regarding the memory was not bc I *wanted* to push it faster, but rather do I *need* to in order to achieve a stable OC in this scenario. So far no crashing @ 1.50v Vcore, but we'll see what happens in time. Maybe the cause of the crashing this entire time was bc my Vcore was too low. I was merely going based on what others are running theirs at, and what they were using for Vcore... Of course I understand that every system is different, and perhaps my chip needs just a touch more voltage. It may also be worth noting that whatever I set my chip to in the BIOS, I see .02v less in Windows. For example, even though I'm setting my Vcore to 1.50v, the chip is actually getting 1.48v. Don't know if this much matters, but just pointing it out. So I suppose what I SHOULD be telling you is that I have it set to 1.50v in BIOS, but it's *truly* only running on 1.48v according to CPU-Z and the ASUS OC utility. Max temp I've seen thus far is 59 deg C, although it's hovering right around 57/58.
  9. Thanks red. I did just get another lock up. No BSOD, just a total system freeze. Mobo temp was @ 34 deg C, CPU temp @ 55 deg C. I bumped up my Vcore to 1.50v, and we'll see what it does there. Furthermore, I noticed that it was running my RAM at 1333, even though the RAM is rated at 1866. I bumped it up to 1866, and up from 1.5v to 1.6v. Does this sound reasonable? I'm not sure how DDR3 is rated, but I know that DDR2-xxx ran at half the speed it was rated for, and the number xxx was its max theoretical speed. Having said that, Idk if my RAM's max theoretical speed is 1866, or if it could (or should) go higher with this overclock. Please advise. Lastly, what would be the highest temp you'd be comfortable seeing on your CPU? I've read that 62 is the hottest you'd want to see for the 8350...
  10. Oh, one last thing regarding Vcore... If set too low, will too low of a Vcore voltage ONLY prevent getting into Windows, or can/will it cause lock ups once gaming? The reason I ask is because I can get into Windows with a lower Vcore than I'm running right now, and am wondering if I should set it lower. Obviously you want the lowest voltage to create the least amount of heat, but enough to have stability. I'm at 1.48v right now, but can get into Windows @ 1.46v. Should I keep going down, or call it good since I seem to have stability right now?
  11. Roger that. Thanks again! I'll let you know if I hit anymore issues.
  12. Thanks Red... I must have been reading your mind, because shortly after I made that post I thought about it, then put my NB @ 2400 w/ 1.3v. I also put my HT at 2400 as well... Think I should set it to 2600? No more lock ups with the changes I made, and we did a solid 2 hrs of gaming. I wonder if that's what it was? I know it's absolutely possible, considering you generally need to run the NB faster when you OC the CPU... Always hard to know if you nailed the problem though, since lock ups can be infrequent and sporadic. I will keep you posted! Thanks again for the help, I really appreciate it.
  13. Ok guys, another question. How fast should I be running my NB, and at what voltage? Also, what about the HT? Right now I'm on 202 x 24 multi (4.86 GHz) w/ 1.48v for Vcore. I get random lock ups after about 45 minutes of gaming (or so), and I'm pretty positive they don't have to do with heat. CPU is sitting around 52-54 deg C while gaming, and mobo temp doesn't go over 34 deg C (according to the ASUS utility, although I'm not sure which sensor its getting this data from). Furthermore, I just got my first BSOD .... Driver_IRQL_NOT_LESS_OR_EQUAL. I'm guessing that's gotta be related to the OC, and wondered what was causing it. I doubt it's related to bad hardware or drivers, but I suppose it's possible. Any help would be appreciated. Thanks guys!
  14. ^^Those are EXCELLENT points guys, and very valid. My downstairs is EXTREMELY warm, as I run an air source heat pump (Mitsubishi Mr. Slim). I run it hard in the winter so that the heat makes its way upstairs, so the ambient temp is pretty warm downstairs... Probably 80 degrees, or even slightly higher. I did pull the water block, remove all the thermal paste, and carefully reapply AS5 to the processor. I even got curious and used ASUS' little "Autotune" utility, where they do the overclock for you. It put my system to 4.55GHz, which I know it's capable of more than that. I'm sure that utility is just playing it extremely safe, as to not fry anything. Now, here's the other thing I think about... OCCT is a nice "worst case scenario" tool, but it's not realistic. I mean really, WHEN are you going to have every core loaded down 99-100% for an extended period of time? More and more I'm considering a different approach. I'm thinking of just hooking up my other monitor, and having all of my temp graphs up while doing some hardcore gaming. Then, I can find out when/where everything plateaus... If I get a system crash, I'll investigate. However, if it turns out my system is 100% stable, nothing is getting into the danger zone as far as temps, and the CPU isn't throttling down, I don't really care if I can run OCCT. lol
×
×
  • Create New...