Hi guys
So for the past couple of months i have been plagued by frequent and unavoidable BSOD on my PC. I've taken it into a repair shop twice and the second time his assertion was that there was something wrong with the power supply. After having that replaced I am still having these crashes. Weirdly enough i can induce these crashes by doing something as simple as plugging in an HDMI cable (which is why i think it might be the GPU now), and these crashes originally started when the desk my PC is on was moved. I'll post my specs below and even a crash dump analysis from "who crashed" if that'll help. If anyone has any suggestions or ideas it would be greatly appreciated because i am at wits end with this.
Specs
Operating System
Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i7 4770K @ 3.50GHz
Haswell 22nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 801MHz (10-10-10-30)
Motherboard
ASUSTeK COMPUTER INC. Z87-A (SOCKET 1150)
Graphics
ASUS VS238 (1920x1080@60Hz)
2047MB NVIDIA GeForce GTX 770 (Gigabyte)
Storage
931GB Western Digital WDC WD1003FZEX-00MK2A0 ATA Device (SATA)
232GB Samsung SSD 840 EVO 250GB ATA Device (SSD)
Crash dump analysis
On Sat 1/27/2018 4:30:30 PM your computer crashed
crash dump file: C:\Windows\Minidump\012718-5194-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D44E028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
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.
So for the past couple of months i have been plagued by frequent and unavoidable BSOD on my PC. I've taken it into a repair shop twice and the second time his assertion was that there was something wrong with the power supply. After having that replaced I am still having these crashes. Weirdly enough i can induce these crashes by doing something as simple as plugging in an HDMI cable (which is why i think it might be the GPU now), and these crashes originally started when the desk my PC is on was moved. I'll post my specs below and even a crash dump analysis from "who crashed" if that'll help. If anyone has any suggestions or ideas it would be greatly appreciated because i am at wits end with this.
Specs
Operating System
Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i7 4770K @ 3.50GHz
Haswell 22nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 801MHz (10-10-10-30)
Motherboard
ASUSTeK COMPUTER INC. Z87-A (SOCKET 1150)
Graphics
ASUS VS238 (1920x1080@60Hz)
2047MB NVIDIA GeForce GTX 770 (Gigabyte)
Storage
931GB Western Digital WDC WD1003FZEX-00MK2A0 ATA Device (SATA)
232GB Samsung SSD 840 EVO 250GB ATA Device (SSD)
Crash dump analysis
On Sat 1/27/2018 4:30:30 PM your computer crashed
crash dump file: C:\Windows\Minidump\012718-5194-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D44E028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
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.