• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

isntability, have tried everything. AMD X6 and Asus board.

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
bobloadmire said:
according to this (http://www.techpowerup.com/reviews/AMD/Phenom_II_X6_1090T/2.html)

"With the core count bump you'd expect TDP to hit the 140 W limit again, just like the first version of Phenom II X4 965 did, but in that case you'd be very wrong. In past AMD reviews we've always checked the lower limit of core voltage where processor are still fully stable, and results have always been very impressive, often reaching near 1.1 V with stock frequency."

and their screen shot shows them @3.2ghz at 1.284v.
Click to expand...

I quote from the same article you just posted:

"The tested model, 1090T Black Edition, works at very high 3.20 GHz clock speed using just 1.300 V on core voltage "

Apparently you're a selective reader? They're also using a 955 and 1090T which aren't even cpu's you have in your possession ....

You can't run a six core Phenom II at 1.2XX full load, maybe your readings are wrong but your results suggest that's not the case.

CPU:1.275 offset
NB:1.125 offset
CPU VDDA 2.5oov

Do these three setting have an Auto?, or are these default? Something very weird is indeed going on if you can't manually set your voltage.
 
Last edited:
BD231, it doesn't matter because it still crashes at 1.35v Does anyone else have a suggestion?

Today i was running prime 95 after setting the voltage to 1.35v for about 20 minutes with no issue. then I stooped it and ran Windows Backup to make a system image and It hung about 5 minutes into the operation. is that a clue?
 
All I know is I tried everything to make memory that was not on the compatiable list work with my 890GX Asus. Never got it to work.
 
i found some windows event logs from my crashes, maybe these are clues.


Log Name: System
Source: EventLog
Date: 8/21/2010 2:04:51 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Brad-PC
Description:
The previous system shutdown at 2:00:55 AM on ‎8/‎21/‎2010 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-21T09:04:51.000000000Z" />
<EventRecordID>7833</EventRecordID>
<Channel>System</Channel>
<Computer>Brad-PC</Computer>
<Security />
</System>
<EventData>
<Data>2:00:55 AM</Data>
<Data>&#8206;8/&#8206;21/&#8206;2010</Data>
<Data>
</Data>
<Data>
</Data>
<Data>2474</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DA07080006001500020000003700B700DA07080006001500090000003700B7003C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>






and




Log Name: System
Source: Disk
Date: 8/20/2010 2:46:00 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Brad-PC
Description:
The driver detected a controller error on \Device\Harddisk3\DR3.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-20T21:46:00.115098400Z" />
<EventRecordID>6423</EventRecordID>
<Channel>System</Channel>
<Computer>Brad-PC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk3\DR3</Data>
<Binary>0E01800001000000000000000B0004C003010000000000000000000000082D0000000000000000009EE00C0000000000FFFFFFFF0600000058000000000000000000061208000010000000003C0000000000000000000000C0EC8E0880FAFFFF0000000000000000105C590980FAFFFF0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>


how do i figure which disk is DR3?
 
from new egg:

Pros: Nice quality and appearance, 8gb in 2 slots so room for expansion, reasonable price (but see below...). Good performance: scores 7.5 in Windows 7 on MSI 890FXA-G70 w/ AMD x6 1055t @ 3.5ghz OC (100&#37; stable)

also what i was wondering is it even possible or likely to have a bad memory controller on a processor?
 
Last edited:
yasasvy said:
Did you perform memtest on each individual memory stick?
Click to expand...

yeah memtest actually fails. It says errors=0 but the program itself stops running and sits there idle, but the memory shows no errors. what does that mean?

coincidence?: It stopped at 50&#37; total and the current 188k-2048M 8190M only made it to 20&#37; then it stopped testing, errors still reading 0 walltime at 36:40. Also memory bandwidths were as follows:

L1: 46107 MB/s
L2: 14881MB/s
L2: 8082 MB/s
Memory: 4850 MB/s (this seems low)

Also i found this on the Memtest site "Memtest86 can not diagnose many types of PC failures. For example a faulty CPU that causes Windows to crash will most likely just cause Memtest86 to crash in the same way."
 
Last edited:
The driver detected a controller error on \Device\Harddisk3\DR3.

that sounds suspicious...

And can you post a link to your ram on newegg?
 
bobloadmire said:
from new egg:

Pros: Nice quality and appearance, 8gb in 2 slots so room for expansion, reasonable price (but see below...). Good performance: scores 7.5 in Windows 7 on MSI 890FXA-G70 w/ AMD x6 1055t @ 3.5ghz OC (100&#37; stable)

also what i was wondering is it even possible or likely to have a bad memory controller on a processor?
Click to expand...

That could be a possibility. I am sure this is a cpu tester program out there somewhere.
 
bobloadmire said:
I looked around, but i didn't find a utility to test cpus/ I have tried Prime95, but it just stops working and freezes, no info.
Click to expand...

I am certain that its your SSD(Assuming your OS is installed in it) that's causing this. Do you have a spare drive that you can use? Just install a linux OS in that spare drive and see if you experience freezes.
 
bobloadmire said:
the ram. http://www.newegg.com/Product/Produc...-311-_-Product



also I just tried memtest on each module individually and they both caused memtest to stop exactly at 53 percent on the 188k-2048M test. Why would it stop at exactly the same point? memory incompatibility or faulty CPU memory controller or something else?
Click to expand...

http://www.newegg.com/Product/Produc...b%2020-231-311

It's this, right? (your link is detonated when I click it)

Regular specced 1333MHz memory. Should work fine with 1.5V.

I would definately remove that harddisk3 first. (although the ram could still be faulty as well, or your mobo, or cpu...)
 
OP, are you booting memtest86 from a cd or floppy, or from somewhere on a harddrive? If so, which drive?

Because if memtest86 is crashing and you're running it from a cd or from some other drive than the SSD, then logic would dictate that you may have a faulty CPU. Or that you need to look at some other aspect of the CPU, like the NB/memory controller.
 
DrMrLordX said:
OP, are you booting memtest86 from a cd or floppy, or from somewhere on a harddrive? If so, which drive?

Because if memtest86 is crashing and you're running it from a cd or from some other drive than the SSD, then logic would dictate that you may have a faulty CPU. Or that you need to look at some other aspect of the CPU, like the NB/memory controller.
Click to expand...


I ran memtest from a flash drive, and unplugged all hard drives and my SSD and unplugged my external USB drive. Only things hooked up were Keyboard and momuse, and I unhooked those once the test was under way.
 
And it still crashed?

Ok, here's my guess: your NB is messed up. Some part of it isn't functioning properly which is throwing your IMC just a bit out of whack. Raising your vcore increased your core temperatures which increased your NB instability, which is probably why your system was more crash-prone after raising vcore - I've observed this before on K10.5 chips. If you increase core temps, the voltage you need to keep the NB happy also goes up sometimes, which is why high NB speeds are so hard to reach when you're pushing your cores to their limits.

Also, an unstable NB/IMC can cause faulty read/writes from storage media, which may be why you're getting errors from the SATA controller.

I would recommend restoring your CPU to its default vcore and raising your CPU-NB and NB voltages. Try a CPU-NB of 1.3v and a NB of 1.2v-1.25v. If you can't find those specific voltage settings in your BIOS, tell us what settings you can find, and we'll try to figure out what the CPU-NB and NB voltages are based on your feedback.

If you can't bring the chip around with some extra CPU-NB and NB voltage, it may be time to consider RMAing the chip. I would not normally recommend RMAing a chip that has been overvolted, but in your case, the faulty chip behavior manifested before you tried different voltages, so I can hardly see how you should be held responsible for whatever problems may exist with the chip.
 
DrMrLordX said:
And it still crashed?

Ok, here's my guess: your NB is messed up. Some part of it isn't functioning properly which is throwing your IMC just a bit out of whack. Raising your vcore increased your core temperatures which increased your NB instability, which is probably why your system was more crash-prone after raising vcore - I've observed this before on K10.5 chips. If you increase core temps, the voltage you need to keep the NB happy also goes up sometimes, which is why high NB speeds are so hard to reach when you're pushing your cores to their limits.

Also, an unstable NB/IMC can cause faulty read/writes from storage media, which may be why you're getting errors from the SATA controller.

I would recommend restoring your CPU to its default vcore and raising your CPU-NB and NB voltages. Try a CPU-NB of 1.3v and a NB of 1.2v-1.25v. If you can't find those specific voltage settings in your BIOS, tell us what settings you can find, and we'll try to figure out what the CPU-NB and NB voltages are based on your feedback.

If you can't bring the chip around with some extra CPU-NB and NB voltage, it may be time to consider RMAing the chip. I would not normally recommend RMAing a chip that has been overvolted, but in your case, the faulty chip behavior manifested before you tried different voltages, so I can hardly see how you should be held responsible for whatever problems may exist with the chip.
Click to expand...


I doubt that i got 2 bad northbridges in a row. Seem highly unlikely. Also instability didn't change with my vcore setting, it wasn't worse or better. On my first board i removed the northbridge cooler and replaced the thermalpad with thermal greese to see if it was a heat problem. Also these motherboards have northbridge overheat protection and will tell you if the northbridge overheated.

I have sent in both the ram and the processor. AMD is interested and said that they are going to test the chip after I told them how many configurations I have tried with it. And getting some fresh ram sticks can't hurt. Im going on vacation for 2 weeks and ill let you guys know how everything comes together. Let me know if you guys think of anything else.
 
The NB is on the CPU, not the motherboard. You have a k10.5 chip. But since you have already RMAd the chip, hopefully your problem will be resolved soon.
 
yup

RMA# xxxxxx

Processor did not pass overnight stress testing - caused system to crash to blank screen.

Possible problem may be with memory controller or a bad register within the CPU.


GOD FUCKING DAMN IT! FUCK YOU AMD! YOU ARE KILLING ME!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top