BSOD PAGE_FAULT_IN_NONPAGED_AREA--Frequently

If you are running in AHCI or RAID mode in the BIOS, you may need to switch to IDE to have Seatools detect the drive (or vice versa).
Note   Note
Consult your manual for steps to enter the BIOS.


Warning

Make sure to back up any important files prior to changing the drive settings.

Changing the settings can leave Windows unable to boot.

 
I freed up some space up to 90GB in my G drive and no BSOD since last 24 Hours....
I had 30GB free before..
Well, lets see forward.
 
jcgriff2 said:
IMO, freeing up space should have no affect re: BSODs.

Perhaps the content...?
Click to expand...

Yeah, it might be the content..

Well, no BSOD's yet..

i will let you guyz know..

I installed windows 8 yesterday and also found drivers for acpi ntn0530 (The Unknown Device). Could it be the cause too?
 
Problem devices, such as those without drivers installed, can cause any myriad of problems. In my experience, blue screens are not too common from these problem devices, but they are not unheard of.

I know that IR devices can cause blue screens if the appropriate drivers are missing, so it is possible that is the root of the problem, but I would not expect a 0x50 BugCheck resulting from an IR device issue. Typically, IR device errors cause BugCheck 0x7E, 0x8E, or 0XD1 but not 0x50 BugChecks.
 
writhziden said:
Problem devices, such as those without drivers installed, can cause any myriad of problems. In my experience, blue screens are not too common from these problem devices, but they are not unheard of.

I know that IR devices can cause blue screens if the appropriate drivers are missing, so it is possible that is the root of the problem, but I would not expect a 0x50 BugCheck resulting from an IR device issue. Typically, IR device errors cause BugCheck 0x7E, 0x8E, or 0XD1 but not 0x50 BugChecks.
Click to expand...

Thanks for the information Writhziden.
 
I'm very curious about this. All the crashdumps are the same, which involve the same function (MiCompressRelocations) every time, which occurs very early in the system's uptime (with one exception), and the currently running process each time is either explorer.exe or svchost.exe. Every callstack is referring to SuperFetch in which it appears to be either prefetching a module image to be used later, or an actual request to use the prefetched image. So something involving SuperFetch is bugging out I reckon.

The only thing I saw when I googled the MiCompressRelocations function is that most people experiencing BSODs with it were dealing with Max Payne 3 with it crashing their system when they didn't have Windows 7 Service Pack 1 installed. While I don't suspect that ahmadlucky here has Max Payne 3 installed nor that it's related, it does appear that he doesn't have Service Pack 1 installed. Is this correct, ahmad? If so, you may wanna resolve that and install it as I do know it has a number of patches involving SuperFetch.

Anyways, aside from that, if we're dealing with a specific module image being prefetched that is crashing the system every time it's prefetched, then we can figure out very well what's really causing the issue here. I'm not ruling out possible hardware failure, but this seems way too consistent for me to initially suspect it as such. Unfortunately, I'm afraid one can't go very far on the information from minidumps alone, and this will require either a kernel dump or maybe even a full memory dump if this thread happened to have been called by a userland application (anything not a kernel service or driver). If you're willing, ahmad, the MEMORY.DMP file located in your Windows directory would probably help us a lot here.

As for other recommendations other than what's greatly been provided already, I recommend doing an SFC scan (from Windows CD, not from drive) and a CHKDSK just to be sure we aren't dealing with any sort of corruption. Also you may wanna do a virus/rootkit scan of some sort too as a just-in-case. If you plan on going that route, you'll wanna create a separate thread in our Security Arena subforum, and refer back to this one. Make sure to follow the posting instructions on the sticky there to give us some info.
 
Vir Gnarus said:
I'm very curious about this. All the crashdumps are the same, which involve the same function (MiCompressRelocations) every time, which occurs very early in the system's uptime (with one exception), and the currently running process each time is either explorer.exe or svchost.exe. Every callstack is referring to SuperFetch in which it appears to be either prefetching a module image to be used later, or an actual request to use the prefetched image. So something involving SuperFetch is bugging out I reckon.

The only thing I saw when I googled the MiCompressRelocations function is that most people experiencing BSODs with it were dealing with Max Payne 3 with it crashing their system when they didn't have Windows 7 Service Pack 1 installed. While I don't suspect that ahmadlucky here has Max Payne 3 installed nor that it's related, it does appear that he doesn't have Service Pack 1 installed. Is this correct, ahmad? If so, you may wanna resolve that and install it as I do know it has a number of patches involving SuperFetch.

Anyways, aside from that, if we're dealing with a specific module image being prefetched that is crashing the system every time it's prefetched, then we can figure out very well what's really causing the issue here. I'm not ruling out possible hardware failure, but this seems way too consistent for me to initially suspect it as such. Unfortunately, I'm afraid one can't go very far on the information from minidumps alone, and this will require either a kernel dump or maybe even a full memory dump if this thread happened to have been called by a userland application (anything not a kernel service or driver). If you're willing, ahmad, the MEMORY.DMP file located in your Windows directory would probably help us a lot here.

As for other recommendations other than what's greatly been provided already, I recommend doing an SFC scan (from Windows CD, not from drive) and a CHKDSK just to be sure we aren't dealing with any sort of corruption. Also you may wanna do a virus/rootkit scan of some sort too as a just-in-case. If you plan on going that route, you'll wanna create a separate thread in our Security Arena subforum, and refer back to this one. Make sure to follow the posting instructions on the sticky there to give us some info.
Click to expand...

Thanks for this great post....

I am not that tech expert so i really could not understand somethings in your reply..

Well, i did have max payne 3 in my system (infact i still have but i did not run it) but i did not play it on the previous windows 7. But i have played it on my pc in windows 7 but after that i did reinstall windows. So previous windows 7 did not had anything related to maxpayne 3 (i think). I am using windows 8 now and no BSOD happened yet..
I will do the steps you mentioned if i face BSOD by any chance...
 
Sorry, I was kinda directing my statements to both the other tech support as well as you, so pardon the technical jargon. If you know to provide us the MEMORY.DMP file and run those scans as well as install Service Pack 1 for your system then that should be good.
 
Vir Gnarus said:
Sorry, I was kinda directing my statements to both the other tech support as well as you, so pardon the technical jargon. If you know to provide us the MEMORY.DMP file and run those scans as well as install Service Pack 1 for your system then that should be good.
Click to expand...

I am running win8 now and no BSOD yet. So, if it happens any time then i will do what you said to do..
Thanks
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top