Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {29ddc, ff, 0, fffff80244825baa}
Probably caused by : ntkrnlmp.exe ( nt!PpmIdlePrepare+41a )
Followup: MachineOwner
Hi Keith,
Bugcheck A is usually caused by drivers. I had a look through yours and one or two jump out as possible culprits:
AiChargerPlus.sys Thu Apr 19 02:17:35 2012: Asus Charger Driver known to cause BSODs.
MAXIMUS VIII HERO - Support
AsUpIO.sys Tue Aug 3 03:47:59 2010: ASUS hardware monitoring software related, too old for W10 really and needs updating or removed.
ASUSFILTER.sys Tue Sep 20 16:46:33 2011: ASUS USB Hub filter driver please update.
MAXIMUS VIII HERO - Support
LHidFilt.Sys Fri Feb 29 10:08:27
2008: Logitech SetPoint HID Filter Driver
LMouFilt.Sys Fri Feb 29 10:08:31
2008: Logitech SetPoint HID Filter Driver. Mouse drivers? Please update
Logitech Support + Downloads
Regarding the use of Raxco PerfectUpdater 2.0. I'm surprised you used something like this as these apps are fallible and can install the wrong driver. Your far better off sourcing and installing the drivers yourself. The motherboard driver support page is usually all you need but please stop using the auto updaters.
If the bsod continues then first make sure you have a recovery disk or zip drive and then run the driver verifier. The driver verifier can induce a bsod boot loop which is why you need to have a recovery key in order to boot from, enter safe mode and turn the verifier off.
This link shows you how to set up the verifier:
Link Removed