A verificação de bug DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) é causada pelo driver Xeno7x64.sys:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000213, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff88006e94c02, The address in the driver's code where the error was detected.
Arg3: fffff98008258e10, IRP address.
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0xc9_213
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 213
FAULTING_IP:
Xeno7x64+1c02
fffff880'06e94c02 8bd8 mov ebx,eax
FOLLOWUP_IP:
Xeno7x64+1c02
fffff880'06e94c02 8bd8 mov ebx,eax
IRP_ADDRESS: fffff98008258e10
DEVICE_OBJECT: fffffa8015337990
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff800039094ec to fffff8000347cbc0
STACK_TEXT:
nt!KeBugCheckEx
nt!VerifierBugCheckIfAppropriate
nt!ViErrorFinishReport
nt!VfErrorReport1
nt!ViGenericVerifyIrpStackDownward
nt!VfMajorVerifyIrpStackDownward
nt!IovpCallDriver1
nt!VfBeforeCallDriver
nt!IovCallDriver
Xeno7x64
0x0
0x0
IMAGE_NAME: Xeno7x64.sys
FAILURE_BUCKET_ID: X64_0xc9_213_VRF_Xeno7x64+1c02
FAILURE_ID_HASH_STRING: km:x64_0xc9_213_vrf_xeno7x64+1c02
Loaded symbol image file: Xeno7x64.sys
Image path: \SystemRoot\system32\DRIVERS\Xeno7x64.sys
Image name: Xeno7x64.sys
Timestamp: Wed Dec 08 18:22:48 2010 (4CFFBEE8)
Atualize o driver para seu Adaptador de jogos PCI-E Bigfoot Networks Killer (TM).
A outra verificação de bug é causada pelo driver mvs91xx.sys:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 7
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
DPC_STACK_BASE: FFFFF88003528FB0
EXCEPTION_RECORD: fffff88003528b58 -- (.exr 0xfffff88003528b58)
ExceptionAddress: fffff880014ad67e (mvs91xx+0x000000000000367e)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000
LAST_CONTROL_TRANSFER: from fffff8000347a5be to fffff80003482b90
STACK_TEXT:
nt!KeBugCheck
nt!KiKernelCalloutExceptionHandler
nt!RtlpExecuteHandlerForException
nt!RtlDispatchException
nt!KiDispatchException
nt!KiExceptionDispatch
nt!KiBreakpointTrap
mvs91xx
mvs91xx
0x0
0x0
STACK_COMMAND: kb
FOLLOWUP_IP:
mvs91xx+367f
fffff880'014ad67f ?? ???
IMAGE_NAME: mvs91xx.sys
FAILURE_BUCKET_ID: X64_0x1E_mvs91xx+367f
FAILURE_ID_HASH_STRING: km:x64_0x1e_mvs91xx+367f
Loaded symbol image file: mvs91xx.sys
Image path: \SystemRoot\system32\DRIVERS\mvs91xx.sys
Image name: mvs91xx.sys
Timestamp: Tue Aug 09 05:05:23 2011
Este é o driver da Marvell-AHCI. Também atualize este aqui.