Page Fault In Non-paged Area

I'm getting a BSOD with this message after downloading updates and restarting to complete their installation.

This is occurring in Windows 8.1 Pro.

I've had none of these issues in Windows 8.1 Core, Windows 10 Pro or Windows 10 Insider Preview.

The Dell Inspiron 15-5555 has run it's memory test on the second restart twice and this last time I ran the extended Windows Memory test with cache turned on and nothing was found.

My system is a Dell Inspiron 15-5555 with AMD A8 7410 quad-core @ 2.2GHz with integrated Radion R5 graphics, 16GB 2Rx8 PC3-1666 RAM and a 1TB Samsung 850 EVO SSD.

Any ideas please?

 

Best matches in your scenario marked ?in red?. The description pretty much rules out hardware memory (RAM), Windows' memory test is pretty weak anyway, better to use MemTest86+ from a bootable USB and do 7+ full runs to be sure.

Try to copy any minidumps to your Desktop, zip and attach the zips, I'll take a look and see what shows up. Alt., use the info/collection tools from Sysnative, they'll include more useful data.

 

I've attached the only minidump in the Windows 8.1 Pro minidump folder and a 7-Zip of the CBS log.

Like I said in my OP, this is only occurring in Win 8.1 Pro after I restart to complete Updates installation. I run 8.1 Core, 10 Pro and 10 (Pro) Insider Preview from the same SSD (I bought it used — could the SSD be failing in a certain area of nand flash?).

 

It looks like it's a bug/driver clash with the TPM (Trusted Platform Module) and BIOS access. I think *something* (presumably an update) is trying to unlock the TPM to update it but *something else* is blocking it.

Probably best to chase this up with Dell and MS, also check for BIOS and other firmware type updates from Dell.

Or, sift through those WUs and disallow any that are TPM -related so that you can otherwise keep it updated.

The guys at Sysnative might be able to dig deeper into the dump to give you a better description of what's going wrong than I can.

There's no 3rd party software that jumps out at me, however, the amdpsp.sys is a possible contender for running interference, it's some kind of AMD security driver "Allow generic all access to system and built-in Admin and read/write access to built-in users." but exactly what it does, I don't know (Cryptography?).

I see nothing that relates to any issues with RAM/SSD or other hardware, it looks like a driver/Service/permissions problem. I can't make head nor tail from the CBS log, way out of my comfort zone.

Code:

Debug session time: Sat Jul  9 11:59:12.569 2016 (UTC + 1:00)
Loading Dump File [C:\Users\Me\SysnativeBSODApps\070916-16937-01.dmp]
Built by: 9600.18340.amd64fre.winblue_ltsb.160513-1153
System Uptime: 0 days 0:00:05.406
Probably caused by : tpm.sys ( tpm!TpmTransportMemBase::UnmapMemoryFromAcpiTable+25 )
BugCheck 50, {fffff6e80030e000, 1, fffff800a8b27505, 9}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Bugcheck code 00000050
Arguments:
Arg1: fffff6e80030e000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800a8b27505, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 0000000000000009, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  AV_tpm!TpmTransportMemBase::UnmapMemoryFromAcpiTable
BiosVersion = A11
BiosReleaseDate = 05/26/2016
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 5555

*** 3rd PARTY DRIVER LIST *** for info only.

Code:

DellRbtn.sys  Fri Aug  3 22:32:54 2012 (501C4386)
NETwbw02.sys  Thu Sep 19 08:40:12 2013 (523AAA5C)
Rt630x64.sys  Fri May 10 10:59:08 2013 (518CC4EC)
amdpsp.sys  Fri Apr 22 16:20:07 2016 (571A4127)

[url=http://www.carrona.org/drivers/driver.php?id=DellRbtn.sys]http://www.carrona.org/drivers/driver.php?id=[B][COLOR=BLUE]DellRbtn.sys[/COLOR][/B][/url]
[url=http://www.carrona.org/drivers/driver.php?id=NETwbw02.sys]http://www.carrona.org/drivers/driver.php?id=[B][COLOR=BLUE]NETwbw02.sys[/COLOR][/B][/url]
[url=http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys]http://www.carrona.org/drivers/driver.php?id=[B][COLOR=BLUE]Rt630x64.sys[/COLOR][/B][/url]
[color=#777777][color=#4b0082]amdpsp.sys[/color] - 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.[/color]


  --- E O J ---  2016 Jul 10 22:05:45 PM  _98-dbug  Copyright 2012 Sysnative Forums

Stack Text (info only)

Code:

**************************Sat Jul  9 11:59:12.569 2016 (UTC + 1:00)**************************
STACK_TEXT:  
ffffd000`5cf8da98 fffff800`a8c121b2 : 00000000`00000050 fffff6e8`0030e000 00000000`00000001 ffffd000`5cf8dd00 : nt!KeBugCheckEx
ffffd000`5cf8daa0 fffff800`a8af8e39 : 00000000`00000001 ffffe001`01673040 ffffd000`5cf8dd00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x268f2
ffffd000`5cf8db40 fffff800`a8be562f : 00000000`00000001 fffff6e8`0030e000 fffff800`a8de1e00 ffffd000`5cf8deb0 : nt!MmAccessFault+0x769
ffffd000`5cf8dd00 fffff800`a8b27505 : fffff6e8`00307c00 00000000`00000000 00000000`00100000 fffff800`a8be5757 : nt!KiPageFault+0x12f
ffffd000`5cf8de90 fffff800`a8b273d6 : ffffe001`0435cb40 00000000`00000001 ffffe001`040c6240 00000001`7f775863 : nt!MiRemoveIoSpaceMap+0xd5
ffffd000`5cf8dff0 fffff800`c181f389 : ffffe001`0435d210 00000000`00000001 ffffe001`0435d210 00000000`00000018 : nt!MmUnmapIoSpace+0x6e
ffffd000`5cf8e020 fffff800`c181e148 : 00000000`00000001 00000000`00000001 ffffe001`0435d210 ffffe001`0435d210 : tpm!TpmTransportMemBase::UnmapMemoryFromAcpiTable+0x25
ffffd000`5cf8e050 fffff800`c18207e8 : 00000000`00000001 ffffe001`036cda00 ffffe001`0435cb40 ffffe001`0000000a : tpm!TpmTransportMemBase::~TpmTransportMemBase+0x38
ffffd000`5cf8e090 fffff800`c181d58c : ffffe001`0435d4a0 ffffe001`036c0000 ffffe001`0435cc20 ffffe001`036cda00 : tpm!TpmTransportACPI::`vector deleting destructor'+0x14
ffffd000`5cf8e0c0 fffff800`c18149bf : ffffe001`0435d4a0 00000000`00000001 ffffe001`036cda00 ffffd000`5cf8e1c8 : tpm!TpmTransport::DeleteTpmTransport+0x14
ffffd000`5cf8e0f0 fffff800`bfe3f763 : ffffe001`036cd710 00001ffe`fc9328e8 ffffe001`036cd730 ffffc000`44ff4460 : tpm!TpmEvtDeviceContextCleanup+0x16b
ffffd000`5cf8e130 fffff800`bfe4b627 : fffff800`bfedd700 00000000`00000001 00000000`00000000 00000000`00000000 : Wdf01000!FxObject::DisposeChildrenWorker+0xc3
ffffd000`5cf8e1b0 fffff800`bfe4b46f : ffffe001`036cd710 00000000`00000000 ffffe001`036cd701 ffffe001`040c4190 : Wdf01000!FxObject::PerformDisposingDisposeChildrenLocked+0x57
ffffd000`5cf8e220 fffff800`bfe4b58c : ffffe001`036cd710 ffffd000`5cf8e400 ffffd000`5cf8e400 00000000`00000000 : Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0x5f
ffffd000`5cf8e290 fffff800`bfe5f1aa : ffffe001`040c4a50 ffffd000`5cf8e400 00000000`00000124 ffffe001`043f81b0 : Wdf01000!FxObject::EarlyDispose+0x5c
ffffd000`5cf8e2f0 fffff800`bfed45c1 : ffffd000`5cf8e400 00000000`00000124 ffffd000`5cf8e400 00000000`00000124 : Wdf01000!FxPkgPnp::PnpEventRemovedCommonCode+0xaa
ffffd000`5cf8e360 fffff800`bfe4d942 : 00000000`00000124 ffffd000`5cf8e400 00000000`00000136 ffffe001`01601290 : Wdf01000!FxPkgFdo::PnpEventFdoRemovedOverload+0x9
ffffd000`5cf8e390 fffff800`bfe4da5a : ffffe001`040c4ba8 00000000`00000002 ffffe001`040c4a50 ffffe001`040c4b00 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x102
ffffd000`5cf8e420 fffff800`bfe4dbc4 : 00000000`00000000 ffffd000`5cf8e510 ffffe001`040c4b80 fffff800`a8a95860 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0xc2
ffffd000`5cf8e4a0 fffff800`bfe60c80 : 00000000`00000000 00000000`00000001 ffffd000`5cf8e620 ffffd000`5cf8e5e0 : Wdf01000!FxPkgPnp::PnpProcessEvent+0xe4
ffffd000`5cf8e540 fffff800`bfe48936 : ffffe001`040c4a50 ffffd000`5cf8e610 00000000`00000000 ffffe001`040c6240 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0xb4
ffffd000`5cf8e5b0 fffff800`bfe43a18 : ffffe001`03e4bcf0 ffffe001`03e4bcf0 00000000`0000001b ffffe001`036cd710 : Wdf01000!FxPkgPnp::Dispatch+0xd2
ffffd000`5cf8e620 fffff800`a8edcaf6 : 00000000`00000000 ffffe001`035fb760 ffffd000`5cf8e7b0 00000000`00000003 : Wdf01000!FxDevice::DispatchWithLock+0x7d8
ffffd000`5cf8e700 fffff800`a8f4ae70 : 00000000`00000002 ffffd000`5cf8e7c9 ffffe001`02327010 ffffe001`0228f060 : nt!IopSynchronousCall+0xfe
ffffd000`5cf8e770 fffff800`a8b9ded6 : ffffc000`4eb151e0 00000000`0000000a ffffe001`02327010 00000000`0000000a : nt!IopRemoveDevice+0xe0
ffffd000`5cf8e830 fffff800`a8f4a875 : ffffe001`0228f060 ffffe001`02327010 ffffc000`4eb11530 ffffe001`0228f060 : nt!PnpRemoveLockedDeviceNode+0xf2
ffffd000`5cf8e890 fffff800`a8f4a7ee : 00000000`00000000 ffffc000`4eb11530 ffffe001`02327010 00000000`3f051397 : nt!PnpDeleteLockedDeviceNode+0x4d
ffffd000`5cf8e8d0 fffff800`a8f49c01 : ffffe001`0228f060 ffffd000`00000002 00000000`00000000 00000000`00000001 : nt!PnpDeleteLockedDeviceNodes+0x9a
ffffd000`5cf8e950 fffff800`a8ee46a1 : ffffc000`4eb15100 00000000`00000001 ffffc000`00000006 00000000`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x539
ffffd000`5cf8eab0 fffff800`a8ee4ae7 : ffffc000`4eb151e0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x9d
ffffd000`5cf8eaf0 fffff800`a8b41a2f : fffff800`a8ee47c8 ffffc000`4eb15990 ffffe001`01727040 ffffe001`035f4150 : nt!PnpDeviceEventWorker+0x31f
ffffd000`5cf8eb50 fffff800`a8b87c10 : 00000000`00000065 ffffe001`01727040 00000000`00000080 ffffe001`01727040 : nt!ExpWorkerThread+0x69f
ffffd000`5cf8ec00 fffff800`a8be19c6 : fffff800`a8d8a180 ffffe001`01727040 ffffe001`0172d040 000e3d30`00000003 : nt!PspSystemThreadStartup+0x58
ffffd000`5cf8ec60 00000000`00000000 : ffffd000`5cf8f000 ffffd000`5cf89000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

 

OK Satrow, thanks.

That AMDPSP.SYS is in the last group of 5 Updates and it's one that MS says is "important". But, it's the one being supplied by MS and not AMD.

I blanked and wiped the partition that Win 8.1 Pro was on and will re-install Windows. I have updates set to notify me but let me choose whether to download and install. I'll make sure to hide that PSP update and see if the problem clears.

That PSP update is installed on Win 8.1 Core (OEM) and hasn't caused this issue. But, we'll see. I'll post back here tomorrow.

 

If you chase up the TPM link and find Dell's implementation of it, you should be able (again, I think, not an area I've studied) to temporarily set the TPM so that the update can access it, once that's done and updated, reset the TPM to whatever it was originally... ?

 

Well, this time I hid ALL device drivers that Microsoft listed. I was fine until the last group of updates which were Security Updates for .NET Framework 4.5.2 and one other that I can't remember but, it WASN'T a device driver. Clicked Restart to complete installation and after the computer restarted, I got that same PageFault error.

There, apparently, was a Restore Point created and Automatic Repair brought up a "Restore" button which I clicked and was able to boot to Win 10 Pro after Restore completed. I don't know how many Updates were lost in Win 8.1 Pro but, now, I'm afraid to re-install those that were lost.

I don't know why this is happening in Win 8.1 Pro but didn't happen in Win 8.1 Core (of course 8.1 Core is OEM and Win 8.1 Pro is Retail).

 

If 8.1 Core = the Dell -supplied OS, then that will have been modified (from the MS original) to suit the hardware supplied.

 

I found that all 49 Updates in the first batch were deleted. I re-installed them and created a Restore Point immediately after the successful installation.

I checked for Updates again and the .NET framework 4.5.2 Updates came up again. I chose to install those one at a time creating Restore Points after each one. The third Update dated 5/9/16 blue screened the computer but, there was no cause listed in the blue screen — just a plain blue screen. I restarted using the Power Button. I've hidden those 4 .NET Framework 4.5.2 Security Updates.

As far as Device Drivers and other Software for this Inspiron, I intend to get those directly from Dell Support like I did the last time I installed Win 8.1 Pro. But, at least Win 8.1 Pro is installed, patched (except for the .NET Framework Updates I hid) and is running now.

If I get another laptop, I'm going to make sure it has an Intel Processor. AMD hasn't impressed me. It's slower and I've found it's more problematic.

 

You could attach the new, zipped dump file?

 

It seems I spoke too soon. I posted my last entry in Win 10, restarted the laptop to go into Win 8.1 Pro and got that D*mn Page Fault in non Paged Area BSOD again. WTF!

It seems I can no longer run Core and Pro side-by-side on this POS machine. I don't have problems on my Intel based laptop.

 

Yup, looks identical to me. I reckon the only way to get Pro running and fully updated on that PC is to chase up Dell on the TPM issue (it's nothing to do with it being on an AMD chip, as far as I can tell + the Dell-supplied core version works and updates), as it's their implementation that's clashing with whatever MS expects of it.

Get on the Dell site and search for clues, ask questions in their forum. It's still under warranty, kick up a fuss (politely).

 

Well, I've got another idea. I'll delete the partition containing 8.1 Pro and use WinToUSB and put 8.1 Pro on an external drive if I want to run it on this machine (which I do). It's the implementation of 8.1 Core that's causing the problem. Initially, I had deleted all of the partitions on the hard drive and tried installing 8.1 Pro. Because of the UEFI embedded Product Key, it got changed to Core. I re-installed Core and installed Pro on another partition and the first time I did this, 8.1 Pro worked along side 8.1 Core. Now...

I don't want to be arguing with Dell. I just want my computer to work the way I want it to. It's bad enough I have to leave it in Legacy Boot and can't boot from a GPT disk.

 

Believe it or not, that same PageFault error occurred today in Windows 8.1 Core after installing Windows Updates. It's got to be a problem with the RAM or SSD (most likely the RAM).

I'll pull both modules, compressed air the slots and the module contacts, reseat the modules and see if that solves the problem. If it doesn't, it means the SSD is going bad (I did buy it used) and I'll have to put the original HDD back in and re-install everything. I can't afford a new SSD at this time. Even Automatic Repair -> Restore couldn't get me to the Metro Bootloader.

 

Well, I ran MemTest86+ for 7 passes after pulling, air dusting and re-seating the modules. It found no errors. I could only run Fail Safe single thread.

I ran SSDLife Pro's diagnostics on the SSD and it showed 100% healthy and over 8 years of remaining life for the SSD (over 9 years for my other SSD) so, I know the issues haven't been hardware related.

I posted a thread on Dell Community Forums and haven't heard squat from them. Maybe my next laptop will be a Lenovo?

 

The Community forum can't open a ticket with Dell for you.

 

So where should I post it? I didn't know I'd have to open a ticket.

 

Dell Support?

 

Try here.
http://www.dell.com/support/home/uk/en/ukdhs1/Products/

 

Mine's US not UK.

 

Then go here.
http://www.dell.com/support/home/us/en/19/Products/

 

Just went to Dell Support again (Via Eldon's link). Apparently, opening a "ticket" is one time fee based (I'm not paying it).

I'm going to try using an unaltered Win 8.1 Pro installation DVD (I was using an NTLited DVD).

 

You bought the machine this year, you can get support from Dell for free.

 

I didn't buy it from Dell though. I bought it from a reseller on Amazon.com although, Dell is honoring the remainder of it's warranty.

I'll see how things go after re-installing Win 8.1 Pro.

 

Dell might honour the remaining warranty if you contacted them about your problem - otherwise it's just words.

 

Apparently, it was my RAM not being seated properly when I WAS having the PAGEFAULT issue. I had pulled the modules, air dusted the slots and contacts, reseated the RAM and ran MemTest86+ for 7 passes with no errors.

I just finished re-installing Win 8.1 Pro and all of the patches successfully. 8.1 Core and 8.1 Pro are running peacefully along with 10 Pro and 10 Pro Insider. Phew!

 

Hmm, that doesn't sound right.

 

I don't know what you mean by that. Dell says that the PAGEFAULT error was due to improper seating of RAM. I've apparently corrected that issue because all of the Windows versions I wanted to run on this Inspiron are now running.

 

Improperly seated RAM only affects the one OS, not the other(s)? Nah, that just doesn't sound right, a hardware fault should hit all OS'.

 

Well, then, it must have been the NTLited ISO I used when I was having the issue. I used an unaltered ISO this time. The AMD PSP.SYS you mentioned previously is installed and not creating any problems. I did have a brief problem when installing the Dell Realtek High Definition Audio Driver for this laptop but Auto Repair had me restart the laptop and the problem was corrected. All of the Dell supplied drivers are installed as well. This time I even got a Recovery ISO (Win 8.1 Core Single Language x64).

I hated having to download and install 242 Windows Updates but, they ALL installed successfully and now I can re-install my programs.

 

Yup, a bad source I can believe