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.

Hi Zep, Here's the information from the Whocrashed report. System Information (local) -------------------------------------------------------------------------------- computer name: LYNNDELL windows version: Windows XP Service Pack 3, 5.1, build: 2600 windows dir: C:\WINDOWS Hardware: Inspiron 530, Dell Inc., 0FM586 CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 2950799360 total VM: 2147352576, free: 2022486016 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Tue 6/10/2014 9:46:41 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini061014-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x5FC9E) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF85FC9E, 0xFFFFFFFFADB9BAE4, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- One crash dump has been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 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'll try reinstalling Firefox, but I'm doubtful because during the course of today - after my initial Firefox difficulties, I did update from Firefox 29 to Firefox 29.0.1. So I can re-install 29.0.1, but installing it this afternoon did not fix the problem. I'll check back later. And now I'll reinstall. Thank you. Lynn.

did they even go in to the event viewer and look at the error messages and codes with event ID? that should have given them some kind of idea. I would suggest fully uninstalling McAfee, use their tool too and remove all traces of it, I was amazed at the number of problems that McAfee had been causing on my pc when I took it off. be sure you use the mcafee removal tool after you have removed them from add remove programs or much will be left behind. I just removed McAfee from one of my computers. I had to go into msconfig and turn off all McAfee items from startup prior to trying to uninstall, just turning them off did not work it would say the program was still running. I then removed everything leaving Security center till last. Then used the removal tool, after that I went to Program Files and deleted all McAfee files. Also set Windows explorer to show all hidden files and folders and deleted the McAfee folders. I found the instructions on how to do this on the McAfee forums. 1. Uninstall all McAfee programs through "Add or Remove Programs" in Windows "Control Panel". 2. Use the MCPR tool, see this article: How to remove supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe). This will remove all McAfee remnants from your computer. (you must have Windows Vista, XP or 2000 SP4 to use this tool) 3. Launch Windows Explorer and delete all McAfee files in "Program Files" but especially in "C:\Document and Settings\\Application Data" and "C:\Document and Settings\All Users\Application Data". You have to set Windows Explorer to show all hidden files and folders (Tools > Folder Options > View tab). Just delete the McAfee folders even if they are empty in all the "Application Data" folders. Can be more than one! In Vista: C:\Program Files, C:\ProgramData and C:\Users\yourname\AppData\Roaming If you scroll down on this thread you will find these instructions given by EX Brit on how to use the removal tool and full removal and including this link. service.mcafee.com/FAQDocument.a···&lc=1033 forums.mcafeehelp.com/showthread···rus+scan

Well, the BSOD said what was wrong. Nobody could translate that information when you did not post those numbers. Further useful facts in the system (event) logs has now been destroyed by a nuke'n'pave. You have fixed many perfectly good things using hardware that was questionable. So now the problem is exponentially complicated. Learn from the experience. You fixed things without first learning what was defective. Destroyed or withheld information that could have identified that defect. And may now have multiple failures. The problems has been made exponentially more complex. I could walk you through the recovery process. But it will be long due to so many unnecessary changes and now so many other questionable items. Recovery means changes only after a defect is identified. The BSOD said what is defective. Post that information if still available. Get whatever is found in the new system logs. And buy or borrow a multimeter. Also learn this. Better computer manufacturers provide comprehensive hardware diagnostics for free on the hard drive, on a CD-rom, and on their web site. All manufacturers have them. But only the better manufacturers provide them. Your problem is why diagnostics exist and are so useful. To see the defect immediately. Because they cut costs (did not provide diagnostics), then notice how confused you have become. Another useful fact for when you next buy a new computer.