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


18 Dec 2011   #1

Windows 7 Ultimate 32bit
 
 
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 file are attached.


My system specs :
Dell Vostro 1510 (about 3 years old)
Windows 7 Ultimate 32-bit (installed about 1.5 years ago)
Mobile Intel(R) 965 Express Chipset Family

Sorry for poor English and Thanks.

My System SpecsSystem Spec
.

18 Dec 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by slugeng View Post
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 file are attached.


My system specs :
Dell Vostro 1510 (about 3 years old)
Windows 7 Ultimate 32-bit (installed about 1.5 years ago)
Mobile Intel(R) 965 Express Chipset Family

Sorry for poor English and Thanks.

You have nearly 20 old drivers dating back to 2002. These have to be updated. When those are updated we can start to look at the underlying problem.

Old drivers

Code:
wanatw4.sys    7/16/2002 10:23:14 AM            0x93bf8000    0x93bfd020    0x00005020    0x3d343a62                    
ElbyDelay.sys    2/12/2004 12:11:28 PM            0x93b4d000    0x93b4df80    0x00000f80    0x402bb3c0                    
ElbyCDIO.sys    7/21/2004 4:45:25 PM            0x97dda000    0x97ddc680    0x00002680    0x40fee3f5                    
VClone.sys    9/2/2004 8:45:13 AM            0x8be9a000    0x8be9f880    0x00005880    0x413723e9                    
Afc.sys    2/23/2005 1:58:55 AM            0x93b45000    0x93b4d000    0x00008000    0x421c29af                    
o2media.sys    11/14/2005 12:28:33 AM            0x8bed6000    0x8bede580    0x00008580    0x43782081                    
Rt86win7.sys    2/26/2009 4:04:22 AM            0x93a9c000    0x93ac1000    0x00025000    0x49a65b16                    
sprj.sys    3/23/2009 1:38:33 AM            0x84ab6000    0x84bb7000    0x00101000    0x49c72e69                    
spldr.sys    5/11/2009 11:13:47 AM            0x8c448000    0x8c450000    0x00008000    0x4a084ebb                    
amdxata.sys    5/19/2009 12:57:35 PM            0x8bedf000    0x8bee8000    0x00009000    0x4a12f30f                    
bcmwl6.sys    7/7/2009 7:44:47 PM            0x9382b000    0x93a92000    0x00267000    0x4a53ebff
How To Find Drivers:
Quote:
- 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 Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
My System SpecsSystem Spec
26 Feb 2012   #3

Windows 7 Ultimate 32bit
 
 

I reinstalled my windows 2 week ago and again I get BSOD.
Here's the information :
My System SpecsSystem Spec
.


27 Feb 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
Mass Storage Controller	PCI\VEN_1217&DEV_7130&SUBSYS_02731028&REV_01\4&280AAD99&0&2BF0	The drivers for this device are not installed.


Antivirus Software:
Code:
avp.exe	c:\program files\kaspersky lab\kaspersky internet security 2012\avp.exe	648	8	200	1380	2/26/2012 12:55 AM	12.0.0.374	197.55 KB (202,296 bytes)	4/25/2011 12:15 AM
avp.exe	c:\program files\kaspersky lab\kaspersky internet security 2012\avp.exe	2924	8	200	1380	2/26/2012 12:56 AM	12.0.0.374	197.55 KB (202,296 bytes)	4/25/2011 12:15 AM


Possible outdated drivers:
Code:
ElbyDelay	911d6000	911d6f80	Thu Feb 12 10:11:28 2004 (402bb3c0)	0000be7f		ElbyDelay.sys
ElbyCDIO	971d6000	971d8680	Wed Jul 21 15:45:25 2004 (40fee3f5)	0000329f		ElbyCDIO.sys
VClone	835d9000	835de880	Thu Sep 02 07:45:13 2004 (413723e9)	00008356		VClone.sys
Rt86win7	9112d000	91152000	Thu Feb 26 02:04:22 2009 (49a65b16)	0002bdef		Rt86win7.sys
bcmwl6	9100b000	91123000	Thu Mar 26 18:58:48 2009 (49cc24c8)	0011a306		bcmwl6.sys
amdxata	835f2000	835fb000	Tue May 19 11:57:35 2009 (4a12f30f)	0000636d		amdxata.sys
ElbyDelay.sys
ElbyCDIO.sys
VClone.sys
Rt86win7.sys
bcmwl6.sys
amdxata.sys

