BSOD dxgmms1 When using 8 GB ram Solid when running 4

shaxs · 16 Nov 2009

Hi All,

I just built a brand new computer when a fresh install of Windows 7 Home Ultimate 64 bit. This computer has never had any other OS on it.

I am having an issue when playing Dragon Age Origins that the computer with BSOD when I have 8 gb of ram in the computer. With only 4 gb in, the computer is rock solid.

I have tested all the ram in Memtest86 overnight with no issues. I have tried different sets of the 4 gb and they all work fine. The problem is when I try to use 8 gb.

My computer has the following:

AMD Phenom II X4 965
8 GB OCZ DDR3-1600 Black Edition
Gigabyte motherboard
XFX Radeon 5870
1000W Corsair PSU

I think the are the most important components. I have installed all Windows Updates, have the latest mobo bios, and the latest video drivers.

Here is the event log from a crash:

----------------------------------------------------------
Fault bucket X64_0xD1_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+9b, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\111109-31886-01.dmp
C:\Users\jason-win7\AppData\Local\Temp\WER-55567-0.sysdata.xml
C:\Users\jason-win7\AppData\Local\Temp\WER9F7D.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\jason-win7\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0c38c5a3

Analysis symbol: X64_0xD1_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+9b
Rechecking for solution: 0
Report Id: 111109-31886-01
Report Status: 0
----------------------------------------------------------

Here is the .WER file that the event log references in C:\Users\jason-win7\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0c38c5a3:

----------------------------------------------------------

Version=1
EventType=BlueScreen
EventTime=129024579011717023
ReportType=4
Consent=1
UploadTime=129024725622324900
ReportIdentifier=0262d554-cf1f-11de-b20c-00241dc2d592
IntegratorReportIdentifier=111109-31886-01
Response.type=4
Response.AnalysisBucket=X64_0xD1_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+9b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly. Windows will notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=d1
Sec[1].Key=BCP1
Sec[1].Value=FFFFF8800913CC88
Sec[2].Key=BCP2
Sec[2].Value=000000000000000B
Sec[3].Key=BCP3
Sec[3].Value=0000000000000000
Sec[4].Key=BCP4
Sec[4].Value=FFFFF88005DAB0EB
Sec[5].Key=OS Version
Sec[5].Value=6_1_7600
Sec[6].Key=Service Pack
Sec[6].Value=0_0
Sec[7].Key=Product
Sec[7].Value=768_1
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=CA
State[1].Value=1
State[2].Key=BLOB
State[2].Value=CHKSUM=0A161440B38C3DB750EC07F75B8FBB6B;BID=OCATAG;ID=14e49d0d-1f59-4b1a-8b1e-526cd578a2b2;SUB=11//11//2009 8:09:27 PM
File[0].CabName=111109-31886-01.dmp
File[0].Path=111109-31886-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\111109-31886-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-55567-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\jason-win7\AppData\Local\Temp\WER-55567-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER9F7D.tmp.WERInternalMetadata.xml
File[2].Flags=589827
File[2].Type=5
File[2].Original.Path=C:\Users\jason-win7\AppData\Local\Temp\WER9F7D.tmp.WERInternalMetadata.xml
File[3].CabName=Report.cab
File[3].Path=Report.cab
File[3].Flags=196608
File[3].Type=7
File[3].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe

----------------------------------------------------------

Any help would be greatly appreciated!

chev65 · 16 Nov 2009

To get 8GB stable it sometimes helps to raise the memory voltage a bit or decrease the memory latency's a notch. Be sure and use the 2T command rate also. It may also help to increase the northbridge voltage a bit.

Set timings to 8 8 8 24 2T manually. According to what I have read about your particular memory, it may take 1.71-1.77 volts to get them stable at 1600MHz.

Source: OverClocked inside - Redaktion ocinside.de PC hardware page

Another one: 790FX-GD70 RAM settings....OCZ AMD vers

shaxs · 18 Nov 2009

Thanks for your reply. I waited to respond until after I had tested things a bit. I had already had the timings manually set to 8-8-8-24 1T at 1.65v. I can only increase voltage by incraments of .5- not .1. I tried the following settings:

2T at 1.7 v - seems to be the most stable. Games run with no crashes. However, I still get BSOD occasionally... I get them in a much less requency. One maybe every 6 hours or less. Majority of them look like this:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8, 0xfffff80002cb912b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111809-34070-01.>

2T at 1.75 or 1.8v an I get TONS of crashes and errors. Random exceptions, irql_not_less_than_equal, usbhub.sys errors, ect.

So, at this point I dont know what to do. Is 4 gigs of ram good enough anyways? Maybe I should just send 4 gb back and be happy with my stable 4....

chev65 · 18 Nov 2009

There is still more you can do to help get the 8GB stable. Chip set voltages will sometimes need to be bumped up a bit to get the 8GB stable. If you aren't sure which voltages to adjust try the Gygabyte forum. The divider you use can also have an impact on stablity.

Set tRFC to {88}
Set Command Rate to {2T}
Set MCH Core to {1.35 volts}
Set C.I.A.2 to {Disabled}
Set Performance Enhance to {Standard}