bl4z31nup

Hey everyone,


im working on a computer to where her sound is heavily malfunctioning. I uninstalled the device from the manager and reinstalled the device. and reinstalled the driver. i use WinStress to test the Sound device and it worked fine for abotu 10 minutes, Then the sound doesn't work until i turn off WinStress and it works. I reboot the computer, works for about 2 minutes then stops.

I ran Registry Mechanic and spotted about 141 errors. 75% of them were High Priority. I was able to fix a bout 17 of the files but the rest i couldn't do without a full version. Could a Registry Attack cause Sound Problems? Ive tried everything else i knew. And usually i take the problem to the root and thats in the registry. Let me know.

Thanks guys

jcgriff2

Hi bl4z31nup. . .

I must tell you that the title of this thread did catch my eye - but what exactly do you mean by a "Registry Attack"?

The Vista NT Registry is really nothing more than an index of sorts that contains information about every aspect of your system from boot-up to shut-down. Very little input/output data (files) used by installed programs is found within it - just mostly program parameters required to run the task at hand.

In my opinion, products such as the one you mentioned do nothing more than take advantage of consumers by scaring them to death when dealing with the Windows NT Registy - which most consider to be mysterious and complex. It most certainly is complex, but far from mysterious. There are millions of hits detailing all areas of the NT Registry found on Internet search engines throughout the world.

The fact that Registry Mechanic came up with 174 "errors" is preposterous and simply not true as if it were the case, your system probably would be (nearly) crippled and in need of much more help than they can provide - even with their "full" version for which you must pay. Furthermore, Vista would have let you know something about this a long time ago. I believe that the 174 items that came up are nothing more than harmless un/dis-associated registry keys - meaning that they do not refer to anything in the system at that moment in time. Many of them are probably from un-installed programs or currently installed programs that have been updated and the folder/file location that a registry key points to on their behalf is no longer there. Some others refer to now-non-existent help files that once were or maybe to a file extension that was used by a program that has since changed or has been removed.

Rarely is it necessary to actually "clean" the registry - usually only in times of system failure - and even then should be done so under instruction from an experienced technical adviser.

For perspective, I just performed a scan on my registry and came up with 3,831 entries or "errors" - which represents 0.32% of total - and pales in comparison to that total of 1.2 million entries (in my system).

Well, enough of the background on this subject for now. My suggestions to you are the following:

• Check the Device Manager for any red/yellow flags - specifically in the audio area
Bring up an ELEVATED command prompt
START | type dev man | click on Device Manager up top | respond to User Access Control prompt.

• Check the Event Viewer - look at entries at and before the exact time of your audio disruption
Go to an Elevated command prompt (DOS)
START | type eventvwr into the Start Search box | right-click on eventvwr.exe that appears up top | select Run as Administrator | view the various logs starting with the Administrative logs.

Good Luck to you.

Regards. . .

jcgriff2

bl4z31nup

Thank you for the feedback so soon. What i meant by Registry Attack was basically a virus that attacked the registry. I had the same problem the other day, this customer of mine i had her computer was basically crippled: couldn't use CD Drives, couldn't click links through emails and etc. .cleaned the registry and it was good as new. So i wasn't positive if that could be a problem.

I uninstalled and reinstalled the sound Hardware device and the driver for the laptop; the sound would work for about 10 minutes testing it with WinStress then it would just turn to crap again with no sound; The device in the manager was working properly. There wasn't any error or yellow warning. You can only uninstall and reinstall so many times and realize this isn't the problem So i went to the root and thought it could of been an error in the registry.