Okay so this looks like an issue when your
vb is on. I wonder what types of hacks do you have in your vbulletin? The evidence the error is not present when you turn off that
vb header narrows it down to really an issue with vbulletin and thats why I am pointing to maybe a hack interference.