PC blue screen issue

ChibiWolf39
Senior Member

491

11-04-2016, 12:36 AM

This article is about a friend's computer that keeps blue-screening. He replaced his SSD, assuming that was the problem. I gave him a bootable Windows USB, but shortly after installation, it started again. I suspect a faulty motherboard, but I need someone more experienced to verify this. I've been trying to fix it remotely for months since Best Buy mishandled the repair.

ChibiWolf39

11-04-2016, 12:36 AM #1

braadworstbrr
Member

11-04-2016, 12:42 AM

Search for issues in the system. Identify critical errors. Retrieve details about each error.

braadworstbrr

11-04-2016, 12:42 AM #2

Search for issues in the system. Identify critical errors. Retrieve details about each error.

keslcg
Member

166

11-04-2016, 01:29 AM

Use a tool like testmem86 to verify memory functionality

keslcg

11-04-2016, 01:29 AM #3

Use a tool like testmem86 to verify memory functionality

saxonsonic
Member

11-04-2016, 03:29 AM

The laptop is brand new.

saxonsonic

11-04-2016, 03:29 AM #4

The laptop is brand new.

SmoldearDash
Junior Member

11-04-2016, 11:01 AM

Keep going, you can achieve this quickly using a Testmem5 or take your time with Memtest86.

SmoldearDash

11-04-2016, 11:01 AM #5

Keep going, you can achieve this quickly using a Testmem5 or take your time with Memtest86.

chrisnoble
Member

103

11-04-2016, 07:23 PM

This indicates the issue is related to the attempt to execute a non-executable memory.

chrisnoble

11-04-2016, 07:23 PM #6

This indicates the issue is related to the attempt to execute a non-executable memory.

Synonikun
Junior Member

11-06-2016, 12:48 PM

The RAM configuration might cause inconsistent performance, even for new units. This is confirmed by a memory-related error code. However, potentially faulty drivers could also be responsible.

Synonikun

11-06-2016, 12:48 PM #7

The RAM configuration might cause inconsistent performance, even for new units. This is confirmed by a memory-related error code. However, potentially faulty drivers could also be responsible.

Kitten645321
Member

181

11-26-2016, 11:12 AM

I discovered a single driver affected by corruption related to the AMD chipset. Was this the root issue from the start?

Kitten645321

11-26-2016, 11:12 AM #8

I discovered a single driver affected by corruption related to the AMD chipset. Was this the root issue from the start?