Recent content by ghostinthemirror

  1. G

    [SOLVED] Windows 10 Installation BSOD at Gathering Files %

    GOT A BAD CPU GUYS, case closed. Tried with another 3000 series ryzen processor and had zero issues.
  2. G

    [SOLVED] Windows 10 Installation BSOD at Gathering Files %

    Update 2: Finally got the chance to swap motherboards, same issue occurred during the installation of windows. So, motherboards have been tested along with gpu, psu, different ram... leaving just the CPU. Sometime tomorrow I'll have the chance to swap CPU's with another ryzen 3000 series...
  3. G

    [SOLVED] Windows 10 Installation BSOD at Gathering Files %

    Update: I've been playing DOOM 2016 at 140-200fps, 1440p in order to push my cpu and cause a BSOD. So far it's been rock solid, which I believe indicates the cpu is indeed NOT the problem here. More than likely it is the motherboard and since I was only able to install windows (on the third...
  4. G

    [SOLVED] Windows 10 Installation BSOD at Gathering Files %

    I recently reseated the cpu and applied arctic 4 mx thermal paste. At any angle I can't spot a single bent pin so I too think the mobo could be the issue or equally possible I might have gotten a cpu from a bad batch, as outrageous as it sounds for a new ryzen 3600. The whole build is less than...
  5. G

    [SOLVED] Windows 10 Installation BSOD at Gathering Files %

    Hello there. Current speed is 3200mhz. This is the speed the ram is rated at, and also the max speed that the mobo can handle. I've already tried installing windows at default speeds and with just a single stick of ram (even swapping between the two 8gb sticks)... I'm starting to think the mobo...
  6. G

    [SOLVED] Windows 10 Installation BSOD at Gathering Files %

    Hey guys, I could really use some advice on how to go about resolving this issue with my new AMD build. So I'm trying to clean install Windows 10 via USB on three different drives, two of which are brand new, and each time the installation fails at "gathering files %" with a BSOD, followed by...