Driver at fault: %s.
Without a debugger attached, the following bugcheck would have occurred.
PopCreateHiberFileSecurityDescriptor: Couldn't allocate Sec. Desc.
PPM: Thread affinitized to parked core %d.
PPM: Core %d previously unparked.  GenericUtility = %d. PercentFrequencySum = %d.
PPM: Parked Core %d overutilized.  GenericUtility = %d. PercentFrequencySum = %d.
PPM: Final unpark count = %d.
PPM: GenericUtilityPercentage = %d.
PPM: Increase Cores - Ideal.
PPM: New percent frequency sum = %d, new generic utility percentage = %d, new unpark count = %d.
PPM: Decrease Cores - Ideal.
PPM: Reporting PRCB = 0x%p as unparked.
PPM: Reporting PRCB = 0x%p as parked.
PPM: Choosing processors to unpark.
PPM: Processors left to unpark = %d.
PPM: Reduced candidate set to over utilized processors.
PPM: Reduced candidate set to highly utilized unparked processors.
PPM: Reduced candidate set to unparked processors.
PPM: Reduced candidate set to previously over utilized processors.
PPM: Processor %d chosen to be unparked.
Bad IRQL -- needed %x, got %x.
Bad IRQL -- needed %x or less, got %x.
Allocating too many map registers at a time: %x (max %x).
Allocated too many map registers : %x (max %x).
Freed too many map registers: -%x.
Freed too many common buffers.
Driver did not flush adapter buffers -- bytes mapped: %x (%x max).
Driver has allocated too many simultaneous adapter channels.
Driver has freed too many simultaneous adapter channels.
Driver has freed too many scatter gather lists %x allocated, %x freed.
KiCompleteEffectiveRangeChange: Overlapping MTRR ranges with conflicting memory type.
PopAllocatePages: Enter, requesting %d pages.
po: POP_WAKE_DEVICE_AFTER_SLEEP enabled.
The system may be powered off now.
Dump complete - %d total handles found.
Phar Lap Software, Inc.
Copyright (C) Rational Systems, Inc.
PopSetPowerSettingValue: state = %d, size = %d first ulong = 0x%08x.
PopSetPowerSettingValue: Creating new setting with empty values.
PopSetPowerSettingValue: Setting value didn't change.
PopSetPowerSettingValue: Allocating new value.
Unknown command passed to EtwWmitraceWorker.
D$ .
FP t.
t$ 9\.
Driver has attempted to access an adapter (%p) that has already been released.
Cannot put adapter %p until all adapter channels are freed (%x left).
Cannot put adapter %p until all common buffers are freed (%x left).
Cannot put adapter %p until all map registers are freed (%x left).
Cannot put adapter %p until all scatter gather lists are freed (%x left).
Driver is attempting to map a 0-length transfer.
Virtual address %p is before the first MDL %p.
Virtual address %p is after the first MDL %p.
Extra transfer length crosses a page boundary: Mdl %p, Length %x.
Cannot flush buffers that aren't mapped (Addr %p).
Area before %x byte allocation at %p has been modified.
Area after %x byte allocation at %p has been modified.
Verified driver or hardware has corrupted memory at %p.
Padding before allocation at %p has been illegally modified at %p.
Padding after allocation at %p has been illegally modified at %p.
Dma MDL %p not mapped in system VA.
CulpritAddress = %p, Irp = %p.
CulpritAddress = %p, Irp = %p, ExpectedStatus = 0x%x, ActualStatus = 0x%x.
CulpritAddress = %p, Irp = %p, Status = 0x%x.
CulpritAddress = %p, DeviceObject1 = %p, DeviceObject2 = %p.
CulpritAddress = %p, DeviceObject = %p.
CulpritAddress = %p.
CulpritAddress = %p, Irp = %p, DeviceObject = %p.
CulpritAddress = %p, Irp = %p, IRQL = %u.
This is a non-BTS processor - no branch tracing will occur.
Cancelled IRP %p didn't complete in due time.
Interrupt Service Routine %p has changed extended thread context.
Context saved before executing ISR: %p. Context saved after executing ISR: %p.
d        Display all log entries, paging is on.
help     Display this list.
restart  Restart the system immediately.
Type ? or Help for a list of commands.
New log entries have been added during dump, command aborted.
New log entries have been added while waiting, command aborted.
request with a failure status code.
A driver has forwarded an IRP at IRQL >= APC_LEVEL.
The I/O Completion APC routine will not be able to run for this IRP.
A driver has forwarded an IRP at IRQL > DISPATCH_LEVEL.
uninitialized variable bug in the driver.
a PDO.
underlying hardware stack.
than PASSIVE_LEVEL.
relations query.
A driver has deleted it's device object during a surprise remove IRP.
A driver has detached it's device object during a surprise remove IRP.
deleted via a prior call to IoDeleteDevice.
A driver has marked an IRP pending but didn't return STATUS_PENDING.
via a call to IoMarkIrpPending.
capabilities IRP was not properly initialized to -1.
capabilities IRP was not properly initialized to -1.
capabilities IRP was not properly initialized.
capabilities IRP was not properly initialized.
Caller has completed successful IRP_MJ_PNP instead of passing it down.
passing it down.
the TargetDeviceRelation query.
PDO has not responded to a required IRP.
pending if the PendingReturned field was set in the IRP passed to it.
IRP completion routines must be in nonpagable code, and this one is not.
this Irp or someone forgot to return STATUS_PENDING.
inconsistent with the Irp's IoStatus.Status field.
the hardware has not been reported as missing in a bus relations query.
should have been passed down.
major function.
it upon receiving a remove IRP.
being passed down stack. Failed POWER IRPs must be completed.
device objects elsewhere in the stack.
status of the IRP to indicate whether it's been handled or not.
being passed down stack. Failed PNP IRPs must be completed.
Caller has changed the information field of an IRP it does not understand.
Caller has changed the status field of an IRP it does not understand.
Caller has trashed or has not properly copied IRP's stack.
Caller has forwarded an Irp while skipping a device object in the stack.
returned by IoAttachDeviceToDeviceStack.
Any WMI IRP must have status initialized to STATUS_NOT_SUPPORTED.
Any Power IRP must have status initialized to STATUS_NOT_SUPPORTED.
Any PNP IRP must have status initialized to STATUS_NOT_SUPPORTED.
forwarded this IRP from another stack.
be broken.
Caller has passed in NULL as a DeviceObject.
the Irp to NULL.
same device object.
Caching is disabled by incorrect MTRR settings.
KiInitializeMTRR: MTRR_MSR_DEFAULT is not consistent between processors.
CRASH TRIAGE: driver verifier settings present.
CRASH TRIAGE: triage skipped because it is not enabled by default.
CRASH TRIAGE: triage skipped because it is disabled explicitely.
CRASH TRIAGE: simulated crash code %X.
CRASH TRIAGE: null loader extension.
CRASH TRIAGE: unexpected loader extension size.
CRASH TRIAGE: standard retail exit point.
CRASH TRIAGE: a fake crash will be simulated.
CRASH TRIAGE: a real crash happened.
CRASH TRIAGE: previous crash was %p %p %p %p %p.
CRASH TRIAGE: triage skipped because it was active in previous crash or server system.
CRASH TRIAGE: some drivers changed from previous crash.
CRASH TRIAGE: triage disabled due to invalid registry rules.
CRASH TRIAGE: crash code %p will not be triaged.
CRASH TRIAGE: no `targets' rule found.
CRASH TRIAGE: triage disabled due to rule with null features.
CRASH TRIAGE: failed to get driver count from the dump.
CRASH TRIAGE: no suspect drivers will be selected for verification.
CRASH TRIAGE: will select target drivers for verification.
CRASH TRIAGE: zeroed rules structure (hit an invalid type rule).
CRASH TRIAGE: found a `targets' rule.
CRASH TRIAGE: rule was found for crash code %X.
CRASH TRIAGE: no rule found for crash code %X.
CRASH TRIAGE: found zeroed rule during validation.
CRASH TRIAGE: rules are ok.
CRASH TRIAGE: all drivers will be targetted.
CRASH TRIAGE: target drivers are `%ws'.
CRASH TRIAGE: system will enable verification features %X.
select Safe Mode.
for hard drive corruption, and then restart your computer.
Run system diagnostics supplied by your hardware manufacturer.
mismatched memory. Try changing video adapters.
select Safe Mode.
utilities or disk-intensive applications.
Options, and then select Safe Mode.
Mismatched kernel and hal image.
to make sure it is properly configured and terminated.
restart your computer.
Run a system diagnostic utility supplied by your hardware manufacturer.
memory. Try changing video adapters.
Advanced Startup Options, and then select Safe Mode.
Hardware malfunction.
Audit attempt has failed.
This system may be infected with a virus.
One or more critical user mode components failed to satisfy a health check.
Inconsistency detected in the PCI Bus driver's internal structures.
Ntfs Structured Storage as a DOCFILE.
system vendor for an updated BIOS.
Allocate from NonPaged Pool failed for a HAL critical allocation.
A wait operation, attach process, or yield was attempted from a DPC routine.
A parity error in the system memory or I/O system was detected.
An initialization failure occurred while attempting to boot from the network.
boot from the network.
The hibernated memory image does not match the current hardware configuration.
An attempt was made to write to read-only memory.
An attempt to access PCI configuration space failed.
so that your operating system will continue to function properly.
A device driver attempting to corrupt the system has been caught.
with a working version.
A device driver has pool.
Check to make sure any new hardware or software is properly installed.
for any Windows updates you might need.
Run the driver verifier against any new (or suspect) drivers.
If that doesn't reveal the corrupting driver, try enabling special pool.
point where the offending driver can be identified.
and then select Safe Mode.
A device driver attempting to corrupt the system has been caught.
with a working version.
a device driver that has not cleaned up properly before freeing memory.
The processor's IRQL is not valid for the currently executing context.
it has finished its task.
The IO manager has detected a violation by a driver that is being verified.
replaced with a working version.
Plug and Play detected an error most likely caused by a faulty driver.
The system is attempting to access memory after it has been freed.
This usually indicates a system-driver synchronization issue.
The system is attempting to access memory beyond the end of the allocation.
This usually indicates a system-driver synchronization issue.
The driver mistakenly marked a part of it's image pagable instead of nonpagable.
The driver unloaded without cancelling pending operations.
The driver is attempting to access memory after it has been freed.
The driver is attempting to access memory beyond the end of the allocation.
The driver is attempting to unmap an invalid memory address.
The driver has used an excessive number of system PTEs.
The driver is corrupting the locked pages tracking structures.
The driver is mismanaging system PTEs.
A driver has corrupted the memory management system PTEs.
of the stack's thread.
A driver corrupted pool memory used for holding pages destined for disk.
disable impersonation before it returned.
faulty by running the diagnostic disk or tool that came with your computer.
hardware problem thereby allowing Windows to operate.
The end-user manually generated the crashdump.
A thread tried to release a resource it did not own.
before freeing memory.
with a usermode execution routine.
working version.
the state was found to be invalid.
that called IoCancelFileOpen is at fault.
An executive worker thread is being terminated without having gone through the worker thread rundown code.
Work items queued to the Ex worker queue must not terminate their threads.
A stack trace should indicate the culprit.
hardware incorrectly.
Please check with your hardware device vendor for any driver updates.
losing data.  Any filesystem or filter driver in the stack may be at fault.
The kernel attempted to ready a thread that was in an incorrect state such as terminated.
The SCSI verifier has detected an error in a SCSI Port/Storport miniport driver being verified.
An interrupt storm has caused the system to hang.
The system does not shutdown in a deterministic manner so bugchecks can occur.
A process or thread crucial to system operation has unexpectedly exited or been terminated.
The PCI driver has detected an error in a PCI device or BIOS being verified.
user to gain control of this machine.
An initialization failure occurred while attempting to boot from the RAM disk.
name spaces.
eventual corruption of the thread pool and an access violation.
before an exit from the machine check code could be completed.
An attempt was made to execute to non-executable memory.
memory management. This indicates a driver bug.
An attempt was made to insert an entry in a reserve queue that was already full.
The loader block is invalid or does not match the system being loaded.
A clock interrupt was not received on a secondary processor within the allocated time interval.
The DPC watchdog routine was not executed with the allocated time interval.
An invalid AGP memory access was detected.
The Graphics Aperture Redirection Table (Gart) is corrupt.
The AGP HW has been reprogrammed by an unauthorized agent.
A thread is terminating or attempting a win32 callout while running on an expanded stack.
A 3rd Party file system or file system filter has failed in an unrecoverable way.
Modification of system code or a critical data structure was detected.
A violation has been detected in the use of FsRtl Extra Create Parameter package.
The Windows Driver Framework has detected that a violation has occurred.
The video memory manager has encountered an unexpected fatal error.
A driver has passed an invalid parameter to a C runtime function.
before an exit from the non-maskable interrupt could be completed.
The kernel mode RPC facility has detected that a state violation has occurred.
The dxgkrnl has encountered an unexpected fatal error.
The shadow driver has encountered an unexpected fatal error.
The AGP driver has encountered an unexpected fatal error.
Attempt to reset the display driver and recover from timeout failed.
The display driver failed to respond in timely fashion.
The kernel has detected an inconsistency in hypervisor enlightened operation.
The video scheduler has encountered an unexpected fatal error.
The Errata Manager has encountered an error on initialization.
A driver has returned from a cancellation call holding the global cancel lock.
configuration manager.
Event Tracing subsystem has encountered an unexpected fatal error.
A file system has caused too many recursive faults under low resource conditions to be handled.
object and referencing the handle.
BitLocker Drive Encryption encountered a problem that it cannot recover from.
A driver has committed an illegal action.
The system encountered a fatal internal error in its hardware error support.
The cryptographic subsystem failed a mandatory algorithm self-test during bootstrap.
The system encountered an uncorrectable hardware error.
NMR (network module registrar) has detected an invalid state.
An invalid pool request has been made to netio managed memory pool (e.g. FSB and MDL).
A worker threads IOPriority was wrongly modified by the called worker routine.
A worker threads Paging IOPriority was wrongly modified by the called worker routine.
Windows did not find any installed, licensed language packs for the system default UI language.
Run CHKDSK /F to check for corruption, and then restart your computer.
Multiple threads have accessed a mutually exclusive resource.
IoBuildPartialMdl was called with a virtual address range outside the range of the source MDL.
An initialization failure occurred while attempting to boot from a VHD.
configuration of processors in the system.
Invalid combination of parameters was detected while saving or restoring extended processor state.
An invalid resource owner pointer was supplied.
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
The drive extender component has experienced a severe internal error.
This bugcheck is caused by an unhandled exception in a registry filtering driver.
The volume that hosts the VHD does not have enough free space to expand the VHD.
The hypervisor has encountered a fatal error.
to your computer.
Check to make sure any new hardware or software is properly installed.
for any Windows updates you might need.
or software. Disable BIOS memory options such as caching or shadowing.
select Safe Mode.
Physical memory dump complete.
A Video Driver Debug Report request.