(1)Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkCddWaitForVerticalBlankEvent+2cc ) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003. This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG. This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff800c060ec7e, The address that the exception occurred at Arg3: ffffe500a4e06bb8, Exception Record Address Arg4: ffffe500a4e06400, Context Record Address (2)Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+4a8 ) KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments: Arg1: 0000000000000000, A stack-based buffer has been overrun. Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, Reserved 两个蓝屏信息 帮看下是怎么回事