Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 2 of 16 FirstFirst 123412 ... LastLast
Results 11 to 20 of 151

Thread: x58A-UD3R Rev2 FB problems




  1. #11
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    dvd drive is ide.

    Going to run a memtest now to see what I can see.

    thanks

    I'll be back

    One other question....what is the difference between dual and triple channel Ram?

    Does dual channel mean that you can only have 2 sticks installed?
    Last edited by hello people; 10-13-2010 at 11:05 AM.

  2. #12
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    I have started to do all of the things advised....from another forum someone has advised me to run Windows SDK bug checking software. My crash dumps...from the last 3 or so days are as follows. It doesn't mean much to me...but to someone else it could mean something. I'll post it here and continue troubleshooting...

    Please note that on the 10th and 11 of Oct...I believe I had bios FB.....after that bios FC1

    Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
    Debug session time: Sun Oct 10 09:26:20.905 2010 (UTC + 8:00)
    System Uptime: 0 days 0:00:11.966
    Loading Kernel Symbols
    ***************

    BugCheck 50, {fffff8a0055da000, 0, fffff80002d6e533, 2}

    10th October 2010
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!HvpSetRangeProtection+a3 )

    Followup: MachineOwner

    1: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

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

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


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0
    fffff8a0055da000

    FAULTING_IP:
    nt!HvpSetRangeProtection+a3
    fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h

    MM_INTERNAL_CODE: 2

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff88003cc25f0 -- (.trap 0xfffff88003cc25f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a001367000 rbx=0000000000000000 rcx=fffff8a0055da009
    rdx=fffff8a0055da000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d6e533 rsp=fffff88003cc2780 rbp=0000000000d8b000
    r8=0000000000000000 r9=0000000000000004 r10=0000000000700065
    r11=0000000001ffffff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nt!HvpSetRangeProtection+0xa3:
    fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h ds:f000:fffff8a0`055da000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002b4e8f2 to fffff80002acf740

    STACK_TEXT:
    fffff880`03cc2488 fffff800`02b4e8f2 : 00000000`00000050 fffff8a0`055da000 00000000`00000000 fffff880`03cc25f0 : nt!KeBugCheckEx
    fffff880`03cc2490 fffff800`02acd82e : 00000000`00000000 00000000`00700065 00000000`00001000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
    fffff880`03cc25f0 fffff800`02d6e533 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`03cc2780 fffff800`02d5da68 : fffff8a0`05c64800 fffff8a0`0088c0c0 fffff8a0`31334d43 00000000`00000004 : nt!HvpSetRangeProtection+0xa3
    fffff880`03cc27e0 fffff800`02e36253 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`038d3000 : nt!HvFreeHive+0x108
    fffff880`03cc2860 fffff800`02d50d89 : fffff880`03cc2a00 fffff880`03cc2b20 ffffffff`80000254 fffff880`03cc2ac8 : nt! ?? ::NNGAKEGL::`string'+0x5a1cb
    fffff880`03cc2950 fffff800`02f4dbed : 00000000`00000000 fffff800`00000200 fffff880`03cc2ae0 fffff800`02c490eb : nt!CmpInitHiveFromFile+0x249
    fffff880`03cc2a70 fffff800`02d73c06 : 00000000`01c194d7 fffffa80`062229a0 00000000`00000080 fffffa80`04e89890 : nt!CmpLoadHiveThread+0x14d
    fffff880`03cc2d40 fffff800`02aadc26 : fffff880`009e9180 fffffa80`062229a0 fffff880`009f40c0 fffff880`0123ba90 : nt!PspSystemThreadStartup+0x5a
    fffff880`03cc2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!HvpSetRangeProtection+a3
    fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!HvpSetRangeProtection+a3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

    FAILURE_BUCKET_ID: X64_0x50_nt!HvpSetRangeProtection+a3

    BUCKET_ID: X64_0x50_nt!HvpSetRangeProtection+a3

    Followup: MachineOwner



    From 11th October

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\101110-20030-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
    Debug session time: Mon Oct 11 17:53:50.624 2010 (UTC + 8:00)
    System Uptime: 0 days 0:00:11.686
    Loading Kernel Symbols
    .................................................. .............
    ................................................
    Loading User Symbols
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, 1097, 0, fffff8a005785800}

    GetPointerFromAddress: unable to read from fffff80002d090e0
    GetUlongFromAddress: unable to read from fffff80002c771b0
    GetUlongFromAddress: unable to read from fffff80002c771b0
    Probably caused by : ntkrnlmp.exe ( nt!HvFreeHive+147 )

    Followup: MachineOwner
    ---------

    1: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 0000000000001097, (reserved)
    Arg3: 0000000000000000, Memory contents of the pool block
    Arg4: fffff8a005785800, Address of the block of pool being deallocated

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

    GetUlongFromAddress: unable to read from fffff80002c771b0
    GetUlongFromAddress: unable to read from fffff80002c771b0

    POOL_ADDRESS: fffff8a005785800

    BUGCHECK_STR: 0xc2_7

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80002c0460e to fffff80002ad1740

    STACK_TEXT:
    fffff880`040c2728 fffff800`02c0460e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx
    fffff880`040c2730 fffff800`02d5faa7 : fffff8a0`00ca7b80 fffff8a0`0079c0c0 fffff8a0`31334d43 00000000`00000004 : nt!ExDeferredFreePool+0x11eb
    fffff880`040c27e0 fffff800`02e38253 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`038d5000 : nt!HvFreeHive+0x147
    fffff880`040c2860 fffff800`02d52d89 : fffff880`040c2a00 fffff880`040c2b20 ffffffff`80000258 fffff880`040c2ac8 : nt! ?? ::NNGAKEGL::`string'+0x5a1cb
    fffff880`040c2950 fffff800`02f4fbed : 00000000`00000000 fffff800`00000200 fffff880`040c2ae0 fffff800`02c4b0eb : nt!CmpInitHiveFromFile+0x249
    fffff880`040c2a70 fffff800`02d75c06 : 00000000`01b02f96 fffffa80`04eb4370 00000000`00000080 fffffa80`04e89890 : nt!CmpLoadHiveThread+0x14d
    fffff880`040c2d40 fffff800`02aafc26 : fffff880`009e9180 fffffa80`04eb4370 fffff880`009f40c0 fffff880`0122ba90 : nt!PspSystemThreadStartup+0x5a
    fffff880`040c2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!HvFreeHive+147
    fffff800`02d5faa7 8b8c2480000000 mov ecx,dword ptr [rsp+80h]

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!HvFreeHive+147

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

    FAILURE_BUCKET_ID: X64_0xc2_7_nt!HvFreeHive+147

    BUCKET_ID: X64_0xc2_7_nt!HvFreeHive+147

    Followup: MachineOwner
    ---------

    From the 12th October 2010

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\101210-20997-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
    Debug session time: Tue Oct 12 06:08:06.156 2010 (UTC + 8:00)
    System Uptime: 0 days 0:00:11.218
    Loading Kernel Symbols
    .................................................. .............
    ...............................................
    Loading User Symbols
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005, fffff80002db0548, fffff880033859f8, fffff88003385260}

    Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceKeyControlBlock+5c )

    Followup: MachineOwner
    ---------

    4: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002db0548, The address that the exception occurred at
    Arg3: fffff880033859f8, Exception Record Address
    Arg4: fffff88003385260, Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt!CmpDereferenceKeyControlBlock+5c
    fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h]

    EXCEPTION_RECORD: fffff880033859f8 -- (.exr 0xfffff880033859f8)
    ExceptionAddress: fffff80002db0548 (nt!CmpDereferenceKeyControlBlock+0x00000000000000 5c)
    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
    ---------

  3. #13
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    This part couldn't fit in the original post....sorry...

    From the 13th October 2010


    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\101310-21871-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
    Debug session time: Wed Oct 13 06:11:56.061 2010 (UTC + 8:00)
    System Uptime: 0 days 0:00:12.029
    Loading Kernel Symbols
    .................................................. .............
    ...................
    Loading User Symbols
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffff8800403f004, 0, fffff80002a82a87, 0}


    Could not read faulting driver name
    Probably caused by : Npfs.SYS ( Npfs!NpCreateNamedPipePrefix+68 )

    Followup: MachineOwner
    ---------

    6: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

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

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


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb00e0
    fffff8800403f004

    FAULTING_IP:
    nt!SepPrivilegeCheck+37
    fffff800`02a82a87 8b19 mov ebx,dword ptr [rcx]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: smss.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff8800403e370 -- (.trap 0xfffff8800403e370)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800403f004
    rdx=0000000000000726 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a82a87 rsp=fffff8800403e500 rbp=fffffa8006097e60
    r8=0000000000000801 r9=0000000000000801 r10=000000000000000d
    r11=0000000e60b1e890 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nt!SepPrivilegeCheck+0x37:
    fffff800`02a82a87 8b19 mov ebx,dword ptr [rcx] ds:d000:fffff880`0403f004=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002af8f14 to fffff80002a78740

    STACK_TEXT:
    fffff880`0403e208 fffff800`02af8f14 : 00000000`00000050 fffff880`0403f004 00000000`00000000 fffff880`0403e370 : nt!KeBugCheckEx
    fffff880`0403e210 fffff800`02a7682e : 00000000`00000000 00000000`00000000 fffff880`00961000 fffff800`02aaa75b : nt! ?? ::FNODOBFM::`string'+0x42837
    fffff880`0403e370 fffff800`02a82a87 : 0000000e`60b1e890 00000000`000001f1 fffff880`0403e6d0 fffff800`02d7dfce : nt!KiPageFault+0x16e
    fffff880`0403e500 fffff800`02d7dfce : 00000000`00000000 00000000`00000000 00000000`00000010 fffff880`0149d000 : nt!SepPrivilegeCheck+0x37
    fffff880`0403e520 fffff880`0149d04c : fffffa80`05ef6890 00000000`00000000 fffffa80`06097e60 fffffa80`04ea5850 : nt!SePrivilegeCheck+0x2e
    fffff880`0403e560 fffff880`0149c6d7 : 00000000`00f80032 00000000`00000002 00000000`00000000 00000000`00000000 : Npfs!NpCreateNamedPipePrefix+0x68
    fffff880`0403e610 fffff800`02d7b807 : 00000000`80000005 7ffff800`02d7b260 fffff800`02d7b260 fffffa80`04f2c610 : Npfs!NpFsdCreate+0x123
    fffff880`0403e740 7ffff800`02d71e84 : fffffa80`05ef6890 00000000`80000000 7ffffa80`04ea6010 00000000`00000001 : nt!IopParseDevice+0x5a7
    fffff880`0403e8d0 fffffa80`05ef6890 : 00000000`80000000 7ffffa80`04ea6010 00000000`00000001 fffffa80`00000040 : 0x7ffff800`02d71e84
    fffff880`0403e8d8 00000000`80000000 : 7ffffa80`04ea6010 00000000`00000001 fffffa80`00000040 7ffff880`0403ea30 : 0xfffffa80`05ef6890
    fffff880`0403e8e0 7ffffa80`04ea6010 : 00000000`00000001 fffffa80`00000040 7ffff880`0403ea30 fffff880`0403e940 : 0x80000000
    fffff880`0403e8e8 00000000`00000001 : fffffa80`00000040 7ffff880`0403ea30 fffff880`0403e940 fffffa80`04f2c610 : 0x7ffffa80`04ea6010
    fffff880`0403e8f0 fffffa80`00000040 : 7ffff880`0403ea30 fffff880`0403e940 fffffa80`04f2c610 00000000`00000000 : 0x1
    fffff880`0403e8f8 7ffff880`0403ea30 : fffff880`0403e940 fffffa80`04f2c610 00000000`00000000 fffff880`0403e928 : 0xfffffa80`00000040
    fffff880`0403e900 fffff880`0403e940 : fffffa80`04f2c610 00000000`00000000 fffff880`0403e928 fffff801`00000000 : 0x7ffff880`0403ea30
    fffff880`0403e908 fffffa80`04f2c610 : 00000000`00000000 fffff880`0403e928 fffff801`00000000 00000000`00000000 : 0xfffff880`0403e940
    fffff880`0403e910 00000000`00000000 : fffff880`0403e928 fffff801`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`04f2c610


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    Npfs!NpCreateNamedPipePrefix+68
    fffff880`0149d04c 84c0 test al,al

    SYMBOL_STACK_INDEX: 5

    SYMBOL_NAME: Npfs!NpCreateNamedPipePrefix+68

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Npfs

    IMAGE_NAME: Npfs.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114

    FAILURE_BUCKET_ID: X64_0x50_Npfs!NpCreateNamedPipePrefix+68

    BUCKET_ID: X64_0x50_Npfs!NpCreateNamedPipePrefix+68

    Followup: MachineOwner
    ---------

  4. #14
    Join Date
    Aug 2009
    Location
    Birmingham,Great Britain
    Posts
    9,250

    Default Re: x58A-UD3R Rev2 FB problems

    i have no idea what those codes mean,maybe lsdmeasap will shed some light on it,in the meantime have you tried with another set/brand of ram?? im still thinking that its ram thats causing it,esp the cold boot ups
    Gigabyte z77x UP4-TH F11c Modded Bios
    Intel i7 3770k 24/7@4.8ghz 1.38v Turbo llc +0.165v dvid multithreading enabled
    Samsung Green(MV-3V4G3D/US) 8GB @2133mhz 9-10-10-21-1t 1.55v
    Thermalright Silver Arrow Cpu Cooler
    1xSamsung 840 pro 256 Gb SSD windows 8.1 pro 64bit
    1xSamsung f4 HD204UI 2tb hard drive Storage
    Powercolor 7970 3gb V3 @1150mhz core/1700mhz mem,1.150v Accelero aftermarket air cooler 55c max
    Razer Lycosa Keyboard
    Logitech X-530 5.1 Speakers
    Lite-On iHAS124-19 24x Sata DVDRW
    K-World Hybrid DVB-T 210SE Digital T.V Card
    L.G E2260V L.E.D 1920x1080 Monitor
    Xfx Pro 750w silver rated Psu 80+
    Fractal Arc Midi Case

    http://i38.tinypic.com/14myvfa.jpg x58 ud5 <=3.8ghz + 4.2ghz Overclock Template!!
    http://www.youtube.com/user/warren304#p/u Visit Me On Youtube

    Lots Of Gaming Videos With X58 Ud5 System And Gpu On My Youtube Channel!!
    Just Uploaded New Battlefield 4 Video!!!!!!!!!!!!!!!!!!!!!!

  5. #15
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    Why would the ram cause cold boots but run perfectly once booted?

    I haven't tried another set of ram yet...just not doable right now. This weekend I am going to the shop...I'll be very tempted to buy another board...

    the x58A-UD3R is infamous

  6. #16
    Join Date
    Aug 2009
    Location
    Birmingham,Great Britain
    Posts
    9,250

    Default Re: x58A-UD3R Rev2 FB problems

    ive seen it happen alot with certain brands of ram,i dont know what it is exactly but once its warmed up it runs fine,maybe its not fully supported in the bios yet? is that brand on gigabytes qvl list? i dont think its the mb,id go for that make of ram or bios or combination of both
    Gigabyte z77x UP4-TH F11c Modded Bios
    Intel i7 3770k 24/7@4.8ghz 1.38v Turbo llc +0.165v dvid multithreading enabled
    Samsung Green(MV-3V4G3D/US) 8GB @2133mhz 9-10-10-21-1t 1.55v
    Thermalright Silver Arrow Cpu Cooler
    1xSamsung 840 pro 256 Gb SSD windows 8.1 pro 64bit
    1xSamsung f4 HD204UI 2tb hard drive Storage
    Powercolor 7970 3gb V3 @1150mhz core/1700mhz mem,1.150v Accelero aftermarket air cooler 55c max
    Razer Lycosa Keyboard
    Logitech X-530 5.1 Speakers
    Lite-On iHAS124-19 24x Sata DVDRW
    K-World Hybrid DVB-T 210SE Digital T.V Card
    L.G E2260V L.E.D 1920x1080 Monitor
    Xfx Pro 750w silver rated Psu 80+
    Fractal Arc Midi Case

    http://i38.tinypic.com/14myvfa.jpg x58 ud5 <=3.8ghz + 4.2ghz Overclock Template!!
    http://www.youtube.com/user/warren304#p/u Visit Me On Youtube

    Lots Of Gaming Videos With X58 Ud5 System And Gpu On My Youtube Channel!!
    Just Uploaded New Battlefield 4 Video!!!!!!!!!!!!!!!!!!!!!!

  7. #17
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    I think it is on the list...no wait...I just had a look...it is not on the list:

    http://download.gigabyte.asia/FileLi...-ud3r_v2.0.pdf

    On the list it says the ADATA Ram it DOES recognise is:

    AX3U 1600GB2G9AG

    But my ADATA Ram is:

    AX3U 1600GB2G91G

    Slight difference.

    Did I mention that Gigabyte replied to my support ticket and sent me the rar for the latest driver? It' FC2....I haven't installed it....maybe it is updated to recognise my Ram?

  8. #18
    Join Date
    Aug 2009
    Location
    Birmingham,Great Britain
    Posts
    9,250

    Default Re: x58A-UD3R Rev2 FB problems

    you mean the latest bios? if so then flash to that and see if it fixes it,they might not have included it in any bios's yet so i would try the bios they sent you first
    Gigabyte z77x UP4-TH F11c Modded Bios
    Intel i7 3770k 24/7@4.8ghz 1.38v Turbo llc +0.165v dvid multithreading enabled
    Samsung Green(MV-3V4G3D/US) 8GB @2133mhz 9-10-10-21-1t 1.55v
    Thermalright Silver Arrow Cpu Cooler
    1xSamsung 840 pro 256 Gb SSD windows 8.1 pro 64bit
    1xSamsung f4 HD204UI 2tb hard drive Storage
    Powercolor 7970 3gb V3 @1150mhz core/1700mhz mem,1.150v Accelero aftermarket air cooler 55c max
    Razer Lycosa Keyboard
    Logitech X-530 5.1 Speakers
    Lite-On iHAS124-19 24x Sata DVDRW
    K-World Hybrid DVB-T 210SE Digital T.V Card
    L.G E2260V L.E.D 1920x1080 Monitor
    Xfx Pro 750w silver rated Psu 80+
    Fractal Arc Midi Case

    http://i38.tinypic.com/14myvfa.jpg x58 ud5 <=3.8ghz + 4.2ghz Overclock Template!!
    http://www.youtube.com/user/warren304#p/u Visit Me On Youtube

    Lots Of Gaming Videos With X58 Ud5 System And Gpu On My Youtube Channel!!
    Just Uploaded New Battlefield 4 Video!!!!!!!!!!!!!!!!!!!!!!

  9. #19
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    Yep...roger that, makes sense to me

  10. #20
    Join Date
    Oct 2010
    Location
    Hong Kong
    Posts
    76

    Default Re: x58A-UD3R Rev2 FB problems

    UPDATE:

    Tested ram last night (all 3 strips) for 6 passes with memtest....2 erros reported.

    I am testing individual strips now....will take some hours

    btw....Gigabyte sent me a new bios - FC2....I can send it to anyone who wants to test it on their system

    thanks

Page 2 of 16 FirstFirst 123412 ... LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •