Artwork

Content provided by Defrag Tools - Channel 9. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Defrag Tools - Channel 9 or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Defrag Tools #179 - Manually Generating a Crash Dump

32:25
 
Share
 

Archived series ("Inactive feed" status)

When? This feed was archived on March 09, 2022 00:03 (2y ago). Last successful fetch was on March 11, 2020 12:16 (4y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 180976324 series 116952
Content provided by Defrag Tools - Channel 9. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Defrag Tools - Channel 9 or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

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)

PCIe NMI card

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!
Keyboard Scan Codes
[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

  continue reading

26 episodes

Artwork
iconShare
 

Archived series ("Inactive feed" status)

When? This feed was archived on March 09, 2022 00:03 (2y ago). Last successful fetch was on March 11, 2020 12:16 (4y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 180976324 series 116952
Content provided by Defrag Tools - Channel 9. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Defrag Tools - Channel 9 or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

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)

PCIe NMI card

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!
Keyboard Scan Codes
[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

  continue reading

26 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide