Windows / Code / 0xc100f001

0xc100f001

Decimal: 3238064129 · Signed: -1056903167

As HRESULT:As NTSTATUS:

Associated Modules

ModuleFound inDescription
bcdedit.exe10BCDEDIT - Boot Configuration Data Store Editor The Bcdedit.exe command-line tool modifies the boot configuration data store. The boot configuration data store contains boot configuration parameters and controls how the operating system is booted. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM entries (in Extensible Firmware Interface-based operating systems). You can use Bcdedit.exe to add, delete, edit, and append entries in the boot configuration data store. For detailed command and option information, type bcdedit.exe /? . For example, to display detailed information about the /createstore command, type: bcdedit.exe /? /createstore For an alphabetical list of topics in this help file, run "bcdedit /? TOPICS". Commands that operate on a store ================================ /store Used to specify a BCD store other than the current system default. /createstore Creates a new and empty boot configuration data store. /export Exports the contents of the system store to a file. This file can be used later to restore the state of the system store. /import Restores the state of the system store using a backup file created with the /export command. /sysstore Sets the system store device (only affects EFI systems, does not persist across reboots, and is only used in cases where the system store device is ambiguous). Commands that operate on entries in a store =========================================== /copy Makes copies of entries in the store. /create Creates new entries in the store. /delete Deletes entries from the store. /mirror Creates mirror of entries in the store. Run bcdedit /? ID for information about identifiers used by these commands. Commands that operate on entry options ====================================== /deletevalue Deletes entry options from the store. /set Sets entry option values in the store. Run bcdedit /? TYPES for a list of datatypes used by these commands. Run bcdedit /? FORMATS for a list of valid data formats. Commands that control output ============================ /enum Lists entries in the store. /v Command-line option that displays entry identifiers in full, rather than using names for well-known identifiers. Use /v by itself as a command to display entry identifiers in full for the ACTIVE type. Running "bcdedit" by itself is equivalent to running "bcdedit /enum ACTIVE". Commands that control the boot manager ====================================== /bootsequence Sets the one-time boot sequence for the boot manager. /default Sets the default entry that the boot manager will use. /displayorder Sets the order in which the boot manager displays the multiboot menu. /timeout Sets the boot manager time-out value. /toolsdisplayorder Sets the order in which the boot manager displays the tools menu. Commands that control Emergency Management Services for a boot application ========================================================================== /bootems Enables or disables Emergency Management Services for a boot application. /ems Enables or disables Emergency Management Services for an operating system entry. /emssettings Sets the global Emergency Management Services parameters. Command that control debugging ============================== /bootdebug Enables or disables boot debugging for a boot application. /dbgsettings Sets the global debugger parameters. /debug Enables or disables kernel debugging for an operating system entry. /hypervisorsettings Sets the hypervisor parameters. Command that control remote event logging ========================================= /eventsettings Sets the global remote event logging parameters. /event Enables or disables remote event logging for an operating system entry.
bcdedit.exe11BCDEDIT - Boot Configuration Data Store Editor The Bcdedit.exe command-line tool modifies the boot configuration data store. The boot configuration data store contains boot configuration parameters and controls how the operating system is booted. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM entries (in Extensible Firmware Interface-based operating systems). You can use Bcdedit.exe to add, delete, edit, and append entries in the boot configuration data store. For detailed command and option information, type bcdedit.exe /? . For example, to display detailed information about the /createstore command, type: bcdedit.exe /? /createstore For an alphabetical list of topics in this help file, run "bcdedit /? TOPICS". Commands that operate on a store ================================ /store Used to specify a BCD store other than the current system default. /createstore Creates a new and empty boot configuration data store. /export Exports the contents of the system store to a file. This file can be used later to restore the state of the system store. /import Restores the state of the system store using a backup file created with the /export command. /sysstore Sets the system store device (only affects EFI systems, does not persist across reboots, and is only used in cases where the system store device is ambiguous). Commands that operate on entries in a store =========================================== /copy Makes copies of entries in the store. /create Creates new entries in the store. /delete Deletes entries from the store. /mirror Creates mirror of entries in the store. Run bcdedit /? ID for information about identifiers used by these commands. Commands that operate on entry options ====================================== /deletevalue Deletes entry options from the store. /set Sets entry option values in the store. Run bcdedit /? TYPES for a list of datatypes used by these commands. Run bcdedit /? FORMATS for a list of valid data formats. Commands that control output ============================ /enum Lists entries in the store. /v Command-line option that displays entry identifiers in full, rather than using names for well-known identifiers. Use /v by itself as a command to display entry identifiers in full for the ACTIVE type. Running "bcdedit" by itself is equivalent to running "bcdedit /enum ACTIVE". Commands that control the boot manager ====================================== /bootsequence Sets the one-time boot sequence for the boot manager. /default Sets the default entry that the boot manager will use. /displayorder Sets the order in which the boot manager displays the multiboot menu. /timeout Sets the boot manager time-out value. /toolsdisplayorder Sets the order in which the boot manager displays the tools menu. Commands that control Emergency Management Services for a boot application ========================================================================== /bootems Enables or disables Emergency Management Services for a boot application. /ems Enables or disables Emergency Management Services for an operating system entry. /emssettings Sets the global Emergency Management Services parameters. Command that control debugging ============================== /bootdebug Enables or disables boot debugging for a boot application. /dbgsettings Sets the global debugger parameters. /debug Enables or disables kernel debugging for an operating system entry. /hypervisorsettings Sets the hypervisor parameters. Command that control remote event logging ========================================= /eventsettings Sets the global remote event logging parameters. /event Enables or disables remote event logging for an operating system entry.
verifier.exe10Copyright (c) Microsoft Corporation. All rights reserved. SYNTAX: verifier {/? | /help} verifier /standard /all verifier /standard /driver [ ...] verifier {/ruleclasses | /rc} [ ...] /all verifier /flags [ ...] /all verifier /flags [ ...] /driver [ ...] verifier /rules {query | reset | default | disable } verifier /query verifier /querysettings verifier /bootmode {persistent | resetonbootfail | oneboot | resetonunusualshutdown} verifier /persistthroughupgrade verifier /reset verifier /faults [probability [pool_tags [applications [delay_minutes]]]] verifier /faultssystematic [ ...] verifier /log [/interval ] verifier /volatile /flags [ ...] verifier /volatile /adddriver [ ...] verifier /volatile /removedriver [ ...] verifier /volatile /faults [probability [pool_tags [applications [delay_minutes]]]] verifier /domain {wdm | ndis | ks | audio} [rules.all | rules.default ] /driver ... [/logging | /livedump] verifier /logging verifier /livedump PARAMETERS: /? or /help Displays this help message. /standard Specifies standard Driver Verifier flags. /all Specifies that all installed drivers will be verified after the next boot. /driver [ ...] Specifies one or more drivers (image names) that will be verified. Wildcard values (e.g. n*.sys) are not supported. /driver.exclude [ ...] Specifies one or more drivers (image names) that will be excluded from verification. This parameter is applicable only if all drivers are selected for verification. Wildcard values (e.g. n*.sys) are not supported. /flags [ ...] Specifies one or more options that should be enabled for verification. Flags are applied to all drivers being checked by Driver Verifier. The provided options values must be either in decimal, hexadecimal ("0x" prefix), octal ("0o" prefix) or binary ("0b" prefix) format. Standard Flags: Standard Driver Verifier options can be specified using '/standard'. WDF verification is included in /standard but is not shown here. 0x00000001 (bit 0) - Special pool 0x00000002 (bit 1) - Force IRQL checking 0x00000008 (bit 3) - Pool tracking 0x00000010 (bit 4) - I/O verification 0x00000020 (bit 5) - Deadlock detection 0x00000080 (bit 7) - DMA checking 0x00000100 (bit 8) - Security checks 0x00000800 (bit 11) - Miscellaneous checks 0x00020000 (bit 17) - DDI compliance checking Additional Flags: These flags are intended for specific scenario testing. Flags marked with (*) require I/O Verification (bit 4) that will be automatically enabled. Flags marked with (**) support disabling of individual rules. 0x00000004 (bit 2) - Randomized low resources simulation 0x00000200 (bit 9) - Force pending I/O requests (*) 0x00000400 (bit 10) - IRP logging (*) 0x00002000 (bit 13) - Invariant MDL checking for stack (*) 0x00004000 (bit 14) - Invariant MDL checking for driver (*) 0x00008000 (bit 15) - Power framework delay fuzzing 0x00010000 (bit 16) - Port/miniport interface checking 0x00040000 (bit 18) - Systematic low resources simulation 0x00080000 (bit 19) - DDI compliance checking (additional) 0x00200000 (bit 21) - NDIS/WIFI verification (**) 0x00800000 (bit 23) - Kernel synchronization delay fuzzing 0x01000000 (bit 24) - VM switch verification 0x02000000 (bit 25) - Code integrity checks /ruleclasses or /rc [ ... ] This parameter is larger set of '/flags' above. While '/flags' is limited to 32 bit bitmap expression, this can include more than 32 verification classes. Each positive decimal integer represents a verification class. Multiple classes can be expressed by separating each class id with space character. Following rule classes IDs are available and leading 0's can be omitted. Standard Rule Classes: 1 - Special pool 2 - Force IRQL checking 4 - Pool tracking 5 - I/O verification 6 - Deadlock detection 8 - DMA checking 9 - Security checks 12 - Miscellaneous checks 18 - DDI compliance checking 34 - WDF Verification Additional Rule Classes: These rule classes are intended for specific scenario testing. Rule classes are marked with (*) require I/O Verification (5) that will be automatically enabled. Flags marked with (**) support disabling of individual rules. 3 - Randomized low resources simulation 10 - Force pending I/O requests (*) 11 - IRP logging (*) 14 - Invariant MDL checking for stack (*) 15 - Invariant MDL checking for driver (*) 16 - Power framework delay fuzzing 17 - Port/miniport interface checking 19 - Systematic low resources simulation 20 - DDI compliance checking (additional) 22 - NDIS/WIFI verification (**) 24 - Kernel synchronization delay fuzzing 25 - VM switch verification 26 - Code integrity checks /log.code_integrity This option suppresses Code Integrity violation breaks and collects only statistics for verified drivers. Statistics could be extracted via /log option or kernel debugger. This parameter is applicable only if Code Integrity checks are enabled. /rules {query | reset | default | disable } Specifies rules level control (advanced). query Shows current status of controllable rules. reset Resets all rules to their default state. default Sets rule ID to its default state. disable Disables specified rule ID. /query Display runtime Driver Verifier statistics and settings. /querysettings Displays a summary of the options and drivers that are currently enabled, or options and drivers that will be verified after the next boot. The display does not include drivers and options added using /volatile. /bootmode Specifies the Driver Verifier boot mode. This option requires system reboot to take effect. persistent Ensures that Driver Verifier settings are persistent across reboots. This is the default value. resetonbootfail Disables Driver Verifier for subsequent reboots if the system failed to start. resetonunusualshutdown Driver Verifier persists until unusual shutdown happens. Its abbrevation, 'rous', can be used. oneboot Enables Driver Verifier only for the next boot. /persistthroughupgrade Makes the Driver Verifier settings persist through upgrade. Driver Verifier will be active during system upgrade. /reset Clears Driver Verifier flags and driver settings. This option requires system reboot to take effect.
verifier.exe11Copyright (c) Microsoft Corporation. All rights reserved. SYNTAX: verifier {/? | /help} verifier /standard /all verifier /standard /driver [ ...] verifier {/ruleclasses | /rc} [ ...] /all verifier /flags [ ...] /all verifier /flags [ ...] /driver [ ...] verifier /rules {query | reset | default | disable } verifier /query verifier /querysettings verifier /bootmode {persistent | resetonbootfail | oneboot | resetonunusualshutdown} verifier /persistthroughupgrade verifier /reset verifier /faults [probability [pool_tags [applications [delay_minutes]]]] verifier /faultssystematic [ ...] verifier /log [/interval ] verifier /volatile /flags [ ...] verifier /volatile /adddriver [ ...] verifier /volatile /removedriver [ ...] verifier /volatile /faults [probability [pool_tags [applications [delay_minutes]]]] verifier /domain {wdm | ndis | ks | audio} [rules.all | rules.default ] /driver ... [/logging | /livedump] verifier /logging verifier /livedump PARAMETERS: /? or /help Displays this help message. /standard Specifies standard Driver Verifier flags. /all Specifies that all installed drivers will be verified after the next boot. /driver [ ...] Specifies one or more drivers (image names) that will be verified. Wildcard values (e.g. n*.sys) are not supported. /driver.exclude [ ...] Specifies one or more drivers (image names) that will be excluded from verification. This parameter is applicable only if all drivers are selected for verification. Wildcard values (e.g. n*.sys) are not supported. /flags [ ...] Specifies one or more options that should be enabled for verification. Flags are applied to all drivers being checked by Driver Verifier. The provided options values must be either in decimal, hexadecimal ("0x" prefix), octal ("0o" prefix) or binary ("0b" prefix) format. Standard Flags: Standard Driver Verifier options can be specified using '/standard'. WDF verification is included in /standard but is not shown here. 0x00000001 (bit 0) - Special pool 0x00000002 (bit 1) - Force IRQL checking 0x00000008 (bit 3) - Pool tracking 0x00000010 (bit 4) - I/O verification 0x00000020 (bit 5) - Deadlock detection 0x00000080 (bit 7) - DMA checking 0x00000100 (bit 8) - Security checks 0x00000800 (bit 11) - Miscellaneous checks 0x00020000 (bit 17) - DDI compliance checking Additional Flags: These flags are intended for specific scenario testing. Flags marked with (*) require I/O Verification (bit 4) that will be automatically enabled. Flags marked with (**) support disabling of individual rules. 0x00000004 (bit 2) - Randomized low resources simulation 0x00000200 (bit 9) - Force pending I/O requests (*) 0x00000400 (bit 10) - IRP logging (*) 0x00002000 (bit 13) - Invariant MDL checking for stack (*) 0x00004000 (bit 14) - Invariant MDL checking for driver (*) 0x00008000 (bit 15) - Power framework delay fuzzing 0x00010000 (bit 16) - Port/miniport interface checking 0x00040000 (bit 18) - Systematic low resources simulation 0x00080000 (bit 19) - DDI compliance checking (additional) 0x00200000 (bit 21) - NDIS/WIFI verification (**) 0x00800000 (bit 23) - Kernel synchronization delay fuzzing 0x01000000 (bit 24) - VM switch verification 0x02000000 (bit 25) - Code integrity checks /ruleclasses or /rc or /dif [ ... ] This parameter is larger set of '/flags' above. While '/flags' is limited to 32 bit bitmap expression, this can include more than 32 verification classes. Each positive decimal integer represents a verification class. Multiple classes can be expressed by separating each class id with space character. The '/dif' command automatically includes rule class 36, DIF mode, but /ruleclasses and /rc do not. Rule classes marked with (RuleClassId) requires users to pass dependent rule class. Flags marked with (^) can be enabled without reboot using the '/dif [ ] /now' command. Rule classes marked with (**) support disabling of individual rules. Rule classes marked with (***) are in logging mode by default and require /onecheck in order to crash upon violation. The following rule class IDs are available (no leading 0's required): Standard Rule Classes: 1 - Special pool (^) 2 - Force IRQL checking (^) 4 - Pool tracking (^) 5 - I/O verification (^) 6 - Deadlock detection (^) 8 - DMA checking (^) 9 - Security checks (^) 12 - Miscellaneous checks (^) 18 - DDI compliance checking (^) 34 - WDF Verification 37 - File System Filter verification (5) Additional Rule Classes: These rule classes are intended for specific scenario testing. 3 - Randomized low resources simulation 10 - Force pending I/O requests (5) 11 - IRP logging (5) 14 - Invariant MDL checking for stack (5) 15 - Invariant MDL checking for driver (5) 16 - Power framework delay fuzzing 17 - Port/miniport interface checking 19 - Systematic low resources simulation (36, ^) 20 - DDI compliance checking (additional) (^) 22 - NDIS/WIFI verification (**) 24 - Kernel synchronization delay fuzzing 25 - VM switch verification 26 - Code integrity checks 33 - Driver isolation checks (***, 36) 36 - Driver Interception Framework (DIF) mode 43 - SCSI Port verification 44 - Storport verification 45 - Win32 verification (3) /dif [ ] /now Enables the rule classes immediately without needing reboot. This option is only valid if no rule classes are already running. See the rule class descriptions for the rule classes capable of immediate activation. /action [1 ... k] This switch is generally used for communicating with plugins and is dependent on '/dif' switch. A positive number is plugin specific communication action ID. Plugins optionally show further usaga via 'verifier /dif {PluginId} /?'. /stop Disables rule classes enabled via '/dif /now' to halt verification. /log.code_integrity This option suppresses Code Integrity violation breaks and collects only statistics for verified drivers. Statistics could be extracted via /log option or kernel debugger. This parameter is applicable only if Code Integrity checks are enabled. /rules {query | reset | default | disable } Specifies rules level control (advanced). query Shows current status of controllable rules. reset Resets all rules to their default state. default Sets rule ID to its default state. disable Disables specified rule ID. /query Display runtime Driver Verifier statistics and settings. /querysettings Displays a summary of the options and drivers that are currently enabled, or options and drivers that will be verified after the next boot. The display does not include drivers and options added using /volatile. /bootmode Specifies the Driver Verifier boot mode. This option requires system reboot to take effect. persistent Ensures that Driver Verifier settings are persistent across reboots. This is the default value. resetonbootfail Disables Driver Verifier for subsequent reboots if the system failed to start. resetonunusualshutdown Driver Verifier persists until unusual shutdown happens. Its abbrevation, 'rous', can be used. oneboot Enables Driver Verifier only for the next boot.
4 entries

Associated Headers

HeaderSymbolicDescription
0 entries