CptCaveman
New Member
- Joined
- Jan 14, 2018
- Messages
- 3
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, fffff802e408ae50, ffffe5031e031ff0, fffff802e1bea386}
*** WARNING: Unable to verify timestamp for mcupdate.dll
*** ERROR: Module load completed but symbols could not be loaded for mcupdate.dll
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+430 )...
Hi folks - I didn't attach the correct dump in the initial post - I edited the thread and attached the correct one - so kemical might have seen the original post which was missing the correct attachment - apologies for the confusion.They have ran that, not sure why but I needed to approve the post for it to show up.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, fffff802e408ae50, ffffe5031e031ff0, fffff802e1bea386}
*** WARNING: Unable to verify timestamp for mcupdate.dll
*** ERROR: Module load completed but symbols could not be loaded for mcupdate.dll
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+430 )
Followup: MachineOwner
Hi,
I can see this 'mcupdate' firing off in the call stack and having never heard of it before ran a search.
Apparently mcupdate.dll can be associated with anti virus products are you using MCAFEE or have done so in the past?
(I can see your currently running Bitdefender)
Failing that you could try running the driver verifier and see if catches anything?
...
.