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

7 BSOD in 30 minutes??? (PAGE_FAULT_IN_NONPAGED_AREA)


  • Please log in to reply
4 replies to this topic

#1 flaskmaster0820

flaskmaster0820

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:21 AM

Posted 24 April 2016 - 04:15 PM

I have a custom built pc that, up until the last week has worked flawlessly. Here are the specs:

Amd fx-8350 cpu 
Msi 790 gaming mobo
Msi GTX 970 gaming GPU
16Gb G.skill Ripjaws X
Rosewill quark 850W PSU
SanDisk 240 SSD plus
Seagate 2tb HD
Lepa dual mount top radiator

I originally bought a 750ti gpu, but quickly realized it wasn't enough, so I upgraded. The os is win 10, free upgrade from oem win 7. For months, it has been fine. Over the last week, I have gotten random BSOD. Each time I get a different error. Tonight, I sat down and wrote down each error that I got while running diagnostics:

DPC_WATCHDOG_VIOLATION
MEMORY_MANAGEMENT
BAD_POOL_HEADER
SYSTEM_SERVICE_EXCEPTION
CRITICAL_PROCESS_DIED
IRQL_NOT_LESS_OR_EQUAL

All of these errors occurred within 30 min. Between boots I tried to run sfc/scannow, but could never finish. I was able to download a hdd tester (I don't remember which) but smart tests showed ok on both drives, no sign of failures.

Also, games seemed to "disappear." At one point uplay told me that the division wasn't installed, so I had to reinstall. I made it thru the 35Gb download, only to crash 2 minutes into the game. Tonight, I tried to load up steam, and it told me steam wasn't installed. 

It almost seems like the ssd is failing, but all tests I ran showed the drive is fine.  I grabbed the Sandisk SSD dashboard, and all the tests showed OK.  I followed a guide someone gave me:

 

https://www.infopackets.com/news/9620/how-fix-sfc-scannow-fails-wont-complete

 

I followed this guide to run chkdsk and sfc /scannow in Administrator.  I never noticed any chkdsk errors, the sfc would make it to 100%, but state it was unable to fix the errors.  Attached is the LOG file it created.  I then proceeded to run Memtest86+ on my RAM, and I didn't notice any errors for roughly 12 hours.  As of today, the system seemed stable, so I loaded up a steam game to try and see how stable it is.  I got this:

 

On Sun 4/24/2016 8:35:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042416-7300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74080)
Bugcheck code: 0x50 (0xFFFFF680800DD098, 0x0, 0xFFFFF80002E8E167, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 4/24/2016 8:35:09 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF680800DD098, 0x0, 0xFFFFF80002E8E167, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

 

I have updated the BIOS for the MSI as well.  Please let me know if you need me to re-run any of these steps.

Attached Files

  • Attached File  CBS.log   3.56MB   0 downloads


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:21 AM

Posted 24 April 2016 - 07:36 PM

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

While waiting for a reply, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html


 


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.

#3 flaskmaster0820

flaskmaster0820
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:21 AM

Posted 25 April 2016 - 06:03 PM

Here is the BSOD-Inspector file.  I'll run the driver verifier in the meantime.

Attached Files



#4 flaskmaster0820

flaskmaster0820
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:21 AM

Posted 25 April 2016 - 08:37 PM

Here's another one.  Not sure if it helps.

 

 

Attached Files


Edited by flaskmaster0820, 25 April 2016 - 08:37 PM.


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:21 AM

Posted 26 April 2016 - 06:48 AM

Only 221 Windows Update hotfixes installed.  Most systems with SP1 have 300-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.

Also, there are very many recent Windows Update errors in the WER section of the MSINFO32 report
 

This device has problems in Device Manager:

 

Ethernet Controller    PCI\VEN_1969&DEV_E091&SUBSYS_76931462&REV_13\4&2DDBB3B7&0&00A8    The drivers for this device are not installed.

This is most likely your Killer E2200 Gigabit Ethernet Controller - please download and install the latest, W7 compatible drivers from the MSI website for  this device.

 

MSI Afterburner (along with EVGA Precision and Riva Tuner) is 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.

Your wireless XBox controller driver (xusb21.sys) dates from 2009 and is known to have BSOD problems with some Windows Systems.

Please uninstall it's software and physcially remove the controller adapter from your system.

FYI - there are no updates for this driver, so if it proves to be at fault you'll not be able to use it without having BSOD's.

The "fix" is to purchase a newer controller that uses the xusb22.sys driver (that one doesn't work with your controller).

 

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.


Finally, please uninstall ALL MSI utilities that use the NTIOLib_X64.sys driver.  This driver is known to cause BSOD's on some Windows systems and MSI scatters them about the system.

In this case they seem to be attributed to the MSI Super Charger program and may also be a part of MSI Afterburner (as mentioned above) - so please be sure to uninstall both of those programs.

 

If you still have BSOD's after doing the above things, then please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

 

Analysis:
The following is for informational purposes only.
**************************Mon Apr 25 21:33:30.094 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\042516-7675-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23392.amd64fre.win7sp1_ldr.160317-0600
System Uptime: 0 days 2:35:42.171
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+49d )
BugCheck 50, {fffffa83033dc290, 0, fffff80002efb125, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: fffffa83033dc290, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002efb125, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DyingLightGame
FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteVirtualAddresses+49d
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 24 16:35:09.713 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\042416-7300-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
System Uptime: 0 days 0:22:38.759
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )
BugCheck 50, {fffff680800dd098, 0, fffff80002e8e167, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: fffff680800dd098, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e8e167, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
**************************Mon Apr 25 21:33:30.094 2016 (UTC - 4:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)
athrx.sys                   Mon Oct  5 12:33:57 2009 (4ACA1FF5)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
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)
NTIOLib_X64.sys             Thu Oct 25 06:27:58 2012 (5089142E)
NTIOLib_X64.sys             Thu Oct 25 21:46:44 2012 (5089EB84)
xhcdrv.sys                  Thu Oct 30 22:44:27 2014 (5452F78B)
ViaHub3.sys                 Thu Oct 30 22:44:32 2014 (5452F790)
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
MpFilter.sys                Fri Oct 30 02:29:35 2015 (56330E4F)
RTKVHD64.sys                Tue Jan 26 06:03:05 2016 (56A75269)
nvvad64v.sys                Mon Mar 14 02:27:42 2016 (56E659DE)
nvlddmkm.sys                Mon Mar 21 21:49:01 2016 (56F0A48D)
NvStreamKms.sys             Fri Apr  1 21:18:58 2016 (56FF1E02)

 

http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=athrx.sys
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=usbfilter.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=AODDriver2.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=xhcdrv.sys
http://www.carrona.org/drivers/driver.php?id=ViaHub3.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.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=NvStreamKms.sys
 


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