1.    15 Apr 2017 #1
    Join Date : Apr 2015
    Port Neches, Texas
    Posts : 238
    Windows 10 Home

    Creators Upgrade--multiple BSOD'S "Page Fault in non-paged area".


    Upgrade to 15063.0 and everything is fine on a Toshiba Laptop that has been running Windows 10 since July, 2016 upgrade from Windows 8.1 flawlessly.

    Further update to 15063.138 (KB4015583) produces BSOD'S when trying to run any one of a number of speed tests or Earthcam (Variety of live cameras around the world). Get message "Page fault in non-paged area"). Have tried install 3 times with same result. Have uninstalled Flash Player and reinstalled with no help. Have uninstalled Display Adapter and reinstalled with no help. Below are the files you require from the latest event.

    I could roll back again but I would like to keep the full Creator Update if possible.
      My ComputerSystem Spec
  2.    15 Apr 2017 #2
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,345
    Windows 10 Pro X64 16299.19

    I suggest doing a roll back to see if that resolves the problem. If it does, then make sure you have a good, full image backup then apply the 138 update again. Meanwhile I'll take a look at the dump(s) you uploaded.

    Edit: Still can't do anything useful with the dump as Microsoft has not uploaded the symbols for any of the 15063 builds yet.
      My ComputersSystem Spec
  3.    15 Apr 2017 #3
    Join Date : Apr 2015
    Port Neches, Texas
    Posts : 238
    Windows 10 Home
    Thread Starter

    I've done the rollback several times, Rich, but I'll do it again.

    C.B.
      My ComputerSystem Spec
  4.    15 Apr 2017 #4
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,345
    Windows 10 Pro X64 16299.19

    Did the rollback resolve the problem?

    Edit: Still can't do anything useful with the dump as Microsoft has not uploaded the symbols for any of the 15063 builds yet.
      My ComputersSystem Spec
  5.    15 Apr 2017 #5
    Join Date : Apr 2015
    Port Neches, Texas
    Posts : 238
    Windows 10 Home
    Thread Starter

    No. The uninstall of the update .138 returning to 15063.0 did not solve the problem. Earlier today, however, before posting here, I had rolled back to 14393.1066 which was completely troublefree and then reinstalled to 15063.0 and all seemed to be fine also. Then updated to 15063.138 and trouble was back. Just now back to 15063.0 from .138 and problem remains.

    I will now go back to 14393.1066 again and update to 15063.0 and use winshowhide to prevent update to 15063.138 unless you have any further advice. This, of course, will require several hours.

    Thank you very much for your help, Rich.

    C.B.
      My ComputerSystem Spec
  6.    15 Apr 2017 #6
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,345
    Windows 10 Pro X64 16299.19

    Probably the best thing to do for now, until Microsoft releases the symbol files for this build.
      My ComputersSystem Spec
  7.    15 Apr 2017 #7
    Join Date : Apr 2015
    Port Neches, Texas
    Posts : 238
    Windows 10 Home
    Thread Starter

    Thanks again for your valued help.
      My ComputerSystem Spec
  8.    15 Apr 2017 #8
    Join Date : Apr 2015
    Port Neches, Texas
    Posts : 238
    Windows 10 Home
    Thread Starter

    Rolled back to 14393.1066 and reinstalled 15063.0 and all is well. I'm using wushowhide to prevent further update to 15063.138.

    C.B.
      My ComputerSystem Spec
  9.    19 Apr 2017 #9
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,345
    Windows 10 Pro X64 16299.19

    Finally got windbg working. Looks like it was a corrupted symbol file cache folder on my hard drive that was causing most of the problems. Wiped and reinstalled all of it and now when I look at the dump you uploaded, I see a problem with bcmwl63a.sys
    Code:
    BugCheck 50, {ffff9a00006f56d8, 0, fffff80318ef03d3, 2}
    *** WARNING: Unable to verify timestamp for bcmwl63a.sys
    *** ERROR: Module load completed but symbols could not be loaded for bcmwl63a.sys
    Could not read faulting driver name
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    Followup:     memory_corruption
    ---------
    Driver Description: Broadcom 802.11 Network Adapter wireless driver

    What you have is: 8/27/2015 6:01:04 AM C:\WINDOWS\system32\DRIVERS\bcmwl63a.sys. See if you can find a newer driver for your wireless. Also would be a good idea to test your RAM. You have 8GB so an overnight run ould be the best bet of getting a full 8 passes which is the minimum needed.
    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
      My ComputersSystem Spec

 


Similar Threads
Thread Forum
BSOD irql_not_less_or_equal / Page fault in non-paged area
I've been having numerous BSODs at different times under different loads and under different temperatures. I've experienced them mostly when playing video games or watching media. My graphics cards never reach above 83 degrees and my CPU stays...
BSOD Crashes and Debugging
BSOD Page Fault in Non Paged Area NDIS.SYS Help!
Since last Thursday I have been getting a BSOD message which says "Page Fault in Non Paged Area" with source of the issue the "nsid.sys" file when I start my desktop PC. Resetting the PC will not work. Autorepair is also unable to fix the problem. I...
BSOD Crashes and Debugging
BSOD on Startup only - page fault in non paged area
Hi, I recently experienced this BSOD and i can't seem to locate whats been giving me this problem from event viewer, i suspect it maybe related to a driver? However im not too sure since i did install a several drivers prior to this, and i couldnt...
BSOD Crashes and Debugging
qbittorrent bsod says Page Fault in non Paged Area
I never encountered this problem until the past two days. Was it a new windows update? A driver? Help please!
BSOD Crashes and Debugging
BSOD Page fault in non-paged area error when using wifi
Hello, I've been having this BSOD problem for a few weeks now - it seems to be prompted when I'm transferring large amounts of data over my wifi connection. I have taken the following steps to try and identify/fix the problem without success; 1)...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:15.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums