Here are your dump files so far
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88005696975, fffff8800abec740, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+6f975 )
Code:
nt!KiKernelCalloutExceptionHandler+e
fffff800`0346e2be 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 6.1.7601.18869
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Code:
Use !analyze -v to get detailed debugging information.
BugCheck D1, {77357f27, 2, 0, fffff8800426e534}
Probably caused by : hardware ( USBPORT!USBPORT_AssertListEntryLog+24 )
Followup: MachineOwner
Code:
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffffffffffff8b, 2, 0, fffff88003e11dd4}
*** WARNING: Unable to verify timestamp for spom.sys
*** ERROR: Module load completed but symbols could not be loaded for spom.sys
Probably caused by : spom.sys ( spom+424ce )
Followup: MachineOwner
Code:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa803860c0a1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880043bbed3, address which referenced memory
Code:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800034f4fd8, Address of the instruction which caused the bugcheck
Arg3: fffff88007f56cd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
For right now, please update all of your motherboard drivers from the Asus Web site for your board. Especially the Chipset driver and the Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC. Also make sure all of your Windows updates are currently up to date.