Windows Frustrations: Return of the BSOD on Startup

[RADD1]

I thought this issue was resolved. It's not. This is the old thread: http://www.tomshardware.com/forum/id-3159044/bsod-startup-error-message-time.html

For the last 6 days, I have had no issues with a BSOD; my laptop started in about 10 seconds, I got to the Windows landing screen without a BSOD. Now, the same problem I had in the previous thread has returned, yet what I did to seemingly resolve it last time isn't working this time.

Sequence of events of its return: I hit Fn+F12 to put the laptop to sleep. I went to wake it up about 3 hours later, so I tapped the power button (which I'm pretty sure is how you're supposed to wake it up) and I saw the splash screen momentarily, then I got the BSOD from before. The laptop proceeded to restart. Now, every time I start the laptop, I get the BSOD again.

When I got to run !analyze -v, I can't. It displays "Debugee not connected."

My questions from the last thread still stand. How should I proceed? (Thank you!)

 

[Colif]

you need to supply John with a copy of the memory dump like in last post and he will help you out again

 

[RADD1]

I've not been able to run !analyze -v properly to get detailed information; I was getting the "Debuggee not connected" error. I didn't think the dump that simply displays

Spoiler

Microsoft (R) Windows Debugger Version 10.0.14321.1024 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ubermann Laptop\Downloads\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.545.amd64fre.th2_release.160802-1857
Machine Name:
Kernel base = 0xfffff802`b7492000 PsLoadedModuleList = 0xfffff802`b776fcf0
Debug session time: Sat Sep 3 13:16:10.350 2016 (UTC - 4:00)
System Uptime: 0 days 0:22:08.050
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols

Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd0006f47b590, ffffd0006f47b4e8, 0}

would be useful. I sort of got around the "Debuggee not connected" issue by going to Debug>Break, but when I run !analyze -v, it just hangs on *Busy*, with the only resultant display of this command being

Spoiler

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0006f47b590, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0006f47b4e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

I didn't want to message john out of nowhere with another link to OneDrive without him first having indicated his consent to assist via replying to this thread. Thanks for your reply!

Update: Never mind, it does complete, but it took about 15 minutes for !analyze -v to do its thing on MEMORY.DMP. The result is:

Spoiler

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0006f47b590, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0006f47b4e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10586.545.amd64fre.th2_release.160802-1857

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: GT72S 6QD

SYSTEM_SKU: Default string

SYSTEM_VERSION: REV:1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: E1782IMS.109

BIOS_DATE: 09/19/2015

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MS-1782

BASEBOARD_VERSION: REV:1.0

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd0006f47b590

BUGCHECK_P3: ffffd0006f47b4e8

BUGCHECK_P4: 0

