Pci error while updating region
I have messed around with paging options as suggested in other posts but it did not appear to solve the problem. As for antivirus software, I am currently using Norton Internet Security 2015, for the sake of testing I have also disabled it before resuming torrent download and reproduced the same BSOD.
12672 Intel(R) MEInfo Version: 126.96.36.1996 Copyright(C) 2005 - 2012, Intel Corporation. Intel(R) ME code versions: BIOS Version: 3010 MEBx Version: Not available Gbe Version: 1.3 Vendor ID: 8086 PCH Version: 5 FW Version: 188.8.131.526 UNS Version: Not Available LMS Version: Not Available MEI Driver Version: 184.108.40.2065 Wireless Hardware Version: Not Available Wireless Driver Version: Not Available FW Capabilities: 0x00101460 Intel(R) Anti-Theft Technology - PRESENT/ENABLED Intel(R) Capability Licensing Service - PRESENT/ENABLED Protect Audio Video Path - PRESENT/ENABLED Intel(R) Dynamic Application Loader - PRESENT/ENABLED Cryptography Support: Disabled Last ME reset reason: Power up Local FWUpdate: Enabled BIOS Config Lock: Disabled Gb E Config Lock: Disabled Host Read Access to ME: Enabled Host Write Access to ME: Enabled SPI Flash ID #1: EF4017 SPI Flash ID VSCC #1: 20052005 SPI Flash BIOS VSCC: 20052005 BIOS boot State: Post Boot OEM Id: 00000000-0000-0000-0000-000000000000 Capability Licensing Service: Enabled OEM Tag: 0x00000000 Localized Language: Unknown Independent Firmware Recovery: Disabled Simple flash instructions (Inside Windows x64 using Intel Flash Programming Tool (NOT FWUPDATE! FOR TINKERERS ONLY - Don't bother with this information unless you are testing things out. Just tested and you can also update to the latest GBE firmware included in that ME update and it works perfectly fine.
The fresh windows 10 install also was installed on a brand new hard disk drive so it could not have been a HDD issue, I only replaced it because Crystal Disk had caution on the old drive (it is fine on the new drive).
My RAM also isn't an issue as I have ran Mem Test86 for approximately 5-6 hours and everything checked out fine.
Thus I think thinking it could potentially be a driver issue which is causing this BSOD but I cannot pinpoint what.
I have read many issues online regarding this BSOD which is why I have done several tests myself before comming onto here.