How to and Guides
Total Page:16
File Type:pdf, Size:1020Kb
How To and Guides Clean Installing Windows 10 Killer Network Drivers Running Memtest86+ HWiNFO - Full Guide How to Describe a Technical Problem DISM and SFC Reading HWiNFO logs Cleaning a Computer Making a System Dossier Making Windows installation media in Linux Clean Installing Windows 10 1. Create a bootable USB flash drive using the Media Creation Tool from Microsoft. This will also wipe any data stored on the USB flash drive. It is best to disconnect all storage disks except from the main (C Drive) disk “from the computer before installing Windows 10. 2. Boot into your USB that has the Windows 10 Media on it. You can do this by entering your systems' BIOS and change the BIOS boot order to have USB media as the first priority (this can usually be found under the boot tab), or simply look for the words "boot menu" when you see your BIOS boot screen, press the corresponding function key and choose the USB flash drive to boot from it. 3. Follow the steps on screen to install Windows 10. 4. Click Install now 5. Continue on until you hit the license key screen. Here you can either enter your license code or, if Windows has been installed to this computer before, click on the "I don't have a product key" link. 6. Continue on until you hit the “Which type of installation do you want?” screen. Click "Custom". 7. Click on each partition of the target drive and select delete. Once all the partitions are gone you will be left with unallocated space. At this point click next. 8. Windows will now install. 9. Once complete you will be facing the setup screen. Configure as you wish. You have successfully installed Windows 10. Killer Network Drivers Killer networking drivers and software are known to cause various issues. To troubleshoot follow these steps: 1. Download the universal drivers 2. Uninstall all Killer software such as the Killer Network Center 3. Install the universal drivers 4. Reboot Running Memtest86+ What is a Linux Live Session Linux is a great OS that has a major advantage when it comes to troubleshooting, it can be run from a USB flashdrive in a 'live' state without installing to a hard disk. This allows you to use a wide range of tools to manipulate the disks, data, and hardware of your computer/OS without worrying about anything running on it. Obtaining media r/Techsupport Rescue Media A Linux ISO has been made for r/Techsupport that has memtest86+ included in the environment. Download Source files for Debian live-build Official Memtest86+ V5.31b You may also use the official Memtest86+ ISO. Download Or the install tool for Windows. Download Creating bootable media This will require a USB that is at least the size of the ISO you downloaded. All methods of creating boot media are destructive and will WIPE the USB flasdrive or external disk. Windows 1. Download and run Rufus 2. Select “ISO Image” and then browse for the ISO image. 3. Select which flash drive you want to put the installer on. 4. Select the target system type MBR/BIOS Memtest can only be ran when booted as Legacy/MBR/BIOS 5. Click “Start” and wait for it to finish. MacOS 1. Download and run Etcher 2. Select your downloaded ISO 3. Select your target drive 4. Click "Flash" and wait for it to finish. Linux 1. Run lsblk to list all disks in your system, identify your flash drive by size. It will look something like /dev/sd[letter] Boot the live media 1. Press your 'Boot menu' key when you power on the machine to access your boot options. You may need to go through BIOS and change boot priority if you cannot find or hit the boot options key during boot. 2. Choose your USB 3. Once it boots select 'Try' or 'Live' Run Memtest86+ Both of these media need to be booted in Legacy/CSM mode. They will not work when loaded in UEFI mode rTechsupport Rescue Media If you booted the rTechSupport Rescue Media then you will be able to choose Memtest86+ on the welcome screen. Official Memtest86+ media If you used the official Memtest86+ media, it will boot straight into the test. Results Let the test run for 8 passes, most likely over night, any errors means means you have a bad RAM stick or DIMM (RAM slot). If you see any errors early you can end the test there and start narrowing it down to which stick/slot. If you have a failure then test each stick individually, and in different slots to isolate the failure to a stick or slot. HWiNFO - Full Guide To start troubleshooting using HWiNFO, follow this guide. It will walk you though how to setup logging and stress testing. All 3 programs are required for this test. None are optional. 1. Download HWiNFO from here All versions will work the same. You won't have to install the portable version. 2. Download Prime95 from here (64-bit) or here (32-bit) If you are using chrome, you may need to copy-paste these links into a new tab. 3. Download Furmark from here 4. Start HWiNFO and launch it in sensors only mode If you get a warning about an emedded EC sensor, just click "Do not monitor" 5. In the sensors only mode window, go to settings and set the global polling frequency to 250 ms and press ok. 6. Start the logging process by clicking the green + with the paper icon and save a csv file to a location. 7. Next, just as soon as you started logging with HWiNFO launch Prime95. 8. Start the "Blend" test. 9. It will look like this when running. 10. After you get prime95 running, install and launch furmark. In the first menu, change the resolution to match your monitor. If you don't see your resolution listed, you can use custom resolution. 11. Read the warning and press "GO!" 12. Leave furmark as the top window on your screen. All 3 programs need to be running for at least 10 minutes, or until your PC crashes. Start the timer after you get furmark running for the best results. If you are getting help from the discord, you can just upload the .csv file directly to discord. If you are getting help from the reddit, or the CSV file is too large for discord, upload the csv to https://www.mediafire.com/ How to Describe a Technical Problem You are facing a technical problem and want to resolve it. That’s why you went on /r/techsupport in the first place. If the AutoModerator redirected you here, that would mean your post may lack sufficient information techs need to know. Follow the four steps shown here for a successful /r/techsupport post: Step 1: Think About Your Problem You may know what your problem is, but you need to think about it carefully. These questions will help you: When does the problem occur? Does it only occur when you do certain things? Where does the problem occur? Is it a hardware or software problem? Does it occur only in one program? For how long has it been that way? Did it start after installing software or hardware? What has changed? What have I already tried? Has it affected the problem positively or negatively, or not at all? What haven’t I tried? There is no such thing as “I’ve tried everything”. These questions might even help you solve your issue yourself. If not, include any relevant ones in your post. Step 2: Gather Information Gather general information about your system or device. These are extremely important for a tech to know. Not all details are relevant to your problem, but adding as much information to your post as you can doesn’t hurt: Operating System (Windows 10, Android, MacOS, which version is it?) Device (Smartphone, Computer, Laptop, which model is it?) Application (one application? multiple? which version do you have?) Specs (System specs like RAM, CPU, GPU, etc, include even if you include the devicemodel) Please refer to our System Dossier article for details. Step 3: Choose a title Your title should be descriptive. Here are some examples of really bad titles: “I have a problem”, “help”, “I’ve been trying for hours and this problem is still here oh no I’m running out of characte” Examples of good titles are: “Windows 10 shows ‘unable to boot from harddrive’ “, “Android has red icon on top left corner”, “Outlook doesn’t sync anymore”. The title should be a tiny summary of your post. Just enough that a tech will know what it is roughly about. Step 4: Conclusions Read through our Wiki - here After reading these articles, go ahead and start writing your post. It should include your problem (with all the information from Step 1), your specs from Step 2, and what you have tried so far. Understand that the techs are here because they like to help. And if you piss them off, they’re gone. None of the techs gets paid by anyone and they have no obligation to you. Please be nice to them and always answer all questions. These steps will make it easier for a tech to help you (and they are more willing to). Describe your problem precisely and you’ll get a good answer. And if your post doesn’t get the attention you’d like it to have, do not repost immediately. Wait a day or so for that.