2/20/2023 0 Comments Intel core 2 duo e7300 lan driverThat took maybe 30 to 45 minutes and was all the time I was going to spend. Tried unplugging all cards, memory and CPU and reseating everything. No display, just a voice error message (some ASUS boards have this) telling me that "System fail CPU test" I turned the system off at the power supply, waited a bit, turned it back on and then pressed the power button to boot it up. No power to the USB ports as the keyboard would light up nor would the mouse. My wife plugged a USB keyboard into the system which brought it down - display stayed up but it was definitely hung. This afternoon my ASUS mobo kicked the bucket. Looks like I'm setting up a new system sooner rather than later. Unless of course I switch it all over to Linux when final/stable drivers are available for the new hardware I want to get. When I convert the system to a pure server (no video output) I will scale back some of the services as well, in addition to some of the eye candy features of the explorer UI. But as I said, 99% of what's updated by MS has nothing to do with the requirements for the two programs I need to run 24/7 on that machine, so I don't risk installing them. I have no clue what part of them caused the issues as it was probably a combination and the way they were applied. The system became worse and worse until finally very unstable, strictly because of the updates that were put up by MS. Something I don't want to update unless I absolutely have to.īack a few years ago I can trace specifically my system troubles to the automatic Windows updates. None of the updates in the past year have required any system updates.įor me, this system is essentially an appliance, not a general purpose computer. If a new requirement is published for either Sage or Slim, then I evaluate and install the required component and any dependencies. Nothing should break when nothing is changed. Everything was configured when the system was set up and that's it. SlimCenter is written in Perl and only touches minimal parts of the system. It uses DirectX for video as well as BDA drivers for capture devices. SageTV is written in Java and some C I believe. On the same token: did you update video drivers and audio drivers? Drivers are the source of most windows system crashes. Then, should SageTV fail again, I suggest that you actually consider to run SageTV after another full (manual) system update. Or do they make any call to the OS DLLs or other OS components? I assume so.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |