BSODs After Installing Glary Utilities

I Installed the free version of Glary Utilities to my computer, a Dell Precision 690 WorkStation desktop (Windows 7 Professional 32-bit, Service Pack 1). I did so to compare it to Advanced SystemCare, which I've had on my computer for more than five years (Currently have PRO Version 7).

After installing GU and running several of its features, I noticed the next morning a Windows message that it had "recovered form an unexpected shutdown" -- meaning a BSOD crash. So I ran WhoCrashed to learn the cause and received the following information:

* * *

Crash dumps are enabled on your computer.

On Thu 6/5/2014 7:26:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060514-87578-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0xFFFFFFFF8F082D40, 0x2, 0x0, 0xFFFFFFFF83CA67A4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 6/5/2014 7:26:20 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0xFFFFFFFF8F082D40, 0x2, 0x0, 0xFFFFFFFF83CA67A4)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL



Conclusion
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


I've also attached the ZIP file with more crash information.

Has anyone else encountered BSOD crashes with Glary Utilities? And is there a compatibility issue between Glary Utilities and Advanced SystemCare loaded on the same computer?

Your analysis and reply will be greatly appreciated.

Window 7 does not need or want such programs as A.S.C. or Glary.

because?

Thanks for the link. That's what I've been looking for.

I don't have a very high opinion of any IOBit products or Glary Utilities. Windows has no need for and will not benefit from such utilities. The fact that Advanced System Care was previously installed (or is currently installed) further complicates things. Such products don't always coexist well and the results are unpredictable.

I would uninstall both and avoid all such programs. Unfortunately the uninstallers may leave behind portions of the programs which may continue to cause problems.

Lady Fitzgerald said:

the latter being superior to CCleaner for uninstalling programs.

true.

I use glary 2.xx portable

SkeeterVT, hope you find useful this info:

BSOD cause by ntoskrnl.exe ( nt+66d08 ) according to - Microsoft Community