Please refer to the links for stale threads HERE and HERE regarding my still unresolved problem. Since my last post to those threads, I have utilized a mobile rack which a friend gave me to remove as many variables as possible. I have a total of 3 drives, with the current slave drive being the backup. 98SE and XP Pro is installed on the now interchangeable primary IDE master drives. Drives are (2) 40 Gigabyte Maxtor Diamond Max ATA 100drives and an IBM/Hitachi 40 Gigabyte ATA 133, as I ended up with an extra drive after ordering a second Maxtor and getting the IBM drive replaced under warranty. That is not really relevant to the problem, I was just mentioning that so that you would have a clear understanding of my hardware profile. Nothing else has changed except the processor, as detailed, and the 56K modem to get rid of a US Robotics winmodem piece of junk. I am still having the same problems. I have been running XP on the IBM since earlier in the week and I have not been getting any fatal exceptions or other BSOD's, but am still getting illegal op errors in firefox and IE. I don't have any other software loaded, because I don't see the point until this problem is resolved. I do have an attached error log from Firefox which I do not know how to interpret and have been unable to find any free info online regarding processor exception 5 and windows error exception 1 online at either the M$, ASUS, or AMD websites. Currently I am running at BIOS default speed, which for the T'bird 1.33 GHz CPU is 1000 and 900 MHz for the 1.2 GHz T'bird. Everything works fine. THe system ran for over an hour the other night after getting a real workout, before I started getting illegal op errors first with firefox and then IE. I have currently been connected for over 5 hours, with almost 3 meg's sent and almost 24 meg's rec'd. I currently have 1 firefox window running with 10 tabs, 1 single tab window and 4 windows explorer windows open with 25 processes, 3-16% CPU usage, and 196MB page file usage. I have changed from jumpered back to jumperless settings. I double checked jumpered voltage settings and did find 2 set incorrectly for unknown amount of time--mobo manual illustrations for settings hard to interpret for VIO and VIO1 which were set for overvoltages for 150 and 100 millivolts, which shouldn't be enough to fry anything. I have checked the condition of motherboard components, especially caps, both running and disconnected from power. No overheating of any components or IC's, bulging or leaking caps or other visible damage. Is there anything else that could cause this besides a logic or other electrical problem. Memory is fine--tested extensively with both memtester and the M$ memory test utility. I have already replaced the processor and if I buy a new motherboard and still have the same problem, I am going to be oh so disgusted. I don't think it is a power supply problem, but what would happen if it were? I have checked thoroughly everything I know to check. I am hoping that by including the Firefox failure log, perhaps the programmers out there will be able to find something that I do not know how to interpret.
"Internet Explorer, You're Fired"
Ignore the liberal media. They do not report the news but their slanted infotainment version of it, and should be declared enemy combatants for willfully undercutting and sabotaging the ongoing war on terror. It's OK to disagree with the reason for the war, but sabotaging the effort is treason.
Just a quick shot... Do google search on JS3250.dll. There seem to be many crash issues revolving around this dll (or a particular version of it) an Firefox.
Please remember to post back whether your problem is resolved or
not, so that others may gain from the knowledge.
I looked at bugzilla and a couple of other sites, but didn't find anything relevant that I could make any sense of, since bugzilla is a developer site. Why does everything work fine at default speed but not at full cpu speed? That is the main thing that I am stuck on. The system has been booted for about 9 hours now without the first error. BTW, how did you determine from the log info that JS3250.dll had crashed?
"Internet Explorer, You're Fired"
Ignore the liberal media. They do not report the news but their slanted infotainment version of it, and should be declared enemy combatants for willfully undercutting and sabotaging the ongoing war on terror. It's OK to disagree with the reason for the war, but sabotaging the effort is treason.
That dll was flagged as creating an error in one of your prior (other thread) postings. And since Firefox seems keeps coming up in these crashes and that dll has reported caused users issues with Firefox (and related software), ... Plus, IE also seems to have had an issue (in your prior posts), and since JS3250.dll is javascript related it makes sense that it could/would have an impact on multiple browsers.
Last edited by DrMDJ; January 21st, 2005 at 07:28 AM.
Please remember to post back whether your problem is resolved or
not, so that others may gain from the knowledge.
OK, that makes sense. I guess I should have reviewed my own post first, huh?
"Internet Explorer, You're Fired"
Ignore the liberal media. They do not report the news but their slanted infotainment version of it, and should be declared enemy combatants for willfully undercutting and sabotaging the ongoing war on terror. It's OK to disagree with the reason for the war, but sabotaging the effort is treason.
Wow, what a crazy ride it has been, not to mention frustrating. Got new motherboard, installed it. DOA. RMA'ed it, got replacement cross shipped, almost 2 weeks downtime. Installed it, installed Windows and some software, running in VGA mode. No problems, life is peachy. Installed video card drivers and software for an Asus V9400-X/TD 8x AGP with 128 MB DDR and is based on an Nvidia GeGorce MX4000 GPU. Suddenly life is not so good. Very difficult to boot, strange behavior. Could not uninstall drivers and revert to VGA mode, uninstall routine indicates software is not installed. OK, fine, buggy install CD. Go to Nvidia website, download and install version 66.94 drivers, so that I at least have a way to uninstall without hacking the registry and system files. Same problem. Difficult to boot, though it passes POST, and as before, if it boots at all, monitor just turns off, though system does not shut down. Reboot in safe mode, uninstall drivers, reboot, system works fine again in VGA mode, albeit in 16 color mode 640 x 480 resolution, not gona get it. Then I find this "arcane" but useful info buried in the readme file: 1. ASUS display cards consume more electrical power so that your motherboard must be able to provide enough electrical current in 3.3V power to maintain its normal operation. 2. ASUS display cards are recommended to use with Intel 440BX chipset for best compatibility. Now there's useful info, and nary an indication of this on the Nvidia or Asus website that I've been able to find, imagine that. So much for the logic of getting an Asus video card because I'm getting an Asus motherboard, to ensure compatibility. So, to avoid another week of downtime, I go to CompUSA and spend $80+ for a PNY card based on an Nvidia FX 5200 GPU that I could have got for probably half that online. So the question becomes what was Asus thinking by putting a graphics processing unit designed for 3.3 volt operation on a card (AGP 8X) for which the voltage spec is 1.5 volts, since 3.3 volts is the spec for older 1x and 2x/4x AGP standards. Oh, wait, like they care, let the beta testers, uh sorry, customers figure it out. So a few motherboards will likely get fried, not our problem. Fortunately, mine didn't, though I did get quite a scare when one of the 3 listings in device manager for motherboard resources indicated a !, which was resolved by uninstalling, rebooting, and letting windows reinstall the driver. I still have a lot of software to reinstall, including Windows XP.
"Internet Explorer, You're Fired"
Ignore the liberal media. They do not report the news but their slanted infotainment version of it, and should be declared enemy combatants for willfully undercutting and sabotaging the ongoing war on terror. It's OK to disagree with the reason for the war, but sabotaging the effort is treason.
Reply With Quote
