BSOD while playing Killing Floor via Steam


  1. highroyds
    Posts : 8
    Windows 7 Home Premium 64Bit
       New #1

    BSOD while playing Killing Floor via Steam


    Hi guys,

    I was playing the game Killing Floor via Steam which I have done for quite some time on this pc but while I was on Vista 32Bit (Home Premium) and not had any problems. But in the last few days I've had 2 BSOD's. The first one I can't remember what I was doing, but the 2nd was playing the game.

    I've attached the dumps to see if anyone can help.

    Cheers

    Edit: Just remembered the 1st BSOD was while I was playing Left 4 Dead 2 and it said something about a DX file had caused the problem.
    Last edited by highroyds; 27 Nov 2009 at 17:51. Reason: More info
      My Computer
    Quote Quote

  3. torrentg
    Posts : 5,747
    7600.20510 x86
       New #2

    Hi,

    Steam does that to Windows 7 systems. It's the norm (and Steam's fault.) Update it to latest if you can.

    You have memory corruption. Update these drivers to latest 2009 version available:

    nmserial nmserial.sys Wed Jan 10 01:44:09 2007
    NmPar NmPar.sys Wed Jan 10 02:13:13 2007
    inflib_x64 inflib_x64.sys Wed Feb 28 07:42:21 2007
    infusb_wlh_x64 infusb_wlh_x64.sys Wed Feb 28 07:42:30 2007
    SiRemFil SiRemFil.sys Wed Jun 20 15:42:10 2007
    SiWinAcc SiWinAcc.sys Thu Jun 14 20:02:02 2007
    SI3132 SI3132.sys Wed Oct 03 14:39:29 2007

    And video card driver from NVIDIA's site too.
      My Computer
    Quote Quote

  4. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #3

    highroyds said:
    Hi guys,

    I was playing the game Killing Floor via Steam which I have done for quite some time on this pc but while I was on Vista 32Bit (Home Premium) and not had any problems. But in the last few days I've had 2 BSOD's. The first one I can't remember what I was doing, but the 2nd was playing the game.

    I've attached the dumps to see if anyone can help.

    Cheers

    Edit: Just remembered the 1st BSOD was while I was playing Left 4 Dead 2 and it said something about a DX file had caused the problem.
    Hi and welcome

    Well I took a quick look at one of the dmps, while waiting for a guru at this to come by. TorrentG is as usual correct. Steam, on win 7 with marginal resources and overclocked machines is a killer. You have 3 distinct problems.
    First the drivers listed below are at least 3 years old, hence we know you didnt do a clean install.
    Second the file tjat probalbly caused this crash dxgmms1.sys has at least 50 references that indicate it as the cause of multiple problems. Update it
    third I think you also have either a memory problem or a heat problem.

    If you are over clocking STOP
    if you have a raid update its driver
    to check your memory dl and run memtestx86 for several hours at least (overnigh preferable)
    run a system file check to verify and fix your system files
    type cmd in search>right click and run as admin>sfc /scannow

    Hppopet his helps and of course if you get any more upload them so we can narrow our/your focus

    Kenn J++


    ASACPI.sys fffff880`0450e000 fffff880`04516000 0x00008000 0x42476c4c 3/27/2005 9:30:36 PM
    secdrv.SYS fffff880`07b96000 fffff880`07ba1000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
    nmserial.sys fffff880`059ab000 fffff880`059c3000 0x00018000 0x45a48b39 1/10/2007 1:44:09 AM
    NmPar.sys fffff880`0598f000 fffff880`059ab000 0x0001c000 0x45a49209 1/10/2007 2:13:13 AM
    inflib_x64.sys fffff880`04734000 fffff880`04739900 0x00005900 0x45e578ad 2/28/2007 7:42:21 AM
    infusb_wlh_x64.sys fffff880`0472c000 fffff880`04734000 0x00008000 0x45e578b6 2/28/2007 7:42:30 AM
    SiWinAcc.sys fffff880`01000000 fffff880`01009000 0x00009000 0x4671d6fa 6/14/2007 7:02:02 PM
    SiRemFil.sys fffff880`017c3000 fffff880`017cb000 0x00008000 0x46798312 6/20/2007 2:42:10 PM
    SI3132.sys fffff880`0114b000 fffff880`01165000 0x0001a000 0x4703e1e1 10/3/2007 1:39:29 PM
    nvm62x64.sys fffff880`044aa000 fffff880`0450dd80 0x00063d80 0x48f8fd12 10/17/2008 4:01:06 PM


    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\K\Desktop\112409-33087-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*d:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0281b000 PsLoadedModuleList = 0xfffff800`02a58e50
    Debug session time: Tue Nov 24 10:18:16.370 2009 (GMT-5)
    System Uptime: 7 days 22:49:45.469
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    .................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005, fffff88004384d26, fffff88005caa188, fffff88005ca99e0}

    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e )

    Followup: MachineOwner
    ---------

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004384d26, The address that the exception occurred at
    Arg3: fffff88005caa188, Exception Record Address
    Arg4: fffff88005ca99e0, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e
    fffff880`04384d26 4a3904f9 cmp qword ptr [rcx+r15*8],rax

    EXCEPTION_RECORD: fffff88005caa188 -- (.exr 0xfffff88005caa188)
    ExceptionAddress: fffff88004384d26 (dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x000000000000008e)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT: fffff88005ca99e0 -- (.cxr 0xfffff88005ca99e0)
    rax=0000000001c36c42 rbx=fffffa80066ee000 rcx=ffff6d1701f5c9e0
    rdx=0000000000000000 rsi=fffffa80066ee000 rdi=fffff8a001f5c160
    rip=fffff88004384d26 rsp=fffff88005caa3c0 rbp=0000000001c36c42
    r8=fffff8a001f5c160 r9=fffff88005caa470 r10=0000000000000000
    r11=fffff880010a0120 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000200 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x8e:
    fffff880`04384d26 4a3904f9 cmp qword ptr [rcx+r15*8],rax ds:002b:ffff6d17`01f5c9e0=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac30e0
    ffffffffffffffff

    FOLLOWUP_IP:
    dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e
    fffff880`04384d26 4a3904f9 cmp qword ptr [rcx+r15*8],rax

    BUGCHECK_STR: 0x7E

    LAST_CONTROL_TRANSFER: from fffff88004382f80 to fffff88004384d26

    STACK_TEXT:
    fffff880`05caa3c0 fffff880`04382f80 : fffff8a0`01f5c160 fffff8a0`01f5c160 00000000`00000000 fffff880`05caa470 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x8e
    fffff880`05caa440 fffff880`04382d97 : 00000000`00000000 fffffa80`066ee000 00000000`00000030 00000000`00000002 : dxgmms1!VIDMM_GLOBAL::MapVideoApertureSegmentInternal+0x15c
    fffff880`05caa5d0 fffff880`0438c54e : 00000000`00000030 00000000`00000001 fffff8a0`01f5c160 fffff8a0`00000020 : dxgmms1!VIDMM_GLOBAL::MapVideoApertureSegment+0x16b
    fffff880`05caa650 fffff880`0438c282 : fffff880`0436fc40 00000000`00030000 fffffa80`063a8830 fffff880`00000000 : dxgmms1!VIDMM_APERTURE_SEGMENT::MapApertureRange+0x62
    fffff880`05caa6b0 fffff880`0438dfa1 : 00000000`00000000 fffffa80`066eec60 fffff8a0`01f5c160 00000000`00030000 : dxgmms1!VIDMM_APERTURE_SEGMENT::MapTemporaryResource+0x76
    fffff880`05caa710 fffff880`0437f904 : fffffa80`063a7830 fffff8a0`01f5c160 fffff880`78000001 fffff8a0`0216dc00 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x7e1
    fffff880`05caa880 fffff880`0437f7e3 : fffffa80`066ee000 fffff880`0437f76c 00000000`00000000 fffffa80`05e2bd10 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x40
    fffff880`05caa8c0 fffff880`0437c70d : 00000000`0000042b 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x43
    fffff880`05caa910 fffff880`0439665d : 00000000`00000000 fffff8a0`024d1010 fffffa80`00000000 fffffa80`05e2bd10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xc79
    fffff880`05caaae0 fffff880`04396398 : fffff880`02f67f40 fffff880`04395d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`05caacd0 fffff880`04395e96 : 00000000`00000000 fffffa80`058ced50 00000000`00000080 fffffa80`065f7410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`05caad00 fffff800`02b30166 : 00000000`038d55d3 fffffa80`063a8b60 fffffa80`03cd0040 fffffa80`063a8b60 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`05caad40 fffff800`0286b486 : fffff880`02f63180 fffffa80`063a8b60 fffff880`02f6dfc0 fffff880`0121b534 : nt!PspSystemThreadStartup+0x5a
    fffff880`05caad80 00000000`00000000 : fffff880`05cab000 fffff880`05ca5000 fffff880`05ca9db0 00000000`00000000 : nt!KxStartSystemThread+0x16


    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME: dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

    STACK_COMMAND: .cxr 0xfffff88005ca99e0 ; kb

    FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e

    BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e

    Followup: MachineOwner
    ---------
    Last edited by zigzag3143; 21 May 2011 at 06:24.
      My Computer
    Quote Quote

  6. highroyds
    Posts : 8
    Windows 7 Home Premium 64Bit
    Thread Starter
       New #4

    zigzag3143 said:
    Hi and welcome

    Well I took a quick look at one of the dmps, while waiting for a guru at this to come by. TorrentG is as usual correct. Steam, on win 7 with marginal resources and overclocked machines is a killer. You have 3 distinct problems.
    First the drivers listed below are at least 3 years old, hence we know you didnt do a clean install.
    Second the file tjat probalbly caused this crash dxgmms1.sys has at least 50 references that indicate it as the cause of multiple problems. Update it
    third I think you also have either a memory problem or a heat problem.

    If you are over clocking STOP
    if you have a raid update its driver
    to check your memory dl and run memtestx86 for several hours at least (overnigh preferable)
    run a system file check to verify and fix your system files
    type cmd in search>right click and run as admin>sfc /scannow

    Hppopet his helps and of course if you get any more upload them so we can narrow our/your focus

    Kenn J++
    torrentg said:
    Hi,

    Steam does that to Windows 7 systems. It's the norm (and Steam's fault.) Update it to latest if you can.

    You have memory corruption. Update these drivers to latest 2009 version available:

    nmserial nmserial.sys Wed Jan 10 01:44:09 2007
    NmPar NmPar.sys Wed Jan 10 02:13:13 2007
    inflib_x64 inflib_x64.sys Wed Feb 28 07:42:21 2007
    infusb_wlh_x64 infusb_wlh_x64.sys Wed Feb 28 07:42:30 2007
    SiRemFil SiRemFil.sys Wed Jun 20 15:42:10 2007
    SiWinAcc SiWinAcc.sys Thu Jun 14 20:02:02 2007
    SI3132 SI3132.sys Wed Oct 03 14:39:29 2007

    And video card driver from NVIDIA's site too.
    Thanks for the replies guys,

    I didn't know about the problems with Windows 7 and Steam. I did do a Full Clean install with Windows 7 as I formatted the hard drive that used to have my Vista installed on. So the drivers that were installed came from Microsoft themselves including the Nvidia. I'll have a look at updating the drivers and see if I can get them updated.

    I've got the very latest Steam version as that keeps updating automatically.

    inflib_x64 inflib_x64.sys Wed Feb 28 07:42:21 2007
    infusb_wlh_x64 infusb_wlh_x64.sys Wed Feb 28 07:42:30 2007

    These two drivers I know for a fact are the latest.

    Cheers for your help and once I've gotten the drivers updated I'll let you know what happens if anything. Though I do remember changing a few settings in my BIOS before installing Windows 7, so I've reverted them as I thought it would help my system.
      My Computer
    Quote Quote

 

  Related Discussions
