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.

Photo

Windows 7 BSoD: Help


  • Please log in to reply
2 replies to this topic

#1 BadNarrative

BadNarrative

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:25 AM

Posted 11 September 2016 - 06:42 AM

· OS - Windows 7
· x64
· What was original installed OS on system? Custom installed Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full Retail Version
· Age of system (hardware): Er... The oldest piece must be like what, 2010?
· Age of OS installation - have you re-installed the OS? About a year and a half back.
· CPU - AMD FX-6350
· Video Card - Nvidia GeForce GTX 560
· MotherBoard - (if NOT a laptop) - msi 970 Gaming
· Power Supply - brand & wattage (skip if laptop) - CoolerMaster 700w
· System Manufacturer - Myself.
· Exact model number (if laptop, check label on bottom) 

· Laptop or Desktop? - Desktop

 

Information: When I'm NOT in Safe Mode / Safe Mode (With Networking), it turns to a blue screen about a minute after a laggy startup. 

If this IS about software, the most recent thing I installed was either Google Chrome or Popcorn Time.

 

Please help

 

If the BSOD things didn't come up right, the most recent bsod have been like 0x0000001E (followed by a couple others), 0x000000D1, And that IRQL_Driver_Insufficient error or something like that. 

 

UPDATE: Ok, yeah, it still happens in Safe Mode. But delayed a lot longer.

Attached Files


Edited by BadNarrative, 11 September 2016 - 06:59 AM.


BC AdBot (Login to Remove)

 


#2 stavros3000

stavros3000

  • Members
  • 57 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:25 AM

Posted 12 September 2016 - 09:45 AM

Have you been able to run a full virus/malware scan?  Good start would be:- https://www.malwarebytes.com/antimalware/ where you can grab a free copy.



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 12 September 2016 - 07:09 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 308 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.

You have a Belkin Wireless G USB Network Adapter:

I do not recommend using wireless USB network devices.
These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

 

The memory dumps point at your wifi drivers. Tne drivers date from 2008

Please:

- download a fresh set of the latest, W7 compatible wifi drivers for your system

- uninstall the current wifi drivers from your system (using Control Panel...Programs and Features)

- install the freshly downloaded drivers

- monitor for further BSOD's

 

The other possibilities here are either a hardware problem with the networking devices or another internet-aware program interfering with the wifi drivers.

 

Please uninstall SuperAntiSpyware - it's drivers date from 2011

 

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.


Your wireless XBox controller uses the xusb21.sys driver

This driver is known to cause BSOD's on some Windows systems

