Constant Disconnections and Latency Spikes
|
Ever since patch 1.0.3, I've been experiencing constant "unexpected disconnection has occurred" messages, sending me back to the log in screen. I also experience frequent latency spikes, which causes the in-game action to freeze up. When the action resumes, I usually find my Character dead. (A reason I only play in Standard League these days).
Because I have a Sound Blaster X-Fi series sound card, I use the "-swa" switch in my PoE command line. My system information is included below, with some connection information. And while I'm thinking of it, my 4 CPU cores are running at a temperature of 43 to 45 degrees, Celsius. My GPU is running at 38 degrees, Celsius. (If that matters). I have contacted my ISP three times. Each time, they sent a technician out to my house to check the equipment and the signal. They have found no problems so far. I have a cable connection and own my telephony cable modem (to avoid rental fees). Note: The WinMTR and PingPlotter results were taken on one of my better days. The SpeedTest and PingTest results are typical with my connection. WinMTR Trace Route Results:
Скрытый текст
 PingPlotter Trace Route Results:
Скрытый текст
 SpeedTest.net and PingTest.net Connection Results:
Скрытый текст
  I could not include the entire DirectX information, as it exceeds the 50,000 character post limit. I've tried to include the important information. (Let me know if you need more). I run PoE at a resolution of 1280 x 720. And, before anyone asks, I have all the latest device drivers installed. System Information from dxdiag.exe:
Скрытый текст
------------------
System Information ------------------ Time of this report: 12/23/2013, 13:46:42 Machine name: (removed for security) Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532) Language: English (Regional Setting: English) System Manufacturer: Dell Inc. System Model: Dell XPS420 BIOS: Phoenix ROM BIOS PLUS Version 1.10 A07 Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz Memory: 8192MB RAM Available OS Memory: 8126MB RAM Page File: 2970MB used, 13279MB available Windows Dir: C:\Windows DirectX Version: DirectX 11 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled DxDiag Version: 6.01.7601.17514 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer. Sound Tab 2: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: NVIDIA GeForce GT 640 Manufacturer: NVIDIA Chip type: GeForce GT 640 DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_0FC1&SUBSYS_26493842&REV_A1 Display Memory: 3738 MB Dedicated Memory: 4027 MB Shared Memory: 3806 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: ViewSonic VA2248 SERIES Monitor Model: VA2248 SERIES Monitor Id: VSC0E28 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: DVI Monitor Name: Dell SX2210T(Digital) Monitor Model: DELL SX2210 Monitor Id: DELA047 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: DVI Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um Driver File Version: 9.18.0013.3182 (English) Driver Version: 9.18.13.3182 DDI Version: 11 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 11/14/2013 06:55:24, 18208624 bytes WHQL Logo'd: Yes WHQL Date Stamp: Device Identifier: {D7B71E3E-4C81-11CF-9C57-44061CC2C435} Vendor ID: 0x10DE Device ID: 0x0FC1 SubSys ID: 0x26493842 Revision ID: 0x00A1 Driver Strong Name: oem179.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section090:9.18.13.3182:pci\ven_10de&dev_0fc1 Rank Of Driver: 00E02001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled Read My Links!: http://www.theamazonbasin.com/forums/index.php?/topic/121389-read-my-links/ Последняя редакция: Perusoe. Время: 23 дек. 2013 г., 16:42:22
| |
|
Were the WinMTR and/or PingPlotter traces capturing when you were experiencing the issues? I want to ensure that your lag and disconnects were captured in the trace. A trace without a capture isn't very useful because it doesn't show the network state at the time of the problem. Only before or after... when there might not be a problem.
| |
" I ran the WinMTR and PingPlotter trace routes according to the instructions in this thread: How to: WinMTR / trace route How to use PingPlotter It does not state to run the trace while the game is running. (If that is what you mean). I used "US.login.pathofexile.com" for the Host in WinMTR, since I log in through the America Gateway and "www.pathofexile.com" for the Host in PingPlotter (as per the instructions). After I posted the OP, I went in-game and spent about an hour trying to get from the Imperial Gardens Waypoint to the Waypoint in the Sceptre of God on Merciless Difficulty, which I haven't tagged yet. I was constantly getting killed from latency spikes. At least, this left my Town Portal up, so I could get back to the Sceptre of God. But, whenever I was disconnected and had to log back in, my TP would be gone and I'd have to fight my way through or run past hordes of monsters to get back to the entrance of the Sceptre of God. I finally got frustrated and quit my game session. (I still haven't tagged the Sceptre of God Waypoint. And I'm not looking forward to going back in until the connection issues have been resolved). Read My Links!: http://www.theamazonbasin.com/forums/index.php?/topic/121389-read-my-links/
| |
|
although the thread doesn't state you should run it while experiencing the issues, that is usually the best way to locate a problem.
WinMTR captures the network conditions over time. If you just have a crappy connection in general, then the trace might be lucky and capture it while it is in the crappy state. If you have a mostly stable connection but sometimes experience issues, then capturing DURING the issues gives us the best chance to locate the problem. Think of it like taking an "accident" or "crime scene" photo after it's already been cleared. Doesn't do much good right? We need to capture the scene at the time the problem happens so we have the best evidence to detect the problem. Последняя редакция: Drakier. Время: 23 дек. 2013 г., 16:51:48
| |
|
Okay. Thanks. I'm not sure I should run WinMTR and PingPlotter at the same time. This is what I'll do. I'll run WinMTR and play the game until I experience the issue. Then I'll run PingPlotter and start another game session until I, again, experience the issue. I'll post the results as soon as I have them.
Read My Links!: http://www.theamazonbasin.com/forums/index.php?/topic/121389-read-my-links/
| |
|
You don't necessarily need to run PingPlotter and WinMTR at the same time.
The only reason to use PingPlotter really is to "validate" results, and in cases where WinMTR packets are blocked/filtered and prevent the WinMTR from properly resolving. | |
|
Okay. I spent about 30 minutes in-game. (15 minutes running WinMTR and 15 minutes running PingPlotter). I didn't experience any disconnections this time, but I had plenty of latency spikes. (Very frustrating!)
Here are the results. WinMTR Trace Routes with PoE running:
Скрытый текст
 PingPlotter Trace Routes with PoE running:
