Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Glary Utilities?


  • Please log in to reply

#1
Nenei

Nenei

    Member

  • Member
  • PipPip
  • 27 posts
Is Glary Utilities a good, safe program to use, or is it a virus in disguise? What is a good program that can clean up registry errors?
I did a scan with Glary Utilities and it says I have 826 problems in my registry.
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Miracle programs like this will cause you more issues then you can imagine.
A registry cleaner will not increase your system's speed or performance, and has the potential to break your registry to the point that your PC is no longer bootable.
We strongly advise that people stay away from any of the registry cleaners out there.
Go HERE to get more information about why registry cleaners aren't needed.


Thanks to Sari for the explanation

Are you having any issues that would suggest a Registry issue or are you basing your statement solely on Glary Tools?
  • 0

#3
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
I have been getting bluescreens, and a friend told me it may be a registry issue and suggested Glary Utilities.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
BSOD's are not always Registry issues. Lets take a look and see what the Blue Screens are actually saying.

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#5
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
For some reason the program did not find anything in the minidump folder. Yesterday the blue screen happened 3 times, and I only remember one part: DRIVER_IRQL_NOT_LESS_OR_EQUAL.
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
That would indicate either a ahrdware or driver issue.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply







http://www.resplendence.com/downloads
  • 0

#7
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
The crash happened again this morning. I was able to get something on the BluescreenView and the Whocrashed.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 7/19/2011 1:25:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071911-16598-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFF88005646BD4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Tue 7/19/2011 1:25:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x1CBD4)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFF88005646BD4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
This may be the answer from your log.

It is suggested you look for an update for the following driver: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL


  • 0

#9
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
Thanks so much. Do you know how I can get an update for the driver?
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
First place I would suggest is the manufacturer of your system.
Is this a name brand system and if so what make and model. I can then try to locate the drivers page for it and see if there is a updated driver from the original.
  • 0

Advertisements


#11
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
it's an HP Compaq Presario CQ61-410US.
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Go HERE and expand the Network area. Middle driver there dated 2010-05-18 , Version:1.00, 20.91M looks ot be a newer driver then the one you have. Let me know if it works
  • 0

#13
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
It didn't work. I'm still bluescreening.
  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Can you post a new WHoCrashed log please.
  • 0

#15
Nenei

Nenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 7/25/2011 5:13:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-16005-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFF88003C39BD4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Mon 7/25/2011 5:13:34 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x1CBD4)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFF88003C39BD4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sat 7/23/2011 5:05:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072311-16536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFF88004E8CBD4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Tue 7/19/2011 1:25:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071911-16598-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFF88005646BD4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP