Announcement

Collapse
No announcement yet.

x58A-UD3R Rev2 FB problems

Collapse
X
Collapse
 
  • Page of 11
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 11 template Next
  • #1

    x58A-UD3R Rev2 FB problems

    Hi...I've been in and out of this forum over the past week or so trying to work out how to fix issues with the x58A-UD3R Rev 2 FB...

    My rig:
    i7 930 2.8g
    Gigabyte X58A-UD3R Rev2.0
    HIS ATI pcie HD5670
    Seagate 3.5 Sata2 1TB x2
    ADATA 2g DDR3 1600 3x2g
    Zalman CNPS10X Quiet CPU Cooler
    Cooler Master Silent Pro M700 PSU
    Windows 7 Home Premium 64b

    What happened:

    1. Install W7 64bit...no problem
    2. Tweak stuff in services/ startup...the usual things
    3. No overclocking...I don't want to OC it
    4. Noticed that 2 of my 3 RAM sticks were not being recognised
    5. Online solution seemed to be to update bios
    6. Did that...updated to FB bios...all RAM recognised fine but...
    7. Started experiencing cold boot failures
    8. First time cold boot failure. I turn off, unplug HD cables, plug back in, turn on and it's ok. And it's been doing this for the last 2 days on a cold boot.

    This is where I am now. I'm of course super keen on solving these issues and believe that I can and will be able to without taking it back to the shop.

    My next plan is to flash bios with FC1....as I have read it has been successful for some with my cold boot failure. I really hope it works. I'll be doing it tonight. Also....CPU pins....I have checked them once....I didn't see any bent ones....but I am prepared to look again and to take photos if need be.

    I'll be happy to provide any information that is required to fix my particular problem for my machine.

    Also....1 more thing. I am willing to buy a replacement mobo...(if nothing works) (though I think a solution will be reached)....so can anyone suggest a mobo that would be appropriate and would marry up with the rest of my hardware?

    thanks very much
    Last edited by hello people; 10-12-2010, 12:31 AM.
    Tags: None
  • #2
    Re: x58A-UD3R Rev2 FB problems

    Yes please take photos of the CPU socket if you are not sure, do so in Macro mode if your camera has it and take them in a well lit room with no flash, taken from several angles.

    This can also be incorrect voltages, are you setting voltages yourself manually?

    Comment

    • #3
      Re: x58A-UD3R Rev2 FB problems

      About the photos...sure

      I am not setting voltages manually, no...I can give full bios specs later tonight if need be.

      thanks

      ps...I just had a thought after talking to a friend....he mentioned that probably the best way to solve this problem is not to flash bios like this with flash after flash update....but to flash the latest bios and then do a complete reinstall of Windows 7 so that it can recognise and 'connect' to the latest bios right from the very start.......as opposed to being installed on an 'out of date' bios and repeatedly flashed up to the latest bios.

      Does that make any practical sense?
      Last edited by hello people; 10-12-2010, 03:20 AM.

      Comment

      • #4
        Re: x58A-UD3R Rev2 FB problems

        Ahh well since you are not setting voltages yourself it could be either that or bent pins maybe.

        Windows has nothing to do with the BIOS, nor do they interact in any real way in regards to this, so no need to reinstall windows at all. Just flash the BIOS you want to use and go from there.

        If you are sure you have no bent pins that's fine, don't remove the CPU anymore unless you already are doing so. If you're sure we'll try to get your voltages right and see if that fixes it, if not we'll have to check your socket later on to be sure.

        Give me a link to your memory and then your current full BIOS settings and I'll advise back, template is in my signature.

        Comment

        • #5
          Re: x58A-UD3R Rev2 FB problems

          Ok thanks...I have just flashed to FC1...and was thinking about flashing the backup bios (which is still FA at the moment).

          I will get all the bios specs and post them up here.

          Then I think I will turn my PC off for an hour and a half or so and try a cold boot.

          Comment

          • #6
            Re: x58A-UD3R Rev2 FB problems

            Here's the results of my bios.....some entries I couldn't locate...1 or 2

            <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";} </style> <![endif]-->
            Advanced CPU Features:</pre>
            CPU Clock Ratio ................................ [21x]</pre>
            Intel(R) Turbo Boost Tech .................. [Enabled]</pre>
            CPU Cores Enabled ............................ [All]</pre>
            CPU Multi Threading .......................... [Enabled]</pre>
            CPU Enhanced Halt (C1E) ................... [Enabled]</pre>
            C3/C6/C7 State Support .................... [Disabled]</pre>
            CPU Thermal Monitor ......................... [Enabled]</pre>
            CPU EIST Function ............................ [Enabled]</pre>
            Virtualization Technology ................... [n/a no entry for this] << Disabled if you do not use Vmware or Virtual PC Programs</pre>
            Bi-Directional PROCHOT ..................... [Enabled]</pre>
            </pre>
            </pre>
            Uncore & QPI Features:</pre>
            QPI Link Speed .............................. 4.8Ghz</pre>
            Uncore Frequency .......................... (2667mhz)</pre>
            Isonchronous Frequency ..................[n/a no entry for this]</pre>
            </pre>
            </pre>
            Standard Clock Control:</pre>
            Base Clock (BCLK) Control ................ [Disabled]</pre>
            BCLK Frequency (MHz) .....................133mhz</pre>
            PCI Express Frequency (MHz) ........... [Auto]</pre>
            </pre>
            C.I.A.2 [n/a no entry for this]</pre>
            </pre>
            Advanced Clock Control:</pre>
            CPU Clock Drive ..............................[700mV]</pre>
            PCI Express Clock Drive ................... [900mV]</pre>
            CPU Clock Skew ............................. [0ps]</pre>
            IOH Clock Skew ............................. [0ps]</pre>
            </pre>
            </pre>
            Advanced DRAM Features:</pre>
            Performance Enhance ...................... [Turbo]</pre>
            Extreme Memory Profile (X.M.P) ......... [n/a no entry for this]</pre>
            System Memory Multiplier (SPD) ........ [AUTO]</pre>
            DRAM Timing Selectable (SPD) .......... [Auto]</pre>
            </pre>
            Channel A + B + C</pre>
            </pre>
            Channel A Timing Settings:</pre>
            ##Channel A Standard Timing Control##</pre>
            CAS Latency Time ......................</pre>
            tRCD .......................................</pre>
            tRP .........................................</pre>
            tRAS .......................................</pre>
            </pre>
            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</pre>
            XtremeSystems Forums - View Single Post - Gigabyte EX58-UD5/Extreme Discussion Thread</pre>
            </pre>
            ##Channel A Advanced Timing Control##</pre>
            tRC ........................................ (Should be = tRAS + tRP or above for stability)</pre>
            tRRD .......................................</pre>
            tWTR ...................................... (Must be Write to Read Delay/Same Rank - (tWL + 4)</pre>
            tWR ........................................</pre>
            tWTP ....................................... (tWTP Must = tWR + tWL + 4)</pre>
            tWL ........................................ (tWL Must be CAS Latency -1)</pre>
            tRFC .......................................</pre>
            tRTP .......................................</pre>
            tFAW ......................................</pre>
            Command Rate (CMD) ................</pre>
            </pre>
            I gues config for this was:</pre>
            7 7 7 20 4 19 60 1</pre>
            </pre>
            ##Channel A Misc Timing Control##</pre>
            Round Trip Latency ...................47</pre>
            </pre>
            B2B CAS Delay ..........................- (Auto)</pre>
            </pre>
            </pre>
            Advanced Voltage Control:</pre>
            </pre>
            CPU</pre>
            Load Line Calibration ................. [Auto]</pre>
            CPU Vcore ...............................1.25000V (Auto)</pre>
            QPI/VTT Voltage 1.175v </pre>
            CPU PLL 1.800v .......................(Auto)</pre>
            </pre>
            MCH/ICH</pre>
            PCIE 1.500v ...........................</pre>
            QPI PLL 1.100v .......................</pre>
            IOH Core 1.100v .....................</pre>
            ICH I/O 1.500v .......................</pre>
            ICH Core 1.1v ........................</pre>
            </pre>
            DRAM</pre>
            DRAM Voltage 1.500v (Auto)..............</pre>
            DRAM Termination 0.750v [AUTO]</pre>
            Ch-A Data VRef. 0.750v [AUTO]</pre>
            Ch-B Data VRef. 0.750v [AUTO]</pre>
            Ch-C Data VRef. 0.750v [AUTO]</pre>
            Ch-A Address VRef. 0.750v [AUTO]</pre>
            Ch-B Address VRef. 0.750v [AUTO]</pre>Ch-C Address VRef. 0.750v [AUTO]


            For the data that differed from the template I made the font red....hopefully that will show up in this post.

            My RAM:
            http://oc.adata.com.tw/product-series.asp?sid=02


            Known as:
            ADATA 2g DDR3 1600 Longdimm Cl9-9-9-24 Ram

            thanks
            Last edited by hello people; 10-12-2010, 05:33 AM.

            Comment

            • #7
              Re: x58A-UD3R Rev2 FB problems

              looking at your settings you need to change these

              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
              Gigabyte z77x UP4-TH F11c Modded Bios
              Intel i7 3770k 24/[email protected] 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!!!!!!!!!!!!!!!!!!!!!!

              Comment

              • #8
                Re: x58A-UD3R Rev2 FB problems

                I'll give it a shot then, thanks.

                I have input those values....and will wait until the morning to see if it can cold boot.

                thanks again...
                Last edited by hello people; 10-12-2010, 08:34 AM.

                Comment

                • #9
                  Re: x58A-UD3R Rev2 FB problems

                  Well it's morning and my cold boot problems are still here. The PC tried to boot 3 times before giving me a blue screen with these details:

                  Stop: 0x000000FC (0xFFFFF8A0000CA588, 0x8CA00001938B6963, 0xFFFFF8802B32AF0, 0x0000000000000002)

                  After encountering the blue screen, I shut down (and in what always seems to help the computer to boot up) I unplugged the HD cables power and sata, replugged in...booted up.

                  Any help or tips regarding this blue screen message?

                  Some hardware driver conflict?

                  Could it be my old DVD drive? It's the oldest part of this build.

                  I dunno....any help would be great

                  thanks

                  Comment

                  • #10
                    Re: x58A-UD3R Rev2 FB problems

                    is your dvd drive ide or sata? its most likely a driver or ram/bios problem imo
                    Gigabyte z77x UP4-TH F11c Modded Bios
                    Intel i7 3770k 24/[email protected] 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!!!!!!!!!!!!!!!!!!!!!!

                    Comment

                    • #11
                      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-12-2010, 10:05 PM.

                      Comment

                      • #12
                        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
                        ---------

                        Comment

                        • #13
                          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
                          ---------

                          Comment

                          • #14
                            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/[email protected] 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!!!!!!!!!!!!!!!!!!!!!!

                            Comment

                            • #15
                              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

                              Comment

                              Previous 1 2 3 4 11 template Next
                              Working...
                              X