Problem - Crashing with ProcessPendingReads() or ProcessPendingWrites() Or likely Phinny

[arb22]

Hi, I am new here, and fairly new to using this, I have been having all 3 boxes crash within moments of each other (not normally all at once, just closing) The EQBCS.exe reports line like
Server::ProcessPendingReads() client [char] Disconnected or Server::ProcessPendingWrites() disconnected. I think I have everything up to date (found a thread where that was the reported fix a few months ago) I don't seem to see any other log file for an error.

Thanks again for any tips.

 

[Sic]

Hi, I am new here, and fairly new to using this, I have been having all 3 boxes crash within moments of each other (not normally all at once, just closing) The EQBCS.exe reports line like
Server::ProcessPendingReads() client [char] Disconnected or Server::ProcessPendingWrites() disconnected. I think I have everything up to date (found a thread where that was the reported fix a few months ago) I don't seem to see any other log file for an error.

Thanks again for any tips.

are you getting any .dmp files? these would go in your mq2->release->log folder

if you are, and would like me to take a look at 1 or 2 of them, please PM them to me, keep in mind there may be personal information like toon names or server information

the last time someone mentioned that eqbcs issue, it was just a force close due to an unrelated crash > here < might be where you saw that

 

[arb22]

Alas I do not have a a .dmp file or a log folder, checked to see if it was hidden. Is there something I should do to turn on logging that will produce a detailed file that I may have missed during setup? That is the thread I was looking at when I searched those messages ?

 

[Sic]

Alas I do not have a a .dmp file or a log folder, checked to see if it was hidden. Is there something I should do to turn on logging that will produce a detailed file that I may have missed during setup? That is the thread I was looking at when I searched those messages ?

you should have a logs folder inside your Release folder if there were dmps or not.

are you *sure* you don't have a logs folder?


and to answer your question - no you don't need to turn on any logging. if you are having a crash that results in a .dmp it would go in that folder

 

[arb22]

ok, well I don't have a log folder but perhaps that is pointing to maybe something going wrong on my system during the install? Thank you again for your help thus far and comitment to the community

 

[Sic]

ok, well I don't have a log folder but perhaps that is pointing to maybe something going wrong on my system during the install? Thank you again for your help thus far and comitment to the community

its very possible that a log folder isn't created unless there's something to go in there, i just wanted us to double check just in case

 

[arb22]

My best guess / working thery at this point is it has something to do with the server, Phinny, even though it no longer is Truebox as of the last patch. the time to crash varries, but I have tried duplicating it on lower level charicters on cazic and have not yet crashed, but it has happened when I set it all up on the 2nd PC.

Any other Phinny users here able to say if they are having similar problems or not by chance/

 

[arb22]

Test copy and a couple hours of play seems to confirm my hypothesis as that allowed me to test with the same characters and zones , I think there is ether something in EQ or something in MQ2 that still at some point sees Phinny as a "no go" and leads to a boot.

 

[sfajk1]

I posted on another thread with no others from phinny responding. I am having same problem on phinny.

 

[brainiac]

almost certainly its because mq2ic still is anti-phinny

 

[Sic]

almost certainly its because mq2ic still is anti-phinny

sounds likely, tho @eqmule said he updated for selo/phinny can you confirm mule?
Selos is getting merged into Povar, but phinny appears to be staying phinny

 

[arb22]

Thank you for passing this on to have this looked into, hopefully that is the case and makes it easy to fix.

 

[Sic]

Thank you for passing this on to have this looked into, hopefully that is the case and makes it easy to fix.

Spoke to mule this morning, he said he'd take a look

 

[arb22]

Just wanted to toss this out there for others who may be having this. The issue is non existent in mqnext I suspect likely due to what @brainiac said about mq2ic and my short research and new understanding that next does not use it. More experienced users feel free to correct me on that.