%3CLINGO-SUB%20id%3D%22lingo-sub-725840%22%20slang%3D%22en-US%22%3ENew%20Mark's%20Blog%20Post%3A%20The%20Case%20of%20the%20Crashed%20Phone%20Call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-725840%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20TechNet%20on%20Jan%2006%2C%202009%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CA%20class%3D%22%22%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fmarkrussinovich%2Farchive%2F2008%2F12%2F30%2F3174871.aspx%22%20mce_href%3D%22http%3A%2F%2Fblogs.technet.com%2Fmarkrussinovich%2Farchive%2F2008%2F12%2F30%2F3174871.aspx%22%20title%3D%22Mark's%20Blog%3A%20The%20Case%20of%20the%20Crashed%20Phone%20Call%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%20Mark's%20Blog%3A%20The%20Case%20of%20the%20Crashed%20Phone%20Call%3A%20%3C%2FA%3E%20Check%20out%20Mark's%20latest%20blog%20post%20to%20see%20how%20David%20Solomon%2C%20Mark's%20coauthor%20for%20the%20Windows%20Internals%20books%2C%20resolved%20a%20blue%20screen%20problem%20most%20likely%20related%20to%20an%20outdated%20driver.%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-725840%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TechNet%20on%20Jan%2006%2C%202009%20Mark's%20Blog%3A%20The%20Case%20of%20the%20Crashed%20Phone%20Call%3A%20Check%20out%20Mark's%20latest%20blog%20post%20to%20see%20how%20David%20Solomon%2C%20Mark's%20coauthor%20for%20the%20Windows%20Internals%20books%2C%20resolved%20a%20blue%20screen%20problem%20most%20likely%20related%20to%20an%20outdated%20driver.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-725840%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edavid%20solomon%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMark%20Russinovich%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on TechNet on Jan 06, 2009
Mark's Blog: The Case of the Crashed Phone Call: Check out Mark's latest blog post to see how David Solomon, Mark's coauthor for the Windows Internals books, resolved a blue screen problem most likely related to an outdated driver.