For the 3rd time, my server where my MySQL instance is running simply shutdown unexpectedly, this time, causing my tables to be corrupt as I had ALTER statements running.
While in contact with my hosting company, they deny that it is a hardware failure (they have done test that showed no hardware failure) and says that MySQL uses up all resources which causes the server to just shutdown. In my mind, the MySQL instance would shutdown unexpectedly, not the server itself but maybe I'm wrong.
My question is simple. Could MySQL cause the server to shutdown unexpectedly?
There are nothing in the error logs of either the server, or MySQL. Just that the server had shutdown unexpectedly.
Has anyone had this problem where MySQL causes a unexpected server shutdown?
I found that a kernel-power error with event id 41 has been generated all 3 times the error has occured.
EventData BugcheckCode 10 BugcheckParameter1 0xffffffff49bd9dc9 BugcheckParameter2 0x2 BugcheckParameter3 0x1 BugcheckParameter4 0xfffff80005ed80d8 SleepInProgress false PowerButtonTimestamp 0
Luckily, I've managed to find a minidump file, (only for the first time it happened thought) and I've decoded it to this.
IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.
Could this be that I've simply used up all available memory or is there maybe something wrong with the memory itself? I've just sent this details to the hosting company and I am awaiting answer but figured I would get some more opinions.