Alienware 15 R2 BSOD

Hi, 

So the BSOD always occurs during boot? I assume you ran the ePSA/Diagnostics test in the Boot menu correct?

Yes running the diagnostic check from bios came clean. But running the stress test within windows using the Dell tool caused the laptop to crash after some time.

Unfortunately this is the Alienware 15 R2 with 4K display, i7 6800K series processor, 16 GB ddr 4 ram, 256gb Samsung NVME SSD + 1 TB HDD, Killer Wifi + Ethernet (not customizable). 

Seems refund / return and replace is only viable option

dude, get a refund and get a 17 R3 with 4k lcd panel. it's fantastic. Make sure to choose intel wifi card. Never never choose killer wifi.

How did you exactly factory reset? Like a fresh installation of windows?

Since the crashes are due to driver, can you go to device manager and update all of your system components?

It's due to windows 10. Use SupportAssist software. Choose system history (system events), then click on the date and cause of system crashes. Google search remedy. I used to have a lot of crashes with my AW 17 R3. Disabling some system service prevent crashes, now no crashes.

Is there somehow we can get Dell support who can read the dump logs and provide the analysis of the issue. The generic  irql_not_less_or_equal indicates a kernel lever driver issue. But sometimes just uninstalling the app seems to resolve the issue. 

To me this seems to be a software issue. Trying to manually troubleshoot each service one by one is not practical. Better option would be for support to analyse the error logs / crash dumps and suggest few services which can be tested . 

*** yes. I was with them for 2 hours on the day I got the laptop in my hand. Had done system reset 4 times and then finally gave up and called support. 

They basically showed me how to boot in safe mode and suggested to restrict virtual memory between 2 GB to 4 GB (not sure why this is needed why RAM is 16GB) and then suggested to enable each service one by one and reboot and see what causes BSOD. 

I just thought it was easier to do another factory reset and then install one app at a time and then test. Finally got the PC working for a day with no crash. Then it has now been crashing intermittently. 

I have 2 minidump from 0201, 5 minidump from 0202 and now 3 minidump in the past 1.5 hours on 0203. 

Finally thinking that this was the biggest mistake of my life and going to get this replaced. If nothing else works, will ask for a refund. 

Just ran SupportAssist and the laptop BSOD on me and crashed with error Bad Pool Header

holy cow. did you call aw tech support? i know they are useless but maybe they can entertain you for a while.

;Running SFC shows errors on few DLL and windows is not able to fix it. Seems the windows 10 pro image deployed on the laptop is corrupted. Is this true....

End of SFC log shows :

2016-02-03 21:42:58, Info CSI 00004f90 [SR] Beginning Verify and Repair transaction
2016-02-03 21:42:58, Info CSI 00004f91 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-03 21:42:58, Info CSI 00004f92 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-02-03 21:42:58, Info CSI 00004f93@2016/2/4:02:42:58.917 Primitive installers committed for repair
2016-02-03 21:42:58, Info CSI 00004f94 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-03 21:42:58, Info CSI 00004f95 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-02-03 21:42:58, Info CSI 00004f96 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-02-03 21:42:58, Info CSI 00004f97 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-03 21:42:58, Info CSI 00004f98 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-03 21:42:58, Info CSI 00004f99 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-02-03 21:42:58, Info CSI 00004f9a@2016/2/4:02:42:58.948 Primitive installers committed for repair
2016-02-03 21:42:58, Info CSI 00004f9b [SR] Repair complete
2016-02-03 21:42:58, Info CSI 00004f9c [SR] Committing transaction
2016-02-03 21:42:58, Info CSI 00004f9d Creating NT transaction (seq 2), objectname [6]"(null)"
2016-02-03 21:42:58, Info CSI 00004f9e Created NT transaction (seq 2) result 0x00000000, handle @0x1028
2016-02-03 21:42:58, Info CSI 00004f9f@2016/2/4:02:42:58.995 Beginning NT transaction commit...
2016-02-03 21:42:59, Info CSI 00004fa0@2016/2/4:02:42:59.011 CSI perf trace:
CSIPERF:TXCOMMIT;25958
2016-02-03 21:42:59, Info CSI 00004fa1 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Just ran SupportAssist and the laptop BSOD on me and crashed with error Bad Pool Header

that seems to be a common problem, see en.community.dell.com/.../19670599

do you have a fresh copy of windows 10? do a fresh installation. Make sure to write down your windows 10 key before downloading it.

Yes, I received my Alienware 15 r2 a couple of weeks ago.  On a full days use I get 2-3 BSOD with "bad pool header" as the fail.

To get even one isn't acceptable as I require a machine that is dependable for data loss and security.

My self built desktop has been on Win10 since release without a single BSOD.  To spend this much on a laptop and have this experience is disappointing to say the least.    My help desk ticket is in, but this will be returned rather fast if I don't get full resolution.  I have to depend on the system.

Not interested in spending my weekends or evenings refreshing or removing bloatware.