Registered User
  • Content count

  • Joined

  • Last visited


About Folterknecht

  • Rank
    Plays Forums More Than Tanks

Profile Information

  • Gender
  • Location
    Where the beer is good
  • Server

Recent Profile Visitors

27,614 profile views
  1. It has - for the worse. I don't know how long you are playing, but around the time the french were introduced (4th tree - after they toned them down a little) you had at least in some tiers (looking at my favorite t8) a somewhat decent balance, which made playing them a joy. Sure it wasn't perfect in 2012 but "no" prem ammo in randoms, armor that meaned something without overbuffed fails, more open maps, made playing T32 vs. IS3 vs KT a real joy and the mediums even with 175 - 200mm pen at the same tier also were relevant.
  2. Reset (manually???) or loaded "Optimized Defaults"?
  3. Nah - you might miss something there (general information) With OC there are 2(3) states where things can go wrong Full load - insufficiant "max" voltage, where either dialed in voltage is to low or Vdrop to high (->LLC) load change (go from from idle/medium to full load). Changing speeds in a processor is not like flipping a switch when it comes to voltage. The voltage always has a horizontal component when you look at it on a oscilloscope. It's not binary. Where Prime (blend - full run) usually shines is full load testing and going from min to max load to some degree. The steps in between - when they make trouble - usually need a small nodge in secondary voltages or/and Vcore or they occur at/near the limit of the CPU. With what you are describing (voltages + speeds applied to your CPU model and the circumstances) I get the hunch, that something elsed might be off. That 's why I'm advocating eleminating broader areas first here (RAM, OC in general). Especially eliminating the RAM is a good and easy to apply measure (Memtest from USB over night) nearly every time the PC acts up.
  4. No, he isn't. I havn't played WoT in ages, but from past experience coming back after several months I still got around 2000 WN8 in the first days while playing horribly. Around 2000 WN8 is just getting the basics right (without HEAT spam and playing solo).
  5. Hmm - go into your BIOS and save your current settings in a profile. After that load "Optimized Defaults", adjust boot order and other things you need, "Save&Exit". That way you 'll see if the issues are OC related or not.
  6. Agree - that could have been anything from a stray cosmic particle to an external USB device acting up. See above - and while you re at it you can check your SSD/HDDs for S.M.A.R.T. errors (though that has nothing to do - probably - with the issue). Checking that now and then can save you a lot of trouble.
  8. Keep XMP disabled (for now), just make sure the RAM isnt running above 2133 or 2400 MHz (1066 or 1200) and timing arnt below CL15 And please Memtest86+ for RAM testing
  9. Enough of this 1.5V nonsense - lets get something done here. @thegeek2 1) Do you find the following errors in your event manager " WHEA Loggers ... Error Type: „Internal parity error“ ? 2) Are you running "Auto Voltages" on VCore, QPI, VTT ... or manually set to certain values? 3) What RAM are you using? XMP??? Did you test your RAM when setting up your OC???? - suggestion - let Memtest run from an USB stick over night with your current settings (testing RAM within the OS is BS). That way we can start to narrow it down.
  10. @thegeek2 Please upload a screenshot where you clicked on the error in the event viewer that was directly before the PC crashed. And I agree with Blackadder - 15 min Prime is a joke. Only good enough to check temps with "Prime small FFTs" for air coolers. What Prime test were you running?
  11. 1) He needs a new PSU, doesnt matter if he buys a 1060, 970 or 1080Ti -> might cause problems, if HP opted for proprietary connectors somewhere in the system 2) GPU clearance ... this being a of the shelf PC, room for GPUs is often very limited. Some of the bigger custom cards probably won't even fit into that case!
  12. [GUIDE] Forcing backup BIOS on Gigabyte motherboards. Ran into some problems today so I've decided to make a guide on how to kick-start the backup BIOS. Method #1: 1. Shut your PC down (if you're reading this guide, than your PC isn't working anyways) 2. Hold the power button until the PC starts and shuts down again 3. Press the power button again, your backup BIOS should kick in now and should re-flash the main BIOS if there's anything wrong with it. Method #2: 1. Shut your PC down 2. Hold the power AND the reset button for about 10 sec, than release. 3. Backup BIOS should kick in anytime soon now. Method #3: Had to use this one in order to get my 990FXA-D3 working again. Backup BIOS kicked in using method #2, but I was back to the good ol' no signal state once the procedure finished.. 1. Short out pins 1 and 6 on the main BIOS chip (pin #1 should be marked with a red dot or whatever) 2. Tell a friend (or a relative) of yours to press the power on button 3. Remove the ghetto-like jumper you're holding between pins 1 and 6 as soon as you hear a beep. 4. Backup BIOS should kick in again and everything will (hopefully) be fine. Uhm yeah, that's about it, I guess. P.S Please bare in mind that the 3rd method should only be used if you have the following options: Option #1 Follow my dumb advices. Option #2 RMA the board.
  13. How do you arrive at the conclusion that your CPU is fried? That usually is the last part that dies - obvious mishandling aside. Edit: Ofc it wouldnt post without RAM ... The purpose of that only was trying to brake the loop. Did you try only running with one stick in different slots?