Windows 10: BSOD page_fault_in_nonpaged_area mcupdate_authenticamd.dll

Hi,

I've been getting some BSODs lately and it intensifies. I don't really know what causes them, it seems completely random to me. I've been lurking here but didn't find anything i could use to solve my problem, so i thought i'd start a new one. Sorry if i missed something.

My younger cousin has been using this notebook lately, but i think he couldn't mess things up this much. I've already tried to clean up after him, haha.

I'll be grateful for any help.

Attachment 32006

Sorry for my english.

:)

 

BSOD - Memory Management and other errors on newly installed Windows 10

Was one of the BSoDs PAGE_FAULT_IN_NONPAGED_AREA?

 

How to deal with BSOD (PAGE_FAULT_IN_NONPAGED_AREA)

Repeated BSOD with error PAGE_FAULT_IN_NONPAGED_AREA (HipShieldK.sys)

solution?

 

Ocenvo, I looked at your last 5 dumps and they were all the same

Code: Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff6fb400037a8, 0, 0, 6} *** 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 Probably caused by : bcmwl63a.sys ( bcmwl63a+8ea6f ) Followup: MachineOwner[/quote] That is your Broadcom 802.11 Network Adapter wireless driver. You need to try to find a Windows 10 driver from Lenovo if you can.

I need you to also fill out your system specs as detailed as possible.

Please go to your last post and in the bottom left corner click 'My System Specs'. there is a link there to update your system specs, click it and fill them all out in as much detail as possible. Please list Manufacturer and Model, and list Desktop or Laptop. If it is an OEM, please list the Manufacturer and Model number. If you would like to know what we would like, please click 'My System Specs' at the bottom left of this post and see mine.

 

That is your Broadcom 802.11 Network Adapter wireless driver. You need to try to find a Windows 10 driver from Lenovo if you can.

I need you to also fill out your system specs as detailed as possible.

Please go to your last post and in the bottom left corner click 'My System Specs'. there is a link there to update your system specs, click it and fill them all out in as much detail as possible. Please list Manufacturer and Model, and list Desktop or Laptop. If it is an OEM, please list the Manufacturer and Model number. If you would like to know what we would like, please click 'My System Specs' at the bottom left of this post and see mine.[/quote]
Thank you for your response.
I tried to fill everthing I could find, but it's not much.
I also tried to uninstall the only broadcom software i found, but couldn't find any windows 10 version (and BSOD appeared about an hour after I did that). What should I do next?

 

In device manager, expand Network Adaptors and you should find Broadcom 802.11 Network Adapter. Right click it and select properties, click on the Driver Tab. It should show the installed driver. You can uninstall it from there. But, before doing that, make sure you have a replacement driver. Otherwise your Wireless will not work. See if you can find a Windows 8 driver from Lenovo. In most cases, a windows 8 driver will work.

 

Ok, i've uninstalled the driver and installed the one from lenovo website, everything seemed to be fine but now i got another BSOD (and another two about 3 minutes after each start). Is there any other possible cause?

 

Please upload the BSOD Posting instructions Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.

 

You mean upload the new debug folder here? Sorry, i'm a little confused.

 

Follow the links marked in blue and upload a new folder just like you did in post # 1.

 

I looked at your dump files and they are the same as before

Code: Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff6fb400037a8, 0, 0, 6} *** 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 Probably caused by : bcmwl63a.sys ( bcmwl63a+8ef6f ) Followup: MachineOwner[/quote]