PDA

View Full Version : Black screen of death is back.


Elkay
10-29-2004, 06:06 PM
It's back as of the last CVS update. Not sure what changed, but the problem had been fixed for a couple weeks and all of a sudden tonight it's back after I updated to the latest CVS. Zone shows the following:

10864: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10880: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10896: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10912: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10928: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10944: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10960: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10976: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
10992: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
11008: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
11024: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................


For many, many lines before and after this. At the end I get:

0: 00 FF FF FF 00 00 00 00 - 00 00 00 06 28 9F 00 00 | ............(...
16: 00 00 00 1E 05 05 00 01 - 4B 32 00 73 96 FF 00 00 | ........K2.s....
32: 00 00 00 88 FF FF FF 00 - 00 00 00 08 00 00 01 00 | ................
48: FF 04 00 00 00 03 4D 65 - 6C 6F 00 00 00 00 00 00 | ......Melo......
64: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
80: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
96: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
112: 00 00 00 00 00 00 03 04 - 00 64 00 46 00 91 04 00 | .........d.F....
128: 00 00 E0 27 FE 0D C1 07 - 00 00 00 74 FF 02 FF FF | ...'.......t....
144: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 48 40 | ..............H@
160: 01 1F 85 EB 3E FF FF FF - FF 00 00 F7 00 00 00 00 | ....>...........
176: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
192: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
208: 00 00 00 00 16 00 00 00 - 03 00 00 00 03 00 00 00 | ................
224: 03 00 00 00 03 00 00 00 - 03 00 00 00 31 29 00 00 | ............1)..
240: E2 29 00 00 00 00 00 00 - 00 FF 00 00 00 00 00 00 | .)..............
256: 00 00 8C 01 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
272: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
288: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
304: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
320: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
336: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
352: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 | ................
368: 00 00 00 FF FF FF FF FF - FF FF FF | ...........
[Error] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING:
opcode: 0x0355, size: 4
Unknown opcode: 0x02e9 size:8 Client:Melo
0: F7 00 00 00 40 00 00 00 | ....@...
Unknown opcode: 0x02e9 size:8 Client:Melo
0: F7 00 00 00 80 00 00 00 | ........
Unknown opcode: 0x037b size:12 Client:Melo
0: F7 00 00 00 00 00 00 00 - 00 00 00 00 | ............
Client linkdead: Melo
Dropping client: Process=false, ip=192.168.1.103, port=1768
[Status] Zone Shutdown: sebilis (89)

Found a backup from a week ago and copied those back over, BSOD gone. Just a heads up since I figure you're in between updates right now anyway.

scaerick
10-31-2004, 04:59 AM
yar, I'm getting that too. Got it after I recompiled from CVS last night. I'm going to go look in a bit.

Edgar1898
10-31-2004, 11:48 AM
I'm pretty sure I know whats causing it, I'll upload a fix to cvs within the next few hours.

scaerick
10-31-2004, 02:39 PM
Turns out the problem was my inability to read simple english. I missed sourcing the LDoN sql. I'm fine now!

Thanks :)

Elkay
10-31-2004, 05:49 PM
I'm sourced up to current with SQLs and still experiencing the problem. I'm pretty sure all of CVS is up to date at this point as well, as I saw your update propogate hours ago. Still experiencing the problem. I'm one to run a pretty customized database, so if it's a problem you think might be data related please let me know what you think you're fixing when it comes to that because I can verify whether my data corresponds to a code fix you make. My problem fix is "almost there" though, as I do get zoned in, but freeze almost exactly 1 second after I get into the zone and see mobs. Console from Zone.exe is as follows:

[Status] 476391 New client from ip:192.168.1.103 port:2114
Read group ID for 'Muug': 0
[Error] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING:
opcode: 0x0355, size: 4
[Error] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING:
opcode: 0x02e9, size: 8
[Error] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING:
opcode: 0x037b, size: 12
Client linkdead: Muug
Dropping client: Process=false, ip=192.168.1.103, port=2114
[Status] Zone Shutdown: pofire (217)

I've tried this in multiple zones, some with pathing, some without, same issue. Let me know if I can provide you with any additional info. Thanks as always.

Elkay
11-01-2004, 06:10 AM
Somewhat odd, neither my live nor my eqemu copies of EQ have been creating dbg.txt files. Is there some option in the INI possibly that is disabling creation of that file? Never noticed it wasn't being used anymore until now.

Edgar1898
11-01-2004, 06:47 AM
could you email me your client's dbg.txt file? LethalEncounter@eqemulator.net

Derision
11-01-2004, 07:50 AM
Somewhat odd, neither my live nor my eqemu copies of EQ have been creating dbg.txt files. Is there some option in the INI possibly that is disabling creation of that file? Never noticed it wasn't being used anymore until now.

They moved it from the main EQ client directory into the logs subdirectory at some point, e.g. c:\everquest\logs\dbg.txt

Edgar1898
11-01-2004, 08:38 AM
one thing I did notice is that if you dont have any items the client doesnt send those unknowns. Try to change your characters id in the character_ table. (That will cause it to not send items assuming that the id that you change it to isnt in the inventory table.) Let me know if you still have the problem.

Elkay
11-01-2004, 12:06 PM
Ok found the debug file, unfortunately it's from when I reverted back and ran successfully in game. Now I have no compile of the latest from CVS because what's on CVS right now has errors and won't compile. Next time CVS gets a clean update I'll try this out for you and send you the dbg.txt file too.

hypershadow66
11-01-2004, 02:18 PM
i have been having this problem with my server since i started and no new compile has been working

If we got a 6.0DR1 compile from like a week ago, will the black screen problem go away? and also, if its from a week ago, do we have to get rid of the whole LDON table as well since it was added just a few days ago?

Elkay
11-01-2004, 02:53 PM
I didn't have to revert any SQL to get back to a working version.

hypershadow66
11-01-2004, 05:00 PM
Did you have the adventure table already added?

Elkay
11-01-2004, 05:01 PM
Yep. Additional tables should not matter. You can have a table named poopie_poop_poop with column turd(float) and the program would still run fine.

hypershadow66
11-01-2004, 05:13 PM
ok i am gunna try to revert a while back and hope the black screen goes away

sotonin
11-01-2004, 06:40 PM
You can have a table named poopie_poop_poop with column turd(float) and the program would still run fine.

Shit! you have that table too! omg i thought i was the only one :(

hypershadow66
11-02-2004, 12:54 PM
lol. Hey when they fixed the black screen, was the problem in Zone.exe or World.exe? because i cant get zone compiled since the new quest system but world compiles fine.

Elkay
11-02-2004, 08:18 PM
The BSOD is "fixed" as of the latest pre-compiled release. I've tested it with multiple characters in multiple zones. I quote "fixed" for a couple reasons, but foremost because of a question of compilers over an actual problem with the code. I've never worked with Eqemu off of VC 6. I started working off my own compiles of the emu only after I installed VS .NET 2K2 when our company adopted this suite as our standard. Since then I have used VS 2K2 as the compiler, until a couple days ago when our company upgraded to 2K3 as our compiler. This same night was the night I started having ASCII beep issues, tho I had the CVS compile bug issues for the past couple days, possibly completely unrelated. I'm not sure where the problem lies for sure at this point, and it may take a day or two to figure it out for sure, but at this point I see it as one of two places, either SF/CVS or the difference in VC6/VS2K2/VS2K3 compilers. All I know is that as of the moment, I have a current working server, and that makes me very happy. Compileable sources are just the icing on the cake. WTG and big thumbs up to all of the EQEmu dev team for all the recent improvements.

EDIT:

As of tonight, 6PM 11/3, the current CVS was able to be downloaded, compiled with VS 2003 without errors, and the emulator runs perfectly with no login problems or crashes. WTG guys! =)