TCPIP.SYS blue screen crash
Posted in xn--kfs74mzzid01b.com edit by jane on January 8th, 2009
I wanted to find out if anyone else has had a problem with OP2 causing XP Pro to crash out to the blue screen memory dump... With error arising from TCPIP.SYS and error message something like DEFAULT_IRQ_NOT_LESS_THAN (I forget exactly what it says... have not written it down recently... but can do next time it happens)?
This seems to happen while browsing on a dial-up connection.
XP Firewall is not enabled and was disabled when OP was installed. Presently running on latest version.
XP Has SP1 installed and most updates etc.
It seems to happen when I am doing certain "intensive" actions in the browser... What I mean by this is it doesn't seem to happen when things are just sitting there or I am reading a page... It will happen when I am actually downloading a page etc...
I have not managed to ascertain any particular action that causes it though.
It happens very regularly when using IE6.
I have now started using Mozilla Firebird (highly recommend it BTW) and as far as I can tell it happens much less... but has still happen a couple of times today since using Firebird.
I wish you all the best and extend my gratitude to anyone that is able to assist.
Regards,
Jonathan
Be advised, you should probably start the GoldMemory test before bed time and examine the results in the morning. If it is memory, you should see fairly consistent results with regards to the bad locations found. And yes, GoldMemory the free version will do a decent job in this respect.
Keep us advised of your progress. :)
1. In Control Panel, click Performance and Maintenance.
2. Under Performance and Maintenance, click System.
3. On the Advanced tab, in the Startup and Recovery group box, click Settings.
4. Under Write Debugging Information, select Small Memory Dump, and then click OK.
5. In the System Properties dialog box, click OK
I still strongly suspect your video driver. I suggest you update that as well.
As far as I can tell the reinstall procedures as outlined elsewhere in this Thread would seem to have worked.
I actually haven't tested IE6 since the complete overhaul, which was what I was using to browse when the consistent crashing was happening originally. One of the positive outcomes of this whole ordeal was that I discovered Firebird and am finding it to an excellent choice of browser.
I did get the crash in Firebird prior to the super reinstall operation though and it has not happened since.
I will, however, (reluctently) do some browsing with IE6 and see how that goes but I don't plan to use it as my primary browser now that I am on to something much better.
So... it would seem, for now, that this situation has been resolved.
I give much thanks and appreciation to those that helped me through it. I am real pleased I am not writing this update as a convert to some other inferior firewall!!
With my regards,
Jonathan
Yes, I have Windows XP Home with SP1 and all of the latest patches and updates installed. The only thing that I ignore sometimes is the Windows driver recommendations. I prefer to get my drivers directly from the vendor, for example Nvidia.com in the case of my video card. All other Critical Patches and Recommended Updates get loaded onto my system.
Good luck with your investigations. I will be very interested in hearing about your progress and hopefully good results.
Have a good day. :)
Now you can concentrate on using OP rather than fixing things.
Best of luck to you.
Welcome to the forums. :)
Please try the following:
1. Search for TCPIP.SYS using the forum search function and see if there are any threads that might help. For your convenience, here are the Search Results:
TCPIP.SYS Search Results (http://www.outpostfirewall.com/forum/search.php?s=&action=showresults&searchid=149976&sortby=lastpost&sortorder=descending)
2. If #1 does not help, please try uninstalling and reinstalling using these instructions:
Extended Outpost Uninstall/Reinstall Instructions (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=7188)
3. If #2 does not help, please try report this BSOD to Agnitum through the following link:
Agnitum Support Form (http://www.agnitum.com/support/supportform.html)
Keep us advised of your progress.
Have a good day. :)
I'm sure I'd be checking the memory and drivers. But the strangest thing is that there 3 different machines in my office. Two P4 with no HT and one Athlon 1.7Ghz. They all have diff. memory sticks. 2 machines with P4 have BSOD's.
My colleage has an Athlon machine at home. Had an OP 2 installed, had BSOD. After system reinstall has OP 1.0 installed - had BSOD.
First I checked my sticks with DocMemory - 't was ok as in your case. But when I found out that those other machines have BSODs either - I decided that the faulty memory on every machine would be to much of a coincedence.
The question is - why sending a report to MS Online crash analysis site returned that BSOD was caused by a filtnt.sys on all those 3 machines?
Maybe I just not quite understand the meaning of the fact that the bug was caused by the application/driver residing at the address NxNNNNNNNN in the memory space.... And why is the very that app/driver is to blame? What else in the system could made it to cause BSOD?
I may sound lame but I'd very-very like to crack this case with the filtnt.sys and stick to OP in the future.
It'll be usefull, I'm sure.
If everything's ok with your memory, then the next thing to check is the video, in my case at least. It just the only thing in common on my 3 machines with BSOD's and another one is WinXP SP1, by the way.
When I detonator 44.03 and OP1 were installed - everything was A'OK. Not sure whether SP1 was installed or not.
If your memory turns out to be having bads or smth, then I'll sure will check mines.
If mine's are ok, then I will install WinXP Sp1 with the possibility to roll back and OP2 with Detonator 44.03.
If I have BSOD's I'll roll back to WinXP with no SP1. If I still be having BSOD's, I'll install Win2000 SP4 and will rest in peacefully, 'cos that's a 100% tested and fault tollerant variant.
Amin. :D
I have a D-Link DFE 550TX card. And there no drivers at the vendors site. They say that for WinXP needed drivers are already built in into the WinXP distributive.
After the WinXP SP1 installation I went to the Windows Update site and there was a Â-Link Ethernet adapter driver update. I installed it, but don't know whether they are better or not..:confused:
Is there a way to check the LAN card driver?
But, since you are getting consisten failures on your systems, I would look for commonalities in those systems.
That's exactly what I'm up to. First thing in the morning. This forum gave me a fresh thoughts and a willing to get to the bottom.
On Win2000 SP4 I had no problems at all with OP 1.0 either. (Mb I'll reinstall Win2K after all)
Question to you, David:
did you have SP1 installed on your Win XP Home PC?
I still think that is the most probable issue here.
;)
Here how the things are on my PC:
If I have OP installed and running - I get a BSODs caused by one of OP filter drivers.
If I have OP installed and NOT running - I have a BSODs caused by one of OP filter drivers.
I have different Stop Errors in BSOD info: DRIVER_IRQL_NOT_LESS_OR_EQUAL and others
If I have OP UNINSTALLED - No BSODs.
Most of the times BSOD are encountered when there is a heavy network activity - on LAN or Internet Downloading (eMule).
And, in my case, BSOD pop up doesn't depend on the browser type.
So, what is in common here - is the Win XP SP1. My guess is that OP and some new file in SP1 are in conflict :confused:
Another thing is that if SP1 is not installed - everythings just fine.
By the way - BSOD happened with OP pro 1.0 and Win XP SP1 either.
So what I'm implying is installing NOT the whole SP1 but just major critical bugfixes. At list till the SP2 release date or till OP guys deal with the conflict.
Sorry my being too wordy :boo:
For what it is worth...
I am almost 100% sure this started after I installed SP1.
I have always known it happened after I installed a whole lot of updates back in Oct/Nov last year and I seem to recall that SP1 once one of them...
Thanks for your input. I am sorry to hear that you too have this BSOD issue... or one similar to it.
Regards,,
Jonathan
I misunderstood. I thought you had done a repair install. The way you defined clean install- turning off all running applications - is the proper way to load all applications. I'm sorry that I didn't realize this sooner. You should continue this practice of doing a "clean install" for all applications you install. It'll save you much time in the long run.
PS: It's not really necessary to turn off all services. On the other hand it certainly can't hurt since after the reboot they'll turn on again.
Actually what I had been referring to as a "clean install" was regarding a clean install of Outpost itself. Earlier in the thread there were detailed instructions given (via a link) on how to completely remove all aspects of Outpost from ones computer (digging everything out of the registry too) etc. before reinstalling it.
Because I couldn't even boot XP after reinstalling OP after that I tried installing with msconfig turning off all aspects of the system that it can.
I trust that is now clear... I am sorry if there was some misunderstanding.
In regards to use of MSCONFIG for installations as "proper" or normal practice.... Really ?
It's the first time I have used it for the install of an app. I can't say I've ever found it necessary before and I have over 50 apps on this computer at any given time. Perhaps God has been on my side and provided a prob free situation...
I can't say I would suggest to other general users that they need to use msconfig in order to do an install of some app....
But I guess for those that are cautious it might be a useful precaution to take.
Regards....
That has to be the slowest procedure I've seen a computer carry out!!
I have run Goldmemory... It provided me with an unexpected holiday which was nice although unexpected.
:stunned:
It took about 18 hours to make one pass through 256MB of RAM... Not the sort of thing you site by the computer waiting to complete!! It then kicked into a second round of checking which I aborted this morning as 29 hours was about as long as I could go (two nights and one full day)... I actually thought it said that LOOPING/CONTINUOUS MODE was only avaialble on registered mode... I did use the /L commend though to see if that would work (not knowing how long one pass would take at that point)
Results as follors...
------------------------------------
01:21(AM) 11/06/2003 Memory: 261056 KB, 473 MB/s
Normal Test
Elapsed Time/Test Count: 29:08:28/1
TEST PASSED
Program interrupted by user!
--------------------------------------
I assume then that this means my memory is okay...
Does it normally take this long for a program like Goldmemory to do its thing? Amazing!!
So it seems it is not a memory issue.
I have installed all the latest patches and updates for IE6.
I will now do some browsing during the day and see what happens...
If TCPIP still crashes then I'll do the full uninstall/reinstall of OP and TCP/IP stack.
Thanks again...
Jonathan
I'm using Opera and it doesn't prevent me from getting BSOD's.
The thing is that IE is like a core everything in the Windows interface is build upon. So... it doesn't really matter if we stop using IE as a browser. We just postponing the next BSOD pop up. :)
... Frankly speaking I was praying for my machine to keep working more than 1 day ;) So it might be usefull.;)
Cheers!
So... I have managed to at least get OP installed and running again...
I used the MS Config consol to disable ALL aspects of windows that it can disable, and then I also removed the Ethernet and Internal modem installs.
I then rebooted and installed OP.
I then rebooted (still with Config Consol disabling everything) and it booted up fine. So bit by bit I started to enable things again using the Consol tool. And rebooting each time.
Eventually everything was enabled and it was booting up fine.
Once I have enabled all the services (the last thing I did) XP then detected the modem and ethernet card and installed them again.
Reboot and everything fine. So... At least I have OP on here...
Of course, I still do not know if it works properly (ie. no more BSOD).
BUT at least I have now installed it when the environment was entirely clean, free of all clutter, free of all networking devices, free of all past installation files and reg entries, and with a clean TCPIP stack.
So what I can say is that if I still get a BSOD then there is really not much I can do... expect installed XP which is not an option (as it would take some days to get this thing set up again).
I shall keep you posted on how things go.
In case this still gives me BSOD then I would still love to know what people think is the next best Firewall (for free or for purchase).
Thanks,
Jonathan
In the case of your ethernet card driver, you have done all that you can at this point by just updating it to the latest version. Hopefully you have already done this with your video driver also. Now we will have to wait and see if things improve.
Lots of discussion here... which is good.
So the gist I am getting is that perhaps OP is simply using my system in a way that is highlighting an existing issue... with memory perhaps... or with drivers etc.
I will look into the memory thing with Goldmemory (is it free - hope so... only want to use it this once).
An interesting point...
Today I have continued to use the net,,, doing all the things I normally do... But continueing to use Firebird as opposed to IE6. So far... no crashing and I have had Outpost running the whole time. Still doesn't take the stress away of wondering just when it might crash and I lose what ever I am working on etc... Would be nice to know it was resolved entirely... not just by me using another browser.
I have not done the reinstall just yet... been real busy today... will do that shortly... after the mem test.
Another point... I do find it interesting that the system file having the issue is part of the TCP/IP stack (something OP obviously must have intensive interaction with)....
Regards,
Jonathan
Ditto for all other built in devices.
It's probably OK to get the drivers directly from NVIDIA but laptops sometimes use proprietary code. The best thing to do is check with Acer to be sure.
Ditto for all other built in devices.
I did check the Acer site... They have some drivers they released a year or so ago... NVIDIA has released numerous updates in that time... I have actually been using more recent NVIDIA releases as I updated the vid driver earlier in the year to try and solve this OP problem and some other crashing prob I had (which did get solved by the update as far as I recall).
Anyway... now I am not sure which to use. I will email Acer and find out if there is an reason I should NOT use the latest NVIDIA driver.
Thanks,
Jonathan
I have to agree. Multiple machines having memory problems is highly unlikely. But, since you are getting consisten failures on your systems, I would look for commonalities in those systems. Perhaps you use a particular application or piece of hardware on all three machines. I am not sure. But, it is worth investigation. I have run Outpost on an AMD system with Me and also XP Home and I have never had serious or unsolveable problems. I even have it running on a 98 laptop without issue at the moment.
There has to be something, so please keep looking at your system hardware, drivers, and applications (including startups) that are running while Outpost is running.
Glad you all are still here and wanna thank Inspired for his patience during the test :D .
Now I know I won't test my memory, at least till the moment I'll be willing to reinstall my system. :eek:
Concerning the firewall chenge: I would suggest the Sygate personal Pro (or free version), which I use these days, or Look'n'Stop firewall. The latter I haven't tested yet, but I saw it perfoming good and stable enough in different tests on several sites.
But! The best and most comfortable user interface has OP - IMHO of course. Another one with such a UI was AtGuard, but that was back in a days and it's dead now. OP has much more easier and exact (or specific) process of rule creation than ALL other firewalls I've seen and used. (I used 5 and seen 3 more) I'll still be bouncing towards the OP despite of Sygate some advantages.
Ispired, if you have never got a message "Your system has recovered from a serious error" and send a report option in it after a BSOD, then I suppose you haven't error reporting turned on. (System properties -> Advanced Tab -> Error Reporting)
David, thanks for advices and support! I'll keep in touch as I will update video drivers. I discovered yesturday nVidia has released WHQL certified drivers two times since the release of the version I currently use.
I' sure together will get pass that BSOD thing. I CAN FEEL IT! :D
Okay... I am going to do a full uninstall... clear out all reg data etc... as per the instructions.
I have actually already done close to that a number of times... just not he manula clean out of registry and TEMP files.
An extra step I am going to take is to get XP to rebuild the TCP/IP stack to it's original state. I will do this once Outpost is uninstalled, and prior to reinstalling it.
I found on the MS support site that this commang, issued in the command prompt, will cause XP to rebuild the TCP/IP stack.
netsh int ip reset c:resetlog.txt
I mention it here because throughout this issue (goes back to Version 1.0 for me)... I have wanted to know how to completely rebuild the TCP/IP stack. Just removing network devices and forcing XP to reinstall them does not do it . So many this is of use to others.
I'll let you know how I get one.
Mind you, I have been browsing intensively through a whole variety of code, scripting etc heavy sites, pages, forums tonight and the problem has not occured... I am using Firebird however (which I am just loving)... so after doing the full reinstall I will use IE for a while and see if the prob occurs.
Also, in answer to the question about "how do I know it is OP causing the cracsh"... I have ascertained this is certainly the case.
It simply does not happen when OP is not running...
And when OP is running and I am on a dial-up connection (never happened on Lan net connection (adsl etc)) it invariable happens rather too often for any sane minded person to put up with.
Thank you both for the help.
Regards,
Jonathan
>I will look into the video driver - that too was quite likely something I updated back in late 2002 when this started to occur on OP1. BTW What makes you think it is the video driver?
Two reasons. 1. You said that this problems occurs when you are "doing certain intensive actions in the browser. Well, this creates more demand on your video system. 2. For XP, blue screens happen 90% of the time due to hardware, driver problems. Put the two together and the a strong possibility becomes the video driver. It may not be the problem but since it's so easy to change why not give it a try.
Normally Online Crash Analysis (http://oca.microsoft.com/EN/welcome.asp) will start automatically after a BSOD. I know that it does on my Windows XP box. The crash reporting process should take you directly to their site where you can login using a Microsoft Passport and report the error.
Are you saying this service kicks in even after a BSOD (which obviously results in complete system restart) ?
If this does not turn out to be hardware or drivers, then there must be some interaction with something running in the background, another service, or another application that you are using. Have you tried terminating some unecessary processes and then seeing if Outpost performs better. If there is an interaction between Outpost and another running process, at least we will know.
There is really nothing I am aware of that loads up as a Service or system process outside the normal WinXP stuff.
At this stage it is no longer a matter of OP performing better because it has now (after trying to improve the situation) resulted in OP not even being at all usable... meaning I can not even have it installed on my system because XP won't start with it on there...
So I am not really sure how practical it would be to try and test if other processes are messing with it... because I have to complete uninstall it just to get into XP...
Thanks for the help and input.
Jonathan
If this does not turn out to be hardware or drivers, then there must be some interaction with something running in the background, another service, or another application that you are using. Have you tried terminating some unecessary processes and then seeing if Outpost performs better. If there is an interaction between Outpost and another running process, at least we will know.
If I have OP installed and running - I get a BSODs caused by one of OP filter drivers.
If I have OP installed and NOT running - I have a BSODs caused by one of OP filter drivers.
I have different Stop Errors in BSOD info: DRIVER_IRQL_NOT_LESS_OR_EQUAL and others
If I have OP UNINSTALLED - No BSODs.
Most of the times BSOD are encountered when there is a heavy network activity - on LAN or Internet Downloading (eMule).
And, in my case, BSOD pop up doesn't depend on the browser type.
So, what is in common here - is the Win XP SP1. My guess is that OP and some new file in SP1 are in conflict :confused:
Another thing is that if SP1 is not installed - everythings just fine.
By the way - BSOD happened with OP pro 1.0 and Win XP SP1 either.
So what I'm implying is installing NOT the whole SP1 but just major critical bugfixes. At list till the SP2 release date or till OP guys deal with the conflict.
Sorry my being too wordy :boo:
Hi inspired,
Yes, GoldMemory will take quite a while. But, if the memory passes that test, it is most likely good memory. As far as actions for the immediate future are concerned, I would do the following:
1. Make sure that the video and ethernet drivers are up to date.
2. Reinstall OP and the TCP/IP Stack as you noted above.
Thanks for the update.
Keep us advised of your progress. :)
I see that NVIDIA have updated drivers for all their cards... but Acer (who make the laptop) have not posted any new ones in a while. Should I go ahead and use the updated drivers from the graphics chip manufacturer?
Also... updating Ethernet Drivers... Again... ethernet built into laptop and no new drivers... but again the manufacture of the ethernet chipset might have something new out... is that worth doing ? (it is only MODEM connections that I get the crash... never on Ethernet based ones).
Regards,
Jonathan
I have to agree with Manny. Drivers and also hardware faults are the primary cause of BSODs. My first post here was concerning a filtnt.sys BSOD with the stop error being DRIVER_IRQL_NOT_LESS_OR_EQUAL. And, initially I blamed Outpost. But, I also closely scrutinized every detail of the error and BSOD that I was getting and made good use of Microsoft Online Crash Analysis. After closely studying the problem and making sure my drivers were up to date, I decided that I should check my memory as this is the easiest piece of hardware to check. I used two applications, DocMemory (www.simmtester.com) and GoldMemory (www.goldmemory.cz), for my tests. DocMemory showed all of my RAM as consistently good. But, the checks happened so quickly that I wondered if DocMemory was really doing a thorough job. So, I tried GoldMemory and it found some bad memory addresses in my RAM. And, it found those bad locatations with great consistency. Once I identified the stick of RAM with the bad locations, I replaced it and have never had a problem since.
My point is that just because a problem has started right after installing Outpost, does not mean that Outpost is the cause. This thinking can be applied in any case where a new application is installed. Different applications may stress our processor or memory differently. So there can easily be a case where a new application is installed and all of a sudden there are problems that seemingly can be blamed on that application. In these cases, as I found out, quick judgements should not be made. A dull and detailed analysis of the problem including checking drivers, other installed and running software, and checking hardware should be done. The problem may indeed lay elsewhere. That said, if everything is checked, and it is still Outpost, then a bug report must be made directly to Agnitum through the Support section of their site. I believe that I have already provided a link above.
Have a good day. :)
[B]Hello Jonathan,
Welcome to the forums. :)
Please try the following:
1. Search for TCPIP.SYS using the forum search function and see if there are any threads that might help. For your convenience, here are the Search Results:
TCPIP.SYS Search Results (http://www.outpostfirewall.com/forum/search.php?s=&action=showresults&searchid=149976&sortby=lastpost&sortorder=descending)
Thanks for that. Yes, I had searched and read through the posts. Not much mention though of this... Some V1 issues... one or two V2 tcpip.sys issues but no solution.
I did manage to find the error msg though from someone who had a similat prob on V1...
DRIVER_IRQL_NOT_LESS_OR_EQUAL
With the file being tcpip.sys...
2. If #1 does not help, please try uninstalling and reinstalling using these instructions:
Extended Outpost Uninstall/Reinstall Instructions (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=7188)
I will read over this now and let you know how I get on.
I greatly appreciate the help. With my regards,
Jonathan
Originally posted by inspired
I shall keep you posted on how things go.
In case this still gives me BSOD then I would still love to know what people think is the next best Firewall (for free or for purchase).
You can be assured that if it comes to you having to switch firewalls, we will do our best to give you some alternative choices. Our forum is interested in your security, is supported by volunteers, and cares about your experience with Outpost. So, if Outpost does not work for you, we will give you some good alternative choices.
Have a good day. :)
I was hoping I'll be the first to try the "Matrix reloaded" thing :D
Glad there is hope at least and a proof at most to the fact that BSOD bug can be cured in my case either.
By the way, could you tell me the OS + Service Packs (if any) you had reinstalled? (My connection is slow and I'm short in time to list back thru the posts...)
Ispired, if you have never got a message "Your system has recovered from a serious error" and send a report option in it after a BSOD, then I suppose you haven't error reporting turned on. (System properties -> Advanced Tab -> Error Reporting)
Hi Alexx187,
That's the odd thing... I do have Error Reporting turned on for Windows and for applications. I recall when I first had this laptop that messages use to get sent to MS and I could get info on the results. But none of that for many many months... Any body know how I reset this Error Reporting feature?
Also, I enjoy your enthussiam and nature as expressed through your posts.
--------------
David and others... I'll see how I go with this extrememly "clean" installation... If I get another BSOD I'll let you know.
Thanking each of you...
Jonathan :)
I would like to do that, but unfortunately I don't know how.
I have a D-Link DFE 550TX card. And there no drivers at the vendors site. They say that for WinXP needed drivers are already built in into the WinXP distributive.
what you would so is uninstall the device in device manager and reboot. Windows will see it as a new device and install a fresh copy of the driver.
After the WinXP SP1 installation I went to the Windows Update site and there was a Â-Link Ethernet adapter driver update. I installed it, but don't know whether they are better or not..:confused:
Is there a way to check the LAN card driver?
Drivers at the WU site tend to be a little old because they have to go through so many hands. There's nothing worng with them but the latest drivers are at the vendor's site. I prefer to get them there.
There's no real practical way to check a driver. Usually you have an indication that there's a problem and you get an update or reinstall the device. It's simple and easy to do. It may not fix the problem but on the other hand, nothing is hurt either.
No, as I said in my post above it's not necessary to shutdown services before installation. What's good practice is to shutdown all software including antivirus programs. The AV may require shutting down a service but not necessarily through MSCONFIG.
It's like this: It's recommended you change the oil in your car every 3,000 miles or so. You don't have to and can probably stretch it to every 15,000 miles if you want to. It's up to you whether you pay now or pay later. Same thing for installing software. Yep, you can just go ahead and install it right away and get away with it. But a safe approach will save you time and headaches in the long run. It's up to you.
PS: It's not really necessary to turn off all services. On the other hand it certainly can't hurt since after the reboot they'll turn on again.
Not good news unfortunately.
I followed the detailsed UNINSTALL/REINSTALL instructions that were suggested earlier in the thread.
I also reinitialised the tcpip stack as per the details I gave earlier in thread.
I reinstalled OP and this time my computer would not even start up... Windows XP would try to load... The black screen with the progress bar on it was showing for some time with the hard drive loading things... then it woudl crash... out to BSOD... with error IRQ_NOT_LESS_OR_EQUAL and a memory address. But this time no text below the memory address so no mention of the offending driver (previously always TCPIP.SYS).
I had to then boot in safe mode and restore back to pre-installation of OP.
Tried reinstall again...
Same problem...
Again had to restore back to pre-install.
So I am now at the point where I can not run OP at alll... which is not exactly progress. I had at least got to the point where I could run OP with Firebird and get a BSOD less often... Oh well...
Any other suggestions?
BTW... I have not done anything with the graphics driver yet. But to be honest I seriously doubt it has anything to do with that. When the graphics driver has cased probs in the past the offending driver displayed in BSOD was generally kernal.* (forget the extension) or something like that.
Also, I can see how the graphics driver is resulting in OP creashing the system PRIOR to XP actually completing startup.
So... The plot thickens... the challange goes up a notch... And the **** seems to have hit the fan. I suspect it's over to another firewall :boo: ...
Any suggestions?
- Further ideas on how to solve OP issue
- OR the next best option for a firewall. I have tried a few and OP is by far the best I have seen... but if it ain't gonna work then I'll have to go to the next best thing... Anyone have an opinion on what the best option is?
ALSO... How to I submit a crash dump to MS for free analysis? I seem to recall a post where someone said they did this... ??
Thanks so much....
Jonathan
Yes, GoldMemory will take quite a while. But, if the memory passes that test, it is most likely good memory. As far as actions for the immediate future are concerned, I would do the following:
1. Make sure that the video and ethernet drivers are up to date.
2. Reinstall OP and the TCP/IP Stack as you noted above.
Thanks for the update.
Keep us advised of your progress. :)
By the way, could you tell me the OS + Service Packs (if any) you had reinstalled? (My connection is slow and I'm short in time to list back thru the posts...) [/B]
Thanks.
Now... I did not resort to reinstalling the OS. It's not really an option for me. This computer is a business machine and has a lot set up on it... It takes days to get it set up and then ongoing things for many weeks as it's not really an option to reinstall the whole PC in one hit.
So... Nothing reinstalled in that regard.
Running XP Pro SP1 with all updates.
The final key in my case was doing a clean install of OP in something close to SAFE mode but not safe mode... I used msconfig system to turn off all services and all other stuff it can turn off. Then in that state I installed OP.
Then turned all those things back on (with msconfig) and voila.
If it came to the point where an OS reinstall was required I would have had to jump to another FW app.
David... yes me too. I can say, however, that I have now done some pretty heavy duty use of web browsing (10-20 pages open, javascripts on many of them, files download, Quicktime content running, media player going at the same time, etc etc.) which certainly brought the system down before.
I have actually not got around to testing with IE6 (the browsers I was using previously) except to browse through MS site, download some updates for XP and Office etc. No probs. I won't be bothering to test much beyond that because Firebird is just so much nicer to use and it's all working as it is. Still... I will post an update if anything out-of-the-ordinary happens.
To provide you with the best help you need to convey the contents of your error message exactly. From what you wrote it sounds like you are having an IRQ conflict.
Go into device manager and see if it lists any problems. About 90% of the time blue screens are caused by driver problems. I'd look at the video driver since you say certain "intensive" actions of the browser cause the problem and update it at the vendor's site.
Yes congratulations. I am somewhat of a skeptic, so it will be very interesting to me to hear about your experiences over the coming weeks.
By the way, what uninstall thread?
Have a good day. :)
I will run Goldmemory over night... I gather it takes a while then... doing multiple passes over the memory etc...?
I will look into the video driver - that too was quite likely something I updated back in late 2002 when this started to occur on OP1. BTW What makes you think it is the video driver?
Today it crashed whilst browsing with Firebird... so there goes that temp answer.
I noticed that it happened when a page with substantial java menus (which involved a Java engine or something to process) was loading. I recall that this has been the case more than a few times before. Not sure what to make of that though.
I will update IE too..
Thanks,
Jonathan
Perhaps it would be a good idea to check out the ethernet (network card/modem) driver too, just to be sure. :)
An interesting point...
Today I have continued to use the net,,, doing all the things I normally do... But continueing to use Firebird as opposed to IE6. So far... no crashing and I have had Outpost running the whole time. Still doesn't take the stress away of wondering just when it might crash and I lose what ever I am working on etc... Would be nice to know it was resolved entirely... not just by me using another browser.
I have had the same experience, but I am using Opera (I was the first one to suggest using an alternate browser). I have been BSOD free for several weeks now. Whenever I see threads on crashes, reboots, etc., I almost instantly think it appears to be the same problem that I had with my hyperthreaded system when I was using IE!!!
Also, I am noticing a lot more posts on this specific problem. Initially, it seemed it was just me and one or two others, but as this continues to affect more users, I suspect it shall get increased attention from Agnitum.
#If you have any other info about this subject , Please add it free.# |
