BSOD - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Question

I get frequent BSOD crashes (>1 per day) with different codes, identifying different possible modules

A mini-dump is below. I have other dumps from other BSODs.

Q1: How can I diagnose the problem?

The procedure at https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors is not a diagnostic procedure, but a 'try everything' procedure. It's no help in this situation; for example, step 2 is 'update drivers'. The instruction page https://support.microsoft.com/en-us/help/4028443/windows-update-drivers-in-windows-10 says 'While it's likely you already have the most recent driver, if you're having trouble with a device, you can try fixing it by updating the driver or reinstalling it.' Sure. The problem is I don't know what device it might be - or if a device is actually causing the problem. 

Q2: So do I have to update all drivers? If so, how (Please, not one at a time!)?

Surely having multiple memory dumps with different error codes should provide enough data for an (automated) analysis of the root cause?

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 16299 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff8011208e000 PsLoadedModuleList = 0xfffff801123f5130

Debug session time: Sat Mar 17 09:55:22.899 2018 (UTC - 4:00)

System Uptime: 0 days 19:23:03.580

Loading Kernel Symbols

.............

Loading User Symbols

Loading unloaded module list

*******************************************************************************

*                        Bugcheck Analysis                                    *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff8059d70124a, ffffc082a31807c8, ffffc082a3180010}

Probably caused by : bcmwl63al.sys ( bcmwl63al!wlc_bmac_led_hw_deinit+671 )

Followup:     MachineOwner

Analyze:

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This is a very common bugcheck.  Usually the exception address pinpoints

the driver/function that caused the problem.  Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003.  This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG.  This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG.  This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc000001d, The exception code that was not handled

Arg2: fffff8059d70124a, The address that the exception occurred at

Arg3: ffffc082a31807c8, Exception Record Address

Arg4: ffffc082a3180010, Context Record Address

Debugging Details:

---

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.309 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  10A7CTO1WW

SYSTEM_SKU:  LENOVO_MT_10A7

SYSTEM_VERSION:  ThinkCentre M93p

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  FBKTCPAUS

BIOS_DATE:  12/13/2017

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  SHARKBAY

BASEBOARD_VERSION:  SDK0E50510 WIN

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff8059d70124a

BUGCHECK_P3: ffffc082a31807c8

BUGCHECK_P4: ffffc082a3180010

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP:

ndis!NdisCancelTimerObject+6a

fffff805`9d70124a f6411a02        test    byte ptr [rcx+1Ah],2

EXCEPTION_RECORD:  ffffc082a31807c8 -- (.exr 0xffffc082a31807c8)

ExceptionAddress: fffff8059d70124a (ndis!NdisCancelTimerObject+0x000000000000006a)

   ExceptionCode: c000001d (Illegal instruction)

  ExceptionFlags: 00000000

NumberParameters: 0

CONTEXT:  ffffc082a3180010 -- (.cxr 0xffffc082a3180010)

rax=ffff9388983ec100 rbx=ffff938898f49bf0 rcx=0000000000000000

rdx=0000000000001420 rsi=0000000000000011 rdi=ffff938898f49f01

rip=fffff8059d70124a rsp=ffffc082a3180a00 rbp=ffff938898f49fd8

 r8=ffff938898f49c30  r9=fffff8011208e000 r10=0000000000000045

r11=ffffc082a31809c8 r12=0000000000000001 r13=0000000000000000

r14=ffff938898f49cd0 r15=ffff938898f44e60

iopl=0         nv up ei pl zr na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246

ndis!NdisCancelTimerObject+0x6a:

fffff8059d70124a f6411a02        test    byte ptr [rcx+1Ah],2 ds:002b:000000000000001a=??

Resetting default scope

CPU_COUNT: 8

CPU_MHZ: d40

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 23'00000000 (cache) 23'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR:  c000001d

ANALYSIS_SESSION_HOST:  LENOVO-PC

ANALYSIS_SESSION_TIME:  03-17-2018 10:37:12.0883

ANALYSIS_VERSION: 10.0.16299.91 x86fre

LAST_CONTROL_TRANSFER:  from fffff805a1df8371 to fffff8059d70124a

FAILED_INSTRUCTION_ADDRESS:

ndis!NdisCancelTimerObject+6a

fffff805`9d70124a f6411a02        test    byte ptr [rcx+1Ah],2

STACK_TEXT: 

ffffc082a3180a00 fffff805a1df8371 : ffff938896577410 fffff801109c8180 ffff9388965772b0 fffff805a1d85e6d : ndis!NdisCancelTimerObject+0x6a

ffffc082a3180a30 fffff805a1d86b8c : 000000000428d01a ffff938896577410 ffff9388983ec050 ffff938898078060 : bcmwl63al!wlc_bmac_led_hw_deinit+0x671

ffffc082a3180a80 fffff805a1f0e870 : ffff938896577000 ffff93889e28d7c0 0000000000000000 0000000000000000 : bcmwl63al!wl_free_timer+0x14c

ffffc082a3180ab0 fffff8059d766192 : ffff938898f3b670 0000000000000000 0000000000000000 fffff80500000000 : bcmwl63al!wl_queue_work_item+0x110

ffffc082a3180ae0 fffff8011219b28b : 0000000000000000 0000000000000000 ffff938800000000 ffff938892cac160 : ndis!ndisDispatchIoWorkItem+0x12

ffffc082a3180b10 fffff801120c94d5 : ffff938892cac160 ffff93889e28d680 fffff8011219b190 fffff8010000000c : nt!IopProcessWorkItem+0xfb

ffffc082a3180b80 fffff801121a4c07 : ffff93889e28d680 0000000000000080 ffff938892ca6100 ffff93889e28d680 : nt!ExpWorkerThread+0xf5

ffffc082a3180c10 fffff8011220acc6 : ffffd301227aa180 ffff93889e28d680 fffff801121a4bc0 0000000000000000 : nt!PspSystemThreadStartup+0x47

ffffc082a3180c60 0000000000000000 : ffffc082a3181000 ffffc082a317b000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC:  5a9d220ca97c0ee00654ca568d7d060b1550b896

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cc779ede60d22e43ad49bea433f8e93d1e6a8d93

THREAD_SHA1_HASH_MOD:  465d1c08e6a200480022a3099be45d7ca72fb138

FOLLOWUP_IP:

bcmwl63al!wlc_bmac_led_hw_deinit+671

fffff805`a1df8371 4c896b28        mov     qword ptr [rbx+28h],r13

FAULT_INSTR_CODE:  286b894c

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  bcmwl63al!wlc_bmac_led_hw_deinit+671

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl63al

IMAGE_NAME:  bcmwl63al.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5182c5da

IMAGE_VERSION:  5.100.245.200

STACK_COMMAND:  .cxr 0xffffc082a3180010 ; kb

BUCKET_ID_FUNC_OFFSET:  671

FAILURE_BUCKET_ID:  AV_BAD_IP_bcmwl63al!wlc_bmac_led_hw_deinit

BUCKET_ID:  AV_BAD_IP_bcmwl63al!wlc_bmac_led_hw_deinit

PRIMARY_PROBLEM_CLASS:  AV_BAD_IP_bcmwl63al!wlc_bmac_led_hw_deinit

TARGET_TIME:  2018-03-17T13:55:22.000Z

OSBUILD:  16299

OSSERVICEPACK:  309

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-03-01 00:36:55

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.309

ANALYSIS_SESSION_ELAPSED_TIME:  c6e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_bad_ip_bcmwl63al!wlc_bmac_led_hw_deinit

FAILURE_ID_HASH:  {7ce2dfb1-d634-29fd-982b-77dc21986199}

Followup:     MachineOwner

Answer 1

The error points to the  bcmwl63al.sys which is the Broadcom wireless driver:

Probably caused by : bcmwl63al.sys ( bcmwl63al!wlc_bmac_led_hw_deinit+671 )

Can you do the following:

In the Device Manager double-click the wireless adapter > Driver

What is the "Driver Version" ?

Then click on the  "Details" tab, then choose "Hardware Ids" from the drop-down menu under "Property".

What is listed under "Value"?