BSOD "0x0000000a Hero

[septerra]

Hello guys! New to the forum 🙂
I have the same problem and it drives me nuts. I also thought my computer was restarting on shutdown but when I disabled "Automatic Restart on System Failure" in control panel/system I now found that restarting was not really the case. I found I was really getting the following BSOD on the last stage of shutdown "0x0000000a IRQL_NOT_LESS_OR_EQUAL". I do not however get memory dump or kernel memory dump to work. I spent counless hours reading countless threads on how to set up memory dump files but there is just no file for me (I did ALL the tricks mentioned in every forum I found). I should mention that I have a samsung 840 pro for system drive and 2x1tb in raid 0 for storage. Do you think the solution you are giving here is going to work for me because you are specifically talking about restarting, not BSODs on shutdown. I will of course try the solution with uninstalling IRST, but since my problem is not happening every time I shutdown but maybe 1 out of 4-5 times I wanted to be sure we are talking about the same stuff. I also read on other maximus VI hero threads of people having BSOD on shutdown and infinity loops on start/restart but no specific solutions or consistent inforamtion.
Thank you in advance!!! 🙂

[HiVizMan]

Moved as your issue is not the same.

Please list all your hardware and what your memory is clocked to, and if you have any other OC.

I would suggest starting with the basics, testing your memory out, a possible good place to start is the Memtext86+ guide that can be found in my sig.

[Praz]

0x0a is normally because of faulty system memory or a driver/service issue.

[septerra]

Thank you for your reply! I will try memtest tonight but somehow I doubt that ram is my problem. The PC is VERY stable; I never had a crash other than the one on the final stage of shutdown that we are talking about. The system works without any other issues. I don’t want to be annoying but are you 100% certain my problem isn’t the same as the guys reporting restarts on shutdown. If all of them have “automatic restart on system crash” they may never realize it is an actual crash (as I didn’t saw it for couple of weeks). Anyway my system specs are as follows:
Maximus VI hero with the latest bios; 4670K on stock speeds; Asus hd6950 2GB, 2x8GB GEIL EVO POTENZA at 2400 MHz and 1.65v (XMP enabled – 11, 13, 13, 30, 2t); 128GB Samsung 840 pro for system drive and 2x1tb WD black caviar in raid 0 for storage; the PSU is a modular 700W Chieftec (from their high-end series, not the cheap ones); all this is in a new Corsair carbide 400r case.
I also have the latest drivers for any component and IRST running 12.8.0.1016.
Also what do you think of my memory dump file not being created – do you have any ideas? Isn’t it somehow connected to the crash on shutdown and the system not being able to write it down? I’ve read so many threads on similar subjects the last couple of days that my head will explode 😛
Cheers!

[HiVizMan]

In the line of work I am in, being detached and outside of the problem environment is required. So I can fully appreciate your head will explode feeling, so to prevent a nasty mess all over your screen and keyboard let us start systematically isolating variables. The memory is the most logical place to start as pretty much all revolves around the memory on modern systems.

😄

[Nodens]

Does this happen at stock?

[septerra]

3.5 hours of Memtest with xmp enabled and no errors. I will leave it again at night but I am now pretty sure RAM is not an issue 🙂
Any other suggestions?
#Nodens - I run the CPU at stock speeds

[Nodens]

You really need to generate a minidump. So let's fix that.

Pagefile should not be disabled. And should be higher than 50MB.
Make sure that Small Memory Dump is selected in Startup and Recovery settings.

Registry:
In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
Ensure these values are set:

CrashDumpEnabled set to "3"
DumpFile set to "%SystemRoot%\MEMORY.DMP"
MinidumpDir set to "%SystemRoot%\Minidump"

If with these settings you don't get a Minidump in C:\Windows\Minidump then also do this change:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

Create new DWORD value named: "DedicatedDumpFile" set it's value to a file on your second drive (the RAID0 array) like this:
"D:\dumpfile.sys"


Don't enter the quotes of course:) And reboot after making the registry changes.

If still you can't get a Minidump generated with these changes then your Windows installation is corrupted a lot.

[septerra]

I followed your instructions (I already had everything exept for the last dword). I will wait for a BSOD and update you.
Thanks for helping 🙂

[Nodens]

septerra wrote:
I followed your instructions (I already had everything exept for the last dword). I will wait for a BSOD and update you.
Thanks for helping 🙂

Last DWORD makes sure that Windows uses the second drive to store the crash dump instead of the pagefile on the system drive. If the flags are right and Windows is not corrupted, the only reason why a crash dump would not be created is inability to write to the system drive.

But let's hope you won't get a BSOD at all like Viz says:)