Avast scan stuck at 41

broken image
broken image

Are you not seeing any past BSOD's information displayed when you launch this utility? Look around startup time (for any processes, apps, or drivers that fail to start) and a couple hours prior to the lockup (which will be identified by by a generic Kernel Power EventID 41 that tells of the unexpected shutdowns).īlueScreenView should be able to gather information from past BSOD's by reading the mini-dump files created when they occur.

broken image

For example, Disk Errors in the System Event Log could indicate a failing HDD that may be causing the lockup. The best you can hope for is to examine the Windows System and Application Event Logs for any Warnings or Errors that may point to a troubleshooting direction. System lockups typically don't provide you with any diagnostic information.