Tech Support Forum banner

LFD - does it run in Win7 - 64 bit?

1589 Views 6 Replies 2 Participants Last post by  pikeman666
L4D installed OK, Steam OK. Should have received any patches in Steam link.
Intro runs OK, but system crashes hard when a game is launched. Must restart in safe mode and the reboot again to recover. System has been stable for over six months and this game killed it dead!

My system:
Win7 Ultimate 64-bit, Asus M4A79XTD EVO w/updated BIOS, AMD Phenom X3 435, fourth core activated, 4Gig G Skill DDR3 PC12800, Radeon 4830, 512Meg, Catalyst Control Center 2010.0504.2152.37420, Samsung HD502 HD
Not open for further replies.
1 - 7 of 7 Posts
Please provide this information:

Although this may not be BSOD related, the reports contain information on system errors that we can use.
Answer to: Re: LFD - does it run in Win7 - 64 bit?

OS - Windows 7 Ultimate
· x64
· What was original installed OS on system? None - new build
· Full retail version
· 7 months old
· Age of OS installation -7 months
· CPU - AMD x3 435 with 4th core unlocked
· Video Card- Radeon 4830, 512Meg, Catalyst Control Center 2010.0504.2152.37420
· MotherBoard - ASUS M4A79XTD EVO w/updated BIOS
· Power Supply - Antec 550

Looked at the report - I'm not trained - but the services halted had nothing to do with the OS crashing. Plus this was no BSOD. It was a "killed the OS dead" event. Never saw a blue screen. Never have on this machine since building it in January. So does L4D run on Win 7/64 or not?
Thanks for your interest.


See less See more
L4D runs on my Win7 64 bit and my son's Win7 32 bit (on an M4 series board) systems.
I know that you didn't mention BSOD's - but the reports are needed for the information that they provide.

Please zip up and upload this file:

Also, search your system for any files ending in .dmp, the zip them up and upload them with your next post. If they're too big to upload, please upload them at a free file hosting service and post a link to them so we can download them.
requested file is attached.
No dmp files - used the search utility . . .


This is a STOP 0x117 error that, for some reason, wasn't trapped by the normal error handling mechanisms.

It points at atikmpag.sys - a component of your ATI video drivers.
Please do the following:
- visit and download the DISPLAY DRIVER ONLY - DO NOT download the entire Catalyst Control Center as some people have had issues with it.
- uninstall all ATI stuff from your system using Control Panel...Programs...Uninstall a program
- install the DISPLAY DRIVER ONLY and see if that stops the BSOD's.

If not, please have a look at the suggestions in this link:
The STOP 0x117 and the STOP 0x116 errors are very similar - so the troubleshooting will be the same.

As a last resort, borrow a video card and try that (don't buy one unless you know that you can return it).

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page:
- - Driver manufacturer links are on this page:

Here's the older drivers (You can look them up here: ).
Please pay particular attention to any dated 2008 or earlier:
SSPORT.sys    Thu Aug 11 19:07:32 2005 - Samsung printer driver -
AsIO.sys      Mon Dec 17 04:11:49 2007 - Asus PCProbe Utility -
Text of the memory dump:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\WD-20100701-1331.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is: SRV*c:\symbols*
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
Debug session time: Thu Jul 1 14:31:18.787 2010 (UTC - 4:00)
System Uptime: 3 days 10:12:02.192
Loading Kernel Symbols
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8005bbb1e0, fffff88003b3d67c, 0, 0}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+667c )

Followup: MachineOwner

2: kd> !analyze -v
* *
* Bugcheck Analysis *
* *

The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arg1: fffffa8005bbb1e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003b3d67c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:

fffff880`03b3d67c ?? ???


TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b




fffff880`03fc7630 fffff880`0405d4ef : fffffa80`05bbb1e0 00000000`00000080 fffffa80`05bbb1e0 fffff880`0402b843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03fc7b50 fffff880`0405e1b4 : fffff8a0`0340c840 fffff8a0`0340c840 00000000`00000080 fffffa80`05bbb1e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03fc7ba0 fffff880`040326b3 : 00000000`00000001 fffffa80`05dbc000 00000000`00000000 fffff880`0000009f : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`03fc7bd0 fffff880`0405ed07 : 00000000`00000000 ffffffff`fffe7960 fffffa80`05bbb1e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`03fc7c80 fffff880`0412dec1 : fffffa80`05e94540 00000000`00000080 00000000`00000000 fffffa80`05d94410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03fc7d00 fffff800`02d79a86 : 00000000`039a41a5 fffffa80`05ac2a10 fffffa80`039cc040 fffffa80`05ac2a10 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03fc7d40 fffff800`02ab2b06 : fffff800`02c4ee80 fffffa80`05ac2a10 fffff800`02c5cc40 fffff880`0120f534 : nt!PspSystemThreadStartup+0x5a
fffff880`03fc7d80 00000000`00000000 : fffff880`03fc8000 fffff880`03fc2000 fffff880`06796b60 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

fffff880`03b3d67c ?? ???

SYMBOL_NAME: atikmpag+667c


MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys


FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

Followup: MachineOwner
See less See more
I uninstalled the catalyst control center.
I followed the link and tried four old drivers, and there was no improvement. I also discovered a thread relating to DX9.0c on another forum. Turns out that this version was distributed with the game at release. According to the thread, although Win7 includes DX11, there are supposedly some components missing to make it entirely backward compatible. That does not make sense to me, but I located DX9.0c and installed it. And it crashed again - even safe mode would not launch so I'm in startup repair mode and using a restore point I created this AM before beginning this adventure. So I guess that's a worse crash than before.

I'm really amazed at this. I installed and am successfully playing Halflife 2 episode 1. I went through the entire first level with no issues. However I had a crash with the "Lost Coast" episode. So there is really something fishy going on. I'm going to uninstall LFD and reinstall and see if that makes any difference.
See less See more
1 - 7 of 7 Posts
Not open for further replies.