• We should now be fully online following an overnight outage. Apologies for any inconvenience, we do not expect there to be any further issues.

New system problems

Toggle sidebar Toggle sidebar
H

Hopper642

Member
Jan 30, 2010
79
0
0
I just built a new machine with a i7 975 on an Asus P6T Deluxe V2 with 12G of Corsair memory (TR3X6G1600C8D) and an Intel ssd. I am not overclocking at all. I am just trying to get a stable platform. I originally had trouble with the system being stable (Win 7 64bit), so I called tech support with Corsair and I manually increased the QPI/Dram core voltage from the default of 1.20 to 1.35 and decreased the bus voltage from the default of 1.66 to 1.60. But Windows 7 still crashes on me with this kernel power error:

<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-01-23T23:12:48.102008100Z" />
<EventRecordID>19223</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>

I am monitoring the voltages with the Turbo application from Asus, and I read where there was a "Golden Rule" that the CPU voltage should not differ from the core voltage more than .03. My CPU voltage is still at the default of 1.22something. Is this difference between the 1.22 on the CPU voltage and the 1.35 on the QPI/DRAM core voltage enough to still be causing these random crashes?

As you can tell, I am new to PC building, and I appreciate any help on this. Thanks. Hopper.
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
BTW-I do have plenty of power with a Silverstone 1200W modular power supply. Running 2 ATI 5870s in Crossfire too.
 
S

spittledip

Diamond Member
Apr 23, 2005
4,480
1
81
These look interesting:
http://www.google.com/#hl=en&source=hp&q=Microsoft-Windows-Kernel-Power+Guid&#37;3D{331C3B3A-2005-44C2-AC5E-77220C37D6B4&aq=f&aqi=&oq=&fp=64df356c6a3f8304

Seems to be a driver issue for several of the links, but not all. Is windows producing a crash dump?
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
This is the first link I came to which describes the problem. I even disabled SpeedStep in the bios and I never had a crash after that. I reenabled it after a recent windows update thinking that would address the problem. This has happened with ATI's 9.12 and now 10.1 catalyst drivers. Here is the first link that describes the issue well:

http://social.technet.microsoft.com...f/thread/a611d79d-9865-4a8e-917b-74b0a891912f

There is a crash dump file, I just can't find the right program to open it.
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
Here is another error message on system too:


Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 1/29/2010 11:09:51 PM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0
The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
<EventID>18</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2010-01-30T05:09:51.309220800Z" />
<EventRecordID>24769</EventRecordID>
<Correlation ActivityID="{AA123110-EFC5-4C1F-9F2F-BCC6248826FA}" />
<Execution ProcessID="1360" ThreadID="1640" />
<Channel>System</Channel>
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
Thanks. I will try to post the dump file contents. I found something else too. Sometimes this does happen after a long period of inactivity, but not always. I also found this thread and increased the hibernation size since I have 12 gigs of memory. There's a post in here as follows by mrbarry:



also with windows 7 x64 and also stupid restarts...tried: memory, psu, videocard replacement no solution for me BUT: try this i found on the asus support site. it helped for me:
My computer is crashing with the following error: &#8220;INTERNAL_POWER_ERROR (a0) The power policy manager experienced a fatal error.&#8221; What can I do about this?


This error is caused by the hibernation file size being is too small for the current memory requirements of the computer. To fix this problem,
increase the size of the hibernation file by following these steps:
1.Click the Start button.
2.In the search box, type command prompt. (cmd)
3.In the list of results, right-click Command Prompt, and then click Run as administrator.
4.In the Command Prompt window type:
powercfg /hibernate /size <size&#37;>
where <size%> equals the size of the hibernation file in percentage of total physical memory.
The default size is 75% and can be increased to 100% with:
powercfg /hibernate /size 100

my system works smootly now for a month already
good luck





Here's the link:

http://social.technet.microsoft.com...f/thread/9e71f600-7c62-4869-8236-964e93d17936


Wonder if this will fix it?
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
I think I might try this a while and see what happens before I change anthing else. I noticed when I did change the hibernation size that there was a significant difference in the default of 75 and 100&#37;. The size went from

9656684544

to

12875583488




The crash I had yesterday was right after the machine was idle for about 2 hours.

?????? Hope this is it. ??????
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
The QPI/DRAM core voltage is now 1.35 (was default 1.20) and the DRAM bus voltage is now 1.60 (was default 1.66), but the CPU voltage is still at default at 1.225.

I appreciate the help. I am hoping that hiberation size change will do the trick. The machine just came out of a 3+ hour at idle and no problem, yet..... I am using Intel's 160g SSD only in this machine.

I still thought that the CPU voltage should be closer to the memory voltage, but I don't know. This was just a guess on my part.

Thanks again.
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
This is the original error:



Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 1/29/2010 11:09:44 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer:
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-01-30T05:09:44.195608300Z" />
<EventRecordID>24700</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer></Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>


