Sign in with
Sign up | Sign in
Your question
Solved

Return of the BSOD

Last response: in Systems
Share
December 14, 2013 7:03:27 PM

I previously posted on the forums about this issue about a week ago:
http://www.tomshardware.com/answers/id-1908611/absence-...
http://www.tomshardware.co.uk/answers/id-1907728/bsod-g...

I thought I found the fix when I started using an older NVIDIA driver based on responses on the forum which worked GREAT. I've been gaming off and on for the last week until today. I havent installed any new updates. My system is as follows:
mobo: Maximus V Extreme
CPU: intel i7 2600K at stock
GPU: GTX 690
PSU: OCZ 1000W

I ran whocrashed, which showed:

On Sun 12/15/2013 2:42:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121413-9984-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8010970028, 0xBE200000, 0x5110A)
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 12/15/2013 2:42:49 AM 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, 0xFFFFFA8010970028, 0xBE200000, 0x5110A)
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 Fri 12/13/2013 11:10:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-9937-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8010909028, 0xBE200000, 0x5110A)
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 Fri 12/6/2013 2:36:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120613-9765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.

So I've been busting my bottom to figure out if it is my graphics card or my cpu. I reapplied a fresh coat of thermal paste and placed my Hyper212 Evo. I've been running realtempGT and the EVGA precision X (software that came with gpu) to monitor these 2 components while gaming. While playing SWTOR, cpu at biggest load of about 29% had max temp of low 60s and gpu temp in 50s (Celsius of course). I got to Skyrim and in fullscreen mode things are going fine. I lose myself and after about 20 mins BAM, screen freezes. I restart, fire up Skyrim, game for about 10 mins then BSOD again. What other thermal issue is there if not the cpu or gpu? Am I missing a cpu or gpu thermal issue? Could it be my HDD?

More about : return bsod

Best solution

December 14, 2013 7:15:55 PM

I believe I remember your previous post and it looks like you have plenty of information. Since the problem seems to happen while gaming do you have or can get a hold of a video card you can test against?
Share
December 14, 2013 7:46:31 PM

neieus said:
I believe I remember your previous post and it looks like you have plenty of information. Since the problem seems to happen while gaming do you have or can get a hold of a video card you can test against?


My wife has a 560 Ti which I cant strip from her comp until a few days from now. I guess this IS the best way to test this. In the meantime I'm figuring out how I can rma my graphics card to newegg (bought it over 30 days ago so wont be easy, plus for some reason they dont have this type of 690 in stock anymore...hmmm, wonder why?)
m
0
l
Related resources
December 14, 2013 7:54:22 PM

Well if the video card is the problem you will need to RMA with the manufacture it actually is the video card. Either way confirm it first before you waste time with RMA processing.
m
0
l
December 15, 2013 3:25:11 PM

neieus said:
Well if the video card is the problem you will need to RMA with the manufacture it actually is the video card. Either way confirm it first before you waste time with RMA processing.


Will do. FYI I just ran Valley Benchmark from Nvidia to see if it'll cause a bsod. Wanted to do something while waiting to use another GPU. My GPU temp went up to 75-77C but no crash while CPU was about 50C. I'm sure its GPU now since thats pretty high although not 80s its close. what else could it be? I'll let you know results when using another GPU while gaming?
m
0
l
!