New
#1
BSODs on Alienware 18
My Alienware 18 was my backup computer until my primary computer died. Now that it is my primary computer I have experienced frequent BSODs. I use this computer primarily for gaming (Warcraft). To my knowledge the crashes have only occurred during gaming.
Note: There should be many more crash reports, so I'm not sure why only two appear in the C:\Windows\Minidump folder. (I disabled CCleaner from deleting these files).
Win 10 is up-to-date as are all of my drivers. I don't know what else to check.
Purchased: Sep 27, 2013
Here are some specs (if it helps):
Processor: Intel Core i7-4930MX CPU @ 3.00 GHz 3.10 GHz
Installed memory (RAM): 32.0 GB (31.8 GB usable)
System type: 64-bit Operating System, x64-based processor
Although this info is probably redundant with the information in the attached file, I included it in case there's anything helpful in it. It is from "WhoCrashed"
On Sat 10/15/2016 06:50:46 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFF8701D05E3790)
Bugcheck code: 0x139 (0x3, 0xFFFF8701D05E3790, 0xFFFF8701D05E36E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_SECURITY_CHECK_FAILURE
On Wed 10/12/2016 00:26:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-25906-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8015220E389)
Bugcheck code: 0xA (0x3C, 0xD, 0x0, 0xFFFFF8015220E389)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 10/7/2016 17:22:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100716-23734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD5FF2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027B159FF2, 0xFFFFAC80DD5B43C8, 0xFFFFAC80DD5B3BF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
3 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Thanks in advance for your assistance.
Quote