dxgmms1.sys crash – Blue Screen Of Death

Desired Blue Screen Of Death



There have been a number of issues reported experiencing Blue Screen Of Death (BSOD) crash on Vista and Windows 7 related to dxgmms1.sys and nvlddmkm.sys files. There are few solutions available and all of them are not 100% guarantee to fix your problem :-\

Please specify solution that worked for you in the comments below.

Solution 1

Try installing Windows hot-fix http://support.microsoft.com/kb/974431

Solution 2

nvidia drivers may cause BSOD, try running the straight up vista/windows 7 drivers

Solution 3

There might be a bad memory or other piece of hardware. Run the built-in Memory Diagnostic or other diagnostic tools to find any potential problems.

Solution 4

  1. Disable C1E in BIOS
  2. Disable any boost in BIOS (standard only)
  3. Run driver sweeper in safe mode to uninstall display drivers
  4. Reboot
  5. Install newest video drivers and update directx

Please let me know if you are aware of any other solutions for fixing this problem

P.S. There is a relevant post on the forum: BSOD – dxgmms1.sys

And here is an epic Microsoft fail video demonstrating Blue Screen of Death ;)

29 Comments Posted in Windows
Tagged ,

29 Comments

  1. In my case there was a hardware issue, after replacing my video card the problem have disappeared.

  2. I replaced also the videocard ( ATI 4850 into 5750), problems are gone

  3. Hi ! i need some help with my computer !! bough it for 1 week ago and getting bluescreen everytime i play a game , can play for like 1-10 min and then i get bsod .. i have updated all my drivers and still get it >.< // sorry for my bad english

  4. Yes i have the same problem what have Djurarn pls help

  5. i’m getting the problem in vmware on a mac, so not necessarily a hardware problem (!).

    Here’s the bugcheck analysis in my case:


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    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.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8287a882, The address that the exception occurred at
    Arg3: 8a8fd874, Exception Record Address
    Arg4: 8a8fd450, 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:
    nt!memcpy+c2
    8287a882 8a06 mov al,byte ptr [esi]

    EXCEPTION_RECORD: 8a8fd874 -- (.exr 0xffffffff8a8fd874)
    ExceptionAddress: 8287a882 (nt!memcpy+0x000000c2)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 00000000
    Attempt to read from address 00000000

    CONTEXT: 8a8fd450 -- (.cxr 0xffffffff8a8fd450)
    eax=00000003 ebx=b0606053 ecx=0007ffff edx=00000003 esi=00000000 edi=b0606053
    eip=8287a882 esp=8a8fd93c ebp=8a8fd944 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!memcpy+0xc2:
    8287a882 8a06 mov al,byte ptr [esi] ds:0023:00000000=??
    Resetting default scope

    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: 00000000

    FOLLOWUP_IP:
    dxgmms1!VIDMM_DMA_POOL::WriteDmaBufferToMinidump+261
    912da8c1 8b45fc mov eax,dword ptr [ebp-4]

    BUGCHECK_STR: 0x7E

    LAST_CONTROL_TRANSFER: from 912da8c1 to 8287a882

    STACK_TEXT:
    8a8fd944 912da8c1 b0606053 00000000 00080000 nt!memcpy+0xc2
    8a8fd9e0 912db721 868c7138 b060600b 00000048 dxgmms1!VIDMM_DMA_POOL::WriteDmaBufferToMinidump+0x261
    8a8fda9c 912cfbea 00000000 b060600b 00156ff1 dxgmms1!VIDMM_DMA_POOL::WriteDmaHistoryToMinidump+0x1a5
    8a8fdad4 912bb577 00000000 00003344 00000000 dxgmms1!VIDMM_GLOBAL::LogInformationToMinidump+0xae
    8a8fdaf4 91214c0e 85f6e000 00000000 00003344 dxgmms1!VidMmLogInformationToMinidump+0x1f
    8a8fdb18 91290553 8578d0b8 85f6e000 00000000 dxgkrnl!VIDMM_EXPORT::VidMmLogInformationToMinidump+0x26
    8a8fdb9c 91290941 00000000 00000001 853a2510 dxgkrnl!TdrCollectDbgInfoStage1+0x676
    8a8fdbbc 912c092c 00000000 00000102 848d1008 dxgkrnl!TdrIsRecoveryRequired+0xfe
    8a8fdc34 912eaa32 fffffcfb 0007dedc 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    8a8fdc5c 912eb153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
    8a8fdc98 912c78f0 8a8fdc90 85e00b10 85a1b5e8 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
    8a8fdd28 912ec4b7 848d1008 828783f1 848d1008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
    8a8fdd3c 912ec573 848d1008 00000000 85b13120 dxgmms1!VidSchiRun_PriorityTable+0xf
    8a8fdd50 82a4a6bb 848d1008 a71134e7 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8a8fdd90 828fc0f9 912ec4f4 848d1008 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: dxgmms1!VIDMM_DMA_POOL::WriteDmaBufferToMinidump+261

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME: dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265

    STACK_COMMAND: .cxr 0xffffffff8a8fd450 ; kb

    FAILURE_BUCKET_ID: 0x7E_dxgmms1!VIDMM_DMA_POOL::WriteDmaBufferToMinidump+261

    BUCKET_ID: 0x7E_dxgmms1!VIDMM_DMA_POOL::WriteDmaBufferToMinidump+261

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

  6. Peter, did you find a solution to your problem? I have the same issue with Windows 7 64-bit on my Macbook Pro 13 (mid 2010) via Bootcamp.

  7. nope no solution yet, but does not seem to be very common. i’m now diligent about suspending the vm before sleeping the mac, because i suspect that; also since my posting fusion 3.1 came out. but on the whole – nope not sure what’s happening, but it hasn’t been troubling me for the past several weeks.

  8. Same no solution. No VM but bootcamp. Tried disabling GPU acceleration and ZoneAlarm’s IPv6 networking but doesn’t stop the BSODs.

  9. update BIOS to the latest, then problem gone =)

  10. how do i update the BIOS? any good site with clear instructions?

  11. macs don’t have bios

  12. WTF???

    Jimmy
    September 2, 2010 at 2:02 am

    how do i update the BIOS? any good site with clear instructions?

    reader#
    September 16, 2010 at 12:45 pm

    macs don’t have bios

  13. Hi guys,
    I also had this error yesterday. But my case is little different……I have been experiencing numerous BSODs nowadays and windows memory diagonostic shows that “hardware problem has been detected” only in the extended test…..I will be solving this problem of ram in a few days when I will leave my pc in the hands of people at the computer shop, but what i wanted to ask is that can dxgmms1.sys also be caused by faulty RAM??

  14. I get this same problem everyday, but only once a day. I don’t have a solution but I do have a work around.

    After I first boot my pc; I purposely will run a 3D-intense program. Any game usually works but the more intense the faster I get my pc to crash.

    Once I get the BSOD I let my pc reboot but before it passes my BIOS password I power it down manually. Next I wait a few seconds before starting it up; past the bios password and windows warns me of the previous crash. Then I select the option to “start windows normally”. After I get to windows I get a log of the crash(1033) which I close.

    Finally after all that my machine won’t crash on games or other 3D applications. Like I said this is just a work around. I could use my computer all day thereafter but I power it down at bedtime. If I do leave it running then about 36-48 hours after the first BSOD I will get another one. Rinse & repeat.

  15. @Me

    Mine is EXACTLY the same. Although when my computer crashes, I let mine just reboot normally, and without having to power down manually.;

    But everything else is exactly the same, my computer will crash once a day, and only once. (Rare occasions sometimes it crashses more).

  16. Dan and Me – Mine is EXACTLY the same. I’m on a Sony 64-bit Win 7 laptop, and get BOSD crashes once a day, usually within 5 or 10 minutes of booting up. After I reboot (Dan’s way – I let it reboot normally) I’ll be fine for the rest of the day.

    The BOSD messages indicates all kinds of different things depending on the day. Today’s was dxgs1mm.sys but sometimes it’s a page fault, and sometimes it’s an unknown error, and sometimes it’s a dll file.

    If you get this figured out, I’d love to know.

    Kate

  17. hi,
    I have windows7 (86) and I´m experiencing the same problem like the rest of you, it´s just that my comp is crashing differently every day. Sometimes this happens few times and sometimes it doesn´t. I´ve also tryed to format the whole windows system and before it usualy worked, but unfortunatly that didn´t happen this time. Somebody wrote that he updated BIOS and that it helped him, so I would like to know if anybody knows, hot to update the BIOS, because this BSOD really pisses me off. And does anybody know, what to do to find out if there is something else wrong with my comp?

  18. I’m on Windows 7 (64) and I’ve experienced random crashes since the Win 7 Beta. Sometimes they are quite regular but sometimes they come without warning. I think I should look over my BIOS to see if that can fix my problem however I’m sceptical.

    Today I got the dxgsmm1 thing and that’s what lead me to this site but my problem is more like the one Kate has. Different messages all the time although some are more likely than others.

  19. Solution 6: insert foot into computer and kick to the road.

  20. I had no issues with this “dxgmms.sys” crash until yesterday (2011 10 26). I applied some Windows updates and within two hours I had a BSOD on my Windows 7 64-bit system running as a virtual machine on a VM Ware ESX server. The ESX server is basically a mainframe and we can run about 64 virtual machines on it.

    The dump took AGES….

    This particular VM has been utterly stable for about a year. I run MS SQL Server on it for testing an application our company writes.

  21. I had a crashes too, but i found a solution.
    Check your GPU and look for directX version. For example for my GPU 9600GT is directX 10 dedicated and i had directX 11 installed, and this was the problem.

  22. I installed a PATA ebay version but the disk is not appearing on my system. I got a replacement opti-bay but same thing happens. If I swap back the CD drive that works fine.Am I missing something?

  23. Zborek, how do I do this? Can you give me instructions please?

  24. I’m finally free from my random Bluescreens!

    After updating the BIOS on my motherboard the random BSODs have completely disappeared. I should’ve known my BIOS was outdated but because flashing it is kind of risky I’ve never tried it until I read a sufficient amount of articles about my motherboard saying it might need updating.

    My Computer has run perfectly for months since I flashed it to the newest version. Hopefully this will be the cure for your problems as well.

Leave a Reply

Using Gravatars in the comments - get your own and be recognized!

XHTML: These are some of the tags you can use: <a href=""> <b> <blockquote> <code> <em> <i> <strike> <strong>