Windows 10 BSOD on ntoskrnl.exe and bcmwl63a.sys

Nicholas_97

Commendable
May 2, 2017
11
0
1,510
Hello, I'm having a serious problem with my Windows 10. It keeps causing BSOD caused by ntoskrnl.exe and bcmwl63a.sys. I tried to fix this for weeks now but it is still there.

Here are the following dump files:

crash dump file: C:\WINDOWS\Minidump\050217-4578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x50 (0xFFFF8A80006F56D8, 0x0, 0xFFFFF8001E8DB3D3, 0x2)
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

crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: bcmwl63a.sys (bcmwl63a+0xE1D1F)
Bugcheck code: 0x50 (0xFFFF8A80006F56D8, 0x0, 0xFFFFF8001E8DB3D3, 0x2)
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


As for the bcmwl63a.sys, it's weird because I do not have this wireless driver on my device manager. In fact, I'm using an Asus PCE68 wireless driver for my wifi.

 
asus just uses the broadcom chips so broadcom makes the driver.
Broadcom 802.11 Network Adapter wireless driver
your asus board uses BCM4360 chip
you should see if asus has a updated driver, otherwise you might be able to install the generic driver for the chip

 


I have the latest driver version 7.35.315.0 based on the website :https://www.asus.com/sg/Networking/PCEAC68/HelpDesk_Download/
 
you also want to make sure that that driver is selected as the default one.
when you install a new network driver it does not always pick it as the default.

go into control panel, device manager, find the network adapter, right mouse click on properties,
browse for drivers on your computer, select let me pick form a list of available drivers
it should give you a list (that may or not have dates or versions but they are different versions)
I checked on my windows 10 and I have 6 intel(r) ethernet connection(2) 1218-v entries
with no way to tell them apart without installing them and checking the driver build number

normally i would use the PNPutil.exe and remove all of the older versions of the driver.


for my second network adapter, I have 12 entries but they show a version number and a date with each entry. (not sorted by date)



 


Ok I have done that. I will let you know if the problem is still there
 


Regarding the BSOD caused by ntoskrnl.exe. I can't seem to find the source of the problem. Is it also related to my wifi driver?
 
the kernel is the interface for device drivers, when a bugcheck is called it will be in the device driver or the kernel code that the device driver called.

if you put the current memory dump from c:\windows\minidump directory on a server like microsoft one drive, share the file for public access and post a link. I can take a quick look in the debugger.




 


Here is the link: https://1drv.ms/u/s!Ao2gnEmuc5l5kFvt5Si2U9ghbjEI. The file is 050217-4578-01.dmp

Please let me know if you have any difficulty accessing the link
 
make sure the file is shared for public access, i could not get to it



 


https://1drv.ms/f/s!Ao2gnEmuc5l5gQxiLPhU14tAgIXn. There you go, i have placed in a public folder
 
I would try and force a memory dump before the system crashes and post a link
------
memory dump corrupted.
I think some driver is using up all of your nonpaged pool
basically, pool is memory resources that drivers share, nonpaged means that it can not be swapped to the hard drive virtual memory (c:\pagefile.sys)

normally you would run poolmon.exe from the windows ddk and watch to see what drivers are using up all of the nonpaged pool. then get a driver update.

the minidump was corrupted and would not provide the correct info anyway. You need to change the memory dump type to kernel, reboot and provide a kernel memory dump.

it took your system a day and 4 hours to run out of non paged pool. you might google
"how to force a memory dump using a keyboard" make the registry change (and the memory dump type change) reboot and use the system for a few hours and force a memory dump.

this way, there will be enough resources to do a proper memory dump and the driver would have enough time to eat up a bunch of non paged pool so it can be easy to spot.

the new memory dump will be at c:\windows\memory.dmp

if I were to guess the driver is going to be
CorsairVHidD, or WinRing0x64. or wdcsam64.sys
(but it is just a guess)








------
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
System Uptime: 1 days 3:59:56.361

machine info:
BIOS Version 1.D0
BIOS Starting Address Segment f000
BIOS Release Date 12/16/2016
Product Z170A GAMING M5 (MS-7977)
Version 1.0
Processor Version Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 4000MHz

memory:
Part Number F4-2800C15-8GVR
Speed 2800MHz