This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION.
This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.
|Description||The default facility code.|
|Error Code||265 (0x0109)|
First off I suggest that you invest in a high quality surge protector and make sure that your PC is protected. Another suggestion is investing in a UPS (Uniterupted Power Supply) as these will supply power to your computer during power outtages, and depending on the type will notify your PC that power has been cut and will properly shut down your PC.
Also, with the fact that there are errors I want to make sure that you do replace those memory modules as (one) maybe more are bad.
Finally, before I get into actual testing, a fresh install of Windows may be a smart thing to do. If system files were being accessed at the time of the power outage, then they may have become corrupted.
With those things said, here are some tools that you can use:
Memory: Memtest86+ is the best option I have seen so far
Hard Drives: Ultimate Boot CD has a great collection of diagnositc software for testing all sorts of brands of HDD's
GPU: This is a little more difficult as there is no (that I know of) targeted diagnostic software to test GPU's, however the use of benchmark software like FurMark can be used. Run the benchmark and if there are errors or system crashes then there is a possible issue
Power Supply: The best way to test these is to purchase a specific Power Supply tester which will measure the voltages output by the PSU and tell you if there are problems
CPU: Similar to the GPU there is no direct software to test that I know of. However you can use benchmark software like Prime95
Motherboard: This is very, very difficult to directly test. In my experience it's been if you know everything else is working, and there are still crashes. There are some symptoms that you may look at but there is no direct testing that can be done (besides replacing and checking).
I had the same issue today. Resolved by upgrading the (Debian Wheezy) server to the latest Mono; the staging servers had been Ubuntu Trusty and they did not exhibit this problem.
So this is fixed in Mono 3.2.8+ (which is Ubuntu Trusty's version).
Solution that worked for me:
Note: The highlighted lines are the important changes, but make sure the other settings are also the same as in the pictures
Other things that I did, which may have helped (I did these before doing the above, so I'm not sure if it is relevant or not):
Installed KB2970215 from Microsoft - this fixes "random blue screens" on specific CPU chipsets
Installed the latest drivers for the Intel Chipset from Supermicro's web site (for me, it is ftp://ftp.supermicro.nl/driver/Intel_INF/C612_Series_Chipset/Chipset_v10.1.2.8.zip - locate one best suited for you)
Setting "Package C State Limit - C0/C1 State" causes BSODs (as well as setting Power Technology - [Disable]). Because I can't set "C0/C1 State", I choosed "C2 state" which is working without problems. In a nutshell: The higher Package C State Limit you chose, the more energy efficient CPU would be (by stopping clocks, reducing voltage...).
The best performance settings in this case should be:
Power Technology - [Custom]
Energy Performance Tuning - [Disable]
Energy Performance BIAS setting. - [Performance]
Energy Efficient Turbo - [Disable]
EIST(P-States) - [Enable]
Turbo Mode - [Enable]
P-state Coordination - [HW_ALL]
Package C State Limit - [C2 state]
CPU C3 Report - [Disable]
CPU C6 Report - [Disable]
Enhanced Halt State (C1E) - [Disable]
I found, that this type of problem appeared few times in the past and was fixed by updating ROM or by Host Microcode update like this: KB2970215. But I haven't found any working update yet.
My experiences with power surges have never been good. I had one machine where nearly every component was toasted, whatever machine I put any part of it into started to get issues. After nearly 6 months i threw the entire thing out. UPS and surge plugs are alot higher up my shopping list now.
That said, you should be ok on the harddrives, and you can check them with s.m.a.r.t easy enough. The ram is toasted by the sounds of your memtest output, the real question is did the motherboard survive ? I'd suggest it's unlikely or at least unlikely in terms of being rock solid now, in which case you might be looking at a do-over more or less from scratch.
The psu may well be affected also, I had this happen recently to a machine from a power surge.
Smart test your drives, stress test the cpu (using something for windows, else "stress" for linux), and get new ram if you think its worth the gamble.
We've had the same errors also. The answer from @KeyszerS is a really good hint.
It seems that the errors are related to the power management of X10 boards (at least for supermicro). I did several tests with and without any power management - sometimes the BSODs occured more often and sometimes they've been nearly passed.
Since a few days i've a solution that works (at least for us) reliable. We've evaluating the stability with 20 VMs on one affected server - no crashes anymore.
So, how to get it: Easiest way is to revert BIOS settings to defaults and just disable "energy efficient turbo".
No issues at all for around 7 days - workload seems to be quite stable. Here's a screenshot of power management settings in BIOS - it seems to be related to "Energy Efficient Turbo".
First step, replace the power supply. Surge suppressors can only stop so much, it's better to have invested in a UPS as they have a stiffer power conditioning system that is better at stopping over-voltage and spikes than a couple MOVs arranged accross the various circuits in the hopes they dissipate all the power crazieness.
Unless the power surge got in by other means like a modem (thankfully no longer a secondary lighting strike path for a lot of people), usually the power supply absorbs the excess energy as the voltage regulators do their job.
It could mean there is also a problem with a windows system file. Easy way to check its not a windows system file is to run command prompt. and type SFC /SCANNOW
the other thing you could try doing, is creating a custom view in the event viewer and attach any event collectors you think might hold the information you are looking for and wait for it to happen again, then check your custom event view. You can add an event logger to just about anything that your OS has installed to hardware plugged in. And to just give you and idead what you can do with event viewer of how powerful it is, you can even make custom tasks run based off when certain events happen, given the event is loggable.
As some have said, it is possible it is a bad driver, the common one of these drivers to cause your computer to reboot is a bad graphics driver. However, any bad driver can cause your computer to restart. Also, if the inside of your computer is dirty, it can cause it to shutdown because something shorts out or some other component gets too hot and thus not working right because of it.
So to help you resolve this, the best thing to do in this type of situation is to start at the basics by first physically cleaning your computer and then cleaning the up junk inside the OS. From removing old programs, emptying the recycle bin, defrag the computer install windows updates if there is any and the last, go research to see if there is updated drivers for hardware you have in your computer. Such as graphics driver, network card drivers, audio drivers, etc. If there was problems with your hardware like the memory or harddrive the OS would have detected it and logged it somewhere before the system crashes or in your case just reboots. As you can see without further information, it can be a number of things, but if you do some of these maintenance tasks you will at least be able to eliminate more things off your list as to what is possibly causing it.
User contributions licensed under CC BY-SA 3.0