New
#11
Also the complete Blue Screen of Death (BSOD) Posting Instructions . The last one was missing a bunch of files we need. Sometimes it takes longer than you think to finish it's work.
Also the complete Blue Screen of Death (BSOD) Posting Instructions . The last one was missing a bunch of files we need. Sometimes it takes longer than you think to finish it's work.
Both files, I am pretty sure processes ended
thru, would you please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Run it and if it finds errors, close the program and reboot the computer, then run it again, up to 3 times. it may take 3 times to say windows found no integrity violations.
then run this again, it is not completing properly and some files appear to be corrupt.
Blue Screen of Death (BSOD) Posting Instructions
Both MSINFO texts are corrupter, systeminfo.txt is blank other files are missing. that is why I asked the above actions. We need those files to proceed.
Sfc found nothing. Everything seems fine.
My netbook is working for nearly 24 hours and no BSOD so far.
Well, I will save us some work. I will wait a bit. If there wont be any BSOD I will switch back to my old keyboard&mouse. If it wont cause and BSOD I will plug the new microphone and wait for it.
If there will meet any BSOD which wont be connected to input devices I will let you know.
I am not sure if re-installing VGA driver and C++ packages (which is used by that driver) have helped or it's because of switching USB devices or simply some luck.
I will mark the thread as solved for now until I get a new BSOD.
Thank you for your time Jedi Master essenbe!
I would suggest you do them one at a time and test it after each one so if you get a BSOD, you will know which one it is, assuming you get no BSOD before hand. I am not sure I did very much to help you, but thanks anyway.
I will do so!
You spent your own time on unknown's problem. I appreciate it.