Wand3r3r's WHEA overclock util - *Update 9/13* #Beta0.2

[wand3r3r]

I decided to whip up a little util to scour the event viewer logs for WHEA-Errors. I found this to be a bit tedious so now it's a button click away. Update* It can also clear the event logs, or search since the last time you ran it.

Why?
They pop up if you are overclocking and the data in the processor starts getting corrupt. (Someone can elaborate and I'll put it here.)

Give it a try and let me know what you think or if you have ideas to improve it.

How does it work?
Simply run it, press the "Find WHEA errors" button and wait a bit.

Results:
A list of errors and the count.
or
No errors found text.

Refinement can be done by selecting a starting date and/or ending date to see if any happened during a known interval.
e.g. 1/1/2013 - now
history -> 1/1/2013
1/1/2013 -> 1/31/2013

Requirements:
Windows
.NET (installed for games anyway)

wand3r3r.overclock.util #BETA 0.2
Usability improvements.
Added last search date, can be filtered since the last time you ran it.Can clear the event viewer logs.
*Disclaimer, I have only tested the Event Viewer clearing in a virtual machine as I want the WHEA errors that I have for testing.*

To download from google docs: File / Download, it will download everything in the zip.
1. On the google docs page it's just FILE - Download.
2. Once you have the ZIP, unzip it and run the Setup.exe
3. If you unzip it just make a shortcut from the desktop to the .exe.
https://docs.google.com/file/d/0B7CtGVODPUTteWE2V3VWV2FmRGM/edit

Old version.
wand3r3r.overclock.util #BETA 0.1
Basic search for errors.
https://docs.google.com/file/d/0B7CtGVODPUTtQnNDTkhZWXJnUlk/edit

 

[Idontcare]

Awesome! Can't wait to give it a try

 

[Rvenger]

Nice man!

I got my 3rd 3770k CPU and this is the only CPU that doesn't get WHEA errors when Vcore is too low, it just blue screens with IRQL_NOT_LESS_OR_EQUAL. Its amazing how different each CPU can behave.

 

[wand3r3r]

I only tried it in win8 so let me know if anyone has issues.

Of course feel free to let me know if it works or if it's lacking.

I should try figure out how hard it is to get into the dumps from BSODs.

 

[john3850]

thanks works good in win 7

 

[wand3r3r]

Thanks, that's good to know.

Looking (very very briefly) at BSOD and memory dumps I don't know whether it's worth pursuing. Maybe I'll take a look when I get more time (might take a while). I should also try figure out if there are other events which are as sure of a sign of a failed OC as WHEA errors. If anyone knows of any events that are a pretty fair warning of a failed OC, let me know.

 

[Rvenger]

It would be awesome if you can actually pull the error codes and get some kind of description with the program if you are looking into memory dumps. When Windows 8 bluescreens, it is near impossible to find what went wrong unless you pull the memory dump file and read it.

 

[tynopik]

does this report ECC memory corrections?

 

[wand3r3r]

It would be awesome if you can actually pull the error codes and get some kind of description with the program if you are looking into memory dumps. When Windows 8 bluescreens, it is near impossible to find what went wrong unless you pull the memory dump file and read it.

Yeah I hate BSODs especially when they dissapear quickly and you don't even remember what they said. I'll have to look into this.

does this report ECC memory corrections?

It should if they are reported through the Microsoft-Windows-WHEA-Logger which they seem to be.

 

[Liquid_Static]

how do I go about installing this?

 

[ViRGE]

how do I go about installing this?

Download the ZIP file, run the installer?

 

[Mr. Fox]

This is a cool little utility. Thank you for sharing it.

 

[wand3r3r]

I've been playing with BSOD dump files (very briefly) and so far haven't figured out a (good) way to get any actual usable data (namely error codes).

how do I go about installing this?

1. On the google docs page it's just FILE - Download.
2. Once you have the ZIP, unzip it and run the Setup.exe
3. If you unzip it just make a shortcut from the desktop to the .exe.

Download the ZIP file, run the installer?

Yeah, you don't have to do much. Maybe I'll drop in an actual installation package at some point.

This is a cool little utility. Thank you for sharing it.

Thanks, and you're welcome!

Any suggestions are welcome, I don't have much spare time atm but I plan to look into adding features.

 

[tracerbullet]

Any suggestions are welcome

The option to have a box pop up when a WHEA error occurs (I forget the details but I remember it being an option to notify when one occurs, would be slick to automate that w/ a "button"). I don't have any idea how easy or difficult that might be, but it seems like it would be cool, especially when experimenting with overclock settings.

 

[akugami]

Thanks for the tool. Going to give it a test later and add it to the tool chest.

WHEA errors are not something everyone remembers to search for. I was 3 hours stable on Lin-X and 24 hours on Prime95 but didn't think to check for WHEA errors. Someone else asked me about it on these forums which is when I checked for them.

Bumped the core voltage up another 0.05 and all is well. i7-3770k @4.2ghz using 1.55v. I was only going for a modest overclock, I'm sure with better cooling my CPU can do more.

 

[guskline]

Thanks for the tool. Works well in Win 8

 

[tracerbullet]

i7-3770k @4.2ghz using 1.55v.

I don't want to wander off topic so I'll just say that if those #'s are right, you should make a thread of your own to get some assistance, 1.55V is staggeringly high.

 

[moonbogg]

Good job man! I'm impressed. I'll give it a try.

 

[wand3r3r]

The option to have a box pop up when a WHEA error occurs (I forget the details but I remember it being an option to notify when one occurs, would be slick to automate that w/ a "button"). I don't have any idea how easy or difficult that might be, but it seems like it would be cool, especially when experimenting with overclock settings.

Thanks for the idea, it sounds like a decent feature. I was wondering if it should save some data and just search for newer data than the last time so you know if anything new has arisen. The idea that it's monitoring for new data sounds interesting, I'll have to look into how it could work out.

Thanks for the tool. Going to give it a test later and add it to the tool chest.

WHEA errors are not something everyone remembers to search for. I was 3 hours stable on Lin-X and 24 hours on Prime95 but didn't think to check for WHEA errors. Someone else asked me about it on these forums which is when I checked for them.

Bumped the core voltage up another 0.05 and all is well. i7-3770k @4.2ghz using 1.55v. I was only going for a modest overclock, I'm sure with better cooling my CPU can do more.

Yeah, it's easy to forget much less most people don't even realize you should look for them much less where they are. (Plus they are actually tricky to find when you have 50k entries)

Overclocking could have a routine (test stability, monitor, increase).

Thanks for the tool. Works well in Win 8

:thumbsup:
Thanks for the feedback!

Good job man! I'm impressed. I'll give it a try.

Let me know if you have any ideas to improve it.

 

[akugami]

I don't want to wander off topic so I'll just say that if those #'s are right, you should make a thread of your own to get some assistance, 1.55V is staggeringly high.

Wrong numbers.

It's 1.155. I think the magic smoke appears if you use 1.55.

 

[tweakboy]

This looks risky. even I aint tweakin dat,

 

[24601]

Do I have to turn WHEA error logging on in the logging in Windows 7 or is it on automatically?

My 3570k doesn't show any events with your tool, which i guess is a good thing .

 

[tracerbullet]

Logging is turned on, but letting you know about it is not.

 

[john3850]

I last checked WHEA errors a few months back and had a few.
When I checked WHEA this time I find 1200+ errors and cleared all the logs.
Now I set intel burn to the max and come up with no errors at 46k with 1.256-1.272v.
The no errors may be do to the latest 2.80 bios update on extreme4 I hope.

 

[wand3r3r]

Do I have to turn WHEA error logging on in the logging in Windows 7 or is it on automatically?

My 3570k doesn't show any events with your tool, which i guess is a good thing .

Yes, it means one aspect of your overclock is not generating errors. :thumbsup: