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

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.

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.

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.

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.

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.

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.

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?

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

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