Jump to content
Corsair Community

TW3X4G1600C9DHX on Asus M4A785TD-V EVO


joksi

Recommended Posts

I have recently bought some new parts building my new AMD rig.

 

I know the board is pretty new, but their have already been released two new BIOS versions and im at the moment using the latest (0219). The BIOS setup is untouched, all voltages and frequencies are at "Auto".

 

When I first booted up in Vista x64 CPU-Z told me my memory was running at 553mhz (dual) at 1.5v, this gave me some rounding errors on Blend testing in Prime.

 

So I followed the instructions on the package and set the speed manually in BIOS to 800mhz with 9-9-9-24 at 1.8v, and then I dont see any errors in Prime because the computer either gives me BSOD or just simply reboots. This is after about 1-1,5h Blend testing in Prime. I have managed small FTT testing at about 4-5h succesfully though.

 

Now, could someone please help me? I cant get it stable running at 1600mhz, not even on the slower BIOS auto settings without errors. The motherboard are supposed to support up to 1800mhz OC.

 

This is my latest MEMORY.DMP file from Vista after running Prime, if it helps anything.

 

C:\Program Files (x86)\Support Tools>dumpchk C:\Windows\Minidump\Mini081809-01.dmp

Loading dump file C:\Windows\Minidump\Mini081809-01.dmp

----- 64 bit Kernel Mini Dump Analysis

 

DUMP_HEADER64:

MajorVersion 0000000f

MinorVersion 00001772

KdSecondaryVersion 00000000

DirectoryTableBase 00000001`0f178000

PfnDataBase fffff800`0227e250

PsLoadedModuleList fffff800`0221bdd0

PsActiveProcessHead fffff800`021fb440

MachineImageType 00008664

NumberProcessors 00000003

BugCheckCode 0000000a

BugCheckParameter1 fffff800`0a75bb1d

BugCheckParameter2 00000000`0000000d

BugCheckParameter3 00000000`00000000

BugCheckParameter4 fffff800`021237cf

KdDebuggerDataBlock fffff800`021c8f20

ProductType 00000001

SuiteMask 00000110

WriterStatus 00000002

MiniDumpFields 00000cff

 

TRIAGE_DUMP64:

ServicePackBuild 00000200

SizeOfDump 00040000

ValidOffset 0003fffc

ContextOffset 00000348

ExceptionOffset 00000f00

MmOffset 00002080

UnloadedDriversOffset 000020d0

PrcbOffset 00002260

ProcessOffset 00005d80

ThreadOffset 00006168

CallStackOffset 000065b8

SizeOfCallStack 00000ab8

DriverListOffset 000073a0

DriverCount 00000032

StringPoolOffset 00008fc0

StringPoolSize 00001080

BrokenDriverOffset 00000000

TriageOptions ffffffff

TopOfStack fffffa60`0bcad2f8

BStoreOffset 00000000

SizeOfBStore 00000000

