PC Screen flicker and freezes or BSOD mainly when playing games like WoW or D3

Anonymous
2014-09-18T11:54:47+00:00

So I bought my machine on January, everything good until like 2 months in it started Screen freezing with a really loud noise or random BSODs when playing either Battlefield, World of Warcraft or Diablo III.

I've tried every troubleshoot possible and no success.

The problems aren't stable, as it happens some days, and then some other days the games run smoothly and fine.

I'd really like to solve this problem, as it's somewhat annoying.

Thanks in advance, best regards

Luís

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-09-19T14:31:21+00:00

I've recommended the removal of the software below because of their tendency to cause BSOD's

NTIOLib_X64.sys Wed Oct 20 02:45:49 2010 (4CBE901D)

NTIOLib_X64.sys Thu Oct 25 21:46:44 2012 (5089EB84)

Driver Description: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5

 I've also recommended removal of avgtpx64.sys, AVG Secure search. If your current installed version of MBAM is not the full version, please uninstall it and turn on Windows Defender

Neither of these recommendations have been acted on. Please do so and test the system to see if these crashes re-occur.

Please upload a copy of your system information file. Click "start", type 'msinfo32", Click "file" at the top of the page, select "export" and give the file a name and click "save". Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2014-09-19T14:26:58+00:00

Update Intel USB3 driver to version 3.0.0.34:

http://download.msi.com/dvr\_exe/intel\_usb30.zip

Update Intel Smart Connect Technology driver to version 5.0.10.2832:

http://download.msi.com/dvr\_exe/intel\_sct.zip

Update Realtek High Definition Audio driver to version 6.0.1.7293:

http://download.msi.com/dvr\_exe/realtek\_hd\_audio.zip

Update Killer Network driver to version 1.1.42.1045:

http://download.msi.com/dvr\_exe/Killer\_network\_win78.zip

Update Razer Naga drivers to version 1.18.15:

http://drivers.razersupport.com/index.php?\_m=downloads&\_a=viewdownload&downloaditemid=861&\_m=downloads&\_a=viewdownload&downloaditemid=861

Download the driver and copy it to a folder on your desktop. Write down the path to the folder. If the driver has been zipped you will need to right click on the file and extract to your folder.

Next type Device Manager in the Search box above the Start button and press ENTER. Locate and right click on the device and select Properties. Click on the Driver tab and the Update Driver button. Click on “Browse my computer for driver” and click the Browse button. Type in the Search box the file path to your folder and click on Next. The system should find the driver in your folder and update. If it does not find the driver recheck that the driver is not zipped.

Please advise the chipset installed version:

http://www.tomshardware.co.uk/forum/209590-30-which-chipset-driver-version-have#

When you have updated all drivers please restart your computer, allow 30 minutes for the system to run before uploading further information so that the impact of making changes can become apparent.

Please provide an updated copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload to your OneDrive (formerly Sky Drive), share with everyone and post a link here. Reports in normal mode preferred. Please say if the report has been obtained in safe mode.

Please upload and share with everyone copies of your System and Application logs from your Event Viewer to your OneDrive and post a link here.

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window expand Windows Logs and select System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do the same for the Applications log. Do not provide filtered files. Do not place the cursor in the list of reports before selecting Action from the menu. Do not clear logs whilst you have a continuing problem.

Was this answer helpful?

0 comments No comments

62 additional answers

Sort by: Oldest
  1. Anonymous
    2014-09-18T14:35:38+00:00

    BugCheck D1, {fffff8800705f000, 2, 0, fffff88004bb6fa0}

    Unable to load image \SystemRoot\system32\DRIVERS\e22w7x64.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for e22w7x64.sys

    *** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys

    Probably caused by : e22w7x64.sys ( e22w7x64+19fa0 )

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ff100

     fffff8800705f000

    CURRENT_IRQL:  2

    FAULTING_IP:

    e22w7x64+19fa0

    fffff880`04bb6fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  LolClient.exe<== You were right.

    Please update Killer e2200 PCI-E Gigabit Ethernet Controller

    Loaded symbol image file: e22w7x64.sys

        Image path: \SystemRoot\system32\DRIVERS*e22w7x64.sys*

        Image name: e22w7x64.sys

        Timestamp:        Wed Dec 05 11:43:48 2012 (50BF79C4)

    Driver Description**: Killer e2200 PCI-E Gigabit Ethernet Controller**

    Driver Update Site: http://www.qca.qualcomm.com/resources/driverdownloads/

    Remove the following drivers.

    Image path: \SystemRoot\System32\Drivers**\sptd.sys**

        Image name: sptd.sys

    Driver Description: SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)

    Removal tool at: http://www.duplexsecure.com/en/downloads

    Image path: ??\C:\Program Files (x86)\MSI\Super-Charger*NTIOLib_X64.sys*

        Image name: NTIOLib_X64.sys

        Timestamp:        Thu Oct 25 06:27:58 2012 (5089142E)

    Driver Description: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-09-18T14:45:57+00:00

    You should also look into uninstalling and reinstalling Malwarebytes.. It is likely conflicting with avgtpx64.sys possibly playing a part in these crashes. The pro version of Malwarebytes probably also has a safe search feature so it probably cant co-exist with AVG Secure search.

    AVG Remover.

    http://www.avg.com/us-en/utilities

    Image path: ??\C:\Windows\system32\drivers*avgtpx64.sys*

        Image name: avgtpx64.sys

        Timestamp:        Thu May 29 08:32:11 2014 (538728CB)

    Driver Description: Driver for AVG Secure Search

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-09-18T15:39:14+00:00

    XP Rocks

    http://www.killergaming.com/solutions/Embedded\_Ethernet

    Your link does not work. The hardware driver and resulting software have been incorporated by a number of computer manufacturers into their machines. There are many reports of users looking for an updated version of the driver. Bigfoot would appear to have been taken over by Qualcomm. I suspect there may not be a suitable update at this time. Please let me know if you find a driver that resolves the problem. Meantime I think the best bet for the OP may be to take all the latest drivers from the MSI site.

    Was this answer helpful?

    0 comments No comments