TravelMate Blue Screen of Death Help

Hello,

I bought my TravelMate back at the end of 2017 and it has been working excellent EXCEPT one minor thing - an occasional, but regular blue screens of death.

The most common Blue Screen of Death code I get is this:

Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 41790
Parameter 2: ffff8d0003000000
Parameter 3: 0
Parameter 4: 1
OS version: 10_0_18363
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.18363.2.0.0.256.48
Locale ID: 1033

Much less often I get this:

Problem Event Name: BlueScreen
Code: 12b
Parameter 1: ffffffffc00002c4
Parameter 2: 5af
Parameter 3: 2381853b620
Parameter 4: ffffdd00e5b33000
OS version: 10_0_18363
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.18363.2.0.0.256.48
Locale ID: 1033

My OS setup is this:

Some more additional details about the circumstances of the error:
1) It seems to have started with one or more of the following events:
1a) the upgrade of BIOS from 1.11 to 1.12 after the revelations of Meltdown and Specter vulnerabilities
1b) the repartitioning of the hard drive done for installing Linux Ubuntu, which also necessitated the change of boot method (from UEFI to Legacy)

Under Linux, my laptop still rebooted randomly but displayed no error messages. After some time, I reverted back to Windows 10. I created a fresh install and for a long while everything worked fine. Then it started again but I figured it might be because of Adobe Acrobat that I had installed, and after uninstalling it all came back to normal again.

I even sent the laptop to be serviced but it came back with a note that they were not able to identify anything wrong with it, probably because of the randomness of the error.

I ran Windows Memory Test, sfc and chkdsk from Windows PowerShell. I don't know how to check logs of the latter two, and the Memory Test for some reason does not return any logs in Windows Event Logs - there is only information that it was scheduled, with no results. I believe I even once ran memtest86+ but it was a while ago and I don't remember the results. My system and drivers are up to date.

As of now, the error happens either after I close the lid and I learn about it when I open it back again; or shortly after opening the lid; or randomly while using the laptop.

My reliability history graph looks like this (BSOD marked):

Image: https://us.v-cdn.net/6029997/uploads/editor/85/l7l6gb884jj5.jpg

My full reliability history in XML file: https://www.dropbox.com/s/4ggeqv1sa4p9tzw/reliability-history.XML?dl=0

Can you please direct me on what I could do to identify and eliminate the culprit of this error?

Accepted answers

All comments

htbrch

PS. Oh, and since I'm back on W10 I switched back to UEFI, I also disabled fast startup per some help guides

billsey

Just for information, pretty much all of the current flavors of Linux boot just fine in an UEFI environment, no need for Legacy... Normally a blue screen has a faulting process displayed on the screen, which helps immensely in pinning down things to a specific driver or app. Could you bring up the Technical Details on the three critical events shown in your Reliability History Graph for June 11th? The XML doesn't really help, since it looks like it's only showing graph points, not the data behind them.

htbrch

Sure, here they are:

The 3 critical events from June 11:

1)

Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 41790
Parameter 2: ffff8d0003000000
Parameter 3: 0
Parameter 4: 1
OS version: 10_0_18363
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.18363.2.0.0.256.48
Locale ID: 1033

2)

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xffff8d0003000000, 0x0000000000000000, 0x0000000000000001). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 06430a04-9b76-4352-b154-28655c5a69c0.

3)

The previous system shutdown at 12:29:36 AM on ‎6/‎11/‎2020 was unexpected.

htbrch

MEMORY.DMP at this moment is 1.55 GB in size

billsey

Yeah, memory.dmp will be the size of the used memory when the crash happened, so normally fairly large. Those three again didn't help. Can you use Event Viewer to capture the info for me instead? Somewhere the faulting application of driver will be listed. Here's what I see when I select the details for an error event on my system:

Source
AppMonitorPlugIn

Summary
Stopped working

Date
‎6/‎12/‎2020 8:56 AM

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\Acer\User Experience Improvement Program Service\Plugin\AppMonitor\AppMonitorPlugIn.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    AppMonitorPlugIn.exe
Application Version:    4.0.3002.0
Application Timestamp:    5b03fc13
Fault Module Name:    AppMonitorPlugIn.exe
Fault Module Version:    4.0.3002.0
Fault Module Timestamp:    5b03fc13
Exception Code:    c0000005
Exception Offset:    00000000000064fa
OS Version:    10.0.19041.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    c488
Additional Information 2:    c488ba5bfb60ce772c0186bc28ef8e03
Additional Information 3:    4191
Additional Information 4:    41914101d70394a04b8ea03df3b855b9

Extra information about the problem
Bucket ID:    df47a19e2bfc4cf30f5f3d63192209b8 (2260593033795996088)
As you can see it's much more specific as to what caused the error.

htbrch

There are loads of error messages in the Event Viewer... Around the time of the last crash, under Event Viewer -> Custom Views -> Administrative Events there are a lot of messages reading "The [insert name] service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
The names of services are: ClickToRunSvc, AGSService, AGMService, ProductAgentService, UPDATESRV, cplspcon, BDPRotSrv, ibtsiva, DbxSvc.

Then the WpnService and TrkWks "failed to start due to the following error:
The service did not start due to a logon failure."

Then there are a bunch of errors reading "The [insert name] service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

The request is not supported."
These were: WpnService, TrkWks, etc.

Tens, tens of those continue.

Then: "DCOM got error "1069" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:

{A47979D2-C419-11D9-A5B4-001185AD2B89}"

Then: "Session "PerfDiag Logger" failed to start with the following error: 0xC0000035"

Then: "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xffff8d0003000000, 0x0000000000000000, 0x0000000000000001). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 06430a04-9b76-4352-b154-28655c5a69c0."

Then: "The driver \Driver\WudfRd failed to load for the device USB\VID_1C7A&PID_0570\5&29094482&0&6."

Then the "critical error": The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

billsey

All of those seem to be happening during the initial boot process as Windows does it's load. They sound like you've got a corrupted system, which breaks access to several of the services that load with SYSTEM credentials. What we're hoping to see is the crash that started the whole thing off... But it's possible that's not captured anywhere except in the crash dump. It's looking very much like the best way to go is a full wipe and reinstall of the OS and your apps. You'll want to backup your data first!

Quick Links

Top Members

Weekly

Puraw 135

Swift Series Intel^® Evo™

Game Pass

Acer Corner

Gaming on Chromebook

Swift Series Intel® Evo™

Game Pass

Acer Corner

Gaming on Chromebook

Swift Series Intel^® Evo™