Just recreated the BSOD again. Found this in my Windows Event logs:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000020, 0xffffe000182a4140, 0xffffe000182a4200, 0x000000000c0c000a). A dump was saved in: C:\WINDOWSi\MEMORY.DMP. Report Id: 035ac710-7ea6-45e8-af08-e28ba844e6eb.

I'll attach it to my OP above for review/reference.

Here's some more - taken from Windows debug (I'm not experienced in using it, but I understand the basics and looked a guide to get this much for your Tech Support team to utilize. This is taken from the CRASH.dmp file created after I recreated the BSOD.

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Aion\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\Symbols*msdl.microsoft.com/.../symbols
Symbol search path is: srv*c:\Symbols*msdl.microsoft.com/.../symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.63.amd64fre.th2_release.160104-1513
Machine Name:
Kernel base = 0xfffff802`3f40a000 PsLoadedModuleList = 0xfffff802`3f6e8c70
Debug session time: Wed Feb 10 05:59:36.681 2016 (UTC - 5:00)
System Uptime: 0 days 0:06:04.479
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000043`8441e018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, ffffe000182a4140, ffffe000182a4200, c0c000a}

Page 1300 not present in the dump file. Type ".hh dbgerr004" for details
Page 1300 not present in the dump file. Type ".hh dbgerr004" for details
Page 1300 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : disk.sys ( disk!DiskDeviceControl+8f )

Followup:     MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe000182a4140, The pool entry we were looking for within the page.
Arg3: ffffe000182a4200, The next pool entry.
Arg4: 000000000c0c000a, (reserved)

Debugging Details:
------------------

Page 1300 not present in the dump file. Type ".hh dbgerr004" for details
Page 1300 not present in the dump file. Type ".hh dbgerr004" for details
Page 1300 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10586.63.amd64fre.th2_release.160104-1513

SYSTEM_MANUFACTURER:  Alienware

SYSTEM_PRODUCT_NAME:  Alienware 17 R3

SYSTEM_SKU:  Alienware 15 R2

SYSTEM_VERSION:  1.2.7

BIOS_VENDOR:  Alienware

BIOS_VERSION:  1.2.7

BIOS_DATE:  01/18/2016

BASEBOARD_MANUFACTURER:  Alienware

BASEBOARD_PRODUCT:  Alienware 17 R3

BASEBOARD_VERSION:  A00

DUMP_TYPE:  1

BUGCHECK_P1: 20

BUGCHECK_P2: ffffe000182a4140

BUGCHECK_P3: ffffe000182a4200

BUGCHECK_P4: c0c000a

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  ffffe000182a4140 Nonpaged pool

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 74'00000000 (cache) 74'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  pcdrrealtime.p

CURRENT_IRQL:  1

ANALYSIS_SESSION_HOST:  ECHELON

ANALYSIS_SESSION_TIME:  02-10-2016 13:36:24.0992

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

IRP_ADDRESS: ffffe00012acb128

LAST_CONTROL_TRANSFER:  from fffff8023f63bde5 to fffff8023f54c770

STACK_TEXT:  
ffffd000`21936be8 fffff802`3f63bde5 : 00000000`00000019 00000000`00000020 ffffe000`182a4140 ffffe000`182a4200 : nt!KeBugCheckEx
ffffd000`21936bf0 fffff802`3f460bd9 : ffffd001`c0df4010 00000000`00000000 ffffe000`116a7b10 fffff802`20206f49 : nt!ExFreePool+0x2c5
ffffd000`21936cd0 fffff802`3f45f364 : ffffe000`12acb1a0 ffffe000`1765df78 ffffd001`c0df4000 ffffd000`305ef1e0 : nt!IopCompleteRequest+0x79
ffffd000`21936dc0 fffff802`3f54f963 : 00000000`00000001 ffffe000`174b6960 00000000`00000000 ffffe000`12acb1a0 : nt!KiDeliverApc+0x134
ffffd000`21936e50 fffff801`18083bb2 : 00000000`00000101 00000000`00000000 00000000`00000000 00000000`00000140 : nt!KiApcInterrupt+0xc3
ffffd000`21936fe0 fffff801`1808346f : ffffd001`c16a9000 ffffe000`174b6a00 00000000`00000001 ffffe000`116a7b03 : storport!RaidStartIoPacket+0x3f2
ffffd000`21937020 fffff801`1808303a : ffffe000`116a7b10 ffffe000`182a41e0 ffffe000`12abf060 ffffd001`00000096 : storport!RaUnitScsiIrp+0x3ef
ffffd000`219370c0 fffff801`180d9391 : 00000000`00000103 ffffe000`116a7b10 ffffe000`174b6960 ffffd001`00000096 : storport!RaDriverScsiIrp+0x5a
ffffd000`21937100 fffff801`180d8cc2 : ffffe000`17671af0 fffff801`180bcb0f 00000000`00000000 ffffe000`189fb5c0 : storport!PortPassThroughSendAsync+0x1b9
ffffd000`219371b0 fffff801`180d6e0a : ffffe000`189fb5c0 00000000`00000000 00000000`0004d000 ffffe000`12acb1a0 : storport!PortPassThroughExSendAsync+0x72
ffffd000`21937220 fffff801`18098b7c : ffffe000`189fb5c0 00000000`0004d004 ffffe000`12acb1a0 00000000`00000007 : storport!RaidAdapterPassThrough+0xa2
ffffd000`21937270 fffff801`180844c5 : 00000000`00000000 ffffe000`17671af0 ffffe000`189fb5c0 fffff801`180c8000 : storport!RaidAdapterDeviceControlIrp+0x142e4
ffffd000`219372f0 fffff801`180d7e76 : ffffe000`189fb5c0 00000000`0004d004 ffffe000`12acb1a0 ffffe000`12abf1b0 : storport!RaDriverDeviceControlIrp+0x95
ffffd000`21937330 fffff801`180988d1 : 00000000`00000000 ffffe000`11512118 ffffe000`189fb5c0 ffffe000`12abf1b0 : storport!RaUnitScsiPassThroughIoctl+0xfa
ffffd000`219373a0 fffff801`1808448a : ffffe000`18bd7620 fffff801`191642dc 00000000`00000000 fffff801`180c8000 : storport!RaUnitDeviceControlIrp+0x14401
ffffd000`21937420 fffff801`19163a6d : 00000000`00000000 ffffd000`21937560 ffffe000`189fb5c0 00000000`00000000 : storport!RaDriverDeviceControlIrp+0x5a
ffffd000`21937460 fffff801`191416cf : 00000000`00000000 fffff802`3f63ac33 00000000`0004d004 ffffe000`11b97a98 : CLASSPNP!ClassDeviceControl+0x52d
ffffd000`219375d0 fffff801`19168a73 : 00000000`00000000 00000000`c0000910 ffffe000`12aba1b0 ffffe000`117f6c60 : disk!DiskDeviceControl+0x8f
ffffd000`21937660 fffff801`17f34925 : ffffe000`189fb5c0 ffffe000`117f6c60 00000000`00000001 ffffe000`11b977c0 : CLASSPNP!ClassDeviceControlDispatch+0x53
ffffd000`21937690 fffff801`17f22935 : ffffe000`189fb500 00000000`00000000 00000000`00000000 ffffe000`189fb5c0 : partmgr!PmIoctlRedirect+0x4d
ffffd000`21937700 fffff802`3f7f2de2 : ffffe000`11b60090 ffffd000`21937a80 ffffe000`11b60090 00000000`00000001 : partmgr!PmFilterDeviceControl+0x2a5
ffffd000`21937750 fffff802`3f7f1c76 : e0001a02`0fb0fffb 00000000`001f0003 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1162
ffffd000`21937920 fffff802`3f556fa3 : 00000000`00000102 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffffd000`21937990 00007ffc`f51c4ec4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000043`84cff798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`f51c4ec4


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  8bb53bfc2275551627e0bc786fb5077d78d70ab8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  07bc6681eef9d3ec9a0a315b293e557efc81cc97

