Windows 2012 r2 error code 0x000000c4
The following forum(s) have migrated to Microsoft Q&A: All English System Center 2012 Configuration Manager forums!
Visit Microsoft Q&A to post new questions.
Answered by:
Question
I am trying to install Windows 7 on a physical machine from Configuration Manager via OSD Deployment. As soon after the computer finishes loading the boot.wim file the following error is popping up
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x000000C4
Can anybody help please
Answers
A lot of these problems seem to relate to BIOS and Windows 8.1. Personally I would update the BIOS on the affected device to the latest version and try the OSD push again.
All replies
A lot of these problems seem to relate to BIOS and Windows 8.1. Personally I would update the BIOS on the affected device to the latest version and try the OSD push again.
I concur with Paul.
How old is this system you are booting?
What version of ConfigMgr 2012 (RTM, SP1,or R2)?
What boot image version are you using?
I am using Configuration Manager 2012 R2. The Computer I am trying to install is the Dell Optiplex GX620.
I tried upgrading the BIOS as Paul said, however the last BIOS update the I have found on the Dell website was one released in 2006, the A11 which I did upgrade to, but I experienced the same error.
Having said the above, however on other system with the same pc model the OSD worked properly.
Yes you’re correct. Drivers stopped around Windows XP, however if I install the PC with the Windows 7 DVD it works properly, even with Windows 7 64bit.
And since Microsoft is going to stop issuing updates for Windows XP next April 2014, I am trying to upgrade the last few computers we have to Windows 7, because budget have not been approved yet for new computers.
You may have to use an older version of WinPE to achieve this, specifically WinPE 3.1. See the link http://blogs.technet.com/b/brandonlinton/archive/2013/06/21/how-to-create-and-import-a-winpe-3-1-boot-image-for-use-in-configmgr-2012-sp1-cu2.aspx
Note it is not advised to run WAIK and ADK on the same SCCM server so install WAIK on another device.
Note it is not advised to run WAIK and ADK on the same SCCM server so install WAIK on another device.
Actually, it’s not possible to install them both on the same system to my knowledge. Also, each version of ConfigMgr requires a specific version of the AIK or ADK so installing another one would cause weird issues.
Ultimately, this is why I was asking about the version of the boot image though as many/most older CPUs do not support the NX or SSE requirements of Win 8.x which the boot images created using the ADK 8.x are based upon.
Assuming this is the case, you must install SP1 CU3 or R2 and then you can import (and be fully supported) a down-level boot image that will support your CPU.
Windows 2012 r2 error code 0x000000c4
Сообщения: 2382
Благодарности: 330
Требования к системе
Процессор. 1 ГГц* или выше с поддержкой PAE, NX и SSE2
Win 8.1х32 без проблем ставил и на более ранние D 540 2 Гига озу
Либо воткните внешнюю видео если у вас встроенная, либо добавить ОЗУ.
Как вариант установите ОСь на другом железе. Перенесите Хард в старый комп. Восьмёрка должна подняться. Возможна засада от дров конкретной материнки. Я свои ПК на Асусах P5xxxx собирал.
——-
Я здесь не для того чтобы учить, а для того чтоб учиться.
Последний раз редактировалось Kirill_S, 28-08-2017 в 14:11 .
Как вариант установите ОСь на другом железе. Перенесите Хард в старый комп. Восьмёрка должна подняться. » |
Тоже пробовал — не удалось.
Вероятно, ЦПУ припятствует установке Windows 8.1 x64
Подозреваю, что Windows 7 x64 встанет, но меня интересовала именно 8.1. 10-ку, пожалуй, пробовать даже бесмысленно. » |
Обновлял тут один ноутбук с предустановленной Win-8 (не 8.1), впаренный покупательнице услужливым продаваном за месяц до полного окончания поддержки этой операционки.
Win-8.1 не вставала ни обновлением, ни установкой с нуля.
Win-7 не вставала.
Win-10 встала не поперхнувшись.
Reported by: | birdie | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.14 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
My host is: Linux 3.9 i686 PAE, CentOS 6.4, 16GB RAM
Attachments
Change History
Changed 7 years ago by birdie
Changed 7 years ago by birdie
VM logs, settings and storage
comment:1 Changed 7 years ago by birdie
This bug affects Windows 8.1 preview installation as well.
comment:2 Changed 7 years ago by birdie
The solution is to run this command:
Hopefully the next VBox release will have this instruction enabled by default.
comment:3 Changed 7 years ago by frank
comment:4 follow-up: ↓ 6 Changed 7 years ago by gernst
The solution with CMPXCHG16B is NOT working for me in Windows 8.1 preview. Still the same error message.
comment:5 Changed 7 years ago by Piotr Orwat
comment:6 in reply to: ↑ 4 Changed 7 years ago by birdie
The solution with CMPXCHG16B is NOT working for me in Windows 8.1 preview. Still the same error message.
What is your CPU? Some old 64bit AMD CPUs don’t have this instruction.
comment:7 follow-up: ↓ 8 Changed 7 years ago by frank
A VBox.log file would include information about his CPU.
comment:8 in reply to: ↑ 7 Changed 7 years ago by birdie
A VBox.log file would include information about his CPU.
gernst hasn’t provided a log file.
comment:9 follow-up: ↓ 10 Changed 7 years ago by frank
Therefore I wrote ‘would’ 🙂
comment:10 in reply to: ↑ 9 Changed 7 years ago by birdie
My bad 🙂 I haven’t noticed «would» 🙂
Changed 7 years ago by gernst
comment:11 Changed 7 years ago by gernst
I tried also global, but still not working. Logfile attached.
comment:12 Changed 7 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
Fix included in VBox 4.2.16. Make sure to select the Windows 8.1 OS type.
comment:13 follow-up: ↓ 14 Changed 7 years ago by gernst
VBox 4.2.16 installed, machine for Windows 8.1 newly created. Tried Windows 8.1 and Windows 8.1 (64bit), still the same error. Nothing has changed. It looks like no one has read my log file. My CPU is a Intel Core 2 Quad Q9650. Let me know if someone needs a new log file.
comment:14 in reply to: ↑ 13 Changed 7 years ago by birdie
VBox 4.2.16 installed, machine for Windows 8.1 newly created. Tried Windows 8.1 and Windows 8.1 (64bit), still the same error. Nothing has changed. It looks like no one has read my log file. My CPU is a Intel Core 2 Quad Q9650. Let me know if someone needs a new log file.
Create a new Windows 8.1 guest in VBox 4.2.16 and append its log here.
(If you have the same error as I did I have reasons to believe that the CMPXCHG16B instruction is disabled somewhere on your PC — I cannot imagine how).
Changed 7 years ago by gernst
comment:15 Changed 7 years ago by gernst
Here is my new log file. As I have written in my previous post I have created everything totally new from ground up. That means I have all Windows 8.1 guest removed and newly created. But still the same error when I start from CD to install. The CMPXCHG16B instruction is enabled, as shown in the log file.
comment:16 Changed 7 years ago by yuhong
«WARNING: Can’t turn on NX/XD when the host doesn’t support it!!»
Check your BIOS and make sure this is enabled.
comment:17 Changed 7 years ago by gernst
Thats it. NX/xd was not enabled. Thanks.
comment:18 Changed 7 years ago by yuhong
I hope CMPXCHG16B will be enabled regardless of the OS setting in the future.
comment:19 Changed 6 years ago by ConcreteGannet
Same problem with VirtualBox 4.3.14 and Intel i7 processor. setextradata fixed it for me too. Why is the fix not standard in VirtualBox by now?