Jump to content

BSOD PAGE_FAULT_IN_NONPAGED_AREA


Recommended Posts

Hello, recently my PC has been getting a BSOD every time it starts up.

The technical information that the BSOD gives is: STOP: 0x00000050 (0xFFFFFA801600000, 0x0000000000000000, 0xFFFFF800034E92A8, 0x0000000000000002 )

I am using Windows 7. If I restart it normally after the BSOD, everything runs fine. I also cleaned my PC of dust with some compressed air, which may have caused problems with the hardware although I'm not sure.

I also recently posted a topic about malware and followed the instructions given there, although I doubt that is the cause of the BSOD: https://forums.malwarebytes.com/topic/196374-afraid-that-i-might-have-been-hacked-or-downloaded-an-unsafe-program/

Whenever I boot up in safe mode everything seems to run fine, so I think it might be a software problem although I don't know how to identify which.

I checked my event viewer for errors and the first error I got on startup was:

The following boot-start or system-start driver(s) failed to load:

AppleCharger
discache
MpFilter
spldr
UsbCharger
Wanarpv6

The event ID was 7026

I tried looking at some other help threads I found on the issue through Google, but they all identified the problem as a RAM hardware problem. I haven't installed any new hardware since I got my PC a year ago, the only time I have gone near the hardware is when I cleaned it of dust recently, so I don't think that is the cause.

I would appreciate a reply, thanks.

Link to post
Share on other sites

  • 3 weeks later...

FYI, I am recovering from some severe eye problems.
If I don't reply promptly, please be patient.

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum):  https://forums.malwarebytes.org/topic/170037-blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities.
.ZIP is the type file that can be uploaded to the forums.

 

Link to post
Share on other sites

The perfmon report is only one of the reports that are requested.  Please follow the instructions for the Sysnative Collection app or the directions for the alternate tool (with the github link) in my previous post.

I looked at the perfmon report and didn't find anything significant in it.

 

Link to post
Share on other sites

Only 1 recent memory dump in the uploaded reports.
If using a disk cleaner (such as CCleaner), please stop while we're troubleshooting.


Only 266 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.

Interestingly, your systeminfo report does not show the USB wifi adapters installed on your system.
FYI:

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 MSINFO32 report shows both AMD and nVidia video components installed.
The report also only shows an nVidia video card installed (yet the motherboard specs show that onboard AMD video is available).
Have you disabled the AMD video in the BIOS?

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.  Please uninstall AMD OverDrive (also uninstall any instances of Gigabyte EasyTune and EasySaver that may be installed).

Please uninstall the Apple Charger (Gigabyte On/Off Charger) app, as it has been known to cause BSOD's also.

If this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

The stack shows problems with an HIDCLASS driver.  I wonder about the different input/output devices that you use on the system
I have seen issues with USB audio devices in the past and wonder also about your VB Audio software.


Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Wed Mar 15 08:28:00.071 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\031517-23259-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
System Uptime:0 days 1:50:34.881
Probably caused by :HIDCLASS.SYS ( HIDCLASS+55f0 )
BugCheck 1A, {5100, fffff6fc400034c0, 1, 22cf00121}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fc400034c0
Arg3: 0000000000000001
Arg4: 000000022cf00121
BUGCHECK_STR:  0x1a_5100
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: X64_0x1a_5100_HIDCLASS+55f0
  BIOS Version                  F2
  BIOS Release Date             11/25/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-78LMT-USB3 6.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 


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:
**************************Wed Mar 15 08:28:00.071 2017 (UTC - 4:00)**************************
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)
PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
xhcdrv.sys                  Sun Aug 11 23:13:09 2013 (520852C5)
ViaHub3.sys                 Sun Aug 11 23:13:14 2013 (520852CA)
AppleCharger.sys            Sun Oct 27 21:59:21 2013 (526DC4F9)
RTKVHD64.sys                Tue Jun 10 08:20:20 2014 (5396F804)
Rt64win7.sys                Tue Jun 17 07:59:14 2014 (53A02D92)
vbaudio_cable64_win7.sys    Thu Aug 14 02:15:25 2014 (53EC53FD)
MpFilter.sys                Mon Aug  8 19:01:17 2016 (57A90F3D)
WRkrn.sys                   Fri Nov 18 12:49:11 2016 (582F3F17)
nvvad64v.sys                Mon Dec 19 00:50:05 2016 (5857750D)
nvvhci.sys                  Tue Dec 27 20:44:00 2016 (586318E0)
nvhda64v.sys                Wed Feb  8 07:32:14 2017 (589B0FCE)
nvlddmkm.sys                Thu Feb 23 02:41:16 2017 (58AE921C)
 


http://www.carrona.org/drivers/driver.php?id=amdiox64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.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=AppleCharger.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
vbaudio_cable64_win7.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.
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=WRkrn.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
nvvhci.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.
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

 

 

 


 

 

Link to post
Share on other sites

Hi, I haven't disabled AMD in the BIOS as far as I know, but I'll try it now.

I've uninstalled the AppleCharger driver, but when I checked for AODDriver2, the only thing I could find was AODDriver4.1. I wasn't sure if I should still uninstall it so I left it alone.

The only input/output devices I use on the system are my keyboard, mouse, monitor and a Devolo device (I'm not sure which, but I use it to pick up the internet connection from downstairs as the signal was too weak without it).

Link to post
Share on other sites

AODDriver4.1 is a component of the AMD OverDrive program.
It was AODDriver2 when I first wrote that guide.
Still, the point is to uninstall AMD Overdrive and see if that helps
 

If you still get BSOD's after removing the AMD Overdrive, then please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Link to post
Share on other sites

Removing things from Device Manager often doesn't work.  This is because removing drivers in Device Manager doesn't remove the program associated with the device.  So, the program (when launched) can take steps to heal itself (and drag copies of the driver out of the driver store).

Uninstall AppleCharger (Gigabyte On/Off Charge) from Control Panel...Programs and Features.

Try this to remove AMD Overdrive (particularly the part about the driver-only installation):
 

Quote

AMD OverDrive (AODDriver2.sys or AODDriver4.1) 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.



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.

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, etc) 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.



 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.