You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello folks. Yesterday, I got this error in GPT4ALL when using RAG. My laptop is a Surface Book 2, running the latest version of Windows 10. So far, GPT4ALL is an amazing app, as it helped me substitute Parmesan cheese in my lasagna, helped me clean the basin of my bathroom sink by recommending a vinegar soaked paper towel, and helps me with making devotionals. In 2020 (nearly 5 years ago), running artificial intelligence locally, let alone chatting with my documents would have been science fiction. This tech reminds me of Star Trek's computers.
One theory for why the error happened, is because the connection could be loose between my keyboard (GPU) and tablet (CPU) part of my laptop. It is showing signs of age. I am just waiting for a new AMD version of the Framework Laptop with 32 GB of RAM, and I expect the AI to run much better on that, plus Framework is future proof to an extent.
The text was updated successfully, but these errors were encountered:
Hello folks. Yesterday, I got this error in GPT4ALL when using RAG. My laptop is a Surface Book 2, running the latest version of Windows 10. So far, GPT4ALL is an amazing app, as it helped me substitute Parmesan cheese in my lasagna, helped me clean the basin of my bathroom sink by recommending a vinegar soaked paper towel, and helps me with making devotionals. In 2020 (nearly 5 years ago), running artificial intelligence locally, let alone chatting with my documents would have been science fiction. This tech reminds me of Star Trek's computers.
One theory for why the error happened, is because the connection could be loose between my keyboard (GPU) and tablet (CPU) part of my laptop. It is showing signs of age. I am just waiting for a new AMD version of the Framework Laptop with 32 GB of RAM, and I expect the AI to run much better on that, plus Framework is future proof to an extent.
The text was updated successfully, but these errors were encountered: