Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


custom build, gaming, BSOD, game crashes, streaming crashes

  • Please log in to reply
1 reply to this topic

#1 gothylox


  • Members
  • 1 posts
  • Local time:04:39 AM

Posted 20 June 2016 - 04:48 PM

I'll keep this short and sweet because I know how busy you guys are.

I built a gaming computer from scratch, there were a lot of problems even getting it working initially this time, as compared to the last one I built that I had zero problems with ever.

I am getting a lot of BSOD's, games freeze and crash, movies freeze and crash, and streaming does too. In addition, I am getting an error occasionally with the GPU that tells me it has timed out and reset the GPU. I used the windows recommended fix for this and set the response timeout time to 8 seconds, since I have done so I have only seen this problem once. I was wondering if I had too little power for my system, but I have seen threads with similar problems that have plenty of power. I followed the instructions to the best of my ability, and you should find all of the information you have asked for below. Please don't hesitate to ask for anything else you may need. I truly appreciate what you guys are doing here for so many people.



· OS - Windows 8.1, 8, 7, Vista ? Windows 7 Ultimate
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? W7 Ultimate x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Purchased auth key, downloaded and mounted files to flash drive for install
· Age of system (hardware) less than 6 months, components purchased separately at the same time
· Age of OS installation - have you re-installed the OS? Original install on this hard drive. Initial attempts to install the same OS to SSD failed, and SSD was replaced with a standard SATA hard drive

· CPU AMD FX-6300
· Video Card MSI R7 370 2GD5T OC Radeon R7 370
· MotherBoard - (if NOT a laptop) MSI 970A SLI KRAIT EDITION AMD 970 CHIPSET
· Power Supply - brand & wattage (skip if laptop) EVGA 100-B1-0600-KR 80 PLUS Bronze 600W
HD - Hitachi 2TB 64MB 7200RPM SATA 6.0Gb/s
WIFI CARD - 300Mbps PCI -E WiFi wireless Card
RAM - Kingston HyperX Fury Memory White - 16GB Kit (2x8GB) - DDR3 1866MHz - (installed in the slots that don't share the bandwidth - don't know a ton about this so forgive me if that doesn't make total sense)

· System Manufacturer 
· Exact model number (if laptop, check label on bottom)

· Laptop or Desktop?
custom built desktop, mostly MSI components



DRIVER VERIFIER - forced to reset computer to the restore point I was instructed to make before running it

HD TEST - haven't run yet

RAM TEST - haven't run yet, ran windows memory test, was never showed results after restart

Attached Files

Edited by gothylox, 20 June 2016 - 05:06 PM.

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:39 AM

Posted 21 June 2016 - 04:45 PM

IMO, the suggested fixes for the TDR timeout of the video card only conceals the problem - it doesn't fix it.

If the card is timing out, then fixing the cause of the timeout is preferable (IMO) to just lengthening the timeout.


Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.

Just FYI, sometimes the owner won't know about this.  So here's 2 scenarios that might ring a bell:
- if they had a "friend" help with the computer - and the "friend" installed a pirated copy.
- or they used a copy that they had from another OEM computer.  The OEM license is tied to the hardware that it came from - so you can't just use it on another system (that means that it's pirated).

And here's the analysis:

Only 263 Windows Update hotfixes installed.  Most systems with SP1 have 350-400 or more.  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Many more Live Kernel Events than BSOD events in the WER section of the MSINFO32 report.
This is suggestive of a hardware problem (this isn't a 100% diagnosis - rather it's an increased likelihood of a hardware problem).

Regardless, it's enough to suggest doing hardware diagnostics.  Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html


Out of 21 memory dumps there were 8 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Windows systems.


NOTE:  these symptoms were from the previous release of OverDrive.  The new release uses the same driver name, but is dated from 4 November 2013.


Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program.
Please note that I stated "video stuff", as some integrated processors may have the graphics chip built in (which may involve the chipset software).
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://www.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLYhttp://www.sysnative.com/forums/showthread.php/668-ATI-video-cards-DRIVER-ONLY-installation-procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install".  Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.


The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:


**************************Mon Jun 20 16:40:50.253 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062016-28173-01.dmp]
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 5:20:38.315
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Probably caused by :ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5708972E5E6000 )
BugCheck 1E, {ffffffffc0000005, fffff80002eb91d1, 0, ffffffffffffffff}
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002eb91d1, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
PROCESS_NAME:  ntoskrnl.wrong.symbols.exe
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_7601.23418.amd64fre.win7sp1_ldr.160408-2045_TIMESTAMP_160409-054622_5708972E_nt_wrong_symbols!5708972E5E6000
  BIOS Version                  V25.2
  BIOS Release Date             10/22/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970A SLI Krait Edition (MS-7693)
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.


3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Jun 20 16:40:50.253 2016 (UTC - 4:00)**************************
netw5v64.sys                Thu Mar 26 12:21:24 2009 (49CBAB84)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
oem-drv64.sys               Mon Jun 21 13:23:32 2010 (4C1FA014)
usbfilter.sys               Mon Nov 29 04:50:21 2010 (4CF3775D)
amd_sata.sys                Fri Apr 15 14:37:14 2011 (4DA8905A)
amd_xata.sys                Fri Apr 15 14:37:17 2011 (4DA8905D)
AODDriver2.sys              Tue Sep  6 03:11:44 2011 (4E65C7B0)
AtihdW76.sys                Thu Feb 23 07:30:12 2012 (4F463154)
NTIOLib_X64.sys             Thu Oct 25 06:27:58 2012 (5089142E)
Rt64win7.sys                Thu Jan 15 01:06:44 2015 (54B758F4)
asmtxhci.sys                Thu Sep 10 05:38:13 2015 (55F14F85)
asmthub3.sys                Thu Sep 10 05:38:17 2015 (55F14F89)
atikmpag.sys                Sun Apr  3 21:31:54 2016 (5701C40A)
atikmdag.sys                Sun Apr  3 22:46:46 2016 (5701D596)
xNtKrnl.exe                 Sat Apr  9 01:46:22 2016 (5708972E)
**************************Thu Jun 16 05:57:12.711 2016 (UTC - 4:00)**************************
exfat.SYS                   Mon Jul 13 19:23:29 2009 (4A5BC1F1)
**************************Wed Apr 27 22:41:56.486 2016 (UTC - 4:00)**************************
xNtKrnl.exe                 Thu Mar 17 17:43:02 2016 (56EB24E6)
**************************Thu Apr  7 15:45:47.646 2016 (UTC - 4:00)**************************
xNtKrnl.exe                 Tue Mar 17 00:02:04 2015 (5507A73C)
**************************Wed Apr  6 12:25:22.777 2016 (UTC - 4:00)**************************
atikmpag.sys                Fri Dec  4 11:42:57 2015 (5661C291)
atikmdag.sys                Fri Dec  4 12:14:28 2015 (5661C9F4)

oem-drv64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
xNtKrnl.exe - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
xNtKrnl.exe - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
xNtKrnl.exe - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.




Edited by usasma, 21 June 2016 - 04:46 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users