解决12-14代CPU在win7上睿频不正常的方法。
本帖最后由 Canon-控 于 2024-1-30 11:38 编辑从AMD的500及Intel 600系开始,由于BIOS结构的调整,CPU的硬件加载不再采用以前的老标准,采用了ACPI0007这种只支持win8以上系统的方案。这种方案导致硬件管理器不加载CPU,由于AMD平台的睿频由BIOS控制,所以不影响。但Intel的睿频跟随系统,所以睿频不正常。所以可以通过修改BIOS,把ACPI0007修改回传统的加载CPU方法。(黑苹果睿频问题也可以这么弄。)效果如图:
下面说说解决办法:
1、在UEFITool中打开需要修改的官方BIOS文件
2、Ctrl+F 搜索GUID C118F50D-391D-45F4-B3D3-11BC931AA56D
3、Extract Body提取Raw section 部分另存为 1.raw
4、从https://www.acpica.org/downloads下载最新的iasl.exe
5、反编译提取的 1.raw(直接拖拽1.raw文件放到iasl.exe文件上就可以自动编译与反编译)
6、打开反编译的 1.dsl 文件并搜索:ACPI0007
7、找到以下内容:
Scope (_SB)
{
Device (PR00)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, Zero)// _UID: Unique ID
}
Device (PR01)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, One)// _UID: Unique ID
}
Device (PR02)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x02)// _UID: Unique ID
}
Device (PR03)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x03)// _UID: Unique ID
}
Device (PR04)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x04)// _UID: Unique ID
}
Device (PR05)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x05)// _UID: Unique ID
}
Device (PR06)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x06)// _UID: Unique ID
}
Device (PR07)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x07)// _UID: Unique ID
}
Device (PR08)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x08)// _UID: Unique ID
}
Device (PR09)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x09)// _UID: Unique ID
}
Device (PR10)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x0A)// _UID: Unique ID
}
Device (PR11)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x0B)// _UID: Unique ID
}
Device (PR12)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x0C)// _UID: Unique ID
}
Device (PR13)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x0D)// _UID: Unique ID
}
Device (PR14)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x0E)// _UID: Unique ID
}
Device (PR15)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x0F)// _UID: Unique ID
}
Device (PR16)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x10)// _UID: Unique ID
}
Device (PR17)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x11)// _UID: Unique ID
}
Device (PR18)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x12)// _UID: Unique ID
}
Device (PR19)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x13)// _UID: Unique ID
}
Device (PR20)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x14)// _UID: Unique ID
}
Device (PR21)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x15)// _UID: Unique ID
}
Device (PR22)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x16)// _UID: Unique ID
}
Device (PR23)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x17)// _UID: Unique ID
}
Device (PR24)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x18)// _UID: Unique ID
}
Device (PR25)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x19)// _UID: Unique ID
}
Device (PR26)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x1A)// _UID: Unique ID
}
Device (PR27)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x1B)// _UID: Unique ID
}
Device (PR28)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x1C)// _UID: Unique ID
}
Device (PR29)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x1D)// _UID: Unique ID
}
Device (PR30)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x1E)// _UID: Unique ID
}
Device (PR31)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x1F)// _UID: Unique ID
}
Device (PR32)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x20)// _UID: Unique ID
}
Device (PR33)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x21)// _UID: Unique ID
}
Device (PR34)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x22)// _UID: Unique ID
}
Device (PR35)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x23)// _UID: Unique ID
}
Device (PR36)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x24)// _UID: Unique ID
}
Device (PR37)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x25)// _UID: Unique ID
}
Device (PR38)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x26)// _UID: Unique ID
}
Device (PR39)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x27)// _UID: Unique ID
}
Device (PR40)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x28)// _UID: Unique ID
}
Device (PR41)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x29)// _UID: Unique ID
}
Device (PR42)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x2A)// _UID: Unique ID
}
Device (PR43)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x2B)// _UID: Unique ID
}
Device (PR44)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x2C)// _UID: Unique ID
}
Device (PR45)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x2D)// _UID: Unique ID
}
Device (PR46)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x2E)// _UID: Unique ID
}
Device (PR47)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x2F)// _UID: Unique ID
}
Device (PR48)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x30)// _UID: Unique ID
}
Device (PR49)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x31)// _UID: Unique ID
}
Device (PR50)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x32)// _UID: Unique ID
}
Device (PR51)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x33)// _UID: Unique ID
}
Device (PR52)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x34)// _UID: Unique ID
}
Device (PR53)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x35)// _UID: Unique ID
}
Device (PR54)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x36)// _UID: Unique ID
}
Device (PR55)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x37)// _UID: Unique ID
}
Device (PR56)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x38)// _UID: Unique ID
}
Device (PR57)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x39)// _UID: Unique ID
}
Device (PR58)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x3A)// _UID: Unique ID
}
Device (PR59)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x3B)// _UID: Unique ID
}
Device (PR60)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x3C)// _UID: Unique ID
}
Device (PR61)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x3D)// _UID: Unique ID
}
Device (PR62)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x3E)// _UID: Unique ID
}
Device (PR63)
{
Name (_HID, "ACPI0007" /* Processor Device */)// _HID: Hardware ID
Name (_UID, 0x3F)// _UID: Unique ID
}
}
8、把以上代码替换成以下代码:
Scope (_SB)
{
Processor (PR00, 0x00, 0x00001810, 0x06){}
Processor (PR01, 0x01, 0x00001810, 0x06){}
Processor (PR02, 0x02, 0x00001810, 0x06){}
Processor (PR03, 0x03, 0x00001810, 0x06){}
Processor (PR04, 0x04, 0x00001810, 0x06){}
Processor (PR05, 0x05, 0x00001810, 0x06){}
Processor (PR06, 0x06, 0x00001810, 0x06){}
Processor (PR07, 0x07, 0x00001810, 0x06){}
Processor (PR08, 0x08, 0x00001810, 0x06){}
Processor (PR09, 0x09, 0x00001810, 0x06){}
Processor (PR10, 0x0A, 0x00001810, 0x06){}
Processor (PR11, 0x0B, 0x00001810, 0x06){}
Processor (PR12, 0x0C, 0x00001810, 0x06){}
Processor (PR13, 0x0D, 0x00001810, 0x06){}
Processor (PR14, 0x0E, 0x00001810, 0x06){}
Processor (PR15, 0x0F, 0x00001810, 0x06){}
Processor (PR16, 0x10, 0x00001810, 0x06){}
Processor (PR17, 0x11, 0x00001810, 0x06){}
Processor (PR18, 0x12, 0x00001810, 0x06){}
Processor (PR19, 0x13, 0x00001810, 0x06){}
Processor (PR20, 0x14, 0x00001810, 0x06){}
Processor (PR21, 0x15, 0x00001810, 0x06){}
Processor (PR22, 0x16, 0x00001810, 0x06){}
Processor (PR23, 0x17, 0x00001810, 0x06){}
Processor (PR24, 0x18, 0x00001810, 0x06){}
Processor (PR25, 0x19, 0x00001810, 0x06){}
Processor (PR26, 0x1A, 0x00001810, 0x06){}
Processor (PR27, 0x1B, 0x00001810, 0x06){}
Processor (PR28, 0x1C, 0x00001810, 0x06){}
Processor (PR29, 0x1D, 0x00001810, 0x06){}
Processor (PR30, 0x1E, 0x00001810, 0x06){}
Processor (PR31, 0x1F, 0x00001810, 0x06){}
Processor (PR32, 0x20, 0x00001810, 0x06){}
Processor (PR33, 0x21, 0x00001810, 0x06){}
Processor (PR34, 0x22, 0x00001810, 0x06){}
Processor (PR35, 0x23, 0x00001810, 0x06){}
Processor (PR36, 0x24, 0x00001810, 0x06){}
Processor (PR37, 0x25, 0x00001810, 0x06){}
Processor (PR38, 0x26, 0x00001810, 0x06){}
Processor (PR39, 0x27, 0x00001810, 0x06){}
Processor (PR40, 0x28, 0x00001810, 0x06){}
Processor (PR41, 0x29, 0x00001810, 0x06){}
Processor (PR42, 0x2A, 0x00001810, 0x06){}
Processor (PR43, 0x2B, 0x00001810, 0x06){}
Processor (PR44, 0x2C, 0x00001810, 0x06){}
Processor (PR45, 0x2D, 0x00001810, 0x06){}
Processor (PR46, 0x2E, 0x00001810, 0x06){}
Processor (PR47, 0x2F, 0x00001810, 0x06){}
Processor (PR48, 0x30, 0x00001810, 0x06){}
Processor (PR49, 0x31, 0x00001810, 0x06){}
Processor (PR50, 0x32, 0x00001810, 0x06){}
Processor (PR51, 0x33, 0x00001810, 0x06){}
Processor (PR52, 0x34, 0x00001810, 0x06){}
Processor (PR53, 0x35, 0x00001810, 0x06){}
Processor (PR54, 0x36, 0x00001810, 0x06){}
Processor (PR55, 0x37, 0x00001810, 0x06){}
Processor (PR56, 0x38, 0x00001810, 0x06){}
Processor (PR57, 0x39, 0x00001810, 0x06){}
Processor (PR58, 0x3A, 0x00001810, 0x06){}
Processor (PR59, 0x3B, 0x00001810, 0x06){}
Processor (PR60, 0x3C, 0x00001810, 0x06){}
Processor (PR61, 0x3D, 0x00001810, 0x06){}
Processor (PR62, 0x3E, 0x00001810, 0x06){}
Processor (PR63, 0x3F, 0x00001810, 0x06){}
}
9、编译修改好的 1.DSL文件(直接拖拽1.DSL文件放到iasl.exe文件上会自动生成 1.aml)。出错的话,可以用cmd运行iasl.exe强制编译,命令如下:iasl -f 1.dsl
10、回到UEFITool中,用1.aml文件替换(Replace Body)GUID C118F50D-391D-45F4-B3D3-11BC931AA56D里的Raw section,然后另存为BIOS文件。
11、修改的BIOS 用flashback刷BIOS,具体参考各家主板的指南。
12、只推荐有一定DIY基础的玩家去折腾
厉害...学习了... 不明觉厉,不愧是搞驱动的大师! 十二代的机子装win7设备管理器中竟然没有一个问号、一个感叹号,我是真服了! 厉害。
看天书一般。
不敢弄。 有点复杂,不敢弄啊,谢谢楼主! 大佬就是牛,留个脚印 还有个比睿频更严重的问题是BIOS里面的存储控制器只有VMD模式,而win7没有VMD驱动,止步于此了。 ljq0527 发表于 2024-1-30 19:35 https://bbs.pcbeta.com/static/image/common/back.gif
还有个比睿频更严重的问题是BIOS里面的存储控制器只有VMD模式,而win7没有VMD驱动,止步于此了。
只有部分品牌机主板才这样。通用零售主板是有ahci的。 ljq0527 发表于 2024-1-30 19:35
还有个比睿频更严重的问题是BIOS里面的存储控制器只有VMD模式,而win7没有VMD驱动,止步于此了。
VMD驱动我弄个修改的,但好像用处不大,我测试了华擎和七彩虹主板都是默认关闭VMD功能。 这个帖子强烈推荐管理员加入精华帖,如果经常折腾黑苹果的人这个帖子的内容还是很简单的,普通用户的确有一点门槛。 战天涯 发表于 2024-1-30 16:40
十二代的机子装win7设备管理器中竟然没有一个问号、一个感叹号,我是真服了!
驱动好说,毕竟除了ME驱动要手动指定安装,其它的intel的官方芯片组驱动也是单纯在签名上限制了一下,强制安装就可以了。 时代是前进的,改放弃的就放弃 厉害了,确实牛! 这个操作方法门槛太高了 感觉很厉害,实际也很厉害的那种
https://herder.cdn.bcebos.com/images/dot.gif 2024年了,还能看到Canon大佬分享的win7修改驱动,感谢!!!!! Canon-控 发表于 2024-1-30 20:09 https://bbs.pcbeta.com/static/image/common/back.gif
VMD驱动我弄个修改的,但好像用处不大,我测试了华擎和七彩虹主板都是默认关闭VMD功能。
没有磁盘控制器驱动系统无法读写硬盘,开机就蓝屏,你修改的VMD驱动用处不大什么意思,不是只有两种情况吗,要么能用要么不能用;DIY领域的主板似乎大多都没启用VMD功能,品牌机尤其是品牌笔记本电脑默认启用了VMD的比较多 本帖最后由 ljq0527 于 2024-1-31 19:52 编辑
xdm2211 发表于 2024-1-30 19:39 https://bbs.pcbeta.com/static/image/common/back.gif
只有部分品牌机主板才这样。通用零售主板是有ahci的。
确实是这样,台式机我都是自己组装,笔记本电脑就得买品牌机了,这不,我的暗影精灵7笔记本电脑就因为只有VMD模式和win7绝缘了,而且这个VMD还有个不好的地方就是升级三星固态硬盘的升级程序无法用,必须要的M.2固态取下来撞到AHCI模式的电脑上升级好再装回来,比较麻烦。