It's more likely an issue with your card itself. For some reason I'm seeing in some of the crashdumps a power IRP being sent to your ATI driver to remove the device associated with it (graphics card). It was an invalid request, but it couldn't be handled properly, so it got held up until the system BSOD.
You can try updating your driver since it's from April 2012. However, these symptoms look very similar to an issue dealing with your graphics card. The fact it's happening so early in your system's life also gives suspicion on that. My recommendation would be to turn the laptop in for a replacement.
If you wish to approach this further, then update your drivers, turn on
Driver Verifier, let the system crash some more, then send us the resulting crashdumps.
EDIT: actually, now that I think about it, all your crashdumps have some form of corruption one way or another, making me thing the RAM is being compromised. Run
Memtest86+ for several passes (all tests done once = 1 pass).
Analysts:
Older November crash shows up a bad power IRP trying to be requested:
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800dae9a10, fffff80000b9c3d8, [COLOR=#008080]fffffa802c8f2300[/COLOR]}
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : pci.sys
Followup: MachineOwner
0: kd> [COLOR=#0000cd]!irp[/COLOR] [COLOR=#008080]fffffa802c8f2300 [/COLOR][COLOR=#0000cd]1[/COLOR]
Irp is active with 4 stacks 3 is current (= 0xfffffa802c8f2460)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
Flags = 00000000
ThreadListEntry.Flink = fffffa802c8f2320
ThreadListEntry.Blink = fffffa802c8f2320
IoStatus.Status = [COLOR=#ff0000]c00000bb[/COLOR]
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa802c8f2378
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffff80003435b00
Tail.Overlay.ListEntry.Blink = fffff80003435b00
Tail.Overlay.CurrentStackLocation = fffffa802c8f2460
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[ [COLOR=#ff0000]16, 2[/COLOR]] 0 e1 fffffa80172ae850 00000000 00000000-00000000 pending
[COLOR=#ff0000] Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
\Driver\amdkmdap (IopUnloadSafeCompletion)
Args: 00014400 00000001 00000004 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa801ccc5810
Args: 00000000 00000000 00000000 00000000
Iostatus says NTSTATUS c00000bb 'request not supported', meaning the IRP code sent to the driver was not supported, most likely because it's some odd power IRP. The irp function codes are 16, 2, meaning Power Irp for Remove Device. Sounds kinda funny to have the graphics card removed in the middle of gaming. 0x116 crashes seem to correlate with this.
However, I'm seeing corruption in nearly all the crashdumps. Modules missing from the dump, other data ranges omitted unexpectedly or corrupt. Most likely RAM is getting messed up pretty bad.
