BSOD Running Crysis (dxgmms1.sys)

I know these forums are quite busy lately, but any help from knowledgeable parties would be most welcome. I have a freshly-installed (last night) and updated copy of Windows 7 Pro 64-bit with nothing but device drivers, Firefox, and iTunes installed. I then proceeded to install Crysis Warhead with Patch 1.1 and ran the 64-bit executable. About 10 minutes or so into the game, the graphics freeze, the screen goes black, and the sound locks up. All of this takes about 1.5 seconds and then the BSOD appears, citing "dxgmms1.sys" as the problem. I had been smoothly running the game in 1650x1080 with every setting at maximum except for disabled motion blur.

I sought help from the internet and couldn't find much on the matter. I have uninstalled my graphics driver, run DriverSweeper in Windows safe mode, and re-installed a newly-downloaded copy of the drivers. This has not helped my problem. My system specs can be seen in my profile but I'll post them here if you wish. When someone has the time, I would very much appreciate any thoughts or suggestions. Cheers!

High temperatures are not the issue. I ran two stress tests: Prime95 64-bit for my CPU, and OCCT for my GPU. The hardware got a workout but no errors were reported. I ran the Windows Memory Diagnostic twice at startup with no errors. I have a Silverstone 750W power supply that is about three months old and powered the same hardware in XP.

Hi.

Update your chipset drivers from here.

Also, there's a relatively new bios that you should install. After these changes, the system should run well.

Let us know how it goes.

Monotony said:

I know these forums are quite busy lately, but any help from knowledgeable parties would be most welcome. I have a freshly-installed (last night) and updated copy of Windows 7 Pro 64-bit with nothing but device drivers, Firefox, and iTunes installed. I then proceeded to install Crysis Warhead with Patch 1.1 and ran the 64-bit executable. About 10 minutes or so into the game, the graphics freeze, the screen goes black, and the sound locks up. All of this takes about 1.5 seconds and then the BSOD appears, citing "dxgmms1.sys" as the problem. I had been smoothly running the game in 1650x1080 with every setting at maximum except for disabled motion blur.

I sought help from the internet and couldn't find much on the matter. I have uninstalled my graphics driver, run DriverSweeper in Windows safe mode, and re-installed a newly-downloaded copy of the drivers. This has not helped my problem. My system specs can be seen in my profile but I'll post them here if you wish. When someone has the time, I would very much appreciate any thoughts or suggestions. Cheers!

hi and welcome. all three of the dumps was about the same. It seems that they were probably cusued by your video driver. the specific file is dxgmms1.sys.

I would update the video driver
if you are overclocking stop
download and run memtestx86 preferable overnight
run system file check by typing cmd in search>right click and run as admin> then
type sfc /scannow
Let us know the results





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


Loading Dump File [C:\Users\K\Desktop\111309-18236-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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Fri Nov 13 18:09:57.237 2009 (GMT-5)
System Uptime: 0 days 0:50:56.891
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004620ce5, fffff88004fd06a8, fffff88004fcff00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )

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: fffff88004620ce5, The address that the exception occurred at
Arg3: fffff88004fd06a8, Exception Record Address
Arg4: fffff88004fcff00, 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::ReferenceAllocationForPreparation+19
fffff880`04620ce5 488b02 mov rax,qword ptr [rdx]

EXCEPTION_RECORD: fffff88004fd06a8 -- (.exr 0xfffff88004fd06a8)
ExceptionAddress: fffff88004620ce5 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000019)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88004fcff00 -- (.cxr 0xfffff88004fcff00)
rax=fffff88004fd0908 rbx=0000000000000000 rcx=fffffa8005417000
rdx=bffffa80045c92b0 rsi=fffffa8005b08800 rdi=fffffa8005417000
rip=fffff88004620ce5 rsp=fffff88004fd08e0 rbp=fffffa8005b25808
r8=fffffa8005b0c501 r9=0000000000000000 r10=0000000000000000
r11=000000000000017a r12=000000000000007a r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19:
fffff880`04620ce5 488b02 mov rax,qword ptr [rdx] ds:002b:bffffa80`045c92b0=????????????????
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 fffff80002caa0e0
ffffffffffffffff

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`04620ce5 488b02 mov rax,qword ptr [rdx]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff8800461ded3 to fffff88004620ce5

STACK_TEXT:
fffff880`04fd08e0 fffff880`0461ded3 : 00000000`00000000 fffffa80`05b08800 00000000`0000007a 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffff880`04fd0910 fffff880`0463865d : 00000000`00000000 fffff8a0`03038940 fffffa80`00000000 fffffa80`05b0c520 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`04fd0ae0 fffff880`04638398 : fffff800`00b96080 fffff880`04637d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04fd0cd0 fffff880`04637e96 : 00000000`00000000 fffffa80`03e87a50 00000000`00000080 fffffa80`039f6010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04fd0d00 fffff800`02d17166 : 00000000`02ca6d1d fffffa80`051a9b60 fffffa80`03973890 fffffa80`051a9b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04fd0d40 fffff800`02a52486 : fffff800`02bece80 fffffa80`051a9b60 fffff800`02bfac40 fffff880`0104b534 : nt!PspSystemThreadStartup+0x5a
fffff880`04fd0d80 00000000`00000000 : fffff880`04fd1000 fffff880`04fcb000 fffff880`04fd0690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff88004fcff00 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

Followup: MachineOwner

Hope this helps

Ken J
---------

torrentg said:

Hi.

Update your chipset drivers from here.

Also, there's a relatively new bios that you should install. After these changes, the system should run well.

Let us know how it goes.

Thank you very much for the reply. Unfortunately, I have already done what you suggested. The chipset driver you pointed me to was the one I used last night on my clean install of Windows 7. The F6 BIOS was flashed this afternoon before the last minidump was generated. The latest minidump was the result of Crysis Warhead again crashing in the same manner as before.

For the sake of it, see if you can open your case and let a nice big room fan blow on it while you play a game.

See if any bsod happen under this condition.

Also while doing that, you can run some fan speed control and put it on max. I think Rivatuner can do this.

Also, it can't hurt - on the game disc might be a directx install folder. Run any setups you can find in relation to this. You could also search online for March 2009 DirectX patch and August 2009 DirectX patch and install.

hi and welcome. all three of the dumps was about the same. It seems that they were probably cusued by your video driver. the specific file is dxgmms1.sys.

I would update the video driver
if you are overclocking stop
download and run memtestx86 preferable overnight
run system file check by typing cmd in search>right click and run as admin> then
type sfc /scannow
Let us know the results

I greatly appreciate the help! My graphics driver was installed during the clean installation of Windows 7 last night. It is the latest from AMD/ATI for Windows 7 64-bit which I found here. I also have cleaned and re-installed it this afternoon.

I am not overclocking and my settings have not changed since I stopped using Windows XP (last night) before which Crysis Warhead ran flawlessly.

I will run memtestx86 overnight and report back.

This is the second time I have run the system scan and still no inconsistencies were found.

I am prepared for the fact that ATI's drivers are as yet immature and I will simply have to wait for a revision. Also, I'm not exactly new at system troubleshooting; feel free to fire relatively advanced procedures my way... This issue has me stumped, though.

Monotony said:

I am prepared for the fact that ATI's drivers are as yet immature and I will simply have to wait for a revision. Also, I'm not exactly new at system troubleshooting; feel free to fire relatively advanced procedures my way... This issue has me stumped, though.

No, the driver is pretty much flawless. There's a problem specific to your system. See above to my last post.

Also, it can't hurt - on the game disc might be a directx install folder. Run any setups you can find in relation to this. You could also search online for March 2009 DirectX patch and August 2009 DirectX patch and install.

This is an area in which I'm a bit fuzzy. Windows 7 comes with DX11 as my dxdiag informed me. Doesn't this cover previous versions? My card is a DX10.1 card and to my knowledge, Crysis Warhead was running in that mode. How will downloading the August 2009 9.0c patch help?

I'm downloading a fan utility and the side is off my case... I'm going to make a run with Crysis and report back.

Doesn't matter which game it is. DirectX games typically need to rely on DX9 no matter which version the game is designed for. Those patches I mentioned may go a long way to helping here.