My husband was in michigan this week and that was one of the flights he thought about taking on thursday night. He flies a lot and it just hit close to home. Clarence is not far from where we live. We are a little more out in the country. Big sigh of relief. When the news came on at 10pm they announced at the end of the broadcast that a plane had crashed by the airport, but they didn't know anything yet. By the time the 11pm news came on, it was not until after the weather that their news crews made it to the neighborhood and they announced it was a commercial plane. WIVB broadcast without commercial break until I went to bed at 2am. When my husband called to say he was alright i was so grateful. (wipes tears and sniffles) Fran, Could i have the blanket flower, please? BTW, DS#3 watered my keyboard once, its still a little iffy. We set it in from of the blower on the woodstove for a week. Just FYI those of you sowing in the keys LOL! Thank all of you for the prayers. Families here are esp. close knit and things like this are difficult for anyone. Praying for your FIL, too Nichol. Fleethart

The problem is a corrupted area of the hard drive. The remedy is to run chkdsk /r If you can't run it within Windows, try Safe Mode. If that doesn't work, run it from the Recovery Console. Any more BSOD's while doing the above and you need to save as much as possible and do a clean install.

You can run some basic scans that might repair something but usually blue screen is a driver file that needs reinstalled or updated.. Look in Device Manager to see if any warnings? From your Command Prompt (admin) ChkDsk /Scan DISM /Online /Cleanup-image /Scanhealth DISM /Online /Cleanup-Image /RestoreHealth SFC /ScanNow You can get to F8 from any power button... click Restart while holding the Shift key. Or just add it to your boot manager with this command.... Bcdedit /set (bootmgr) displaybootmenu yes (((( those brackets above are the Curly brackets )))]]] that don't seem to show right here when posted. then go to MSConfig boot tab and set the timeout to maybe 5 seconds. Then you will have a option to press F8 for 5 seconds anytime when you restart the computer. This post was edited by mikie on Thu, Jul 18, 13 at 19:33

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.