TRAP_FRAME: ffffd0006f47b590 -- (.trap 0xffffd0006f47b590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe0012b537e90 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe00123914f70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802b762735d rsp=ffffd0006f47b720 rbp=fffff802b77b1ae8
r8=ffffe0012b537eb0 r9=000000000000000b r10=ffffd0006f465180
r11=fffff802b7492000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x4405d:
fffff802`b762735d cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffd0006f47b4e8 -- (.exr 0xffffd0006f47b4e8)
ExceptionAddress: fffff802b762735d (nt! ?? ::FNODOBFM::`string'+0x000000000004405d)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 8

CPU_MHZ: a98

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 39'00000000 (cache) 39'00000000 (init)

DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

ANALYSIS_SESSION_HOST: UBERLAPTOP

ANALYSIS_SESSION_TIME: 09-03-2016 20:22:03.0703

ANALYSIS_VERSION: 10.0.14321.1024 x86fre

LAST_CONTROL_TRANSFER: from fffff802b75df4e9 to fffff802b75d4940

STACK_TEXT:
ffffd000`6f47b268 fffff802`b75df4e9 : 00000000`00000139 00000000`00000003 ffffd000`6f47b590 ffffd000`6f47b4e8 : nt!KeBugCheckEx
ffffd000`6f47b270 fffff802`b75df810 : 00000000`00000000 fffff802`b7521021 00000001`fa956b5b ffffd000`6f46aec8 : nt!KiBugCheckDispatch+0x69
ffffd000`6f47b3b0 fffff802`b75de9f3 : 00000000`00000007 00000000`00000002 fffff802`b7492000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd000`6f47b590 fffff802`b762735d : 00000001`fa97e213 ffffd000`6f46aec8 00000000`00000000 00000000`000000ff : nt!KiRaiseSecurityCheckFailure+0xf3
ffffd000`6f47b720 fffff802`b7565ff4 : ffffe001`2b537e70 ffffffff`00000000 00000000`00000002 ffffe001`0000000b : nt! ?? ::FNODOBFM::`string'+0x4405d
ffffd000`6f47b790 fffff801`3d2955c2 : ffffe001`2b537e50 ffffffff`ff676980 00000000`0000000b 00000000`00000000 : nt!KeSetTimerEx+0xa4
ffffd000`6f47b7f0 fffff801`40239b43 : ffffe001`22da0030 ffffffff`ff676980 00000000`00000000 00000000`000000ff : ndis!NdisSetTimerObject+0x82
ffffd000`6f47b840 ffffe001`22da0030 : ffffffff`ff676980 00000000`00000000 00000000`000000ff ffffe001`22da0030 : Qcamain10x64+0x59b43
ffffd000`6f47b848 ffffffff`ff676980 : 00000000`00000000 00000000`000000ff ffffe001`22da0030 fffff801`40239bd2 : 0xffffe001`22da0030
ffffd000`6f47b850 00000000`00000000 : 00000000`000000ff ffffe001`22da0030 fffff801`40239bd2 00000000`00000000 : 0xffffffff`ff676980


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 2d2247e092914624f90cd72c94c7fe62c5aea864

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: cf18188fe1a6b528163668f1e4cb7520787a3343

THREAD_SHA1_HASH_MOD: 685cc074fb8977777a711617996efb349f7559b8

FOLLOWUP_IP:
Qcamain10x64+59b43
fffff801`40239b43 b801000000 mov eax,1

FAULT_INSTR_CODE: 1b8

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: Qcamain10x64+59b43

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Qcamain10x64

IMAGE_NAME: Qcamain10x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55e6aebb

BUCKET_ID_FUNC_OFFSET: 59b43

FAILURE_BUCKET_ID: 0x139_3_Qcamain10x64!unknown_function

BUCKET_ID: 0x139_3_Qcamain10x64!unknown_function

PRIMARY_PROBLEM_CLASS: 0x139_3_Qcamain10x64!unknown_function

TARGET_TIME: 2016-09-03T17:16:10.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-08-03 05:15:01

BUILDDATESTAMP_STR: 160802-1857

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.545.amd64fre.th2_release.160802-1857

ANALYSIS_SESSION_ELAPSED_TIME: 50859

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_3_qcamain10x64!unknown_function

FAILURE_ID_HASH: {4576ae2e-9109-1045-88f4-cb0d1a7b795f}

Followup: MachineOwner
---------

I'm not able to get the minidump files to get past "Debuggee not connected."

 

[Colif]

qcamain10x64.sys = Atheros CB42/CB43/MB42/MB43 Network Adapter

Are you using an addon USB card? From looking at your laptop this device isn't part of it, so I had to wonder. Your laptop has killer lan and intel lan... Your laptop drivers (unless I got wrong model)

if you have an addon card in, take it out. PC will probably boot without it as I think the hardware itself is faulty or it wouldn't be stopping the PC at boot.

 

[RADD1]

No, I haven't installed any 3rd party hardware on the device yet (I'm planning on adding another M.2 SSD in about a month). (What follows may be totally irrelevant, but it's all I can think of relating to my network) To the best of my knowledge, I haven't changed the network settings in any meaningful way, either. I've been in a hotel for about 7 weeks now, and the support provider for the hotel's internet suggested that I use a static IP to get around some of the issues I was having with DCs. I tried it for a while, but it didn't help, so I went back to the default. I am using a VPN service, if that could somehow being having an impact.

I have windows updates disabled (under services), so my drivers may not be entirely up to date as of this moment, but, as I pointed out in my last thread, this issue began when the drivers were up to date, and I even downloaded the latest windows update (which updates drivers automatically) to see if it would fix the issue, and it didn't.

That said, I'm happy to manually update whatever drivers you think may be at fault. Also, I left windbg open with the minidump file loaded, where it was stuck being unable to connect to the debuggee, and its icon in the system tray just started flashing. It let me input the !analyze -v command and is currently *Busy*. (Question: Why was it displaying "Debuggee not connected" and why did it take about 30 minutes from the time I clicked "Break" to the time it finally allowed me to input a command?)

Edit: Yes, that's my model and those are the correct drivers.

 

[Colif]

Okay, it seems I just learned something, Killer Ethernet is Atheros...

WiFi: Killer Wireless-n/a/ac 1525, Atheros/Qualcomm QCA6174 802.11ac Wireless Network Adapter
Ethernet: Qualcomm/Atheros e2200 PCI-E Gigabit

Seems to me you need to update your killer drivers. Not that this helps since you cannot boot

I don't know enough about the debugging you running to know why you getting that other error.

 

[Colif]

Try this
On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB

boot from installer, on 2nd screen after languages, choose repair this pc, not install
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode

right click start menu
choose device manager
find your Ethernet and WiFi drivers here & uninstall the drivers

on other PC download the correct up to date drivers and put them on a USB
install them on your laptop and see if error is gone

 

[Colif]

Memory dumps can be over 6gb in size, the analyser has to work through it all I guess so it might just take that long to do your drive.

 

[RADD1]

Thanks for your responses! Here's the result of !analyze -v on the minidump

Spoiler

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0006f47b590, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0006f47b4e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.10586.545 (th2_release.160802-1857)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: GT72S 6QD

SYSTEM_SKU: Default string

SYSTEM_VERSION: REV:1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: E1782IMS.109

BIOS_DATE: 09/19/2015

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MS-1782

BASEBOARD_VERSION: REV:1.0

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd0006f47b590

BUGCHECK_P3: ffffd0006f47b4e8

BUGCHECK_P4: 0

TRAP_FRAME: ffffd0006f47b590 -- (.trap 0xffffd0006f47b590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe0012b537e90 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe00123914f70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802b762735d rsp=ffffd0006f47b720 rbp=fffff802b77b1ae8
r8=ffffe0012b537eb0 r9=000000000000000b r10=ffffd0006f465180
r11=fffff802b7492000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x4405d:
fffff802`b762735d cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffd0006f47b4e8 -- (.exr 0xffffd0006f47b4e8)
ExceptionAddress: fffff802b762735d (nt! ?? ::FNODOBFM::`string'+0x000000000004405d)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 8

CPU_MHZ: a98

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 39'00000000 (cache) 39'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

ANALYSIS_SESSION_HOST: UBERLAPTOP

ANALYSIS_SESSION_TIME: 09-03-2016 20:56:54.0353

ANALYSIS_VERSION: 10.0.14321.1024 x86fre

LAST_CONTROL_TRANSFER: from fffff802b75df4e9 to fffff802b75d4940

STACK_TEXT:
ffffd000`6f47b268 fffff802`b75df4e9 : 00000000`00000139 00000000`00000003 ffffd000`6f47b590 ffffd000`6f47b4e8 : nt!KeBugCheckEx
ffffd000`6f47b270 fffff802`b75df810 : 00000000`00000000 fffff802`b7521021 00000001`fa956b5b ffffd000`6f46aec8 : nt!KiBugCheckDispatch+0x69
ffffd000`6f47b3b0 fffff802`b75de9f3 : 00000000`00000007 00000000`00000002 fffff802`b7492000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd000`6f47b590 fffff802`b762735d : 00000001`fa97e213 ffffd000`6f46aec8 00000000`00000000 00000000`000000ff : nt!KiRaiseSecurityCheckFailure+0xf3
ffffd000`6f47b720 fffff802`b7565ff4 : ffffe001`2b537e70 ffffffff`00000000 00000000`00000002 ffffe001`0000000b : nt! ?? ::FNODOBFM::`string'+0x4405d
ffffd000`6f47b790 fffff801`3d2955c2 : ffffe001`2b537e50 ffffffff`ff676980 00000000`0000000b 00000000`00000000 : nt!KeSetTimerEx+0xa4
ffffd000`6f47b7f0 fffff801`40239b43 : ffffe001`22da0030 ffffffff`ff676980 00000000`00000000 00000000`000000ff : ndis!NdisSetTimerObject+0x82
ffffd000`6f47b840 ffffe001`22da0030 : ffffffff`ff676980 00000000`00000000 00000000`000000ff ffffe001`22da0030 : Qcamain10x64+0x59b43
ffffd000`6f47b848 ffffffff`ff676980 : 00000000`00000000 00000000`000000ff ffffe001`22da0030 fffff801`40239bd2 : 0xffffe001`22da0030
ffffd000`6f47b850 00000000`00000000 : 00000000`000000ff ffffe001`22da0030 fffff801`40239bd2 00000000`00000000 : 0xffffffff`ff676980


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 2d2247e092914624f90cd72c94c7fe62c5aea864

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: cf18188fe1a6b528163668f1e4cb7520787a3343

THREAD_SHA1_HASH_MOD: 685cc074fb8977777a711617996efb349f7559b8

FOLLOWUP_IP:
Qcamain10x64+59b43
fffff801`40239b43 b801000000 mov eax,1

FAULT_INSTR_CODE: 1b8

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: Qcamain10x64+59b43

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Qcamain10x64

IMAGE_NAME: Qcamain10x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55e6aebb

BUCKET_ID_FUNC_OFFSET: 59b43

FAILURE_BUCKET_ID: 0x139_3_Qcamain10x64!unknown_function

BUCKET_ID: 0x139_3_Qcamain10x64!unknown_function

PRIMARY_PROBLEM_CLASS: 0x139_3_Qcamain10x64!unknown_function

TARGET_TIME: 2016-09-03T17:16:10.000Z

OSBUILD: 10586

OSSERVICEPACK: 545

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-08-03 05:15:01

BUILDDATESTAMP_STR: 160802-1857

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.545

ANALYSIS_SESSION_ELAPSED_TIME: 5fc07

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_3_qcamain10x64!unknown_function

FAILURE_ID_HASH: {4576ae2e-9109-1045-88f4-cb0d1a7b795f}

Followup: MachineOwner
---------

Sorry if this wasn't clear from the beginning; I can boot up my laptop and use it. Whenever it's a cold start, I get the BSOD, the laptop restarts itself, everything works fine. I turn it off, when it starts up again, I get the BSOD. If I just restart the laptop, I don't get the BSOD. Based on the sequence of events described in my first post in this thread, this was somehow caused (or catalyzed) by me waking the laptop up from sleep mode by pushing the power button.

Should I update the Killer drivers?

(Also, the minidump file is only 382KB, the MEMORY.DMP was 762MB, yet it was completed faster than the minidump that I just posted).

 

[Colif]

I think you should remove old drivers and reinstall the new ones, yes.

I didn't know it only happened on fresh starts. You could try this to bypass that - turn off fast start up: http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

 

[Colif]

Something in your PC doesn't like the new power modes that come with win 10, did you ever update your BIOS? Sure John would have suggested that in other post if he thought it necessary.

 

[RADD1]

Updating the killer WIFI drivers seems to have solved the issue! It didn't work at first, and succeeded only in uninstalling the drivers I had, leaving me with no internet. I hadn't downloaded the drivers onto a USB, and somehow the drivers disappeared from my downloads, so I had to use another computer to download them.

No, I have not updated my BIOS. Is there any reason I should do that at this point?

A somewhat related question: I went through my Event Viewer to see if the Critical that was causing the crash is gone. It is no longer occurring, but I noticed 4 Errors and a dozen Warnings in my event viewer that all occur when I restart the laptop. They don't seem to be having an impact on my ability to use the laptop, but I'm concerned about them, none the less. Is it normal for there to be errors/warnings in a healthy laptop's Event Log?

Errors/Warnings are below in chronological order for reference:

Spoiler

Error 1: (Service Control Manager 7031) The Sync Host_3f8a6 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
param1 Sync Host_3f8a6
param2 1
param3 10000
param4 1
param5 Restart the service
4F006E006500530079006E0063005300760063005F00330066003800610036000000

Error 2: (DistributedCOM 10010) The server CortanaUI.AppXn73w0hsq3g4wx1h9fhf7q02vw2wta6qc.mca did not register with DCOM within the required timeout.
EventData

param1 CortanaUI.AppXn73w0hsq3g4wx1h9fhf7q02vw2wta6qc.mca

Error 3: (Service Control Manager 7009) A timeout was reached (30000 milliseconds) while waiting for the Sync Host_3f8a6 service to connect.
EventData

param1 30000
param2 Sync Host_3f8a6
4F006E006500530079006E0063005300760063005F00330066003800610036000000

Error 4: (Application Popup 56) The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ACPI
5

the message resource is present but the message is not found in the string/message table

EventData


ACPI
5
000000000300280000000000380004C000000000380004C000000000000000000000000000000000

Warning 1: (Kernel-PnP 219) The driver \Driver\WUDFRd failed to load for the device ACPI\ENE0110\5&c8cf257&0.
EventData

DriverNameLength 24
DriverName ACPI\ENE0110\5&c8cf257&0
Status 3221226341
FailureNameLength 14
FailureName \Driver\WUDFRd
Version 0

Warning 2 (This warning occurs 5 times in the same instant, but for different programs): (Task Scheduler 414) Task Scheduler service found a misconfiguration in the NT TASK\PDVDServ12 Task definition. Additional Data: Error Value: C:\Program Files (x86)\CyberLink\PowerDVD12\PDVD12Serv.exe.
EventData

TaskName NT TASK\PDVDServ12 Task
Parameter C:\Program Files (x86)\CyberLink\PowerDVD12\PDVD12Serv.exe

(Task Scheduler 414) Task Scheduler service found a misconfiguration in the NT TASK\NahimicMSIUILauncherRun definition. Additional Data: Error Value: C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIUILauncher.exe.

EventData

TaskName NT TASK\NahimicMSIUILauncherRun
Parameter C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIUILauncher.exe

(Task Scheduler 414) Task Scheduler service found a misconfiguration in the NT TASK\NahimicMSIsvc64Run definition. Additional Data: Error Value: C:\Program Files\Nahimic\NahimicMSI\UserInterface\x64\NahimicMSIsvc64.exe
EventData

TaskName NT TASK\NahimicMSIsvc64Run
Parameter C:\Program Files\Nahimic\NahimicMSI\UserInterface\x64\NahimicMSIsvc64.exe

(Task Scheduler 414) Task Scheduler service found a misconfiguration in the NT TASK\NahimicMSIsvc32Run definition. Additional Data: Error Value: C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIsvc32.exe.
EventData

TaskName NT TASK\NahimicMSIsvc32Run
Parameter C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIsvc32.exe

(Task Scheduler 414) Task Scheduler service found a misconfiguration in the NT TASK\Nahimic2Svc64Run definition. Additional Data: Error Value: C:\Program Files\Nahimic\Nahimic2\UserInterface\x64\Nahimic2Svc64.exe.
EventData

TaskName NT TASK\Nahimic2Svc64Run
Parameter C:\Program Files\Nahimic\Nahimic2\UserInterface\x64\Nahimic2Svc64.exe

Warning 3 (Last warning, occurs 8 times, nearly identically; the processor number changes in each warning, 2 4 0 3 1 6 5 7): (Kernel-Processor-Power (Microsoft-Windows-Kernel-Processor-Power) 37) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
EventData

Group 0
Number 2
CapDurationInSeconds 71
PpcChanges 1
TpcChanges 0
PccChanges 0

What can I do to address these? Or are they harmless? (Thank you for your help!)

 

[Colif]

If PC is working now, ignore the event viewer. Can also ignore BIOS too.

You’re sure to see some errors and warnings in the Event Viewer, even if your computer is working fine.

The Event Viewer is designed to help system administrators keep tabs on their computers and troubleshoot problems. If there isn’t a problem with your computer, the errors in here are unlikely to be important. For example, you’ll often see errors that indicate a program crashed at a specific time, which may have been weeks ago.

http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/

A brand new PC which has Win 10 on it for just 1 day could have Event viewer errors, they aren't anything to worry about.

 

[RADD1]

Brilliant! Thanks for your help!