Please remove the CD/DVD Clone software from your system. It may cause conflicts due to the age of the drivers. Update the rest of the drivers listed above and install all Windows updates.



Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\slugeng\Seven Forums\022612-28017-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 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82807000 PsLoadedModuleList = 0x8294f810 Debug session time: Sat Feb 25 14:24:16.479 2012 (UTC - 7:00) System Uptime: 0 days 23:39:31.305 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ............................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 9141b501, 92057ba0, 92057780} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 ) Followup: MachineOwner --------- 1: 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: 9141b501, The address that the exception occurred at Arg3: 92057ba0, Exception Record Address Arg4: 92057780, 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 9141b501 8b00 mov eax,dword ptr [eax] EXCEPTION_RECORD: 92057ba0 -- (.exr 0xffffffff92057ba0) ExceptionAddress: 9141b501 (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: 92057780 -- (.cxr 0xffffffff92057780) eax=00000000 ebx=00000000 ecx=ffffffd8 edx=ae1937c8 esi=8ca82a00 edi=87e18438 eip=9141b501 esp=92057c68 ebp=92057cc4 iopl=0 nv up ei pl nz na po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443: 9141b501 8b00 mov eax,dword ptr [eax] ds:0023:00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE 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: 00000000 EXCEPTION_PARAMETER2: 00000000 READ_ADDRESS: GetPointerFromAddress: unable to read from 8296f718 Unable to read MiSystemVaType memory at 8294f160 00000000 FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 9141b501 8b00 mov eax,dword ptr [eax] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 9141be66 to 9141b501 STACK_TEXT: 92057cc4 9141be66 01057ce0 00000000 92057cf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443 92057cf0 9141d4c8 00000000 92057d18 914312cd dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40 92057cfc 914312cd 8797e850 87a48428 87a48428 dxgmms1!VidMmiProcessTerminationCommand+0x10 92057d18 9143227d 87a48760 87a48528 92057d3c dxgmms1!VidSchiSubmitDeviceCommand+0x33 92057d28 914324cc 87a48428 828433f1 87523008 dxgmms1!VidSchiSubmitQueueCommand+0xaf 92057d3c 91432573 87523008 00000000 875f8558 dxgmms1!VidSchiRun_PriorityTable+0x24 92057d50 82a1566d 87523008 b950c6dc 00000000 dxgmms1!VidSchiWorkerThread+0x7f 92057d90 828c70d9 914324f4 87523008 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: 4a5bc265 STACK_COMMAND: .cxr 0xffffffff92057780 ; kb FAILURE_BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\slugeng\Seven Forums\022512-21028-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 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x8280b000 PsLoadedModuleList = 0x82953810 Debug session time: Fri Feb 24 14:35:22.838 2012 (UTC - 7:00) System Uptime: 1 days 1:03:47.664 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ...................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 9264a6bc, b28f3b00, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: 9264a6bc, The address that the exception occurred at Arg3: b28f3b00, Trap Frame Arg4: 00000000 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::CloseOneAllocation+116 9264a6bc 894804 mov dword ptr [eax+4],ecx TRAP_FRAME: b28f3b00 -- (.trap 0xffffffffb28f3b00) ErrCode = 00000002 eax=00000000 ebx=87a61000 ecx=b5061b18 edx=00000001 esi=87e42830 edi=b9e322b8 eip=9264a6bc esp=b28f3b74 ebp=b28f3ba8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x116: 9264a6bc 894804 mov dword ptr [eax+4],ecx ds:0023:00000004=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 9264af53 to 9264a6bc STACK_TEXT: b28f3ba8 9264af53 00000000 00000000 c62db5b0 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x116 b28f3bc8 9262e32b bb90cea0 00000000 b28f3c54 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x37 b28f3bd8 9253f4aa 87a61000 bb90cea0 00000000 dxgmms1!VidMmCloseAllocation+0x13 b28f3c54 9253d481 00000000 00000000 997e4168 dxgkrnl!DXGDEVICE::DestroyAllocations+0x19a b28f3c7c 92542ee8 00000001 00000000 00000000 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x89 b28f3d28 8284e42a 002fb3c8 002fb36c 779464f4 dxgkrnl!DxgkCreateAllocation+0x28c b28f3d28 779464f4 002fb3c8 002fb36c 779464f4 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 002fb36c 00000000 00000000 00000000 00000000 0x779464f4 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116 9264a6bc 894804 mov dword ptr [eax+4],ecx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265 FAILURE_BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116 BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116 Followup: MachineOwner ---------
  1. Caused by DirectX/graphics card/graphics card drivers. Other possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
  2. Caused by DirectX/graphics card/graphics card drivers. Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...

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



Update to Service Pack 1 (SP1)
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
My System SpecsSystem Spec
01 Mar 2012   #5

Windows 7 Ultimate 32bit
 
 

Thanks for your help.
except updating to SP1(which is impossible considering my bandwidth) I've done all you said. I didn't have a BSOD for 3 days and it seems it got better.

but now I have a new BSOD
My System SpecsSystem Spec
01 Mar 2012   #6

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\slugeng\Seven Forums\030212-20857-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82a1d000 PsLoadedModuleList = 0x82b65810
Debug session time: Thu Mar  1 15:53:50.476 2012 (UTC - 7:00)
System Uptime: 0 days 1:14:33.177
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 00000000, Object type of the object whose reference count is being lowered
Arg2: 85718e20, Object whose reference count is being lowered
Arg3: 00000002, Reserved
Arg4: ffffffff, Reserved
	The reference count of an object is illegal for the current state of the object.
	Each time a driver uses a pointer to an object the driver calls a kernel routine
	to increment the reference count of the object. When the driver is done with the
	pointer the driver calls another kernel routine to decrement the reference count.
	Drivers must match calls to the increment and decrement routines. This bugcheck
	can occur because an object's reference count goes to zero while there are still
	open handles to the object, in which case the fourth parameter indicates the number
	of opened handles. It may also occur when the objectís reference count drops below zero
	whether or not there are open handles to the object, and in that case the fourth parameter
	contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x18

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82a86062 to 82af9e34

STACK_TEXT:  
9b737930 82a86062 00000018 00000000 85718e20 nt!KeBugCheckEx+0x1e
9b737954 82a86010 85718e20 82c4fc04 b0268893 nt!ObfDereferenceObjectWithTag+0x4b
9b73795c 82c4fc04 b0268893 00000040 00000040 nt!ObfDereferenceObject+0xd
9b737bc8 82c4f8f2 00000040 9b737cf4 00000001 nt!ObpWaitForMultipleObjects+0x2e1
9b737d18 82a6048a 00000040 00f885c0 00000001 nt!NtWaitForMultipleObjects+0xcd
9b737d18 76ef6194 00000040 00f885c0 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
033afef8 00000000 00000000 00000000 00000000 0x76ef6194


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObfDereferenceObjectWithTag+4b
82a86062 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ObfDereferenceObjectWithTag+4b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea76ed3

FAILURE_BUCKET_ID:  0x18_OVER_DEREFERENCE_nt!ObfDereferenceObjectWithTag+4b

BUCKET_ID:  0x18_OVER_DEREFERENCE_nt!ObfDereferenceObjectWithTag+4b

Followup: MachineOwner
---------
Possible causes are Memory problems... Drivers...
Thanks to Dave76 for help understanding possible causes.


Do the following the check the two possible causes:
  • If you are overclocking any hardware, please stop.


  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.


  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
My System SpecsSystem Spec
02 Mar 2012   #7

Windows 7 Ultimate 32bit
 
 

Before applying the advices I got 2 other crashes, the usual ones.
My System SpecsSystem Spec
Reply

 BSOD dxgmms1.sys




Thread Tools



Similar help and support threads for2: BSOD dxgmms1.sys
Thread Forum
BSOD dxgmms1.sys BSOD Help and Support
Dxgmms1.sys BSOD... What should I do? BSOD Help and Support
BSOD dxgmms1.sys BSOD Help and Support
BSOD - dxgmms1.sys BSOD Help and Support
BSOD in dxgmms1.sys BSOD Help and Support
dxgmms1.sys BSOD BSOD Help and Support
Solved Bsod--dxgmms1.sys 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 09:05 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33