[22h2] PC just "stops"

[neonetman]

I've got a strange issue with one PC on the network. It has started booting up, then a few seconds after completing the boot, the keyboard stops working, light on the mouse goes out, display goes off, and we lose the ability to ping it.

 

It works fine right through a re-install (using mecm), and works fine in safe mode, yet on a normal boot this behaviour occurs. There is absolutely nothing in the event log relating to an issue, yet it re-occurs even after a re-install of windows.

 

It is identical hardware to all other machines in the room, and an identical software image. A memtest shows no hardware errors

 

Any ideas?

[Rob_D]

Can you build it without any third-party drivers?

If that works okay then you could leave it at that, or start adding in the drivers in the vendor/updated drivers until it stops working.

[Oaktech]

Have you tried physically swapping the ram & storage with another device? Edited October 11, 2023 by Oaktech
Cannot brain

[Dos_Box]

Does Event Viewer report anything?

[neonetman]

Event viewer shows nothing related at all. Tried moving NVMe to another identical PC and it works fine there, so we're contacting our provider to log a warranty claim

[Oaktech]

Event viewer shows nothing related at all. Tried moving NVMe to another identical PC and it works fine there, so we're contacting our provider to log a warranty claim

 

Can you humour me and try swapping the ram out too?

[neonetman]

I've packed this machine up to send back now, however we did boot a Memtest86+ USB and ran a memory test, with no issues found

[Domino]

leftfield option - I saw this once years ago. machine would totally lock up, took it out to a test bench, worked fine. Back to where it was, same issue. Tried swapping everything I could.

 

...eventually found the culprit, the USB mouse. Somehow it was malfunctioning so badly it caused the entire system to lock up. Never seen it since, but always stuck in my mind

[neonetman]

We brought it back to the testbench, and ran it on different cables and peripherals with the same issue

[MrEprise]

I had a PC fairly recently where it was doing much of the same, fine outside of Windows but would soon freeze once in Windows. Turned out that the CPU had blown part of its circuitry (due to a bent pin in the socket - it was working fine for ages but I suspect vibrations may have caused it to move) and the PC was fine if it ran on a single core which it generally does outside of any major OS, but as soon as it tried to engage the other 3 (i.e. in Windows) it'd freeze.

 

As a test I set the BIOS to only allow the use of a single core and once in Windows, it ran fine albeit a considerable bit slower than normal which is to be expected.

[aarono]

Aliens!

 

Or some sort of faulty hardware?

[neonetman]

Only thing we could surmise was a faulty device on the motherboard, which only became "active" when the relevant driver was installed - hence the Windows build and safe mode are both fine but normal boot isn't

[Julian]

Have you checked for a broken USB port, with the contacts shorting out I have had some coomputers where that happened, and then the BIOS shut the machine down due to USB overcurrent.