Windows 7: New RAM, BSOD playing dota 2

feufollets · 01 Sep 2012

Hi everyone, first of all thank you for taking time to help me.

I recently bought new RAM (old one was 2x2go DDR3 1333Mhz), Now I have 2x4go DDR3

1866Mhz (XMP enabled) I have done a torture test (blend all cores loaded) with prime95

64bit for around 45 minutes with no BSOD at all. My only overclock was to increase the

intel turbo boost ratio up to 4.2Ghz. I got some BSODs playing dota 2, so I went back to

bios and put it back to default except for XMP and I still have the BSOD.

Arc · 01 Sep 2012

Welcome aboard

First, you need to update DirectX

Code:

 *******************************************************************************
  *                                                                             *
  *                        Bugcheck Analysis                                    *
  *                                                                             *
  *******************************************************************************
   
  Use !analyze -v to get detailed debugging information.
   
  BugCheck 3B, {c0000005, fffff880076307ac, fffff8800b413420, 0}
   
  Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )
   
  Followup: MachineOwner

The installed one is old enough.

Code:

 kd> lmvm dxgmms1
  start             end                 module name
  fffff880`07600000 fffff880`07646000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
      Loaded symbol image file: dxgmms1.sys
      Mapped memory image file: c:\symcache\dxgmms1.sys\4CE799C146000\dxgmms1.sys
      Image path: \SystemRoot\System32\drivers\dxgmms1.sys
      Image name: dxgmms1.sys
      Timestamp:        Sat Nov 20 15:19:53 2010 (4CE799C1)
      CheckSum:         00047A89
      ImageSize:        00046000
      File version:     6.1.7601.17514
      Product version:  6.1.7601.17514

Second, You are also getting some hardware faults.

Code:

 *******************************************************************************
  *                                                                             *
  *                        Bugcheck Analysis                                    *
  *                                                                             *
  *******************************************************************************
   
  Use !analyze -v to get detailed debugging information.
   
  BugCheck 124, {0, fffffa800980d028, be200000, 5110a}
   
  Probably caused by : hardware

To deal with it, follow: Stop 0x124 - what it means and what to try

Third, Run memtest for at least 8 passes: RAM - Test with Memtest86+

Let us know the results

feufollets · 01 Sep 2012

Hi Arc! Thank for taking time to help me

.

I did memtest in my bios and with windows memory diagnostic tool ; no errors.

I'll do memtest86 during this night, I also posted my problem of frequent bsods on the MSI forum and someone told me 0x124 is caused by too low voltage to the cpu and told me to switch SVID to APS for a little bit more cpu voltage. I'll let you know if APS works or not and the result of memtest86 probably tomorow. I got a new bsod 5 minutes ago and I included it in my new .ZIP maybe you can tell me what is it this time.

I installed winDbg to try understanding my problem (I don't have good knowledge about crash dump and debugging). So I thought I will do my part and check for myself, so here is the bugcheck I found in the dump.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8800b6c2688, 2, 1, fffff80002aa5af2}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Not sure if this is what you need but I just wanted to do my part and help

Arc · 01 Sep 2012

Your new dumps are almost essentially identical with the older ones. In the same order, too.

As your dumps still includes dxgmms1.sys. you need to upgrade it. How to download and install DirectX

And, have you followed it? Stop 0x124 - what it means and what to try

feufollets · 01 Sep 2012

Strange because I downloaded and installed new directX.

Arc · 01 Sep 2012

Have a look

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880076307ac, fffff8800b413420, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )

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


1: kd> lmvm dxgmms1
start             end                 module name
fffff880`07600000 fffff880`07646000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\4CE799C146000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Sat Nov 20 15:19:53 2010 (4CE799C1)
    CheckSum:         00047A89
    ImageSize:        00046000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514

feufollets · 01 Sep 2012

I might have an idea of what caused some problem, could it be the spread spectrum? I forgot to disable it when I put everything back to default o_O?

feufollets · 01 Sep 2012

Hey Arc I just wanted to tell you that the previous 0x124 bsod I had was when I was doing testing overclocking so my major problem with BSOD are related to dxgmms1.sys. I have reinstalled all directX but I still got an BSOD.

Arc · 01 Sep 2012

Bugcheck 0x124 is present in not only the first dump, but also in the second one. Overclocking is a reason behind 0x124, but there are many other reasons for it. That is why I suggest you to follow all the steps mentioned in Stop 0x124 - what it means and what to try

If the hardware is not made error free, crashes cannot be stopped. So do it first.

feufollets · 02 Sep 2012

Everything on my computer is updated, there is no overclock (xmp enabled), This night I ran memtest86 with no errors, I tested with intel burn test with maximum setting ; everything looks stable. But today I still got an BSOD with the error code 0x0000003B. I removed ati Driver and put it back with the latest version and updated directX again with no results.

Windows 7: New RAM, BSOD playing dota 2

New RAM, BSOD playing dota 2 problems?