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.


BSOD - First Gaming Rig build

  • Please log in to reply
1 reply to this topic

#1 Deadsy


  • Members
  • 1 posts
  • Gender:Male
  • Local time:12:17 AM

Posted 10 August 2016 - 09:17 PM

BSOD happens at random. So far during streaming on HBO Now in any browser, while switching from one PC game to another, or in the middle of watching videos using KODI. Unable to obtain a perfmon output, gave repeated error: The interface is unknown. Also noticed i do not have a Ping function in CMD. possibly missing other commands :/ 

Any advice appreciated, Thanks in advance!

EDIT: #5:

· OS - Windows 7 64-bit SP1
· x64
· What was original installed OS on system? Windows 7 64-bit SP1
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Purchased
· Age of system (hardware) less than a year, over 6 months
· Age of OS installation - have you re-installed the OS? Have not re-installed, initial install date - 11/07/2015

· CPU - AMD FX-8350
· Video Card - 1023 MB NVIDIA GeForce GTX 560 Ti (PNY)
· MotherBoard - ASRock 990FX Killer Southbridge model SB910/950  Southbridge revision 40
· Power Supply - brand & wattage - EVGA SuperNOVA NEX 750W 80+ Bronze Certified Semi-Modular ATX Power Supply

· System Manufacturer - ??? me?
· Exact model number - ?? its custom. heres a link to all its parts?

· Laptop or Desktop? Desktop

Attached Files

Edited by Deadsy, 10 August 2016 - 09:31 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:01:17 AM

Posted 12 August 2016 - 04:26 PM

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 1 memory dump in the uploaded reports.

Only 1 memory dump listed in the KernelDumpList.txt report

No entries in the WER section of the MSINFO32 report

No entries in the Application or the System Event Viewer logs

Beyond this I have these 5 suggestions:
1.  Get ALL available Windows Updates.  It may take several trips to get them all
2.  Get ALL available, compatible updates for your system from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website
4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If all of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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.

Unable to view hard drive sizes in the MSINFO32 report


Your wireless XBox controller is known to cause BSOD's on some Windows systems.

Please uninstall it (from Control Panel...Programs and Features), then physically remove it from your system

Then test to see if the BSOD's have stopped


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 entry will remain in Device Manager even though you've removed it.  So, open up Device Manager and check for the AODDriver4.2.0 (it may have another number).  Right click on it and select "Uninstall".  If it asks to remove software, put a check in the box.  Then click on OK.

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.


The memory dump blames NETwsw01.sys - a driver for your Intel wireless networking device.


- download a fresh copy of the latest compatible drivers from the manufacturer's website

- uninstall the current wireless software from Control Panel...Programs and Features

- install the freshly downloaded software

- monitor for further BSOD's




The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Aug  9 22:29:03.387 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\080916-40529-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 2:31:26.043
*** WARNING: Unable to verify timestamp for NETwsw01.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsw01.sys
Probably caused by :NETwsw01.sys ( NETwsw01+9fe79 )
BugCheck 1E, {0, 0, 0, 0}
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: X64_0x1E_NETwsw01+9fe79
  BIOS Version                  P1.60
  BIOS Release Date             01/06/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             990FX Killer

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:

**************************Tue Aug  9 22:29:03.387 2016 (UTC - 4:00)**************************
mcdbus.sys                  Tue Feb 24 05:34:07 2009 (49A3CD1F)
PAC7302.SYS                 Mon Apr 27 22:07:52 2009 (49F664F8)
xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AODDriver2.sys              Tue Mar  6 04:55:00 2012 (4F55DEF4)
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
vusbstor.sys                Wed Jan 16 22:01:04 2013 (50F76970)
AsrRamDisk.sys              Thu May  9 04:50:45 2013 (518B6365)
EtronXHCI.sys               Wed Jul 17 02:23:45 2013 (51E63871)
EtronHub3.sys               Wed Jul 17 02:23:48 2013 (51E63874)
xhcdrv.sys                  Sun Jan 19 21:19:50 2014 (52DC87C6)
ViaHub3.sys                 Sun Jan 19 21:19:55 2014 (52DC87CB)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
NETwsw01.sys                Mon May  4 09:10:57 2015 (55476FE1)
AmUStor.SYS                 Thu May 14 05:43:35 2015 (55546E47)
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
e2xw7x64.sys                Fri Feb  5 17:44:58 2016 (56B525EA)
RTKVHD64.sys                Thu Feb 18 03:23:21 2016 (56C57F79)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
nvlddmkm.sys                Mon May  9 18:57:39 2016 (573115E3)

vusbstor.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.
e2xw7x64.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.



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.

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users