Hi Teeto,
Hold on, I don't think this is a memory problem, and Windows' diagnostic tool is by no means a good test for that (even though one might think it would be).
DPC_WATCHDOG_VIOLATION (133)
This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.
Since we don't have a kernel-dump, there's no way we can see what driver(s) causing the DPC hang. We can see if it was driver or driver(s) by checking the 1st argument:
Code:
3: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
1st argument = 1, this tells us multiple drivers caused it and not just one. This is also why we don't have an informative stack, as this happened
some time before the crash, and not just with one driver (for example holding a lock).
1. AiCharger.sys is listed and loaded in the modules list which is the Asus Charger driver. It's included in many Asus bloatware, which you appear to have installed. Please go ahead and uninstall any and all Asus software as it's unnecessary bloatware.
2. Remove and replace McAfee with
Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's
very likely causing conflicts:
McAfee removal - How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)
Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8
-- FWIW, I would never have McAfee on any of my systems.
Regards,
Patrick