Скрытый текст
 See the OP for system information. Read My Links!: http://www.theamazonbasin.com/forums/index.php?/topic/121389-read-my-links/
| |
|
Looks like you've got something going on with your home network. Something is causing 4 second ping spikes, and it's not the PoE servers... it's showing on your first hop. That is the network between your PC and your Router/Modem.
I'm not sure if it is a hardware or software issue, but something is causing those spikes... and it's not your ISP or the GGG servers. If you're using wireless, try hard-wired. Double check your cabling if you're wired, and perhaps try rebooting your PC and Router/Modem. Also check if anyone else is using the network (maybe unplug them) and see if they are utilizing a lot of bandwidth. Hopefully you can figure out where the issue is, but it appears within your own network somewhere. Good luck. | |
|
Thank you for your help.
I only have the one computer. My connection is wired (not wireless). I run an Ethernet cable directly from my computer's internal Ethernet card to my telephony modem, which is about 6 months old. The Comcast technician ran their coaxial cable directly from their service (the wall plug) to my telephony modem. In the last 2 days, I've tried Comcast's instructions to reset my modem 3 times. This involved unplugging all cables, including the power cord, from the modem and waiting at least 30 seconds. After plugging the cables back in, I pressed and held the reset button on the back of the modem for a minimum of 10 seconds. Then, I let the modem reboot. If what you say is correct, then the problem would be my Ethernet card, telephony modem or the software drivers. Would you, by any chance, have any suggestions on an easy, inexpensive way to test these components? (Comcast technicians couldn't find anything wrong). Read My Links!: http://www.theamazonbasin.com/forums/index.php?/topic/121389-read-my-links/
| |
|
It doesn't have to be hardware causing your problem either. Could be software on the PC filtering packets, taking too much time, etc.. firewall or AV are common causes.
|
