BSOD while OC'ing, just trying to figure it out.

[jbguillo]

I recently replaced my motherboard with an Asus M4A79T Deluxe from a Gigabyte board. I'm running an AMD 965BE currently.

Previously on the Gigabyte board, I ran 3.8gz @ 1.425v no problem; it could run Prime95 torture all night long. With the new Asus board, if I up the multiplier at all, with or without changing the CPU volts, it will blue screen within a minute of running Prime95. All of my temps are under 54c as well. Just wondering wtf is up, and maybe if the RAM is disagreeing with the Northbridge chip? Nbridge is an AMD 790FX, and I'm running 8GB Gskill F3-12800CL9D-4GBNQ.

This is the same BSOD I get every time; any info would be greatly appreciated.

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Extra information about the problem
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007DD68F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

 

[Orpheous]

Hi there,
I don't have debugging tools installed just yet, but this program will most likely help you to analyse and decipher your dump files
BlueScreenView - blue screen of death (STOP error) information.

 

[chev65]

The odds of both boards requiring the same voltages for the same overclock are pretty much zero. Unfortuneately changing boards also means you will need to change some settings and redo your overclock, then stablity test your overclock all over again. Unless somebody made up a magic formula for this that I'm not aware of.

I can only assume that you found the chip-set drivers for your new board, even then it is sometimes best to reinstall the Op system when changing to a new board.

The new board might also require higher or lower chip-set voltages, higher or lower FSB and V-core voltages. Perhaps even using a different divider for your memory or working with the memory settings will help. In general the DDR3 boards are easiest to set up using the linked and synced memory settings and usually the 2T command rate is more stable.

 

[reghakr]

Go to Control Panel > Device Manger and see if there are any entries with a yellow flag

 

[usasma]

The crash occurred in ataport.sys - so it's likely that the overclock is stressing out your motherboard, and that's causing the crash.

Try adding cooling to your northbridge and southbridge to see if that helps.

 

[jbguillo]

I can only assume that you found the chip-set drivers for your new board, even then it is sometimes best to reinstall the Op system when changing to a new board.

I re-installed the OS for the new board, as well as chip-set drivers.

Go to Control Panel > Device Manger and see if there are any entries with a yellow flag

None.


Thanks for all of the replies guys!

I messed around with some settings, and upped the NB voltage to 1.2 and CPU/NBv to 1.2 as well. FSB is @ 206mhz with a 17.5x multiplier, and CPUv is 1.45v. So I'm pushing 3.6ghz stable after running Prime95 Torture for 2 hours.

I tried going back down to 200mhz and upping the multiplier to 18x; Within 2 seconds of starting up Torture test, BSOD. So, it seems that I really can't up the multiplier like I could on the other board; this Asus board seems to hate it, even with 1.5v CPU Core. (Previous board I could hit 19x no problem)

It also runs very stable with everything at Auto at just 18x multiplier

I really don't want to increase my FSB anymore to up my clock, but it seems as though it would be my only option. What do you guys think about me upping the FSB to say maybe 210mhz? If I really have no other stable options, I'll keep it at 3.6, but that seems a little useless for a BE processor with a stock clock of 3.4ghz.

I'm really a noob when it comes to seriously messing around with voltages, so any tips would be awesome. How would I know wether or not to raise or lower voltages, and which voltages to achieve what I'm looking for?

 

[unnefer]

Prolly a little late, but I have a similar setup to you (same board, similar memory from G.Skill, same CPU) and I too am having the same BSOD issues that you experienced.

What I found is that the BIOS (latest - 2304) is very buggy, and although you set vcore in BIOS, for whatever reason, sometimes when you boot it will revert to default and that will cause the BSOD. Even at stock settings, with stock vcore, the Asus M4A79T Deluxe board with the current BIOS the vcore setting is very buggy and can and does drop below even the stock vcore voltage.

I have no idea why this occurs, but all it is definitely BIOS related. I have emailed Asus and am waiting for a reply.

All I can suggest to keep things simple is do not try and overclock the CPU on the M4A79T Deluxe until a new (bug free) BIOS is released, instead look to overclocking your memory as dram voltage changes in the BIOS are much more stable and work as expected.