1 / 20

CrashDump

CrashDump. Agenda. Problem Unexplainable field phenomena New Developments in Crashdump Solution How to get to ‘The Why’? Opportunity New work and timelines. Unexplainable Field P henomena. All of these devices worked normally after reboot.

mya
Download Presentation

CrashDump

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CrashDump Microsoft Corporation

  2. Agenda • Problem • Unexplainable field phenomena • New Developments • in Crashdump • Solution • How to get to ‘The Why’? • Opportunity • New work and timelines Microsoft Corporation

  3. Unexplainable Field Phenomena • All of these devices worked normally after reboot. • No defects were found by file system scan. Microsoft Corporation

  4. Unexplainable Field Phenomena • Microsoft has been tracking these for years • Things aren’t getting better • Customers expect a solution from us • We have nothing to give them • There are 2 theories • The device has a flaw • The device has been mishandled Microsoft Corporation

  5. Theory #1: The device has a flaw • Goal: Address the flaw. • Assumption: • ATA devices are sophisticated enough to perform their own internal ‘crashdump’. • Microsoft is not able to address these issues along. • Digression: Microsoft attempt to do this with the millions of crash reports it receives every day • In general, user mode crashes are available to partners from http://winqual.microsoft.com through different portals. • Partners with kernel mode drivers can download ~50 randomly selected CABs for a given bucket through the WER portal • Partners only receive external mini dumps. Full dumps and internal crashes may only be given out by selected groups. • Kernel mode crashes typically are driver issues that cause Blue Screens of Death or reset the machine. Analysis of data has found that device failure is a significant source of perceived “driver issues”. • Goal: Address the flaw. • Assumption: • ATA devices are sophisticated enough to perform their own internal ‘crashdump’. • Microsoft is not able to address these issues along. Microsoft Corporation

  6. Agenda • Problem • Unexplainable field phenomena • New Developments • in CrashDump • Solution • How to get to ‘The Why’? • Opportunity • New work and timelines Microsoft Corporation

  7. Windows devices customer experience data flow Cloud Services (OCA,SQM, RAC) Improved reliability of Windows storage experience End user IHV MS info Vendor info

  8. Response Example

  9. OCA process and workflow • Crash occurs on the client • WER client collect crash data • Microsoft shares data with software developers • Software developers troubleshoot • Software developers respond to Microsoft and Customer

  10. +Devices OCA’s Expanding Focus • +Drivers • +ISVs • MSFT Microsoft Corporation

  11. Theory #2: The device has been mishandled • Goal: Enable proper device handling. • Assumptions: • Device has background scan information about internal issues, error handling, and results attempted corrections. • This background scan information would be useful to manufacturers if there was a method for delivering it from active deployed systems. • Background scanning can result in actionable requests from devices, improving robustness, and raising handling issues to the users attention. Microsoft Corporation

  12. Agenda • Problem • Unexplainable field phenomena • New Developments • in Crashdump • Solution • How to get to ‘The Why’? • Opportunity • New work and timelines Microsoft Corporation

  13. How to get to ‘The Why’ • How to transport? • Time limited • Size negotiation • Security • When to transport? • Host triggers • Device triggers • Dump persistence and recycling • What to transport? • Bucketization • Device CrashDump (flavors?) • Background scan info • Does DSM affect collection content? • How big are we willing to let this feature become? Microsoft Corporation

  14. Background Scan Coordination Components • Idle time notification • Power event notification • Background Scan vs. Power policy precedence • Host/Device Event synchronization (TimeStamped) Microsoft Corporation

  15. Background Scan Coordination Considerations Microsoft Corporation

  16. Background Scan Coordination Considerations Microsoft Corporation

  17. Background Scan Coordination Considerations Microsoft Corporation

  18. Background Scan Coordination Considerations Microsoft Corporation

  19. Agenda • Problem • Unexplainable field phenomena • New Developments • in Crashdump • Solution • How to get to ‘The Why’? • Opportunity • New work and timelines Microsoft Corporation

  20. New work and Timelines • Call for feedback, now. • Proposal for T13 in June • Approval in August Microsoft Corporation

More Related