urlee, Like 'genes' and 'raven' said, you should not have more than one antivirus program running at the same time. If you plan on keeping Avast I would uninstall AVG either by using 'Programs/AVG/AVG uninstall' or 'Control Panel'. To answer your question: To disable AVG, right click on the AVG icon in the system tray (by the clock), and click on 'Quit AVG Control Center', that will shut down AVG. It will start up again however, if you should reboot your computer. To stop AVG from restarting on reboot go to the MS Config Utility, click 'Start', click 'Run', type in (msconfig) without the quotes and click 'OK'. In the 'System configuration utility' select the 'Startup' tab and deselect (uncheck) the box by 'avgcc' (avgcc.exe/startup). You will be asked to restart your computer, select 'Restart'. After your computer restarts you will get a 'nag' notification box that you have made changes to the Configuration Utility. 'Check' the box 'Do not show me this message again' and click ok. To have AVG start again with Windows go back into the Config Utility, recheck 'avgcc'. You will receive the same prompts again. Witz

Hi, Zep, I had not run the whocrashed program bc. sysnative has it's own two programs it recommends. I used those - the diagnostic one contained 18 files filled with information I would not have been able to decipher - including 2 containing the dump file info that were roughly 3 and 11 MB (roughly). But your post reminded me to download whocrashed for the future. I went ahead and ran it for curiousity's sake. The results are below. It does seem they are suggesting a bad drive - and in at least one place they point to Avast. The larger diagnostic files generated for sysnative showed all the crashes were tied to an Avast driver. I uninstalled and it's been running fine. I might want to reinstall Avast since I run it on all our home desktops and laptops. I'm familiar with it and it hasn't posed a problem elsewhere. The folks at sysnative suggest waiting a little longer and using microsoft security essentials for now. Whocrashed: On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21091-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: 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 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 Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x4133E) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) 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: aswsp.sys . Google query: aswsp.sys IRQL_NOT_LESS_OR_EQUAL On Sun 8/4/2013 9:33:50 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21340-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C9CD6C) Error: 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 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 Sun 8/4/2013 8:58:12 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21418-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CDCD6C) Error: 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 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 Sun 8/4/2013 6:30:46 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-22152-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CE6D6C) Error: 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 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. ----------------------------- This report is in somewhat more plain English - but seems to contain less specific diagnostics than the tests for sysnative. thanks. Lynn. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 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: aswsp.sys 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. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I have a 19 year old tabby who is suffering from CRF, which I really consider old age more than I consider it to be kidney failure. He is off the charts when it comes to longevity. The vet just gave me some RenAvast. My vet used to work with the Humane Society and he has been my cat's vet for 19 years. I'm going to trust him on this, but I'll update everyone in about a week or two to tell you if there is any difference. I understand people being cynical about something like this, but I figure if my vet of 19 years gave me this there must be something to it. I wanted to post my story for everyone because I don't want people to be too cynical about something that might help your kitty. Maybe it will work, maybe not. But in my case, it did come from a trusted source so there must be something to this.

OP-To see if the drawers can be adjusted enough to suit you try one yourself. Attached is a picture. From the looks of your level they are just a little beyond the built in adjustment. Naturally doors will also need to be adjusted and at some point if things are seriously off it will show in the reveal at the bottom of the cabinets. A careful installer should be able to "cheat" reveals so things don't look bad. Within the adjustment available there will be no impact on performance or longevity of the glides. Since you already have hardware installed adjusting drawerheads to boxes would be a headache and less than ideal. Should they be off that much? -NO. Is it a big problem?-with overlay cabinets not really but it is if you feel it is. Will it affect the counter installation over time?- Tre or someone else could better answer that but if the stone is fully supported over its' length I don' see why. Better than a shim every 3 ft IMO. Where/who is the problem?-First and foremost the cabinet installer - the job is to install plumb, level and square, then the counter installer AND the GC. . Why not the mfg?- it is all too easy to rack cabinets during installation. It is also easy to straighten slight imperfections in installation (especially on pocket hole cabinets). That is the installers job- install plumb level and square. Example- I handle two better brands of inset cabinets. One is doweled together the other is mortise and tenon. They always come dead straight and square. The cabinet is stiff compared to a pocket hole cabinet. The M&T cabinet has only an 1/8" reveal and mortised hinges that allow very little adjustment. I warn installers that they must back installation screws completely with shims and not to over torque them. Every now and then I get a call that the cabinet door is rubbing. I go to the job levels in hand and something is always off. Most of the time all that is needed is to relieve the pressure on one or two screws, shim it and gently tighten it back up. Voila reveal magically is straight and true. Levels- I'm with Mongrel on this- the only 4 ft I own is a masonry level that I wouldn't allow near a cabinet. I keep an ok torpedo, and quality 16" , 2', 3' and 6' (along with two on my phone, one on the tablet and a bubble lippage level for tile.) As a homeowner I use the 2 and 6 most. As a KD the 16" lives in my "go visit bag". When I pull up to the home during installation the 16, a tape measure, and notebook go with me. The 6 ft comes along on measures, when a problem is brought up, or during installation if I didn't see one there to begin with. Why should I have to check? as noted above even just a glorified cabinet salesman I need a couple of reliable levels at my disposal all the time. If your KD is not as pissy as me; then yes, you WANT to be able to check things. Folks are often asking here what to check BEFORE ordering or signing, well there are things worth checking DURING...It is a lot easier to take care of issues before completion than after. No one is perfect and you end up paying for it and living with it. If money is tight send DH to buy it, be careful with whatever packaging, then when done, go back and return it. You can have fun making up a story that DH is all thumbs and was nuts to buy it :) First run around the house and check a few things just for fun. oops, forgot to include adjustment info for you. This post was edited by jakuvall on Mon, Sep 1, 14 at 13:20