THREAD_SHA1_HASH_MOD:  101e2f17952a7b9c9c1077e56e35dd0afb4cbb5f

FOLLOWUP_IP:
disk!DiskDeviceControl+8f
fffff801`191416cf 488b4c2450      mov     rcx,qword ptr [rsp+50h]

FAULT_INSTR_CODE:  244c8b48

SYMBOL_STACK_INDEX:  11

SYMBOL_NAME:  disk!DiskDeviceControl+8f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: disk

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5632d16e

BUCKET_ID_FUNC_OFFSET:  8f

FAILURE_BUCKET_ID:  0x19_20_disk!DiskDeviceControl

BUCKET_ID:  0x19_20_disk!DiskDeviceControl

PRIMARY_PROBLEM_CLASS:  0x19_20_disk!DiskDeviceControl

TARGET_TIME:  2016-02-10T10:59:36.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-01-04 20:28:56

BUILDDATESTAMP_STR:  160104-1513

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.63.amd64fre.th2_release.160104-1513

ANALYSIS_SESSION_ELAPSED_TIME: 629

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x19_20_disk!diskdevicecontrol

FAILURE_ID_HASH:  {d33c16fb-cc5f-e3bb-76ce-3c8db2d9afc0}

Followup:     MachineOwner
---------

Dell Moderators/Tech Support,

After extensive testing the last two weeks, I have concluded this:

- My hardware is not faulty/an issue

- All windows updates have been installed / latest version of Windows 10 64-bit is stable

- Overall, my system is stable. The only time it BSOD at this time is when utilizing your SupportAssist program, version 1.2.6745.47

- It is important to note that I've isolated it down to SupportAssist. Once the Intel Dynamic Platform and Thermal Framework drivers are touched/updated, the Dell SupportAssist program will create BSOD each and every time a user attempts to launch it. Switching the Intel Dynamic Platform and Thermal Framework drivers back to their original version, after upgrading them, will not resolve the issue. Once the Intel drivers are touched, Dell SupportAssist is broken/unusable without doing a system Factory Restore, and starting over from scratch.

- Please, fix the very program that is supposed to prevent, fix, and help a user troubleshoot issues! How is it the very program designed to help is causing BSOD issues (i.e. BAD_POOL_HEADER)

- Speaking of which, BAD_POOL_HEADER is the error code that is created each time Dell SupportAssist is launched and BSOD.

- I've ran all the tests, diagnosis, etc. to rule out hardware/other software issues. REFERENCE MY OTHER POSTS that provide you (Dell Tech Support Lvl 3) with all the info you should require to isolate, and resolve, the BSOD surrounding your Dell SupportAssist program version 1.2.6745.47

Alienware 15-R2, i7-6820HK, 980, 4K Touch, 16, 512 PCIe
OC LVL 2
BIOS 1.2.7 LATEST

Problem: CPU down clocks after resuming from sleep S3. Need a Bios update.

How to replicate the issue:
Step 1: In bios, chose Overclock Level 1, 2, 3, or non (Disabled)
Step 2: Start laptop, open task manager, see CPU clock. you will see full OC clock 4.10 Ghz
Step 3: Put the laptop to sleep, wake up the laptop, see clock again stuck at 3.60 GHz

If you're reading this, send it to the correct department.

For what it is worth, I am having exactly the same issues you are having.  Please post with any updates but so far Support Assist is completely a no-go.

Thanks

I have the same problem with SupportAssist on my Alienware 15 R2. This is a software issue and not a driver issue. I got errors on Intel RST driver most of the time. I have basically uninstalled Support assist for now. Even if it were to run a diagnostic on the background, the machine will crash. 

Thanks for posting this.  I received my Alienware 17 r3 about two weeks ago.  Since receiving it, I have experienced BSOD issues a half a dozen times or more per day.  I definitely have this issue, as well as probably more issues.  I see many different error and types of errors in the event log.

I really want this laptop to work reliably, but I am about to send it back.  Stability issues like this are unacceptable, especially for a $3k laptop!

I am also having the exact same crashes on my Alienware 15 R2.  Thanks for your investigation.

I had a similar issue with my new Alienware. They seem to have a bad os image. I downloaded I do of Windows from my Microsoft account and reinstalled. Then it was stable except when running dell support connect software.

Dell Support suggest to return the laptop for a replacement. Did that. The new machine has been stable after I uninstalled dell support software

me 2 the same problem on 15 R2 since 2 month without any reason :-(