No, because cross browser design means taking into account not only that some errors are handled differently by each browser and even versions of the same browser, but also that many techniques for building sites simply don't work in all browsers reliably, if at all. How's it work in FF? Opera? Safari? Chrome? ALL of them have oddball behaviors that you have to be prepared to deal with from the START before you even THINK about IE's oddities... and what's working fine for you in IE8/IE9 could be broken in other people's IE8/IE9 because of things like default font size differences.
But without SEEING the page in question, NOBODY here is going to be offering anything helpful. You could have broken non-semantic markup, tables for layout, CSS3 elements nothing supports yet, CSS 2.1 elements that are inconsistent cross browser -- you could have rendering bugs caused by comment placement, inconsistencies in the default attribute values on elements from a lack of a reset or consistently setting margins/paddings/borders, you could have positioning bugs due to a lack of haslayout where needed or haslayout triggers where they cause harm. You could have quirks mode rendering tripping, list element stagger due to IE7's special handling of LI... You might be relying on a wysiwyg like the stupid preview pane in Dreamweaver basically flushing ANY chance of making it work cross browser... Shall I go on?
There are THOUSANDS if not hundreds of thousands of things that could be wrong, and without showing what it is you're working on we can't help you! It's like calling the auto mechanic and saying "My car wont start, how do I fix it?" without letting the mechanic see the car or even provide what make/model it is. Problem could range from dead battery to dead alternator to faulty wiring to blown fuse to seized engine block... They can't diagnose that over the phone with "It's a car and it won't start"