Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The output from dmesg is often useful for determining which hardware is detected on a given system but it is also very useful for looking at hardware errors such as when wifi interface won't work or when a a hard drive is about to die.

I would very much like to learn about a Windows alternative to read kernel messages of that sort. I imagine It could be useful in determining the cause of the bsod in some cases.

share|improve this question
up vote 2 down vote accepted

There is the system error log ("eventvwr.msc"), but it's not as descriptive as dmesg. There's also C:\BOOT.LOG, where available.

share|improve this answer
I will have to look closer at that viewer thing. Doesn't look very useful right-off. – Ярослав Рахматуллин Nov 11 '12 at 5:19
Linux generally has better messages than windows because there is the possibility of the user hacking the source and fixing it. A lot of Windows stuff fails silently or opaquely. Having said that, eventvwr offers a link to the Knowledgebase for an error message which is often quite good. – pjc50 Nov 12 '12 at 9:33

see wevtutil and Sysinternals' psloglist

share|improve this answer
Specifically wevutil qe system /f:Text /rd | more is probably the closest command-line equivalent for the Windows System log. But the messages are not as informative. – LawrenceC Oct 2 '15 at 15:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.