Unfortunately, there are no newer drivers available for this device (this means that you'll have to buy a new device in order to use the xusb22.sys driver

 

There are several NTIOLib_x64.sys drivers in the memory dumps

These are known to cause BSOD's on some Windows systems.

Search your computer for these drivers (they are usually in the Program Files or Program Files (x86) directory in an MSI sub-directory)

When you find them, uninstall the program that belongs to them.

 


Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sun Sep 11 06:48:22.251 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\091116-27456-01.dmp]
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 0:03:17.891
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by :nwifi.sys ( nwifi+8767 )
BugCheck 1E, {0, 0, 0, 0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Arguments:
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
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x1E_nwifi+8767
  BIOS Version                  V22.3
  BIOS Release Date             05/12/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 27 22:39:51.283 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\082816-26644-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
System Uptime:0 days 3:59:59.925
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by :athrxusb.sys ( athrxusb+760e1 )
BugCheck 1E, {0, 0, 0, 0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Arguments:
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
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x1E_athrxusb+760e1
  BIOS Version                  V22.3
  BIOS Release Date             05/12/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 24 17:40:50.827 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\082416-16614-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: 7601.18933.amd64fre.win7sp1_gdr.150715-0600
System Uptime:0 days 0:26:50.467
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by :nwifi.sys ( nwifi+8767 )
BugCheck 1E, {0, 0, 0, 0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Arguments:
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
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: X64_0x1E_nwifi+8767
  BIOS Version                  V22.3
  BIOS Release Date             05/12/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler




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:

**************************Sun Sep 11 06:48:22.251 2016 (UTC - 4:00)**************************
athrxusb.sys                Tue Jul 29 08:47:13 2008 (488F1151)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SASKUTIL64.SYS              Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)
lvrs64.sys                  Fri Sep 21 15:02:17 2012 (505CB9B9)
lvuvc64.sys                 Fri Sep 21 15:03:12 2012 (505CB9F0)
NTIOLib_X64.sys             Thu Oct 25 06:27:58 2012 (5089142E)
NTIOLib_X64.sys             Thu Oct 25 21:46:44 2012 (5089EB84)
NTIOLib_X64.sys             Mon Nov 26 05:11:53 2012 (50B34069)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
AODDriver2.sys              Mon Nov  4 14:47:26 2013 (5277F9CE)
amd_sata.sys                Wed Nov  6 01:10:20 2013 (5279DD4C)
amd_xata.sys                Wed Nov  6 01:10:23 2013 (5279DD4F)
usbfilter.sys               Mon Feb 17 01:23:43 2014 (5301AAEF)
mbam.sys                    Wed Sep  3 13:50:25 2014 (540754E1)
xhcdrv.sys                  Thu Oct 30 22:44:27 2014 (5452F78B)
ViaHub3.sys                 Thu Oct 30 22:44:32 2014 (5452F790)
rzpmgrk.sys                 Thu Jun 11 22:57:21 2015 (557A4A91)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
NvStreamKms.sys             Fri Jun  3 07:28:21 2016 (575169D5)
VBoxUSBMon.sys              Tue Aug 16 14:17:53 2016 (57B358D1)
VBoxNetAdp6.sys             Tue Aug 16 14:17:53 2016 (57B358D1)
VBoxNetLwf.sys              Tue Aug 16 14:17:53 2016 (57B358D1)
VBoxDrv.sys                 Tue Aug 16 14:18:29 2016 (57B358F5)
nvlddmkm.sys                Thu Aug 25 16:31:15 2016 (57BF5593)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 27 22:39:51.283 2016 (UTC - 4:00)**************************
usbaapl64.sys               Thu Jun 11 02:08:10 2015 (557925CA)
NvStreamKms.sys             Sat Jul 25 05:22:15 2015 (55B35547)
nvvad64v.sys                Mon Aug 10 03:51:42 2015 (55C8580E)
nvlddmkm.sys                Thu Aug 11 07:07:29 2016 (57AC5C71)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 29 14:48:35.578 2015 (UTC - 4:00)**************************
xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)
ccSetx64.sys                Mon Aug 18 15:33:11 2014 (53F254F7)
SRTSPX64.SYS                Tue Aug 26 02:36:42 2014 (53FC2AFA)
SYMEVENT64x86.SYS           Mon Jan 19 17:43:56 2015 (54BD88AC)
nvhda64v.sys                Thu Apr 16 15:03:16 2015 (55300774)
Ironx64.SYS                 Mon May  4 19:51:42 2015 (5548060E)
SYMEFASI64.SYS              Thu May  7 05:44:15 2015 (554B33EF)
SYMNETS.SYS                 Fri May  8 18:20:49 2015 (554D36C1)
BHDrvx64.sys                Sat Jul 11 00:11:26 2015 (55A0976E)
EraserUtilRebootDrv.sys     Wed Jul 15 21:17:05 2015 (55A70611)
eeCtrl64.sys                Wed Jul 15 21:17:05 2015 (55A70611)
nvlddmkm.sys                Thu Aug  6 23:22:42 2015 (55C42482)
IDSvia64.sys                Tue Aug 18 22:25:26 2015 (55D3E916)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 29 14:34:05.097 2015 (UTC - 4:00)**************************
cpuz134_x64.sys             Fri Jul  9 07:16:58 2010 (4C37052A)
EX64.SYS                    Sat Nov 15 04:14:03 2014 (5467195B)
ENG64.SYS                   Sat Nov 15 04:15:33 2014 (546719B5)
SRTSP64.SYS                 Sun Jun 14 03:19:20 2015 (557D2AF8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 29 07:38:53.115 2015 (UTC - 4:00)**************************
ssudbus.sys                 Thu Jan  2 04:51:22 2014 (52C5369A)
IDSvia64.sys                Mon May 11 18:15:04 2015 (555129E8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 24 18:47:14.127 2015 (UTC - 4:00)**************************
nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
nvlddmkm.sys                Thu Feb  5 13:01:37 2015 (54D3B001)


http://www.carrona.org/drivers/driver.php?id=athrxusb.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=SASKUTIL64.SYS
http://www.carrona.org/drivers/driver.php?id=SASDIFSV64.SYS
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=xhcdrv.sys
http://www.carrona.org/drivers/driver.php?id=ViaHub3.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp6.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=usbaapl64.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=cpuz134_x64.sys
http://www.carrona.org/drivers/driver.php?id=EX64.SYS
http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=ssudbus.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

 

 

XXXXX


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