|
When D/ling with eMule PC Restarts??????
|
|
|
fassa
Account closed as per user's own request
|
5. October 2003 @ 23:58 |
Link to this message
|
|
Well I think I have probably the weirdest thing happening lately...
Whenever I download with eMule,my PC, at any given time will just crash and restart. Sometimes after 10min or sometimes after 10hours. This is really frustrating as I have to restart emule all the time and get thrown at the back of the queue!
Has anyone had this happening to them before or is it just my PC?? Any suggestions?
Thanks!
***>>--Stray--<<***
|
|
Advertisement
|
 |
|
|
Staff Member
|
7. October 2003 @ 19:02 |
Link to this message
|
|
Is this where ur PC just switches off, like u just see a black screen and then it starts up again?
|
|
fassa
Account closed as per user's own request
|
8. October 2003 @ 00:25 |
Link to this message
|
|
Yeah it just restarts and reboots...I have been looking around on the net, some people have said that it could be hardware or sometimes your anti-virus. Whatever it is my pc does not like emule, overnet and after it is has been running anywhere from 10min onwards my PC just reboots!! WTF! It is really annoying!
***>>--Stray--<<***
|
Staff Member
|
8. October 2003 @ 05:42 |
Link to this message
|
|
Firewall is a cause of this one too, especially with Kazaa I believe, other problems would be power management and how much pressure you are putting on your comps resources!
|
|
fassa
Account closed as per user's own request
|
8. October 2003 @ 09:20 |
Link to this message
|
|
Well, it seems to working fine again now! WTF, anyway I disabled my anti-virus(!) but it worked fine now. Do you think that it could be with the amount of downloads that you have that that can go heavy on your comp resources and thus rebooting it? Also for anyone out there...With XP there is a setting that you can set so that youre PC doesn't reset on a failure. Goto Start, Control Panel, System and then Advanced. Click on the System restore, virtual memory button etc, and then unchech the restart system on failure(something like that) checkbox. At least when a critical failure occurs you will know what the cause is of the restart. It will show the infamous blue screen(apparently). So...Seeing that my emule runs fine, I suppose I'll see what happpens. Thanks for the replies anyway!
|
Staff Member
|
8. October 2003 @ 09:25 |
Link to this message
|
|
Do you think that it could be with the amount of downloads that you have that that can go heavy on your comp resources and thus rebooting it?
Of course yes, because when you start downloading with eMule, .part files and .met files are made, these files have to be properly hashed up when u start eMule along with any files you share so that would eat resources.
On another note, this doesnt just happen to XP this is common in all Windows OS's!
|
|
fassa
Account closed as per user's own request
|
17. October 2003 @ 00:24 |
Link to this message
|
|
It would appear that updating my cable modem drivers solved the problem of my PC rebooting randomly. Well...for the time being...also I opened up my case to let some fresh air in and that seemed to help as well.
Just some tips on the rebooting thing! Hope it helps!
|
Staff Member
|
17. October 2003 @ 18:00 |
Link to this message
|
|
Interesting lol! well if i have that trounle again I'll try it out!
|
|
enzyme
Newbie
|
30. October 2003 @ 02:51 |
Link to this message
|
|
I have a similar problem and have had this for 5 months or so on XP, but not on Win2k. I get this blue screen memory dump thing come up saying something like 'Driver IRQL not or less equal' and some type of problem with NDIS.SYS, a D1 error. The closest thing I came up with was
a nvidia driver problem, which I got from ms update, even after having uninstalled it the problems still seem to occur. If it is a firewall problem, why does the problem not exist on the Win2k side? I also tried disabling the firewall built within XP, that actually did sort out a low ID problem, but nothing in regards to rebooting the pc. This problem in its definition happens only with emule running and does not occur if emule is not running and only on XP. If anyone can guide us to a possible solution it would be much appreciated.
|
|
fassa
Account closed as per user's own request
|
30. October 2003 @ 04:17 |
Link to this message
|
|
I don't think that there is any hard-fast rule on diagnosing the problem why this happens. Have tried typing the error message into google? That might give an explanation as to why the problems occurs. As I said earlier after I updated my cable modem drivers and opened my box up to cool it down, the problem disappeared. That was about a 3 weeks ago! So yeah, I'm smiling. I think you should just try a lot of stuff and maybe something will set it right!
***>>--Stray--<<***
|
|
enzyme
Newbie
|
3. November 2003 @ 01:42 |
Link to this message
|
|
Interesting that you mentioned about changing the cable modem drivers, because I've just done the same and emule and XP seem to be running together without no problems....24 hours and counting. When I installed XP it offered to install MS cable modem drivers, which I accepted. On Win2k I have to install them manually from a floppy. I basically changed/updated the driver on the XP while it gave some warning about the drivers not being digitally signed or something and went ahead with it, and so far so good. I'm still a bit gobsmacked however, of all things....cable modem drivers!
|
|
Wicked666
Newbie
|
14. December 2003 @ 17:57 |
Link to this message
|
|
Where can one go to update modem drivers? Is there a general download I need or does it have to be specific to the company I got mine from?
|
|
Daxx
Member
|
14. December 2003 @ 18:24 |
Link to this message
|
|
I WinXP ya can go to ControlPanel--System--Advanced and there choose the settings 4 what I reckon is called something like "Start and Restore" in English.
There ya have different options bout how WinXP should react when a system-error occurs...
By default this is set to "restart" and make a "memory-dump" which is quite stupid (as always with MS) cuz ya just dont have a clue WTF happened...
But, ya can change it by unticking "Restart Automatically" and then the next time this error occurs ya will just get an old-fashioned BSOD (Blue Screen) whith some details about where the error occured will show up and it will give ya more help to track down where the error occured.. ;)
Those "error codes" can however sometimes be quite cryptic but if ya dont get an exact description with file/driver-name and just a memory-address I suggest ya write down the complete error-code and make a search with it on Google cuz theres lotsa info out there about it.. ;)
Many times Ive experienced that this is caused by some driver-problem...
|
|
Advertisement
|
|
|
|
Daxx
Member
|
14. December 2003 @ 18:29 |
Link to this message
|
|
|