Here's the bugcheck information, and I have done memtest about 3 times with 5-7 passes on all 12 gigs of memory without any errors:



Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 1/29/2010 11:09:51 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800b0898f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\012910-11824-01.dmp. Report Id: 012910-11824-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-01-30T05:09:51.000000000Z" />
<EventRecordID>24759</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000124 (0x0000000000000000, 0xfffffa800b0898f8, 0x0000000000000000, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\Minidump\012910-11824-01.dmp</Data>
<Data Name="param3">012910-11824-01</Data>
</EventData>
</Event>


And here's the WHEA logger:


Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 1/29/2010 11:09:51 PM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer:
Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0
The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
<EventID>18</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2010-01-30T05:09:51.309220800Z" />
<EventRecordID>24769</EventRecordID>
<Correlation ActivityID="{AA123110-EFC5-4C1F-9F2F-BCC6248826FA}" />
<Execution ProcessID="1360" ThreadID="1640" />
<Channel>System</Channel>
<Computer></Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">3</Data>
<Data Name="ApicId">0</Data>
<Data Name="MCABank">5</Data>
<Data Name="MciStat">0xfe00000000800400</Data>
<Data Name="MciAddr">0x380002ff77ee</Data>
<Data Name="MciMisc">0x7fff</Data>
<Data Name="ErrorType">5</Data>
<Data Name="TransactionType">256</Data>
<Data Name="Participation">256</Data>
<Data Name="RequestType">256</Data>
<Data Name="MemorIO">256</Data>
<Data Name="MemHierarchyLvl">256</Data>
<Data Name="Timeout">256</Data>
<Data Name="OperationType">256</Data>
<Data Name="Channel">256</Data>
<Data Name="Length">928</Data>
<Data Name="RawData">435045521002FFFFFFFF03000100000002000000A00300002C0905001E010A140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB6320B86C6AA1CA0102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000001000000000000000000000000000000000000000000000057010000000000000002080000000000A50601000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000A506010000081000BDE39800FFFBEBBF0000000000000000000000000000000000000000000000000000000000000000577FAB4834DC6C4FA7D3B0B5B0A74314030000000000000027009D0000000000EE77FF02003800000000000000000000000000000000000000000000000000000100000001000000D0C5596F6AA1CA0100000000000000000000000000000000000000000500000000048000000000FEEE77FF0200380000FF7F0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

Hope this helps. Thanks.
 
Markfw

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
27,274
16,120
136
Forget those errors for now. I am not sure of the terminology, but your DRAM voltage should be 1.5-1.65 depending on the specs of the ram you have. What is the spec on your ram ? and for the motherboard ?

Also, run memtest at boot using a boot disk to eliminate all changes of ram error. I suspect this is your problem, but I have no way to prove it with all these unknowns.
 
BTRY B 529th FA BN

BTRY B 529th FA BN

Lifer
Nov 26, 2005
15,194
403
126
Do as Markfw900 says.

Set the DRAM timings and voltage to the vendors specified settings. If Memtest86 makes 3 full 100% passes without fail, boot into windows and run prime95. It will usually catch memory errors if Memtest doesn't, but Memtest it first.

Prime95 can take a while so be prepared.

I was having a similar issue. I was getting an error that so far it hasn't re-occurred. I'm not 100% sure of the antidote but I reset my DRAM voltages back to 1.609 from 1.55x - this may have been the problem but here are some of the other things I tied in my venture. Below is my event error:

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 1/23/2010 11:53:55 AM
Event ID 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ***-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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
<EventID Qualifiers="49152">10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-01-23T16:53:55.000Z" />
<EventRecordID>16871</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>***-PC</Computer>
<Security />
</System>
<EventData>
<Data>//./root/CIMV2</Data>
<Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage &gt; 99</Data>
<Data>0x80041003</Data>
</EventData>
</Event>

I reinstalled the 9.12 drivers and the problem didn't come up for a few days, then bang, it happened again (my 30 return policy is nearing.) I updated the bios, same crash. Next I took an old Raptor 150 and installed it with XP Pro - I got a crash. I did some googling and found a forum with a guy that had the same problem and the guy stated he raised his DRAM voltage. And then I remembered, I had lowered mine a while back. In-between that time I did a full check disk also. So I set my voltage back to normal with the timings at 1 step tighter than specified. I did 1hr of prime95 blend and came up with an error. I then reset my timings to manufacturers settings and it did the same test without errors until i stopped it 2hrs and 40min later. That's as far as I have gotten and I'm feeling a little bit more confident about its stability.
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
Thanks. I have already done memtest at boot several times, but I have not done Prime95 yet. I will do this.

Also, I called tech support with Corsair for the current voltages. The major spec I know about is the 1.65 volt limit on the memory. Mine is set at 1.60. I thought the techs at Corsair would be the best to know.

I will report back on this. Thanks again.
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
I'm actually running the memory at 1333, not 1600. That's why the tech guys at Corsair recommended 1.60. I think the timings are 9.9.9.24 at 1333 by default.

Just ran Prime95 almost an hour without any problems.

Thanks again for the help.
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
I still think it might be this hibernate size. Machine has run all day without any problems after this. Hope this is right.
 
BTRY B 529th FA BN

BTRY B 529th FA BN

Lifer
Nov 26, 2005
15,194
403
126
Hopper642 said:
I'm actually running the memory at 1333, not 1600. That's why the tech guys at Corsair recommended 1.60. I think the timings are 9.9.9.24 at 1333 by default.

Just ran Prime95 almost an hour without any problems.

Thanks again for the help.
Click to expand...

Well, your problem might still be there. My pc just crashed after all my recommendations I've told you. I'm at a loss at what to do. *sigh*
 
H

Hopper642

Member
Jan 30, 2010
79
0
0
I actually just looked at my settings and I had the thing set never to turn off, i.e. hibernate. There are other settings for hybrid sleep that I just left alone. I think there is some problem with the way memory is handled and that's why the errors are coming up, but I'm just not sure. Just coming from being idle to using memory may be the problem???

No problem all day after making the change above. Who knows???
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom