Defrag Tools (HD) - Channel 9

Defrag Tools (HD) - Channel 9
By Microsoft
About this podcast
Defrag Tools with Andrew Richards, Chad Beeder and Larry Larsen
Latest episodes
Nov. 27, 2017
In this episode of Defrag Tools, Chad Beeder and Andrew Richards talk about what tech you could buy on Cyber Monday.We talk about USB Sticks, USB Cables, MicroSD Readers, International Power Adapters, Charging Stations, UPS Backup, Network Testers, Memory Sticks, Disk Drives, Drive adapters, Xbox Live, Xbox Game Pass, ... and many more things.For Intel Product Specs (to determine supported RAM, etc.), refer to http://ark.intel.com(Apologies for Andrew's poor voice)
Oct. 30, 2017
In this episode of Defrag Tools, Chad Beeder and Andrew Richards talk to Marc Goodner and Reid Borsuk about the maker community at Microsoft, and the cool Ninjacat statue they built. Make sure to watch to the end to see all of its, shall we say... special features! 
Oct. 23, 2017
In this episode of Defrag Tools, Andrew Richards is joined by JCAB (Juan Carlos Arevalo Baeza) and Jordi Mola from the Windows Debugger team to demonstrate some more advanced usage of a new feature of WinDbg Preview: Time Travel Debugging (TTD).Related Links:WinDbg Preview (download from Microsoft Store)Time Travel Debugging Overview (Online documentation)Debugging Tools for Windows BlogTime Travel Debugging FAQTimeline:[00:00] Introductions[01:07] Seeing a memory corruption crash in the Chakra Core when running a script. Difficult to debug![05:33] Now reproduce the same crash while recording a Time Travel Debugging trace[07:06] Looking at the TTD trace with unoptimized code[07:55] Use the !events command to list interesting events and exceptions in the trace and jump to them[11:43] Found the corrupt memory, step backwards to figure out where it came from.[13:15] Identifying the memory location containing a bad value with dx command, and setting a data breakpoint (with ba) to see who previously wrote to it.[17:37] Getting closer. Keep following the trail backwards...[19:29] Found where the bad value came from![21:08] Another use case: Find where a value is bad and track it back from there with a binary search (use !tt with a percentage value to jump to locations in the trace)[22:09] Second demo: Looking at the same crash but with optimized production code.[25:09] Exceptions will be hit when running the trace either forward or backward.[26:54] To give feedback on WinDbg Preview, use the Feedback Hub. 
Sept. 25, 2017
In this episode of Defrag Tools, Chad Beeder is joined by James Pinkerton and Ivette Carreras to introduce a new feature of WinDbg Preview: Time Travel Debugging (TTD).Related Links:WinDbg Preview (download from Microsoft Store)Time Travel Debugging Overview (Online documentation)Debugging Tools for Windows BlogTime Travel Debugging FAQTimeline:[00:00] Introductions[00:54] Introducing Time Travel Debugging (TTD)[05:06] Tracing[07:33] Debugging Forwards[09:23] Debugging Backwards![13:31] Data is available[17:20] Great for Customer Support[19:11] Email us at [email protected]
Sept. 18, 2017
In this episode of Defrag Tools, we continue our series on the new WinDbg Preview. Andrew Richards is joined by Bill Messmer to talk about the updated scripting engine.Related Links:WinDbg Preview (download from Microsoft Store)Documentation for WinDbg Preview (Dev Center)Announcement blog postRelated Episodes:Defrag Tools #138 - Debugging - 'dx' Command Part 1Defrag Tools #139 - Debugging - 'dx' Command Part 2Defrag Tools #169 - Debugging Tools For Windows TeamDefrag Tools #170 - Debugger - JavaScript ScriptingDefrag Tools #182 - WinDbg Preview Part 1Defrag Tools #183 - WinDbg Preview Part 2 
Aug. 28, 2017
In this episode of Defrag Tools, Chad Beeder is joined by Tim Misiak and Andy Luhrs to introduce WinDbg Preview, a new version of the WinDbg tool.Also see our followup episode: Defrag Tools #183 - WinDbg Preview Part 2Related Links:WinDbg Preview (download from Microsoft Store)Documentation for WinDbg Preview (Dev Center)Announcement blog postTimeline:[00:00] Welcome and introductions[00:32] All new shell, and it's available as a Store app[01:17] Yes, all your old debugging commands and extensions still work[02:06] New features enabled by the debugger data model (for more on this topic, see Defrag Tools Episode #138 and Episode #139)[03:24] Use the Feedback Hub to help us make it better[04:17] All new UI. (Ribbon, relaunch recent sessions, new windowing system, dark theme)[07:05] Watch window, locals window, etc., can all use the new debugger data model[08:13] New script window - makes it easy to write NatVis and JavaScript visualizations[08:50] WinDbg Preview is a work in progress! Expect frequent updates.
Aug. 28, 2017
In this episode of Defrag Tools, Chad Beeder is joined by Nickolay Ratchev and Tim Misiak to show off some features of WinDbg Preview, a new version of the WinDbg tool. Also see our previous episode, if you missed it: Defrag Tools #182 - WinDbg Preview Part 1 Related Links: WinDbg Preview (download from Microsoft Store)Documentation for WinDbg Preview (Dev Center)Announcement blog post Timeline: [00:00] Welcome and introductions[00:42] Recent targets - every debugging session is saved for easy access next time[01:44] New features of the locals window and watch window: Use LINQ expressions[03:22] Model window allows different views (i.e. grid)[04:05] Demo: Use a NatVis script to modify how data is shown in the Model window. JavaScript supported as well.[06:00] New interactions between windows, new features in Command window... better copy & paste[08:15] Right-click to search on MSDN[08:58] Use the Feedback Hub for bug reports and feature requests!
June 26, 2017
In this episode of Defrag Tools, Chad Beeder and Andrew Richards are joined by Paresh Maisuria from the Windows Kernel Power team and Zach Holmes from the Fundamentals team to talk about System Power Report, a new feature in Windows 10 Creators Update. Related links:Defrag Tools #168 - Powercfg Sleep Study (older version of this tool)Defrag Tools #157 - Energy Estimation Engine (E3) (the framework used for estimating power usage) Timeline: [00:00] Welcome and introductions[00:30] This is an updated and expanded version of a feature previously called Sleep Study. Now it covers everything related to power, not just details of modern standby states.[02:55] You can still run it with powercfg /sleepstudy (for backwards compatibility) - but the new command is powercfg /systempowerreport, or powercfg /spr[04:08] Opening up the generated report - lots more data than in the old Sleep Study report.[05:32] Looking an active session: How much battery power was used, and by what? What was the screen brightness? Which apps used the most power?[09:40] Why some power usage gets attributed to "Unknown"[15:00] Unlike the old Sleep Study report, the System Power Report even gives useful info on traditional standby (S3) systems.[16:40] Looking at a standby session: You can tell why a system went into standby, and why it woke up. Also lots of other stats, like how long it took to hibernate, etc.[20:27] The report also contains an "expert tab" which contains data about the battery design capacity, current capacity, and health[23:18] Bugchecks are also logged in the report (including the parameters).[24:35] Still has all the details on a modern standby system (like in the old Sleep Study report). But enhanced. Now we have better instrumentation to track why a system got woken from standby.[27:58] Of interest to OEMs and hardware engineers: We track power usage data for the SoC (System on a Chip) subsystems. Can give you the first indication of where to look further if
June 19, 2017
In this episode of Defrag Tools, Graham McIntyre joins Andrew Richards and Chad Beeder to talk about the new Active Memory Dump type. This new kernel dump size replaces the Complete Memory Dump type, and although much smaller, is equally as useful. 
June 12, 2017
In this episode of Defrag Tools, Andrew Richards and Chad Beeder walk through the process of manually creating a full memory dump via the keyboard. This is useful when you want to capture the state of the operating system. For example, to debug a hang. Resources: Forcing a System Crash from the Keyboard Registry files (.reg) demonstrated in this episode are on the Defrag Tools OneDrive share (ManualCrashRegistrySettings.zip) PCI Express Dump Switch Card (if you need to use the NMI method) Timeline: [00:00] Welcome and Intro[00:57] When would you need to manually force a crash dump?[02:42] Typically you'll want to get a Complete Memory Dump[05:57] ...which also requires you to set a large enough page file on the C: drive (RAM size plus some additional)[08:00] Setting up manual crash dump via CrashOnCtrlScroll (if your keyboard has a ScrollLock key)[13:20] Discussion of keyboards and keyboard scan codes. The old Peter Norton "pink shirt" book still comes through for this![16:55] Once you know the scan code, you can use the Dump1Keys and Dump2Key registry settings to choose your own keyboard combo. Make sure not to use CrashOnCtrlScroll at the same time![25:04] The big guns: If a system is hung badly enough that keyboard crash doesn't work, you can try CrashOnNMI. Usually requires special hardware like a PCIe NMI card.[28:34] Looking at the memory dump we just created. Bugcheck 0xE2: MANUALLY_INITIATED_CRASH