Windows 7: A Hyper Transport sync flood error occured

Ok ive been having this problem for a while now, every once in a while my computer shutsdown and when i reboot it has a Error that said "A hyper Transport syhnc flood error occured" and i start to Windows normally....Ive been having this problem after i installed a new RAM and windows 7....anyone know how to fix this??

F.Y.I
I am now using Two RAM
-One 2gb DDR2 RAM (800Mhz) (new one)
-One 2gb DDr2 RAM (400mhz) (old one)



the 400mhz one is my old RAM..and i bought 2 (800Mhz)RAM...(to replace my old one) but i always have BSOD when using those two..so i just used my old RAM paired with one of the New 800mhz ram that i bought...everything wnt well for about a week until im having that Hyper sync flood" thing

DDR2 wasn't manufactured in 400MHz; 400MHz chips are the top end of DDR (1) memory. EDIT: I stand corrected after a quick google search.

A friend at work had this same BSOD as well, but I can't recall how he fixed it. The first thing I would do is go back to the matching sticks of 800MHz and then attempt to adjust the timings in the motherboard's BIOS. However, if this is something you are unfamiliar with then of course do not even try.

I'm unable to pull up any guides for you since I don't know what board you have. Please fill out your system details as per the forum guidelines.

I already Edited my system specs sorry about that...when i try to use my 2 new RAM i always have BSOD....i know it has something to do with timings and all...i tried to search in google on how to fix that but some of the guide said that just adjust the timing...something like 1-2-3-4-3....something like that...but i dont really know whats the meaning of that...i wanna tinker my BIOS but im afraid ill only make it worse

If you have any reservations about adjusting timings in the BIOS then, as I said, don't attempt it. I've looked up the manual for your motherboard and while it does offer the option to adjust your DRAM settings I would advise reading up on the subject first.

The following links will help you first to understand memory timings, and what all the numbers mean:
A Shortcut to Understanding Memory Timings - The Essential Guide To PC Memory | Roundup | PCMag.com
Understanding RAM Timings | Hardware Secrets

While this link has a lot of the above information broken down in a far more readable way:
Info: Ram Timings For Dummies.


To find the manual for your motherboard, go here:
MSI UK ? Mainboard - 740GTM-P25


This is not going to be something you'll be able to look at straight away but it something that you will have to read up on for a couple of days, taking time to fully digest it before trying to change any settings. If you feel too daunted to even give it a try, don't worry! The majority of system owners, even advanced ones, don't bother with messing with memory timings unless they need to fix something.


A slightly easier alternative you could try to fix your Hypertransport problem would be to step down the HT Link Speed, also in the BIOS. If you press DEL (the true delete key, not the same as the backspace) while the system is booting then you will enter into your BIOS. From here, enter into Cell Menu.
Toward the bottom of this new screen you'll see HT Link Speed, and setting this to Manual by pressing the + or - key will allow you to change the number. I don't know what it will say to begin with (it may be for example something like 1800), but you are best off only reducing it by one button press, again with + / -.

If this doesn't work I have seen reference to adjusting the HT voltage, but unfortunately this isn't supported with your board, and so we might then have to enter the rocky road of BIOS updating.

Thank you for the recommendations .....I really appreciate it...Ill definitely try to understand all about RAM timings,cus its really been bugging me for quite sometime...ill also try that Ht link speed that you recommended..On a side note do you know why i just rarely get this error?..it only occurs maybe once a week..why is that?...

I don't understand a great deal about Hyper Transport but my best (and completely random, based on no knowledge whatsoever) guess would be that your system is not always using this feature, at least not in such a way that causes it to become overloaded with Hyper Transport requests.

As I say, a complete stab in the dark, as it is nigh impossible to find an explanation online as to just what causes it in any defined sense. There are several different causes, it seems.