Misadventures in BIOS updates

So I’m on a new-ish motherboard from ASUS that has an AM4 socket for my Ryzen 1700x processor. So far so good right? Well, ASUS released a new BIOS update that “Update AGESA to”. This sounded awesome, or at least a fix, as BIOS 0803 updated to and was noticeably no longer on the download page…


So I updated. What could possibly go wrong?

So, the new bios 805 appears to have an issue with mixed DRAM configurations where it marks RAM bank B as present, but Windows sees it as hardware reserved and BIOS doesn’t account for it…


So above is the problem case, note memory is 16384, even though DRAM status sees all 4 sticks and they amount to 24GB…


It’s been my experience that computers are generally good at math, at least better than I am at it…so…yeah.

I dorked around, on a whim. I reboot, force D.O.C.P. config (whatever that is). We are now good after 1 reboot for D.O.C.P. to take effect. #becausesunspots



Now, the bad part, when I do this it reboots (naturally), but then fails to post 3 times and recovers). I have to hit F1 (apparently D.O.C.P. means “OVERCLOCKME BADLY”. Since, well, it thinks my DDR4 RAM is capable of 2667 when it is capped at 2400. Whatever.

So I disable D.O.C.P., now I have my memory accounted for properly?!



Homophobic space nazis here on earth to buy remaindered furniture.

or something.

I bought some SC (Sia coin)

Here’s why I bought into Sia…spending like, $27 for 1500-ish coins.

  1. It’s a practical use-case for crypto-coin tech (imo).
  2. It has some good development skill backing it.
  3. It has some extremely favorable news (see below)
  4. Someone bothered to engineer and produce an ASIC to mass-produce SC and it comes out soon.

Here’s how:

  1. I bought BTC (bitcoin) at CoinBase using my CC.
  2. I went to shapeshift and converted the BTC to SC.


1. Sia could disrupt DropBox and Amazon,

2. valued above $.01 USD,

3. SIA takes on cloud providers with decentralized storage.

Sorry for the formatting I suck at WordPress.

Continue reading “I bought some SC (Sia coin)”

Quick and Dirty – Collect an ETW shutdown trace on Windows 7.

Let’s say you need to collect a trace of the shutdown of a Windows 7 box. Or 8, or 10. Whatever.

Maybe it takes forever, hangs up, et etc.

Jeff to the rescue;

For Windows 7, or Window 8.x, download the WADK for 8.1 update. You’re going to say, “but dude, this is for Windows 7”. The dude abides, for reasons I can’t go into, use the 8.1 update ADK please for a Windows 7 trace. Capiche?

Ok. So, Download here

That downloads adksetup.exe. Run it. It’s a web installer, we are going to opt-out of almost all of it; when you get to the below screen, make it look like so:


And then click Install. You’re going to want to know, what do all these do? Later, padwan learner, we’ll get to that sometime in the future.

For now, focus on the present. I know master Yoda says to be mindful of the future, but not at the cost of the now.

Anyway, when it is done, run WPRUI;

On Windows 7, you’ll likely be prompted to disable paging executive. Do it and reboot. This tells Kernel “YO! Keep all those stacks in RAM and don’t outpage them with yo bad self”.

Then rerun WPRUI if you had to reboot. Make the checkboxes look so;


Arrows are where you need to change something. Then hit “start” and reboot.

After you power back up, you’ll find a trace in your appdata by default.

View with WPA (Windows Performace Advisor).


Docker on Windows: MobyLinuxVM failed to realize – fixed


  1. Download Docker for Windows (edge or stable branch, doesn’t seem to matter).
  2. Boot up and Docker will fail to start with MobyLinuxVM failed to realize.DBTDIHvU0AAdvLk

The hint is the text “<No file>” in the window above, for my scenario fix anyway.

To fix:

  1. Further investigation reveals the vhd is actually not there, nor is the VM present in Hyper-V manager. Looking further, something is amiss.
  2. Right-click the Docker icon in your system tray, select Settings.2017-06-02_3-44-56
  3. Select Advanced and validate your path for “Images and volumes VHD location”.2017-06-02_3-46-59
  4. Note the path. Does it exist? For me, no. It’s an old setting from a previous installation of Hyper-V on this system. The path is invalid as I removed Hyper-V to a dedicated host and deleted the directories post migration.
  5. Uninstall Docker (rerun the installer you downloaded, select Remove).
  6. Open Hyper-V Manager. (start, type “Hyper-V” and click it) 2017-06-02_4-03-38
  7. Right click your host name in Hyper-V Manager and select “Hyper-V Settings”.
  8. Browse your “Virtual Hard Disks” and “Virtual Machines” paths and set to valid directories, Save/Ok/Apply/etc.2017-06-02_4-05-33.png
  9. Reinstall Docker from the downloaded installer. Now that the Hyper-V path for VM/disks is valid, Docker can place the MobyLinuxVM disk and create the Virtual Machine in Hyper-V and start it. yay.
  10. ???
  11. Profit


Suggestion: Pre-flight installer for Docker for Windows might want to check that the paths are valid for the creation of the vhd file/VM.

Further suggestion: When you run Hyper-V for a bit, then remove the feature from Windows. MAYBE, just maybe, Windows should remove the damn settings so when you re-enable Hyper-V it starts off fresh, instead of with stale info.

Further further suggestion: Live long and prosper.

This is the bug I filed, looks like they might fix it (should be a hyper-v fix too honestly, maybe I’ll feedback that too).


Dude out