drpiety Posted December 20, 2005 Report Posted December 20, 2005 I have some BSOD lately but I am not sure it is utorrent. However it does not happen when I am at the machine about 8h running. I read that this was happening prior to 1.3, anyone having BSOD with the 1.3 ?
Ultima Posted December 20, 2005 Report Posted December 20, 2005 It's working perfectly fine here -- running hours at a time without a hiccup.
hofshi Posted December 20, 2005 Report Posted December 20, 2005 I'm running 1.3 for days w/o any problem.
Firon Posted December 20, 2005 Report Posted December 20, 2005 Don't just mention a problem, GIVE US DETAILS! Can't do anything without DETAILS.Hardware, software, client settings, etc.
drpiety Posted December 21, 2005 Author Report Posted December 21, 2005 Firon, before giving details and boring you I wanted to ask if there IS anyone on this planet with a BSOD on 1.3.Software outpost 3.0, PW, BLM, Antivirenkit pro (Gdata)Hard:Dlink Router 604 Computer: Betriebssystem Microsoft Windows XP Professional OS Service Pack Service Pack 2 Internet Explorer 6.0.2900.2180 not used Computername Benutzername Domainanmeldung Motherboard: CPU Typ Unknown, 2200 MHz (11 x 200) Motherboard Name Unbekannt Motherboard Chipsatz Unbekannt Arbeitsspeicher 1984 MB BIOS Typ AMI (11/17/05) Anschlüsse (COM und LPT) Kommunikationsanschluss (COM1) Anschlüsse (COM und LPT) Bluetooth-Kommunikationsanschluss (COM3) Anschlüsse (COM und LPT) ECP-Druckeranschluss (LPT1) Anzeige: Grafikkarte NVIDIA GeForce 6150 (256 MB)write queue size -1flush truenet low cpu falsethe rest is unmodified as i remember.
Firon Posted December 21, 2005 Report Posted December 21, 2005 Do you have the latest drivers for your NIC and motherboard chipset? And does it only happen with µTorrent? You may wanna test with Outpost uninstalled.
drpiety Posted December 21, 2005 Author Report Posted December 21, 2005 i have outpost running since the first second of UT and there was never a problem. BSOD started with 1.2 however the PC is quite new.Will check for updates. BSOD is very constant. when i get up and get back home. I will try not running UT for a day.As Outpost is also reported to make some BSOD i will try to use this worlkaround:http://outpostfirewall.com/forum/showthread.php?t=14789it deletes the Pagefile at shutdown.ill be back
1c3d0g Posted December 21, 2005 Report Posted December 21, 2005 Try writing down the exact number of the BSOD next time. One Google search with that number can reveal clues as to what is causing it, and hopefully point to a solution.
drpiety Posted December 21, 2005 Author Report Posted December 21, 2005 good idea, will do so. thanks
Firon Posted December 21, 2005 Report Posted December 21, 2005 Try uninstalling Outpost later and see if µT runs without crashes.
drpiety Posted December 22, 2005 Author Report Posted December 22, 2005 so far so good, with the swapfile deleted no BSOD this morning. Will check back if this stays so. So really looks like am Outpost Problem.
drpiety Posted December 22, 2005 Author Report Posted December 22, 2005 no bsod, the swapfile del did the trick. Thanks for the advices.
drpiety Posted December 24, 2005 Author Report Posted December 24, 2005 My beloved BSOD is back with 374. Will check what caused it. Where are the XP logs ?
chaosblade Posted December 24, 2005 Report Posted December 24, 2005 Upgrade to the latest beta and try to reproduce it, first.
chaosblade Posted December 24, 2005 Report Posted December 24, 2005 b376 is already on the download page here.
drpiety Posted December 25, 2005 Author Report Posted December 25, 2005 installed 376, to dump outpost is not an option. Worked well since the the first version of UT. Its either the new UT versions or my new system. Athlon or Dual Core maybe.
drpiety Posted December 26, 2005 Author Report Posted December 26, 2005 OK, I did as asked and removed Outpost and installed Zonealarm. Incrdibly my 1.0 Key still works for 7.0, not bad Zonelabs. Will report back if I am bluescreened. Thanks for the help, kind as allways.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.