Skip to main content

Weird Sleep/Wakeup problems in Windows 10 preview laptop

My Lenovo X1 Carbon laptop experienced some weird problems earlier in the Windows 10 preview cycle; it would crash after a couple of sleep/wakeup cycles, and reboot afterwards. I was surprised that I was the only one experiencing that problem internally, especially since all the preview flighting was going smoothly. But when the problem persisted after a couple of internal upgrades, I decided to dig deeper and figure out what was going on.


When Windows crashes, it writes a memory dump to the C:\Windows\memory.dmp file, and you can examine the contents of that file, and figure out reasons for the crash through windows kernel debugger (Windbg). Windbg is available for download either separately or as part of the WDK. Once it is downloaded, the process is easy. First run Windbg with elevated permissions (Run as Administrator), and open the memory dump file (CTRL+D). If the debugger complains about the symbols, try to fix them and reload through:
.symfix; .reload


You can then look for what caused the crash. In my case, it was a problem with ndis.sys where the network driving was timing out and causing Windows to crash. I am not sure how the network driver got corrupted during my flighting upgrades, but uninstalling the driver (Winkey+X, run device manager, find the adapter, and uninstall) and reinstalling it solved the problem from that time onward.

Comments

Post a Comment

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...
2 comments
Read more

A paper a day keeps the dr away: Dapper a Large-Scale Distributed Systems Tracing Infrastructure

Modern Internet scale applications are a challenge to monitor and diagnose. The applications are usually comprised of complex distributed systems that are built by multiple teams, sometimes using different languages and technologies. When one component fails or misbehaves, it becomes a nightmare to figure out what went wrong and where. Monitoring and tracing systems aim to make that problem a bit more tractable, and Dapper, a system by Google for large scale distributed systems tracing is one such system. The paper starts by setting the context for Dapper through the use of a real service: "universal search". In universal search, the user types in a query that gets federated to multiple search backends such as web search, image search, local search, video search, news search, as well as advertising systems to display ads. The results are then combined and presented back to the user. Thousands of machines could be involved in returning that result, and any poor p...
Post a Comment
Read more

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...
Post a Comment
Read more