I would with a bit of c# code create a program to forward the files by mail to an anon mail of mine, or just have the program push the files to an anon file uploading service with a predefined name. For instance to http://www.tinyupload.com/ so it will be there anonymopusly, then u urself can go on the page and find it by searching on the predefined name you gave the file.
First try at least one pass of Memtest86+: http://memtest.org
If Memtest passes, next try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes, go ahead and run Prime95 by itself with logging (CPU stressing) and then Furmark by itself with logging (GPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes then do ONLY Prime95 for 10 minutes with logging then ONLY Furmark for 10 minutes with logging.
Try a quick stress test with HWiNFO logging: https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Also, can you give us more info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
The other tracks absolutely could interfere via side-chaining.
> Do you want me to share a reaper project file
A reaper project containing only what's necessary to reproduce the issue. Start by saving a copy of a the entire project (use copy media to project directory). Then go nuclear. Delete any track that's not relevant. Issue go away? Backup and find the cause.
Get it down to just the tracks that replicate it the problem, then delete everything but a portion of the track necessary to replicate the issue. Use file > 'clean project directory' to remove unnecessary bulk, zip entire folder, upload somewhere and share.
Download the latest driver for your video card from geforce.com and select Custom > Clean Installation during the install, then reboot.
If the problem persists try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
First: Verify your memory clocks in Windows (msinfo32.exe) and in the BIOS. For some reason Speccy is showing "398MHz" (800MHz) but I doubt that's right.
If everything OK there, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
The point here beyond stressing is to look at what information HWiNFO can gather during those 10 minutes about your system--temps, voltages, clocks, etc. Not just averages but patterns can tell us more about what may be going on.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Make sure your graphics driver is up-to-date from Nvidia's website, select Custom > Clean Installation on install. If everything is fine there, or the problem still occurs, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try some of the tips here: https://rtechsupport.org/kb/perf/
If none of them seem to solve the issue then follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
(Huh, the 2nd post today with this CPU and same problem.) AMD A10-5800K has known overheating problems partly due to its included iGPU, even if it's not being used, and has a relatively low max temp of around 75C. But we can try further troubleshooting. It also performs horribly for a Quad-Core, about a modern Core i3 level, so I would put that at the top of your list for upgrading.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Let's get more info. Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
> Also, it did this when I bought a second HDD as well, except it would shut off even while idling. It worked when I took it out.
This statement leads me to believe it's a hardware problem, possibly with the PSU on its 12V rails, as both a HDD and your GPU need power from the 12V.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
I know you said you already tested using both Prime95 and Furmark but can you please do so with both at once and HWiNFO logging the results? https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try first what /u/tboland1 suggested (DDU) and if that doesn't work, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Your Speccy link mentions that your Seagate 7200RPM HDD has a S.M.A.R.T. status of "Warning", probably because of possibly bad sectors on the drive. Download HDTune or HDTune Pro and verify the S.M.A.R.T. data. Any errors or warnings involving sectors is bad: http://www.hdtune.com/download.html Do an Error Scan (without Quick Scan checked) if you want more confirmation. If you use HDTune Pro then you can also click on "Speed Map" after the scan for a map of the drive's performance.
If everything seems fine with that HDD then you can further go on to stress-testing your CPU and GPU. Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes, go ahead and run Prime95 by itself with logging (CPU stressing) and then Furmark by itself with logging (GPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes, go ahead and run Prime95 by itself with logging (CPU stressing) and then Furmark by itself with logging (GPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Also, can you give us more info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Also, can you give us more info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Use the instructions here to setup HWiNFO logging, ignoring the parts about the actual stress testing (Prime95 and Furmark), instead running Warhammer and trying to recreate the issue: https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging: https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Also, can you give us more info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes during the stress test then try ONLY Prime95 for 10 minutes, then ONLY Furmark for 10 minutes.
$700 and they've been doing it since October. Damn. I'd feel bad if they weren't getting that A-list opener money. If someone who isn't you wanted to share it they might use tinyupload or uploadfiles.
Your log is a bit short to see too much.. I suggest taking it for a flight of at least 3-5 minutes. Try both hovering in place for a little bit and moving around some, yawing, etc. Then upload the entire log (just the zipped .txt will do) to some free service, such as http://www.tinyupload.com/
But as said below: Balancing props is the easiest and main way to improve vibrations.
Absolutely! If you upload the link to Dropbox of Google Drive if you have them, or FileDropper or TinyUpload (or really any other hosting service), you can PM me the link and I'll render it out for you.
Can you upload your System.xml file from rdr2 ? cause if you copy that and copy it inside the file the structure is fucked :P
Like upload here http://www.tinyupload.com/
Do you have a savegame file at the point you posted this message? I'd like to fix your problem by working it out in play. I can get back to you. Hopefully you don't have any mods so it will work in my unmodded game. You can use http://www.tinyupload.com/ to make the savegame file available.
Are you on PC?
If so, post links to your save and we can try to load them in-game, or inflate them. You can use something like TinyUpload if you don't have Google Drive, Dropbox, or whatever.
You can find PC saves for Steam in this folder:
C:\Users\%Username%\AppData\Local\Astro\Saved\SaveGames
You can find PC saves for Microsoft Store by running this in PowerShell:
explorer ((Get-ChildItem $env:LOCALAPPDATA\Packages\SystemEraSoftworks\SystemAppData\wgs\ -Recurse -Filter container.).FullName | Where-Object { Format-Hex $_ | Select-String '$.(\d.){4}' } | Split-Path)
I also made Astroneer Backup because I was sick of losing saves, too.
Those are really your only options. Setting width to 0% makes that track mono. Look for any other sends on the track and delete/mute them to see what I'm talking about.
If you're adamant that even with no other sends, a track with width 0% is still stereo, you can do the following:
Synth 1 is free, right?
Problem still occur?
> It’s not making sense to me either.
It's more that your behavior makes no sense. Don't spend hours replacing notes; find out what replacing the note is changing and fix that. It's not like a MIDI note can get "corrupted" and need to be replaced. The new note is different in some way. Check the CC lanes.
Feel free to post a Reaper project containing one of the pre-replacement MIDI files. They're small text files. You can post them here.
Look in the folder:
%AppData%\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config
You'll find a file called ModsConfig.xml.
​
Upload it here http://www.tinyupload.com/
Strip project down to just those tracks. Remove all VSTs not required to reproduce the problem. Replace non-native VSTs with Reaper-native VSTs.
This will leave you with a small, self-contained text file (.rpp) that reproduces the problem, which you can share here. That will make it several orders of magnitude for others to troubleshoot and/or to report a bug.
That's a million times easier than playing 20 questions to figure out how your project is setup.
hmm interesting... I have a few more guesses but I think the fastest thing would be if you could zip up 3 of the jpg images. The 1 that works and 2 that don't. You can upload the zip here and send the link it gives.
You can private message it to me if you prefer.
> I'm unaware of how to check the crash log but if there are steps I should follow I can check.
Your crash log will usually be located inside a compressed folder in %AppData%\XRay Engine\reports\ and will be named 'xray_<Yourname>.log'. Paste the last few lines of the latest one if you find it.
> what's the best way to do this?
Just upload the .sav file somewhere like http://www.tinyupload.com/ and paste the link here.
A very simple synth that comes with Reaper.
Save a copy of your project, then remove any third-party VSTs. Replace any synths with ReaSynth. If the problem goes away, you've learned something. If it doesn't. you'll have a tiny file (a few KB) while illustrates your problem. You can upload it somewhere and we can help you troubleshoot.
Hmm, maybe double check that there are no leading / trailing spaces in the filter you pasted into ublock so it looks like this.
If that doesn't work then save me a copy of the webpage (ctrl+s) and send it to me with something like http://www.tinyupload.com/.
I have Synth1. Just tried that. Can't reproduce it. When the envelope is created it has one node, set to the current value of the control, so there's no change.
If you want to strip the project down to just one track with that one VST on it, and share it (it's just MIDI data, so it should be just a few KB), I can see if I can reproduce it with your patch.
Yeah the 950 doesn't require extra power from the 12V rails but the 580 certainly does. The 950 only requires 19A while the 580 requires 28A. Now according to EVGA for the 100-w1-0500-kr your 12V should support up to 40A but 500W is also the minimum power requirements for the 580 so it could be pushing things depending on your other specs and if you overclock your CPU or not and such.
First go to AMD's website and download the latest ReLive drivers--even the beta ones--and install those and see if anything improves.
If updated drivers don't help try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
RAM will show up as 570MHz in many SPD reports because it's DDR--Double Data Rate--so really running at ~1140MHz. That's a weird RAM timing to be running at but it could be because of your overclocking. Verify with Speccy or CPU-Z on the SPD tab.
Open-World games are very taxxing on the CPU. Again the RAM isn't that big of a deal. And all the games you mentioned except Minecraft were designed to run as low as 30 FPS on consoles, so they can lag a bit without monster machines when you push them on PC. As for Minecraft, that runs horribly no matter what you do; though the Windows 10 version is a fair bit better than the original Java version (and the Windows 10 version is free if you paid for the original version and have Windows 10).
If you want more information of what's really being taxxed follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
This testing will give us detailed information on a variety of sensors in your system (not just temperature).
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Note - You may also try the new automated script in beta here: https://www.reddit.com/r/techsupport/comments/7azowy/testers_needed_fully_automated_hwinfo_logging/
You may also want to check your fans carefully while this stress testing is going on, even taking the side off.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Reset your BIOS back to factory defaults (no overclocking), with all cores enabled. Then try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Short answer: No, not really. It could be a software issue or it could be a hardware issue (yes, there are hardware issues that only show up with very specific behavior).
Download the latest graphics driver from geforce.com and select Custom > Clean Installation then reboot. See if the problem remains.
If it does, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Put the system through at least one pass of Memtest86+, preferably leaving it overnight: http://memtest.org (I know you said you swapped out RAM but this is is testing whether it can pass Memtest86+ and for how many passes)
If everything is good with Memtest86+ then try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test (which it sounds like it will), go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
What /u/MK2555GSFX said.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
With the GTX 760, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
From personal experience I can say that a heavily modded Bethsoft game can add serious strain / different strain on a system that even newer games may not do.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
First check you have the latest ReLive drivers from AMD's website. If everything is fine there, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try some tips here, especially the clean boot / startup items: https://rtechsupport.org/kb/perf/
If nothing seems to help, follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur (the more instances the better).
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Use AMD Overdrive to verify that all cores can burst to maximum frequency, also verifying thermal margin: http://www.tomshardware.com/faq/id-2122665/understanding-temperature-amd-cpus-apus.html
If one or more of the cores is "stuck" at a lower frequency, re-enable Cool'n'Quiet.
If everything otherwise seems OK, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try at least one pass of Memtest86+: http://memtest.org
If everything's OK there we can check your system near max load with a stress test and HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Hmm, let's try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Well again this is probably all normal, but let's investigate more about what type of load the system is under when this occurs. Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then fool around until the problem occurs.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
The PSU could be at fault. Try a quick stress test with HWiNFO logging (select "Sensors only") with only Prime95: https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Download the latest graphics drivers from geforce.com if you got them somewhere else. Install these using the option Custom > Clean Installation, then reboot. See if this improves anything.
If it doesn't follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Follow some of these tips, especially the ones about disabling startup items (including AV, etc.): https://rtechsupport.org/kb/perf/
If none of the tips seem to help let's do a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
If neither of those two seem to help then let's stress your CPU, RAM, GPU, and PSU all at once with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
(Note: I suspect your PSU. Let's see what the stress testing may show us about its ability to provide at max load.)
Try some of the tips here: https://rtechsupport.org/kb/perf/
If none of them seem to solve the issue then try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
First follow the tips here, especially the part about a "Clean Boot" (Disable Startup Items): https://rtechsupport.org/kb/perf/
If those tips don't seem to help follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your system? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
AMD A10-5800K has known overheating problems partly due to its included iGPU, even if it's not being used, and has a relatively low max temp of around 75C. But we can try further troubleshooting. It also performs horribly for a Quad-Core, about a modern Core i3 level, so I would put that at the top of your list for upgrading.
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Everything looks normal there. Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Download the latest drivers from geforce.com and select Custom > Clean Installation during install.
If the above doesn't seem to help, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Can you give the make & model of PSU?
How old is the video card?
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Follow these instructions to do HWiNFO logging, ignoring the parts about Prime95 and Furmark--just do the logging: https://rtechsupport.org/kb/hwinfo-logging/ and then play the game for long enough for the problem to occur.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Samsung's website and the manual I downloaded from there says your TV supports Motion Blur--check your manual (you can download it from Samsung).
Try either enabling the FPS counter in Steam if playing a Steam game or downloading MSI Afterburner and enabling the FPS counter there. Furthermore, let's also do HWiNFO logging at the same time. Follow these instructions to setup HWiNFO logging, ignoring the parts about the actual stress-testing programs (ignoring Prime95 and Furmark): https://rtechsupport.org/kb/hwinfo-logging/
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
First check the "reliability history" for any problems listed there, using Windows Search tool in Windows 10 or 8 (or from Settings).
Next try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
Try a "Clean Boot": https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
If the system still seems slow, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
First download the latest drivers for your graphics card from AMD's website. If that doesn't solve your problem:
Try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
Also, can you give us more detailed info on your hardware? Download Speccy from: https://www.piriform.com/speccy/download/portable — at the top of the Speccy window, go to File > Publish snapshot. Then, paste the link in your submission or in a comment reply.
What's your make & model of PSU?
Also, try a quick stress test with HWiNFO logging (select "Sensors only"): https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).
You can try stressing the system at max load to see if it'll shut off, logging the sensors in your system using HWiNFO: https://rtechsupport.org/kb/hwinfo-logging/
Make sure to check the temperatures in HWiNFO before doing any stress testing. The CPU and GPU shouldn't be above ~60C on idle.
If you need a place to upload the CSV file to share it with us you can use http://www.tinyupload.com/
If it crashes or reboots during the test, go ahead and run Furmark by itself with logging (GPU stressing) and then Prime95 by itself with logging (CPU stressing).