WIn 10 errors in events\Application

What sort of desktop do you have, if its classic then I don't know the answer but many who use the tonka toy version, whatever its called complain of instability. Brian

Honda is suffering from a massive ransomware attack currently but its website seems to be functioning. It did try to immediately play a load of video which NoScript and friends stopped.

As for you event log report, there's plenty of descriptions and cures on Google. Have a look and see if the cause matches your setup and act accordingly.

Windows Defender (Win10) has the ability to turn off the PC instantly, if it appears an unstoppable malware exploit is happening. This means it has to spot some software being "hooked", determine it does not have a remedy for it, and it just... shuts off the PC.

There is no time, during such an event, to write anything to Event Viewer. There should not be any log at all of what happened. As I understand it, not even a STOP code. The PC is intended to just drop dead, in microseconds.

Your symptoms are not an exact match, because "your fan is howling". A howling fan means either the CPU is very hot, or, the system has already done a hardware RESET and the BIOS is not loading and intelligently setting the main fan speed setting properly. A computer with a "blown BIOS" or a computer with no RAM sticks, could suffer a howling fan, due to a lack of sanity.

A howling fan is a Dell-ism most of the time. Dell has a jolly great 110CFM fan in its BTX cases, which most of the time is turned way way down (to run quietly). During a loss of control, the fan gets set to "full blast" as the hardware default after a RESET pulse. The BIOS can then program a correct value as part of POST.

Even NVidia video card fans can howl, until the driver loads and sets the fan to a correct value. I suspect some more modern NVidia kit, has a hardware control instead that prevents howling. And it no longer relies on software for sanity (Nvidia once released a driver update, with the fan control missing, and a couple NVidia cards overheated).

I would have expected the PC power to go off, for a controlled crash event. Which is why I'm a bit suspicious of what really happened in your case. The description doesn't exactly line up with the failure modes I know of. The fan should go OFF during THERMTRIP or as a response to the triggering of the Windows 10 jiggler. In fact, it should be relatively difficult to make a "howling fan" scenario. That's why I'm having trouble with the symptoms... It sounds like The Jiggler triggered, but the damn fan should be OFF.

*******

In your personal account on C:, lives the information for making the Start menu and "wall of tiles" for Metro.

\AppData\Local\TileDataLayer\Database\vedatamodel.edb

The EDB.log would be part of the journaling scheme for the Tile Database. Microsoft doesn't always have consistent naming for the things it does - this could be a JetBlue database (ese-nt).

The "tiledatalayer" term in Google, will likely hook you up with some recipes for repair. Tiledatalayer problems were a hot topic, many OS versions ago (causing the menu/taskbar area to be devoid of icons for example). When I had one of those, I just nuked and paved, even though this particular failure was happening on *brand new installs* !

Another example.

*******

Another data point. I can't find vedatamodel.edb on anything later than 15063. That's the release which was the last to have that file in the above location. I have a few .vhd files I keep, as "reference file system images" for doing checks like this. I don't have a complete set because I'm lazy. I have enough of them, to be able to figure out your OS is not more modern than 15063. You're three years behind, more or less. Use winver.exe to check your OS version.

%\AppData\Local\TileDataLayer\Database\vedatamodel.edb

(last seen winver.exe == 15063.xxx)

1507 10240 1511 10586 1607 14393 1703 15063 last vedatamodel.edb and edb.LOG 1709 16299 1803 17134 1809 17763 1903 18362 \ 1909 18363 \___ a limited number of releases 2004 19041 / get Windows Updates (you'll have to check)

Having a release that old, means a couple of things:

1) Equipment so crusty, it actually fails a sufficiency test of some sort. Like a "missing" video card driver update. A later release can easily be "forced" in as a Repair Install. (Just because WU isn't working, doesn't stop a Repair Install from being successful.

With Windows 10 running, right click 16299.iso, select "Mount", when the virtual DVD opens, double click "Setup.exe" to start the Repair Install flavor of an Upgrade. Your personal files and installed programs will be (mostly) preserved. CPU-Z might be removed. DataRAM RAMDisk may need to be repaired via Programs and Features control panel. There will be the odd grumble, but not a dumpster fire. Now, if you had TurboTax, that might be a dumpster fire.

2) Your Windows Update has been non-functional since the middle of 2017, and you didn't notice. If you were to use the Windows Update Troubleshooter in Control Panels : Troubleshooters, it could attempt to repair SoftwareDistribution folder. But once repaired, the OS is too old to be offered updates. As in (1), use *any* later update version (MediaCreationTool-generated ISO) to fix up your OS as you see fit.

