BSOD Playing BF3 - Help newbie please

[Herefordquattro]

Good evening folks, hoping for some help with a recurring BSOD, i've tried analyzing the dump file but don't know wahti'm looking at areally so over to the experts:

Playing BF3 i've been getting the occasional lock up (also with Crysis3) and the screen goes blank and will recover to desktop eventualy but tonight i've had BSOD.

MB and CPU are old but stable and GPU is very new, have recently updated Nvidia driver but been ok till last couple of days.

Help please....

Minidump zip attached

 

[Golden]

Hi,

There appears to be both a thermal and graphics related issue going on here.

crash dump file: E:\Debug2\111012-9468-01.dmp
uptime: 05:45:45
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004EBD028, 0xB2004000, 0xF4000175)
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.

Lets deal with the thermal issue first. Please ensure that the fans on the PC are clean and operating normally. Now please follow this to stress test your CPU - note read the tutorial carefully before proceeding. Once the program completes, post a screen capture image of the results and the temperature reported by HWINFO.

http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

crash dump file: E:\Debug2\101912-9218-01.dmp
uptime: 01:11:00
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800FBB6004) 
Bugcheck code: 0x116 (0xFFFFFA8003FEE4E0, 0xFFFFF8800FBB6004, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
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: nvlddmkm.sys . 
Google query: nvlddmkm.sys VIDEO_TDR_ERROR

Completely uninstall the NVidia card drivers - there is a known problem with the latest drivers. Reboot the system, Windows update will run and attempt to install the latest Microsoft signed Nvidia driver (which will not be the problematic one).

Run your games and report back if you get new BSODS.

 

[Herefordquattro]

a reply already thank you. I'm off to bed now but will run stress test in morning. cpu is water cooled so shouldn't be thermal problem I hope...

 

[Golden]

Yes, I noticed the water-cooling - perhaps the thermal paste needs re-applications? lets see.

 

[Herefordquattro]

maybe so. the cpu not been out in 3 years since I fitted water loop. ill test and report back tomorrow. thanks again

 

[Herefordquattro]

oh bugger.
First attempt didn't even finish 2nd run before reporting unstable on standard!
I turned the overclock down 100Mhz and got much better results; managed to complete standard and high no problems.
Ran very high and it got through 1 run then blue screened on the second.
ill post up temps from high run later (on my phone now).
is it worth me copying dump files or is it obvious temp?

 

[Golden]

I turned the overclock down 100Mhz and got much better results

Ahhh, I should have thought of that. Please turn OFF all overclocking, then run it again on high - watch those temperatures carefully!

 

[Herefordquattro]

ok will do. always been confused on temps as k10 sensor is always 10-15 deg lower than Mb reading. max temp on 9950 is 60 deg allegedly which seems very low for 140w.,

 

[Herefordquattro]

Ran Intelburn on very high setting and passed with NO overclock at max 51.5c (34deg at idle) so OK there.

Assume my current OC is a bit much so may lower till it plays games ok, realisticaly the stress of very high intel burn is more than i should expereince in day to day running and gaming isn't it?

Without being able to dechipher dump files though i'm stuck.

still issues with latest gpu driver though?

next step golden?

cheers

Jake

 

[Golden]

realisticaly the stress of very high intel burn is more than i should expereince in day to day running and gaming isn't it?

Absolutely, yes it is. For now, don't overclock - clearly it was an issue with the earlier tests you ran.

Did you follow previous suggestion for the Nvidia driver?

 

[Herefordquattro]

no not looked at driver yet, it is very recent so may be buggy I guess. ill investigate more tomorrow.
cheers

 

[Golden]

Completely uninstall the NVidia card drivers - there is a known problem with the latest drivers. Reboot the system, Windows update will run and attempt to install the latest Microsoft signed Nvidia driver (which will not be the problematic one).

 

[Herefordquattro]

driver uninstalled and MS signed one installed automatically.

It's very old though, gone from 310.90 back to 306.23?

 

[Golden]

Yep, thats OK. We have seen loads of BSODS due to the latest drivers from Nvidia. The 306.23 is what all our analysts are currently recommending.