Skip to content

Instantly share code, notes, and snippets.

@m1el

m1el/ru.md

Forked from Izumi-kun/ru.md
Last active August 29, 2015 14:16
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save m1el/a56e2f1dee16ebf2eee8 to your computer and use it in GitHub Desktop.
Save m1el/a56e2f1dee16ebf2eee8 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
ru.md

Description

The first BSOD (0x00000139) occured this year January 2 and never happened before.

After core dump analysis I came to conclusion that this error happens because because of a network adapter.

January 4 after a BSOD during the night I tried to manually reproduce this error.

Experimentally, I found out the moment the error occurs - Computer maintenance Screnshot 3.

Error dates can be found on Screenshot 1.

After reinstalling the Hyper-V network adapter (2015-01-04T15:18:48 as seen on Screenshot 2), the error during computer maintenance has stopped to occur.

The next error (February 4) happened roughly after a month (date diff) during automatic system maintenance.

As seen on screenshots, the network adapter I removed after the error occured, has been installed after 2 days. This error had happened today, after a month (date diff).

As you can see on Screenshot 2, the first configuration of this network adapter was on December 2 2014 (one month before the first BSOD (0x00000139) occured).

Files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment