Minidumps are not the best tools to use for hardware errors like this, they don't contain all the kernel data areas. There should be a kernel dump, it's the file C:\Windows\Memory.dmp. That will be too large to upload here so upload it to the cloud somewhere with a link to it here. That will contain the relevant data areas.
Please also export and upload your System and Application logs. To do that....
1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application-forumname' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System-forumname' (an .evtx suffix will be added automatically).
5. Upload the Application-forumname.evtx and System-forumname.evtx files to the cloud and add a link to them in your post.
Your system information output would be useful too....
1. Enter the command msinfo32 into the Run command box and the System Information window will open.
2. Click on File > Export, choose any suitable destination folder and call the file SysInfo-forumname (a .txt extension will be added automatically). The SysInfo-forumname.txt file should be small enough to upload directly to the forum, or you can upload it to the cloud with a link to it here.
A description of what happened, what you were doing and what you observed will help too. The BSOD happened whilst WoW.exe was the process in control and it's clear from the stack trace that a hardware error happened as soon as the kernel was entered. All we see is the context swap as the kernel was entered and then we get a machine check. We really need the kernel dump.
