After you install all updates and drivers, hopefully all is well, but try to set all Bios setting to factory default and then if you decide to overclock, see where it will let you without recieving any errors or blue screen. I hope you have resolved your problems.
Yes, I was talking about what the intel diagnostic gave back was all. Thanks for the max temp, I was interested in that.
I will upload the full bsod info log that tool gets, but ignore the dmp file, its from before I deleted that driver.
I will post my new voltages in a bit.
Here is the log.
Ok so, I found the reason for the crashing/restarting. Now I just want to know why its doing this and if its normal. Should I RMA?
The reason is because my CPU Voltage was Set at Auto, so it would idle up and down when I did different tasks. However when it dropped below a certain voltage, it would restart, no BSOD, no Dump.
Here is the results after I did some testing, what are your thoughts.
Code:Auto & Normal = Restart after Load 0.750 -> 0.950 = Restart after post 1.000 = BSOD on Load 1.050 = BSOD after Hard Lock, right after desktop loads 1.100+ = Stable
If the processor is causing so many problems for you return it and get a new one to see if the problem persists, it should be under warranty.
Are you overclocking anything?
What is your BIOS version?
Need to know the answers to these questions.
What are you using to get the voltages?
Good work on finding this issue.
There might be an easy fix, will be able to confirm with more information.
At this point you have two options.
1. RMA the CPU, you may find that the new CPU is doing the same thing. Might be the BIOS settings that are causing this to happen.
2. Do a little testing and see what the cause is, there are settings that can compensate for CPU low voltage.
Then you can make your decision if you want to RMA the CPU.
If you can post the CPUZ tabs and BIOS voltage settings requested previously, it will be much easier to analyze your issue.
Kind of shooting in the dark now, with the above info or your BIOS template settings, this will be much easier.
At this info level, a shot in the dark would be to increase the CPU offset voltage by small amounts until the CPU is stable.
You aren't the first person with this issue for the 2500K and Gigabyte board.
From you last crash files.
Event Log Apps:
Several of these indicating Windows Updates aren't installing.Code:Event[1]: Log Name: Application Source: Windows Error Reporting Date: 2012-03-25T09:32:51.000 Event ID: 1001 Task: N/A Level: Information Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Test-PC Description: Fault bucket 2847416715, type 5 Event Name: RADAR_PRE_LEAK_WOW64 Response: Not available Cab Id: 0 Problem signature: P1: League of Legends.exe P2: 1.0.0.136 P3: 6.1.7601.2.1.0 P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Users\Bryon\AppData\Local\Temp\RDR164E.tmp\empty.txt These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: fc8124b1-767e-11e1-ad10-50e549cfa478 Report Status: 0
This is in reference to your CPU issue.Code:Event[6]: Log Name: Application Source: Microsoft-Windows-CAPI2 Date: 2012-03-25T09:10:05.709 Event ID: 4107 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Test-PC Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
The USB3 controller is failing, may be the driver.Code:Event[16]: Log Name: Application Source: Microsoft-Windows-WMI Date: 2012-03-25T09:09:25.000 Event ID: 10 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Test-PC Description: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Code:Event[84]: Log Name: Application Source: MsiInstaller Date: 2012-03-25T08:58:10.000 Event ID: 11729 Task: N/A Level: Information Opcode: Info Keyword: Classic User: S-1-5-21-2527555929-1053617246-259929116-1000 User Name: Test-PC\Bryon Computer: Test-PC Description: Product: Etron USB3.0 Host Controller -- Configuration failed.
Last edited by Dave76; 26 Mar 2012 at 03:30.
Are you overclocking anything? - No
What is your BIOS version? - F11
What are you using to get the voltages? - Setting them manually in the Bios and checking them in HWMonitor
Not sure how to increase my CPU Offset voltage, So I will wait untill I hear back, my CPU info pics will be posted below.
Attachment 204525
Attachment 204526
Attachment 204527
Attachment 204528
Attachment 204529
Your motherboard manual: GA-Z68X-UD3H-B3 (rev. 1.3)
Look on the lower left corner of your motherboard, there is a circle with the revision number on the left side, it will say 'REV:1.0' or 'REV: 1.3'. Let us know which revision you have.
CPUZ and your BIOS are showing a high Vcore for stock, non-OC'ed CPU settings.
Your RAM is default 1.50v and is set to 1.620v according to your BIOS screen shot, this may not be necessary.
Also, your VTT is low for 16GB RAM.
These don't appear to be stock/default settings.
If you have changed these settings in the BIOS, what other changes have you made?
Please answer this before you change any BIOS settings, without knowing what all the settings have been changed to before making any adjustments, can cause system instability.
FYI, changing Vcore on these boards is not a good idea, best to set Vcore to 'Normal' and adjust it with the CPU Voltage Offset (DVID).
Page #43&44 in your motherboard manual.
'Advanced Voltage Settings'
'CPU Vcore' (should be set to 'Auto') - let us know what the exact setting was before you change it to 'Normal'.
You should then be able to access 'Dynamic Vcore(DVID)', set at +0.050v, check for stability, if stable drop by 0.010v until unstable, then back up 0.010v.
Last edited by Dave76; 27 Mar 2012 at 01:00.
Hi bryonM
I had exactly the same problem with this Board (Rev. 1.3) and tried everything.
In the end, the solution was a twisted contact pin in the cpu socket.
Maybe you have the same problem.
Be sure all pins are in correct position, because i had to look twice to find the twisted one.
Good Luck
Greetings from Germany
I have Rev: 1.3
Everything in the BIOS is stock EXCEPT for the Vcore voltage which I had to switch off of Auto or normal and manually set to 1.350v to keep my system stable and the Ram voltage because I read a few reviews on that ram that the 16gb needs a bit more voltage to keep stable.
I will set Vcore to Normal and then try and find that DVID and do what you suggested.
So because its NOT stable on normal, I should increase the CVID by +0.010 untill stable?
Bryon
Hi, you had said:
So just waiting to hear back from you before I make an changes.Please answer this before you change any BIOS settings, without knowing what all the settings have been changed to before making any adjustments, can cause system instability.
Quote