Solved Fresh Build - Constant BSOD - Multiple Codes - 3b, 50, a

[LP81]

I ran the ProcMon first since it was the easiest to pull down and run.

It compressed rediculouly small from 61MB to 5MB so I was able to attach it

I started to download Windows6.1-KB947821-v22-x64.msu from microsoft.com - 341MB file.

Hit record

download stalled after about 4-5 seconds. I paused it. Waited 10 seconds or so. Resumed the download. it stalled after another 5 seconds. Stopped recording and exported the save file which is attached.

I can capture a 2nd file loading up Diablo III as well if you like for a 2nd set of data.

 

[Vir Gnarus]

I don't believe what I'm seeing correlates with what you mentioned. I'm witnessing some network activity from FF for about 1 second at start of logging, then absolutely no network activity for 20 seconds, followed by network activity for 14 seconds, then no activity for the rest of the log. Observe the attached graph.

 

[LP81]

Let me kill the desktop widgets that are running for a clearer picture to eliminate traffic outside of FF. I will try to more accurately time things on my end to correspond. 4-5 seconds were estimates previously.

 

[Vir Gnarus]

You don't really need to get exact timing down, I just need estimates on how many hills and valleys I should expect to see. You seemed to infer that there should be two hills, but I only witness 1 in the middle.

 

[LP81]

OK, attached is a second log file - I turned off LogMeIn, as well as all my widgets to clear some background noise (maybe)

Capture starts with the same file being downloaded as before.

I let it run for 30 seconds without touching it, and it seemed to stall out around 10 or so seconds.

Paused the download for 10 seconds I think.

Resumed the download and let it sit for another 30 seconds. It stalled out at the 14-16 second mark.

Please let me know if you'd like a different test run for more info.

 

[Vir Gnarus]

Something isn't jiving here, this log shows no activity from FF at all, and not just that, but hardly any from any process, with the most being 46KB (96KB total).

I'm not understanding why this isn't working, but it sounds as if we'll need to resort to Xperf.

 

[LP81]

I installed xperf back when we discussed it before.

to verify, I will need to tweak past the quick set up oft "xperf -on DiagEasy" in the CMD run as administrator?

Correct?

 

[Vir Gnarus]

You'll want to set it up and run it as instructed here. Remember that you don't need to do the heap profiling.

 

[LP81]

Did the following:

Manually modified registry to value of "1" (cmd line didn't seem to modify it)
Restarted
Ran CMD as admin
Strarted moitoring with "xperf -on latency -stackwalk profile"
Started download of file
Ran for about 5-6 seconds pulling down 17.8 MB then stalled. I waited 15-20 seconds then clicked pause
Paused download for 10 seconds
Resumed Download
Pulled down 6 MB of data and stalled after 3-4 seconds
Waited another 20 seonds or so.
Paused Download for 10 seconds
Resumed download
Initially downloaded 16.9 MB more over 10 seconds or so, stalled for a moment, continues to download another 25.6 MB over 30 seconds or so. Stalled out.
Paused Download

Stopped xperf with "xperf -d out.etl"

Opened the output file with "xperfview out.etl"

Did a save as to save to desktop with personalized naming convention

Uploaded here: Zippyshare.com

 

[LP81]

double post removed

 

[Vir Gnarus]

urgh, ok, I apologize, but the Latency kernel group they recommend is very limited. I'm not sure why the Mozilla dev article suggests it because it hardly even records anything involved with networking. I'm afraid I'll have to ask you to record once more. This time, instead of "latency" in the command line make it "latency+networktrace". Also, if somehow you can get "latency+networktrace+drivers" to work then that'd be super duper awesome, but it may BSOD your system. If it doesn't work somehow just use the first option.

Also, just to ask, what happens if you decide not to pause the download? Does it stall indefinitely? If you can get it to just recover on its own without pausing that would be preferable.

I apologize for asking you over and over on these logs. I haven't had the opportunity to use xperf much (which really should change) so I haven't yet solidified all of its options in my head yet.

 

[Vir Gnarus]

Oh,oh,oh! And add "Filename" too while you're at it since we're dealing with file I/O. So the most optimal log is "latency+networktrace+drivers+filename". Again, if the "drivers" option messes things up then remove it and leave the rest. Thanks a mil.

 

[LP81]

No, thank YOU for all your help so far... I will try running it with latency+networktrace+drivers+filename and letting the file just hang indefinatly just to see if it makes any difference.

I'll report back in a bit (working from home today so I am between 2 computers)

 

[Vir Gnarus]

Well I'm just wondering if it DOES hang indefinitely unless you intervene. Does it?

 

[LP81]

Ran it again, using xperf -on latency+networktrace+drivers+filename -stackwalk profile

Started the download. It didn't initially start coming down so I cancelled it.

Picked "retry download"

It started to pull down, and stalled after 5 seconds.

I let it hang for 2-3 minutes with no change at all.

paused/resumed really quickly then killed the profiling.

new report uploaded: Zippyshare.com


Per your other reply, I tested letting it hang on it's own. When I hit the 5 minutes mark of hanging I decided to verify it's not the specific file.

While the first one hangs I started pulling down another file from Creative Worldwide Support got about 65K pulled down before it hung, so now both downloads are hanging indefinitely for the last 10 min

 

[LP81]

Quick update - in case you are curious - 1 hour later, same files still hanging. I am going to cancel them since I figure after an hour, it's pretty definitive.

 

[Vir Gnarus]

So it sounds like TCP streams aren't sustaining, as opposed to something just coming in and halting all the bandwidth. Two completely different scenarios. That'll definitely help with my diagnosis of this.

I noticed you said you let it run for about 2-3 minutes before stopping the profiling, though I see it going as far as 360 seconds (6 minutes). Can you clarify?

Anyways, this looks like a good bit of data to chew on. In the meantime while I peruse it, if you wish to continue providing more info, I would highly recommend a Wireshark log. Just log a moment of a download attempt (just one) and when it halts wait a couple seconds then stop it and then Save As and send on yonder.

Also, one question I haven't asked that I'm not sure has been answered: If you try Safe Mode with Networking, does the same problem arise? Thanks.

 

[LP81]

Now I am confusing myself, because I remember that the one file showed 6 Minutes of activity but my description doesn't match... I gues it was more like 5-6 minutes of letting it stall. I apologize for the confusion. So many tests, I should keep a stop watch around and write things down as they happen.

I cannot remember if I have tried safe mode + networking yet. With all of the hullabaloo around the original BSOD issues I never got a stable platform until now to really think about booting into safe mode again. I will test this tonight when I get home from work. (can't specify safe mode + networking via logmein remote boot.)

I will download and run wireshark remotely (hopefully) and report back after I have done so

 

[LP81]

Started Wireshark
Started download
Stalled after 2-3 seconds at most.

Let it keep running, it actually restarted itself downloading after a 20 second (estimate) or so stagnation period then stalled out at around 45 seconds +/-

Let it stay stalled til the end of the log file at 116 seconds then I stopped recording.

File ended up over 20 MB after zipping so it's hosted again: Zippyshare.com


Have not been able to confirm nor deny safemode + networking.

I booted into it once and the one file momentarily stuttered but then downloaded fine. But, I was antsy and wanted to run Wireshark and robooted right away. I will test again tomorrow morning

 

[LP81]

Just for S&Gs, I ran Wireshark and booted up Diablo III.

Ran nice for the first few seconds at a 200 ms ping then game totally lagged out and showed a 1900+ ping and stopped moving, had to task manager force quit it then saved out the file.

Despite being 110 Seconds, almost the same as the download, the file is tiny so it is attached here rather than hosted