If you want specific versions, you can use Heidoc tool It *required* a pretty high version of .NET to work. Run this from your crippled Win10 if you want, as it's likely to function properly there.

You can "Copy the URL" from the tool and paste it into Firefox and complete the download if you want. The ISO in this case, you right-click, "Mount", run Setup.exe and Repair Install. The ISO may be too big to fit on single-layer DVD media. Some of the ISOs fit on dual-layer DVD (or on a USB stick). The Heidoc tool gives a URL generated by Microsoft TechBench, and the download comes from Microsoft, not from the Heidoc site.

As always, use your backup software to backup C: and System Reserved, before taking action. This is your alternative if the OS gets broken by attempts to fix it. Restore from backup. I've done a ton of these, and I'm still doing backups. It's because restore from backup is a hell of a lot faster than a Windows-initiated "Revert" operation, which takes a couple hours. If it says something about "rolling back your OS", then you can just restore over top of C: and fix it that way instead.

While your problem doesn't absolutely require Repair Install, you are out-of-date, and maybe you didn't intend that to be the situation. If you always intended to run 15063 forever, that's your right - download 15063 with Heidoc, and do a Repair Install to the same OS version you're running, and freshen it up that way. Windows Update won't work but it also won't be broken any more, and your Tile Cache will get regenerated too.

HTH, Paul

winver says I am on version 1909 of Win 10 Pro. I used the free upgrade route in feb when Win 7 support ceased. It's a 32 bit install on a Phenom 1055 6-core with 4G ram, bought from Novatech, Portsmouth in 2011.

Actually the first thing I did was switch it to classic view to look like Win7. Updates arrive as usual, the most recent one was yesterday, which included the V2004 upgrade 'patch', which I haven't yet installed. Maybe I will, since other people here have installed it without issue.

The odd behavieor after visiting the honda.co.uk site reminds me of a similar problem with the hifi site of NAIM. That seems to download some sort of 360 degree viewing package for their hifi systems and also brought my PC to a 'halt', i.e. whatever the PC was doing, the mouse and keyboard drivers never got a look in, so I had to power it off on that occasion. The same thing happened yesterday, as soon as I clocked on accept cookies the CPU fan went into overdrive mode and the mouse and keyboard seemed to have no response, presumably because the cpu was massively engaged doing something else.

This time after switching off and on, it took much longer to power up, didn't even ask me if I wanted to boot into safe mode, and when I got into task manager I noticed something showing very high interupts in a red box. I'm afraid I didn't make a note of what process or service that it related to.

Andrew

I was unable to find any info on what happened to vedatamodel.edb . I assumed it was removed, becauses searches for edb weren't getting me anywhere.

But many things can screw up searches (permissions), so who knows why I can't see it. It's got to be somewhere, if your 1909 throws that error.

No utility on Windows can see absolutely everything in NTFS. The everything.exe search tool does a pretty good job. Even the nfi.exe program that Microsoft wrote around the year 2000, isn't perfect at it. And this means loads of fun when searching for system stuff.

And there's a reason they keep you out of C:\System Volume Information. There's nothing of interest in there anyway. I don't think backups back it up. Shadow copies live in there. Don't touch :-)

Paul

Here is some more info on tiledatalayer versus tilestore.

(Older Win10)

C:\Users\{original-username}\AppData\Local\TileDataLayer\Database\vedatamodel.edb

(Newer Win10)

Part of the storage is in the Registry.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore

The Default layout, is in some XML files.

C:\Users\%username%\AppData\local\Microsoft\Windows\Shell\DefaultLayouts.xml C:\Users\Default\AppData\local\Microsoft\Windows\Shell\DefaultLayouts.xml

There is also no explanation of why it's called CloudStore above.

*******

Storing a default layout here, shouldn't be happening, as near as I can determine. On an upgrade install, you'd think this would be discarded.

C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\ vedatamodel.edb #database EDB.log #playback journal

*******

The deprecation record is here.

"Tile Data Layer To be replaced by the Tile Store. 1709"

Paul

Thanks. Very interesting.

I'll try installing the 2004 upgrade and see if the same errors still get logged before I do anything else.