Error codes on startup

[RDeni2]

I will keep this short. I did a rebuild of a computer. My motherboard was failing. The hard drive was one of the of the parts reused, the motherboard and processor was not. It boots into Win 7 most of the time, but USB's don't work. ASUS says it is because it is a Win 10 board and I have Win 7 on it. I called before I bought any parts and did the rebuild. They said it was no problem, I would just need a few drivers. They didn't tell me one of them was the USB driver. I have tried multiple versions of Linux on a bootable USB to get access to the computer. It worked once, but not very well. Now all I get is a screen of error codes. Online searches mainly say they are codes from the processor. I have no clue what they mean. Any ideas?

Thank you

[0.105075] mce: [Hardware Error]: CPU 7: Machine Check: 0 Bank 0: b200000000 070005

[0.105079] mce: [Hardware Error): TSC 0

[0.105081] mce: [Hardware Errorl: PROCESSOR 0:50654 TIME 15037969448 SOCKET 0 APIC e microcode 2000026

[0.193989] ACPI: [PCCT:Ox01] Invalid zero length

[0.193993] ACPI: [PCCT:0x02] Invalid zero length

[0.193995] Error parsing PCC subspaces from PCCT

[0.278176] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)

[0.278180] ACPI Error: Method parse/execution failed [\SHAD._STA] (Mode ffff 8e85be549e10), AE_NOT_FOUND (20160930/psparse-543)

[0.278190] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT,FOUND (20160930/psargs-359)

[0.278192] ACPI Error: Method parse/execution failed [\SHAD._STA] (Mode ffff 8e85be549e10), AE_NOT_FOUND (20160930/psparse-543)

[0.303521] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT,FOUND (20160930/psargs-359)

[0.303525] ACPI Error: Method parse/execution failed [\SHAD._STA] (Mode ffff 8e85be549e10), AE_NOT_FOUND (20160930/psparse-543)

[0.342033] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT,FOUND (20160930/psargs-359)

[0.342037] ACPI Error: Method parse/execution failed [\SHAD._STA] (Mode ffff 8e85be549e10), AE_NOT_FOUND (20160930/psparse-543)

OS: Windows 7 Home Premium

Processor: I7-7820X 8-core, 16-thread @ 3.6GHz

Processor cooler: Corsair Hydro Series H105 Extreme Performance 240mm fan

Motherboard: ASUS TUF X299 Mark 1

OS HD: Crucial M4 64GB SSD

Storage HD: Western Digital 750GB

Ram: 32GB 4-channel G.Skill TridentZ Series DDR4@3200MHz

GPU: EVGA GeForce GTX 1080 Ti SC2 Hybrid Gaming

PSU: Antec EarthWatts Series EA-750W ATX12V v2.3

[n_scott_pearson]

Only Windows 10 x64 is fully supported on this platform. In general, drivers for Windows 7 are not available (there may be the odd one that happens to also support Windows 7, but these are few).

Sorry,

...S

[RDeni2]

Actually that is not true. ASUS, and I think only ASUS, supports all of their boards on Win 7. That is why I stated ASUS said I need to install drivers. That is also why I stated I was trying Linux to access the computer to install the drivers. I already have them. Just FYI for anyone doing a similar build, ASUS has the following drivers for Win 7 on the new LGA 2066 boards: BIOS, Realtek audio driver, LAN driver, USB driver, Chipset driver, SATA driver, and a driver for their Thermal Radar 3 utility. They also support Win 8.1 and both 7 and 8.1 in 32 and 64 bit.

I did not know any of this either until I was trying to repair my computer and it seemed all of both the good and affordable processors were LGA 2066 ones. After scanning a bunch of chatrooms, I read about this. I was skeptical, so I verified it with ASUS. I think it is good because if LGA 2066 boards are the future, we would all be forced into Win 10 whether we wanted to or not.

Any clue on there error codes?

[TFörs]

Do you still have the problem?

I get the same errors with a MSI X299 Raider board and a i7-7820X.

If you want to boot a linux system. you have to add acpi=off to the boot options.

Follow the link: https://askubuntu.com/questions/160036/how-do-i-disable-acpi-when-booting installation - How do I disable ACPI when booting? - Ask Ubuntu

This is only a temporary work around as this disables hyperthreading.

So far I could not find any idea on the reason for the errors. It might a bug in the Boards UEFI.