I don't know; what are the details on the blue screen?
the blue screen says uninstall the previous install of hardware or whatever you installed. if this is the first notice just shut off the computer. it happened twice.it seeemed to be ditchinting something to a disk. not so sure about all this.
There is no error code or module name? If indeed not, can you check if there are more information in the Event Viewer?
Administrative events reports critical error from all administrative logs. other than that I don't know what I'm looking for under event viewer.there doesn't seem to be anything suspicous other than the admin logs
The blue screen came up again and this time it says bad pool header. Is that Flash Player or something else?
Bad Pool Header is not something you want to see. It usually means Hard drive problems, but it can (on very rare occasions) be "just an OS problem". I put that in quotes because "just an OS problem" in this case is ONLY remedied by completely reinstalling your Operating System, and that's in the rare event that your hard drive isn't on its last leg. From another forum (http://www.sevenforums.com/bsod-help-support/208817-bad-pool-header-bsod.html)
Your crashes could be related to system file corruption or errors on the hard disk. Use Advanced Boot Options to select Repair Your Computer and get to System Recovery Options and start command prompt.
Click Start and Run (or press the Windows key+R)
Run this three times
Yes, three times (unless the first time gives the message that there were no integrity violations). If that does not work, get into command prompt the Run command box as before and run the following lines.
chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:
until it says it cannot open the volume.
If the SFC (system file checker) shows errors it cannot repair... you need to reinstall your OS. Or if the chkdsk (check disk) says it cannot complete the check, then it's your hard drive.
Thank you. After the last repley I went to the control Panel and checked problems and reports only to find it was a driver failure. I then hit restore and that seems to have fixed the problem. Not sure why I didn't think of that first. Thanks so much for the support.