The Event Viewer in the Windows operating system is used to troubleshoot any computer issues. It is one of the most useful tools that keep logs of both security and system events. It also monitors for both software and hardware problems in the computer. This tool is the only one with amazing features that maintain logs about everything that’s going on in the computer system. It keeps track of all the information to the point where going over them will take a lot of time.
Luckily, the Event Viewer tool now allows users to create custom views where you can set the filters and sort the data recorded to limit the information details to only what you’re interested in seeing. For instance, if you want to troubleshoot with one hard drive, you can just create a special custom view to display only the hard drive warnings in the security logs. This will save you hassle and time.
Take note that the logs in the Event Viewer are divided into two main categories namely the Window logs and the Application and Services logs. You can just set the filter to the logs by their event id, specific date, and many other events when you have to troubleshoot some problem in your computer. So if you are trying to troubleshoot a problem in your Windows 10 computer and you’re checking the Event Viewer, read on as this post will guide you in creating custom event views in the Event Viewer. To get started, refer to the instructions given below.
Step 1: Go to the Start menu and in the search box, type “event viewer” and then click on Event Viewer from the search results to open it.
Step 2: After opening Event Viewer, click on Custom Views located in the left pane of the window.
Step 3: Next, click on the Administrative events under the Custom View to create special log views.
Step 4: Then on the right side of the window, click on Create Custom View to open the Create Custom View window.
Step 5: There is a logged drop-down list under Filter. From there, you have the option to choose an appropriate predefined time or use a custom time range for your Custom log views.
Step 6: After that, select an appropriate event level for your custom view. You have fine entry-level options to choose from such as critical event level, error, warning, information and verbose.
- Critical – select this if you want to see the events that require your immediate attention in the custom view.
- Error – select this if you want your Event Viewer to display the events that are less critical but hints at the problems.
- Warning – select this event-level if you want to see the event with the potential problem but may not bound to happen.
- Verbose – select this if you want to see detailed information about all the events.
Step 7: After you’ve selected the event level, you now have to select how you want the events to be filtered. They can either be filtered By the log or By the source.
- By the log – you can select two options called Windows log and, Application and Service logs. The Windows logs allow you to filter the logs created during events like setup, security, applications, and system events. While the Application and Service logs filter the log created by the installed applications in your system.
- By the source – select this if you want your Custom View to search for information in event sources. It allows you to view events in detail for various applications and devices.
Note: You have the option to further customize the event logs with more filters like Event IDs, task category, keywords, User, and Computer. Using these additional filters, you can choose to filter the events in the special views by specifying event id numbers in the Event IDs, entering predefined Windows words in the Keyword, specify the user accounts in the User field, as well as choose the system from the server to maintain logs in the Computer field.
Step 8: Once you’re done customizing the log filter, click on OK to apply the changes made.
Step 9: After that, a Save Filter should be displayed in the Custom View window. Just enter the Custom View name and select the Event Viewer folder where you want to save the Custom view. The folder name should be Custom View by default. And if you want, you can also create your own folder if you want your custom views to be visible to all the system users.
Step 10: Next, check all the Users box located in the lower corner of the window and then click the OK button after you’re done.
You should now see the customized filter you just created on the left side of the window. Just click on it to check your filtered events in the center of the Event Viewer window. And for you to save the custom view logs, simply right-click on the Custom views you created and then click on Save All Events in the Custom View As from the drop-down menu. Then put a name on the file and select the appropriate location where you want to save the logs and click on the Save button. Note that the log file is saved with the “.EVTX” file extension and when you double click on it, it will open the file in the Event Viewer.
If we are to believe news from Intel, new series of processors based on Alder Lake architecture are about to be released somewhere in October. Alder Lake is the 12th Generation Core of Intel processors and it is meant to have all advantages of the current CPU structure.
I9 is aimed to pack a punch against its competitors with technology including eight high-performance Golden Cove cores (P-cores) with Hyper-Threading and eight energy-efficient Goldmont (E-cores) equipped with a 30MB L3 cache and operating at high clock speeds.
During the benchmark test, the new CPU outperformed all of Intel’s previous Rocket Lake structure processors which is logically expected but the big surprise came from results that indicate better performance than Apple’s new M1 processor even in single-threaded performance which is supposed to be best in that field.
Another surprise was really beating AMD Ryzen 9 in each field. If we take into account that i9 has 16 cores in total and can process 24 threads against Ryzen 9 with 16 Cores and 32 threads this is an impressive feature.
Now truth to be told Alder lake has massive L3 cache and microarchitectural advantages and consumes much more power but the results of performance are high. Also, note that this early CPU is not really a mass production one and maybe some things will still change but early results are very satisfactory.
We will see what will price tag be since in this age of shortage and competition that will also play a big role in its overall success. Speaking of competition I eagerly await AMD’s response to this, in any way it seems that the CPU market is for some turbulence which is always a good thing for the final customer and I welcome it. 