GA-X58-UD3R: 4Gb on cold boot.

[yann3804]

I cannot find the requested S/N on my dimms (for the authorization form)
Where is that serial number located? Is it the 13 digit number on every dimm?

EDIT: And forgot to say, thank you G.Skill for such an amazing customer support.

[yann3804]

Update:

I ran Prime95 for more than one hour, and had a memory fault.
This is the message from the log file:

[Mon Dec 27 15:54:26 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Maybe a voltage problem, but it is memory related. Could mean something.

[GSKILL TECH]

Yes, the S/N is typically right under the barcode.

Rounding error can surely be voltage related, but I don't know what voltages you are using.

Thank you
GSKILL TECH

[yann3804]

Should I type in the three s/n?
The only difference between the three serial numbers is the ending digit

I was using 1.56 VDimm when the error occurred. This was for testing purpose only since another guy from TweakTown told me that some chips did not like high voltage...

[Tradesman]

Correct on the ser#, and you can raise the VDimm a bit more

[yann3804]

Will do.

I sent in the RMA authorization form.

EDIT: I just found another guy who fixed his problem by replacing his RAM. In fact, the same model as me...

http://gskill.us/forum/showthread.php?t=4995

Even another one here

http://gskill.us/forum/showthread.php?t=4874

[yann3804]

6gb detected this morning... But the trade-off is that it didn't want to boot into Windows!
No matter what voltage or latency I tried to modify, it would get stuck at the Windows 7 booting logo and just get back to the POST like a power cycle.

Then when I restarted the computer (shutting it down electrically) it booted correctly.

I also got some minidump file here, but I don't really know how to read it. Windbg tells me I have the wrong symbols or something.

[yann3804]

So here's the mini-dump...

BugCheck 50, {fffff88027c22fd8, 0, fffff88002dcea0f, 2}

Unable to load image \SystemRoot\system32\DRIVERS\epfw.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for epfw.sys
*** ERROR: Module load completed but symbols could not be loaded for epfw.sys

Could not read faulting driver name
Probably caused by : epfw.sys ( epfw+4a0f )

Followup: MachineOwner

More debugging details:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88027c22fd8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88002dcea0f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b00e0
 fffff88027c22fd8 

FAULTING_IP: 
epfw+4a0f
fffff880`02dcea0f 448b93488d4c24  mov     r10d,dword ptr [rbx+244C8D48h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003759cb0 -- (.trap 0xfffff88003759cb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800375a310 rbx=0000000000000000 rcx=fffff8800375a410
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002dcea0f rsp=fffff88003759e40 rbp=0000000000000080
 r8=0000000000000000  r9=0000000000000000 r10=2652a54cd85fabd9
r11=0000000000000020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
epfw+0x4a0f:
fffff880`02dcea0f 448b93488d4c24  mov     r10d,dword ptr [rbx+244C8D48h] ds:1e20:00000000`244c8d48=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e9220c to fffff80002e77580

STACK_TEXT:  
fffff880`03759b58 fffff800`02e9220c : 00000000`00000050 fffff880`27c22fd8 00000000`00000000 fffff880`03759cb0 : nt!KeBugCheckEx
fffff880`03759b60 fffff800`02e7566e : 00000000`00000000 fffff880`27c22fd8 00000000`00000000 fffff880`0375a290 : nt!MmAccessFault+0x79d
fffff880`03759cb0 fffff880`02dcea0f : fffffa80`00000000 fffff880`0375a710 00000000`a02e2e12 ffffffff`fffff954 : nt!KiPageFault+0x16e
fffff880`03759e40 fffffa80`00000000 : fffff880`0375a710 00000000`a02e2e12 ffffffff`fffff954 44566bf8`9edafe41 : epfw+0x4a0f
fffff880`03759e48 fffff880`0375a710 : 00000000`a02e2e12 ffffffff`fffff954 44566bf8`9edafe41 5ed1a3e2`1435fbf1 : 0xfffffa80`00000000
fffff880`03759e50 00000000`a02e2e12 : ffffffff`fffff954 44566bf8`9edafe41 5ed1a3e2`1435fbf1 00000000`a02e2e12 : 0xfffff880`0375a710
fffff880`03759e58 ffffffff`fffff954 : 44566bf8`9edafe41 5ed1a3e2`1435fbf1 00000000`a02e2e12 00000000`00000000 : 0xa02e2e12
fffff880`03759e60 44566bf8`9edafe41 : 5ed1a3e2`1435fbf1 00000000`a02e2e12 00000000`00000000 00000000`00000000 : 0xffffffff`fffff954
fffff880`03759e68 5ed1a3e2`1435fbf1 : 00000000`a02e2e12 00000000`00000000 00000000`00000000 00000000`00000000 : 0x44566bf8`9edafe41
fffff880`03759e70 00000000`a02e2e12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5ed1a3e2`1435fbf1
fffff880`03759e78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa02e2e12


STACK_COMMAND:  kb

FOLLOWUP_IP: 
epfw+4a0f
fffff880`02dcea0f 448b93488d4c24  mov     r10d,dword ptr [rbx+244C8D48h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  epfw+4a0f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: epfw

IMAGE_NAME:  epfw.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49dded6b

FAILURE_BUCKET_ID:  X64_0x50_epfw+4a0f

BUCKET_ID:  X64_0x50_epfw+4a0f

Followup: MachineOwner

Basically the error code is this:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b00e0
fffff88027c22fd8

So basically Windows tried to allocate memory on nonexistent memory, so it messed up things. Still a RAM problem.