If you believe that this driver is causing the problem, Windows 10 comes with drivers to nearly all the hardware in the market. Why don't you use Windows 10 driver?. I PMed you the link for the driver released by Acer for Windows 10 x64.. Microsoft seems to suggest it is a hardware issue?? and another site suggests it is a software issue!!! By the way, don't you get the name of the offending system file after the message???
Arquivo Dump : 101715-8359-01.dmp Hora de criação : 17/10/2015 02:35:56 Canal de verificação de bugs: PAGE_FAULT_IN_NONPAGED_AREA Codigo de verificação de bugs: 0x00000050 Parametro 1 : fffff6fb`400037a8 Parametro 2 : 00000000`00000000 Parametro 3 : 00000000`00000000 Parametro 4 : 00000000`00000006 Causada pelo driver: mcupdate_AuthenticAMD.dll Causada pelo enderesso: mcupdate_AuthenticAMD.dll+aa541340 Descrição do arquivo: Nome do produto : Empresa : Versão do arquivo : Processo : x64 Crash Address : ntoskrnl.exe+14e2e0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Nome do Computador: Caminho completo : C:\Windows\Minidump\101715-8359-01.dmp Nome do processo : 4 Versão principal : 15 Versão menor : 10240 Dump File Size : 281 096 Dump File Time : 17/10/2015 02:36:26 ==================================================
I had this issue too and it would randomly happen. It drove me crazy. It turns out I needed to track down both the AMD IDE controller driver and the onboard ethernet adaptor driver. Microsoft's stock driver just wasn't doing any good. Check your event logs and see if you have any clue as to what warning or error you may had before you reached this blue screen
@perre, You have indicated that your notebook is "E5 551". Why are you trying to install Broadcom drivers when the Acer page says it should be Atheros??
mcupdate is the microcode update , so very likely the problem is in the bios. He should look for an update one.
So the windows 10 driver page dictates what hardware is on the Mobo. Search a few sites for answers as to how to find onboard hardware.
Are you confirming it is Broadcom because it is listed in your computer specification or you saw the chip or because Hardware ID reported "PCI\VEN_14E4&DEV_4365&SUBSYS_664511AD&REV_01" in device manager. I have seen incidents when windows reported the wrong Hardware ID, but the proper driver fixes the problem any way. Just for the sake of learning, if you go to Acer support site and insert your (E5 551) notebook details, do you get a driver for Atheros (as attached) or Broadcom (like the E5 511)? (my computer comes with Intel or Qualcomm or Ralink, but they are all listed) At the end of the day, you don't know what is the problem or how to solve it, nor any of who tried to help you, but you are the only one suffering from it. I hope you will be able to sort it, Good luck.
I want to thank all the help you gave me about me having BSOD. I did a clean installation of rtm windows, and installed these drivers who sent me 7.35.267_Win10_x86_x64_WHCK_driver_with_installshield and everything is working well. PS.Deixei windows install AMD drivers update windows, because before had the beta version 15.10.0.
I got this error too PAGE_FAULT_IN_NONPAGED_AREA and the screen didn't turn on after turn on computer, only just after several times of pressing the power button. Couple minutes ago windows 10 was freezing. So I uninstall video driver and let Win10 install it (before when I made clean install of Win10 I let it install video driver). I hope I don't get this error again or another one. Boot defrag can help ?
Boot-Defrag gave me a blabla.sys Error afterwards in a previous build and I had to remove the whole app via forced save-mode to get my sys fully booting again. So better be careful !
SSD 3-4 years, where the OS installed. HDD 9 years. I have installed Intel Desktop Utilities and it show all the hard drives are good. BTW, couple hours after when I try to type password to login, I got the BSOD with the error : KERNEL_SECURITY_CHECK_FAILURE. Before I installed Windows 10 10240, I almost not got BSOD.
KERNEL_SECURITY_CHECK_FAILURE thats related to bad mem or bad HD....check both again. swap them out if u can.