memory_corruption BSOD

B

bascotie

Well-known member
Joined
Feb 14, 2021
Posts
206
Hi guys,

Working on a computer that has been getting stuck during boot (black screen, windows 10 loading circle but never goes anywhere)

It does seem to boot if you restart it manually. I have collected and examined the logs, which say there have been 4 crashes (I personally witnessed 1, and it happened while shutting down windows).

I've checked drive health
I'm currently updating from Win 10 2004 to 20H2

Attached are logs, just wondering if you guys can spot anything glaring? I run the built in Windows 10 memory test and it says it passed. I could not run memtest since it seems not to support this legacy boot type (no UEFI available).

I'm gonna keep at it, but I also like to see what the professionals say about the logs :)
 

Attachments

I would suggest running MemTest86 first of all. It shouldn't matter if the system is UEFI-based or not.
 
x BlueRobot said:
I would suggest running MemTest86 first of all. It shouldn't matter if the system is UEFI-based or not.
Click to expand...
When I try to run memtest, I get a blinking cursor in the top left corner with a black screen.

Just FYI, once the system is up and running, it seems to be fine. I've had it on for 24 hours now running tronscript and attempting updates with no issue.

It seems to me like each time it gets stuck on boot (loading circle with black screen), after a couple reboots, when it comes back up it says updates failed. I'm currently trying to get it on 20H2 but it's getting stuck so I'm going through tronscript which does various repairs and checks (dism , sfc, etc)
 
Got memtest running, it does look like errors are coming up immediately. I'm going to start testing stick by stick and also rule out the slots. Thanks guys
 
Appreciate the help. I'm narrowing it down now and it's been a little tricky. Sometimes I can run an hour no problems, but if I leave it long enough, I usually see memory errors so now I've narrowed it down to the last stick and am gonna run memtest for at least 2-3 hours to see if that's the culprit
 
@x BlueRobot

I'm starting to think the issue here is CPU or Motherboard, here's why:

1) There are 4 ram sticks in this machine
2) If I test each one individually, they finish 1 full pass without error
3) If I test all of them together, I usually get an error within one full pass, or shortly after the first pass

What does that sound like to you?
 
An update for anyone wondering:

Looks like there were a couple problems with this old machine

1) The memory issue, which I finally narrowed down and removed the offending stick (I had to test different configurations for about 2-3 hours each to get an accurate idea of it)

2) The boot issue. It no longer BSOD's after removing the offending ram stick, BUT if you shut down, it would hang up on next boot. The solution was to turn off FAST BOOT (windows+r -> type in powercfg.cpl -> click ok -> click link on left to "choose what power buttons does" and turn it off from there.

Consistently, I would have issues booting if I did a full shutdown, then I'd have to hit the restart button and it would boot. After changing that, I tested a few full shutdown/startup cycles with no issue.

Thanks again guys
 
Generally speaking, even when testing, you need to run the maximum number of passes it will allow, since each pass runs a number of different tests. I've seen plenty of occasions where a RAM stick would only fail on the last test.

bascotie said:
BUT if you shut down, it would hang up on next boot. The solution was to turn off FAST BOOT (windows+r -> type in powercfg.cpl -> click ok -> click link on left to "choose what power buttons does" and turn it off from there.
Click to expand...
That can be a "sticky" point for some older machines, especially those who rely on drivers which weren't designed with fast startup in mind.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top