Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: hello people on October 12, 2010, 12:40:34 am
-
I'm having cold boot failures. If I shut down and unplug and replug in HD it then boots. But on a cold boot...nope.
My specs:
I7 930 2.8g
Gigabyte X58A-UD3R Rev2.0
HIS ATI pcie HD5670
Seagate 3.5 Sata2 1TB x2
ADATA 2g DDR3 1600 3x2g
Zalman CNPS10X Quiet CPU Cooler
Cooler Master Silent Pro M700 PSU
Windows 7 Home Premium 64b
I think my bios if FB...
I am looking for the FC1 bios....anyone know where I can dl it?
I think it might help with my cold boot problems.
Or...it could be another issue.
I would love to get to the bottom of it.
Once booted, the system runs awesome!
thanks
-
Hi and welcome to the Gigabyte Forum.
I would suggest that you try TweakTown Forum (our USA counterpart) or ask GGTS for a copy. TweakTown usually have newer versions before we get them.
http://forums.tweaktown.com/
-
Sure...I have flashed the bios to FC1. I suppose I need to power off and wait for a cold boot. So I'll do that now.
I noticed that my cpu temps were showing 50 degrees since the flash to FC1...I'm sure I saw that it held steady at around 37 degrees before the flash.
Actually before I power down I am going to try to flash the backup bios by pressing Alt/ F12. The backup bios is still FA version.
Hope my problems are solved.
How long do you wait for a cold boot? An hour?
-
To be honest I suppose it depends on what is causing the problem that you are testing for. In normal circumstances I would just say to power down the machine completely(as if you were going to do a CMOS clear) by removing the power from the mains and then pressing the power button for a few seconds. Leave for a few minuites to cool and then boot up.
-
Cold boot testing this morning gives me this blue screen error:
Stop: 0x000000FC (0xFFFFF8A0000CA588, 0x8CA00001938B6963, 0xFFFFF8802B32AF0, 0x0000000000000002)
I suppose it means it's either bad physical ram...or some settings are wrong in bios
-
I would say so. Try downloading Memtest86+ and running it on the sticks one at a time for at least 10 loops each. If you get any errors then the memory is faulty.
Memtest86+ http://www.memtest.org/
or this version, updated for X58A http://www.memtest.org/download/beta/415b2/mt415.rar
-
I have started to do all of the things advised....from another forum someone has advised me to run Windows SDK bug checking software. My crash dumps...from the last 3 or so days are as follows. It doesn't mean much to me...but to someone else it could mean something. I'll post it here and continue troubleshooting...
Please note that on the 10th and 11 of Oct...I believe I had bios FB.....after that bios FC1
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101010-21668-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Sun Oct 10 09:26:20.905 2010 (UTC + 8:00)
System Uptime: 0 days 0:00:11.966
Loading Kernel Symbols
...............................................................
.............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a0055da000, 0, fffff80002d6e533, 2}
10th October 2010
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!HvpSetRangeProtection+a3 )
Followup: MachineOwner
1: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8a0055da000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d6e533, 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 fffff80002d070e0
fffff8a0055da000
FAULTING_IP:
nt!HvpSetRangeProtection+a3
fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h
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: fffff88003cc25f0 -- (.trap 0xfffff88003cc25f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a001367000 rbx=0000000000000000 rcx=fffff8a0055da009
rdx=fffff8a0055da000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d6e533 rsp=fffff88003cc2780 rbp=0000000000d8b000
r8=0000000000000000 r9=0000000000000004 r10=0000000000700065
r11=0000000001ffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!HvpSetRangeProtection+0xa3:
fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h ds:f000:fffff8a0`055da000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4e8f2 to fffff80002acf740
STACK_TEXT:
fffff880`03cc2488 fffff800`02b4e8f2 : 00000000`00000050 fffff8a0`055da000 00000000`00000000 fffff880`03cc25f0 : nt!KeBugCheckEx
fffff880`03cc2490 fffff800`02acd82e : 00000000`00000000 00000000`00700065 00000000`00001000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`03cc25f0 fffff800`02d6e533 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03cc2780 fffff800`02d5da68 : fffff8a0`05c64800 fffff8a0`0088c0c0 fffff8a0`31334d43 00000000`00000004 : nt!HvpSetRangeProtection+0xa3
fffff880`03cc27e0 fffff800`02e36253 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`038d3000 : nt!HvFreeHive+0x108
fffff880`03cc2860 fffff800`02d50d89 : fffff880`03cc2a00 fffff880`03cc2b20 ffffffff`80000254 fffff880`03cc2ac8 : nt! ?? ::NNGAKEGL::`string'+0x5a1cb
fffff880`03cc2950 fffff800`02f4dbed : 00000000`00000000 fffff800`00000200 fffff880`03cc2ae0 fffff800`02c490eb : nt!CmpInitHiveFromFile+0x249
fffff880`03cc2a70 fffff800`02d73c06 : 00000000`01c194d7 fffffa80`062229a0 00000000`00000080 fffffa80`04e89890 : nt!CmpLoadHiveThread+0x14d
fffff880`03cc2d40 fffff800`02aadc26 : fffff880`009e9180 fffffa80`062229a0 fffff880`009f40c0 fffff880`0123ba90 : nt!PspSystemThreadStartup+0x5a
fffff880`03cc2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!HvpSetRangeProtection+a3
fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!HvpSetRangeProtection+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x50_nt!HvpSetRangeProtection+a3
BUCKET_ID: X64_0x50_nt!HvpSetRangeProtection+a3
Followup: MachineOwner
From 11th October
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101110-20030-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Mon Oct 11 17:53:50.624 2010 (UTC + 8:00)
System Uptime: 0 days 0:00:11.686
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 0, fffff8a005785800}
GetPointerFromAddress: unable to read from fffff80002d090e0
GetUlongFromAddress: unable to read from fffff80002c771b0
GetUlongFromAddress: unable to read from fffff80002c771b0
Probably caused by : ntkrnlmp.exe ( nt!HvFreeHive+147 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a005785800, Address of the block of pool being deallocated
Debugging Details:
------------------
GetUlongFromAddress: unable to read from fffff80002c771b0
GetUlongFromAddress: unable to read from fffff80002c771b0
POOL_ADDRESS: fffff8a005785800
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002c0460e to fffff80002ad1740
STACK_TEXT:
fffff880`040c2728 fffff800`02c0460e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx
fffff880`040c2730 fffff800`02d5faa7 : fffff8a0`00ca7b80 fffff8a0`0079c0c0 fffff8a0`31334d43 00000000`00000004 : nt!ExDeferredFreePool+0x11eb
fffff880`040c27e0 fffff800`02e38253 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`038d5000 : nt!HvFreeHive+0x147
fffff880`040c2860 fffff800`02d52d89 : fffff880`040c2a00 fffff880`040c2b20 ffffffff`80000258 fffff880`040c2ac8 : nt! ?? ::NNGAKEGL::`string'+0x5a1cb
fffff880`040c2950 fffff800`02f4fbed : 00000000`00000000 fffff800`00000200 fffff880`040c2ae0 fffff800`02c4b0eb : nt!CmpInitHiveFromFile+0x249
fffff880`040c2a70 fffff800`02d75c06 : 00000000`01b02f96 fffffa80`04eb4370 00000000`00000080 fffffa80`04e89890 : nt!CmpLoadHiveThread+0x14d
fffff880`040c2d40 fffff800`02aafc26 : fffff880`009e9180 fffffa80`04eb4370 fffff880`009f40c0 fffff880`0122ba90 : nt!PspSystemThreadStartup+0x5a
fffff880`040c2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!HvFreeHive+147
fffff800`02d5faa7 8b8c2480000000 mov ecx,dword ptr [rsp+80h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!HvFreeHive+147
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xc2_7_nt!HvFreeHive+147
BUCKET_ID: X64_0xc2_7_nt!HvFreeHive+147
Followup: MachineOwner
---------
From the 12th October 2010
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101210-20997-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Tue Oct 12 06:08:06.156 2010 (UTC + 8:00)
System Uptime: 0 days 0:00:11.218
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002db0548, fffff880033859f8, fffff88003385260}
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceKeyControlBlock+5c )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002db0548, The address that the exception occurred at
Arg3: fffff880033859f8, Exception Record Address
Arg4: fffff88003385260, 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!CmpDereferenceKeyControlBlock+5c
fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h]
EXCEPTION_RECORD: fffff880033859f8 -- (.exr 0xfffff880033859f8)
ExceptionAddress: fffff80002db0548 (nt!CmpDereferenceKeyControlBlock+0x000000000000005c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000618
Attempt to read from address 0000000000000618
CONTEXT: fffff88003385260 -- (.cxr 0xfffff88003385260)
rax=0000000000000000 rbx=fffffa8004f04600 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffff8a00098aa58
rip=fffff80002db0548 rsp=fffff88003385c30 rbp=0000000000000001
r8=fffff8a0000596b0 r9=000000000d7820f2 r10=fffff8a0009894a8
r11=fffffa8004f04680 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CmpDereferenceKeyControlBlock+0x5c:
fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h] ds:002b:00000000`00000618=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000618
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
0000000000000618
FOLLOWUP_IP:
nt!CmpDereferenceKeyControlBlock+5c
fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002db09c4 to fffff80002db0548
STACK_TEXT:
fffff880`03385c30 fffff800`02db09c4 : fffffa80`04f04600 00000000`00000001 fffff8a0`000232e0 fffffa80`04f04680 : nt!CmpDereferenceKeyControlBlock+0x5c
fffff880`03385c80 fffff800`02aca961 : fffff800`02db08dc fffff800`02c625f8 fffffa80`04f04680 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8
fffff880`03385cb0 fffff800`02d61c06 : ee11ed10`3a13b813 fffffa80`04f04680 00000000`00000080 fffffa80`04e89890 : nt!ExpWorkerThread+0x111
fffff880`03385d40 fffff800`02a9bc26 : fffff880`03167180 fffffa80`04f04680 fffff880`031720c0 98a4022c`91b15939 : nt!PspSystemThreadStartup+0x5a
fffff880`03385d80 00000000`00000000 : fffff880`03386000 fffff880`03380000 fffff880`033859f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpDereferenceKeyControlBlock+5c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff88003385260 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c
BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c
Followup: MachineOwner
---------
-
I have to put the rest in a new post.........
From the 13th October 2010
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101310-21871-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Wed Oct 13 06:11:56.061 2010 (UTC + 8:00)
System Uptime: 0 days 0:00:12.029
Loading Kernel Symbols
...............................................................
...................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8800403f004, 0, fffff80002a82a87, 0}
Could not read faulting driver name
Probably caused by : Npfs.SYS ( Npfs!NpCreateNamedPipePrefix+68 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8800403f004, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a82a87, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb00e0
fffff8800403f004
FAULTING_IP:
nt!SepPrivilegeCheck+37
fffff800`02a82a87 8b19 mov ebx,dword ptr [rcx]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: smss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800403e370 -- (.trap 0xfffff8800403e370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800403f004
rdx=0000000000000726 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a82a87 rsp=fffff8800403e500 rbp=fffffa8006097e60
r8=0000000000000801 r9=0000000000000801 r10=000000000000000d
r11=0000000e60b1e890 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!SepPrivilegeCheck+0x37:
fffff800`02a82a87 8b19 mov ebx,dword ptr [rcx] ds:d000:fffff880`0403f004=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002af8f14 to fffff80002a78740
STACK_TEXT:
fffff880`0403e208 fffff800`02af8f14 : 00000000`00000050 fffff880`0403f004 00000000`00000000 fffff880`0403e370 : nt!KeBugCheckEx
fffff880`0403e210 fffff800`02a7682e : 00000000`00000000 00000000`00000000 fffff880`00961000 fffff800`02aaa75b : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`0403e370 fffff800`02a82a87 : 0000000e`60b1e890 00000000`000001f1 fffff880`0403e6d0 fffff800`02d7dfce : nt!KiPageFault+0x16e
fffff880`0403e500 fffff800`02d7dfce : 00000000`00000000 00000000`00000000 00000000`00000010 fffff880`0149d000 : nt!SepPrivilegeCheck+0x37
fffff880`0403e520 fffff880`0149d04c : fffffa80`05ef6890 00000000`00000000 fffffa80`06097e60 fffffa80`04ea5850 : nt!SePrivilegeCheck+0x2e
fffff880`0403e560 fffff880`0149c6d7 : 00000000`00f80032 00000000`00000002 00000000`00000000 00000000`00000000 : Npfs!NpCreateNamedPipePrefix+0x68
fffff880`0403e610 fffff800`02d7b807 : 00000000`80000005 7ffff800`02d7b260 fffff800`02d7b260 fffffa80`04f2c610 : Npfs!NpFsdCreate+0x123
fffff880`0403e740 7ffff800`02d71e84 : fffffa80`05ef6890 00000000`80000000 7ffffa80`04ea6010 00000000`00000001 : nt!IopParseDevice+0x5a7
fffff880`0403e8d0 fffffa80`05ef6890 : 00000000`80000000 7ffffa80`04ea6010 00000000`00000001 fffffa80`00000040 : 0x7ffff800`02d71e84
fffff880`0403e8d8 00000000`80000000 : 7ffffa80`04ea6010 00000000`00000001 fffffa80`00000040 7ffff880`0403ea30 : 0xfffffa80`05ef6890
fffff880`0403e8e0 7ffffa80`04ea6010 : 00000000`00000001 fffffa80`00000040 7ffff880`0403ea30 fffff880`0403e940 : 0x80000000
fffff880`0403e8e8 00000000`00000001 : fffffa80`00000040 7ffff880`0403ea30 fffff880`0403e940 fffffa80`04f2c610 : 0x7ffffa80`04ea6010
fffff880`0403e8f0 fffffa80`00000040 : 7ffff880`0403ea30 fffff880`0403e940 fffffa80`04f2c610 00000000`00000000 : 0x1
fffff880`0403e8f8 7ffff880`0403ea30 : fffff880`0403e940 fffffa80`04f2c610 00000000`00000000 fffff880`0403e928 : 0xfffffa80`00000040
fffff880`0403e900 fffff880`0403e940 : fffffa80`04f2c610 00000000`00000000 fffff880`0403e928 fffff801`00000000 : 0x7ffff880`0403ea30
fffff880`0403e908 fffffa80`04f2c610 : 00000000`00000000 fffff880`0403e928 fffff801`00000000 00000000`00000000 : 0xfffff880`0403e940
fffff880`0403e910 00000000`00000000 : fffff880`0403e928 fffff801`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`04f2c610
STACK_COMMAND: kb
FOLLOWUP_IP:
Npfs!NpCreateNamedPipePrefix+68
fffff880`0149d04c 84c0 test al,al
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: Npfs!NpCreateNamedPipePrefix+68
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Npfs
IMAGE_NAME: Npfs.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114
FAILURE_BUCKET_ID: X64_0x50_Npfs!NpCreateNamedPipePrefix+68
BUCKET_ID: X64_0x50_Npfs!NpCreateNamedPipePrefix+68
Followup: MachineOwner
---------
-
Well there are quite a lot of memory pointers there so I would carry on and test the RAM with Memtest as I suggested earlier. Make sure that you test the modules one at a time for at least ten loops
-
No problems and thanks for your patience....ummm...I am going to run the memtest tonight.
For your info...Gigabyte just replied to my support request and sent me the latest bios...which is FC2...I have't seen or heard of that online as yet....so there again is another option to try...
-
No a new one on me. It is probably just the FC1 that they have tweaked to see if it will cure your problem. Anyway let us know how you get on with both ventures please.
-
Will try it soon and let you know. Thanks
More discussion on my issue here:
http://www.sevenforums.com/crashes-debugging/117643-x58a-ud3r-included-dump-system-files.html
...for anyone with the same...let's just say...challenges
-
I'm in the middle of testing ram. Tested all 3 strips for 6 passes.....2 errors detected. Have started testing individual strips...can report back in some hours.
Btw....Gigabyte sent me another bios...this one FC2.....if anyone wants to try it on their rig I can send it...
-
So basically you have some memory problems there and that is what is causing your troubles no doubt.You will need to RMA the whole set of RAM not just the failed one or two sticks. Let us know when you have finished testing.
-
Let me throw a spanner into the works here...
I just finished a 6hr47minute Ram testing session (which went through 7 full passes) with memtest....I tested all 3 sticks together using FC2 BIOS at 'optimised defaults' settings. I got ZERO errors.
Now before when I was testing the ram my BIOS settings were custom done by me...on the back of multiple suggestions by a lot of people from various forums. By the time I first started to test the Ram I had no idea of what mad settings I must have input....so these mad settings could skew the memtest (according to some).
A 6 hour 47 minute test...with 7 full passes and zero errors must be a good sign....right?
-
I just finished a 6hr47minute Ram testing session (which went through 7 full passes) with memtest....I tested all 3 sticks together using FC2 BIOS at 'optimised defaults' settings. I got ZERO errors.
You MUST test the modules seperately! That is why I said it to start with. Singularly, on their own, one at a time...
Now before when I was testing the ram my BIOS settings were custom done by me...on the back of multiple suggestions by a lot of people from various forums. By the time I first started to test the Ram I had no idea of what mad settings I must have input....so these mad settings could skew the memtest (according to some).
Well that make sense to put all the settings back to their defaults if you have been messing about with them. At least they should work at the deault values.
-
I thought you said to test them all together first and then if there was a problem to weed them out one by one and test them....
-
I would say so. Try downloading Memtest86+ and running it on the sticks one at a time for at least 10 loops each. If you get any errors then the memory is faulty.
Memtest86+ http://www.memtest.org/
or this version, updated for X58A http://www.memtest.org/download/beta/415b2/mt415.rar
This was my original advice but it doesn't matter now obviously just some confusion somewhere. Anyway just carry on and test them seperately.
-
Test them one at a time in each slot?
So stick 1 in slot a) b) c) stick 2 in slot a) b) c) stick 3 in slot a) b) c)?
btw...I just changed these settings in bios:
set ram to run at 1600 (because this is the ram's speed)
set ram/memory multi to 12
set the timings to the specified ram timings: 9 9 9 24
I think it's best to run the memtest when the bios is configured for the ram right?
-
No just test them one at a time in the first slot and yes I would agree with you on the configuration of the RAM.
-
Ok Dark Mantis I will do that...sometime this weekend.
Just to report...it is morning now....BSOD on cold boot
Plus all my temps in realtemp seem hotter.
I am sure last night with the same settings they all read in the mid to high 30's....now they are ranging 40-44
Anyway...I'll test the ram at these settings.....but I don;t like those temps....could bad ram contribute to higher temps?
-
The temperatures are not anything to worry about at that sort of level. I can't think hopw bad memory could make the temps increase but some funny things do happen.
-
So what happens if it is bad ram?
I go and buy new ram?
-
Some more info from my local forums:
I have the same board, rev 2.0, and noticed a bit of weirdness with my setup. However I am running the Geil 1600 @ 1333 and everything works fine.
After reading through the manual, the board doesn't actually support 1600 ram:
from page 10:
"Support for DDR3 2200/1333/1060/800 MHz memory modules." Try running the ram at a slower speed and see if:
a) the ram is recognised
b) the OS stops BSD'ing
Also this board is very picky about the RAM it likes. I have a mate who has built 2 of these machine and has had a lot of trouble with the RAM modules.
I thought maybe that's what the new bios's were doing....making the board support 1600....?
-
So what happens if it is bad ram?
I go and buy new ram?
If the memory fails you RMA it and get some replacements.
I thought maybe that's what the new bios's were doing....making the board support 1600....?
Well that is true I am sure but how well it works and if your memory is ok is another point.
-
I know you don't want to read oodles of stuff but there's some insights here maybe:
http://www.tomshardware.com/forum/270183-30-x58a-ud3r-1600-support
When I tested my ram at optimised in fc2....I think the ram speed was 1333....I had no errors.
Maybe my ram just is incapable of running stably at 1600
Furthermore....my cpu only supports up to 1066
http://ark.intel.com/Product.aspx?id=41447
-
Maybe my ram just is incapable of running stably at 1600
Furthermore....my cpu only supports up to 1066
Your CPU is capable of running much faster memory than 1066 but that is the JEDEC standard for the memory so that is what is quoted. If your memory was specified as 1600 speed then it should run at that speed if not RMA it.
-
I'm going to go back to FB bios...the last official bios...set to default and try the adjustements to get the ram to run at 1600.
In no way do I want to OC the machine....I just want the ram to run at spec.
I aim to use the PC as a recording studio...using Cakewalk Sonar...recording audio, mixing audio...that kind of thing
thanks again....I'm off to go back to defaults
When you flash bios that makes all values default doesn't it?
Here are some cpuz screens of my PC using FB bios (last known official) freshly flash, no tweaks:
(http://img.photobucket.com/albums/v704/frankgrimes/cpuzzzz.jpg)
What do you think of these values? Seems ram isn't running at 1600....so what values should I try to change in bios?
-
When you flash bios that makes all values default doesn't it?
When you flash your BIOS back to FB as planned on the QFlash main page there is the option to clear the DMI settings so use it (top option I think) By default it is enabled as it says Keep DMI Settings so you need to select disable and then carry on and flash the BIOS as normal.
-
I didn't see that option...I will look again.
By the way....if we start from defaults here and try to tweak bios to run my ram at spec.....and it DOESN'T work...then it is almost a certainty that there is a problem with the ram modules (most likely) or the board (maybe) right?
-
It is a little more complex than that but that would be the inference. Do the modules have a XMP attached?
-
No...these modules don;t have XMP.
And here is the screen shot of cpuz having flashed bios AND cleared VMI
(http://img.photobucket.com/albums/v704/frankgrimes/cupuzzzzzzzzzzzzz.jpg)
-
Can you post a pic of your SPD tab?
-
Here you go...
(http://img.photobucket.com/albums/v704/frankgrimes/Image1-5.jpg)
Oops...it's a bit big...what do you make of it?
-
Right well your RAM will run at 1333 which is JEDEC#4 settings as long as it isn't faulty.
-
As an experiment to see if I could make it run at 1600....
... from default bios settings....to get my ram to run at spec (1600) I changed to these settings in bios:
memory multi - x12
uncore - x25
ram voltage - 1.66
timings 9 9 9 24/ command rate 1
qpi/ vtt - 1.315v
This is my cpuz:
(http://img.photobucket.com/albums/v704/frankgrimes/Image1-6.jpg)
The ram looks like it is running at the right speed now...but the 'Clocks core speed' is 1598.9mhz......shouldn't it be running at 2.8ghz/ 2800mhz?
-
It should be changing all the time depending on load. If it is in quiet mode then it will be down to 12x. It is recognising the CPU correctly as 2.8Ghz
-
wtf???????????
-
I take it that you didn't understand what I was talking about from your previous post. The BIOS power saving modes regulate the processors speed etc depending on what is called for. EIST (speedstep) etc cuts the CPU power back when it is not being used heavilly and boosts it when it is doing a lot of work.
-
So I wanna cut that?
Sorry I'm pretty drunk right now....but I'm trying to keep up
-
No need to do anything unless you want to overclock your system and then you have to set everything manually. Just have another drink and enjoy life.
-
I dont want to OC it
-
The settings came with an armed guard
-
Nice one! I agree with you in general, I prefer not to overclock as I hold reliability over speed any day.
-
If I buy new ram do you think I should buy 1600 again?
-
btw guys.....If you HAD to go with your gut instincts on this....would you say I have bad ram?
and one last thing:
If I buy new ram....what bios should I use? Last official one?
Would I just install the ram physically and the bios will do the rest?
Will I have to go back to bios for my new ram to adjust its settings?
-
By the way.........I can run this PC at cpu spec speed (all this is shown in CPUZ) and at 1600 spec ram speed..........it just WONT COLD BOOT
So what do I do? Is there one tiny setting in bios that needs to go from .01 to .02?
-
Gut instincts are ok in some circumstances but can cost you a lot of dollars if they are wrong ;) Always better to do proper testing and then you are more sure that what you are doing is right. I think it is quite likely that it is a memory problem but I could be wrong and if you want to gamble on that feel free. I would prefer to do the tests I suggested (Memtest86+) and check 100%.
-
Yep. I have time tonight. I will do the tests one module at a time....but at what bios settings?
Should I set bios so hardware runs at spec?
btw....Just cold booted (bios running hardware at spec) got BSOD:
Stop 0x0000000A (plus some other values I can type in if you think it's relevant)
Anyway...will test ram soon
-
I would try running the memory at the recommended settings to start with as that is what they were sold for and see what happens. If you start getting faults on each module the try running them at 1333 instead. Thing is they should run at 1600 so if they don't then they are faulty and you can return them but it would be best to know if they run at 1333 as well.
Microsoft think that the error message maybe to do with a bad or incompatible driver so you could always check that as well.
-
Hi guys,
I'm having the exact same issue with the same motherboard. I also have a i7-930 but have different RAM.
The RAM I bought was
OCZ DDR3 PC3-16000 / 2000 MHz /Gold Edition / Triple Channel Kit / 6GB / CL 10-10-10-30 / 1.65v
http://www.ocztechnology.com/products/memory/ocz_pc3_16000_gold_low_voltage_triple_channel
I bought this RAM because it was on the office gigabyte supported list for the board but I've just checked now and the supported OCZ 2000Mhz model number has changed ... I'll see if I can find the old supported list that I had downloaded.
I've been on the OCZ forum to get the right settings for the RAM (VTT/QPI = 1.35) and also tried running the RAM at 2000Mhz but I got Memtest errors in 5 seconds. So I dropped the RAM down to 1600 (133 x 12) and the memory passed with 9 hours Memtest but only on second boot.
http://www.ocztechnologyforum.com/forum/showthread.php?79208
I booted last night straight into Windows from cold and ran Prime95 and it failed on 7 of the 8 workers in 5 seconds. I then rebooted and I have been running a Prime95 64 bit Blend test for 15 hours now and have no errors.
I don't quite understand why the motherboard can run fine on second boot but not on booting from cold.
Based on reading all the posts here - the fact that the RAM passes on Memtest with all 3 sticks for 9 hours doesn't mean anything and should test them 1 by one? Should I try to get them working at the full 2000Mhz or just 1600 ? Is there any difference in performance of having my RAM at 2000Mhz by either doing 133 x 15 or 166 x 12 ? I'd rather keep my BCLK down to avoid OC my CPU and I'd like to keep temps low.
So - Memtest for X58 boards linked above - 1 stick at a time at factory recommended settings for 8 passes each?
Should I post up my CPU-Z screenshots also for the settings I have now?
-
I THINK you should memtest it individually at spec (recommended settings).....but I'm not sure.
I think you should post up whatever screenshots you want...maybe something will fall into place for someone reading this and the key will be found...
-
Did you have the same issues with the FA bios?
-
Hi notshy and welcome to the Gigabyte Forum.
Yes download and run Memtest86+ (preferably the beta version for X58 boards) on one module at a time for at least 10 loops each.Use the first slot for the memory testing.
To be honest unless you want to overclock above 4 Ghz then 2000Mhz RAM is pointless. As long as you can run it at 1600 Mhz then you are fine and you would never notice the difference in a real world scenario.
-
Hiya,
I'm running OSX on my machine and it was recommended to me to put the BIOS to FB for greater stability in OSX, so I was only running FA for 1 week or so.
Thanks for the welcome!
I will stop my Prime95 running now as 18 hours and no errors I think means that things are OK for second boot. I just have this issue with cold boot but will go and have another go with my BIOS settings - I'll post up here what my settings are using the template and also get my signature all sorted with my hardware.
I'll get some screen shots of CPUZ up here too! Good job it's a saturday - I get the feeling this could take a while.
Do you think that it could be something to do with the second boot loading a different BIOS (the back up one) rather than FB? How do you know when the back up BIOS kicks in? I've realised that when I flashed my main bios is used @Bios which I shouldn't have done and I'm guessing that wouldn't have flashed my back up BIOS.
I'm off to try loading FB to both main BIOS and back up ... write down all my current BIOS settings and my hardware and try some testing.
I'll update my Memtest boot USB to that new version and try 1 pass on all 3 and 1 pass on each stick first - then post up the findings. 8 passes will take a while to do ....... but that will be next!
-
Can I offer a summary?
Ok thanks...where do I begin!? At the beginning.
Some preliminaries (my PC now):
OS Windows 7 Home Premium 64bit
CPU i7 930 2.8g
Motherboard x58A-Ud3R rev2.0 FC2 (FC2 is the latest beta BIOS, sent to me personally by Gigabyte)
Memory 6gig ADATA DDR3 1600
Graphics Card HIS ETI pcie HD5670
Sound Card Presonus Firebox
Monitor(s) Displays 19" LG Flatron
PSU Cooler Master 700W Silent Pro
Case Antec
Cooling Zalman CPU Cooler CNPS10x-Quiet
Hard Drives 2x1TB Seagate Sata2 7200
So two weeks ago it was time to buy a new PC. The last one I had I built in 2005. I assembled components for what I thought would be a powerful system for recording audio and mixing audio. These were the components on my list:
i7-930
Gigabyte GA-X58A-UD3R Rev2.0
6 GB (2 x 3 GB) Mushkin Enhanced Blackline 8-8-8-24 DDR3 1600 RAM
Zalman CNPS10X Quiet CPU Cooler
HIS H465PS1GH Radeon HD 4650 fanless Video Card (I did not end up getting this card. I got the one listed above)
(2) Samsung F3 500 GB Hard Drives
Pioneer DVD-RW with Lightscribe
Cooler Master Silent Pro M700 PSU
Antec Solo Case
I showed this list to my friend (quite good with computers) and he suggested that the ram was not gettable...so recommended I get this ram:
A-DATA AX3U DDR3 - 1600g (9) 2G9-1G 2Gx16
A70-090131 Gaming Series
Voltage: 1.55-1.75v
CL: 9-9-9-24
Here's some pictures of one of the modules:
(http://img.photobucket.com/albums/v704/frankgrimes/Ram3.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Ram4.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Ram2.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Ram1.jpg)
Ok...I came home and assembled the components carefully. In the back of my mind I kind of suspected there might be some teething problems especially considering my very low level knowledge of BIOS and RAM configurations. I hoped that the default BIOS configurations would be enough to drive my hardware to the best of its ability...to its spec. Anyway, the build was successful. The OS installed nicely and the PC booted up first go. I was pretty happy. I used the computer normally for 1 week. I installed some software...the usual things. Then after about a week I got curious...I wanted to find some apps to look under the hood. I started using CPUZ, realtemp and generally looking in Task Manager at things like Performance and Resource Monitor.
The first suspect thing I noticed was that not all of my RAM was being recognised. I had 3x2g modules in there but only one was being recognised. I also noticed when looking in Task Manager/ Resource Monitor/ Memory/ Hardware Reserved that 4096mb were allocated to 'Hardware Reserve'. This didn't sound right so I googled it. I found out that typically the Hardware Reserved is value is more like 10-60mb! So...I googled these problems and found out that the fix was commonly found to be a BIOS update. I went to the Gigabyte site and downloaded the newest official BIOS called FB. I flashed BIOS (from within BIOS) and rebooted. It was successful....all RAM modules showed up and my Hardware Reserved value was 2mb! I thought I was in the clear.
So I shut down the PC and went to work. In the afternoon I came home and turned my computer on....failure. I did not get any specific actual blue screen....the PC just keep cycling. It would reach the Windows loading screen and reboot itself. I was pretty worried! So anyway all I could do was turn it off. All I could think to do was to disconnect the HD cables (both the power and sata cables). I plugged them back in again and rebooted...and it worked. Then for a while as I restarted sometimes it would boot, other times not. That was maybe a week ago. Every cold boot for a week has failed. Eventually the PC boots. Once it's booted it seems to run fine. It's fast and responsive...but using the utilities like CPUZ and realtemp...I knew that there were problems.
For starters...it seemed that the RAM was not running at 1600. It also seemed that the CPU was not running to it's potential. That's when I started looking on forums to find an answer to the cold boot issues and to the RAM/ CPU issues. I opened up the hugest can of computing worms I've ever seen. There's people out there with this x58A-UD3R board in all sorts of trouble. I followed all kinds of advice...I used BIOS versions FB, FC1, FC2...I altered BIOS settings at will. dRam values, qpi/vtt, memory timings, uncore values, memory multi values. My aim was to get the RAM to run at spec and the CPU to do the same. Nothing I tried worked. The PC continued to fail on cold boots. Sometimes an actual blue screen would show...other times not. In altering settings in BIOS it seems that I was able to get the PC to run at spec. The CPU reported something like 2900mhz...slightly above the 2.8 spec. The RAM also ran at 1600. But the PC failed on cold boots every time.
I never went back to the initial BIOS FA to check that.
Before I forget...some info about my RAM...and the compatibility list:
RAM
http://oc.adata.com.tw/product-series.asp?sid=02
Compatibility List
http://download.gigabyte.asia/FileList/Memory/mb_memory_ga-x58a-ud3r_v2.0.pdf
Ok...so I will show you my FC2 BIOS settings as they are now and with the PC idle. Also I'll post some images of CPUZ and realtemp.
These are in no real order...but they should cover pretty much all the main sections and subsections of my BIOS:
(http://img.photobucket.com/albums/v704/frankgrimes/Bios17.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios16.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios15.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios14.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios13.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios12.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios11.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios10.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios4.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios9.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios8.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios7.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios6.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios5.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios3.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios2.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/Bios1.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/cpuzidle.jpg)
(http://img.photobucket.com/albums/v704/frankgrimes/tempsidle.jpg)
Well...that is about at...can you please have a look...and if there is any other info you need or you think would be helpful, let me know
thanks very much :P
-
Well the first thing that I noticed on checking your memory on the QVLs it doesn't appear on either one.
The Gigabyte QVL lists this as the nearest:
AET16C2 2GB A-DATA AX3U1600GB2G9-AG DS v 6PCS
and the A-DATA QVL lists the GA-X58-UD3R but not your board. Similar but not the same.
You would have had less trouble if you had made sure that the memory had been tested as compatible. That is not to say that it cannot be persuaded to work with your board but it is more trouble getting the settings right.
-
I've just had a look in EastTune6 > Tuner > Advanced > Voltage I
And seen that my
QPI/VTT power on 1.175v target = 1.355V
DRAM Voltage power on 1.3v target = 1.64V
I turned up my QPI/VTT and DRAM voltage upon recommendation from the OCZ forum guys however it looks like that voltage isn't being applied.
Is this important at all?
-
I've just had a look in EastTune6 > Tuner > Advanced > Voltage I
And seen that my
QPI/VTT power on 1.175v target = 1.355V
DRAM Voltage power on 1.3v target = 1.64V
I turned up my QPI/VTT and DRAM voltage upon recommendation from the OCZ forum guys however it looks like that voltage isn't being applied.
Why are you using this utility when it can all be done from the BIOS? Personally I am not keen on any of these programs as they usually bring more trouble than they save.
-
Sorry - I'm not using it to change the voltages at all - I'm just using it to read what the current voltages are that are being applied.
The Target voltages are the ones that I set in my BIOS - I'm not changing those settings at all.
What I thought it was showing was that those voltages that I set in my BIOS are not being applied!
-
Oh I see. Sorry I wasn't having a dig just mentioning the fact that I don't like those types of program.
That is one reason I don't like them because I find they are not always trustworthy. I would be inclined to go with the BIOS settings if you are sure they are entered right. ;)
-
Well the first thing that I noticed on checking your memory on the QVLs it doesn't appear on either one.
The Gigabyte QVL lists this as the nearest:
AET16C2 2GB A-DATA AX3U1600GB2G9-AG DS v 6PCS
and the A-DATA QVL lists the GA-X58-UD3R but not your board. Similar but not the same.
You would have had less trouble if you had made sure that the memory had been tested as compatible. That is not to say that it cannot be persuaded to work with your board but it is more trouble getting the settings right.
Those compatibility sheets are fairly....loose. Read about it here:
http://www.tomshardware.com/forum/274399-30-memory-part-evaluation-selection
-
That is why I said that it might still work but you would have to play around a lot with the settings probably.
-
Agreed....we'll see :o
-
The trouble is it can be a bit of a minefield. ;)
-
When Gigabyte lists a particular DDR3-1600 memory as compatible with a given motherboard, are they even saying it's compatible at 1600, or only that it's compatible at speed it comes up at with default settings (e.g. 1066)?
-
They are saying that it has been tested and passed at that speed. That's why on the QVL there are different speeds listed in sections.
-
Still no joy - tried BIOS FC2 and didn't fix the problem.
Going back to FB
???
-
The spec sheets are ambiguous and misleading at best.
I'm going to exchange the 1600 Corsair Ram I bought yesterday for 1066 ram.
That's the only ram supported on official specs by BOTH the board and the CPU
.....but the only 1066 ram on the compat sheet that is of any note (in terms of manufacturer) is:
Kingston KVR1066D3N7/2G
And besides.............SO MANY people ARE getting their x58A-UD3r boards to work with 1600 ram
-
The spec sheets are ambiguous and misleading at best.
I'm going to exchange the 1600 Corsair Ram I bought yesterday for 1066 ram.
That's the only ram supported on official specs by BOTH the board and the CPU
.....but the only 1066 ram on the compat sheet that is of any note (in terms of manufacturer) is:
Kingston KVR1066D3N7/2G
And besides.............SO MANY people ARE getting their x58A-UD3r boards to work with 1600 ram
You really shouldn't be having a problem getting 1600 Mhz RAM to run as long as it is on the QVL. Is the Corsair the Dominators part number TR3X3G1600C8D?
-
Ladies and gentlemen...boys and girls...I would like to announce...
SUCCESS!!!!!!!!!!!!!!!!!!
Ok...I'm just joking about my excitement levels....but I can report as follows:
- My first cold boot total success in over a week.
How did it happen?
- I took out the old ADATA ram (which didn't feature XMP)
- I installed new 1600 Corsair Ram...which DOES support XMP
- I set XMP in BIOS to profile 1...
done like a dinner
I am not considering myself out of the woods yet...I will be closely monitoring what goes on. But this is the best news I've had all week. My PC issues have been sucking my will to live!
All measurements are reading at spec. Everything appears normal.
I'd like to thank everyone...especially Dark Mantis for his help...and well...what can say...ram with no XMP feature is dangerous to configure for x58/ i7 rigs.
I'll keep you all posted.
-
Well done in getting it sorted, think your issue was more of a compatabilty one. Now just e-bay that adata stuff and recoup some funds :D
-
SUCCESS!!!!!!!!!!!!!!!!!!
How did it happen?
- I took out the old ADATA ram (which didn't feature XMP)
- I installed new 1600 Corsair Ram...which DOES support XMP
- I set XMP in BIOS to profile 1...
All measurements are reading at spec. Everything appears normal.
I'd like to thank everyone...especially Dark Mantis for his help...and well...what can say...ram with no XMP feature is dangerous to configure for x58/ i7 rigs.
I am really pleased for you as I know how draining it can be having problems that just won't be fixed. Sometimes it just makes sense to cut your losses and buy what is needed. As Fatman says you can always sell the old stuff on Ebay. ;)
-
Yep...and I heard that there is a strong possibility that my ADATA ram was not intended for x58 chipsets...so maybe it is useful for someone else in some other capacity...so yeah I'll try to sell it.
Did you know initially on my RAM buy list I had some Mushkin modules....they were guaranteed to work with my hardware. But I asked a friend here in Hong Kong (I'm from Australia, working in HK) to have a look at my proposed rig. He right away crossed out the Mushkin ram and told me he would find a replacement module set. He suggested the ADATA I have been struggling with. Mushkin ram is not common in HK. ADATA is everywhere.
It's not his fault. So when you think about it my rig was sabotaged from day 1. It was a tragedy waiting to happen...like the Titanic.
I have another question about CPUz....on the 'Clocks/ Core Speed' value...should it display your total possible gig for your cpu (ie in my case 2.8g)...or does it show current usage only...(e.g. idle)
thanks again
-
As you say you had checked the specification out beforehand but then it was changed. A lot of heartache can be avoided by good information research in the beginning.
CPU-Z... It should show the full speed of the CPU in the Specification box and then the actuasl speed it is running at the moment in the Core Speed box.
-
Ok...all's well then. So far so good....not counting my chickens though
Yes....because I researched the specs for this PC for a while before I got my initial list. I showed it to my friend...who works in computers...and he got it wrong on the ram. And that was the kicker right there.
I didn't know enough to question him and I didn't really bother to look into that ram he specified. On top of that...he never wrote down a specific ram...he just wrote down ADATA 1600 2gx3. It was when I went to buy it that the clerk came back with whatever module set he came back with...and there you have it.
Careless I suppose
-
Right ..... so the answer is XMP Corsair 1600 i7 RAM?
What would anyone suggest doing with the fact that the reason I bought the RAM was because it WAS on the suuported memory list and has now been removed ..... ???
-
Well if it was on the supported list...maybe it's faulty...or maybe there is still more tweaking you have to do.
Does XMP show in your BIOS?
-
Right ..... so the answer is XMP Corsair 1600 i7 RAM?
What would anyone suggest doing with the fact that the reason I bought the RAM was because it WAS on the suuported memory list and has now been removed ..... ???
Yes I have had that happen to me in the past. I sent it back to the retailer and exchanged it for some that was. I am using the Corsair Dominator 1600 with XMP and had no problems whatsoever on my board GA-X58A-UD7. I do think that it is bad form on the behalf of the manufacturer though as people make purchasing decisions on the QVL listing recommendations.
-
Hmmmmmm
Worth an email to Gigabyte at all? This is a tad frustrating !!!
I will also contact the retailer today ...
-
How long have you had the memory and when did they remove it from the QVL?
-
Hi "Hello People", I suggest you do not celebrate too early... I have been battling with the same issues you have for the last 3 weeks with no joy >:(
Like yourself I am a Cakewalk Sonar user and was intending to use this mother board for audio processing. I was also planning on NOT overclocking and running the memory at the default 1066 (as specified for the i7 950).
My system setup is as follows:
CPU - Intel i7 950
Mobo - Gigabyte GA-X58A-UDR3 rev2
RAM - Corsair 6 GB kit TR3X6G1600C9 (which is 3x CM3X2G1600C9)
System Hard Disk - Western Digital WD3000HLFS Veloraptor 300 GB
Data Hard Disk - 2x Western Digitial WD50000AAKS Caviar Blue 500 GB (configured as RAID 1 mirror to store audio data)
Graphics - 2x Gigabyte GV-R455D3-512I (ATI HD 4550 Silent)
Cooler - Noctua NH-U9B SE2
OS - Windows 7 Home Premium 64-bit
Here is the history of what I have done:
1. Built the system with shipped bios FA and default bios settings. This appeared to run fine for a week while I was sorting out the device drivers and installing all my software and testing out windows compatibility issues doing a dress rehearsal build. Did not have a single BSOD during this phase.
2. Started a completely new installation with all the right drivers and software apps. It was at this point in time I noticed that the use-able memory varied between 2, 4 or 6 GB. I then flashed the bios to FB. This is when my cold boot BSOD issues started.
I have tried all the things you have:
a. Ran Memtest86 on each DIMM separately and all together - have never had a single error reported. Last run of all three DIMMs in for 4 passes running for 3.5 hours - still no errors. The memory is on Corsair's recommended list for this motherboard.
b. Checked for bent pins on the LG1366 and found one. In the process of photographing it the fabric strap of my camera feel onto the socket and got snared on it. In the process of freeing it I bent another pin! WORD OF WARNING - if photographing the CPU socket make sure you remove your camera strap first and keep everything clear of the pins. I have managed to straighten both pins. There appear to be no issues with this now.
c. Tried using XMP profile1 - no success
d. manual settings at 1066 MHz, DRAM 1.65 v and QT/VTT voltages of 1.315v - no success
e. I have tried both optimised and fail-safe bios settings.
The symptoms are the same as yours: I always get a memory related BSOD on cold booting (if PC has been switched off for several hours/overnight). Once it has been running for about 15-30 mins the BSODs stop and the system stabilises and then runs fine for several hours OK. No manner of BIOS settings seems to make any difference.
3. I then tried flashing to the FC1 beta bios. This resulted in the graphics card in PCI-Express x16-2 going either blank or completely blue! Also the OS starting grinding to a halt and was useable. There were the odd BSODs.
4. I flashed the BIOS back to FA and retested. No BSODs, but useable RAM varies.
5. I then flashed the BIOS to FB and retested. The BSODs came back!! Tried all manner of settings with no joy.
I submitted a ticket to Gigabyte support on Thursday, but they have not even read the message yet!
I have been using Gigabyte products for over 15 years and am very disappointed by the quality of this motherboard.
I am convinced that this is an issue with the BIOS and not the memory. How can all three bios FA, FB and FC1 all behave so differently?
Dark Mantis do you have any further suggestions?
-
Right so back to square one?
I bought the board + ram over 1 month ago which is over the RMA with the store and have a minor issue that it was bought for me as a present so I might have difficulty getting in touch with the store direct.
I'll maybe hold tight for the moment and keep my machine in sleep mode when I'm not using it?
-
FunkyErn
Dark Mantis do you have any further suggestions?
I agree with you in that I think it is down to a badly written BIOS routine
I submitted a ticket to Gigabyte support on Thursday, but they have not even read the message yet!
I am afraid that from past experience you will be lucky to get an answer before the middle of next week at the earliest. When you do it probably won't be anything to do with your question so you will need to follow it up with another question and hopefully you will get a proper answer in the end.
-
notshy
What would anyone suggest doing with the fact that the reason I bought the RAM was because it WAS on the suuported memory list and has now been removed .....Worth an email to Gigabyte at all? This is a tad frustrating !!!
I that case I would certainly complain about the fact that the QVL was changed, whether it will get you far is another matter, but it is worth making a noise about otherwise nothing ever gets done.
-
ram with no XMP feature is dangerous to configure for x58/ i7 rigs.
Sometimes, though, it does work ok. In my case there was little difficulty getting GA-X58A-UD3R rev2 (FB) working with i7-950 (no OC) and 6GB of OCZ3G1600LV6GK (on the QVL), even though that RAM has no XMP.
The system has worked perfectly with memory speed of 1066 (default) and 1600. The only glitch with the latter was that after I configured the BIOS RAM settings to x12(1600) 8-8-8-24/88 1.64v, I found that the yellow CPU-voltage LED turned on (not just the green). At Lsdmeasap's suggestion here, I then installed EasyTune and examined the QPI/Vtt target, which was 1.435v (normal is 1.175v; it was still set to Auto in the BIOS). The Intel i7-950 spec warns of possible permanent damage if Vtt exceeds the absolute max of 1.35v. So I set Vtt in the BIOS to 1.335v, which turned off the yellow LED, and everything still works great.
Anyway, congratulations on sorting things out!
-
Mobo - Gigabyte GA-X58A-UDR3 rev2
RAM - Corsair 6 GB kit TR3X6G1600C9 (which is 3x CM3X2G1600C9)
That RAM isn't on Gigabyte's QVL for the GA-X58A-UD3R (I assume you meant UD3R, unless there's a UDR3 I don't know about). If the motherboard were advertised to support DDR3-1600 memory, then any decent brand should suffice. But since DDR3-1600 is not a supported category, particular brands may have quirks that are incompatible with the board, even though those brands may meet the DDR3-1600 spec. So it may help to play it safe and stick to Gigabyte's QVL.
b. Checked for bent pins on the LG1366 and found one. In the process of photographing it the fabric strap of my camera feel onto the socket and got snared on it. In the process of freeing it I bent another pin!
Is is possible that the first bent pin caused damage to the CPU while the system was running?
-
But since DDR3-1600 is not a supported category, particular brands may have quirks that are incompatible with the board, even though those brands may meet the DDR3-1600 spec. So it may help to play it safe and stick to Gigabyte's QVL.
My thoughts exactly and that is why I am always trying to drum into people the importance of using memory on the QVL ( whether Gigabyte's or the memory manufacturer's). ;)
-
Hi "Hello People", I suggest you do not celebrate too early... I have been battling with the same issues you have for the last 3 weeks with no joy >:(
Like yourself I am a Cakewalk Sonar user and was intending to use this mother board for audio processing. I was also planning on NOT overclocking and running the memory at the default 1066 (as specified for the i7 950).
My system setup is as follows:
CPU - Intel i7 950
Mobo - Gigabyte GA-X58A-UDR3 rev2
RAM - Corsair 6 GB kit TR3X6G1600C9 (which is 3x CM3X2G1600C9)
System Hard Disk - Western Digital WD3000HLFS Veloraptor 300 GB
Data Hard Disk - 2x Western Digitial WD50000AAKS Caviar Blue 500 GB (configured as RAID 1 mirror to store audio data)
Graphics - 2x Gigabyte GV-R455D3-512I (ATI HD 4550 Silent)
Cooler - Noctua NH-U9B SE2
OS - Windows 7 Home Premium 64-bit
Here is the history of what I have done:
1. Built the system with shipped bios FA and default bios settings. This appeared to run fine for a week while I was sorting out the device drivers and installing all my software and testing out windows compatibility issues doing a dress rehearsal build. Did not have a single BSOD during this phase.
2. Started a completely new installation with all the right drivers and software apps. It was at this point in time I noticed that the use-able memory varied between 2, 4 or 6 GB. I then flashed the bios to FB. This is when my cold boot BSOD issues started.
I have tried all the things you have:
a. Ran Memtest86 on each DIMM separately and all together - have never had a single error reported. Last run of all three DIMMs in for 4 passes running for 3.5 hours - still no errors. The memory is on Corsair's recommended list for this motherboard.
b. Checked for bent pins on the LG1366 and found one. In the process of photographing it the fabric strap of my camera feel onto the socket and got snared on it. In the process of freeing it I bent another pin! WORD OF WARNING - if photographing the CPU socket make sure you remove your camera strap first and keep everything clear of the pins. I have managed to straighten both pins. There appear to be no issues with this now.
c. Tried using XMP profile1 - no success
d. manual settings at 1066 MHz, DRAM 1.65 v and QT/VTT voltages of 1.315v - no success
e. I have tried both optimised and fail-safe bios settings.
The symptoms are the same as yours: I always get a memory related BSOD on cold booting (if PC has been switched off for several hours/overnight). Once it has been running for about 15-30 mins the BSODs stop and the system stabilises and then runs fine for several hours OK. No manner of BIOS settings seems to make any difference.
3. I then tried flashing to the FC1 beta bios. This resulted in the graphics card in PCI-Express x16-2 going either blank or completely blue! Also the OS starting grinding to a halt and was useable. There were the odd BSODs.
4. I flashed the BIOS back to FA and retested. No BSODs, but useable RAM varies.
5. I then flashed the BIOS to FB and retested. The BSODs came back!! Tried all manner of settings with no joy.
I submitted a ticket to Gigabyte support on Thursday, but they have not even read the message yet!
I have been using Gigabyte products for over 15 years and am very disappointed by the quality of this motherboard.
I am convinced that this is an issue with the BIOS and not the memory. How can all three bios FA, FB and FC1 all behave so differently?
Dark Mantis do you have any further suggestions?
With all due respect...your history is slightly different from mine.
Where you state that XMP Profile 1 did not work...it did and is working for me....with the new ram I put in.
I never had any bent pins either
If there's another reason you think I shold not celebrate too early please let me know (btw...I am NOT celebrating too early)...
But my system has successfully cold booted 2 times now with FB BIOS...all values are on spec...everything is fine
Haha...a Sonar user too huh...it's a long way to the top if you wanna ram and roll
:)
-
Gary123 - Apologies a typo - it is UD3R. Also I am trying to run it at 1066 and not the full 1600. This does not make a difference. The question to ask is how come when running Memtest86 at either 1066 or 1600 the memory runs fine without any errors? It is only when Windows 7 is running does the system start to fail, but then only for the first 15-30 mins - after that it is stable. I really do not think it is the memory.
Re: bent pins - the CPU seems fine. When I switched back to bios FA - the system is stable with no BSODs so I do not think the issue is bent pins. If the CPU was damaged or pins still bent/damaged I would not expect changing bios to make any difference but it does. This leads me to think that it is a problem with the bios.
One other thing to maybe consider is the Noctua NH-9UB cooler - some other forum postings suggested reverting to the stock Intel cooler fixed similar problems. This did not make sense to me so I have not yet tried that. What does everyone think? Worth a try or not?
I have flashed to bios FC1 since the last post for one more try and using the XMP (set to 1600 just out of curiosity) - will let everyone know the results later on once the pc is completely cold. I think I had originally used @bios to try out FC1 - this was due to my 4GB Verbatim USB flash drive not being visible to QFlash. I have since bought a 2 GB SanDisk Cruzer blade and have now been using QFlash. I believe there have been some issues with @bios flashes in the past - maybe this was causing the graphics card problem when trying FC1?
Dark Mantis - the TR3X6G1600C9 is on the Corsair list for the GA-X58A-UD3R - I did check that before ordering the parts. http://www.corsair.com/configurator/product_results.aspx?id=1362102
Hello People - while our histories/experiences are not identical, there are strong similarities. The XMP profile 1 would kind of work for me, but only once the PC had been running for 15-30 mins. The cold boot issue tends to manifest itself overnight. I would suggest you see how it behaves over the next few days before cracking open the champagne. The BSODs did corrupt one of my hard disks and I am sure you do not want to lose any of your music compositions - hence why I recommend caution before you start using the machine for recording.
-
Funky...have a read of my last few posts.........I'm a long way from breaking out the Bollinger. And I clearly stated that.
XMP has been working flawlessley for me. Since I installed the new ram and set bios I have had 2 successful cold boots, each cold boot about 3.5 hours wait. I will be nervous in the morning for a cold boot though.
We'll see
-
FunkyErn
One other thing to maybe consider is the Noctua NH-9UB cooler - some other forum postings suggested reverting to the stock Intel cooler fixed similar problems. This did not make sense to me so I have not yet tried that. What does everyone think? Worth a try or not?
I can't see any correlation between the heat sink and the problem except for if it was caused by the CPU not seating properly or something and then moving it to replace the heatsink could make a difference, but I think it is unlikely. As I said earlier I think it is more likely a problem that is BIOS related.
Dark Mantis - the TR3X6G1600C9 is on the Corsair list for the GA-X58A-UD3R - I did check that before ordering the parts. http://www.corsair.com/configurator/product_results.aspx?id=1362102
Yes I know the Corsair memory is on the QVL. Nobody was disputing that fact.
-
Funky...have a read of my last few posts.........I'm a long way from breaking out the Bollinger. And I clearly stated that.
XMP has been working flawlessley for me. Since I installed the new ram and set bios I have had 2 successful cold boots, each cold boot about 3.5 hours wait. I will be nervous in the morning for a cold boot though.
Try putting the system in the fridge with the Bollinger and you can kill two birds with one stone.
-
If only I had some Bollinger....and a fridge...
-
I am trying to run it at 1066 and not the full 1600. This does not make a difference.
Ok, but if the board is not advertised to support DDR3-1600 modules in general, is it necessarily expected to support DDR3-1600 modules running at 1066? (I don't know whether DDR3-1600 memory is required, or advertised, to be backward compatible with DDR3-1066, although it does often seem to work that way.)
It's tricky to say what (if not incompatible memory) distinguishes your system from others that work properly. It could, as you suggest, be a problem with the FB BIOS, but not necessarily, since many of us use FB successfully. Possibly there is an interaction between different (but correct) BIOS versions and some other problem.
One other thing to maybe consider is the Noctua NH-9UB cooler - some other forum postings suggested reverting to the stock Intel cooler fixed similar problems. This did not make sense to me so I have not yet tried that.
Have you looked at your core temps while the system is under load?
-
What you have to take into account is manufacturing tolerances on every component that is used to make the motherboard. These tolerances can add up or cancel each other out and that is why no two boards behave exactly the same, the same as CPUs, memory or any other device.
-
Mmmm... this is all very strange and irritating....
I flashed FC1 bios with XMP enabled at 1600 and ran OK for 30 mins and then the OS just froze. So I have reverted back to the FB bios, loaded fail safe seetings and then enabled XMP profile1 at 1600. This has been booting fine (warm) and running without any BSODs - am just running a SiSoft Sandra burn in test on it. However, the true test is the cold boot from an overnight "rest".
Hello People - what model number is the Corsair 1600 XMP memory you are currently using? The TR3X3G1600C8D? Let us know how it goes in the morning.
Dark Mantis - I am inclined to agree with you on the question of the heatsink. It does not make sense. After reseating the CPU and replacing the cooler I took care that it was not too tightly attached incase that was flexing the board or socket in anyway. It makes sense that no two motherboards will be exactly identical.
Gary123 - As far as I am aware from what I have read about DDR3 the faster speed ones are backwardly compatible. The memory timings are different for each speed setting though. Regarding CPU temp - the average core temp is around 37-39 degrees centigrade. I believe this is acceptable.
I guess the acid test will be in the morning once the pcs have completely cooled down overnight. Fingers crossed...
-
Regarding CPU temp - the average core temp is around 37-39 degrees centigrade. I believe this is acceptable.
Yup, better than my temps anyway. :) With the memory at 1600, CoreTemp shows 37-40° at idle, 54-62° at 50% CPU load, and 68-71° when the temperatures level off during the Prime95 torture test. (i7-950, no OC, CoolerMaster Hyper 212+)
-
Yup, better than my temps anyway. :) With the memory at 1600, CoreTemp shows 37-40° at idle, 54-62° at 50% CPU load, and 68-71° when the temperatures level off during the Prime95 torture test. (i7-950, no OC, CoolerMaster Hyper 212+)
Maybe you could do with a little more cooling in your case or even just a better ballanced airflow.
-
Yup, better than my temps anyway. :) With the memory at 1600, CoreTemp shows 37-40° at idle, 54-62° at 50% CPU load, and 68-71° when the temperatures level off during the Prime95 torture test. (i7-950, no OC, CoolerMaster Hyper 212+)
Maybe you could do with a little more cooling in your case or even just a better ballanced airflow.
Perhaps, though it's a Gigabyte 3D Aurora--a large case with three 120mm fans (in addition to the CPU fan).
Am I correct to understand that my core temps, though higher than average, are still safely within specs? (During the Prime95 torture test, with 100% CPU use, the processor was still running at the turbo speed of 3.2 GHz, so the processor itself doesn't seem to think it's too hot.) Memtest and Prime95 haven't shown any errors, and the system has been completely stable so far.
-
Yes you seemed to stay within the saftey zone ok. It's just that you have to remember that if your system is nice and clean and everything working at optimum power it can only get worse. As dust etc builds up so does the temperatures. ;)
-
Yes you seemed to stay within the saftey zone ok. It's just that you have to remember that if your system is nice and clean and everything working at optimum power it can only get worse. As dust etc builds up so does the temperatures. ;)
Yup, I'll keep an eye on that. But for now, I'm happy to declare victory and stop spending time on this. Plus I don't want to keep tinkering until I eventually break something. :)
-
Funky I'm using Corsair CMX6GX3M3C1600C7 2gx3
By the way........just had my first successful morning cold boot in 1.5 weeks. That's 3 cold boot wins in total.
Still not counting chickens though.
Good luck everyone
-
Well it sounds hopeful now and you have to crack the Bollinger at some point! ;)
-
Hello People - Congratulations!! That must be a relief :)
Dark Mantis - my cold boot issues are still unresolved.
I ran Sisoft's burn in for 3-4 hours on Sunday without any issues on bios FB. Monday morning BSOD BCCode 1A on first boot after overnight cool down! I then decided to swap the Noctua cooler for the stock intel retail package one - I wanted to eliminate all options inspite of us both thinking this would not be the issue. Booted first time without any issues (of course it would now that is was warm), I then ran SiSoft's burn in for about 3 hours and no issues. However on first cold boot this morning the BSOD BCCode 1A stuck again as soon as I logged in to Windows. So I think we can now safely conclude that the cooler is not the issue. The problem manifests itself only for about 15 mins on cold booting from overnight. I do switch off my computer at the mains overnight - could this impact things?
I have now flashed the FC1 bios and will sit back and see what happens overnight. When I tried this previously Windows stopped responding after 30 mins. I have switched from using my wireless mouse and keyboard to my old wired ones to eliminate any other variables. Any idea where I can get the latest bios (FC2?) from?
Gary123 - the temps I quoted were at idle. While running the burn-in tests the core temps varied from about 40 at idle to 73 at peak load.
-
Hi FunkyErn
If you contact Hello People they have FC2 and you can get it off them http://forum.giga-byte.co.uk/index.php?action=pm;sa=send;u=5480
I still can't help feeling that it is something to do with the PSU. Try not turning the mains power off at night and see if it does indeed make any difference. There would only be residual power there but it may make a difference. Try not to change more than one thing at a time though otherwise you are introducing more variables into the equation.
-
What's your email funky? pm me
-
Hey...my PC crashes when I try to launch or uninstall Easy 6....I remember that it could have become corrupted during my 9 days of troubleshooting....a few days ago I remember trying to launch it and it crashing my computer.
Any known issues with Easy 6?
If I want to uninstall it, should I do it in safe mode or something?
thanks
-
If you take my advice you will uninstall it and leave it that way ;) No, I do understand some people like these free toy programs but to my way of thinking there are always better alternative ways of doing the same thing. Often as you have found out they come at a price. :-\
-
Yeah I don't want it at all. What's the best way to uninstall?
In statr menu I tried to click uninstall and the PC crashed hard and fast.
I'll try from control panel
....safe mode?
-
I would think(as I have never installed it ) that just the add/remove programs should do it in Control Panel.
-
Nope...and doesn't uninstall in safe mode either...I get these errors:
Open device failure!
Open driver handle failure!
Memory map failed!
Do you know anything about this?
Instant crash in normal boot...in safe mode the PC just hangs and I have to end task
ps....I mean Smart 6....not Easy 6
This is the 'Windows recovered from an unexpected shutdown' review:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: c4
BCP1: 00000000000000F6
BCP2: 00000000000002F4
BCP3: FFFFFA8007F8D060
BCP4: FFFFF8800812C809
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\101910-20576-01.dmp
C:\Users\matt\AppData\Local\Temp\WER-33555-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Should I maybe try to re-install it/ or repair install it...and then uninstall?
-
Maybe try something like Revo Uninstaller Pro. I use this program and it is extremely good. cleans every last bit of a program if you set it properly.
Just google for the download ;)
-
;)
I just tried that...didn't work...PC crashed hard.
But...I didn't fiddle with any settings in Revo...have any settings in mind I could try??
-
Not particularly just run the thorough scan to find everything. If that didn't work I think you are on dodgy ground as it looks like registry editing is going to be the only way to get rid of it. Trouble is that is always fraught with danger. If you are up to it you could try finding all the entries in the registry :-\
First I would do a search of the forum as I seem to remember someone else having this problem I just can't remember how it was resolved.
-
I searched google and this site came up...the guy fixed it with Revo...lol...
I'll search this forum...EDIT: Nothing much of interest came up in a forum search...
If I look around in registry....does deleting all the entries....uninstall it? Is it the equivalent?
I'm even more of a noob in registry than I am in bios!
-
In that case I wouldn't recommend it as there is no second chance if you delete the wrong thing.
Maybe if you re-install the program and then uninstall it with Revo?
-
When I put the disc in and tried to reinstall/ repair...instant crash.
I went into safe mode and used Revo...seems to have nuked it and that Green program thing from Gigabyte too.
Anyone know what these progs are (both Gigabyte entries in my install/ uninstall control panel list):
On_OFF Charge B10.0422.2
DES 2.0
What are they?
Are they needed?
EDIT: Ok I know what they are...and they don't seem too important
Hey...people pm'ing me for the FC2 bios.....it is at media fire...there should be a link on this forum somewhere...you can ask Lsdmeasap
-
On_OFF Charge B10.0422.2
DES 2.0
DES is Dynamic Energy Saver and does what it says on the tin.
On/Off charge is for charging iPads, Iphones etc even when the computer is turned off. It also increases the rate of charge.
-
Yeah I just got rid of them...although ONOFF could be useful I suppose
-
Oh yes for some people it could be very useful. ;)
-
If you take my advice you will uninstall it and leave it that way ;) No, I do understand some people like these free toy programs but to my way of thinking there are always better alternative ways of doing the same thing. Often as you have found out they come at a price. :-\
I find EasyTune6 useful and have never had a problem with it. I read about Smart6 and decided I'd be smart and not install it. From Gigabyte's description it sounds as if it interacts with (changes somehow) the BIOS. If I were have problems with BSOD's, I'd surely get rid of it. I had (have?) enough without it! From Gigabyte:
BIOS QuickBoot : Shorten boot up POST time !!!
There is nothing more frustrating than having to wait ages for your PC to boot.That is why GIGABYTE developed Smart Quickboot. Smart Quickboot speeds up the system boot-up process and shortens time it takes to enter the operating system. This is done in two ways. Part one is a BIOS QuickBoot. Normally, every time you boot up your PC, your BIOS checks your hardware to make sure everything is working properly. This takes time, as your system checks the memory, hard drives, etc. By enabling Smart QuickBoot, your BIOS will only run through the hardware scan once. If all your hardware checks out ok, the next time you boot, your PC will only scan the most critical components. This allows for a time saving of up to 3-5 seconds on the BIOS boot time alone.
The second part of Smart QuickBoot is OS QuickBoot. This utility allows you to power down your PC into a combination of Suspend Mode (S3) and Hibernate Mode (S4). By putting your PC into S3 and S4 mode is like putting your PC to sleep, allowing you to maintain your data, while at the same time, saving energy. When you power your PC back on, Smart QuickBoot will resume from Suspend Mode in a matter of seconds, rather than the time it takes to boot the OS. The great thing about OS QuickBoot is that your data is stored in both the memory thanks to the S3 state as well as being stored on your hard drive for the even deeper S4 state. This means that even if your PC is unplugged or you lose power, the next time when you boot your PC, it will resume from S4 automatically, using the data that was stored on the hard drive.
-
Yes I can understand your position and as I said some people will find them useful. However a few BIOS changes and you have done the same thing. Same with Windows. It can be made to start and in particular shut down quicker. It is handy for people who don't want to delve into the workings of their systems I suppose. ;)
-
FYI - after flashing to FC1 I left machine off for 7.hours and same cold boot issues of BCCode 50 and 1A. This is driving me nuts.
Dark Mantis - I agree with you that one should only change one variable at a time. I will power down the PC tonight and leave plugged in to the mains. I currently have all my gear powered via a Samson Powerbrite power conditioner (mainly to protect my audio gear). I will leave the PC plugged directly into the main socket over night and see what happens. I am not convinced this is issue as with bios FA it worked fine being disconnected overnight. I still suspect the bios. Still no reply from GTS! >:(
Hello People - I will pm you my email address. I will give FC2 a go. Regarding Smart 6 and Easy Tuner I only installed ET on my initial build to test them out along with all the variants of the drivers (audio and midi interfaces). I have uninstalled ET using the add/remove programs. I would suggest doing a completely clean build and reformatting the discs once the system has stabilised. This is what I intend to do as during the build/debug process one needs up installing and trying out all sorts of utilities - e.g. SMART and ET.
-
I am in total agreement with what you have just posted. Especially the end part . When everything is sorted it's best to do a clean install and get rid of all the rubbish before you start using your system properly.
-
The sooner the cold boot issue is sorted the better it is driving me mental
May even go back to FA to sort this and hope my memory doesnt start disappearing again
-
I must admit I come down on the side of the BIOS issue. I think that GGTS needs to get this addressed as soon as possible and the more people complain to them the quicker it will get done. :-\
-
It is handy for people who don't want to delve into the workings of their systems I suppose. ;)
Or for people who think the engineers and programmers at Gigabyte just might know a little more than they do. :)
-
It is handy for people who don't want to delve into the workings of their systems I suppose. ;)
Or for people who think the engineers and programmers at Gigabyte just might know a little more than they do. :)
I am not sure if they are even written by Gigabyte staff, more likely farmed out to outsdide contractors to write. ;)
-
You guys having the cold boot issues still...what kind of ram are you using? I ask because once I ditched that initial ADATA ram and started using other ram, my cold boot failures completely stopped. Maybe your ram is causing the problems. I have no idea why a PC would fail to cold boot but would operate normally once finally booted up...but my cold boot failures did stop once I got new ram. It's just a thought...maybe there's no use trying to bash a square peg into a round hole...it seems that's exactly what I was doing with my old ram.
-
Latest update...
Left PC plugged in to mains overnight with latest bios FC2 and.... still BSOD on cold start up this morning ??? I ran MemTest86 straight away and was getting 300+ errors in the first 5 secs!! I rebooted and set the DRAM v from 1.5v to 1.65v and reran - suddenly no errors. Switched back to 1.5v from 1.65v and still no errors. It is not the DRAM voltage - I am running at 1066 which according to the SPD spec runs at 1.5v.
I am stumped... it has to be either the memory or the motherboard. This is bizarre. Is there anyone else out there using TR3X6G1600C9 with the GA-X58A-UD3R rev 2.0?
Next steps:
a) RMA the memory?
b) RMA the motherboard?
c) RMA both?
I am inclined to think it is the motherboard/bios - the reason for this is that the memory works fine with bios FA. I will reflash to FA and leave off overnight and see if thiis confirms it.
Dark Mantis - what do you suggest? I still have not had a reply from Gigabyte.
-
I would be inclined to RMA the memory mainly due to the time factor. I am sure it will take less time to have the memory replaced than to have the motherboard checked/ repaired/ replaced. Don't forget it could be the CPU itself as now the memory controller is part of the CPU die.
-
Well I have thrown in the towel and RMA'd both the board and RAM back to the supplier. I have wasted over 3 weeks trying to get this to work and now have to wait another 10 working days. And as sod's law would have it GTS finally respond after I am arranged the RMA and dismantled the computer and packed up the bits. I have passed their suggestions on to the supplier's tech support.
I almost ordered an ASUS P6X58D-E today - it has a more extensive list of memory on the QVL and actually includes my memory model! The only thing that stopped me is that it uses a VIA chipset for its firewire vs the TI one on the UD3R. This is an issue for my audio firewire interface. I might reconsider it in a couple of weeks time. Any idea what the ASUS P6X58D-E is like? Is it as problematic as this board?
A word of warning to people out there using the stock Intel cooler - remove the thermal paste before you attach and check there are no defects hidden under it! And then use a quality thermal paste to apply. While dismantling the board today I discovered that there was a nick in the surface of the copper cooler core which has slightly dented my processor heatsink cover!!! This defect was hidden by the thermal paste. Boy was I £"^$*&"^*&$()!!! I might well now need to RMA that back as well...
Dark Mantis - that is a good point about it might possibly being the processor as well. The memory controller is on it!! My money is still on a poor quality bios, or way too tight specs required of the mother board. We are pushing the limits of engineering with these boards, and the wealth of complex features on them. I actually write software for a living so I know a thing or two about increasing complexity bringing about increased likelihood of bugs.
Will keep everyone informed of how the saga progresses...
-
Good luck funky....yeah...funny old board this one...lots of issues. From time to time I swear I can hear that high pitched digital whining that heaps of others have been complaining about
::)
-
Good luck funky....yeah...funny old board this one...lots of issues. From time to time I swear I can hear that high pitched digital whining that heaps of others have been complaining about
::)
Nice quick fix for that is to Disable C1E and maybe EIST as well in the BIOS. Not perfect but a good workaround for now.
-
If I disable eist wont my cpu motor at full spec all the time? The temps will be up too
-
Yes this is the downside to the fix. Just try disabling C1E first you may not need to disable EIST also. ;)
-
It might be my ears...most of the time I hear nothing...sometimes I think it's starting to whine quietly. Anyway...I think it's ok
-
It could be just a fan bearing starting to whine a little. You will soon know if it becomes more pronounced. ;)
-
Hello people - sorry to hear about the latest development with the whining noise. Have you checked out the other thread "Re: GA-X58A-UD3R electrical noises"?
Dark Mantis - latest update - after packing up the motherboard last night and discovering the scratch/dent on the processor IHS from the defective Intel cooler, I had another look at the processor this morning. Looking at the underside of the processor, one thing sprung out and struck me, most of the copper pads had marks pretty much dead centre from the pins, however one entire quadrant of the pads, all had marks close to or on the edges of the pads, some of them possibly even off the pads. Plus there were about 5 pads with no marks on them at all. This has got me thinking there might be an issue with the 1366 sockets. If the pins are not correctly aligned with the processor or move around when heated up, this might explain the issues some of us are having.
These appear to be manufactured by FoxConn - would this be the same company recently in the news for over working its workers? Has anyone else reported any issues with pin alignment - other than bent pins?
-
You are quite right about the marks on the lands(the copper plates) on the reverse of the CPU. They should all be marked fairly centrally and is another test we use to check the pins if unsure.If any are unmarked then that is a problem certainly. If there is a whole area of unmaked lands then it would suggest to me that the socket was not level, maybe not inserted evenly on manufacture. It would definitely need more close inspection. Most of the sockets used by most motherboard companies are made by FoxConn.
-
There was only one cluster of 3 unmarked pads. One whole quadrant (further away) had misaligned pins. Maybe I just got a socket from a bad batch or there was an issue soldering the socket onto the board? Courier has picked up the board and RAM earlier today - now I have to sit back and wait...
Q: what tools do tech support use to verify S1366 pin alignments? And can these tools realign the pins?
-
To be perfectly honest I don't know what tools they use, I have never been to the service centre. We are only lowly users like yourself and not invited into the holy of holys. :o
Most techs use the same tools as everyone else to be fair. It's not the tools it's knowing what to do with them that counts ;) They can straighten pins exactly the same way we would...very carefully! They also have the option of replacing the socket.
-
Hello people - sorry to hear about the latest development with the whining noise. Have you checked out the other thread "Re: GA-X58A-UD3R electrical noises"?
Yeah sure, I read that. I think I'm fooling myself a little bit though...I haven't heard any suspicious noise for a fair while now. Seems ok. Almost time to put the side panel back on and get on with recording music.
-
Yes if you listen hard and long enough you can fool yourself into hearing anything ;)
-
...there's these voices in my head...telling me to burn things....
-
Oh that's ok then as mine say the same so they must be right ;D
-
Latest update...
Left PC plugged in to mains overnight with latest bios FC2 and.... still BSOD on cold start up this morning ??? I ran MemTest86 straight away and was getting 300+ errors in the first 5 secs!! I rebooted and set the DRAM v from 1.5v to 1.65v and reran - suddenly no errors. Switched back to 1.5v from 1.65v and still no errors. It is not the DRAM voltage - I am running at 1066 which according to the SPD spec runs at 1.5v.
I am stumped... it has to be either the memory or the motherboard. This is bizarre. Is there anyone else out there using TR3X6G1600C9 with the GA-X58A-UD3R rev 2.0?
Next steps:
a) RMA the memory?
b) RMA the motherboard?
c) RMA both?
I am inclined to think it is the motherboard/bios - the reason for this is that the memory works fine with bios FA. I will reflash to FA and leave off overnight and see if thiis confirms it.
Dark Mantis - what do you suggest? I still have not had a reply from Gigabyte.
Google has sent me this way as I have almost exactly the same issues that you do.
My specs are as follows
OS Windows 7 Ultimate x64
CPU Intel Core i7 920 D0 Quad Core CPU 2.66GHz
Motherboard Gigabyte GA-X58A-UD3R
Memory Corsair TR3X6G1333C9
Graphics Card XFX GeForce 9800 GT OC 512MB GDDR3 PCI-Express
PSU 650W Corsair CMPSU-650TX, single 12
Hard Drives RealSSD C300 64GB 2.5" SATA 6Gb/s
RAM:
Corsair XMS3 6GB CTR3X6G1333C9
and I'm currently running 3x2gb of Corsair XMS3 CM3X2G1600C9
As you can see from my thread here I've been having plenty of issues!
http://www.sevenforums.com/crashes-debugging/115685-memory_managment-issues.html#post994148
and
http://forum.corsair.com/forums/showthread.php?t=89780
Essentially running the FA BIOS I had no BSOD issues, but had the missing memory issues. Update to FB and I have all 6gb but loads of BSOD issues. Thought it could have been the BIOS, played around with all manner of settings, got nowhere. Then put everything back to Failsafe Defaults and had a day of good running.
Next cold boot, the system POSTs fine and gets to the Loading Windows screen and will blue screen 100% of the time. The only way I can get the system to boot is to run the Startup repair from my Windows 7 ISO that I run off a multi boot USB stick. Running Startup Repair from the SSD doesn't seem to work.
I'm starting to suspect the SSD is now corrupt and haven't had time to check it. However, I'm also very tempted to RMA the board, as it doesn't seem fit for purpose and I seem to have read a huge amount online about these boards having issues. Trouble is, I'm not sure which MoBo to replace it with.
FunkyErn: How are you getting on with your RMA?
-
Hi and welcome to the Gigabyte Forum.
So in a nutshell the board is ok as it runs fine with FA BIOS(even though it doesn't show all memory) but the BIOS is badly written as it BSODs on FB BIOS. I would suggest a question to GGTS about rewriting the BIOS is called for.
-
Hi and welcome to the Gigabyte Forum.
So in a nutshell the board is ok as it runs fine with FA BIOS(even though it doesn't show all memory) but the BIOS is badly written as it BSODs on FB BIOS. I would suggest a question to GGTS about rewriting the BIOS is called for.
Your nutshelll is indeed correct. I'd be interested to have a look at the pins again, as the post above seems to suggest that they socket could be offset. I can't do this at the moment as I'm away from home, but will do once I'm back.
Forgive my ignorance, but is GGTS the tech support part of the website?
-
I am still awaiting a reply from them regarding this issue
-
Forgive my ignorance, but is GGTS the tech support part of the website?
Yes you are quite correct GGTS is Gigabyte Global Technical Support
I am still awaiting a reply from them regarding this issue
Hey, nowhere in that sentence do you see the word fast
-
They have been very good and fast with everything else but sorting the problem :(
-
Yes you are quite correct GGTS is Gigabyte Global Technical Support
Thanks, I've sent a mail. I'll let you know what they come back with. Once I'm home I'll try the FC3 BIOS and see what happens.
Also, silly question, but should the system SSD be plugged into a particular port?
-
It is best to have it on port 0 the first port on the Southbridge controller.
-
Where have you got this FC3 Bios from
Last one I had was FC1
-
I have also been plagued with the cold boot issue on the UD3R v2. I haven't solved the issue but have found a compromise. I am running B18 beta bios and do not have the cold boot BSOD issue, I do however get an error on cold boot post that states 'recovering missing dram' the reboots and works fine the next boot. This to me is much better than several BSOD until the system is 'warmed up' and lowers the risk of OS corruption. I still think there is something really wrong with this motherboard and will not advise people to buy it (I have built several game systems on this mobo for friends, only mine plays up)
I did RMA the mobo cpu and memory but the reseller found no fault and charged me for the joy of it, they ran the bloody tests in IDE mode and the cold boot issue only plagues me in AHCI mode :(
-
I did RMA the mobo cpu and memory but the reseller found no fault and charged me for the joy of it, they ran the bloody tests in IDE mode and the cold boot issue only plagues me in AHCI mode :(
Are you using a SSD for booting then? If not you are not really gaining anything much in the way of speed over IDE mode and you would benefit from the stability.
-
Where have you got this FC3 Bios from
Last one I had was FC1
The link is here: http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-bios.html
If you install it in the next couple of days, please let me know how you get on.
I have also been plagued with the cold boot issue on the UD3R v2. I haven't solved the issue but have found a compromise. I am running B18 beta bios and do not have the cold boot BSOD issue
Do you have a link for this?
Are you using a SSD for booting then? If not you are not really gaining anything much in the way of speed over IDE mode and you would benefit from the stability.
Which mode should we select if we are booting from an SSD?
-
Quote from: Dark Mantis on Yesterday at 10:42:02 pm
Are you using a SSD for booting then? If not you are not really gaining anything much in the way of speed over IDE mode and you would benefit from the stability.
Which mode should we select if we are booting from an SSD?
No it was not a case of which mode to use when booting but which mode gives greater stability. The OP was complaining of BSODs when in AHCI mode that why I recommended using IDE mode over AHCI.
-
I've switched to Corsair 1600Mhz CAS8 Ram (TR3X6G1600C8D) and seems to be working a lot better on cold boots - so far so good - although I will know more after a week or so.
I had set everything back to Auto and set XMP Profile 1 - it failed on 5th pass of IntelBurnTest on Maximum - so I've upped the QPI/VTT a bit and will re-run my tests.
So far so good though ...
-
Yes it is excellent memory for these boards and very stable. I am running it myself and would like to upgrade it to 12Gb to fill the slots so I could test the board out with that configuration but it is fairly expensive when you have to buy triple kits.
-
That OCZ Gold Series should come with a severe heath warning ... off to eBay it goes !
-
I have had nothing but trouble with the OCZ memory even though it used to be good quality kit. The few times I have tried to use it have ended in replacements. :-\
-
Not to dispute your experience, but just to provide another data point, my OCZ3G1600LV6GK has worked flawlessly (both at stock 1066 and at 1600) with my GA-X58A-UD3R(r2 FB). Win7 is very stable and memtest86+/Prime95 pass all tests.
-
Oh I am sure that you are right. There must be many happy users out there or the company wouldn't still be in existance. ;)
-
Hi theboyfold - sounds like you are having the same type of issues which all seem to lead back to the bios. I have not yet heard back from the supplier about the RMA. They would have received it on Thursday last week and as they have to test it overnight I would expect to hear back from them towards the end of this week. GTS have been slow and they only suggested trying bios FC3 (which I did not do as I had already packed up the board and RAM by then). Have you had any luck with bios FC3?
-
Hi theboyfold - sounds like you are having the same type of issues which all seem to lead back to the bios. I have not yet heard back from the supplier about the RMA. They would have received it on Thursday last week and as they have to test it overnight I would expect to hear back from them towards the end of this week. GTS have been slow and they only suggested trying bios FC3 (which I did not do as I had already packed up the board and RAM by then). Have you had any luck with bios FC3?
Not tried it yet, as I'm working away from home for the start of this week. Back tomorrow so should give it a try then. It's a real pain to be honest as I'm not sure if I'm suffering from a BIOS issue or hard drive corruption.
The fact I can boot once I've repaired the machine either points to the fact that it's 'warm' by the time I've run Windows Startup Repair or that the HDD keeps corrupting stuff.
If I'd not spent so much money on the thing I'd be tempted to chuck it in the bin and buy a motherboard bundle that's already been tested by the vendor :( With the fact I've been away so much since I've bought it I've had it for nearly 3 months now and without it fully working, apart from when I had the missing RAM issue.
-
I did RMA the mobo cpu and memory but the reseller found no fault and charged me for the joy of it, they ran the bloody tests in IDE mode and the cold boot issue only plagues me in AHCI mode :(
Are you using a SSD for booting then? If not you are not really gaining anything much in the way of speed over IDE mode and you would benefit from the stability.
Yep, running the vertex LE SSD as boot so want to stick with AHCI. Oddly enough the B18 bios has nowresorted back to the behaviour of FC3 after I tested it so Im wondering it it actually took hold when I flashed it back. There are quite a few people with this cold boot issue so it has got to be something with the mobo or bios as memory and other parts do not seem to be the common factor.
-
Yep, running the vertex LE SSD as boot so want to stick with AHCI. Oddly enough the B18 bios has nowresorted back to the behaviour of FC3 after I tested it so Im wondering it it actually took hold when I flashed it back. There are quite a few people with this cold boot issue so it has got to be something with the mobo or bios as memory and other parts do not seem to be the common factor.
I agree with that statement, there doesn't seem to be a consistent issue with memory or any other factor. When I picked the bits I wanted, I made sure I checked on Corsair and with various vendors as to the package they put together in motherboard bundles and the kit I went for was used by plenty of good vendors. Plus the fact I've used 2 different sets of RAM, both have issues I can't believe that I've managed to buy two duff RAM kits...
I'm still waiting on an answer from Tech Support
-
Got home last night, tried to boot up the machine. It hit a BSOD.
Booted this morning, straight into the BIOS, set the default fail safe settings, enabled Profile 1 in the RAM (I forget the acronym!) and it booted straight into Windows and passed a Very High setting Intel Burn Test.
Will try booting from cold tonight to see what happens.
-
So, just tried again 14 hours later and guess what. BSOD!
I'm going to try the latest BIOS tomorrow and if that fails I'll be RMAing the board. It's just not good enough really
-
FC3 still does the same for me ??? :'(
-
No I am sure it is down to a poorly written BIOS code as everything points that way but I just can't see what is taking so long to rewrite a few lines of code. ???
-
FC3 still does the same for me ??? :'(
Rubbish, I was going to try and install that version tonight.
I've got an RMA agreed with the company I bought the MoBo from.
No I am sure it is down to a poorly written BIOS code as everything points that way but I just can't see what is taking so long to rewrite a few lines of code. ???
I work with developers daily and wonder this very self same question all day long...
-
I work with developers daily and wonder this very self same question all day long...
Well they don't want it to appear too easy do they? A good code writer can write in excess of 20,000 lines a day.
-
Just installed the new BIOS and it booted right away, after 4 attempts on the old BIOS, so I'm not sure if that means that it's warm!
Could anybody confirm what the voltages I would need to set for Corsair TR3X6G1600C9
From here it would suggest 1.65v but I don't have an option for that: http://www.corsair.com/products/corei7/faq.aspx
Also, I've set the timings to match those in the doc I've linked to, but that's all. Is there anything else I can look at?
-
1.65 is the recommended voltage but that is not an option on a lot of BIOSes so 1.64 will normally do. It is possible to go up to 1.66v but that will get you a red warning. Quite a few people do run at this voltage though when overclocking heavily.
If it's the Corsair Dominators they normally come with an XMP attached so it is just a case of enabling that and choosing profile 1
-
OK, I'll turn it back down to 1.64, although it seems to be happy running a max Intel Burn Test. However, that's never really been an issue in the past.
Is there anyway of replicating a cold boot?
-
(http://i21.photobucket.com/albums/b296/theboyfold/Capture.png)
How do these voltages look to you? I'm a little lost to be honest outside of what I should set apart from what's printed on the sticks themselves
-
They all look pretty much the norm to me.
Is there anyway of replicating a cold boot?
Short of spraying it with CO2 or similar I think you will just have to wait. It's just the joys of testing ;)
I was just so close to doing the "wellie in the fridge" bit
-
I'll try using it to do a few things and boot it up again tomorrow morning.
Thanks for your help with this, very grateful!
-
You are very welcome. 8)
-
Guess what. Blue screen!
Fingers crossed the retailer will also find fault with this board.
-
Yes I think that is your next step. Good luck. ;)
-
Had to go back to FB BIOS still have problems but a lot less BOOT problems than FC1 FC2 or FC3
-
hi Bob
You have my sympathy. It is a real pain when these problems go on and on and there seems no resolution but I am still sure it is the BIOS that is the trouble. Hopefully they will sort it out soon.
-
My earlier post was incorrect, it wasnt FB16 that bypassed the cold boot BSOD for me, it was FB11. This bios doesnt completely solve the issues, just stops the BSOD. The trade off is that just after verify DMA step I get a message saying recovering lost dram and then it reboots fine the second time every time as opposed to the several BSOD.
I did RMA my mobo and retailer returned no fault found and charged me for it :( Basically they did the tests in IDE mode whereas I use AHCI because I have an SSD. Very odd and very frsutrating
-
Yes very frustrating and happens very often. As a general rule you must make sure that the retailer or whoever is testing the board knows the fault and how it is setup. Best to attach a note to the board with any special particulars.
-
So I've RMA'd my board, will let you know what they say.
In other news, I've just heard back from Gigabyte Tech Support, saying they are sorry they have taken so long to get back to me, do I still want them to answer my question!! :)
-
Sounds about right. They probably know that you've been on the forum. ;D
-
HAHA! Maybe :)
I do hope the RMA finds something, otherwise I'll be stumped as to what's actually wrong...
-
Hi guys - I am back and so is my RMA old motherboard with new replacement Corsair TR3X6G1600C9 memory 8) Turns out it was a thermal problem with the memory on cold boot - once it warms up it was OK. The tech support guys confirmed this in their tests and it worked fine with their test RAM. I got them to test it out with the replacement RAM before sending it back. I have a new set of Corsair TR3X6G1600C9 - same model with different serial numbers (I had noted them done before sending back).
So far so good - it booted fine last night after reconnecting everything. There were some POST errors warning the hardware settings were different to the BIOS screens - I cleared the CMOS and loaded the optimised settings - this now seems fine. I have just cold booted this morning straight into Windows and then Memtest86+ without any issues!!
It feels too good to be true... I will wait a few more days before celebrating - it has been over 6 weeks now to get this far. Basically a dodgy chip on one of the DIMMs caused such a nightmare and hassle.
I will keep everyone posted. If anyone has similar issues I suggest RMAing the board and RAM back to the supplier along with a detailed note of how to replicated the prolem and your setup (as recommended by Dark Mantins previously).
-
Well I am really happy for you FunkyErn. You deserved some luck after all those problems. Fingers crossed mate. ;)
-
Well I spoke too soon - I appear to have a new problem. While MemTest86+ runs fine from cold boots, when I start up Windows and login I get BSOD BCCode 101!!!! This has happened several times now. I am using the optimised defaults with RAM settings of 8-8-8-20 (CmdRate 1T). I have since changed to the actual RAM settings of 8-8-8-22 (CmdRate 2T) - has been working fine since but cannot be sure it is resolved yet. Will need to check again when I get home tonight.
What exactly does "A clock interupt was not revieved on a secondary processor within the allocated time interval." mean? What should I be looking for? Any ideas?
I did verify there weren't any bent pins before re-inserting the processor. I am currently on bios FB - is there any point flashing to FC3?
-
I think from looking at your timing values it was purely a matter of data corruption because of the too fast closing of the bank. Your timing settings should be more like 8-8-8-24 although you might get away with tighter timings if it is good quality RAM
-
The specs for the RAM at 1066 are 8-8-8-22, but could try 8-8-8-24. Does changing the RAS value from 20 to 22 or 24 fix these kind of BCCode 101 problems?
I am also running this at 1066 with 1.5v as per spec. I do not believe I need to up the memory voltage to 1.65v as I am not running at 1600.
Unfortunately I lost the timing values the tech guys at the supplier used due to the POST errors I was getting and having to clear the CMOS to get round that.
-
BSOD 101 means Vcore is not set properly, this can be too much or not enough ( << generally this)
Recovering DRAM size means a channel was dropped, if you are seeing this on cold boots but not warm try increasing QPI/Vtt, or set Dram voltage to 1.66V if it's not already.
If you are underclocking the ram, as you mentioned 1066 instead of stock 1600, then 1.5 may be ok or may not be, you might need to try 1.55-1.6 as the memory was not designed to run that slow so 1.5V may or may not work.
-
The actual message for BC Code 101 is "A clock interrupt was not received on a secondary processor within the allocated time interval". I do not believe this is restricted to vcore voltage being over or under. My latest research suggests there are three categories of issues that can cause this:
1. bios issues (wrong settings, inc. voltage settings)
2. hardware problems (overheating, defective components)
3. device drivers
Update to saga so far: got home last night, cold booted into MemTest86 and no memory errors! Logged on to Windows 7 and no BSODs! At this stage I have always been running bios FB.
However, one of my two graphics cards started intermittently going blank or showing an all blue screen. I had encountered this issue several weeks before when flashing the bios to FC1. So I swapped both card over to make sure they were seated correctly. And as expected the issue now switched over to the other monitor. As I had this issue one and by flashing to a different bios it stopped, I thought I would flash to bios FC3 to see if that would fix that. All went fine and with FC3, both graphics cards working fine. Run Sisoft burn in to stress test it - all OK, no BSOD.
First thing this morning I cold booted (with bios FC3) and ran MemTest86 and - lo and behold MEMORY ERRORS are back. They lasted for over 20 mins. I then gave up flashed back to bios FB, and no memory errors. All rather confusing. Too many variables.
This is new replacement memory which was tested as ok by both supplier tech support and me, with bios FB. As soon as I flashed to bios FC3 memory errors came back on cold boot. I am so sick of this - all I wanted to do was get on and use the new SONAR 8.5 music software on a decent machine and make music and here I am wasting my time with this...
The graphics card might be a red herring. So what I have done is flashed back to FB and will see what happens tomorrow morning after a overnight cold boot.
-
I think that it would still be a good idea to increase your memory voltage as this generally increases stability. If it is not a settings problem it is normally down to a bad chip on one of the modules that once warmed up will work reliably.
-
Dark Mantis - the saga continues....
I have tried your suggestion and increased DRAM voltage to 1.64v and QPI/VTT to 1.2v (as per the XMP settings) and run at both 1066 and 1600 - with identical results. Cold boot MemTest86 errors consistently! I have tried all permutations of optimised and fail-safe defaults without any joy.
Either this second set of RAM is also bad, or there is a motherboard issue. I have emailed the supplier's tech support saying that the RMA did not address the problem and asking what we should do next.
I am considering purchasing Kingston KVR1066D3N7K3/6G which is on both Gigabyte QVL and Kingston memory configurator as supported. This is 1066 memory which is fine as I do not want to OC. Does anyone know if there have been issues with using KVR1066D3N7K3/6G with the GA-X58A-UD3R rev 2.0 motherboard?
I will try and RMA the motherboard once again. I am also seriously considering ditching Gigabyte and going for the MSI-X58A-GD65 instead. Judging by posting on various forums the ASUS P6X58D-E which is of comparable features and price also suffers from cold boot issues with memory.
-
I would say that if you are still getting cold boot issues and Memtest is recording errors thewn the memory is faulty. If the Kingston memory you mentioned is on both lists it should be fine.
-
Have you tried with the voltage at 1.66 and QPI/VTT at 1.355? I've just finished running through a guide to OC-ing and got my system stable after running through a lot of the settings. I have Corsair TR3X6G1600C8D RAM - I'm running BIOS FB and here are my settings - they are overclocked but stable. Also see that there is a link below to the Corsair recommended settings from their forum
BLCOCK ................................... 200
Load Line calibration .................... Level 2
Standard Vcore ........................... 1.25v
Dynamic Vore ............................. +0.05000v
QPI/VTT voltage ......................... 1.355v
IOH Core ................................. 1.100v
DRAM Voltage ............................. 1.660v
Enabled EIST, C1E , other C States
CPU Multiplier = x19
SPD Multiplier = x8
Uncore = x16
QPI = x36
XMP Profile = Profile 1
RAM Set at 8-8-8-24 - everything else on Auto
I tested my system with CPU at x15 (Vcore=normal), and BLCOCK from 150 - 200 with RAM at x6 and x8 - it was stable once I'd increased the QPI/VTT to 1.355 (From the Corsair forum they tested the RAM with QPI/VTT of 1.35 to get stable - http://forum.corsair.com/v3/showthread.php?s=89e1dacb2680af46b8e7c0f945fafa54&t=81035)
Then to get a higher CPU, I did x21 CPU with Block from 150->180 and that's when I had to up Vcore to 1.25.
I'm sorry if this reads like an OC guide but there are a bunch of other BIOS settings that I'd switched from Auto to a manual setting and I thought they might help.
Feel free to ignore it if I'm talking rubbish - I'm new to OC and manual settings in BIOS.
-
QPI/VTT has to be within 0.5 of the RAM Voltage - so if you are upping the DRAM Voltage to 1.66 then you have to have at least QPI/VTT = 1.16v
But i've found my RAM stable up to 1600Mhz only with QPI/VTT up to 1.355 (I had it around 1.25/1.27 when I had Bclock on 133 - but upped to 1.355 when I upped the Blcock to 200).
I was told that you could run QPI/VTT up to about 1.45 but that is quite high - I've had no issues 1.355 with only a couple of case fans to cool my machine and Mobo.
-
notshy, did you have any issues booting from cold as well?
-
I had issues with some OCZ 2000 Mhz Gold Series (OCZ3G2000LV6GK) - they would give me issues with a cold boot but would pass 10 hours Memtest and 24 hours Prime95 when warm.
I've switched to 6GB CORSAIR Dominator DDR3-1600MHZ (TR3X6G1600C8D) and had no issues - I can post my full BIOS settings later on if people would find that useful. As I said earlier, I've been through an overclocking exercise this weekend and it's all working well on cold boots and long stress tests.
Main RAM settings are to use XMP Profile 1 - but manually set voltage to 1.66v, QPI/VTT to 1.355, set only the four timings at 8-8-8-24.
-
To be honest I think the Corsair Dominators take some beating on this platform.
-
I went for them as they were on the supported list, I'd heard good things and Corsair guaranteed that exact model to work with the motherboard - http://www.corsair.com/configurator/product_results.aspx?id=1362102
-
Thanks for the info notshy!
I tried the QPI at 1.2 v which was within 0.5v of the DRAM 1.64v, so I do not think it is that. The thing that gets me is I am just trying to run at stock not OC speeds and this should not be so difficult.
It is interesting that with the OCZ3G2000LV6GK you had cold boot errors, but once warm it would run fine with MemTest. Exactly the same pattern with my Corsair TR3X6G1600C9. I see you are using the TR3X6G1600C8D, which is the Dominator while mine is XMS - that could be the difference. Switching make of RAM resolved the cold boot issue for you - hopefully it will do the same for me!
I spoke to the supplier tech support earlier and he said there are known issues with the GA-X58A-UD3R and TR3X6G1600C9 under certain conditions (which are not clearly understood yet) which both Corsair and Gigabyte are aware of and working to address. Generally this combo works fine. He thinks that the two components are probably fine individually, but just do not work well together under the current FB bios. He thinks this will be addressed in a future release of the BIOS. He did say that the ASUS P6X58D-E also had similar cold boot issues which have now been resolved by the latest BIOS release. These are their two best selling mobos.
So I went ahead and ordered the Kingston KVR1066D3N7K3/6G this afternoon. I also did a search on Google to see if there were any known issues and all looks good so far. Will let you all know the results in the next few days.
-
I went for them as they were on the supported list, I'd heard good things and Corsair guaranteed that exact model to work with the motherboard - http://www.corsair.com/configurator/product_results.aspx?id=1362102
The thing with that list is that I have tried the TR3X6G1333C9 in my motherboard, and it didn't work!
Stuff :)
Did you get my PM?
-
Yup - just got it and replied already.
-
I agree that it must be a compatibility issue thing - the board is only supposed to run RAM at 1066 so any speeds higher than that are an overclock - but you offset that with RAM that's designed to be overclocked and you are going to get some funny issues.
If you look at any board that has been around a bit - they are usually on BIOS v8, v9 or v10 - so I think it's just the fact that we are all on official BIOS v2 (FB) and there are things to iron out. It just so happens that some make/models work better on the current BIOS version? Or maybe it's my individual batch? The other issue is that it's hard to replicate cold boots to test !
I went for them as they were on the supported list, I'd heard good things and Corsair guaranteed that exact model to work with the motherboard - http://www.corsair.com/configurator/product_results.aspx?id=1362102
The thing with that list is that I have tried the TR3X6G1333C9 in my motherboard, and it didn't work!
Is it in the Gigabyte QVL for the board also? If so then I stand corrected.
Thanks for the info notshy!
I tried the QPI at 1.2 v which was within 0.5v of the DRAM 1.64v, so I do not think it is that. The thing that gets me is I am just trying to run at stock not OC speeds and this should not be so difficult.
It might be worth a last ditch try at 1.355v and 1.66v ? I went for that based off the testing conditions that Corsair put the RAM under.
-
I went for them as they were on the supported list, I'd heard good things and Corsair guaranteed that exact model to work with the motherboard - http://www.corsair.com/configurator/product_results.aspx?id=1362102
The thing with that list is that I have tried the TR3X6G1333C9 in my motherboard, and it didn't work!
Is it in the Gigabyte QVL for the board also? If so then I stand corrected.
Just checked and no, they aren't on the QVL http://download.gigabyte.eu/FileList/Memory/mb_memory_ga-x58a-ud3r_v2.0.pdf
However, they are mentioned in the link that you sent, they are suggested for the 'enthusiast' user! So it's a little confusing really...
-
Just checked and no, they aren't on the QVL http://download.gigabyte.eu/FileList/Memory/mb_memory_ga-x58a-ud3r_v2.0.pdf
However, they are mentioned in the link that you sent, they are suggested for the 'enthusiast' user! So it's a little confusing really...
I did notice that there used to be 3 models of RAM in that Corsair link and now there are 2, as we've all said before - I think it's just a case of either trialling different RAM makes until we find ones that work - or waiting 1-6 months for the BIOS to be updated to work with more RAM makes/models
-
they are suggested for the 'enthusiast' user! So it's a little confusing really...
Not really confusing. They are just emphasising that you must be very enthusiastic to get them to work ;D
Simples.
-
they are suggested for the 'enthusiast' user! So it's a little confusing really...
Not really confusing. They are just emphasising that you must be very enthusiastic to get them to work ;D
Simples.
LOL! Maybe my cursing and swearing at them wasn't the right sort of enthusiasm...
-
Getting them to work is easy
Getting them to work as they should is IMPOSSIBLE !!!!
Waiting for a revisied BIOS or option besides RMA is @@@@@@@@@@@@@@@@
-
Right on fatbobuk!!
I am still waiting for the new Kingston RAM to arrive (from a different supplier as the original does not stock Kingston). The system with the Corsair RAM still has the cold boot memory failures. Bizarrely enough for the first time ever it cold booted fine this morning - which shocked me. Could it have miracolously fixed itself??? NO! I switched it off, had breakfast and tried it again and the old familiar combo of blue Memtest screen with bright red flashed back into life again... This is interesting - it would explain how it passed the supplier's testing - it can very rarely start up correctly. If this was purely a thermal issue on the RAM I would not expect to see this variance.
The saga continues... will let you know how the new memory works.
If that does not resolve it - will RMA the motherboard, Corsair RAM and processor back to supplier.
-
I am not sure how it is done in Gigabyte's factories but in most manufacturing plants the product is only batch tested which basically means that a given percentage of the output is pulled for testing. This is normally done as randomly as possible and will be a few % of the total. If a sample fails then a more thorough testing is done to ascertain if there is a bad batch or just a faulty component or such.
-
Yesterday a Fc5 Bios was posted and now this morning a FC Bios has been posted
AM trying The FC one but will have to wait for cold boot results but Hot boot is OK except for still having to have Flash Drive in USB port
Will post results
-
I saw that bios FC doesn't say anything about improving RAM compatibility ! I'll update to it tonight!
-
Forgive my French but b****ks!!! I've just spoken to 'Scam' and have been told that my board works fine and I have to now pay them £10 for testing and £10 for delivery plus VAT.
This wasn't explained to me when I sent it back and it certainly wasn't included in the emails they sent me. I'm tempted to just leave it with them and tell them to stick it where the sun doesn't shine.
However, in a moment of sanity I've asked them to tell me what components they have test it with so I can see what they have to say.
-
Sorry to hear that man - that's rubbish !!!!
-
Sorry to hear that man - that's rubbish !!!!
Did they charge you for sending your board back as well?
-
I didn't send mine back in the end - I forked out for my new Corsair Ram for £125 on top of the £165 that I spent on that OCZ RAM. I'm now selling those OCZ old chips.
It wasn't so straight forward for me to send my board back as it was bought by someone else for me.
-
I'm tempted to leave it with them, they are utter arseholes to deal with I have to say. The company, not the board :)
-
Forgive my French but b****ks!!! I've just spoken to 'Scam' and have been told that my board works fine and I have to now pay them £10 for testing and £10 for delivery plus VAT.
However, in a moment of sanity I've asked them to tell me what components they have test it with so I can see what they have to say.
I would agree that it seems hard but on the other hand if your board was ok and they have doen what they say then they are out of pocket too. They still have to pay their technician for his time in hooking it all up and checking the motherboard and then they have to get it back to you. To be honest I would say that their charges are reasonable in the circumstances. Try and get it done locally and see what the charge would be. I am sure that this is not what you want to hear right now but we have to be fair and take a balanced perspective.
-
Forgive my French but b****ks!!! I've just spoken to 'Scam' and have been told that my board works fine and I have to now pay them £10 for testing and £10 for delivery plus VAT.
However, in a moment of sanity I've asked them to tell me what components they have test it with so I can see what they have to say.
I would agree that it seems hard but on the other hand if your board was ok and they have doen what they say then they are out of pocket too. They still have to pay their technician for his time in hooking it all up and checking the motherboard and then they have to get it back to you. To be honest I would say that their charges are reasonable in the circumstances. Try and get it done locally and see what the charge would be. I am sure that this is not what you want to hear right now but we have to be fair and take a balanced perspective.
It's more the fact they didn't tell me when I requested the RMA and the delivery costs for sending it back are higher than when I bought the board. They mention at the end of the long T&Cs they will charge a 'fair' cost for the return of the board, so the cost will be higher than when it was sent with other goods.
Anyway, I'm just pissed off with them and have a history of being pissed off at them (I stopped buying from them after another issue with a more recent purchase). This thread isn't about my ranting anyway, it's about the boards!!
So, which options should I look at? Getting more of the Corsair RAM that 'Hello People' bought or look at the processor? Even though that's passed loads of Intel Burn tests without the merest hint of a fault.
-
It might pay you rather than paying out more money in the hope of making the right decision first time to take the case to a local computer shop and ask them to swap out the CPU or memory etc and buy just whatever they find works. They are normally quite helpful if they think there might be a sale on the end of it.
-
I'd recommend my RAM has worked on cold boots with no issues at all - note the exact model number though.
I've done cold boots of 15 hours off straight into 10 hour memtest with no issues. I've also running an overclock in CPU up to 3.8Ghz on my i7-930 with no problems.
I'm very happy with it all so far! Do you want me to see if I can get the batch number of the RAM?
-
It might pay you rather than paying out more money in the hope of making the right decision first time to take the case to a local computer shop and ask them to swap out the CPU or memory etc and buy just whatever they find works. They are normally quite helpful if they think there might be a sale on the end of it.
That's what I'm thinking of doing. There is a good local shop round the corner from me that might just be able to help.
-
Hey theboyfold - sorry to hear that - it sucks. Dark Mantis does however make a fair point about the time and effort costing the supplier. However, I think the real issue is the manufacturers of the boards and memory should produce better quality products and support - frankly GTS suck even bigger time in my experience. Enough ranting now...
It might be worthwhile trying some different model memory or possibly from a different manufacturer, but something that is definitely on the Gigabyte QVL - notshy's memory is on that list I believe, as is the new Kingston memory I have just received. I will be trying this out over the weekend and will keep you posted.
-
Yes quite, FunkyErn. I would always advise to play safe when specifying your memory and make sure it is on the QVL of at least one of the parties. Although most memory can be made to work if you have enough time and expertise, why make a rod for your own back. ;)
-
Yes quite, FunkyErn. I would always advise to play safe when specifying your memory and make sure it is on the QVL of at least one of the parties. Although most memory can be made to work if you have enough time and expertise, why make a rod for your own back. ;)
The bump from this thread reminded me that I've not heard back from the reseller about which RAM they tested my board with.
-
Just spoken to them and they used the same memory that I've been testing with :(
http://www.scan.co.uk/products/6gb-%283x2gb%29-corsair-xms3-classic-ddr3-pc3-10666-%281333%29-non-ecc-unbuffered-cas-7-7-7-20-165v
Balls.
Back to the drawing board I guess.
-
Balls.
:o
-
Well FC bios still has cold boot errors
Think its time to give up and return back to FA and put up with a machine that boots but only has 4Gb usable until I can get to the retailers and buy another MOBO probably from another company
The last 8 months has put me off Gigabyte a little
-
Well FC bios still has cold boot errors
Think its time to give up and return back to FA and put up with a machine that boots but only has 4Gb usable until I can get to the retailers and buy another MOBO probably from another company
The last 8 months has put me off Gigabyte a little
Remind me again what ram you are using?
-
Well I am sorry to hear that Bob but I can't say that I blame you. Maybe the problem may get sorted out soon and you won't have to go down thjat route.
-
Ram I am using is
Corsair Dominator TR3X6G1600C8D G
The 3Gb version is on the compatability list but not the 6Gb version which this is
-
That I am suprised about as I am using the exact same memory on a UD7 which is pretty much the same board and it works perfectly. :-\
-
Cough, cough.... Try Mushkin instead if you can get them in your area :D
-
Just tragic if you guys are still having problems after a memory change
Really feel sorry for you.
It was a bad 9/10 days for me.
I lost my girlfriend over it even!
-
It was a bad 9/10 days for me.
I lost my girlfriend over it even!
Couldn't you have RMAd her? or was she out of warranty? :-\
-
Hello people - sorry to hear that! But Dark Mantis' reply really cracked me up. If only is was that easy to RMA partners ;D
Well there is finally good news to report: the Kingston KVR1066D3N7K3/6G are working fine so far. Three days of cold boots straight into MemTest without any errors. And all I did was used optimised defaults with auto settings and did not have to twiddle with any settings!
I had used two different sets of Corsair TR3X6G1600C9 6GB with no luck. With the second set of RMA it did only successfully boot 1 time out of 10.
We should draw up a list of known compatible memory for GA-X58A-UD3R rev 2.0 bios FB. It would seem so far that:
Problematic Memory
TR3X6G1333C9 3x2GB (theboyfold at ????) - individual component CTR3X6G1333C9??
TR3X6G1600C9 3x2GB (Funkyern & theboyfold at either 1066 or 1600) - individual component CM3X2G1600C9??
OCZ3G2000LV6GK 3x2GB (notshy at 1600 & 2000)
AX3U1600GB2G9-1G (Hello people at 1600)
Good Memory
KVR1066D3N7K3/6G 3x2GB (Funkyern at 1066)
OCZ3G1600LV6GK (Gary123 at 1066 and 1600)
CMX6GX3M3C1600C7 3x2GB (Hello people at 1600)
Probably Good Memory
TR3X6G1600C8D 3x2GB (notshy at 1600 and fatbobuk at ????) - NB. this does work for notshy so fatbobuk's issue might be something else
Can other people update this list and correct as necessary?
-
Glad you've got it all working ok now FunkyErn and good idea about the compatibility list as long as it doesn't get contaminated with faulty modules.
-
So far FC is the best BIOS I have tried yet
Still getting some boot errors involving BSOD and Page file and memory errors
But not as bad as before
But cannot get Alt+F12 to work to change my backup BIOS to FC
Keeps going to Boot menu ie F12
Stupid Microsoft Curve keyboard ( USB )
-
Yes Bob I expect it is just your keyboard, not an uncommon problem. Try and get hold of a PS2 model if possible as they seem to work much better for this type of thing.
Quick thought you haven't got one of those keyboards with the Function lock have you?
-
It was a bad 9/10 days for me.
I lost my girlfriend over it even!
Couldn't you have RMAd her? or was she out of warranty? :-\
In the end I did RMA her
-
Sometimes it can be a hard decision but there is no point struggling on with a defective unit. It will only give you problem after problem if you don't get it sorted out properly once and for all. Good call. ;)
-
Well FC bios does seem to be better it will cold boot but not with ram running at 1600.
AFter warm up will run at 1600 but when cold wont boot until it alters itself back to 1066
-
I reckon a couple more BIOS updates and we should be there! ;) At least the problems are being ironed out.
-
Hi guys - just reporting back I have had no more cold error boots :D The Kingston RAM at 1066 resolved the problem! I am also running bios FC.
Fatbobuk - sorry to hear that you are still having cold boot issues running at 1600. Is running at 1066 at option for you?
-
Slowly but surely - the group of us are all working our way onto RAM that cold boots and works!
What are we all going to do with our time now that it works? Maybe talk to real people? Or maybe overclock the board ?
Do you think we should add the batch number on to the RAM list too? Would it be bad form to create a sticky of the forum's tried and tested RAM list? Can I put that the OCZ gold series RAM should be avoided at all costs? :o
P.S.I've got my i7930 up to 3.8Ghz with some help from the TweakTown crew .... and the RAM has been rock solid with BLCK up to 200
-
That's good news notshy that your system is now working well and stable. It's your forum and you can post anything you want as long as it's within the law and Gigabyte's rules. We can see about making it sticky if enough people are interested....maybe we should have a poll?
-
Been researching and testing for couple of weeks now and want to share my experience.
My Specs:
Intel i7-950
Gigabyte GA-X58A-UD3R rev 2.0
6GB (3x2GB GSkill F3-12800CL9T-6GBNQ)
Intel X25M G2 80GB SSD on Intel SATA2
Hitachi 1TB + Hitachi 500GB on Jmicron SATA2
All it's working at stock, even the mem is at 1066 with 7-7-7-20 timings and 1.5v
This is a shot of the mem:
(http://dl.dropbox.com/u/1767311/gskill.png)
I can't provide CPU-Z screens being in office on a notebook.
I had the now famous cold boot memory_management BSOD (0x1A code) for couple of weeks (after 3/4 reboots or sitting in bios screen for some time i get to the desktop, Windows 7 64bit for the record), mobo came with FB bios, i tried FC3 FC5 and FC final, but no joy, also IDE/AHCI both give BSOD. Memory and system are error free after 20 passes of memtest and system passed 8 hours OCCT and maximum Intel Burn Test.
After reading this thread yesterday evening i flashed FA bios (cleared DMI pool and loaded optimized defaults), booted into windows and i had no problems with the OS recognizing all the 6GB of ram, so no reserved ram problem for me on the FA bios which is good news already.
Rebooted and shut down/started 4 times to check mem size was always ok.
I then shut down and tried a cold boot 2 hours later, no BSOD, worked with the PC a little, did a 3DMark and 1h OCCT, no errors, then i shut down again. This morning i tried another cold boot (7 hours after the shut down) and no BSOD, did some basic surfing and an OCCT then had to come office.
PC is now shut down and i will do a 12 hours later cold boot in the evening, if it goes good i would have a 3 consecutive cold boots without BSOD record :o and it would probably mean FA bios does have some mem size issue for someone but it probably solves cold boot BSODs.
Still this would leave me without words that the solution is to use an old bios ::) , i would really like to use the latest bios but if everything works and i can even find a stable oc later, i can live with it.
-
Thanks for the update and it is indeed interesting that you are not getting the cold boot or reserved memory problems with FA. Please let us know how it goes in the long run.
-
Thanks for the update and it is indeed interesting that you are not getting the cold boot or reserved memory problems with FA. Please let us know how it goes in the long run.
The third cold boot at 12h from the shutdown was still without BSOD but the usable memory problem popped up :( It took 3 reboots before the system saw all the 6GB as usable.
At this point i don't know if keep it like this and hope in a future decent bios (because to me it's clear this is a bios issue) or go and buy other ram. I can't RMA the gskill or the mobo so have to cash out for new mem, figures i was tempted to spend a bit more and get an asus rampage the irony is that i will now probably have to spend that money on another set of mem :(
-
Yes would agree that it seems to be a BIOS issue and as such I can't see what is taking so long to fix it. Still hopefully soon there will be an update that works.
-
Yes would agree that it seems to be a BIOS issue and as such I can't see what is taking so long to fix it. Still hopefully soon there will be an update that works.
TweakTown at still on version FC so fingers crossed some beta versions of FD start coming out.
-
It is my day off tomorrow so am tempted to strip my PC down yet again
Set fire to the mobo, urinate on it then post it back to Gigabyte, then go and waste another £150 and buy a Sabertooth
-
I'm probably going to get the same mem kit Hello People got in the end, i have a friend with this mobo e that mem that has no problems at all so it will probably be the solution, i'm just disappointed i have to cash out to solve a stupid bios problem.
-
I have yet again had to resort back to FA bios
FC is causing a lot of BSOD atm, have tried all sorts of voltages and memory settings.
Funny how it shows 6Gb in FA at first boot after reflash.
Will put up with missing memory detection for a while I suppose . At least I know it will boot everytime with FA
-
When you re-flashed the BIOS back to FA did you disable the Keep DMI Settings option on the homepage of QFlash?
-
Yes disabled that
FA runs like a dream, except for the missing memory on cold boot
-
By runs a dream read that as limps slighlty and needs a kick now and a gain to get going
-
As Einstein said "everything is relative" ;)
-
As Einstein said "everything is relative" ;)
Yeah like "you get what you pay for" , really relative in this case because we got a semi functional board ;P
-
Time for the " Trial by fire test !!! " literally
Lighter fluid to hand, jyst need time to get to the retailers for a new board first
-
Please post the pictures :o
Even better idea set fire to it in the retailers!!!!!
-
Time for the " Trial by fire test !!! " literally
Lighter fluid to hand, jyst need time to get to the retailers for a new board first
I'm tempted to switch motherboard myself, if i do i guess gigabyte will never see me as a customer anymore >:(
-
Trust me all manufacturers have their problems and it really doesn't matter which board you buy there is a chance of troubles with it. I had always sworn by Asus boards before this one but now I am quite happy with the switch and I am not swearing at Asus boards any more.
-
bubbl3 - your RAM 6GB GSkill F3-12800CL9T-6GBNQ is not on the QVL, whereas F3-12800CL9D-4GBNQ is. I would seriously suggest you switch or buy some new RAM. See earlier postings on page 17 for list of known good and bad memory. Note the TR3X3G1600C8D has had mixed success - works for Hello People but not for fatbobuk.
fatbobuk - sorry to hear that your issues persist. Are you still using the TR3X3G1600C8D?
I am now running bios FC without any issues - well that is not totally true... any memory issues that is! I very occasionally get one of my two graphics cards go blank and then resume after a few seconds. I suspect it is the C1E power saving issue - have not yet disabled this in the bios. Dark Mantis - do you have any suggestions for this? It happens so intermittently (once or twice as weel) I would not know how to verify any changes I make are actually working.
-
I very occasionally get one of my two graphics cards go blank and then resume after a few seconds. I suspect it is the C1E power saving issue - have not yet disabled this in the bios. Dark Mantis - do you have any suggestions for this? It happens so intermittently (once or twice as weel) I would not know how to verify any changes I make are actually working.
Intermittent faults or issues are always the worst to pin down as you can never really test for them. It could quite possibly be due to the power saving settings as they are often the root cause of this type of thing but proving it is another matter. I would suggest disabling them and see how it goes for a week and if the system behaves then you have a fairly good idea. A BIOS update would probably cure it if that is the case so it would only be a temporary fix anyway.
-
Just spoken to them and they used the same memory that I've been testing with :(
http://www.scan.co.uk/products/6gb-%283x2gb%29-corsair-xms3-classic-ddr3-pc3-10666-%281333%29-non-ecc-unbuffered-cas-7-7-7-20-165v
Balls.
Back to the drawing board I guess.
So finally got a chance to retest the board using the same RAM (see link above) they had used (which I had previously tried on another BIOS I think) and it booted from cold and showed all the RAM.
Now I not jumping for joy yet, but I don't think I have actually tested this combo of RAM and BIOS, plus I had spun the system up a couple of times as I'd been having a short somewhere, so the system might have been 'warm'.
I'll test again in the morning and see what happens. Fingers crossed...
-
Hey, fingers crossed this time. ;)
-
Well it worked first thing this morning. Will check again tonight and run some burn tests.
-
Hi theboyfold!
That sounds promising but you are right not to celebrate too early. When the same company RMA'ed my existing board with the replacement RAM it tested fine with them and also when I initially rebuilt the system. It was only after an overnight cold boot did the errors reappear. One morning out of ten it actually cold booted without any errors. I suggest you test it first thing every morning - cold boot and run MemTest86 straight away. You should only need to run for 5-10 mins as my errors would always popup before test#5 ran. If after a week you have no cold boot errors then it is safe to crack open the champagne 8)
I am not aware of anyone else using TR3X6G1333C7 - so you might be fine with this model (or batch) of memory. Didn't you have TR3X6G1600C9 memory before (same as mine)? That model definitely has "issues" with the mobo and bios FA/FB/FC.
After two sets of TR3X6G1600C9 I finally resolved the issue by switching to Kingston 1066 RAM. Good luck with the TR3X6G1333C7 and keep us posted of your progress... how it works fine!
-
I'm clearly getting my numbers confused!
Before RMAing the board I was running TR3X6G1333C7 and it wouldn't boot from cold.
I'm now running TR3X6G1333C9 and it will boot from cold but it's wildly unstable. I get constant BSODs and programmes like Windows Explorer and Windows Desktop Manager are always crashing. Also seeing a lot of errors on my main HDD.
When I could get the C7 to boot, the system would be pretty much rock solid.
So I'll swap out the RAM again and see where I get to this time, I'm also going to update to the latest BIOS and see where that gets me...
The Champagne is back on ice (or in the garden as it's ruddy freezing here today!)
-
Have you tried running Memtest 86+ on the new memory modules to make sure they are not faulty before you start swapping them out again. Never take anything for granted!
-
Just trying now, but my Linux Multiboot drive doesn't want to work this morning.
Ever get the feeling it's going to be one of those days...
-
Yes... I had trouble with my system this morning and it tried to tell me I had a failed overeclock which was nonsense. I think that maybe computers are getting just like us ....don't like working in the cold mornings.
-
Fixed Memtest, ran it, no errors.
Put in the other RAM (TR3X6G1333C7) and same old BSOD.
Now trying to run the FC BIOS
-
Ladies and gentlemen, we have a BSOD :)
I'm going to head to a local friendly PC store and get them to test with some other types of RAM before I burn the MoBo to keep warm
-
Sorry to hear that :(
So I gather you have tried:
TR3X6G1333C7 (old) - would not cold boot without errors
TR3X6G1333C9 (new) - no cold boot errors, but wildly unstable with BSODs
I recommend you try a completely different make of memory other than Corsair. I can recommend the Kingston KVR1066D3N7K3/6G - but this is running at stock 1066 as I have no desire to OC. I have no errors or BSODs with this for over three weeks now. You could try KVR1333D3N9K3/6G if you want 1333.
-
FunkyErn, you are right in what you say.
I think that the TR3X6G1333C7 are faulty, it's now showing issues in MemTest, which it didn't always do before. Although it could be down to the settings in the BIOS, who knows. Issue with that set of RAM is that I bought it from eBay so I can't really RMA them.
Does anybody have a link to the QVA list for this board?
-
Here is the Gigabyte QVL for this rev 2.0 board: http://download.gigabyte.eu/FileList/Memory/mb_memory_ga-x58a-ud3r_v2.0.pdf
but bear in mind that not every make/model is tested for compatibility. If you go on the manufacturer's website they should also have a QVL for this board.
-
The annoying thing is I'm trying to find something I can buy from here:
http://www.novatech.co.uk/novatech/prods/components/memory-pc/ddr3-triplechannel/
Reason being is that they are just around the corner from me and if I have any issues I can go back and tell them my issues, which is more than can be said for the online retailers I've used up until now!
These are the ones I'm leaning to: http://www.novatech.co.uk/novatech/prods/components/memory-pc/ddr3-triplechannel/corsair/cmx6gx3m3a1600c9.html
However, they don't appear on any of the QVL from either Gigabyte or Corsair (Although I think Corsair have changed the ones they list as they now only show the Dominator GT).
I think they are the sticks that Hello People managed to get working though.
Confused and slightly annoyed now :(
-
Here is the list of compatible modulkes by Corsair:
http://www.corsair.com/configurator/product_results.aspx?id=1362102#other_modules
Guaranteed-Compatible Memory for your Gigabyte GA-X58A-UD3R (perform a new search)
Featured Memory
Enthusiast CMP12GX3M3A1600C9
Overclocker CMT6GX3M3A1866C9
Extreme CMT12GX3M3A2000C9
Highest Density CMP24GX3M6A1600C9
For a complete list of compatible modules for this motherboard, click here.
Information about the CMP12GX3M3A1600C9 Module
No Information Available
Information about the Intel X58 Chipset
Desktop PC platforms based on the Intel® X58 Express Chipset, combined with the Intel® Core™ i7 processor family, drive breakthrough performance and state-of-the-art technology to performance and mainstream platforms. The Intel X58 Express Chipset supports the latest 45nm Intel Core i7 processor family at 6.4 GT/s and 4.8 GT/s speeds via the Intel® QuickPath Interconnect (Intel® QPI). Additionally, this chipset delivers dual x16 or quad x8 PCI Express* 2.0 graphics card support, and support for Intel® High Performance Solid State Drives on ICH10 and ICH10R consumer SKUs.
Information about the Gigabyte GA-X58A-UD3R Motherboard
No Information Available Details for CMP12GX3M3A1600C9
Memory Type
DDR3-1600 (Dominator-12800C9*XMP*3CH)
Size
12GB Kit (3 x 4GB)
Latency
9-9-9-24
Voltage
1.65v
Format
240-pin DIMM
Heat Spreader
Dominator
How to Buy
USA
Worldwide
Forum Search
Click Here to see the latest discussions in the Corsair Forums about the Gigabyte GA-X58A-UD3R .
Details for Gigabyte GA-X58A-UD3R
Maximum Memory » 24GB
Expansion Slots » 6
CPU Socket Format » Socket 1366
Chipset » Intel X58
Vendor Website » Click here to view
--------------------------------------------------------------------------------
Select a module from the list below and the details will be presented above. You may also click the checkbox beside as many modules as you wish and click "Compare" to view a more specific list.
Part Number Memory Type Size Voltage Latency
CMT12GX3M6A1866C9 DDR3-1866 (DominatorGT-15000C9*12GB*XMP) 12GB (6 x 2GB) 1.65v 9-9-9-24-2T
HX3X12G1600C9 DDR3-1600 (XMS3-12800C9*XMP*3CH) HX 12GB (6 x 2GB) 1.6v 9-9-9-24-2T
HX3X12G1333C9 DDR3-1333 (XMS3-10600C9*3CH) 12GB (6 x 2GB) 1.5v 9-9-9-24-2T
CMP16GX3M4A1333C9 DDR3-1333 (Dominator-10600C9) 16GB (4 x 4GB) 1.65v 9-9-9-24-2T
CMX6GX3M3A2000C9 DDR3-2000 (XMS3-16000C9) 6GB Kit (3 x 2GB) 1.65v 9-9-9-24-2T
CMT6GX3M3A2000C8 DDR3-2000 (DominatorGT-16000C8*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 8-9-8-24-2T
CMT6GX3M3A1866C9 DDR3-1866 (Dominator-15000C9*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 9-9-9-24-2T
CMX6GX3M3C1600C7 DDR3-1600 (XMS3revC-12800C7*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 7-8-7-20-2T
CMX6GX3M3A1600C9 DDR3-1600 (XMS3-12800C9*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 9-9-9-24-2T
TR3X6G1600C9 DDR3-1600 (XMS3-12800C9*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 9-9-9-24-2T
TR3X6G1600C8 DDR3-1600 (XMS3-12800C8*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 8-8-8-24-2T
CMT6GX3M3A1600C7 DDR3-1600 (DominatorGT-12800C7*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 7-7-7-20-2T
CMP6GX3M3A1600C7 DDR3-1600 (DominatorGT-12800C7*6GB) 6GB Kit (3 x 2GB) 1.65v 7-8-7-20-2T
CMP6GX3M3A1600C8 DDR3-1600 (Dominator-12800C8*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 8-8-8-24-2T
TR3X6G1600C8D DDR3-1600 (Dominator-12800C8*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 8-8-8-24-2T
CMX6GX3M3A1333C9 DDR3-1333 (XMS3-10600C9*3CH) 6GB Kit (3 x 2GB) 1.5v 9-9-9-24-2T
TR3X6G1333C9 DDR3-1333 (XMS3-10600C9*3CH) 6GB Kit (3 x 2GB) 1.5v 9-9-9-24-2T
CMX6GX3M3A1333C8 DDR3-1333 (XMS3-10600C8*XMP*3CH) 6GB Kit (3 x 2GB) 1.65v 8-8-8-24-2T
TR3X3G1600C8D DDR3-1600 (Dominator-12800C8*XMP*3CH) 3GB Kit (3 x 1GB) 1.65v 8-8-8-24-2T
TR3X3G1333C9 DDR3-1333 (XMS3-10600C9*3CH) 3GB Kit (3 x 1GB) 1.5v 9-9-9-24-2T
CMP24GX3M6A1600C9 DDR3-1600 (Dominator-12800C9*XMP*3CH) 24GB Kit (6 x 4GB) 1.65v 9-9-9-24-2T
CMP24GX3M6A1333C9 DDR3-1333 (Dominator-10600C9) 24GB Kit (6 x 4GB) 1.65v 9-9-9-24-2T
CMX12GX3M3A2000C9 DDR3-2000 (XMS3-16000C9) 12GB Kit (3 x 4GB) 1.65v 9-9-9-24-2T
CMP12GX3M3A1600C9 DDR3-1600 (Dominator-12800C9*XMP*3CH) 12GB Kit (3 x 4GB) 1.65v 9-9-9-24-2T
CMD12GX3M6A1600C8 DDR3-1600 (Dominator-12800C8*XMP*3CH) 12GB Kit (6 x 2GB) 1.65v 8-8-8-24-2T
-
Yep, that's what I've seen. The trouble with it is that it can only be bought from online retailers. Something I'm trying to avoid at the moment with the issues I've had of late...
-
You could always use Crucial. Again they guarantee that their products will work with the board. It does need to be done over the net but yopu deal direct with them and they are noramlly very fast and free delivery. I have even used their warranty process years after purchase and from another country but they made no bones about it and just sent a replacement. Brilliant service.
-
I'm sick of this nightmare, i'm gonna buy a sabertooth x58, my mem is on their qvl, bye bye gigabyte.
-
I think I might give Crucial a try and see how that pans out. Failing that I'll flog the MoBo, CPU and RAM as individual bits on eBay and buy a pre built bundle from somewhere.
-
@theboyfold
I think that is probably your best course of action. Please let us know how you get on. ;)
@bubbl3
I came over to Gigabyte from Asus and I can tell you they have their share of problems and if you get a bad one from them you will wish you were back with Gigabyte as their after sales service is something else. :'(
-
I thought abouth the Sabertooth route aswell
Am waiting to hear back From Asus and Corsair about compatability
I think it is a a X58 chipset issue aswell as a board issue
-
@bubbl3
I came over to Gigabyte from Asus and I can tell you they have their share of problems and if you get a bad one from them you will wish you were back with Gigabyte as their after sales service is something else. :'(
Oh well i just switched to the sabertooth and everything works nice, tempted to burn the old gigabyte and make a video as asked here :D
P.S. even the false start problem disappeared (to be clear: it's when you power up the pc, everything spins up then it shuts down and comes back ... ).
-
Well I am happy, bubbl3 that you've finally got a system that apprears to be working properly for you.
As far as the false starts you were talkng about they happen on many Asus boards also and even on my last one.
-
Well I am happy, bubbl3 that you've finally got a system that apprears to be working properly for you.
As far as the false starts you were talkng about they happen on many Asus boards also and even on my last one.
Don't get me wrong, i own several gigabyte motherboards and my overall experience with them is good. What i think is that their X58 lineup has several quality assurance problems and they probably need to improve something in their QA system.
-
Hey theboyfold - sorry to hear about the pain you are going through.
I have had a look at the web site link you posted. I would suggest you take the Corsair memory list with a pinch of salt as the RAM I was using was on their list, but not on the Gigabyte QVL! Therefore the safest approach is to get something that is on both lists.
One set of RAM that is known to work is OCZ3G1600LV6GK (worked for Gary123 and is on Gigabyte QVL) and is available at
http://www.novatech.co.uk/novatech/prods/components/memory-pc/ddr3-triplechannel/ocz/ocz3g1600lv6gk.html (http://www.novatech.co.uk/novatech/prods/components/memory-pc/ddr3-triplechannel/ocz/ocz3g1600lv6gk.html)
I would suggest you try this out.
-
I'm actually tempted to stick the whole lot on eBay as individual lots. RAM x2 CPU and MoBo to fund the purchase of a new pre-built motherboard bundle. I haven't got the time to keep randomly buying new sticks of RAM or the patience with it at the moment to be honest.
Kinda feels like I'm wimping out, but it's been a good few months and I still haven't got the thing working!
-
We do understand your point of view and it does take it's toll when things just don't seem to want to go right. Wish you luck whatever way you decide to play it. ;)
-
after reading this topic I'm afraid to buy this board :-[
this is my ideia:
Gigabyte GA-X58A-UD3R LGA 1366 rev2.0
Intel Core i7 930
HIS HD 6870 crosfire
Corsair 6144MB (3x2GB) DDR3 1333 MHz PC3-10666 TR3X6G1333C9
OCZ 600W Stealthxstream 2
my old samsung F1 500gb sata2 HDD for now
any recomendations?
-
Hi and welcome to the Gigabyte Forum.
I really would try and put this in perspective. Although the problems some people have had here have been bad don't forget that the number is tiny compared to the number of this model of board sold. It is a very good board and I wouldn't be put off by the old noises problem which has now been sorted out anyway.
-
Hi and welcome to the Gigabyte Forum.
I really would try and put this in perspective. Although the problems some people have had here have been bad don't forget that the number is tiny compared to the number of this model of board sold. It is a very good board and I wouldn't be put off by the old noises problem which has now been sorted out anyway.
Thanks for the reply, I'll give a try!
-
Hi and welcome to the Gigabyte Forum.
I really would try and put this in perspective. Although the problems some people have had here have been bad don't forget that the number is tiny compared to the number of this model of board sold. It is a very good board and I wouldn't be put off by the old noises problem which has now been sorted out anyway.
Thanks for the reply, I'll give a try!
Just make sure you buy RAM from the QVL and from a good dealer and you should be fine :)
-
after reading this topic I'm afraid to buy this board :-[
this is my ideia:
Gigabyte GA-X58A-UD3R LGA 1366 rev2.0
Intel Core i7 930
HIS HD 6870 crosfire
Corsair 6144MB (3x2GB) DDR3 1333 MHz PC3-10666 TR3X6G1333C9
OCZ 600W Stealthxstream 2
my old samsung F1 500gb sata2 HDD for now
any recomendations?
I have zero problems with my GA-X58A-UD3R rev 2 and have 4 friends running GA-X58A-UD3R's all using i7 930's, 3 rev 2's and 1 rev 1. They are not having problems. You only see posts on forums when people have problems. Gigabyte has sold a gazillion of these boards which makes post counts higher for this board. The only real flaw I see is the Marvell SATA3 controller performance and compatibility issues some people are having. All Intel boards made today that support SATA3 use the same Marvell controller so they have the same flaw. There are also many posts about memory issues, missing ram, CPU socket pin problems etc. Go look in Asus, MSI, EVGA etc. forums and you will see the same thing. I'm running 12 gigs 3x4 kit of Patriot DDR3 1600 EL. Runs fine stock, overclocked or with the XMP profile. Three boards are running 12 gigs, 2 6 gig kits of Crucial Ballistix Tracer DDR3 1600. They are all overclock to slightly under 4 Ghz. The last system is running 6 gigs of OCZ gold DDR3 1600 at stock speed aka 1066 mhz as the guy is a wussy and afraid to overclock. As far as I know non of this memory is on Gigabytes QVL list. The list is all but useless as not enough ram was tested.
Bill
-
Yes, I would have to agree with Bill there regarding the Gigabyte QVL. You must use it only to check and see if your memory is on it before you purchase but it is more useful to use the memory manufacturer's QVLs as they are more encompassing.
-
theboyfold - I fully understand your frustration >:(. Word of warning about pre-built motherboard bundles - the company I bought my components from are selling bundles with exactly the same RAM and motherboard models I had issues with so it is not a guarantee it will work. It might just be luck of the draw or just a bad batch of RAM (I had two different sets of the same model with serial numbers very close to each other). Good luck whichever route you go down.
Dark Mantis - in my experience even consulting the memory manufacturer's compatible list is not a guarantee that it will work. The first model of Corsair RAM I used was on their list, but not on Gigabytes and it drove me insane. I agree with peoples comments about not being put off by the high number of postings - this is a very popular board and loads of people do not have any trouble with it. One needs to look at the percentage of issues in relation to the total volume sold. This is a very good board (once it is working) and has excellent features (apart from the Marvell SATA3 controller) and good value for money. X58 boards from other manufacturers have similar issues - this is not unique to Gigabyte X58 boards.
xdxita - I would not use Corsair RAM in your config unless someone else is known to be using this model successfully. I believe other people have been having issues with the model TR3X6G1333C9. Check earlier posts about known compatible models. Wonderwrench comment is correct that just because it is not on the Gigabyte QVL does not mean it won't work - but you will need to check that people are known to be using the specific models without any issues.
-
I've emailed the customer service at Crucial to see what the policy is on the returns. I'm still not 100% convinced that my board is well.
If Crucial are happy to let me return the RAM if I'm still having issues I'll go with them, but if they don't I'd rather buy from a store where I feel you get much better service. I'm just nervous given the issues that I've had trying to return stuff to online stores of late.
Wonderwrench, you are right saying that people never come on to forums to say "My motherboard is great and I have no issues"! It's only when things are wrong they will post.
-
@ FunkyErn
You are quite right about sometimes even after checking there are problems but the thing is that if it is on a memory manufacturer's website as compatible I have always found them to stand by that if there are any problems which is what I was referrring to.
-
BIOS Fe1 is now available
Dont know what happened to FD bios but am trying it out as I Type
will post results when I cold boot tomorrow
-
BIOS Fe1 is now available
Dont know what happened to FD bios but am trying it out as I Type
will post results when I cold boot tomorrow
Remind me what RAM you are using?
Don't worry, just seen it in your older posts.
-
BIOS Fe1 is now available
Dont know what happened to FD bios but am trying it out as I Type
will post results when I cold boot tomorrow
Wow updates are coming fast lately. It took 4 months for FB then 2 months for FC and now FD and FE1 are out. That's 3 updates in less than a month. I'm running FB bios and it working fine for me so I'm going to stick with it until they get everything straightened out. The US site still shows the FD bios BTW. Both FD and FE1 claim the same USB 3 fixes.
Bill
-
Yes doesn't help a lot when these descriptions are so vague. There are obviously other differences but we are left guessing as to what they are as usual.
-
Have just ordered some Crucial RAM after speaking to a support guy there. This is a link to the model I've picked up:
http://www.crucial.com/uk/store/mpartspecs.aspx?mtbpoid=3FC71129A5CA7304
-
Have just ordered some Crucial RAM after speaking to a support guy there. This is a link to the model I've picked up:
http://www.crucial.com/uk/store/mpartspecs.aspx?mtbpoid=3FC71129A5CA7304
According to the specs they should work fine. Crucial is normaly very good memory and it helps that they are owned by the manufacturer.
-
I've bought direct from them and one of the admins has offered to help me get my timings right. Also, I get a 30 day trial with them
-
Well you can't say fairer than that can you? As I said I am sure that you won't have any problems with their memory... and obviously so are they! ;)
-
Have just ordered some Crucial RAM after speaking to a support guy there. This is a link to the model I've picked up:
http://www.crucial.com/uk/store/mpartspecs.aspx?mtbpoid=3FC71129A5CA7304
Crucial Micron makes good stuff and no one beats their support!
Bill
-
BIOS Fe1 is better than all the others so far
havent tried FD because I missed it for some reason
Only strange thing i noticed is the default voltages
Crashed on boot today though and reset my memory to 1066 AGAIN !!!!!
Will try to see what tomorrows cold boot brings
-
Still causing cold boot problems
Wont boot into windows. Says voltages or overcloking causing boot problems still.
Will boot eventually when warmed or BIOS adjusted
Thoguht we had it this time
>:(
-
That's unlucky. As you said I thought it sounded like it might have fixed the problem with this release. :-\
-
Just checking in......wow...this thread is still going...
For what it's worth...my rig is going very well......ever since I changed the ram...no worries. Runs like a well oiled computer.
good luck everyone
-
Well at least that is good news and shows that getting the right combination of motherboard and memory does work. ;)
-
So, I thought I should post a little update should anybody find this thread.
After my issues with the Corsair RAM I ended up ordering these: http://www.crucial.com/uk/store/mpartspecs.aspx?mtbpoid=3FC71129A5CA7304
So far so good, we have had 3 cold boots, 1 successful Memtest and 1 successful Intel Burn Test (on Max). I've also been able to work in Photoshop and Microsoft office, and wait for it. Not seen 1 BSOD.
So, unless I come back it would seem that I've found a winning combo here!
-
Great. As I said the right memory makes all the difference and it would seem that nowadays it is not possible to get just any old memory to play ball . You need to pick the correct RAM for your motherboard and from a reputable memory manufacturer.
-
Indeed that would be the case.
What strikes me as strange through doing this though is:
1) Corsiar seem to have changed what they said the motherboard would support on more than one occasion during this 'process'
2) There werea fair few suppliers in the UK who were selling the motherboard, ram and CPU combo that I originally started off with. Which was one part of my research into picking the right combo
Anyway, I'll report back if I find anything, but thanks to all for the support and advice on this thread, it's been very helpful indeed!
-
You are very welcome and please do let us know any updates in the future. ;)
-
theboyfold - that is excellent news! :) Glad to hear that people are managing to get their systems working.
My system has been stable since moving to the Kingston memory. Seems to me a common denominator to the problems is the Corsair memory - or at least certain models (or even batches) of the RAM.
As the boyfold pointed out several UK suppliers are bundling the same CPU, mobo and RAM together - so surely it cannot be the model numbers - maybe there are differences between batches of the same model?
-
As the boyfold pointed out several UK suppliers are bundling the same CPU, mobo and RAM together - so surely it cannot be the model numbers - maybe there are differences between batches of the same model?
Quite possibly, but of course you won't hear about it from Corsair! Some chips in a batch could possibly have not been quite up to standard as in any manufacturing process.
-
Seems strange that everyone reccomends this combination
I bought this combination after reading reviews in Custom PC magazine. That was before v2 of the board was released.
Even they had major problems with v2.
Corsair have replied to my queries but misunderstood my statements ( i am not too good with words etc ) they said I should RMA the ram if I am getting error. but my ram isnt erroring no matter which test I run.
With Fe1 BIOS on cold boot it BSOD at windows start or halts requiring a restart.
After 3 attempts it always boots to windows. I have applied extra voltage and overclocked it to 4Ghz to try and warm it up quicker ( maybe not the best idea ) but still takes 3 attempts to boot.
Heres hoping the next BIOS may do the trick before ALL my hair falls out. Cant be bothered dismantling again !!!!! to RMA it . nect time it comes out will be to replace it or the memory.
-
Hi fatbobuk
I don't remember if I have suggested it before on this thread but just in case I have been amiss there is the option in the BIOS to insert a hard drive delay so that when being cold booted it gives the drive a chance to initialise before moving on. It might be worth trying.
-
Just thought I'd pop in and report that I dropped in some Kingston DIMMs and my new board booted up first time; no issues.
I tried it with the BIOS level that came on the motherboard (FB I think) - and it worked; but then upgraded to the latest FE - and tried again - with no issues. http://gigabyte.com/products/product-page.aspx?pid=3449&dl=1#bios (http://gigabyte.com/products/product-page.aspx?pid=3449&dl=1#bios)
Memory: Kingston ValueRAM "Triple Channel" 12 Go (Kit 3x 4 Go) DDR3-SDRAM PC3-10600 CL9 - KVR1333D3N9K3/12G
CPU: i7 950 3.06 GHz 130W
Motherboard: Gigabyte GA-X58A-UD3R Rev2
I've not had a single boot failure, cold or warm, although that said - I've not played with over-clocking it yet.
Andy.
-
Having compatible memory modules is probably the single most important thing in a build.
-
Well couldnt take it any more Im afraid.
Bought a Asus Sabertooth.
STill get some missing memory issues. Which is very common I believe in ALL X58 boards due to the memory controller being on the CPU.
My memory modules defo appear on their compatability list.
This board does run a lot smoother than the UD3R though.
Will try to RMA the board to Gigabyte again !!!!!!!!!!!!
Shame though it couldnt be sorted after 10 months of trying :(
Hope it works out for others though in the future.
Many thanks Dark Mantis for all your patience and help though
-
Well good luck with the Asus motherboard. It is a good board but as you say it still has it's problems and one of them is the bent pins issue so I would advise you to check them when you can. I still do a little work on the Asus Forum from time to time but not as much as I used to now that Gigabyte takes up so much of my time.