LimitOfBStore 00000000`00000000

DebuggerDataOffset 00007070

DebuggerDataSize 00000330

DataBlocksOffset 0000a040

DataBlocksCount 0000000a

fffff800`0221c720 - fffff800`0221c79f at offset 0000a0e0

fffff800`02200898 - fffff800`0220089b at offset 0000a160

fffff800`02200894 - fffff800`02200897 at offset 0000a164

fffff800`0227e078 - fffff800`0227e07b at offset 0000a168

fffff800`0227e09c - fffff800`0227e09f at offset 0000a16c

fffffa80`03875000 - fffffa80`03875147 at offset 0000a170

fffff800`021e5970 - fffff800`021e5977 at offset 0000a2b8

fffff800`021e5978 - fffff800`021e597f at offset 0000a2c0

fffff800`0203e000 - fffff800`0203efff at offset 0000a2c8

fffff800`020b1000 - fffff800`020b1fff at offset 0000b2c8

Max offset c2c8, 35ee0 from end of file

 

 

Windows Vista Kernel Version 6002 (Service Pack 2) MP (3 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff800`02057000 PsLoadedModuleList = 0xfffff800`0221bdd0

Debug session time: Tue Aug 18 13:32:48.559 2009 (GMT+2)

System Uptime: 0 days 6:26:51.897

start end module name

fffff800`02011000 fffff800`02057000 hal Sat Apr 11 09:04:56 2009 (49E04118)

fffff800`02057000 fffff800`0256f000 nt Sat Apr 11 06:58:39 2009 (49E0237F)

fffffa60`0060f000 fffffa60`00619000 kdcom Sat Apr 11 09:07:57 2009 (49E041CD)

fffffa60`00619000 fffffa60`0062d000 PSHED Sat Apr 11 09:08:17 2009 (49E041E1)

fffffa60`0062d000 fffffa60`0068a000 CLFS Sat Apr 11 06:54:21 2009 (49E0227D)

fffffa60`0068a000 fffffa60`0073c000 CI Sat Apr 11 09:08:09 2009 (49E041D9)

fffffa60`0073c000 fffffa60`007a2000 volmgrx Sat Apr 11 07:35:14 2009 (49E02C12)

fffffa60`007a2000 fffffa60`007c6000 ataport Sat Apr 11 07:34:25 2009 (49E02BE1)

fffffa60`00805000 fffffa60`008df000 Wdf01000 Sat Jan 19 07:33:27 2008 (479199B7)

fffffa60`008df000 fffffa60`008ed000 WDFLDR Sat Jan 19 07:32:33 2008 (47919981)

fffffa60`008ed000 fffffa60`00943000 acpi Sat Apr 11 07:03:26 2009 (49E0249E)

fffffa60`00943000 fffffa60`0094c000 WMILIB Sat Jan 19 07:33:45 2008 (479199C9)

fffffa60`0094c000 fffffa60`00956000 msisadrv Sat Jan 19 07:02:50 2008 (4791928A)

fffffa60`00956000 fffffa60`00986000 pci Sat Apr 11 07:03:33 2009 (49E024A5)

fffffa60`00986000 fffffa60`0099b000 partmgr Sat Apr 11 07:34:51 2009 (49E02BFB)

fffffa60`0099b000 fffffa60`009af000 volmgr Sat Apr 11 07:34:49 2009 (49E02BF9)

fffffa60`009af000 fffffa60`009b6000 pciide Sat Apr 11 07:34:28 2009 (49E02BE4)

fffffa60`009b6000 fffffa60`009c6000 PCIIDEX Sat Apr 11 07:34:22 2009 (49E02BDE)

fffffa60`009c6000 fffffa60`009d9000 mountmgr Sat Jan 19 07:28:01 2008 (47919871)

fffffa60`009d9000 fffffa60`009e1000 atapi Sat Apr 11 07:34:19 2009 (49E02BDB)

fffffa60`009e1000 fffffa60`009eb000 msahci Sat Apr 11 07:34:29 2009 (49E02BE5)

fffffa60`00a0a000 fffffa60`00a51000 fltmgr Sat Apr 11 06:54:38 2009 (49E0228E)

fffffa60`00a51000 fffffa60`00a65000 fileinfo Sat Jan 19 07:05:23 2008 (47919323)

fffffa60`00a65000 fffffa60`00aec000 ksecdd Mon Jun 15 15:15:18 2009 (4A364966)

fffffa60`00aec000 fffffa60`00b3c000 msrpc unavailable (00000000)

fffffa60`00b3c000 fffffa60`00b95000 NETIO Sat Apr 11 07:43:34 2009 (49E02E06)

fffffa60`00b95000 fffffa60`00ba1000 tunnel Sat Jan 19 07:36:44 2008 (47919A7C)

fffffa60`00ba1000 fffffa60`00baa000 tunmp Sat Jan 19 07:36:30 2008 (47919A6E)

fffffa60`00baa000 fffffa60`00bbd000 processr Sat Jan 19 06:52:45 2008 (4791902D)

fffffa60`00c0b000 fffffa60`00dce000 ndis Sat Apr 11 07:43:15 2009 (49E02DF3)

fffffa60`00dce000 fffffa60`00dfa000 CLASSPNP Sat Apr 11 07:34:15 2009 (49E02BD7)

fffffa60`00e0e000 fffffa60`00f83000 tcpip Sat Apr 11 07:44:47 2009 (49E02E4F)

fffffa60`00f83000 fffffa60`00faf000 fwpkclnt Sat Apr 11 07:42:44 2009 (49E02DD4)

fffffa60`00faf000 fffffa60`00fdb000 ecache Sat Apr 11 07:36:18 2009 (49E02C52)

fffffa60`00fdb000 fffffa60`00fef000 disk Sat Apr 11 07:34:38 2009 (49E02BEE)

fffffa60`01008000 fffffa60`01188000 Ntfs Sat Apr 11 06:55:38 2009 (49E022CA)

fffffa60`01188000 fffffa60`011cc000 volsnap Sat Apr 11 07:35:33 2009 (49E02C25)

fffffa60`011cc000 fffffa60`011d4000 spldr Mon Jan 12 22:51:29 2009 (496BBB61)

fffffa60`011d4000 fffffa60`011db000 speedfan Sun Sep 24 15:26:48 2006 (45168798)

fffffa60`011db000 fffffa60`011ed000 mup Sat Apr 11 06:54:47 2009 (49E02297)

fffffa60`011ed000 fffffa60`011f5000 AtiPcie Tue May 05 17:00:22 2009 (4A005486)

fffffa60`011f5000 fffffa60`011ff000 crcdisk Thu Nov 02 10:39:40 2006 (4549BCDC)

fffffa60`0620e000 fffffa60`06833000 atikmdag Wed Jul 15 04:41:07 2009 (4A5D41C3)

fffffa60`06833000 fffffa60`06914000 dxgkrnl Sat Apr 11 07:10:13 2009 (49E02635)

fffffa60`06914000 fffffa60`06924000 watchdog Sat Apr 11 07:09:16 2009 (49E025FC)

fffffa60`06a0b000 fffffa60`06af8000 HDAudBus Sat Apr 11 07:39:38 2009 (49E02D1A)

fffffa60`06af8000 fffffa60`06b2e000 Rtlh64 Mon May 25 08:51:01 2009 (4A1A3FD5)

fffffa60`06b2e000 fffffa60`06b39000 usbohci Sat Apr 11 07:39:36 2009 (49E02D18)

fffffa60`06b39000 fffffa60`06b7f000 USBPORT Sat Apr 11 07:39:39 2009 (49E02D1B)

fffffa60`06b7f000 fffffa60`06b8b000 usbfilter Fri Apr 03 13:39:51 2009 (49D5F587)

 

Unloaded modules:

fffffa60`0c486000 fffffa60`0c48e000 cpuz132_x64.

Timestamp: unavailable (00000000)

Checksum: 00000000

fffffa60`0c427000 fffffa60`0c42f000 AODDriver.sy

Timestamp: unavailable (00000000)

Checksum: 00000000

fffffa60`081c6000 fffffa60`081cf000 drmkaud.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

fffffa60`00fef000 fffffa60`00ffd000 crashdmp.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

fffffa60`00e00000 fffffa60`00e0c000 dump_pciidex

Timestamp: unavailable (00000000)

Checksum: 00000000

fffffa60`00c00000 fffffa60`00c0a000 dump_msahci.

Timestamp: unavailable (00000000)

Checksum: 00000000

fffffa60`00bbd000 fffffa60`00bc8000 kbdhid.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

Finished dump check

Link to comment
Share on other sites

Oh, sorry I forgot to mention, i have run memtest86+ v1.65 that I have on an old CD, and it dont report any errors. I have run it for 8 h, once or twice for 1 h too.

 

Why do you think I should set them att 1333 when their rated for 1600?

Should i try 1333 with same timings (9-9-9-24)?

Link to comment
Share on other sites

Okey, now you lost me!

 

So my motherboard supports 1600OC (it states so, having option 800mhz speed in BIOS), but my CPU doesnt?

 

Hmm, by overclocking are you meaning incresing the HT reference clock (default 200mhz) or by raising the multiplier (I have a BE)?

 

If so, at what CPU speed should it work together with the memory modules at 1600mhz??

Link to comment
Share on other sites

  • Corsair Employees
Please check with AMD to be sure and I am sorry I cannot tell you how to over clock your system only what we test with a specific module. But to make sure its not a failing module please try what I suggested first.
Link to comment
Share on other sites

Well, I dont understand my motherboard supporting AM3 CPUs stating one thing, and AMD stating another for their CPUs?

 

I understand that multiplier increases doesnt affect memoryspeed, only cpu speed. So that means if the x3 720 doesnt support 1600mhz, i need to set it manually at 1333mhz and raise the HT link to be able to also raise the speed of the memory modules?

 

I did a quick search and found the following, which i were not at all informed about. If i were i sure wouldnt put that extra cash on the 1600mhz modules....

 

"Support for unregistered DIMMs up to PC3 10666 (DDR3-1333MHz) AM3 Board

**NOTE: for DDR3-1333, AM3 boards will support 1-DIMM-per-channel @ 1333MHz "

 

This also means I cannot use my memory modules in dual mode at 1333mhz!??

None of this information is provided in the ASUS user manual, in the contrary it states support from 1600oc-1800oc DDR3

Link to comment
Share on other sites

  • Corsair Employees
"Support for unregistered DIMMs up to PC3 10666 (DDR3-1333MHz) AM3 Board

**NOTE: for DDR3-1333, AM3 boards will support 1-DIMM-per-channel @ 1333MHz "

 

This also means I cannot use my memory modules in dual mode at 1333mhz!??

None of this information is provided in the ASUS user manual, in the contrary it states support from 1600oc-1800oc DDR3

 

I would take that to mean it would support Two modules one per channel Max at DDR1333. So one set at DDR1333 in D/C.

Link to comment
Share on other sites

Why then doesnt Asus mention anything about this limitation if its really facts?

I mean in the user manual for the motherboard it says support for upto 1800Mhz OC DDR3, and the motherboard has an option in BIOS of setting the speed to 400, 566, 667 and 800Mhz.

The Corsair memory is rated at 1600mhz 9-9-9-24, does this mean my CPU is faulty?

 

Also, when sen on auto, why does my motherboard detect my memory as 533mhz modules? Something must be faulty here...

Link to comment
Share on other sites

  • Corsair Employees

I think you may be miss understanding the spec, no offense.

1800Mhz OC DDR

"OC" = Over Clock so what that means is that to reach that speed you would have to over clock the system and actually while it my run fine with DDR1600 or DDR1800 it is still an over clock and there is no way they or any one can guarantee that in every configuration it will over clock to that speed.

Link to comment
Share on other sites

Okey, i start to get it now.

 

But, then answer me, the usual method of overclocking is by rasing the FSB. right?

Only raising multiplier on a BE CPU doesnt affect the memory speed in any way, right?

 

Then if im correct, why on earth does Asus give me the memory setting to choose in BIOS 800mhz, that mean 1600mhz in real DDR speed?

Am I getting it wrong, or is it maybe supposed to raise the multiplier to be able to actually utilize this 800mhz setting on the board?

 

Also, my motherboard QVL lists this Corsair 1600mhz module as compatible, so it should be able to run it at 1600mhz. I dont get why it doesnt.

 

Also I dont understand why my motherboard only detects the memory as 533, and not as you say 667 (1333mhz)

Link to comment
Share on other sites

I have this same motherboard (but I'm using DDR3-1333).

 

When I first installed my memmory it was only registering 533 single channel (2x2GB).

I discovered that the way the manual and board is labelled, the manual incorectly states what slots are D.C. compatible.

 

The MB and manual show this illustration:

::=======-=================:: <-- DIMM_A2

::=======-=================:: <-- DIMM_B2

 

::=======-=================:: <-- DIMM_A1

::=======-=================:: <-- DIMM_B1

 

And the manual states that for dual channel operation:[ Channel ................... Sockets]

[Channel A .................. A1+A2 ]

[Channel B ................... B1+B2 ]

 

This is wrong, only after I placed my memory in side-by-side slots (A1/B1 or A2B2) did my memory run full speed (667) and in D.C. This may be your problem if you've installed the memory per the manual instructions verbatim. When my other 2 sticks of ram get here in a few days, I'll try running two channels in D.C. - hopefully the motherboard can support both pairs @ D.C.

Link to comment
Share on other sites

  • Corsair Employees

You would have to ask the MB maker about these questions as to why they did what they did.

And with most of the channel MB products they have taken the lock and limits off of the BIOS so they are more easy to over clock. I would search for the model of Mb you have and read up on the MB reviews would be the best place to start looking for (How to Over clock) and what the reviewers did to over clock the system.

Link to comment
Share on other sites

I have this same motherboard (but I'm using DDR3-1333).

 

When I first installed my memmory it was only registering 533 single channel (2x2GB).

I discovered that the way the manual and board is labelled, the manual incorectly states what slots are D.C. compatible.

 

The MB and manual show this illustration:

::=======-=================:: <-- DIMM_A2

::=======-=================:: <-- DIMM_B2

 

::=======-=================:: <-- DIMM_A1

::=======-=================:: <-- DIMM_B1

 

And the manual states that for dual channel operation:[ Channel ................... Sockets]

[Channel A .................. A1+A2 ]

[Channel B ................... B1+B2 ]

 

This is wrong, only after I placed my memory in side-by-side slots (A1/B1 or A2B2) did my memory run full speed (667) and in D.C. This may be your problem if you've installed the memory per the manual instructions verbatim. When my other 2 sticks of ram get here in a few days, I'll try running two channels in D.C. - hopefully the motherboard can support both pairs @ D.C.

 

This is not my problem, i had the modules side by side in the black slots first, and BIOS at auto. CPU-Z reports 533mhz DC, now I have moved the modules to the blue slots (side by side) because Asus claims these are better suited for high performing modules (?) but there is not difference, in no way does my motherboard detect my memorys as 667 mhz by default.

 

The manual description your talking about is correct, A1 and A2 is one channel, and B1 and B2 is the other channel. So the modules have to be put each in one of the channels, to become DC. So one module in A1 and one in B1, or one module in A2 and B2. A1 and A2 or B1 and B2 will give single mode.

Link to comment
Share on other sites

Well, in my case i doesnt matter if I have them in the black or blue slots, but I think if Asus recommends higher performance memory in the blue slots then I cannot talk against them. In both cases CPU-Z reports that my MB detects them as 533mhz, yet in DC mode.

 

Im starting to think I need to up the multiplier on the CPU/northbridge (memory controller) to make 1600mhz work.

AMD OverDrive application has a feature called BEMP, downloading supported memory module setting profiles automatically. My memory modules are states as supported in this function, however it seems the MB must also support the BEMP function for automatic setting in AMD Overdrive (mine seem to not support it).

 

I will try to manually use the timings settings from a screenshot from a review of my corsair modules in Overdrive, and up the NB speed at 12x (2400ghz) from default 10x and see if this can make the memory stable at 1600mhz. Maybe this is the key, i have read some things about this today...

 

What is the maximum allowed voltage to the memory modules?

Link to comment
Share on other sites

Update!

 

It seems upping the CPU-NB voltage from default 1.2 to approx 1.25 have solved my instabilities running at 1600mhz.

 

I have now primed the Blend test for approx 8 hours without any reported errors, hickups or reboots. :)

Link to comment
Share on other sites

Okey

 

Please, if you would like to answer some questions (if you can)

 

1 Does increasing the CPU-NB voltage have a negative impact on my CPU temp?

 

2 Do i need to up the cpu voltage too for this?

 

3 In the following test: http://www.modreactor.com/english/Reviews/DDR2-DDR3-Memory-Roundup-Corsair-********-********-Elixir/Page-12-Closer-look-and-Conclusion-on-Corsair-XMS3-2x2GB-DDR3-PC3-16000-1600MHz.html

They say they run these modules I have at tighter timings on other then that default memory setup, 1600mhz 1.8v (8-8-8-24 1600MHz and even at 1600MHz 7-7-7-20)

Could that be true?

 

I have also read that the XMS3 is one of few supported in AMDs Black Edition Memory Profiles (BEMP), i have found a profile for it and it states the following settings.

 

CL 9

tRCD 9

tRP 9

tRAS 24

tRC 34

CR 1T

tRFC 110ns

tRRD 5

tWR 10

tWTR 5

 

In my Bios i have all of those values at auto, except for the cl, trcd, trp and tras (9-9-9-24) at 1.8v. Also the AMD profile is setting the memory volt at 1.75, and the NB frequency at 2400mhz from default 2000 (probably something with AMD CPU stability?)

 

The question is, should i test the review tighter timings, should i use the manual settings from AMD profile (i have a BE CPU) or lastly should I keep my actual settings of 9-9-9-24 1.8v and the rest at auto?

Link to comment
Share on other sites

  • Corsair Employees
1 Does increasing the CPU-NB voltage have a negative impact on my CPU temp?

A: Yes more Voltage will cause more heat, but its a give and take when over clocking.

 

2 Do i need to up the cpu voltage too for this?

A: Yes you may have to but I would only add whats needed.

3 In the following test: http://www.modreactor.com/english/Re...0-1600MHz.html

They say they run these modules I have at tighter timings on other then that default memory setup, 1600mhz 1.8v (8-8-8-24 1600MHz and even at 1600MHz 7-7-7-20)

Could that be true?

A: I can only support the tested settings but you are welcome to try anything you like. And I would just use the settings as printed on the modules and use the settings from the reviewer as a refereence when you setup your system like the memory and CPU VCore.

Link to comment
Share on other sites

Thank you for answers!

 

Well, in search for best possible timings I have browsed the web, and i have done following conclusions from my experiences.

 

1. With the rated settings, 1600mhz 9-9-9-24 1.8v, and every other timing set at "auto" (my asus board has a dozen of these timing values!) my computer freezes after max 2 min in prime blend test (all other components on stock frequencies). The solution is to up the CPU-NB from default 1.2v to 1.25v, like stated earlier.

 

2. When manually changing several timing values instead (according to the attatched picture), I do not have to up the CPU-NB voltage for the modules to not freeze my computer.

 

The attached image is an AMD/Corsair Black Edition Memory Profile screenshot found on the web for these modules!

Now, my question is, should i use these timings in the screenshot (stable without voltage boost) or should I use only "9-9-9-24" per your specifications (plus voltage boost)? And second, why are not the factory specification stable without voltage boost? Its a mess truly!

 

Notice the fact, the profile recommends 1.75v, you recommend 1.8v (at same speed)?

bemp.jpg.a8c90db76b306a18e9416d59cf2f0091.jpg

Link to comment
Share on other sites

  • Corsair Employees
1. With the rated settings, 1600mhz 9-9-9-24 1.8v, and every other timing set at "auto" (my asus board has a dozen of these timing values!) my computer freezes after max 2 min in prime blend test (all other components on stock frequencies). The solution is to up the CPU-NB from default 1.2v to 1.25v, like stated earlier.

A: The CPU would be the determining factor and the CPU you have I am pretty sure is rated at DDR1333 or DDR1066 anything above that would be an Over Clock, but I would suggest asking AMD to be sure.

 

2. When manually changing several timing values instead (according to the attatched picture), I do not have to up the CPU-NB voltage for the modules to not freeze my computer.

A: That is not uncommon with over clocking and would be expected.

 

The attached image is an AMD/Corsair Black Edition Memory Profile screenshot found on the web for these modules!

Now, my question is, should i use these timings in the screenshot (stable without voltage boost) or should I use only "9-9-9-24" per your specifications (plus voltage boost)? And second, why are not the factory specification stable without voltage boost? Its a mess truly!

A: I think that has been explained it is over clocking and some tweaking would be required.

Link to comment
Share on other sites

  • 3 weeks later...

My system is locking up when running the RAM at 1600Mhz.

 

It seems SPD is ignored because the memory is being detected as 1066Mhz. I don't know which option to choose instead of Auto when specifying 9-9-9-24 (DCT 0, DCT 1, or Both?) and which voltage? 1.75 or 1.80? I've tried them all at 1066, 1333, and 1600--values specified or at Auto--and Memtest always finds errors at 1691.6MB and 1693.1MB. Both memory boards are installed in the blue slots.

 

How do I configure my motherboard for use with this memory?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...