Crashing/Restarting - Error 41 - No BSOD - New Build

[rsedgarroman]

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.

 

[bryonM]

FYI, your CPU max temp is 77.6°C
Intel® Core™ i5-2500K Processor
Tcase (the CPU case) max temp is 72.6°C, add 5°C for the CPU core temps 77.6°C.

Sometimes with 4GB RAM or more you may need to adjust the settings, usually voltage.
Also due to various combinations of issues your CPU idle voltage may be a slight bit too low.
In your case I would adjust the RAM settings first, If you can post the info requested in my last post we can look at the RAM and IMC (Integrated Memory Controller) settings.

These are important setting: Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Update all you motherboard drivers from the Gigabyte site, this will help rule out any driver issues.

This crash is blaming AppleCharger.sys.
Did you uninstall the the Gigabyte utility: AppleCharger.sys
This could be caused by the RAM settings.

*******************************************************************************
*                                                                             *
*                        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: ffffffffffffffd0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800030e9f5c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
 
Debugging Details:
------------------
 
 
Could not read faulting driver name
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003312100
 ffffffffffffffd0 
 
FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`030e9f5c f0480fc11f      lock xadd qword ptr [rdi],rbx
 
MM_INTERNAL_CODE:  0
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0x50
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
TRAP_FRAME:  fffff880035bd7a0 -- (.trap 0xfffff880035bd7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000034 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030e9f5c rsp=fffff880035bd930 rbp=0000000000000020
 r8=fffffa8008aedb10  r9=fffffa80036c6248 r10=fffffa80036eebf0
r11=fffff880035bd980 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`030e9f5c f0480fc11f      lock xadd qword ptr [rdi],rbx ds:0010:00000000`00000000=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff8000308d25c to fffff800030e0d40
 
STACK_TEXT:  
fffff880`035bd638 fffff800`0308d25c : 00000000`00000050 ffffffff`ffffffd0 00000000`00000001 fffff880`035bd7a0 : nt!KeBugCheckEx
fffff880`035bd640 fffff800`030dee6e : 00000000`00000001 ffffffff`ffffffd0 fffff6fb`7ea00100 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`035bd7a0 fffff800`030e9f5c : fffff8a0`07e26560 fffff880`035bdb40 fffff880`035bda98 fffff800`00000030 : nt!KiPageFault+0x16e
fffff880`035bd930 fffff880`04830a93 : 00000000`00000020 fffff880`035bda98 00000000`001f01ff fffff880`048321c0 : nt!ObfDereferenceObject+0x2c
fffff880`035bd990 00000000`00000020 : fffff880`035bda98 00000000`001f01ff fffff880`048321c0 fffff800`035aa7c0 : AppleCharger+0x1a93
fffff880`035bd998 fffff880`035bda98 : 00000000`001f01ff fffff880`048321c0 fffff800`035aa7c0 fffff8a0`0139b930 : 0x20
fffff880`035bd9a0 00000000`001f01ff : fffff880`048321c0 fffff800`035aa7c0 fffff8a0`0139b930 00000000`00000000 : 0xfffff880`035bda98
fffff880`035bd9a8 fffff880`048321c0 : fffff800`035aa7c0 fffff8a0`0139b930 00000000`00000000 00000000`00000000 : 0x1f01ff
fffff880`035bd9b0 fffff800`035aa7c0 : fffff8a0`0139b930 00000000`00000000 00000000`00000000 fffff880`035bda90 : AppleCharger+0x31c0
fffff880`035bd9b8 fffff8a0`0139b930 : 00000000`00000000 00000000`00000000 fffff880`035bda90 fffff800`0334a87c : nt!PnpDeviceClassNotifyList+0xa0
fffff880`035bd9c0 00000000`00000000 : 00000000`00000000 fffff880`035bda90 fffff800`0334a87c 00000000`00000202 : 0xfffff8a0`0139b930
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
AppleCharger+1a93
fffff880`04830a93 ??              ???
 
SYMBOL_STACK_INDEX:  4
 
SYMBOL_NAME:  AppleCharger+1a93
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: AppleCharger
 
[COLOR=red]IMAGE_NAME:  AppleCharger.sys[/COLOR]
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4d2ad809
 
FAILURE_BUCKET_ID:  X64_0x50_AppleCharger+1a93
 
BUCKET_ID:  X64_0x50_AppleCharger+1a93
 
Followup: MachineOwner
---------

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.

 

[bryonM]

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.

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

 

[rsedgarroman]

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.

 

[Dave76]

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:

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

Several of these indicating Windows Updates aren't installing.

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.

This is in reference to your CPU issue.

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.

The USB3 controller is failing, may be the driver.

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.

 

[bryonM]

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.

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.

View attachment 204525

View attachment 204526

View attachment 204527

View attachment 204528

View attachment 204529

 

[Dave76]

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.

 

[MiTr]

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

 

[bryonM]

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.

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

 

[bryonM]

Hi, you had said:

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.

So just waiting to hear back from you before I make an changes.

 

[Dave76]

Yes, change the 'CPU Vcore' to 'Normal', this will enable the 'Dynamic Vcore(DVID)' (Page #43&44 in your motherboard manual).
Dynamic Vcore will add/reduce voltage to the Vcore and allow the OS to change it for Stepping and other features. When you manually set Vcore it will remain at that voltage setting regardless of other functions settings. Much better to use Dynamic Vcore for CPU voltage setting adjustments.

increase the CVID by +0.010 untill stable?

Yes, this is a best way to get it stable, some people are impatient so the 0.05v and then reduce by 0.010v until un-stable and bump up 0.010v works better for them.

If the system boots into Win7, test with one of the CPU testing apps.
IPDT
CPU - Stress Test with Prime95
Be sure to monitor CPU temperatures, don't go over 77.6°C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.
Run Prime95 for two hours, this will be enough for this stage of testing.

After the above adjustments are finished and stable.
We can adjust the VTT and DRAM voltages/settings.
The Intel rule for VTT and DRAM voltages is to have DRAM 0.50v(or less) above the VTT. This is to prevent damage to the IMC (CPU Integrated Memory Controller), this is well documented.

Check the 'Command Rate' setting for the RAM, should be 2T. If not then change it.
EDIT: The previous CPUZ Memory tab shows it is set to 2T already, check it and confirm.

Set the VTT manually to 1.120v.
Set the DRAM manually to 1.500v.
Check for stability, if it boots up with no issues then run memtest86+ for 7 full passes, best to run overnight.
You can stop the test if you get any errors, one is too many.

If these settings fail to boot or won't pass memtest86+, then bump the DRAM voltage to 1.550v and test again.


Edit:
As mentioned by MiTr, it's a good idea to check for bent CPU pins.

 

[bryonM]

What do you suggest the max VCID should be. Like if its still crashing where should I stop going higher.

 

[bryonM]

After reaching +0.400v CVID and my VCore peaking at 1.6v while still crashing. I decided to RMA. I will check for bent pins right now.

 

[Dave76]

The DVID limit should be +0.05v, as I posted previously, if the CPU is the cause a max voltage of 1.40v would be as far as I would go for testing. Wouldn't run it that high for every day use.
1.60v is too high, possibility of causing damage.

What is the full load CPU voltage at 0.00 DVID?

Let us know if you found any bent pins.

 

[bryonM]

New CPU will be here on monday. I will check for bent bins and test the new one.

Bryon

 

[Dave76]

Let us know how it's running.