Hang on I'll dig it
Hang on I'll dig it
Let me know if the link works
I don't think so. I'll look tomorrow. I'm burned out for the day. Thanks.Did you look for drivers here... Who knows what chipset that thing is using...
It's not the processor's fault, it's the hardware as a whole. You are still insistent on blaming the cpu manufacturer. They don't make the whole system package anymore, they make the chip. The hardware manufacturer for the computer is the one who puts many chips together and makes a whole package.Rather than blaming AMD I was leaning toward blaming Intel for sabotage as mentioned in the one article. It seemed plausible due to the way it acted when using the old program I used to decode Inmarsat packets. Intel has put out their own buggy cpus in the past so I'm not saying they are any better. Nobody is perfect. I'm just the consumer looking for something to work and was looking for something simple to cure this and it's become obvious that's not possible. And yes it's time to move on.
Sorry, didn't cross my mind in the beginning. Probably because everything else on the computer worked fine and was just thinking there was a setting somewhere that might be the cause. At this point it's not possible to say the problem is this or that or not this or not that. Don't worry about being rude. Time to move on.I know it will probably sound rude, but you probably should have mentioned from the start that's it's a no-name mini computer. As I posted way up in the thread I have several AMD computers with zero issues. Maybe this is a counterfeit AMD??
That was done many times during the course of trying so many things. Thanks for the input but I'm no longer pursuing the issue and have moved on.Try rebooting your PC. Seriously. Just fought the same thing for 2 hours. Rebooted pc. It all worked as it should.