IN DESPERATE NEED OF HELP - Please help me verify if my hardware is dead or not

[iviascitelli]

Hi Guys

I have a Lenovo Legion Y520 Laptop with Intel Core i7-7700k (2.8GHz) CPU and GeForce GTX 1060 GPU with Max-Q Design, as well as Intel(R) HD Graphics 630 OnBoard.
I need help figuring out if I need to get a new computer, or if there is something I can fix with this one. Below I will detail absolutely everything I know about my issues, and what I've done to try to fix them:

WHAT IS THE PROBLEM?
- Essentially, my computer cant do anything intensive without crashing (BSOD). I can still use my computer for basic purposes, but at this point I am absolutely not able to game on it. I usually like to play Slap City or other Steam games on an HDMI monitor plugged into my computer.
- The crashes ALWAYS happen when playing video games, but happen FASTER if there are peripherals plugged in (especially HDMI, Mayflash adapter)
- The crash has happened before when I wasnt even playing video games, just browsing or downloading a program (basically anything semi-intensive the computer will crash)
- I tried DISABLING Nvidia graphics to use just Intel onboard graphics, but it still crashed (i did this because i got a BSOD error message that had to do with Nvidia drivers one time)
- Important Observation:The cooling fan in the computer runs VERY LOUD when the computer isnt even doing anything (ex - starting task manager and you can HEAR the fan speed up dramatically)
- This guy has the same errors pretty much: http://www.tomshardware.com/answers/id-3289079/win10-random-crashes-checked-ram-cpu-gpu-faulty-motherboard.html
- Does this sound like a RAM issue? I'm going to run memtest86 overnight tonight and then post the results here.


BSOD ERROR MESSAGES
- So the error message that appears on my BSOD changes every time, unfortunately. Here is every BSOD error message I've encountered...
DRIVER IRQL NOT LESS OR EQUAL - iaStorA.sys
KMODE_EXCEPTION_NOT_HANDLED
PAGE FAULT IN NONPAGED AREA
SYSTEM SERVICE EXCEPTION - dxgkrnl.sys
MEMORY MANAGEMENT
SYSTEM THREAD EXCEPTION NOT HANDLED - igdkmd64.sys
DRIVER POWER STATE FAILURE

WINDOWS 'SYSTEM' EVENT LOGS
- I performed a RAM check using Windows Memory Diagnostic and here's the main 2 things I found in the 'System' Windows Event Logs:

- The speed of processor X in group 0 is being limited by system firmware (X = 1-6)
- The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user DESKTOP-QG4290Q\Robert SID (S-1-5-21-2386444776-1438355750-1093711146-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

WHOCRASHED ANALYSIS
- Finally, I used the "WhoCrashed" program to analyze the dump logs after a crash. Here's what it found:

System Information (local)
Computer name: DESKTOP-QG4290Q
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: 80YY, LENOVO, LNVNB161216
CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17066790912 bytes total

Crash Dump Analysis
Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 2018-10-07 12:59:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100718-7921-01.dmp
This was probably caused by the following module: igdkmd64.sys (0xFFFFF80189034C7F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80189034C7F, 0xFFFFD903D5E1EA38, 0xFFFFD903D5E1E280)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_1a33d2f73651d989\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: igdkmd64.sys Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sun 2018-10-07 12:59:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: igdkmd64.sys (0xFFFFF80189034C7F)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80189034C7F, 0xFFFFD903D5E1EA38, 0xFFFFD903D5E1E280)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_1a33d2f73651d989\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: igdkmd64.sys Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Sun 2018-10-07 12:55:14 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100718-7812-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1D9D51)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803B4EDB423, 0xFFFFC90A608EF5C8, 0xFFFFC90A608EEE10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_88a8b806be065157\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 391.25
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 391.25
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 391.25 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sun 2018-10-07 12:52:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100718-7578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0x1A (0x61941, 0x4C60250, 0xD, 0xFFFFF88C764AFA00)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2018-10-07 12:41:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100718-7609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80D6C936D17, 0xFFFFF684F559E250, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Sun 2018-10-07 12:35:56 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100718-6609-01.dmp
This was probably caused by the following module: iastoravc.sys (0xFFFFF802F78C0BFA)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFF802F78C0BFA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastoravc.sys
product: Intel(R) Rapid Storage Technology driver (inbox)
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver (inbox) - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

Conclusion
6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 391.25 , NVIDIA Corporation)

^ The problem with this is that my NVIDIA and Intel drivers are already up to date. So I'm not sure what else to do.

 

[asoroka]

The fact that you can hear the CPU fan means that the CPU is getting hot.

You should probably look at replacing the thermal paste between CPU and HS.

Taking laptops apart is painful, so if you are not confident, take it in to the service centre and get them to check your heatsink.

This can happen to laptops as they are mobile machines. You need to decide if its worth spending the money (1hr labour) vs getting a new laptop.
Is it still under warranty?

 

[johnbl]

basically since your error coded during your bugchecks involve this error code
0xC0000005 you will want to update the BIOS to get the best default memory timings then boot and run memtest86 on its own boot image to confirm your memory timings are correct.

one of the bugchecks involve memory management involving access to virtual memory.
generally you would update the sata driver and chipset drivers from your motherboard vendor and run crystaldiskinfo.exe (google for download) the tool can read the SMART errors from the disks.

all of these problems can occur with memory errors, most of the video problem can be caused by overheating of a PSU,gpu or CPU. (blow dust out)

most of the problems can also be caused by overclocking software for the GPU or CPU (remove any overclock drivers)

provide the actual c:\windows\minidump files for a better idea as to the problems cause.
ie copy the files to a cloud server like Microsoft onedrive, share the files for public access and post a link.

also, make sure you update the motherboard sound drivers. some motherboard sound drivers mess up the GPU sound support and crash the various graphics drivers.

the bugcheck 0xd1 while attempting to access memory address 1
is likely to be something (a driver) corrupting data belonging to other drivers.
often this type of corruption is hard to detect since the driver is likely corrupting data of another driver in memory next to it. Window loads drivers in different orders on each boot so you get corruption of different device driver data on each boot.

I would update the various motherboard drivers from the vendors website. if you still get the problem you might run verifier.exe to force the system to bugcheck when a driver corrupts some other drivers data.