Interstingly, your first assumption may very well be correct.
Code:
BugCheck A, {4, 2, 0, 8168d170}
Unable to load image \SystemRoot\system32\DRIVERS\AiCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : AiCharger.sys ( AiCharger+40f )
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8168d170, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 8188647c
Unable to read MiSystemVaType memory at 8185e200
00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopBuildDeviceIoControlRequest+137
8168d170 8b4104 mov eax,dword ptr [ecx+4]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: SYSTEM
TRAP_FRAME: 8a68b9c4 -- (.trap 0xffffffff8a68b9c4)
ErrCode = 00000000
eax=8a674502 ebx=8652e878 ecx=00000000 edx=8a6745c8 esi=8a674554 edi=8652e888
eip=8168d170 esp=8a68ba38 ebp=8a68ba60 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!IopBuildDeviceIoControlRequest+0x137:
8168d170 8b4104 mov eax,dword ptr [ecx+4] ds:0023:00000004=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 817b6ee0 to 81739ee4
STACK_TEXT:
8a68b9a4 817b6ee0 0000000a 00000004 00000002 nt!KiBugCheck2
8a68b9a4 8168d170 0000000a 00000004 00000002 nt!KiTrap0E+0x2c8
8a68ba60 8168d021 00000003 84f8fa48 8a6745c8 nt!IopBuildDeviceIoControlRequest+0x137
8a68ba94 8fcd440f 00220003 84f8fa48 00000000 nt!IoBuildDeviceIoControlRequest+0x29
WARNING: Stack unwind information not available. Following frames may be wrong.
8a68bae0 8fcd4512 854e2900 842eb0b0 854e2900 AiCharger+0x40f
8a68bb90 8a54cdb2 8a68bc64 8a66e120 00000000 AiCharger+0x512
8a68bbc8 8168f3bd 84f8fee0 84f8fb00 27260e44 pci!PciPowerUpDeviceTimerDpc+0x12a
8a68bd40 817b84cc 00000000 0000000e 00000000 nt!KiRetireDpcList+0x286
8a68bd58 81732162 00000001 00000000 8a68bd8c nt!KiIdleLoop+0x38
8a68bd7c 81890eb3 ffdf03c0 8a68bda8 8a68bfc4 nt!KiGetXSaveSupportedFeatures+0x23
8a68bd8c 81890dc8 00000003 00000000 00000000 nt!KiSetXSaveEnabledFeatures+0x16
8a68bfbc 00000000 00000000 00000000 00000000 nt!KiInitializeXSave+0x67
STACK_COMMAND: kb
FOLLOWUP_IP: AiCharger+40f
8fcd440f ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: AiCharger +40f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AiCharger
IMAGE_NAME: AiCharger.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4be12e52
FAILURE_BUCKET_ID: 0xA_AiCharger+40f
BUCKET_ID: 0xA_AiCharger+40f You may want to start by uninstalling that ASUS utility you discussed above.
However if you are not able to boot into the OS and you haven't configured your system yet to safemode boot you may need to resort to some repair options either a refresh or a reset. Be aware either or both have consequences to installed programs and or data. Google Windows 8 Repair