Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD dxgmms1.sys

01 Feb 2012   #1
altyfc

Windows 7 Professional 32bit
 
 
BSOD dxgmms1.sys

Is Windows 7 . . . - x86 (32-bit) or x64 ? 32-bit - the original installed OS on the system? No - an OEM or full retail version? Full Retail - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? 4 years - What is the age of OS installation (have you re-installed the OS?) 1 year

I have updated the video drivers with the latest version as suggested elsewhere but still have the issue.

The requested dump files are attached.



My System SpecsSystem Spec
.
01 Feb 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [K:\BSODDmpFiles\altyfc\Windows_NT6_BSOD_jcgriff2\020112-18096-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d514d0 Debug session time: Wed Feb 1 02:35:47.180 2012 (GMT-7) System Uptime: 0 days 0:31:00.053 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 95908501, 9ac2bba0, 9ac2b780} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 ) Followup: MachineOwner --------- 0: 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: c0000005, The exception code that was not handled Arg2: 95908501, The address that the exception occurred at Arg3: 9ac2bba0, Exception Record Address Arg4: 9ac2b780, 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::ProcessDeferredCommand+443 95908501 8b00 mov eax,dword ptr [eax] EXCEPTION_RECORD: 9ac2bba0 -- (.exr 0xffffffff9ac2bba0) ExceptionAddress: 95908501 (dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x00000443) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000000 Attempt to read from address 00000000 CONTEXT: 9ac2b780 -- (.cxr 0xffffffff9ac2b780) eax=00000000 ebx=00000000 ecx=ffffffd8 edx=b1911d88 esi=b1954980 edi=86807ee0 eip=95908501 esp=9ac2bc68 ebp=9ac2bcc4 iopl=0 nv up ei pl nz na pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443: 95908501 8b00 mov eax,dword ptr [eax] ds:0023:00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE 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: 00000000 EXCEPTION_PARAMETER2: 00000000 READ_ADDRESS: GetPointerFromAddress: unable to read from 82d71848 Unable to read MiSystemVaType memory at 82d50e20 00000000 FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 95908501 8b00 mov eax,dword ptr [eax] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 95908e66 to 95908501 STACK_TEXT: 9ac2bcc4 95908e66 01c2bce0 00000000 9ac2bcf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443 9ac2bcf0 9590a4c8 00000000 9ac2bd18 9591e1df dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40 9ac2bcfc 9591e1df 8748e0c0 866c1b70 866c1b70 dxgmms1!VidMmiProcessTerminationCommand+0x10 9ac2bd18 9591f18f 867babb0 866fe008 9ac2bd3c dxgmms1!VidSchiSubmitDeviceCommand+0x33 9ac2bd28 9591f3de 866c1b70 82c3f509 88fda788 dxgmms1!VidSchiSubmitQueueCommand+0xaf 9ac2bd3c 9591f485 88fda788 00000000 8911ed48 dxgmms1!VidSchiRun_PriorityTable+0x24 9ac2bd50 82e10fda 88fda788 b7a9c84f 00000000 dxgmms1!VidSchiWorkerThread+0x7f 9ac2bd90 82cb91f9 9591f406 88fda788 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d4a24c1 STACK_COMMAND: .cxr 0xffffffff9ac2b780 ; kb FAILURE_BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 Followup: MachineOwner ---------
  2. Loading Dump File [K:\BSODDmpFiles\altyfc\Windows_NT6_BSOD_jcgriff2\013012-20716-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x82c52000 PsLoadedModuleList = 0x82d9b4d0 Debug session time: Mon Jan 30 15:54:54.843 2012 (GMT-7) System Uptime: 0 days 2:37:09.715 Loading Kernel Symbols ............................................................... ................................................................ ............................................. Loading User Symbols Loading unloaded module list .......... 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* QUOTA_UNDERFLOW (21) This bugcheck occurs if a kernel component mishandles quota charges and returns more quota than was previously charged to a particular quota block. Arguments: Arg1: 866bdd40, The process (if any) that was initially charged. Arg2: 00000001, The quota type in question (paged pool, nonpaged pool, etc.) Arg3: ffc83088, The initial charge amount to return. Arg4: fe7974c8, The remaining (unreturned) charge. Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x21 CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 82cf2602 to 82cd67ab STACK_TEXT: bb9e3bd8 82cf2602 82d87a00 866bdd40 00000001 nt!PspReturnQuota+0x11f bb9e3bf0 82e98f44 866bdd40 ffc83088 86722030 nt!PsReturnProcessPagedPoolQuota+0x22 bb9e3c10 82d10452 866bdd40 00000001 866bdd40 nt!MiRemoveVadCharges+0x43 bb9e3c40 82ebb7d0 96a27935 86722030 40010004 nt!MmCleanProcessAddressSpace+0xf3 bb9e3cb4 82ecf111 00000000 86f8f3b0 00000001 nt!PspExitThread+0x685 bb9e3ccc 82d038a0 86f8f3b0 bb9e3cf8 bb9e3d04 nt!PsExitSpecialApc+0x22 bb9e3d1c 82c902d4 00000001 00000000 bb9e3d34 nt!KiDeliverApc+0x28b bb9e3d1c 76f47094 00000001 00000000 bb9e3d34 nt!KiServiceExit+0x64 WARNING: Frame IP not in any known module. Following frames may be wrong. 0d7ee9ec 00000000 00000000 00000000 00000000 0x76f47094 STACK_COMMAND: kb FOLLOWUP_IP: nt!PspReturnQuota+11f 82cd67ab cc int 3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!PspReturnQuota+11f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4 FAILURE_BUCKET_ID: 0x21_nt!PspReturnQuota+11f BUCKET_ID: 0x21_nt!PspReturnQuota+11f Followup: MachineOwner ---------
  1. Caused by your DirectX or graphics card/graphics card driver. Other possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
  2. Possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
  • If you are overclocking any hardware, please stop.


  • Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts

    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts


  • Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.


  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.


  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Also, please follow the very informative steps that Dave76 has laid out in the next post. As always, thanks Dave for the additional super info.
My System SpecsSystem Spec
01 Feb 2012   #3
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

EDIT: Hi writhziden, looks like you beat me to it.

Welcome to Seven Forums altyfc.


You have had four crashes since 10 Jan '12
The last one is STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
This bug check is a very common bug check.
The driver indicated is dxgmms1.sys - DirectX Graphics MMS, this is a Windows system driver and not the cause but the result of the crash.
Code:
*******************************************************************************
*                                                                             *
*                        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: c0000005, The exception code that was not handled
Arg2: 95908501, The address that the exception occurred at
Arg3: 9ac2bba0, Exception Record Address
Arg4: 9ac2b780, 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::ProcessDeferredCommand+443

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
Followup: MachineOwner
---------
  • Make sure you have enough disk space.
  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
  • Try changing video adapters.
  • Check with your hardware vendor for any BIOS updates.
  • Disable BIOS memory options such as caching or shadowing.


Old drivers that need updated.

Code:
bcm4sbxp.sys Tue Nov 21 20:25:43 2006 - Broadcom Corporation NDIS 5.1 ethernet driver
Go to your Dell Support site and update all drivers including the Broadcom 440x 10/100 Integrated Controller.

Code:
DLABMFSM.SYS Fri Oct 27 07:19:29 2006
DLABOIOM.SYS Fri Oct 27 07:19:24 2006
DLACDBHM.SYS Fri Feb 09 12:05:12 2007
DLADResM.SYS Fri Oct 27 07:20:51 2006 
DLAIFS_M.SYS Fri Oct 27 07:18:31 2006 
DLAOPIOM.SYS Fri Oct 27 07:20:03 2006 
DLAPoolM.SYS Fri Oct 27 07:18:34 2006 
DLARTL_M.SYS Fri Feb 09 12:04:41 2007 
DDLAUDF_M.SYS Fri Oct 27 07:18:49 2006 
DLAUDFAM.SYS Fri Oct 27 07:19:10 2006 
DRVMCDB.SYS  Sat Jul 22 02:20:31 2006 
DRVNDDM.SYS  Sat Feb 10 04:33:42 2007
These are Roxio Drag-to-Disc drivers, update drivers or un-install Roxio.

Code:
netw5v32.sys Fri Mar 27 00:10:37 2009 - Intel WiFi Link 5100 AGN wireless driver
Go to your Dell Support site and update the WiFi Link driver.

Code:
VSTAZL3.SYS  Thu Oct 16 08:30:03 2008 
VSTCNXT3.SYS Thu Oct 16 08:29:13 2008 
VSTDPV3.SYS  Thu Oct 16 08:32:04 2008
Go to your Dell Support site and update the Conexant SoftK56 Modem drivers.

Noticed some issues with this driver - rapportiaso.sys - Trusteer Ltd. Rapport Security software.
Can you update this driver/software?

System Event Logs.

There are a lot of these.
Code:
Event[923]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-01-31T09:57:25.996
  Event ID: 7034
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Pauls-PC
  Description: 
The NVIDIA Update Service Daemon service terminated unexpectedly.  It has done this 1 time(s).
As mentioned by writhziden, update your graphics card driver.


Code:
Event[2187]:
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2012-01-29T12:45:58.000
  Event ID: 10005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Pauls-PC
  Description: 
DCOM got error "1053" attempting to start the service RoxMediaDB9 with arguments "" in order to run the server:
{5EFBB572-1CBD-47DA-8BBA-5BAB9CADD108}
Problem with Roxio, update or uninstall.

Code:
Event[2698]:
  Log Name: System
  Source: Application Popup
  Date: 2012-01-27T15:45:49.000
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Pauls-PC
  Description: 
Application popup: Windows - Application Error : The instruction at 0x5ac00a5a referenced memory at 0x02ef9833. The memory could not be read.

Click on OK to terminate the program
Inconclusive but points to driver or RAM issue.

Application Event Logs.

Code:
Event[10]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-02-01T09:38:58.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Pauls-PC
  Description: 
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: daemonu.exe
P2: 1.5.20.0
P3: 4e99198a
P4: daemonu.exe
P5: 1.5.20.0
P6: 4e99198a
P7: 0005f315
P8: c000000d
P9: 00000000
P10: 

Attached files:
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER5E64.tmp.appcompat.txt
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER5F3F.tmp.WERInternalMetadata.xml
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER5F50.tmp.hdmp
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER60B8.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_daemonu.exe_e2a490ee3cddc7461fcdae56c822ff2570f9ba9d_cab_114a619f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8f7fcb27-4cb8-11e1-81cc-001c2395d523
Report Status: 4
daemonu.exe - this is from the NVIDIA Settings Update Manager service.
My System SpecsSystem Spec
.

Reply

 BSOD dxgmms1.sys




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD dxgmms1.sys
Hi I get BSOD a lot. Usually I solve it by restoring to last state in safe mode. But this time I made the minidump file and wondering if you can help. I've tried updating my drivers(specially display adapters) at device manager but windows says they are up to date. Windows_NT_BSOD +report+ dmp...
BSOD Help and Support
BSOD Dxgmms1.sys
Hi! Last night when i played dota2 i got Blue screen error. i checked Ram,Hdd,Gpu without problems! Here is mine Things! Please if u know help to me! Ty
BSOD Help and Support
Dxgmms1.sys BSOD... What should I do?
Hi all... Thought I'd throw this one out there as I don't know what's going on. Getting this BSOD when playing PC games sometimes. Anyone know what I can do about it? Thanks.
BSOD Help and Support
dxgmms1.sys BSOD
Hi i have recently built a new gaming pc but ....when i exit battlefield bad company 2 i get blue screen then restart,any idea's ? Thanks
BSOD Help and Support
Bsod--dxgmms1.sys
I have FRESHLY installed window's 7 32-bit on my computer because of a recent problem with a BSOD. After a fresh install, I'm getting blue screen's which I can't really pin down to any certain activity. It's all random and has no pattern. Sometime's in Google Chrome, some times browsing files on my...
BSOD Help and Support
dxgmms1.sys BSOD
Hi! I recently upgraded to Windows 7 x64 from Windows XP x64. I've had the same BSOD twice now, roughly a week apart. Both times it happened while playing World of Warcraft. My computer spec: Motherboard: ASUS M2N4-SLI CPU: AMD Athlon 64 X2 6000+
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 19:31.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App