Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


About Porkey

  • Title
  • Birthday 1995-11-06

Profile Information

  • Gender
  • Location
    Canada, eh?
  • Interests
    PCs, game design, overclocking, electronics and mountain biking.


  • CPU
  • Motherboard
    ASRock 970M Pro3
  • RAM
    32GB (4x8) Corsair Dominator Platinum 1600MHz (@1333)
  • GPU
    GTX 980 Ti Classified, GTX 950
  • Case
    Corsair Obsidion 350D
  • Storage
    Kingston V300 120GB, Seagate FireCuda 2TB
  • PSU
    Corsair HX1000i
  • Display(s)
    Dynex 24" 1080p LCD TV
  • Cooling
  • Keyboard
    Razer Lycosa
  • Mouse
    Razer Diamondback 3G
  • Sound
    Razer Kraken 7.1 Chroma
  • Operating System
    Windows 7

Recent Profile Visitors

886 profile views
  1. Monero benefits WAY more from CPU threads now. After it switched algos back in November, it seems like it's mostly a CPU-based coin now. From my poking around, it looks like it wasn't a "small" comeback. Each thread on my 8370 is able to match or exceed the hashrate of my 980 Ti.
  2. So I just now found out that my machine was somehow "stolen" by another team and has been submitting work units for the team "STUDIO Mia" despite me specifically selecting the LinusTechTips team. And I'm pissed.
  3. Sorry, what do we do for the WCG Profile field? The provided example link for your profile returns an error, and I'm seeing there are issues with BOINC stats reporting with stats sites. Edit: Nevermind, did two minutes of reading and found out that you need to go into your profile settings on the WCG website, and enable data sharing or your stats will not be visible on the WCG site OR boincstats. I think this will solve the problem for people earlier in the thread having trouble with boincstats. https://boincstats.com/en/forum/8/12112
  4. It's looking like we were both right, Dario. When my server didn't freeze while testing my Dominators, it passed with no errors. My FX-8370 tested my server's 4x2GB sticks of ram and ended up with 4 errors after one run. I then swapped my FX-8370 out for my old Phenom II x6 1045t, and it did four passes of memtest on my server's RAM with no errors. I've now put my whole kit of Dominators back into my rig (lowering speed and timings to stay within the Phenom's even lower capabilities). The Phenom has so far not had any errors, whereas the FX chip would instantly throw hundreds of errors and then freeze, no matter what. I suspected the CPU from the start, but I think I'll be looking for a real motherboard soon either way. I'm still going to go through with all of the testing, just to be sure, as the Phenom is still only 33% into the first pass. I'll probably be back with more updates later today.
  5. Things have just gotten weirder. I've been experimenting with memtest86 and memtest86+ on both my machine and my server. I've been testing two sticks at a time in my server with the version of memtest86 that comes with unRAID (5.01 I believe). I have a dedicated memtest USB drive with version 4 and a version 7 (I think) that runs in UEFI mode. I've experimented with the core options; setting memtest to use all cores, round robin, sequential, and single-core modes. Setting memtest to use all cores on the server eventually causes it to freeze. Sequential, round robin and single core all seem to pass with no errors. Setting memtest to use anything other than single core in either version of memtest on my machine causes it to either reboot instantly, or eventually freeze. I am currently running the last of my tests on the first two sticks of my Dominators in the server, which have had no errors so far with sequential mode. I am testing one of the server's 2GB generic sticks in my main machine, and it has done two full passes with no errors.
  6. The kit of RAM worked well initially; I'm pretty sure I tested it in both my rig and the server (known good for memory) using memtest and a few other tools. Neither my server or my main rig can run the ram at 1600MHz, but everything from my old OC settings of ~1400MHz and below turned up no errors. I don't understand how the motherboard traces or memory controller could become damaged so suddenly like this. The motherboard is likely out of warranty, but should I try talking to ASRock anyway, seeing as this board always seemed iffy? Or should I suspect the CPU and talk with AMD?
  7. Now that you mention it, you could be right, but I was completely certain that FX chips had their northbridge (and memory controller) on the CPU? https://support.amd.com/en-us/kb-articles/Pages/ddr3memoryfrequencyguide.aspx#controller
  8. It seems like there's always something critically wrong with my system, no matter how I run it. Last year it was a faulty kit of RAM. A few months ago I was dealing with a dying H100i, which I sent in for RMA. Now, as of a few days ago, my computer has gotten much less stable. I keep waking up to find my computer at the desktop, having restarted on its own not long after I went to bed. I come home from work to find it restarted on its own right around the time I walked in the door. What is happening is the computer is not just "restarting" on its own; it is bluescreening. To be completely honest, I've been experiencing random BSODs since I rebuilt my current PC with a new motherboard (ASRock 970M PRO3), but I always chalked it up to just being "random" as I do things to my Windows installation that would warrant an occasional BSOD. Over the past few months I noticed BSODs becoming more frequent than I would expect. Oddly, they were all memory related errors. It's fuzzy in my own memory, but usually it would have to do with a driver or program trying to access memory that it isn't allowed to. Now in the past few days the BSODs have gotten really out of hand, to the point where I had my computer bluescreen four or five times in the space of 30 minutes before I had to leave for work. Then I got it up and running again, only to come home to find out that the computer had lasted about 4 hours before bluescreening again. Sometimes the PC can go all night being left alone without a BSOD. Sometimes it will BSOD within 10 minutes of being restarted. This sounded like another RAM-related issue, so I loaded up Prime95 and went to bed last night. Needless to say, that didn't go so well, as I came back to a blank desktop again today. Checking the log, Prime95 completed all of the tests successfully until the computer magically crashed. Now I've tried two separate versions of Memtest86, and the test is freezing early into the test. As I've written this post on my server VM, I've been fidgeting with it and I'm not sure if it really is a RAM problem. I also suspect both the motherboard and the CPU itself. Is there anyone out there who is familiar with odd behavior of AMD's crappy hardware?
  9. Alright, so I've noticed some odd behavior with my PC over the past few months... Long story short, I've got an FX 8370 which seems to need extremely high voltage to sustain an (apparently almost) stable 4.5GHz. The CPU thermal throttles when under heavy load, which I considered pretty normal because I have to have almost 1.5v set in the UEFI to (almost) properly sustain 4.5GHz on all cores. But, after having another system lock up, I was just messing around with the system and booted it up at 1.35v (+50mV offset, really 1.4v), at 4.2GHz (NB and NB-voltage still at OC levels). It still throttled in Prime95, AVX disabled. As in the title, I'm running an H100i (the original H100i from around 2012 or so.), and it is about three years old. I thought this was kind of weird, because back in its day, the H100i was considered pretty capable, and I thought it should be more than capable of handling a very light overclock at only 1.4v. I did do some quick testing at stock speed (roughly; just under due to bus OC), stock voltage, and there was no throttling, but the CPU die temp reached 64C, and if I recall, the CPU socket temp went up to either 70C or 76C, I can't remember. I used to think it was the motherboard/CPU socket overheating and throttling the CPU, but over the past few weeks I checked AIDA64 while torturing my system with work, and saw a socket temp in the mid 80s, while not throttling. Even though the motherboard I'm using is actual shit, I am fairly confident that it's not the VRMs causing me to throttle (for now). 64C under load at stock speed and voltage is way too high for these things. Remember you're not really supposed to go over 61. Using Arctic Silver 5, I have repasted a few times, and I still end up with temps like these. Do you guys think it's time I look into replacing my H100i? My OC settings: My system specs: Last minute edit: it still throttles with the H100i's stock fans on full speed.
  10. I like, big, butts and I cannot lie. (I like bulky high-end laptops like this, just as long as they don't look too much like a brick)
  11. Remember HighLANder? I would happily trek up a mountain with a fully decked out version of this machine if it meant I could own it.
  12. I'd definitely want the new Blade (the first laptop). I'd have no interest in the second laptop whatsoever, because the only games I play DO NOT handle scaling well at all. Not only that, but did I hear that the second laptop (the artist's machine) didn't have dedicated graphics at all? Which means you're using the Intel integrated "graphics" chip? I used Intel graphics once before. Never again.
  13. Yeah sorry for the wall of text. As I said in my long post; I had been planning on getting a good PSU for a while now. It's just that my whole system has gone to hell at the moment.
  14. Hello LTT forum. Today I am faced with a particularly frustrating issue. Recently (about a week ago) I replaced my motherboard and CPU. Before the upgrade, I was using an ASUS M24N68-AM SE2, with a Phenom X4 9500 overclocked to 2.5GHz, with 4GB of DDR RAM. I have upgraded to an MSI H77MA-G43 with a Xeon E3-1225, with four 2GB sticks of DDR3. Since the upgrade, I have been considering a power supply upgrade, as I am running a CX430M to support my system, and my graphocs card was recently upgraded to a GTX 950. Knowing that I was pushing my PSU to the edge with my last few upgrades, I had neen taking it easy on my system since the MB upgrade. I was trying not to put too much load on both the CPU and GPU, save for playing a few games (namely Blade and Soul and Mabinogi). I leave my computer turned on 24/7, and I leave my system to run (GPU-only) Folding@Home when I go to sleep. Yesterday, I woke up to find that my computer had restarted itself at some point throughout the night. Okay, so no more folding until I get a better PSU. I used my computer as usual throughout the day, and at some point later in the day, I noticed that I was putting a lot of strain on the system. I was playing Blade & Soul when I remembered that I had something to check real quick in Mabinogi. I left BnS running and opened Mabi, and while I waited for Mabi to start up, I started watching YouTube videos in Chrome. At some point I checked Task Manager to see constant 100% CPU usage, all of my RAM being used, and I knew that my GPU had to be at 100% load as well. Just as I went to close BnS, the computer shut down and restarted on its own. Woah, okay, so I know why that happened. From now on, only one thing open at a time. One. At. A. Time. I loaded Mabinogi back up again as soon as the computer restarted. I got into the game and started playing normally, until 10 minutes later, the system shut down and rebooted again on its own. This time, Mabinogi was the only thing that I had running. The game is SINGLE-threaded ONLY, so it could only have put 25-30% worth of CPU load on the system at a time. Usually my GPU gets loaded up tp 30-40% while playing Mabinogi. So, when the system restarted this time, it started to seem pretty strange. I Iet the system reboot on its own again, and gave it a minute or two to see if it would restart on its own again. The system sat at the Windows desktop for a while and didn't restart. Since the system had restarted under low load, I figured maybe the PSU had just gotten too hot when it restarted the first time, and was still cooling down the second time it ended up restarting. I figured that I'd give it one more go at Mabinogi, now that the system seems to have "cooled down" and hadn't restarted from sitting at the Windows desktop. Another 10 or so minutes of gameplay, and the system shut down again. At this point, I called it a night and shut the system down. I switched the power switch on the PSU to "off" and went to bed. 5 hours later, I come back to start troubleshooting. The system turns on fine, and works for about half an hour before Windows bluescreens. The cause of the blue screen was apparently my Razer Diamondback 3G's driver. Okay, now this is getting really weird. That driver has never given me problems in the 5 years that I've owned the mouse. Okay, so I uninstall the mouse drivers, and then reinstall them. Reboot. Now, Windows is failing to boot at all. A few seconds after the Windows loading screen comes up, the OS bluesreens and instantly goes back to POSTing. I spent a considerable amount of time trying to get any information from the bluescreen because each time the system bluescreened, the blue screen itself was only shown for less than 0.1 of a second. Apparently the bluescreen error message that I was getting was 0x0000007B (I think. I will re-check my notes after posting this). It was an error message that apparently meant "Boot device is unaccessible." Okay, so I do some Googling and apparently this new bluescreen can be caused by a lot of things; a corrupt MBR, SATA controller mode set tp IDE and not AHCI, or a boot sector virus... I ended up downloading the Windows Defender Offline tool and creating a bootable Windows Defender USB stick that's apparently supposed to scan my system for boot sector viruses. At first the WDO tool refused to scan my system at all, but after a few reboots and retries, the tool started scanning. Since then I've had the tool freeze on me once after an hour of scanning, and the system has yet again randomly shut down on me twice during a scan. As I type this post up on my almost dead phone, my system is upstairs trying to complete yet another scan. I have removed my GPU from the system to take as much load off of the skitzo PSU as possible. Since my forst attempt at using WDO tonscan my system, I have tried again to boot into Windows. Now, the system just restarts any time I try to boot from my C drive. No bluescreens; the system just instantly goes back to the POST screen. I apologise if this post is unformatted, cluttered or etc. I have hastily typed as much info as I can on my dying phone. To leave off; my current full system specs are as follows; CPU: Xeon E3-1225 CPU cooler: H100i RAM: 4x2GB generic DDR3 GPU: GTX 950 (currently removed from system) Storage: Kingston SSDNow v300 120GB PSU: Corsair CX430M Case: Corsair 350D Fans: One 140 and one 120mm front intake Before my Windows install comepletely died, I tried safe mode, system repair, sfc /scannow, last known good configuration; NOTHING worked. If anyone has any idea what could be going on, your input would be much appreciated.
  15. You won't have a Local Area Connection in your Network and Sharing Center if you're not using a wired connection. If you're using a wireless connection, it will say something different. The spot that you click on will still be the same, though. I believe it just says "Wireless Network Connection" if you are connected wirelessly. I've blurred some things out in my screenshots. Again, I'm not an expert with networking, and the stuff that I've blurred out isn't really too sensitive; I just preferred to keep my computer name and some other things specific to my computer, to myself.