Sign in with
Sign up | Sign in
Your question
Solved

Multiple BSOD (gaming PC 2 weeks new)

Last response: in Windows 7
Share
June 9, 2014 11:00:11 AM

Hey guys. So getting these dreaded BSOD from my new PC that I built:

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., GRYPHON Z87
CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8524505088 total
radeon r9 280x 3gb videocard
1tb hard drive

I have never had trouble like this before. I ran all the BSOD minidumps on a program called "WhoCrashed", and here are the results for the last 8 or so crashes:

Spoiler
On Mon 6/9/2014 5:17:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060914-12667-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800996F8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 problem. This problem might be caused by a 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 Mon 6/9/2014 4:01:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060914-21231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80077338F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 problem. This problem might be caused by a 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 6/7/2014 2:15:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060714-25646-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8009906028, 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 problem. This problem might be caused by a 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.



On Sat 6/7/2014 2:15:20 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8009906028, 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 problem. This problem might be caused by a 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.



On Sat 6/7/2014 1:38:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060714-25724-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800991B028, 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 problem. This problem might be caused by a 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.



On Sat 6/7/2014 2:51:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060614-25225-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073798F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 problem. This problem might be caused by a 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 Fri 6/6/2014 9:32:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060614-21434-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80099AC028, 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 problem. This problem might be caused by a 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.



On Mon 6/2/2014 4:52:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-14742-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800997F028, 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 problem. This problem might be caused by a 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.



On Sun 6/1/2014 10:19:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060114-23712-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80099A0028, 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 problem. This problem might be caused by a 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.



On Tue 5/27/2014 6:37:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-14445-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xBDAC)
Bugcheck code: 0x116 (0xFFFFFA800AA03010, 0xFFFFF880072B7DAC, 0xFFFFFFFFC0000001, 0x5)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR





I will also upload all of the minidups for convenience:



PLEASE someone help me out here.... As last resort, I'll try reformatting everything. Warranty is still up on all the parts, so maybe if something is faulty, there will be a nice quick fix.


Regards,

Mat.


Dump 1:
https://www.dropbox.com/s/ufnodw08v6rmlxu/060914-21231-...

Dump 2:
https://www.dropbox.com/s/8wue1uvenq5rabe/060914-12667-...

Dump 3:
https://www.dropbox.com/s/wqk2dymifjjqbap/060614-25225-...

More about : multiple bsod gaming weeks

a b $ Windows 7
June 9, 2014 11:04:22 AM

Have you ruled out overheating, 'thermal issues' are referenced in the WhoCrashed analysis. If you are not overclocked then maybe the heatsink isn't on tight or else the thermal compound is messed up.

Did the PC run fine for an extended period before these crashes started?
m
0
l
June 9, 2014 11:05:27 AM

I ran windows memory test and it came back with no errors btw.
m
0
l
Related resources
June 9, 2014 11:06:08 AM

Sry, didn't see your reply. Heating seems to be fine, I've monitored temperatures. Usually crash happens while gaming. I am not overclocked. I use speedfan to test temps.

They seem to be happening more often lately. Not sure if started on day 1 because there was ANOTHER problem that I fixed (idiots who put the computer together didn't plug in CPU FAN).

Computer was auto shutting down whenever the cpu would heat up. Doubt there was damage to cpu since the motherboard usually just shuts it down when temps get high.
m
0
l
a b $ Windows 7
June 9, 2014 11:08:47 AM

All your drivers are up to date? And what make and model PSU do you have?

Just saw the part about the CPU fan. Makes me wonder if the same idiots didn't hook up the heatsink correctly or apply the thermal compound properly.
m
0
l
June 9, 2014 11:12:31 AM

Im pretty sure drivers are up to date.

PSU is: corsair cx750.
m
0
l
June 9, 2014 11:14:16 AM

If they didn't do the heatsink/thermal correctly, shouldn't the temperature readings hint at it? Nothing is overheating during play, I've checked values.
m
0
l
June 9, 2014 11:16:08 AM

BTW, I ran a CPU and GPU stress test (only like 10 minutes each) putting them at 100%, and there was no BSOD. Also didn't overheat.
m
0
l
a b $ Windows 7
June 9, 2014 11:20:27 AM

Sounds like it's video card or cpu/thermal issue since it happens during games only and you passed a memory diagnostic. Just a few ideas:

1. That is a very power hungry video card and that PSU is kind of a lower end Corsair perhaps being pushed too hard.

2. Either the CPU or GPU are overheating. You should get a reading on both under load.

I'd start with the overheating since that is so easy to check.
m
0
l
June 9, 2014 11:22:11 AM

I'll be back online in a few hours. In the mean time, any other ideas greatly appreciated. will run all longest tests tonight.
m
0
l
a b $ Windows 7
June 9, 2014 11:29:33 AM

bjj_mat said:
BTW, I ran a CPU and GPU stress test (only like 10 minutes each) putting them at 100%, and there was no BSOD. Also didn't overheat.


This came in while I was typing my previous response. I guess you should still try the longer tests, ten minutes might not be enough. But if it isn't a heat issue then all I can suggest is fresh drivers and maybe a more powerful PSU, though I would think the Corsair 750 ought to at least be minimally sufficient. Maybe you should contact the seller with problem and tell them too about the CPU fan, the auto throttling and shutdown SHOULD have protected the CPU but you never know.
m
0
l
June 9, 2014 2:22:54 PM

I'd assume if it was the CPU, a 100% stress test for 1 hour should cause a BSOD? Also the same with GPU? I'll start running the stress tests now and see what happens.

If these two things don't cause a failiure, do you recommend I reinstall windows?
m
0
l
June 9, 2014 2:59:37 PM

Alright. So I dont think it's the PSU. I've currently running Prime95 and FurMark both at the same time (stressing CPU and GPU to 100% at the same time). Been 20 minutes, so power supply is doing it's job at maximum effort I think.

ALSO, temperatures, wiith GPU and CPU being stress tested simutaniously are within safe ranges after 20 minutes and stable.

So when you say "fresh drivers", which devices are we talking about? MB/CPU/GPU, or are we talking abou everything including ipod/mic/mouse/keyboard etc.?
m
0
l

Best solution

a b $ Windows 7
June 9, 2014 3:22:20 PM

GPU drivers #1. And I think I would do a 'clean' install, meaning that you remove all traces of existing drivers. Should be an option for that in the Catalyst setup routine. But yes MOBO, chipset, sound, network (probably not mouse/keyboard/ipod). You might like to try this http://www.iobit.com/driver-booster.php (just install it carefully so you don't install any 'add-ons' like search helpers).

This is kind of a kitchen sink approach to your problem but if heat isn't the problem then drivers are very often to blame.

If that does not work i think I would try first a reset of the BIOS to 'optimized defaults' (or just clear the CMOS) and then an actual BIOS update from Asus.
Share
June 13, 2014 6:53:48 AM

I think I fixed it after reinstalling the gpu drivers. Same version of drivers but no more bsod for the last 4 days.
m
0
l
!