Hyper Transport Sync Flood Error

[hewny]

Hi when I've been playing games my computer would often hang and would restart and I would get the error "Hyper Transport Sync Flood Error". I looked up a solution to change my dram voltage to something higher than 1.5 (the setting it is at) I have put it at 1.67 however CPU-Z still says 1.5V? The bios says 1.67 Is it running at 1.67? Is this likely the problem to my error, what does setting the voltage actually do? Thanks!

Edit: My computer is not overclocked btw Thanks!

 

[ekoostik]

If you're looking a CPU-z's SPD tab, that's just the specced V which CPU reads off the chip. Run HWMonitor to get a look at the operating V: http://www.cpuid.com/softwares/hwmonitor.html

 

[jaquith]

Q - What MOBO {include revision} and what BIOS version?
Q - What MOBO "Utilities" do you have installed -> Uninstall them ALL.

Also, to rule-out BIOS evasive crapware; run MSCONFIG and select Diagnostic. Then Clear CMOS and either Load Default/Optimized settings in your BIOS. Next stress the rig with the latest version of Prime 95 -> http://www.mersenne.org/freesoft/

Q - What 'other' changes to the BIOS have you made?
Q - What RAM is installed? please provide links

 

[hewny]

I'm not home right now but I'll post the info when I get home. But I haven't hanged anything about my setup except update my bios. It didn't start doing this until yesterday, could there be something wrong with my mobo. I'll post more specifically later, but I have a MSI mobo with AMD X4 processor. Thanks!

 

[jaquith]

Most of the time it's the BIOS and in some cases people have had to downgrade their BIOS.

I'm looking for cause and effect. If yesterday then just to rule-out some bizarre driver or corruption -- run System Restore and use one from the 'day before' yesterday.

Also, look at the Event Manager and look for 'Critical' Errors.

 

[hewny]

So here's the what I see after a reboot after the error:
http://imgur.com/s4wLX&EXyF2l

There are indeed critical errors:

http://imgur.com/s4wLX.jpg

The thing is even after I updated my bios, my rig was working fine for a week. It just started doing this and I haven't changed anything :/

My motherboard is:
http://www.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1866

with an AMD phenom II X4 965 Black edition

my memory is
Corsair XMS3 TW3X4G1333C9AG 4GB Dual Channel DDR3 RAM - - PC10666, 1333MHz

Thanks so much guys!

 

[jaquith]

Download BlueScreenView -> http://www.nirsoft.net/utils/blue_screen_view.html
Run and scan, Edit / Select All, File / Save Selected Items, and save the report as BSOD.txt. Then post the info here.

The Critical Errors seem to be a 'forced shutdown.'

RAM: 1333 9-9-9-24 2T @ 1.5v ; you are putting too many volts to the RAM: TW3X4G1333C9AG

Set DRAM Frequecy -> 1333 Mhz
Set CPU-NB Voltage -> 1.1~1.2 volts
Set DRAM Voltage to -> 1.50~1.55 volts
Set Spread Spectrum -> Disabled
-
Set DRAM Timing Mode -> Both
Set DRAM Advance Control -> Both
-
Set DRAM Timings to 9-9-9-24 (CAS-TRCD-TRP-TRAS)
Set 1T / 2T Timing -> 2T
Set DCT Unganged Mode -> Enabled
-
Set Auto Disable DRAM/PCI Frequency-> Enabled

As I stated -> "Also, to rule-out BIOS evasive crapware; run MSCONFIG and select Diagnostic. Then Clear CMOS and either Load Default/Optimized settings in your BIOS. Next stress the rig with the latest version of Prime 95 -> http://www.mersenne.org/freesoft/ "

 

[hewny]

Here is the info from BlueScreenView I will try the stress test now.


==================================================
Dump File : 121410-15210-01.dmp
Crash Time : 12/14/2010 5:48:20 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`049348f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+f64c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\121410-15210-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 121410-15740-01.dmp
Crash Time : 12/14/2010 4:33:51 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`049ba8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+f64c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\121410-15740-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================


Thanks!

 

[jaquith]

hal.dll is a hardware error and unless a 'driver' is listed a non-specific error; hal.dll is used for Windows to communicate with hardware. My assumption is it is/was your RAM.

However to cover a broad spectrum of problems:
1. Run Windows repair -> http://windows.microsoft.com/en-us/windows7/products/features/startup-repair
2. Virus scan -> http://www.eset.com/online-scanner
3. H/W: Scan your PC for compatibility -> http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx