BSOD BF3, error 1053, 0x116, dxgkrnl.sys, dxgmms1.sys, nvlddmkm.sys.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes.
- an OEM or full retail version? Full retail version


- What is the age of system (hardware)? One year approx.
- What is the age of OS installation (have you re-installed the OS?) A few days old, Reinstalled alot of times to try and sort the problem.

I also included a Speccy generated text file with my computer specs.

The crash/lockup occours mainly when playing BF3 on certain levels, skip the level and I can play the game continously for hours sometimes.

The dumpfile at 20:10 was created while playing BF3 on a normal level.


The second dumpfile which was created at 20:30 was done by using the Drive verifier, Looks like Daemon tools might have a finger in it so I'll uninstall that right now.

Quite a few issues here

1-asacpi.sys

Asacpi.sys

The pre 2009 version of this driver is a known bsod cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).

2-Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


3-BBC116

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Updated asacpi.sys.

Removed CD/Dvd emulation program.

Going to open up my Chassi and try to attach a fan to blow directly on the GPU.

Anything else I can do?

Whoopie said:

Updated asacpi.sys.

Removed CD/Dvd emulation program.

Going to open up my Chassi and try to attach a fan to blow directly on the GPU.

Anything else I can do?

Keep track of the temps when it crashes, and wait I guess. It may not. Asacpi.sys is a huge cause.