Thanks, core details (hardware drivers, loaded System drivers, Services) look good
![:)](http://www.tweaking.com/forums/Smileys/smillhey/smiley.png)
Nothing there jumping out at me, seems to be a solid base.
Running software:
Reimage - I'd not use this, my experience/testing of it showed it using scareware tactics, I belive it's unreliable and could easily cause more issues than it claims to be able to 'fix'. If you can revert any changes already made by this, please do so and then uninstall it completely.
Chrome: just be aware that running Chrome in the background
might cause issues whilst gaming, I rarely use it and it's hardly ever installed here but I did have some *interference* from somewhere during a gaming session several months ago. Chrome was the only 'different' software running, with just four tabs open. I've not had those issues before or since and my default browser (Pale Moon) is almost always running with 50+ tabs and 1.6-3+GB memory in use over sessions that might have very long (4-19+ days) uptimes.
Other than the BSOD issues, WER (Windows Error Reporting) has only logged issues with your torrent software (uninstall and try a different software?) and Chrome, so far
![Wink ;)](http://www.tweaking.com/forums/Smileys/smillhey/wink.png)
.
So, apart from Reimage, it looks pretty good to me.
EDIT:
I've delved deeper into the WER for the BSOD types and checked those against John Carrona's (usasma)
database to check for any causes that might be common to all the BSOD's. Apart from the latest 0x139 (which might be a torrent client using too many connections), all the others listed in the WER could be down to the same 'bad' driver:
0x139:
???? but might be torrent software here, see
https://support.microsoft.com/en-us/help/2883658/-0x00000139-stop-error-on-a-windows-server-2012-based-computer-that-has-many-tcp-connections0x7f:
Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
0x3b:
System service, Device driver, graphics driver, ?memory
0xa:
Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
0x1e:
Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
0xd1:
Device driver
Use the PC normally for the next few days/week or so, if you do have another BSOD, collect and attach the new dump(s) and fresh MSInfo data and attach them to a reply. Then
read and follow carefully the steps here for using Driver Verifier, we need to stress the loaded drivers to see if there's still a bad/suspect one loading.