Very frequent restarts on new PC

I just got a new PC and it's giving me the gift of troubleshooting

It's device 1 in my profile: a low-spec refurbished Acer desktop, sourced from Acer Aspire XC - Desktop Intel Celeron J4125 2GHz 4GB RAM 256GB SSD W10H 840226623863 | eBay, Acer Aspire XC - Desktop Intel Celeron J4125 2GHz 4GB RAM 256GB SSD. I added another 4GB RAM (matching the factory issue), a 1TB SSD for data storage and did a clean install of Win10 Pro (ISO via media creation tool). Winver = 21H2 OS Build 19044.2075.

Intention is to run this as a headless home server for low power, lightweight things and RDP into it when needed, or at least it would be if it was stable.

I've been experiencing very frequent reboots, probably on the order of every 15-30 minutes. BlueScreenView notes them all as sourcing from ntkrnl.exe. I assumed this meant memory, but I ran the Windows memory test and then memtest86+ for 24 passes with no issues found. I've finally had the machine up long enough to run through the DISM restorehealth and SFC /scannow commands. The reboots persist. I'm not sure why only 5 minidumps get saved, but event viewer has many more reboots in the history.

Attached to this post are the results from the log collector, a sample export from the event viewer, BlueScreenView, and some other minidumps.

Can you help recommend steps to take? I can do another clean install with a fresh USB image, however I'm not sure how to figure out if this is a hardware issue requiring RMA or software issue that I can resolve. Ideally I wouldn't have to deal with shipping a machine back. I tried digging into the .dmp files with WinDBG Preview and got nowhere fast with that. Appreciate your help and advice.

Is the memory you added compatible with your computer? If you remove the newly added memory from the computer, do the problems persist?

MrPepka said:

Is the memory you added compatible with your computer? If you remove the newly added memory from the computer, do the problems persist?

I used the same exact same model (and brand) as the OEM provided - Samsung DDR4 PC4-2666V-SC0-11 (CA68). And yes, problems persisted. Will try again, though. Might as well re-seat the factory stick just to see if there's a loose connection or something.

Could faulty memory go through 24 passes of memtest without a blip?

Swapped out the additional memory and checked in different slots, improved to 8 hours of uptime. So assuming that the extra memory is bad, but somehow passing tests. But 8 hours uptime is still not great...

New error: Bugcheck 0x00000139 Parameter 3

KERNEL_SECURITY_CHECK_FAILURE (139) --> A LIST_ENTRY was corrupted (for example, a double remove). For more information, see the following Cause section.

dalchina said:

First, eliminate the O/S from the scenario.

Either boot from a live boot disk, which you can create for free (Bob Omb's, Hiren's... ) ...Google
or you can try simply booting from a Win 10 install disk- without changing anything.

Just leave the PC on and see if it reboots.

If it does, there's most likely a hardware issue.

It went for 24 passes of a memtest if that's sufficient. But that included the memory that seems to have been causing the fault so got me on that one... Will try another live disk to see if there's a difference. That said could be a network driver / hardware issue or something in a device that doesn't get utilized in one of the live O/S's.

- - - Updated - - -

Now down to daily reboots, this one is another new error at least (below), but am unable to identify it to a specific driver or piece of hardware (as usual). Will see how long Hiren's stays up on my ventoy USB.

---

IRQL_NOT_LESS_OR_EQUAL with bugcheck code 0x0000000a

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000001000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8046c41ce44, address which referenced memory

- - - Updated - - -

weirdly my last reply is going to updated, but perhaps a forum feature... and confirmed it is :)

Marking this as solved, now up for 3 days running, that's good enough for me. Appreciate the help on this.

The opening post reported BSOD in a refurbished desktop.

The bugchecks in the collected logs were:

4E
7E
1A
1E
E6
BE
50
A


Did the computer come with all of the installed drives?

One of the installed drives has one or more bad block(s).


New PCs should not have BSOD.

For new PC the computer manufacturer is responsible for the hardware and the preinstalled operating system.

The BSOD bugchecks are consistent with either overclocking, incompatible or malfunctioning hardware.

It is best that you contact the vendor for a Return Merchandise Authorization (RMA).



The Celeron J4125 CPU supports RAM up to 2400.

When the log collector ran the speed was recorded at 2666.

Make sure that the RAM is not overclocked.

Turn off XMP.


Run HD Tune (free or trial version) (all drives)
HD Tune website
Post images or share links for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

Run Sea Tools for Windows (all drives)
https://www.seagate.com/files/www-co...sInstaller.exe
https://www.seagate.com/support/seat...or_windows.pdf
Post images or share links into this thread for the Long generic test



------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 208.3 GB
Total Space: 243.6 GB
File System: NTFS
Model: HFM256GD3JX016N

Drive: D:
Free Space: 953.7 GB
Total Space: 953.9 GB
File System: NTFS
Model: CT1000MX500SSD1