Hwinfo itself does NOT cause any of the aformentioned problems even though it's probing and shows the Intel GPU. All it's doing (right?) is accessing the shared memory from Hwinfo. But it's a mystery to WHY the Hwinfo DLL for Rainmeter would cause any similar problems. ![]() It is NOT recommended for overclocking with MSI Afterburner. I went into safe mode and removed it.įound some posts about the "Intel HD Graphics" GPU which is a GPU integrated into the Intel® Bay Trail-T Quad Core Z3735 chip in my laptop. I noticed that AFTER I had the problem I also tried MSI Afterburner which caused even more serious problems including the machine not booting. Of course I just needed "HWiNFOHostId" and now it worksĭisabled the Hwinfo Rainmeter DLL's from loading. I got the skin showing readings from the local machine, but when I set "HWiNFOSensorId, HWiNFOSensorInstance, HWiNFOEntryId" for the remote sensor nothing showed. So my original intent was to use the below Rainmeter skin to show sensor readings from another machine over the network. I completely reinstalled and the problems has gone away. I missed a step or something on installation and was running an old Hwinfo DLL (from the custom skin see below) that was then causing some huge conflict. I'll report any findings whether or not they are related to HWiNFO.ĮDIT/UPDATE: Apologies for any confusion. It looks like I'll need to do further investigation. It sure would be nice if the issue was easier to reproduce. You may be correct in that the problem is not caused by HWiNFO, but so far I can only get it to happen when HWiNFO is running. It seems more likely that, rather than completely freezing, only some features stop working (e.g., video, network). Normally, if the computer is frozen that won't work. I noticed today that, when I became aware that my computer had crashed, I was able to toggle the Num Lock feature on my keyboard. Further, the machine isn't reachable from the network. In the morning, when I try to rouse my computer by wiggling the mouse or pressing a key, nothing happens. During this time, the monitors turn off but the computer doesn't actually go into sleep mode (I was incorrect about this in my initial post). The crash occurs when I leave my computer idle for a long period of time (e.g., overnight). I may have given some bad information in my initial post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |