thlnk3r

Sunrex, sometimes I'm on yahoo messenger in the evening. Just PM me and I'll try and respond as quick as I can.

Those temperature readings may actually be the chipset (system). Have you tried other applications such as Coretemp or Everest?

Good luck

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase

Sunrex

Added. And I'm using HWMonitor, I don't think its messing up.

thlnk3r

Sunrex, what does the BIOS report? Remember the BIOS typically loads the processor anywhere from 60 to 80%. This information is typically located in the "PC Health" section in your BIOS.

Hope that helps

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase

Grim

WHEWWW!!


What and EXHAUSTINGLY long thread to read that was lol
I've been subscribed to this thread from it was about a singe half page thread. Decided I'd like to help, but never had the time.

I decided to read through every single post of the thread though - to gain a comprehensive Idea of what was going on.

SRY to hear about your prob sunrex.
Even more sry to hear that I waited until your RMA'd the board lol.

But anyhow, I few things came to mind

Firstly,
the problem you're having is a board/HDD/OS incompatibility Issue.
Lets just get that out in the clear.

This would be made even more concrete by the fact that you:

You've changed your CPU,
You've tried different RAM
And you've done all of this, in addition to running /REINSTALLING your OS, AT STOCK SETTINGS (correct?)


This whole problem sounds so reminiscent of one I had with an old PCCHIPS motherboard.
The legacy can be found here - its just an interesting read really
:

now the theorized problem there was the misfunction of the onboard IDE controllers used by the boards.
The re-detection of the HDDs is theorized by my expert-on-the-board friend Timmy to be a result of a timing mechanism used by the controller.
Which is randomized every startup, hence causing the problem.


ANYHOW. you've shipped off the board already, but if you're like me, then why this this was behaving like that must be nagging you.

SO I'll ask:
What makes you certain that the data corruption occurs when the PC is turned of for LONG
periods of time, VS, just being turned off/on?

That fact (if it IS fact) is the most peculiar feature of this mystery.
Please comment.

DID YOU EVER get around to cooling your Northbridge?

frankly, I've had similar problems just because of an overheating NB.
And FTR. YOUR NORTHBRIDGE WAS, BEYOND A DOUBT, TOO HOT.

Had you tried setting the drive to run in 1.5GBps mode instead?

(btw - you're right, its the FS being corrupted and NOT the file data, and


YES, that can be caused by the drive being dismounted improperly)


"""The file is possibly corrupt. The file header checksum does not match the computed checksum." thats it. There was nothing else."""

See, this signals Drive data allocating/retrieval problem. Especially because this happened continually.

Here is where the link I gave you is of particular interest.
Its similar in nature really.

My personal theory on your (now shipped off) problem is that you had a hardware incompatibility.

I believe your motherboards IDE controller had incompatibility with your HDD/OS.

Commendations on your determination though.
It may not have yielded an answer this time around - but you're one of those people I can tell will save themselves a decent amount of $$ where problem resolution is concerned in the future lol.

I hope the RMA board works.
If it doesnt - I'm expecting to see this thread ressurect

thlnk3r

Grim, great post

What is extremely strange about this particular issue is that the problem only arises upon a "cold boot". Sunrex doesn't experience any problems after warm reboots. The only thing I can think of is a cold bug. So it's either the 6000+ or perhaps as you stated a hardware compatibility issue.

Good luck

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase

Sunrex

Grim: I.. um.. I'm not quoting that huge post, no offense (THANKS FOR THE INFO! KNEW IT WAS THE FILE SYSTEM YEAHHH!!!!..... well.. at least I was right about something ).

Let me clarify: The other CPU was the same as the previous CPU. Same brand, everything. I decided to order a second one from newegg after all the issues hoping it would solve it (not really.. um.. I sorta forgot to take the MB tray out of the case and I hardly could get it out since it was stuck to the Heat sink.. so, it had around 10+ bent pins. Never knew they were THAT delicate. AMD RMAed that cpu. But before I got it back, I had already ordered a new one just in case they rejected it).

No, I never tried another brand of ram. The other ram I had turned out to be DDR. Not DDR2. Upon talking with OCZ they said if the board supports DDR2 ram then there would be no compatibility issues. And if the issue happened with only one stick in then it wasn't the ram. I don't know if this is true or not, but I wasn't going to waste more money on another brand of ram since I'm planning on getting another 4GB of ram from OCZ so I can use all four slots and have 8GB ram.

Corruption DID happen on the other computer actually. NOTHING like the gigabyte. I had a BSOD and I can't use windows live anymore =(. I'll have to run a chkdsk scan.

Nope, I have not tried cooling the NB. This had nothing to do with money or me being lazy. At the time, it was nearing friday and if I had waited for newegg to ship the fan, it would have been another half a week or more before I could RMA the board since gigabyte (As far as I know anyway) is closed weekends. It would have taken a while to get the RMA number, and for it to arrive there. ETA was today... hang on, let me check UPS tracking. YES!.

Delivered On: 11/21/2008
9:23 A.M.

Gigabyte has the board now. Sadly its friday, so I hope the RMA centers work on weekends. So either I'm going to get a call from gigabyte saying there's nothing wrong (And me *****ing on the phone at them for a few hours.) or a replacement _should_ be sent out on monday. (UPS ships monday, I hope they can finish it by then anyway).

Actually, I believe I had the drive set at 1.5Gbps before I realized what the jumper did. The corruption DID occure less, but it still happened regardless.

I don't understand how its a compatibility issue. I tried a older WD hard drive and a newer seagate hard drive. Same issues on both.

Yes. I did reinstall my OS at stock settings. Actually, I've done this for Linux, and XP/Vista.

Frankly, if it was the NB I plan on complaining.. loudly... to gigabyte since I've had them confirm MULTIPLE times that the heat is "normal". I know it's not GOOD, and can be DAMAGING. But when they say something, if they can't back it up then they are outright lying to people. And that would make my future computer components NOT be from them.

On the other hand, we will know soon enough. When I get the RMA back if it still happens and I try cooling it and that fixes it - we will know.

The only compatibility issue I can think of off the top of my head is the CPU. It's a AM2+ MB and my understanding is AM2 and AM2+ supports backwards compatibility... unless, of course some how gigabyte ****ed up royally in the design.

HWMonitor WAS messing up. BIOS reported.. 42C?. Well under 50 in any case.

I have internet back now to! Yay me!.

Thanks for posting Grim!. I would +rep you.. but you waited to long

thlnk3r

Sunrex, was any of the hardware similar? Were the problems only prevalent during cold boots?

On the weekends, our RMA centers close down. So I'm assuming the repair center for GA boards is closed as well.

Good luck

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase

Sunrex

Awww. Thats to bad.

No, it was a BSOD from a unstable OC. Tried going up to 2.3Ghz. I really killed this processor a year or so ago. The reason live was corrupt is because it was running when the BSOD happened.

Grim

HM!
well then, in that case I'd have to say it was a fault of the board as you had figured!

The more I think about it, the more I believe that your NB overheating was the Issue.
100c is not "normal" for ANY IC COMPONENT in computers of this generation.
Thats bull. (sure Thinker can agree with me on this.)

Its overheating may very well have damaged it.
Lets see how hot/cool it runs when you get your replacement board.

thlnk3r

Grim, thanks for pointing that out. I have a sinking feeling though that the 100C chipset temp is a false reading. However I do know that my nForce 4 chipset can handle up to 90C but still...100C seems almost unrealistic for a motherboard (sustained) without experiencing crashes/lockups. It very well could be possible though.

Good luck

__________________
AMD Overclocking Guides · Terms of Service · My CM690
Socket 939 Appreciation Club and Knowledgebase