Four of the dumps point directly to a hardware problem. I think the only course of action is to take/send it back. It hasn't been fixed.
BugCheck 4E, {99, 0, 0, 0}
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+124 ) <--memory
BugCheck 10000050, {ffffffad, 1, bf80a032, 0}
Probably caused by : hardware ( win32k!NtGdiBitBlt+414 )
FAILURE_BUCKET_ID: IP_MISALIGNED <-- any hardware
BugCheck 1000008E, {c000001d, bf878722, f690c950, 0} <-- exception c1d - illegal instruction --> usually hardware
Probably caused by : hardware ( win32k!ProcessKeyboardInputWorker+14a )
FAILURE_BUCKET_ID: IP_MISALIGNED
BugCheck 10000050, {cab02d98, 1, bf153689, 0}
Probably caused by : hardware ( nv4_disp+141689 )
FAILURE_BUCKET_ID: IP_MISALIGNED_nv4_disp.dll <-- video card