But when running only the latest version of one (non-Microsoft) program out of dozens (100s? 1000s?) in "years" causes such a specific BSOD, you cannot blame Microsoft. I'm all for bashing Microsoft when bashing is due - and certainly they've done plenty that deserves bashing. Running V1.27, HWMonitor, HWInfo64, CoreTemp, Belarc Advisor, Windows System Information and CPUz - not to mention all my other programs too - do not and have not caused any BSODs. Only after upgrading to and running Speccy 1.28 did I receive BSODs with W10 - my only BSODs with W10. So running only the latest version of "Speccy" causes a BSOD with "CPU-Z" - two programs that are NOT made by Microsoft, no other BSODs in "years" indicating all other programs run just fine, yet Microsoft is to blame for creating this problem?įTR, I did not have any BSODs with 1.27. Makes me wonder what M$ did to the OS to potentially cause the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |