- Sep 1, 2017
- 5
- 0
- 510
Hey guys, I was hoping you might be able to help me diagnose these various BSODs I've been getting over the last few months. Excuse my noobiness I'm not exactly a pro at this xD
My specs:
OS: Microsoft Windows 7 Ultimate 64-bit (Desktop)
Motherboard: ASUSTeK COMPUTER INC. (MAXIMUS VII HERO)
Processor: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (architecture: x64; 4001 MHz)
RAM: 2 Sticks of 4.00gb
SSD: Samsung SSD 840 EVO 250G SCSI Disk Device (232.9 GB)
Other Drive: WDC WD20EZRX-22D8PB0 SCSI Disk Device (1.8 TB)
Graphics Card: NVIDIA GeForce GTX 970 (1920x1080x32b)
PSU: Corsair RM750
Right, essentially I've been having consistent BSOD's over the last few months, almost exclusively during gaming on high graphics settings. I would say 90% are 0x124, 8% are 0x101 and say the remaining 2% have been 0xF4 and 0x7a. I'll state what my buddy (my go-to guy on building computers) and I have done so far to try and cut down the list of probable offenders.
Overheating issues: All temperatures well within acceptable levels.
Malware Issues: No Malware on computer.
Driver issues: Used Driver Booster to update everything I could- previous to this i was updating everything manually.
Benchmarking (Graphics card): Used Heaven Benchmark 4.0- everything ran great on highest settings possible, fans kicked in no problem so no overheating. Ran multiple times and no crashes.
Ram testing: Ran memtest overnight for the full amount of passes- no issues with RAM. Also tried re-seating RAM multiple times.
Memory testing: No memory problems whatsoever- ran multiple times using the command prompt.
Overclocking: The graphics card is only Factory Overclocked- I don't mess around with any other overclocking manually.
BIOS: I haven't flashed the BIOS (?) to see if this would fix the problem.
Most of the time the crashes happen when gaming on high settings- these are essentially always 0x124 errors. When gaming on lowest settings I hardly ever get crashes. These crashes have happened during Farcry 4, Guild Wars 2, Total War: Warhammer and Dishonored 2. Note I've never had crashes during games using lower graphics, for example CIV5 or Dark souls series, and hardly ever playing GW2 on lowest graphics settings.
My buddy and I are inclined to think the problem is a failing SSD after exploring all other options and due to the following evidence; Samsung Magician and CrystalDiskInfo once being able to access the drives but now suddenly not recognizing either drive at all even after reinstalling (in addition to occasionally crashing during opening the programs). HWinfo crashing when using Summary-only results and when loading the Drives, slow data transfers even over USB 3.0 ports, when moving icons over the desktop workspace the computer lags out and occasionally crashes or sets all shortcuts to their default location. However, before Samsung Magician failed to read the drives, it stated the drive was in excellent condition (something like 96% intact?).
I'm not really sure how to attach dump files here so I'll copy and paste some of the analysis conclusions from WhoCrashed.
On Sat 23/09/2017 17:08:25 your computer crashed
crash dump file: C:\Windows\MiniDump\092317-11731-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sat 23/09/2017 15:54:12 your computer crashed
crash dump file: C:\Windows\MiniDump\092317-7550-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80081CE028, 0xBE000000, 0x800400)
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.
Before I end up replacing parts, does anybody know whether it's likely the problem is still faulty drivers/software? I'll be reinstalling windows and wiping the damn thing just to see if it is indeed a software problem. I'm also wondering whether the whole problem could be caused by a naff Wireless Adapter I got from BT that disconnects constantly.
I'll try to use a file hosting site if anybody requests the dump files. Thanks guys!
Edit: Shareable link to my google drive with the .dmp files if anybody wants to take a look.
https://drive.google.com/open?id=0B_ycYprcUXDAZ3QtYy1pT1dHMjQ
My specs:
OS: Microsoft Windows 7 Ultimate 64-bit (Desktop)
Motherboard: ASUSTeK COMPUTER INC. (MAXIMUS VII HERO)
Processor: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (architecture: x64; 4001 MHz)
RAM: 2 Sticks of 4.00gb
SSD: Samsung SSD 840 EVO 250G SCSI Disk Device (232.9 GB)
Other Drive: WDC WD20EZRX-22D8PB0 SCSI Disk Device (1.8 TB)
Graphics Card: NVIDIA GeForce GTX 970 (1920x1080x32b)
PSU: Corsair RM750
Right, essentially I've been having consistent BSOD's over the last few months, almost exclusively during gaming on high graphics settings. I would say 90% are 0x124, 8% are 0x101 and say the remaining 2% have been 0xF4 and 0x7a. I'll state what my buddy (my go-to guy on building computers) and I have done so far to try and cut down the list of probable offenders.
Overheating issues: All temperatures well within acceptable levels.
Malware Issues: No Malware on computer.
Driver issues: Used Driver Booster to update everything I could- previous to this i was updating everything manually.
Benchmarking (Graphics card): Used Heaven Benchmark 4.0- everything ran great on highest settings possible, fans kicked in no problem so no overheating. Ran multiple times and no crashes.
Ram testing: Ran memtest overnight for the full amount of passes- no issues with RAM. Also tried re-seating RAM multiple times.
Memory testing: No memory problems whatsoever- ran multiple times using the command prompt.
Overclocking: The graphics card is only Factory Overclocked- I don't mess around with any other overclocking manually.
BIOS: I haven't flashed the BIOS (?) to see if this would fix the problem.
Most of the time the crashes happen when gaming on high settings- these are essentially always 0x124 errors. When gaming on lowest settings I hardly ever get crashes. These crashes have happened during Farcry 4, Guild Wars 2, Total War: Warhammer and Dishonored 2. Note I've never had crashes during games using lower graphics, for example CIV5 or Dark souls series, and hardly ever playing GW2 on lowest graphics settings.
My buddy and I are inclined to think the problem is a failing SSD after exploring all other options and due to the following evidence; Samsung Magician and CrystalDiskInfo once being able to access the drives but now suddenly not recognizing either drive at all even after reinstalling (in addition to occasionally crashing during opening the programs). HWinfo crashing when using Summary-only results and when loading the Drives, slow data transfers even over USB 3.0 ports, when moving icons over the desktop workspace the computer lags out and occasionally crashes or sets all shortcuts to their default location. However, before Samsung Magician failed to read the drives, it stated the drive was in excellent condition (something like 96% intact?).
I'm not really sure how to attach dump files here so I'll copy and paste some of the analysis conclusions from WhoCrashed.
On Sat 23/09/2017 17:08:25 your computer crashed
crash dump file: C:\Windows\MiniDump\092317-11731-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sat 23/09/2017 15:54:12 your computer crashed
crash dump file: C:\Windows\MiniDump\092317-7550-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80081CE028, 0xBE000000, 0x800400)
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.
Before I end up replacing parts, does anybody know whether it's likely the problem is still faulty drivers/software? I'll be reinstalling windows and wiping the damn thing just to see if it is indeed a software problem. I'm also wondering whether the whole problem could be caused by a naff Wireless Adapter I got from BT that disconnects constantly.
I'll try to use a file hosting site if anybody requests the dump files. Thanks guys!
Edit: Shareable link to my google drive with the .dmp files if anybody wants to take a look.
https://drive.google.com/open?id=0B_ycYprcUXDAZ3QtYy1pT1dHMjQ
Facebook
Twitter
Instagram