Windows Event Viewer! Let's take a look behind the dark curtain.
Only time I've looked at the Event Log was when an Indian scammer asked me to lololol.
This is sort of a dumb question to ask. but are some of these issues Diagnosable on Z87/Z97 chipset? this video gave me an idea when to look through these files when my R9-290 crashes my system. it doesn't blue-screen it. but it does crash it to the point where i have to hard-reset it.
Thanks for this video! Pretty helpful. I didn't get these errors, but I honestly didn't know about the event log. Really interesting.
Would be nice to know what mic wendell uses.
I only look at if there is a problem and even then sometimes I don't.
My only problem with the windows event log is that most of the time it's fairly worthless. Sure it will give you the error code and what not. However if you don't work for MS then good luck deciphering what it really means. Most of the really important errors aren't on google or anywhere else publicly.
edit: After watching the video I am eternally grateful for the mention of windbg. I hadn't heard of that one before and will have many uses for it in the future. Since I didn't see a link to it anywhere I'm going to put on here for anyone interested.
exactly...indeed :)
wendell is right...i dislike Google...so i dont use it
I got a black screen and then BSOD right after watching this video. So i installed winDbg and opened the crash dump file. I found out that the problem was caused by atikmpag.sys not sure what that is. Probably some ATI software.
Maybe I'm just exceptionally lucky (touch wood) but I haven't had any entries in my Event Viewer for WHEA-Logger. I'm using a Gigabyte GA-X99-UD5 WIFI. Good to know, though and is definitely something to look out for.
I hadn't heard of WinDBG either. I've used BlueScreenView for years, which has been exceptionally handy in diagnosing BSODs, particularly as it usually tells you which DLL(s) were involved.
Overclock your RAM to insane speeds if you want Event Viewer to geek out. Strange things happen when you let errors pile up. Oops.
Superb video!
This has been something I have been dabbling in, and it is great to come across a cursory introduction to the subject. It's nice to know that I'm doing something right.
something ive always used an rely on to help me diagnose most of the simple issues in windows.
i find them helpful and most of the time i can find the solution to what im looking for by using the 0x000000 error numbers and other error id numbers
looking in the right place also helps.
microsoft knowledge base is a pretty decent archive of errors. but as with all things it takes a while to figure out and correlate information to the errors your getting. most of the time its pretty straight forward to get the infos you need but there has been an odd occasion when some where like majorgeeks or anantach has been more of a help.
i know from experience a lot of people dont even know the admin tools exists. i tell them. go look at the event logs and the reply i often get back is where are they?... (facepalm).
It depends on the quality of the error report and your googling skills ;P The error messages are usually more useful when thrown by the vendor specific drivers than windows generic errors, but then again they can be useless too if programmers didn't bother. So google the error messages if the error is known you'll find it, if not besides guessing, divide and conquer is the way to go.
Thank you for this lovely information! I have always wanted to look cool when I help people with their computers! Now I know how to do that! Also, while watching the video, I remembered that I wanted to figure out how to add duplex mode to my ethernet port. I found it rather quickly on my own. Watching videos from you seem to make me smarter. So I'll just keep doing what I can to learn from you. :)
Thanks again for all of your information. Keep it up! :D