Hi, you might remember me from such other threads as:
Irregular boot up
Anyway...I am following a thousand instructions, suggestions and tips and I'm starting with this one...even managing to follow the BSOD Posting Instructions was a challenge in itself.
Here's some details:
- Windows 7 Home Premium 64
- Original installed OS is on the system
- Full retail version
- Bought whole system (you can see in 'my system specs') 2 weeks ago
- OS install 2 weeks old
Further:
I started with the default bios for the Rev2 version of this mobo. Since then...in an effort to a) have the system recognise all ram and b) cure BSOD....I have flashed bios from original (which I think was FA) to FB...and then on to FC1.
FA gave me no BSOD...but it would not recognise all ram
FB recognised all ram but gave me BSOD
FC1 recognises all ram but gives me frightening BSOD
BSOD are coming only on cold boot.
The specs for my ram in detail are:
AX3U 1600GB2G9-1G
DDR3 1600G(9) 2Gx16
Gaming Series
Voltage: 1.55v-1.75v
cl: 9-9-9-24
A70-090131
Please find attached the Windows NT6 BSOD jcgriff2 file which includes the html report files.
Cpuz images:
Some temps:
Any insights into this from anyone in the know could really be helpful.
If any more information is needed please let me know.
thanks
Irregular boot up
Anyway...I am following a thousand instructions, suggestions and tips and I'm starting with this one...even managing to follow the BSOD Posting Instructions was a challenge in itself.
Here's some details:
- Windows 7 Home Premium 64
- Original installed OS is on the system
- Full retail version
- Bought whole system (you can see in 'my system specs') 2 weeks ago
- OS install 2 weeks old
Further:
I started with the default bios for the Rev2 version of this mobo. Since then...in an effort to a) have the system recognise all ram and b) cure BSOD....I have flashed bios from original (which I think was FA) to FB...and then on to FC1.
FA gave me no BSOD...but it would not recognise all ram
FB recognised all ram but gave me BSOD
FC1 recognises all ram but gives me frightening BSOD
BSOD are coming only on cold boot.
The specs for my ram in detail are:
AX3U 1600GB2G9-1G
DDR3 1600G(9) 2Gx16
Gaming Series
Voltage: 1.55v-1.75v
cl: 9-9-9-24
A70-090131
Please find attached the Windows NT6 BSOD jcgriff2 file which includes the html report files.
Cpuz images:
Some temps:
Any insights into this from anyone in the know could really be helpful.
If any more information is needed please let me know.
thanks
Hi, hello people.
All of these dumps point to a hardware or hardware related problem.
One of your dumps directly blamed AVG. AVG is known to cause crashes on some Win 7 systems. Uninstall AVG using this tool: Tool (64 bit). If you have Identity Protection installed, remove it with this tool: Tool. Download and install Microsoft Security Essentials in its place.
After you uninstall AVG, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any dumps created by Driver Verifier.
Quote:
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Error code C2, BAD_POOL_CALLER. Usual causes: Device driver, ?Memory
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel
Error code C2, BAD_POOL_CALLER. Usual causes: Device driver, ?Memory
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel
Code:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50 Debug session time: Sat Oct 9 21:26:20.905 2010 (GMT-4) 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} 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 --------- Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50 Debug session time: Mon Oct 11 05:53:50.624 2010 (GMT-4) 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 --------- Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50 Debug session time: Mon Oct 11 18:08:06.156 2010 (GMT-4) 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 --------- Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50 Debug session time: Tue Oct 12 09:05:23.065 2010 (GMT-4) System Uptime: 0 days 0:00:57.015 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800819f368, fffff8800819ebd0, fffff8800121ab50} Probably caused by : Ntfs.sys ( Ntfs!NtfsCleanupIrpContext+58b ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800819f368 Arg3: fffff8800819ebd0 Arg4: fffff8800121ab50 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800819f368 -- (.exr 0xfffff8800819f368) ExceptionAddress: fffff8800121ab50 (Ntfs!NtfsCleanupIrpContext+0x000000000000058b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800819ebd0 -- (.cxr 0xfffff8800819ebd0) rax=0000000000000000 rbx=fffff8800819f7b0 rcx=0500000000000101 rdx=0000000000000000 rsi=fffffa80075f6820 rdi=fffff8a002dcdc70 rip=fffff8800121ab50 rsp=fffff8800819f5a0 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000001 r10=fffff80002a5c000 r11=fffff8a002dcd5e0 r12=0000000000000001 r13=0000000000000702 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Ntfs!NtfsCleanupIrpContext+0x58b: fffff880`0121ab50 488b01 mov rax,qword ptr [rcx] ds:002b:05000000`00000101=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: avgchsva.exe CURRENT_IRQL: 1 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d040e0 ffffffffffffffff FOLLOWUP_IP: Ntfs!NtfsCleanupIrpContext+58b fffff880`0121ab50 488b01 mov rax,qword ptr [rcx] FAULTING_IP: Ntfs!NtfsCleanupIrpContext+58b fffff880`0121ab50 488b01 mov rax,qword ptr [rcx] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff8800121fef4 to fffff8800121ab50 STACK_TEXT: fffff880`0819f5a0 fffff880`0121fef4 : fffff880`0819f7b0 fffffa80`00000001 00000000`00000000 fffffa80`075f6820 : Ntfs!NtfsCleanupIrpContext+0x58b fffff880`0819f5f0 fffff880`012a3765 : fffff8a0`02dcdb40 fffff880`0819f7b0 00000000`00000000 fffff8a0`00000000 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd4 fffff880`0819f630 fffff880`012a3906 : fffff880`0819f7b0 fffffa80`075f6820 fffff880`000002d2 fffffa80`000003e8 : Ntfs!NtfsCommonQueryInformation+0xf6d fffff880`0819f710 fffff880`012a3ea4 : fffff880`0819f7b0 fffffa80`075f6820 fffffa80`075f6bc0 00000000`00000000 : Ntfs!NtfsFsdDispatchSwitch+0x106 fffff880`0819f790 fffff880`0111123f : fffff880`0819fa30 fffff880`01110be9 fffff880`0819fa00 fffff800`02c46e05 : Ntfs!NtfsFsdDispatchWait+0x14 fffff880`0819f980 fffff880`0110f6df : fffffa80`05e8ea30 00000000`00000000 fffffa80`05e8ea00 fffffa80`075f6820 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`0819fa10 fffff800`02dafe0a : fffffa80`075f6820 fffff880`0819fca0 00000000`057de7e0 00000000`00000009 : fltmgr!FltpDispatch+0xcf fffff880`0819fa70 fffff800`02acb993 : 00000000`00000904 00000000`057de7c8 00000000`057de7e0 fffff880`000003e8 : nt!NtQueryInformationFile+0x535 fffff880`0819fbb0 00000000`775ffe6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`057de778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775ffe6a SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsCleanupIrpContext+58b FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f STACK_COMMAND: .cxr 0xfffff8800819ebd0 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsCleanupIrpContext+58b BUCKET_ID: X64_0x24_Ntfs!NtfsCleanupIrpContext+58b Followup: MachineOwner --------- Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50 Debug session time: Tue Oct 12 09:16:27.210 2010 (GMT-4) System Uptime: 0 days 0:10:07.272 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff781c0000000, 6da1, 6d9f0000d342} Probably caused by : CI.dll ( CI!MincrypK_UpdateCatalogCache+714 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff781c0000000 Arg3: 0000000000006da1 Arg4: 00006d9f0000d342 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88003377810 -- (.trap 0xfffff88003377810) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000030 rbx=0000000000000000 rcx=0000000000000000 rdx=fffff8a003ad9672 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002cbb5ee rsp=fffff880033779a0 rbp=fffff8a003ad9001 r8=0000000005650b81 r9=0000000000000000 r10=00000000000000ff r11=0000000000000007 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!LZNT1CompressChunk+0x137: fffff800`02cbb5ee 8845ff mov byte ptr [rbp-1],al ss:0018:fffff8a0`03ad9000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002aeee58 to fffff80002a7f740 STACK_TEXT: fffff880`033774a8 fffff800`02aeee58 : 00000000`0000001a 00000000`00005003 fffff781`c0000000 00000000`00006da1 : nt!KeBugCheckEx fffff880`033774b0 fffff800`02a9bca2 : 00000000`00000001 fffff8a0`03ad9000 fffff880`03377810 fffff6fc`5001d6c8 : nt! ?? ::FNODOBFM::`string'+0x29f57 fffff880`033775a0 fffff800`02a99cf1 : 00000000`00136ddf 00000000`00000000 00000000`00000000 fffff680`0002b280 : nt!MiDispatchFault+0x8c2 fffff880`033776b0 fffff800`02a7d82e : 00000000`00000001 00000000`05650b81 fffff8a0`03ad8600 58fee8d8`0000c400 : nt!MmAccessFault+0x8f1 fffff880`03377810 fffff800`02cbb5ee : 00000000`0000d900 00000000`0000d920 00000000`05650b81 fffff8a0`03ad9000 : nt!KiPageFault+0x16e fffff880`033779a0 fffff800`02cbba6d : fffff800`02cbb350 fffff880`00cddbff fffff8a0`03ad9672 fffff8a0`03ad8673 : nt!LZNT1CompressChunk+0x137 fffff880`03377a20 fffff800`02cbbb48 : 00000000`00001002 00000000`00000000 fffff800`02c245f8 00000000`00000000 : nt!RtlCompressBufferLZNT1+0x7d fffff880`03377a90 fffff880`00cdf99c : 00000000`00000000 00000000`00000000 fffff800`02c245f8 00000000`00000000 : nt!RtlCompressBuffer+0x64 fffff880`03377ae0 fffff880`00cdabdf : fffffa80`00000001 fffffa80`00010020 fffffa80`00001000 fffffa80`00000001 : CI!MincrypK_UpdateCatalogCache+0x714 fffff880`03377c80 fffff800`02a8c961 : fffff800`02c24500 fffff800`02d7bc20 fffffa80`04f22040 00000000`00000000 : CI!CipPostBootWorker+0x13 fffff880`03377cb0 fffff800`02d23c06 : 00000000`00000000 fffffa80`04f22040 00000000`00000080 fffffa80`04e89890 : nt!ExpWorkerThread+0x111 fffff880`03377d40 fffff800`02a5dc26 : fffff880`03167180 fffffa80`04f22040 fffff880`031720c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03377d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: CI!MincrypK_UpdateCatalogCache+714 fffff880`00cdf99c 8bf8 mov edi,eax SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: CI!MincrypK_UpdateCatalogCache+714 FOLLOWUP_NAME: MachineOwner MODULE_NAME: CI IMAGE_NAME: CI.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4a5be01d FAILURE_BUCKET_ID: X64_0x1a_5003_CI!MincrypK_UpdateCatalogCache+714 BUCKET_ID: X64_0x1a_5003_CI!MincrypK_UpdateCatalogCache+714 Followup: MachineOwner --------- After you uninstall AVG, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any dumps created by Driver Verifier.
Ok thanks very much....I'll try those things and maybe post back if they don't work.
Also...just want to mention that Gigabyte has relpied to my support ticket....they sent me the zip for the latest BIOS....it is FC2. I haven't seen that anywhere around the online traps...or heard about it...so it must be quite new
Also...just want to mention that Gigabyte has relpied to my support ticket....they sent me the zip for the latest BIOS....it is FC2. I haven't seen that anywhere around the online traps...or heard about it...so it must be quite new
Very good. I will be interested to hear how the new BIOS works. Please update this thread and let us know how your system is doing.
�� Quote: Originally Posted by CarlTR6 
After you uninstall AVG, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any dumps created by Driver Verifier.
Ok...and should I flash to the new bios now?
I have uninstalled AVG (although the avgremoverx86.exe hung 3 times...it did some stuff in a little dos window...but hung and didn't respond)....so I used control panel to uninstall AVG.
I installed the Microsoft virus scanner app and I just enabled Driver Verifier and was abuot to reboot to see if I could get the dumps...
Standing by...
Update to your new BIOS, a Beta BIOS is very risky.
From: Irregular boot up
Those Idle temps are very high, they should be around 30C.
Have you checked your CPU heatsink?
Did you install it?
What thermal paste did you use?
This is the first issue you need to solve, high temps can cause blue screens and shut down your system.
If you have any questions, post them here.
You have received a lot of suggestions, just start them one at a time and post the results.
Let us know if you need any help.
From: Irregular boot up
Quote:
You have received very good trouble shooting advice already.
Have you tried any of them?
Please confirm what steps you have done and specify the ones you have not done.
Cold boot issues can be caused by software, drivers, settings and/or hardware.
This is a difficult problem to troubleshoot, it's similar to an intermittent electrical fault, it may take several tests run repeatedly to find the cause.
If you're having the same or worse issues with the Beta BIOS I would recommend to go back to the last stable BIOS.
Beta BIOS are sometimes not full versions and may add other instability issues to your current problems.
A good place to start is to follow all the steps suggested by Greg in post #2. Also Carl's BSOD log files, he can analyze them while you're testing hardware.
For the Memtest86+ tests I would follow this tutorial:
How to Test and Diagnose RAM Issues with Memtest86+
Be sure to follow the steps in Part 3, this will test the RAM cards and the motherboard slots.
It is possible for all three RAM cards to pass, then when run with one card it can fail. Number of RAM cards assuming 3x2GB.
It is also possible that it will pass several times and then fail.
You should also run memtest86+ under cold boot conditions. Run it from USB memory stick if possible, or from CD, at first startup. This can eliminate the possible settings and/or software probable causes.
There definitely are several possible causes but, have seen this resolved by adjusting RAM settings or running new RAM, by either testing with different RAM cards or RMA'ing the RAM.
Again, suggest you start from Greg's post #2, and Carl's post #10.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
This will give us some information on your system and hopefully some clues for us to continue.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Speed Fan or Real Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Let us know the progress.
If you're methodical and let us know the results from each step, this will help us to resolve your issues.
Have you tried any of them?
Please confirm what steps you have done and specify the ones you have not done.
Cold boot issues can be caused by software, drivers, settings and/or hardware.
This is a difficult problem to troubleshoot, it's similar to an intermittent electrical fault, it may take several tests run repeatedly to find the cause.
If you're having the same or worse issues with the Beta BIOS I would recommend to go back to the last stable BIOS.
Beta BIOS are sometimes not full versions and may add other instability issues to your current problems.
A good place to start is to follow all the steps suggested by Greg in post #2. Also Carl's BSOD log files, he can analyze them while you're testing hardware.
For the Memtest86+ tests I would follow this tutorial:
How to Test and Diagnose RAM Issues with Memtest86+
Be sure to follow the steps in Part 3, this will test the RAM cards and the motherboard slots.
It is possible for all three RAM cards to pass, then when run with one card it can fail. Number of RAM cards assuming 3x2GB.
It is also possible that it will pass several times and then fail.
You should also run memtest86+ under cold boot conditions. Run it from USB memory stick if possible, or from CD, at first startup. This can eliminate the possible settings and/or software probable causes.
There definitely are several possible causes but, have seen this resolved by adjusting RAM settings or running new RAM, by either testing with different RAM cards or RMA'ing the RAM.
Again, suggest you start from Greg's post #2, and Carl's post #10.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
This will give us some information on your system and hopefully some clues for us to continue.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Speed Fan or Real Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Let us know the progress.
If you're methodical and let us know the results from each step, this will help us to resolve your issues.
Have you checked your CPU heatsink?
Did you install it?
What thermal paste did you use?
This is the first issue you need to solve, high temps can cause blue screens and shut down your system.
If you have any questions, post them here.
You have received a lot of suggestions, just start them one at a time and post the results.
Let us know if you need any help.
If you decide to flash your Bios, turn Driver Verifier off first. The mini dumps created by Driver Verifier will be stored in the same folder with your other dumps. Good job on getting rid of AVG. It is tough to uninstall.
I think I am currently using a beta bios - FC1. If I flash to FC2...I suppose that's beta as well. So in your opinion...should I go back to FB...the latest official one on the Gigabyte site?
Also...why did you quote the post from the other thread?
What did you want me to take note of in it?
Also...why did you quote the post from the other thread?
What did you want me to take note of in it?
It is likely a beta also, If Gigabyte sent it to you, it may help with some of the issues.
Let's try it, the other BIOS versions aren't much help, as you've mentioned.
We may need to revert to a stable one, maybe the first, to confirm some of the issues you're having.
I quoted the other thread here so you and others can see the suggestions that have been offered, and it will be easier to reference if its here.
Troubleshooting from different threads is very difficult and will likely slow down any progress.
BTW, if you get suggestions from any other Forums or threads, please let us and any other forum/thread know what your doing.
Trying suggestions from different forums/threads will make it very difficult to make any progress, as the people trying to help you won't know what you have done.
It is your equipment and your choice on what you want to try, but please let us know what you have done.
Let's try it, the other BIOS versions aren't much help, as you've mentioned.
We may need to revert to a stable one, maybe the first, to confirm some of the issues you're having.
I quoted the other thread here so you and others can see the suggestions that have been offered, and it will be easier to reference if its here.
Troubleshooting from different threads is very difficult and will likely slow down any progress.
BTW, if you get suggestions from any other Forums or threads, please let us and any other forum/thread know what your doing.
Trying suggestions from different forums/threads will make it very difficult to make any progress, as the people trying to help you won't know what you have done.
It is your equipment and your choice on what you want to try, but please let us know what you have done.
I understand....everything in this thread is what I have done and tried...nothing more and nothing less.
The advice ultimately on the other thread was to make my own thread here. I tried to make this OP encompass everything that has happened.
I've got some leads going in other forums...but I decided to make this thread a focus.
I'm not worried about breaking anything or money or anything...I just have to solve stuff when it goes bad...it's all I can think about.
Anyway...'let's try it'...you think I should flash to the FC2 bios? I just want to confirm that...I should then revert to a stable bios version if there continue to be problems?
An UPDATE:
On another forum it's been found that the x58A-UD3R Rev2 Mobo only supports some ADATA Ram...just a few types. Of the 1600 ram it supports, the supported list says:
AX3U1600GB2G9AG
But my Ram is:
AX3U1600GB29G1G
Is this relevant to the problem?
The advice ultimately on the other thread was to make my own thread here. I tried to make this OP encompass everything that has happened.
I've got some leads going in other forums...but I decided to make this thread a focus.
I'm not worried about breaking anything or money or anything...I just have to solve stuff when it goes bad...it's all I can think about.
Anyway...'let's try it'...you think I should flash to the FC2 bios? I just want to confirm that...I should then revert to a stable bios version if there continue to be problems?
An UPDATE:
On another forum it's been found that the x58A-UD3R Rev2 Mobo only supports some ADATA Ram...just a few types. Of the 1600 ram it supports, the supported list says:
AX3U1600GB2G9AG
But my Ram is:
AX3U1600GB29G1G
Is this relevant to the problem?
Ok, that's good.
We have had people trying several different things suggested on several different forums and it just makes it impossible to get a handle on what is going on with the system.
Due to the issues you are having, RAM not recognized etc., it is worth the risk to try the BIOS Gigabyte sent you. If this motherboard is having issues, hopefully they are trying to get it fixed.
We'll have to keep this in mind as you work through the issues.
The Real Temp snip you posted, is that with your system at idle?
If it is then it's running very hot.
Shutdown your computer and gently try to turn the CPU cooler, if it moves then it is too loose, try tightening it up.
Check temps again.
If this doesn't lower the temps you will need to take it off, clean and re-apply the thermal paste, check idle temps again.
We have had people trying several different things suggested on several different forums and it just makes it impossible to get a handle on what is going on with the system.
Due to the issues you are having, RAM not recognized etc., it is worth the risk to try the BIOS Gigabyte sent you. If this motherboard is having issues, hopefully they are trying to get it fixed.
We'll have to keep this in mind as you work through the issues.
The Real Temp snip you posted, is that with your system at idle?
If it is then it's running very hot.
Shutdown your computer and gently try to turn the CPU cooler, if it moves then it is too loose, try tightening it up.
Check temps again.
If this doesn't lower the temps you will need to take it off, clean and re-apply the thermal paste, check idle temps again.
Yeah that was during idle. The temps got bad after I tweaked the bios setting as per this:
This is what the bios was like before I tweaked it:
Advanced CPU Features:
CPU Clock Ratio ................................ [21x]
Intel(R) Turbo Boost Tech .................. [Enabled]
CPU Cores Enabled ............................ [All]
CPU Multi Threading .......................... [Enabled]
CPU Enhanced Halt (C1E) ................... [Enabled]
C3/C6/C7 State Support .................... [Disabled]
CPU Thermal Monitor ......................... [Enabled]
CPU EIST Function ............................ [Enabled]
Virtualization Technology ................... [n/a no entry for this] << Disabled if you do not use Vmware or Virtual PC Programs
Bi-Directional PROCHOT ..................... [Enabled]
Uncore & QPI Features:
QPI Link Speed .............................. 4.8Ghz
Uncore Frequency .......................... (2667mhz)
Isonchronous Frequency ..................[n/a no entry for this]
Standard Clock Control:
Base Clock (BCLK) Control ................ [Disabled]
BCLK Frequency (MHz) .....................133mhz
PCI Express Frequency (MHz) ........... [Auto]
C.I.A.2 [n/a no entry for this]
Advanced Clock Control:
CPU Clock Drive ..............................[700mV]
PCI Express Clock Drive ................... [900mV]
CPU Clock Skew ............................. [0ps]
IOH Clock Skew ............................. [0ps]
Advanced DRAM Features:
Performance Enhance ...................... [Turbo]
Extreme Memory Profile (X.M.P) ......... [n/a no entry for this]
System Memory Multiplier (SPD) ........ [AUTO]
DRAM Timing Selectable (SPD) .......... [Auto]
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................
tRCD .......................................
tRP .........................................
tRAS .......................................
Below values may be left in Auto if you like, generally this is fine. For those users who DO Set advanced timings manually, please see some of my thoughts and findings about these settings and rules here
XtremeSystems Forums - View Single Post - Gigabyte EX58-UD5/Extreme Discussion Thread
##Channel A Advanced Timing Control##
tRC ........................................ (Should be = tRAS + tRP or above for stability)
tRRD .......................................
tWTR ...................................... (Must be Write to Read Delay/Same Rank - (tWL + 4)
tWR ........................................
tWTP ....................................... (tWTP Must = tWR + tWL + 4)
tWL ........................................ (tWL Must be CAS Latency -1)
tRFC .......................................
tRTP .......................................
tFAW ......................................
Command Rate (CMD) ................
I gues config for this was:
7 7 7 20 4 19 60 1
##Channel A Misc Timing Control##
Round Trip Latency ...................47
B2B CAS Delay ..........................- (Auto)
Advanced Voltage Control:
CPU
Load Line Calibration ................. [Auto]
CPU Vcore ...............................1.25000V (Auto)
QPI/VTT Voltage 1.175v
CPU PLL 1.800v .......................(Auto)
MCH/ICH
PCIE 1.500v ...........................
QPI PLL 1.100v .......................
IOH Core 1.100v .....................
ICH I/O 1.500v .......................
ICH Core 1.1v ........................
DRAM
DRAM Voltage 1.500v (Auto)..............
DRAM Termination 0.750v [AUTO]
Ch-A Data VRef. 0.750v [AUTO]
Ch-B Data VRef. 0.750v [AUTO]
Ch-C Data VRef. 0.750v [AUTO]
Ch-A Address VRef. 0.750v [AUTO]
Ch-B Address VRef. 0.750v [AUTO]Ch-C Address VRef. 0.750v [AUTO]
And this is after I tweaked bios:
CPU Clock Drive ..............................[700mV]set to 800mv
CPU Vcore ...............................1.25000V (Auto)-set to normal in voltage list for stock cpu clocks
QPI/VTT Voltage 1.175v-set to around 1.25000-1.30000v
DRAM Voltage 1.500v (Auto)set according to ram,either 1.5v or 1.66v
System Memory Multiplier (SPD) ........ [AUTO] set to give you rated ram speed 1600mhz ect either 8x or 10x ect
DRAM Timing Selectable (SPD) .......... [Auto]set manual and type in ram timings below(select quick to set timings for all ram installed)
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................9
tRCD .......................................9
tRP .........................................9
tRAS .......................................24
CPU Enhanced Halt (C1E) ................... [Enabled]disable this and use balanced profile setting in windows7
Control Panel\System and Security\Power Options
Anything suspicious...because the heat of the cpu only got hotter after I changed the bios settings
Have reseated cooler and cleaned thermal paste and reapplied...temps range from 34-39%. Distance to tj max.....mid 60's
EDIT: I have flashed to FC2 now...should I zip crash logs again now?
I was going to run the memtest over night....and see what happens in the morning/ tomorrow with cold boots...
Task manager shows some little cpu spikes....like 0-7/8%......which I never noticed before...perhaps some slight bios tweaking needed?
This is what the bios was like before I tweaked it:
Advanced CPU Features:
CPU Clock Ratio ................................ [21x]
Intel(R) Turbo Boost Tech .................. [Enabled]
CPU Cores Enabled ............................ [All]
CPU Multi Threading .......................... [Enabled]
CPU Enhanced Halt (C1E) ................... [Enabled]
C3/C6/C7 State Support .................... [Disabled]
CPU Thermal Monitor ......................... [Enabled]
CPU EIST Function ............................ [Enabled]
Virtualization Technology ................... [n/a no entry for this] << Disabled if you do not use Vmware or Virtual PC Programs
Bi-Directional PROCHOT ..................... [Enabled]
Uncore & QPI Features:
QPI Link Speed .............................. 4.8Ghz
Uncore Frequency .......................... (2667mhz)
Isonchronous Frequency ..................[n/a no entry for this]
Standard Clock Control:
Base Clock (BCLK) Control ................ [Disabled]
BCLK Frequency (MHz) .....................133mhz
PCI Express Frequency (MHz) ........... [Auto]
C.I.A.2 [n/a no entry for this]
Advanced Clock Control:
CPU Clock Drive ..............................[700mV]
PCI Express Clock Drive ................... [900mV]
CPU Clock Skew ............................. [0ps]
IOH Clock Skew ............................. [0ps]
Advanced DRAM Features:
Performance Enhance ...................... [Turbo]
Extreme Memory Profile (X.M.P) ......... [n/a no entry for this]
System Memory Multiplier (SPD) ........ [AUTO]
DRAM Timing Selectable (SPD) .......... [Auto]
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................
tRCD .......................................
tRP .........................................
tRAS .......................................
Below values may be left in Auto if you like, generally this is fine. For those users who DO Set advanced timings manually, please see some of my thoughts and findings about these settings and rules here
XtremeSystems Forums - View Single Post - Gigabyte EX58-UD5/Extreme Discussion Thread
##Channel A Advanced Timing Control##
tRC ........................................ (Should be = tRAS + tRP or above for stability)
tRRD .......................................
tWTR ...................................... (Must be Write to Read Delay/Same Rank - (tWL + 4)
tWR ........................................
tWTP ....................................... (tWTP Must = tWR + tWL + 4)
tWL ........................................ (tWL Must be CAS Latency -1)
tRFC .......................................
tRTP .......................................
tFAW ......................................
Command Rate (CMD) ................
I gues config for this was:
7 7 7 20 4 19 60 1
##Channel A Misc Timing Control##
Round Trip Latency ...................47
B2B CAS Delay ..........................- (Auto)
Advanced Voltage Control:
CPU
Load Line Calibration ................. [Auto]
CPU Vcore ...............................1.25000V (Auto)
QPI/VTT Voltage 1.175v
CPU PLL 1.800v .......................(Auto)
MCH/ICH
PCIE 1.500v ...........................
QPI PLL 1.100v .......................
IOH Core 1.100v .....................
ICH I/O 1.500v .......................
ICH Core 1.1v ........................
DRAM
DRAM Voltage 1.500v (Auto)..............
DRAM Termination 0.750v [AUTO]
Ch-A Data VRef. 0.750v [AUTO]
Ch-B Data VRef. 0.750v [AUTO]
Ch-C Data VRef. 0.750v [AUTO]
Ch-A Address VRef. 0.750v [AUTO]
Ch-B Address VRef. 0.750v [AUTO]Ch-C Address VRef. 0.750v [AUTO]
And this is after I tweaked bios:
CPU Clock Drive ..............................[700mV]set to 800mv
CPU Vcore ...............................1.25000V (Auto)-set to normal in voltage list for stock cpu clocks
QPI/VTT Voltage 1.175v-set to around 1.25000-1.30000v
DRAM Voltage 1.500v (Auto)set according to ram,either 1.5v or 1.66v
System Memory Multiplier (SPD) ........ [AUTO] set to give you rated ram speed 1600mhz ect either 8x or 10x ect
DRAM Timing Selectable (SPD) .......... [Auto]set manual and type in ram timings below(select quick to set timings for all ram installed)
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................9
tRCD .......................................9
tRP .........................................9
tRAS .......................................24
CPU Enhanced Halt (C1E) ................... [Enabled]disable this and use balanced profile setting in windows7
Control Panel\System and Security\Power Options
Anything suspicious...because the heat of the cpu only got hotter after I changed the bios settings
Have reseated cooler and cleaned thermal paste and reapplied...temps range from 34-39%. Distance to tj max.....mid 60's
EDIT: I have flashed to FC2 now...should I zip crash logs again now?
I was going to run the memtest over night....and see what happens in the morning/ tomorrow with cold boots...
Task manager shows some little cpu spikes....like 0-7/8%......which I never noticed before...perhaps some slight bios tweaking needed?
The temps are much better since you reseated the cooler.
�� Quote: Originally Posted by hello people Sometimes you can get RAM to work by adjusting the settings, but not all the time.
Your best bet is to get RAM listed on the motherboards compatible RAM list.
Can you post the link to this RAM information?
If you can RMA your RAM and get an recommended/approved RAM or from the mobo compatible list you will get the results you are looking for.
�� Quote: Originally Posted by hello people An UPDATE:
On another forum it's been found that the x58A-UD3R Rev2 Mobo only supports some ADATA Ram...just a few types. Of the 1600 ram it supports, the supported list says:
AX3U1600GB2G9AG
But my Ram is:
AX3U1600GB29G1G
Is this relevant to the problem?
On another forum it's been found that the x58A-UD3R Rev2 Mobo only supports some ADATA Ram...just a few types. Of the 1600 ram it supports, the supported list says:
AX3U1600GB2G9AG
But my Ram is:
AX3U1600GB29G1G
Is this relevant to the problem?
Your best bet is to get RAM listed on the motherboards compatible RAM list.
Can you post the link to this RAM information?
If you can RMA your RAM and get an recommended/approved RAM or from the mobo compatible list you will get the results you are looking for.
REPOST EDIT: I have flashed to FC2 now...should I zip crash logs again now?
I was going to run the memtest over night....and see what happens in the morning/ tomorrow with cold boots...
Task manager shows some little cpu spikes....like 0-7/8%......which I never noticed before...perhaps some slight bios tweaking needed?
The site that shows RAM compatibles for the board:
http://download.gigabyte.asia/FileLi...-ud3r_v2.0.pdf
There's an outside chance the new FC2 will be updated to recognise my ram right?
I was going to run the memtest over night....and see what happens in the morning/ tomorrow with cold boots...
Task manager shows some little cpu spikes....like 0-7/8%......which I never noticed before...perhaps some slight bios tweaking needed?
The site that shows RAM compatibles for the board:
http://download.gigabyte.asia/FileLi...-ud3r_v2.0.pdf
There's an outside chance the new FC2 will be updated to recognise my ram right?
Run the Memtest86+ tests and follow this tutorial:
Follow the steps in Part 3, this will test the RAM cards and the motherboard slots.
If you get errors you can stop the test, note what the errors are and let us know.
I wouldn't worry about the CPU spikes, it's likely ok. If you want to know what it's doing use Task Manager and check the Processes tab.
Follow the steps in Part 3, this will test the RAM cards and the motherboard slots.
If you get errors you can stop the test, note what the errors are and let us know.
I wouldn't worry about the CPU spikes, it's likely ok. If you want to know what it's doing use Task Manager and check the Processes tab.
Ok...I will run the memtests and post back later...getting late here...I've been at this all day and night really + fitting in my job.
Anyway...I have the new FC2 in bios and just to make known what I've done...I altered some settings from default by changing these setting entries:
System memory multiplier - 12
Dram voltage - 1.66v
Timings - 8-8-8-24
ok...be back later
thanks
Anyway...I have the new FC2 in bios and just to make known what I've done...I altered some settings from default by changing these setting entries:
System memory multiplier - 12
Dram voltage - 1.66v
Timings - 8-8-8-24
ok...be back later
thanks
I have run memtest for 6 and a half hours. I don't know where to find the results...but this is what I wrote down from the memtest screen:
ECC: disabled
BCLK: 133
QPI: 4.7
Wall time: 6:31
Pass: 6
Errors: 2
ECC Errors: 0
Tst: 7
Pass: 1
Failing Address: 00027f2cf40 - 639.1MB
Good: 09341ece
Bad: 093c1ece
Err-Bits: 00080000
Count: 1
Chan
Ram: 799Mhz (DDR3-1598)
Cas: 8-8-8-24
Seems there is some error...but I don't know exactly what to make of this
I will go on to part 3 of the memtest instructions
I guess I will be some time testing all 3 sticks
ECC: disabled
BCLK: 133
QPI: 4.7
Wall time: 6:31
Pass: 6
Errors: 2
ECC Errors: 0
Tst: 7
Pass: 1
Failing Address: 00027f2cf40 - 639.1MB
Good: 09341ece
Bad: 093c1ece
Err-Bits: 00080000
Count: 1
Chan
Ram: 799Mhz (DDR3-1598)
Cas: 8-8-8-24
Seems there is some error...but I don't know exactly what to make of this
I will go on to part 3 of the memtest instructions
I guess I will be some time testing all 3 sticks
So far I checked 1 stick in one slot....failure on pass 10 and pass 13...16 total passes. I suppose I left it a bit long.
I just don't know what bios settings to use when I do the memtest...any tips?
I just don't know what bios settings to use when I do the memtest...any tips?
Ok Ive been testing my ram with latest bios fc2@optimized defaults bios settings for five hrs and twenty seven minutes......almost six passes compete. Zero errors. Could it almost be safe to assume the ram is ok?
I will continue to test...should I?
7 full passes.....almost 7 hours testing....ZERO errors.
I've stopped the testing. And I am going to assume that the ram is ok and so is the mobo....physically.
So now I should wait for a chance to cold boot....and see what happens
I will continue to test...should I?
7 full passes.....almost 7 hours testing....ZERO errors.
I've stopped the testing. And I am going to assume that the ram is ok and so is the mobo....physically.
So now I should wait for a chance to cold boot....and see what happens
I just adjusted optimised default fc2 bios with these changes:
set ram to run at 1600 (that's the speed of the ram)
set ram/ memory multi to 12
set timings clock to 9 9 9 24 (that's the stated timing of the ram)
Plan to test ram again....should I test one at a time in each slot?
set ram to run at 1600 (that's the speed of the ram)
set ram/ memory multi to 12
set timings clock to 9 9 9 24 (that's the stated timing of the ram)
Plan to test ram again....should I test one at a time in each slot?
Morning....BSOD on cold boot.
I don't know what to do.
Can anyone read the 2 posts before this post and give me any advice?
thanks
I don't know what to do.
Can anyone read the 2 posts before this post and give me any advice?
thanks
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....?
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....?
The fact that you got errors in Memtest tells me something is not right. Run Memtest again from a cold boot, preferably when your computer has been off for a while.
But with what values in bios?
Look at this info....my cpu doesn't even support 1600 ram
GA-X58A-UD3R (rev. 1.0) 1600 MHz support? - Gigabyte - Motherboards-Memory
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
Intel� Core
Look at this info....my cpu doesn't even support 1600 ram
GA-X58A-UD3R (rev. 1.0) 1600 MHz support? - Gigabyte - Motherboards-Memory
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
Intel� Core
I am not a hardware expert; but I do know that you have to go with what your motherboard supports unless you are a true hardware expert and do work arounds.
Well look I'm gonna just try this before I do anymore memory testing.
I'm gonna run the values in bios at optimised so that it hits 1333 or 1066 ram speed. When I have had those bios values I have had no errors in memtest. When the values were different...1600 ram speed...the memtest reported errors.
I think it might be best to set it how it should be set in bios...wait for another cold boot and hope it works.
I'm gonna run the values in bios at optimised so that it hits 1333 or 1066 ram speed. When I have had those bios values I have had no errors in memtest. When the values were different...1600 ram speed...the memtest reported errors.
I think it might be best to set it how it should be set in bios...wait for another cold boot and hope it works.
That is the way to go. I hope it works.
I hope it works. Tell me about it
I'll keep my fingers crossed! 
Looking at the cpu-z pic tells me the ram is OC'ed.
The QPI MHz and the NB MHZ are drastically different.
You have 1600 MHz ram, it runs at 1600MHz not 1333 or 1066.
The relationship between the ram multiplier and cpu multiplier is linked. Setting things to auto may not work.
You need to manually adjust cpu until you get the spec'ed MHz and input the spec'ed voltage. Notice the changes in ram MHz whilest you adjust. You also have to get the ram at its required MHz, initial timings and voltage.
Please note my cpu-z. My system is OC'ed a lot. Because of OC my ram timings are on auto. Its 1333MHz ram at 1472MHz.
Put ram at standard in dram selections
disable ciest, green lan
note how I got the QPI and NB MHz similar.
It would also appear that the cpu is underclocked as well? You have a 2.8 GHz and cpu-z states its at 1.5GHz?????????????????????????????????????????
Mine is a 2.66GHz pushed to 3.8GHz compare the relationships.
The QPI MHz and the NB MHZ are drastically different.
You have 1600 MHz ram, it runs at 1600MHz not 1333 or 1066.
The relationship between the ram multiplier and cpu multiplier is linked. Setting things to auto may not work.
You need to manually adjust cpu until you get the spec'ed MHz and input the spec'ed voltage. Notice the changes in ram MHz whilest you adjust. You also have to get the ram at its required MHz, initial timings and voltage.
Please note my cpu-z. My system is OC'ed a lot. Because of OC my ram timings are on auto. Its 1333MHz ram at 1472MHz.
Put ram at standard in dram selections
disable ciest, green lan
note how I got the QPI and NB MHz similar.
It would also appear that the cpu is underclocked as well? You have a 2.8 GHz and cpu-z states its at 1.5GHz?????????????????????????????????????????
Mine is a 2.66GHz pushed to 3.8GHz compare the relationships.
�� Quote: Originally Posted by hello people Yeah that was during idle. The temps got bad after I tweaked the bios setting as per this:
This is what the bios was like before I tweaked it:
Advanced CPU Features:
CPU Clock Ratio ................................ [21x]
Intel(R) Turbo Boost Tech .................. [Enabled]
CPU Cores Enabled ............................ [All]
CPU Multi Threading .......................... [Enabled] disabled
CPU Enhanced Halt (C1E) ................... [Enabled]
C3/C6/C7 State Support .................... [Disabled]
CPU Thermal Monitor ......................... [Enabled]
CPU EIST Function ............................ [Enabled] disabled
Virtualization Technology ................... [n/a no entry for this] << Disabled if you do not use Vmware or Virtual PC Programs
Bi-Directional PROCHOT ..................... [Enabled]
Uncore & QPI Features:
QPI Link Speed .............................. 4.8Ghz
Uncore Frequency .......................... (2667mhz)
Isonchronous Frequency ..................[n/a no entry for this]
Standard Clock Control:
Base Clock (BCLK) Control ................ [Disabled] enabled
BCLK Frequency (MHz) .....................133mhz
PCI Express Frequency (MHz) ........... [Auto] 100
C.I.A.2 [n/a no entry for this]
Advanced Clock Control:
CPU Clock Drive ..............................[700mV]
PCI Express Clock Drive ................... [900mV]
CPU Clock Skew ............................. [0ps]
IOH Clock Skew ............................. [0ps]
Advanced DRAM Features:
Performance Enhance ...................... [Turbo] standard
Extreme Memory Profile (X.M.P) ......... [n/a no entry for this]
System Memory Multiplier (SPD) ........ [AUTO]
DRAM Timing Selectable (SPD) .......... [Auto]
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................
tRCD .......................................
tRP .........................................
tRAS .......................................
Below values may be left in Auto if you like, generally this is fine. For those users who DO Set advanced timings manually, please see some of my thoughts and findings about these settings and rules here
XtremeSystems Forums - View Single Post - Gigabyte EX58-UD5/Extreme Discussion Thread
##Channel A Advanced Timing Control##
tRC ........................................ (Should be = tRAS + tRP or above for stability)
tRRD .......................................
tWTR ...................................... (Must be Write to Read Delay/Same Rank - (tWL + 4)
tWR ........................................
tWTP ....................................... (tWTP Must = tWR + tWL + 4)
tWL ........................................ (tWL Must be CAS Latency -1)
tRFC .......................................
tRTP .......................................
tFAW ......................................
Command Rate (CMD) ................
I gues config for this was:
7 7 7 20 4 19 60 1
##Channel A Misc Timing Control##
Round Trip Latency ...................47
B2B CAS Delay ..........................- (Auto)
Advanced Voltage Control:
CPU
Load Line Calibration ................. [Auto]
CPU Vcore ...............................1.25000V (Auto) manual
QPI/VTT Voltage 1.175v
CPU PLL 1.800v .......................(Auto)
MCH/ICH
PCIE 1.500v ...........................
QPI PLL 1.100v .......................
IOH Core 1.100v .....................
ICH I/O 1.500v .......................
ICH Core 1.1v ........................
DRAM
DRAM Voltage 1.500v (Auto)..............
DRAM Termination 0.750v [AUTO]
Ch-A Data VRef. 0.750v [AUTO]
Ch-B Data VRef. 0.750v [AUTO]
Ch-C Data VRef. 0.750v [AUTO]
Ch-A Address VRef. 0.750v [AUTO]
Ch-B Address VRef. 0.750v [AUTO]Ch-C Address VRef. 0.750v [AUTO]
And this is after I tweaked bios:
CPU Clock Drive ..............................[700mV]set to 800mv
CPU Vcore ...............................1.25000V (Auto)-set to normal in voltage list for stock cpu clocks
QPI/VTT Voltage 1.175v-set to around 1.25000-1.30000v
DRAM Voltage 1.500v (Auto)set according to ram,either 1.5v or 1.66v
System Memory Multiplier (SPD) ........ [AUTO] set to give you rated ram speed 1600mhz ect either 8x or 10x ect
DRAM Timing Selectable (SPD) .......... [Auto]set manual and type in ram timings below(select quick to set timings for all ram installed)
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................9
tRCD .......................................9
tRP .........................................9
tRAS .......................................24
CPU Enhanced Halt (C1E) ................... [Enabled]disable this and use balanced profile setting in windows7
Control Panel\System and Security\Power Options
Anything suspicious...because the heat of the cpu only got hotter after I changed the bios settings
Have reseated cooler and cleaned thermal paste and reapplied...temps range from 34-39%. Distance to tj max.....mid 60's
EDIT: I have flashed to FC2 now...should I zip crash logs again now?
I was going to run the memtest over night....and see what happens in the morning/ tomorrow with cold boots...
Task manager shows some little cpu spikes....like 0-7/8%......which I never noticed before...perhaps some slight bios tweaking needed?
This is what the bios was like before I tweaked it:
Advanced CPU Features:
CPU Clock Ratio ................................ [21x]
Intel(R) Turbo Boost Tech .................. [Enabled]
CPU Cores Enabled ............................ [All]
CPU Multi Threading .......................... [Enabled] disabled
CPU Enhanced Halt (C1E) ................... [Enabled]
C3/C6/C7 State Support .................... [Disabled]
CPU Thermal Monitor ......................... [Enabled]
CPU EIST Function ............................ [Enabled] disabled
Virtualization Technology ................... [n/a no entry for this] << Disabled if you do not use Vmware or Virtual PC Programs
Bi-Directional PROCHOT ..................... [Enabled]
Uncore & QPI Features:
QPI Link Speed .............................. 4.8Ghz
Uncore Frequency .......................... (2667mhz)
Isonchronous Frequency ..................[n/a no entry for this]
Standard Clock Control:
Base Clock (BCLK) Control ................ [Disabled] enabled
BCLK Frequency (MHz) .....................133mhz
PCI Express Frequency (MHz) ........... [Auto] 100
C.I.A.2 [n/a no entry for this]
Advanced Clock Control:
CPU Clock Drive ..............................[700mV]
PCI Express Clock Drive ................... [900mV]
CPU Clock Skew ............................. [0ps]
IOH Clock Skew ............................. [0ps]
Advanced DRAM Features:
Performance Enhance ...................... [Turbo] standard
Extreme Memory Profile (X.M.P) ......... [n/a no entry for this]
System Memory Multiplier (SPD) ........ [AUTO]
DRAM Timing Selectable (SPD) .......... [Auto]
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................
tRCD .......................................
tRP .........................................
tRAS .......................................
Below values may be left in Auto if you like, generally this is fine. For those users who DO Set advanced timings manually, please see some of my thoughts and findings about these settings and rules here
XtremeSystems Forums - View Single Post - Gigabyte EX58-UD5/Extreme Discussion Thread
##Channel A Advanced Timing Control##
tRC ........................................ (Should be = tRAS + tRP or above for stability)
tRRD .......................................
tWTR ...................................... (Must be Write to Read Delay/Same Rank - (tWL + 4)
tWR ........................................
tWTP ....................................... (tWTP Must = tWR + tWL + 4)
tWL ........................................ (tWL Must be CAS Latency -1)
tRFC .......................................
tRTP .......................................
tFAW ......................................
Command Rate (CMD) ................
I gues config for this was:
7 7 7 20 4 19 60 1
##Channel A Misc Timing Control##
Round Trip Latency ...................47
B2B CAS Delay ..........................- (Auto)
Advanced Voltage Control:
CPU
Load Line Calibration ................. [Auto]
CPU Vcore ...............................1.25000V (Auto) manual
QPI/VTT Voltage 1.175v
CPU PLL 1.800v .......................(Auto)
MCH/ICH
PCIE 1.500v ...........................
QPI PLL 1.100v .......................
IOH Core 1.100v .....................
ICH I/O 1.500v .......................
ICH Core 1.1v ........................
DRAM
DRAM Voltage 1.500v (Auto)..............
DRAM Termination 0.750v [AUTO]
Ch-A Data VRef. 0.750v [AUTO]
Ch-B Data VRef. 0.750v [AUTO]
Ch-C Data VRef. 0.750v [AUTO]
Ch-A Address VRef. 0.750v [AUTO]
Ch-B Address VRef. 0.750v [AUTO]Ch-C Address VRef. 0.750v [AUTO]
And this is after I tweaked bios:
CPU Clock Drive ..............................[700mV]set to 800mv
CPU Vcore ...............................1.25000V (Auto)-set to normal in voltage list for stock cpu clocks
QPI/VTT Voltage 1.175v-set to around 1.25000-1.30000v
DRAM Voltage 1.500v (Auto)set according to ram,either 1.5v or 1.66v
System Memory Multiplier (SPD) ........ [AUTO] set to give you rated ram speed 1600mhz ect either 8x or 10x ect
DRAM Timing Selectable (SPD) .......... [Auto]set manual and type in ram timings below(select quick to set timings for all ram installed)
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................9
tRCD .......................................9
tRP .........................................9
tRAS .......................................24
CPU Enhanced Halt (C1E) ................... [Enabled]disable this and use balanced profile setting in windows7
Control Panel\System and Security\Power Options
Anything suspicious...because the heat of the cpu only got hotter after I changed the bios settings
Have reseated cooler and cleaned thermal paste and reapplied...temps range from 34-39%. Distance to tj max.....mid 60's
EDIT: I have flashed to FC2 now...should I zip crash logs again now?
I was going to run the memtest over night....and see what happens in the morning/ tomorrow with cold boots...
Task manager shows some little cpu spikes....like 0-7/8%......which I never noticed before...perhaps some slight bios tweaking needed?
�� Quote: Originally Posted by hello people But with what values in bios?
Look at this info....my cpu doesn't even support 1600 ram
Look at this info....my cpu doesn't even support 1600 ram
I have a Gigabyte GA-X58A-UD5 running an i7-930 and the CPU DOES support 1600 RAM. See my system specs.
Anyways I'm running at 3.52GHZ, 1600MHz RAM @1.64v, 8-8-8-20.
Bottom line.... you can run at 1600MHZ with your RAM & CPU combo.
Now.... If the RAM isn't designed to run at 1600MHz, and you tried running it at that speed, then that would be a problem!!!
Anyways a good place to get info on that board is here.... GIGABYTE. That's where I get all my info for BIOS tweaks and such.
And.... just so you know... FB is the latest official non-beta BIOS released by Gigabyte for your board.... GA-X58A-UD3R (rev. 2.0) - GIGABYTE. Anything else is beta! Even the one Gigabyte sent you.
As for your issues, since the system is relatively new, replace the RAM and go from there.
�� Quote: Originally Posted by Dave76 Those Idle temps are very high, they should be around 30C.
Case/Case Design
CPU Cooler
Fans
Ambient temps
Room Temps
Hardware
Thermo paste
Voltage
Just to name a few.
I personally don't feel those temps are too high, but than again I don't know the variables I listed.
My two cents
Agree with some of what you said, if the CPU is running at 2.8 GHz to 3.52 GHz or more all the time, then the temps will be higher, of coarse.
Not using EIST, I would have to say my preference is to use it unless you are extreme OC'ing your system, say 4.0 GHz or above. Only for stability issues.
My 2 cents, why run your CPU and system at max settings for checking email and browsing forums, kinda like running your car engine at redline RPM to go get some milk.
If this is what the system owner wants to do, then that is perfectly fine with me. I wouldn't recommend it and for me, I don't do it.
For example now my system is running at 1.44 GHz, multiplier is x9.0, temps are 28 - 30C.
When using graphics programs or Visio, it can go up to 3.84 GHz, multiplier x23, for two cores or less, 3.6 GHz for four cores, x21, temps max at about 57C.
It runs cool and easy until the power is needed, then it kicks into high power and will do what is required quickly.
It depends on what the system owner wants to do.
Many RAM, Motherboard and OC forums are starting to support EIST, or stepping, as a good way to run your system.
Back on topic, the OP is overclocking and seems to be changing the settings depending on what is seen on other forums.
This is not the recommended way to OC, as you will possibly get errors and blue screens.
There are many guides that explain the steps required to get a safe, stable OC.
In my opinion hello people should set his BIOS to default, sort out the BSOD issues, then try the OC'ing again.
I would recommend the slow approach with lots of testing, this will get a stable OC.
Each CPU runs and OCs differently (each i7 930 CPU OCs differently), throw in different MOBOs and different RAM and you have entered many variables. This is why the guides on OC forums recommend to go through the steps from the beginning instead of coping someone's OC settings. Your may get lucky, but one BSOD proves you weren't.
Changing RAM and CPU setting between posts just adds more variables to the equation and makes it more difficult to troubleshoot the issues.
You should start from the beginning with each new BIOS change.
Not using EIST, I would have to say my preference is to use it unless you are extreme OC'ing your system, say 4.0 GHz or above. Only for stability issues.
My 2 cents, why run your CPU and system at max settings for checking email and browsing forums, kinda like running your car engine at redline RPM to go get some milk.
If this is what the system owner wants to do, then that is perfectly fine with me. I wouldn't recommend it and for me, I don't do it.
For example now my system is running at 1.44 GHz, multiplier is x9.0, temps are 28 - 30C.
When using graphics programs or Visio, it can go up to 3.84 GHz, multiplier x23, for two cores or less, 3.6 GHz for four cores, x21, temps max at about 57C.
It runs cool and easy until the power is needed, then it kicks into high power and will do what is required quickly.
It depends on what the system owner wants to do.
Many RAM, Motherboard and OC forums are starting to support EIST, or stepping, as a good way to run your system.
Back on topic, the OP is overclocking and seems to be changing the settings depending on what is seen on other forums.
This is not the recommended way to OC, as you will possibly get errors and blue screens.
There are many guides that explain the steps required to get a safe, stable OC.
In my opinion hello people should set his BIOS to default, sort out the BSOD issues, then try the OC'ing again.
I would recommend the slow approach with lots of testing, this will get a stable OC.
Each CPU runs and OCs differently (each i7 930 CPU OCs differently), throw in different MOBOs and different RAM and you have entered many variables. This is why the guides on OC forums recommend to go through the steps from the beginning instead of coping someone's OC settings. Your may get lucky, but one BSOD proves you weren't.
Changing RAM and CPU setting between posts just adds more variables to the equation and makes it more difficult to troubleshoot the issues.
You should start from the beginning with each new BIOS change.
�� Quote: Originally Posted by Dave76 Agree with some of what you said, if the CPU is running at 2.8 GHz to 3.52 GHz or more all the time, then the temps will be higher, of coarse.
Not using EIST, I would have to say my preference is to use it unless you are extreme OC'ing your system, say 4.0 GHz or above. Only for stability issues.
My 2 cents, why run your CPU and system at max settings for checking email and browsing forums, kinda like running your car engine at redline RPM to go get some milk.
Not using EIST, I would have to say my preference is to use it unless you are extreme OC'ing your system, say 4.0 GHz or above. Only for stability issues.
My 2 cents, why run your CPU and system at max settings for checking email and browsing forums, kinda like running your car engine at redline RPM to go get some milk.
Even though my system is overclocked, I do use EIST as well as Windows Power Management. So my system doesn't run full speed all the time
Attachment 104855
Attachment 104850
Attachment 104851
(temps will stablize at 72ish)
�� Quote: Originally Posted by Dave76 Back on topic, the OP is overclocking and seems to be changing the settings depending on what is seen on other forums.
This is not the recommended way to OC, as you will possibly get errors and blue screens.
There are many guides that explain the steps required to get a safe, stable OC.
In my opinion hello people should set his BIOS to default, sort out the BSOD issues, then try the OC'ing again.
I would recommend the slow approach with lots of testing, this will get a stable OC.
Each CPU runs and OCs differently (each i7 930 CPU OCs differently), throw in different MOBOs and different RAM and you have entered many variables. This is why the guides on OC forums recommend to go through the steps from the beginning instead of coping someone's OC settings. Your may get lucky, but one BSOD proves you weren't.
Changing RAM and CPU setting between posts just adds more variables to the equation and makes it more difficult to troubleshoot the issues.
You should start from the beginning with each new BIOS change.
This is not the recommended way to OC, as you will possibly get errors and blue screens.
There are many guides that explain the steps required to get a safe, stable OC.
In my opinion hello people should set his BIOS to default, sort out the BSOD issues, then try the OC'ing again.
I would recommend the slow approach with lots of testing, this will get a stable OC.
Each CPU runs and OCs differently (each i7 930 CPU OCs differently), throw in different MOBOs and different RAM and you have entered many variables. This is why the guides on OC forums recommend to go through the steps from the beginning instead of coping someone's OC settings. Your may get lucky, but one BSOD proves you weren't.
Changing RAM and CPU setting between posts just adds more variables to the equation and makes it more difficult to troubleshoot the issues.
You should start from the beginning with each new BIOS change.
I would also add that you should stick with the latest "official" BIOS, as the beta can induce unknown issues that have yet to be discovered. Thats why its beta!!!
As Dave has said, set the default values, run the system for a couple of days to see if the system is stable. After that, you can try small steps in overclocking to check stability, then progress from there.
Hope this helps.
I see, we completely agree
Your right about the BIOS, only time I would try a beta BIOS is when issues persist, then you still have to decide if it's helping or not, and you may need to return to a stable BIOS version. This would be assuming the mobo company is trying to solve the issues and giving the beta BIOS as a ready to use version, still risky.
+1 Good advice.
Your right about the BIOS, only time I would try a beta BIOS is when issues persist, then you still have to decide if it's helping or not, and you may need to return to a stable BIOS version. This would be assuming the mobo company is trying to solve the issues and giving the beta BIOS as a ready to use version, still risky.
+1 Good advice.
+1 to you as well. I tried to rep, but... 
Anyways if you go the this forum - GIGABYTE, you'd find it there anyway. There are tons of beta BIOS' posted all the time. I believe one of the posters has conections with Gigabyte.
I still say the OP should really spend his time there as they have some really good people who know these gigabyte boards. Especially Lsdmeasap.
Outside of the overclocking issue I think the OP has memory issues, but it's hard to tell with all the jumping around.
Thanks.
Anyways if you go the this forum - GIGABYTE, you'd find it there anyway. There are tons of beta BIOS' posted all the time. I believe one of the posters has conections with Gigabyte.
I still say the OP should really spend his time there as they have some really good people who know these gigabyte boards. Especially Lsdmeasap.
Outside of the overclocking issue I think the OP has memory issues, but it's hard to tell with all the jumping around.
Thanks.
Ok thanks very much. Yeah I'm guilty of trying all kinds of values in bios as suggested in several forums...in a dumb effort to solve the problem now!
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:
Now to try to get ram up to spec....I should.....?
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:
Now to try to get ram up to spec....I should.....?
Do you have XMP enabled in your BIOS?
Is your CPUZ SPD tab the same as it was on your first post?
If no the the above, then run memtest86+ at your current settings and let us know the results.
Is your CPUZ SPD tab the same as it was on your first post?
If no the the above, then run memtest86+ at your current settings and let us know the results.
XMP is not supported by my ram modules.
No the cpuz spd is different.
Before I revert and do that...I have tweaked bios from defaults doing this:
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:
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?
No the cpuz spd is different.
Before I revert and do that...I have tweaked bios from defaults doing this:
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:
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?
Your overclocking, again.
You should set you BIOS at defaults, test for stability. Run memtest86+, if it passes then run Prime95 blend test.
Worry about RAM frequency later, first get your system stable. If it's not stable at default settings, then you know you have a problem with your RAM.
Once you OC you don't know what the cause of your instability is from.
You should set you BIOS at defaults, test for stability. Run memtest86+, if it passes then run Prime95 blend test.
Worry about RAM frequency later, first get your system stable. If it's not stable at default settings, then you know you have a problem with your RAM.
Once you OC you don't know what the cause of your instability is from.
�� Quote: Originally Posted by Dave76 Your overclocking, again.
You should set you BIOS at defaults, test for stability. Run memtest86+, if it passes then run Prime95 blend test.
Worry about RAM frequency later, first get your system stable. If it's not stable at default settings, then you know you have a problem with your RAM.
Once you OC you don't know what the cause of your instability is from.
You should set you BIOS at defaults, test for stability. Run memtest86+, if it passes then run Prime95 blend test.
Worry about RAM frequency later, first get your system stable. If it's not stable at default settings, then you know you have a problem with your RAM.
Once you OC you don't know what the cause of your instability is from.
I tested it for 7 hours....as specified earlier.
NO error
Now what?
THANKS
NO error
Now what?
THANKS
�� Quote: Originally Posted by hello people XMP is not supported by my ram modules.
No the cpuz spd is different.
Before I revert and do that...I have tweaked bios from defaults doing this:
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:
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?
No the cpuz spd is different.
Before I revert and do that...I have tweaked bios from defaults doing this:
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:
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?
- What are the specs of the RAM?
If the spec sheet for the modules say, for example... 1600MHz @8-8-8-20, Volt 1.6, and the modules don't support XMP.... then that's what you'd manually set in the BIOS.
In short, what's posted on the modules is what should be set in the BIOS! This way you take the "guess" work out.
My corsair modules for example are designed to run @ 1600MHz, 8-8-8-20, 1.6 Volts. However, and this is where experience comes in, even though my modules support XMP, I set them manually because XMP raises my CPU Vcore & QPI/VTT voltages higher than I actually need.
My point.... set the RAM to their specified specs manually!!!
Right now your RAM sticks are running at 1600, if they�re designed to run at that speed, no problem, if not�.problem. Read the spec sheet!!!
Some people will tell you anything above 1066 is theoretically overclocked, that�s debatable. Again, my system doesn�t have to be overclocked to run my modules at 1600, all I have to do is enable XMP and the modules run at that speed.
I would suggest you run the system at its default settings but manually set the RAM to its specs, run mentest. If the RAM errors out, you know you have a problem with the RAM running at its intended speed!!! If no errors, you know the RAM is stable at that speed and the BSOD's aren't RAM related!!!
Now, once you start overclocking from there... well...
Hope this clears things up.
I mentioned what kind of ram it was some posts ago.
Just ran with this. Cold boot....after 3 hrs almost......no boot....dbl boot....no actual bsod
memory multi - x12
uncore - x25
ram voltage - 1.66
timings 9 9 9 24/ command rate 1
qpi/ vtt - 1.315v
Just ran with this. Cold boot....after 3 hrs almost......no boot....dbl boot....no actual bsod
memory multi - x12
uncore - x25
ram voltage - 1.66
timings 9 9 9 24/ command rate 1
qpi/ vtt - 1.315v
�� Quote: Originally Posted by hello people Just ran with this. Cold boot....after 3 hrs almost......no boot....dbl boot....no actual bsod
If the system is only two weeks old, there's no need in fighting faulty RAM. Have it fixed, replaced, or returned.
�� Quote: Originally Posted by hello people Bought whole system (you can see in 'my system specs') 2 weeks ago
First off his latest cpu z shows a cpu underclock. Defaults values will not put the hardware at specs. It will allow the puter to POST, so you can enter bios and SET THE MANUFACTURERS SPECS!
Threader,
you should set the cpu to 2.8 GHz, at correct voltage, same for ram. You need to set these values with the base clock and dram settings. They are interlinked with a QPI mobo.
I think that uncore multi is to high. Default it for now. You will change that when you get a stable platform you can OC. You need to strike a balance with the different options that get you a CPU at 2.8GHz and RAM at 1600MHz. I say disable eist, ht, green lan all those things that leave decisions for the mobo to make.
You need a stable baseline to start with if you intend to OC. You also need to let mobo run awhile with baseline settings to break the mobo in, before going to OC mode. I have done these things, this build has never crashed, except once, I was playing with video card. Its OC'd to hell. You'll luv how the X58 OC's with QPI. But slow down and get a baseline, watch the linked relationships in bios!
Its been awhile since build and I'm slowly remembering my approach. Its an amatuers approach, very simple. If you are interested I will get more detailed.
ie: look my bios again for choices, refresh me mind.
Threader,
you should set the cpu to 2.8 GHz, at correct voltage, same for ram. You need to set these values with the base clock and dram settings. They are interlinked with a QPI mobo.
I think that uncore multi is to high. Default it for now. You will change that when you get a stable platform you can OC. You need to strike a balance with the different options that get you a CPU at 2.8GHz and RAM at 1600MHz. I say disable eist, ht, green lan all those things that leave decisions for the mobo to make.
You need a stable baseline to start with if you intend to OC. You also need to let mobo run awhile with baseline settings to break the mobo in, before going to OC mode. I have done these things, this build has never crashed, except once, I was playing with video card. Its OC'd to hell. You'll luv how the X58 OC's with QPI. But slow down and get a baseline, watch the linked relationships in bios!
Its been awhile since build and I'm slowly remembering my approach. Its an amatuers approach, very simple. If you are interested I will get more detailed.
ie: look my bios again for choices, refresh me mind.
Was this addressed to me?
�� Quote: Originally Posted by spyknee No kidding 
Please read this entire thread before making assumptions!!!
BTW his "cpu underclock" is caused by EIST (Enhanched Intel Speedstep Technology) In short.... his power management, as explained here... http://www.sevenforums.com/crashes-d...ml#post1014795, in this very thread
�� Quote: Originally Posted by spyknee First off his latest cpu z shows a cpu underclock. Defaults values will not put the hardware at specs. It will allow the puter to POST, so you can enter bios and SET THE MANUFACTURERS SPECS!
Please read this entire thread before making assumptions!!!
BTW his "cpu underclock" is caused by EIST (Enhanched Intel Speedstep Technology) In short.... his power management, as explained here... http://www.sevenforums.com/crashes-d...ml#post1014795, in this very thread
No it was not. It was directed at the thread in general. I have read the thread. I did not get pointed when my advice was gainsayed. I stated what was to me the obvious based on his last cpu z pic.
This is about helping the threader, you and I do not matter! So........................moving forward. LOL
This is about helping the threader, you and I do not matter! So........................moving forward. LOL
I'm buying a new board and ram.....any tips?
I want a great board but not over featured....but a great board and ram that is perfect for it
Any ideas....remember my cpu is i7930
I want a great board but not over featured....but a great board and ram that is perfect for it
Any ideas....remember my cpu is i7930
�� Quote: Originally Posted by hello people I'm buying a new board and ram.....any tips?
I want a great board but not over featured....but a great board and ram that is perfect for it
Any ideas....remember my cpu is i7930
I want a great board but not over featured....but a great board and ram that is perfect for it
Any ideas....remember my cpu is i7930
Your keeping the cpu, obviously you select one that the cpu is for. DOH!
Select a mobo that works your video card wants. ie SLI or Cross Fire
Add ram thats on the mobos QVL.
Get the right SATA ports for your drive, another mobo consideration. SATA 1, 2 or 3.
Onboard sound??????
Luck
Maybe I should just buy new ram....but 1600 again??
I'm floundering here...out of my depth
BTW...thanks all for trying to help me...and can I ask a question.....for those who know the thread....
What is your gut instinct? Do you think my ram is bad?
I'm floundering here...out of my depth
BTW...thanks all for trying to help me...and can I ask a question.....for those who know the thread....
What is your gut instinct? Do you think my ram is bad?
Your motherboard is fine, maybe a BIOS issue, but as spyknee mentioned, he has the same motherboard and no problems.
I would get new RAM, make sure it is listed on you motherboard QVL.
Several things about your current RAM suggest it will not work correctly on your motherboard.
Since your RAM is fairly new you should be able to return it and get the correct RAM for your motherboard.
I would get new RAM, make sure it is listed on you motherboard QVL.
Several things about your current RAM suggest it will not work correctly on your motherboard.
Since your RAM is fairly new you should be able to return it and get the correct RAM for your motherboard.
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?
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?
�� Quote: Originally Posted by hello people Maybe I should just buy new ram....but 1600 again??
I'm floundering here...out of my depth
BTW...thanks all for trying to help me...and can I ask a question.....for those who know the thread....
What is your gut instinct? Do you think my ram is bad?
I'm floundering here...out of my depth
BTW...thanks all for trying to help me...and can I ask a question.....for those who know the thread....
What is your gut instinct? Do you think my ram is bad?
The bios needs to be set proper for hardware you have. Turn off all the goodies that are suppose to conserve power or slow down the cpu for usage considerations.
Get a stable unchanging baseline. Hell I could just put up my cpu and ram settings but mine aren't yours. Go into bios set it to your hardware.
Look you have a 2.8GHz cpu, your multiplier is gonna be greater than 12. Your default base clck is 133. 133 x 12 =?
Cpu z has you at 1.5GHz. So to raise cpu to 2.8 you either increase the multiplier,
133 X 20 = ? or you increase the base clck, 140 X 12 =
Base clck x multiplier = CPU MHz
? X 12 = 2800MHz or
133 X ? = 2800MHz
Disable iest
Now based on what your ram ratio is, it will change the rams MHz setting based on the base clck.
Ram you put in the voltage manually, you set the initial timings manually, you dither with the rato untill it works with base clck to get 1600MHz setting.
base clck x dram ratio = ram MHz
133 x 10 to 2 = 1600MHz
Do not hold me to the exact math, illustration only. Do you have enough to experiment???
You see why I say theres a balance.
You buy another board but still do not set it up correctly.....................................
slow down and experiment, go in and make the numbers move. If its already broken, you can't hurt it. And if it is broken, expose yourself to what to expect with the replacement.
I can get all those figures as you say in CPUZ....I can get 2.8....I can get 1600 ram...everything works...
I just can not cold boot
Seriously...I have tweaked bios carefully...testing....cpuz tells me my cpu is at 2.8...cpuz tells me my ram is at 1600
I'll post you the screenshot to prove it!
So which setting do I adjust/ test to stop it from failing on a cold boot???
But a cold boot just doesn't work.
So I don't know what to do now
I just can not cold boot
Seriously...I have tweaked bios carefully...testing....cpuz tells me my cpu is at 2.8...cpuz tells me my ram is at 1600
I'll post you the screenshot to prove it!
So which setting do I adjust/ test to stop it from failing on a cold boot???
But a cold boot just doesn't work.
So I don't know what to do now
Frustrating I know.
You say that you can get hardware settings in, at the manufacturers specs, yes?
You can set the bios up and get POST, yes?
You say cold boots are the hang ups, how have you got passed the bsod?
If you can get booted to windows, do so and leave on all night. No hibernate just and S1 sleep. Make sure all the case connections are correct. Power button, reset button etc...
You say that you can get hardware settings in, at the manufacturers specs, yes?
You can set the bios up and get POST, yes?
You say cold boots are the hang ups, how have you got passed the bsod?
If you can get booted to windows, do so and leave on all night. No hibernate just and S1 sleep. Make sure all the case connections are correct. Power button, reset button etc...
Yes to all those questions I can get the hardware specs up.....how I get past BSOD on a cold boot......I just restart restart restart until the ******* boots. Sometimes I unplug HD cables and replug in.
Leave it on all night.........what's the reason for doing this?
Will it make my computer work on a cold boot?
Will it help in some way?
Leave it on all night.........what's the reason for doing this?
Will it make my computer work on a cold boot?
Will it help in some way?
May I offer a summary of where I'm at now?
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:
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
A-DATA OC Offical Website
Compatibility List
http://download.gigabyte.asia/FileLi...-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:
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
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:
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
A-DATA OC Offical Website
Compatibility List
http://download.gigabyte.asia/FileLi...-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:
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
GA-X58A-UD3R (rev. 2.0) - GIGABYTE
This is your board ?
Does not support 1600MHz ram?????????????????? or its not listed anyways. Goes from 1333 to 2200MHz??????
Use the FB bios listed. No BETA's from somewhere else.
http://ark.intel.com/Product.aspx?id=41447
your cpu, under dram specs only 800/1066 is listed???????????????????
Anyways,
You say you can get spec settings, So do so.
CPU at 2800MHZ at 1.3volts
RAM at 1600MHz at 1.7volts, timings all auto. 9-9-9-24 at 1T is what you would put in manually. Remove all sticks but 1, in slot closest CPU.
Run memtest on that stick, maybe two passes. Any errors, mark stick and put in a different one. Get 1 with no errors.
Remove sound card, vid card closet PCI slot to cpu.
Bios suggestions,
cpu warn temp enable
cpu fan fail enable
smart fan disable
ACPI suspend type S1
Soft Off by PWR But 4 sec off
PME...... disable
power on by ring disable
HPET disable
power on mouse and keyboard disable
Is your drive SATA 3 ready
SATA 3 firmware selection ??????
SATA Port 0-3 native mode enable
full screen logo disable
init display first choose pci-e if your card ready
Intel turbo boost disable
cpu eist disable
cpu vcore 1.3volts
dram volts 1.7
system mem multi manual ???? you want 1600MHz
performance enhance standard or lowest option
base clck get a 2800MHz cpu
Turning off Intel boost will only allow for a 20x multi, so
base clck x multi = 2800MHz
? x 20 = 2800MHz
base clck = 140
This is your board ?
Does not support 1600MHz ram?????????????????? or its not listed anyways. Goes from 1333 to 2200MHz??????
Use the FB bios listed. No BETA's from somewhere else.
http://ark.intel.com/Product.aspx?id=41447
your cpu, under dram specs only 800/1066 is listed???????????????????
Anyways,
You say you can get spec settings, So do so.
CPU at 2800MHZ at 1.3volts
RAM at 1600MHz at 1.7volts, timings all auto. 9-9-9-24 at 1T is what you would put in manually. Remove all sticks but 1, in slot closest CPU.
Run memtest on that stick, maybe two passes. Any errors, mark stick and put in a different one. Get 1 with no errors.
Remove sound card, vid card closet PCI slot to cpu.
Bios suggestions,
cpu warn temp enable
cpu fan fail enable
smart fan disable
ACPI suspend type S1
Soft Off by PWR But 4 sec off
PME...... disable
power on by ring disable
HPET disable
power on mouse and keyboard disable
Is your drive SATA 3 ready
SATA 3 firmware selection ??????
SATA Port 0-3 native mode enable
full screen logo disable
init display first choose pci-e if your card ready
Intel turbo boost disable
cpu eist disable
cpu vcore 1.3volts
dram volts 1.7
system mem multi manual ???? you want 1600MHz
performance enhance standard or lowest option
base clck get a 2800MHz cpu
Turning off Intel boost will only allow for a 20x multi, so
base clck x multi = 2800MHz
? x 20 = 2800MHz
base clck = 140
I think it would be better to just go and get 1066 ram
I don't want to OC my PC just so I can run ram that would give a barely noticeably increase in performance
.....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
I don't want to OC my PC just so I can run ram that would give a barely noticeably increase in performance
.....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
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 for their 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.
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 for their 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.
Good to hear.
Altho, I have to mention that I do not use XMP ram. But your bios are slightly different than mine, however.
Possibly just bad ram sticks or stick, only takes 1 to sour the works.
Please remember a bad bios set up can trash the hardware!
Have a sunny day.
Altho, I have to mention that I do not use XMP ram. But your bios are slightly different than mine, however.
Possibly just bad ram sticks or stick, only takes 1 to sour the works.
Please remember a bad bios set up can trash the hardware!
Have a sunny day.
Thanks spyknee...things are looking up
�� Quote: Originally Posted by hello people 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 for their 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.
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 for their 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.
No worries....thanks to your forum....I learned a lot about bios!
This morning was my first successful morning cold boot in about 9 days
This morning was my first successful morning cold boot in about 9 days
Không có nhận xét nào:
Đăng nhận xét