
tennic
Member-
Posts
25 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
tennic's Achievements
-
After using the unlocked version 1.07.08 for years, I need to lock it again, before sending the computer in for service. I tried the procedure, selecting item 2 "relock", but it doesn't work, the BIOS remains unlocked. Any possible solution?
-
I tried a "BIOS defult" but this didn't resolve the problem. I will try a complete reinstallation of original BIOS 1.07.08 (latest BIOS that I have, download from Clevo website years ago) ๐ค
-
Thank you. Unfortunately, for the X170KM-G, I saw that it is not very updated, the latest BIOS available is 1.07.07, while on the official website (when you could still download BIOS), I had downloaded 1.07.08, and currently XMG has published 1.07.09 (so evidently the official version of version 1.07.09 should exist). However, I am resigning myself to sending the computer for repair, the only way to make it pass the POST is to remove all the SSD units, or leave one and try turning it off and on many times, or with 2 SSD units connected, the probability that it passes the POST is perhaps 1 in 50.
-
Unfortunately XMG customize the BIOS, it is not "original", but in the absence of anything else I can try that. I used to find the BIOS on the official CLEVO website, but now they are no longer present. I have currently been using version 1.07.08 modified to have the complete menus for years, and it works perfectly. A problem has been occurring for a few days, the computer often does not pass the POST, it remains blocked, and I have to turn it off and on several times, until it goes forward. During the POST, the RAM test (very long, for 64GB), is regularly passed. Initially I thought the cause was a damaged SSD, in fact when I removed it then the computer started regularly. Therefore I changed the SSD, finding that it shows the problem even with the new one. The problem rarely occurs if I leave only one SSD (regardless of which one it is and which slot it occupies), while it is practically constant if I insert both SSDs, regardless of which slots I use (I tested by swapping the 2 SSDs in the 4 slots) Therefore, the BIOS update is the last resort, but I am skeptical that it will solve anything. Has anyone ever had a similar problem?
-
Where can I find the official BIOS? In the Clevo sites where I searched there are various drivers (very old) but not the BIOS (years ago it was present instead) ๐ค
-
2x32GB @3200MHz (CL16) work perfectly only with unlocked bios, setting the XMP profile ๐
-
Unfortunately yesterday there were two sudden shutdowns. Therefore, in my case, disabling C-States seems to have only affected the BSODs when I enable Overclocking mode in BIOS, in fact at the moment no BSODs happen anymore, but sudden shutdowns still happen. As soon as possible I will install the EC kindly indicated by Sergey Muratov, to see if it only solves the problem of restarting after sudden shutdown, or it also avoids sudden shutdown
-
Excuse me, I hadn't read your post. I don't use the battery, but I think the problem is the same, since I have to electrically disconnect the computer, to be able to rekindle it. I will try to install the EC version indicated (now I am using the official 1.07.04), but this is a secondary problem, the primary problem is that it suddenly turns off. However, I disabled C-State, and for a few days no sudden shutdown has been verified, and not even BSOD despite having tried to enable the overlclocking mode in the BIOS, in order to use the XMP profile of the RAM (3200 MHz CL16)
-
Currently the Ram (2x32 GB) are installed in the bottom of the computer, installing them under the headboard solves the Windows BSOD problem when overclocking is activated in the bios? Instead, as regards BIOS and EC, they are both updated to the latest official version๐
-
There are actually two types of problems: - BSOD when overclocking mode is activated in the BIOS, and then the relative tile appears in the Control Center, but no "hardware problem", the computer restarts perfectly (I solved it by not enabling overlocking from the BIOS ๐) - Abrupt physical shutdown, with no errors in the OS (which is what has been happening to me lately), and then the computer doesn't turn back on, until after unplugging and plugging the power again If I remember correctly, did you have the first type of problem? Or am I wrong?๐
-
After months of good operation, sudden shutdowns are happening these days while I play with full screen games. The strange thing is that it's impossible for the temperatures to be high, I'm playing with the "quiet" energy profile (the game, Fallout 76, doesn't respond well to commands if the FPS is very high, so if the computer runs at full speed), and fans on personalized, but following the predefined profile, therefore already with a temperature of 50ยฐC they turn at 50% of the speed. While gaming, I don't hear the fans spinning fast, so temperatures should be cool. Well, every now and then, a sudden shutdown occurs, and the computer doesn't turn back on again, if I try to turn it on again, the power LED turns green for a few moments, and then turns orange again. it is necessary to switch off the computer by disconnecting the electric cable, switch it on again, and only at this point can it be switched on. Is there any way to try to avoid these sudden shutdowns?
-
I will try this setting, to see if it solves the problem ๐ Problem which however, in my case, is caused by the Control Center, i.e. when I activate the overclock in the BIOS, the "overclock" tile appears in the Control Center, and this component causes the Windows BSOD. Without Control Center no BSOD occurs
-
So, if I disable this setting no more BSOD's occur when overclocking is enabled? (although not actually used)? Thanks๐
-
It happened to me too, I seem to remember that I solved it by saving, restarting, entering the bios again, and this time you can select the XMP1 profile
-
In fact, just because they have the same hardware I tried the XMG BIOS but without solving the problem, so I went back to the official Insyde BIOS๐ Hopefully they can fix it ๐