XPS13 (9343) Win10 Page Fault in NonPaged Area

I am experiencing exactly the same error in Windows 10 on my XPS 13 (infinity screen with touch).

I normally get the crash within half hour of login.

I have also updated BIOS and suggested drivers to no avail.

Basic hardware tests all pass. However, when I ran the thorough memory test I got the above error whilst it was part way through the test.

I thought that this was probably a memory hardware issue.

Any help on this would be much appreciated.

I've been having the exact same problem for the last two days. Did you find a way to fix it? 

It's fixed after 55 min on the phone w/ the guy performing test after test. It was a software issue -something that has not updated as it should to keep Windows 10 happy...

You seem more able than me since all I did on my own was a factory reset which actually made things worse. So if you don't want to go with the phone or chat, there is something else available on the dell online tech support site. Unfortunately I can't remember exactly how I ended up there -I was clicking away in full panic mode while dreading the inevitable blue screen which kept coming every 5 minutes by the third day.

Anyway, I did come across a diagnosis tailored for "blue screen" and it DID actually report the exact same problem that the tech guy finally caught:  the "Dell Wireless 1560 802.11ac" listed under Network adapters in Device Manager. The thing is I did check it for myself before the phone tech guy did and both times, it did NOT show the yellow exclamation point that is supposed to be there when there is a problem. I figured I should share that info with you in case your Device Manager is lying to you as well!

Do let me know when you figure it out. Good luck to you.

Thanks alot it worked for me!

Hi is there an actual solutiion to this... Sorry but I dont see it above. I am having the same problem

Hi is there an actual solutiion to this... Sorry but I dont see it above. I am having the same problem

credits to isik111

go to settings> search device manager> network adapters> Dell Wireless 1560 802.11ac> right ckick> uninstall> reboot

i did that and from then i'm blue screen free!

hope this will help

When I run who crashed i get 

On Tue 10/6/2015 8:07:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100615-6671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x50 (0xFFFFF6FB400037A8, 0x0, 0x0, 0x6)
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 Tue 10/6/2015 8:07:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: bcmwl63a.sys (bcmwl63a+0x8E64F)
Bugcheck code: 0x50 (0xFFFFF6FB400037A8, 0x0, 0x0, 0x6)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\bcmwl63a.sys
product: Broadcom WiFi Driver wireless driver
company: Broadcom Corp
description: Broadcom WiFi Driver wireless driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwl63a.sys (Broadcom WiFi Driver wireless driver, Broadcom Corp).
Google query: Broadcom Corp PAGE_FAULT_IN_NONPAGED_AREA

So i know it is something with the wirelesss adapter i just can't seem to fix it. 

I've tried this multiple times... unfortunately I have the same problem. I've even tried to roll back the drivers and I have the same problem.. super frustrating as I have already had the SSD replaced because it was defective. this laptop has been a massive headache. 

Has anyone had any luck fixing this?  Same thing here.. looks like dell did an update for me on the 6th and now I'm crashing with a BSOD every 20 minutes.  Same dumps.  looks like wireless problems.

The problem got worse and worse every single day for me, being unbearable today,  so I went ahead an uninstalled the wifi driver as people before suggested and it was good for an hour, but then it happened again...

What worries me is that, this started being a problem beginning of October, yet when checking for drivers updates the last version of the wifi driver is from August so something else is involved...

I rolled the wifi driver back to ver 6.30 and now all my problems are gone.  It wasn't easy as I had no option to roll back in my device manager settings.  Somewhere in these forums (sorry don't remember where) but someone else explained downloading the old install exe for the 6.3 broadcom drivers.  So I uninstalled the wireless driver , ran the setup for the 6.3 drivers and now I'm all good.

As a side note I noticed this got particularly bad while on the road.  May be exacerbated by the wireless connection at the hotel.

Have you got Hyper-V installed? My XPS 13 crashed constantly with that BSOD until I uninstalled the hypervisor.

After I updated wifi driver, I had connection issues but it was livable with. Now the blue screen issue I reverted back and assuming the problem is related to wifi driver. I will report back.

Hi Guys,

I had the same issue, and was able to SOLVED it finally. My XPS has crash-free for 2 weeks now!!

It turned out that MS onedrive is responsible. Go to System Configuration- Startup- open task manager.

then disable MS OneDrive.

Let me know how it goes..

It was the same for me. XPS 13 (9343) and, right after installing Hyper-V, the BSODs started (every time I tried to download a large file in Google Chrome - so it may be something related to the network driver indeed). After uninstalling Hyper-V, everything went back to normal.