Event viewer WHEA-Logger issues with NTLite modified ISO

U

username99

New Member
Messages
4
Reaction score
1
Hello, I've used NTLite to make a custom ISO based on the latest official windows 10 ISO from Microsoft. I mostly just followed the gaming template and didn't remove anything that should break event viewer as far as I know. Also added a registry file with some tweaks that I believe shouldn't have any effect on this. Event viewer still works but somehow the WHEA-LOGGER is not working correctly.

I tested an unstable overclock that should trigger WHEA-19 events. On a fresh official win10 install, the events correctly appear under Windows Logs/System. On the ntlite modified ISO these don't appear at all under Windows Logs/System. On both installs they do appear under Applications and Services Logs/Microsoft/Windows/Kerneal Wheas/Errors as information events but that's separated from the warning so something is definitely not working properly.

I attached the preset. Any help is appreciated.
 

Attachments

You've disabled the Windows Error Reporting (WER) Service.
 
garlin said:
You've disabled the Windows Error Reporting (WER) Service.
Click to expand...
Hi, I've enabled it in services but problem still persists. I set it to manual thinking it would be triggered when needed but it didn't start so I set it to automatic inside windows and started it manually but still doesn't capture wheas. Is there any other service/component associated that I need to keep, such as "Problem Reports Control Panel Support"?

Edit: I've narrowed it down to be service related, not component related, but still not know which one affect it besides WER. "Performance Logs&Alerts" might be connected? I just checked and using an ISO with Windows error reporting, performance logs&alerts, problem reports control panel support all enabled and whea logger still doesn't work properly.
 
Last edited:
The Windows Hardware Error Architecture (WHEA) raises an Event Tracing for Windows (ETW) event whenever a hardware error occurs. These hardware error events are recorded in the system event log.
Click to expand...
diagnosticshub.standardcollector.service manages ETW logging.
 
Divide and conquer. Half of the remaining half, and so on..
 
You must log in or register to reply here.
Back
Top