ASUS P6T Anomalous Behavior

[EXCellR8]

I've been having some real issues with my '09 ASUS P6T board lately; I'm not sure what's causing this sort of erratic behavior. I suspect that it may be the memory but I don't have anything to base my guess on. I've been using this board since late 2010 and I've been overclocking my i7-920 @ 4Ghz from day 1. I've never had any real problems and everything has been fine up until now.

Basically, the board seems to have a lot of trouble POSTing and the Windows doesn't seem to like booting. I notice the board has issues detecting SATA ports 3 and 4, which are just non-booting hard drives or possibly an optical drive. It often gets 'stuck' on detection here and I need to do a hard restart. Sometimes when I do this I get a long beep followed by a few short ones. I've reseated the memory a few times and that usually helps, but it just happens again eventually. I don't OC my RAM btw.

Also, sometimes Windows 7 doesn't completely load... the splash screen or whatever goes away but then the system just sits black. I've gotten a blue screen 'SYSTEM_SERVICE_EXCEPTION' a couple of times which points to the graphics driver, but that seems to be a separate issue. I've also noticed that sometimes my keyboard is unresponsive but other USB devices are fine??

I can eventually get the board to POST normal and load the OS, with everything reading normal, but this behavior starts again once the machine is powered down. I don't really understand what's causing it but once it's up and running it seems absolutely fine... no freezing, no blue screens, no performance hits, nothing. I'm pretty sure there are no new mobo drivers and I'm using the latest from AMD for graphics.

Any ideas what could be causing this? Is the board just getting 'tired?' lol

 

[EXCellR8]

Didn't want to bump but I have too much to add...

For the past week or so I haven't experienced any issues with the board not POSTing, up until last night when the system froze up completely. I replaced the RAM and adjusted the timings and voltage but then I couldn't get the board to POST with the OC settings I had dialed in. Finally got it up to speed again after a little tinkering but it froze up again shortly after Windows 7 loaded.

Tried the new RAM kit again, this time I raised the CPU, DRAM, and NB voltages, and everything seemed fine. I used the machine normally, did some gaming for a few hours and I didn't experience any issues. I don't know, but I should probably replace a couple components like the PSU... but if i do that I might as well just rebuild the entire machine.

Any thoughts? I think I may have just started to wear the board out, at least that's what it seems.

 

[bleucharm28]

Set everything back to default and leave it running 24/7 for a week or 2 weeks and see if anything happens. Have you tried memtest86? Maybe a bios update if needed. Look at your mobo's manual and see what those beeps mean.

Im not sure how P6T mobo oc's, but when i increase base clock; my ram mhz also increases. I think multiplier was at 21 (That is if i remember correctly). I had the Asus Rampage II, which i think OC should be the same or close to it.

What's your voltage at with CPU @ 4.0? I oc my 920 D0 at 4.2g in water and i think my voltages was like 1.35-1.39.

 

[EXCellR8]

The board is definitely becoming an old tank, but I've been using it awhile and it does offer decent OC headroom for a non-flagship board. If it crashes again I'll do a stock run for an extended amount of time and run some memtest passes. I'm pretty sure I'm on the latest BIOS but I will double check.

As for the CPU itself, it's @ 1.35v on liquid but I think it might be a C0. Multi is set to 20.0 I believe and I run the stock speed and timings on the RAM. Never had issues with the board's stability up until now which makes me think memory.

I have a ASUS P8Z77-V LE and 3570k that could replace this setup, but I'd really like to see at least another year out of it before it's retired. Might have to rebuild sooner than later it seems. I'm going to find my manual and see what those beeps mean, even though I haven't heard them again recently. Very odd...

Thanks for the input!

 

[SpeedTester]

I've been having some real issues with my '09 ASUS P6T board lately; I'm not sure what's causing this sort of erratic behavior. I suspect that it may be the memory but I don't have anything to base my guess on. I've been using this board since late 2010 and I've been overclocking my i7-920 @ 4Ghz from day 1. I've never had any real problems and everything has been fine up until now.

Basically, the board seems to have a lot of trouble POSTing and the Windows doesn't seem to like booting. I notice the board has issues detecting SATA ports 3 and 4, which are just non-booting hard drives or possibly an optical drive. It often gets 'stuck' on detection here and I need to do a hard restart. Sometimes when I do this I get a long beep followed by a few short ones. I've reseated the memory a few times and that usually helps, but it just happens again eventually. I don't OC my RAM btw.



Any ideas what could be causing this? Is the board just getting 'tired?' lol

I had the same exact problems a few months back then it shit the bed one day. Same board, Same cpu but oc'd to 4.2 ghz. Couldnt get it ever to post again. CPU and memory now sitting on a shelf someday going for sale.

 

[EXCellR8]

^thanks for the input, that certainly concerns me a little bit but I did get the settings dialed back in eventually. for some odd reason even the profiles i saved, well the settings that they kept, didn't allow the board to POST. it was only until I gradually brought the base clock back up that it worked again. i don't recall ever having to do that in the past.

let me know if you decide you want to sell that CPU and memory, I'd be interested. wouldn't have to ship them very far...

the system had been running just fine for a couple of days but i just ran into an issue with the graphics driver failing and crashing me. uninstalled and now I'm on the latest beta so I'll see how that holds up. hopefully my card is fine because i haven't had that very long.