BSOD When playing some games on Steam
in BSOD Help and Support

Hi, I've been having this problem for a while now but have pretty much just been ignoring it, but its got to the stage where I can't play games without it happening. I've tried googling the errors I get but am not sure if what is coming up is specific to my problem. I'm running windows 7 x64,...
BSOD playing most steam games
in BSOD Help and Support

wondering if someone could help me so my computer has been crashing these past few weeks when playing games and skyping when i play minecraft league of legends sometimes blade and soul ark survival arma 3 i get BSOD or a weird freeze where it makes a loud sound constantly and i have to turn my...
BSOD while playing Steam games?
in BSOD Help and Support

If the title is misleading, I apologize in advance, but that's the only time I've experienced this problem thus far. I have a fear that it's endangering my computer, so any help would be greatly appreciated. Thanks!
Windows 7 Enterprise -32bit -age of system: 1 month old(still new) -age of OS: 1 month old I was just playing Garry's Mod online, then the computer just had a BSOD. The game has a problem sometimes where the whole game would freeze or just a part of the game would stop working. Any ideas on...
Hello, I didn't know where to post this to be honest so feel free to move this if needed... anyways here it goes... I have recently purchased Killing Floor and I love it, it runs GREAT on Windows 7 RC I'm using the 7100 Build, my issue is more of an annoyance than anything else, but I digress......
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 14:50.
Find Us