F5F Stay Refreshed Software Operating Systems The system stops unexpectedly after applying an update.

The system stops unexpectedly after applying an update.

The system stops unexpectedly after applying an update.

P
Porkbelly
Junior Member
6
10-19-2016, 12:01 PM
#1
P
Porkbelly
10-19-2016, 12:01 PM #1

D
drewnecros
Junior Member
28
10-20-2016, 02:23 PM
#2
You're facing a significant hardware issue. It could be an SSD, a damaged SATA cable, or possibly a faulty RAM causing Windows to display a BSOD screen. The CPU might also be malfunctioning, leading to strange behavior. Most likely, the problem lies with your SSD. You might want to try swapping in a different drive—such as an unused HDD—and install a fresh Windows system to see if it resolves the issue. Before proceeding with a return or replacement, consider updating the SATA controller drivers, as a serious bug could be the cause.
D
drewnecros
10-20-2016, 02:23 PM #2

You're facing a significant hardware issue. It could be an SSD, a damaged SATA cable, or possibly a faulty RAM causing Windows to display a BSOD screen. The CPU might also be malfunctioning, leading to strange behavior. Most likely, the problem lies with your SSD. You might want to try swapping in a different drive—such as an unused HDD—and install a fresh Windows system to see if it resolves the issue. Before proceeding with a return or replacement, consider updating the SATA controller drivers, as a serious bug could be the cause.

_
___21pilots___
Junior Member
13
10-26-2016, 12:02 AM
#3
Thanks for the update, I'll switch to another cable since it's easier. The new drive should be simpler to locate. I'm planning to mention that my system has a RAID 1 array with two WD green 2TB drives built into the motherboard's RAID chip. Could the raid hardware on the board be interfering with SATA connections? In any case, the RAID setup is functioning perfectly. The RAM, motherboard, power supply, and CPU are all fairly old components, but I ran a memtest86 recently and got no errors. If the SSD isn't the issue, that would be the next component to check.
_
___21pilots___
10-26-2016, 12:02 AM #3

Thanks for the update, I'll switch to another cable since it's easier. The new drive should be simpler to locate. I'm planning to mention that my system has a RAID 1 array with two WD green 2TB drives built into the motherboard's RAID chip. Could the raid hardware on the board be interfering with SATA connections? In any case, the RAID setup is functioning perfectly. The RAM, motherboard, power supply, and CPU are all fairly old components, but I ran a memtest86 recently and got no errors. If the SSD isn't the issue, that would be the next component to check.

T
TightMrKI113r
Junior Member
2
11-16-2016, 01:56 PM
#4
It might be a RAID configuration issue. Possible reasons include faulty RAID drivers (ensure you're using the newest versions) or the RAID controller not accepting your drives. Keep in mind my understanding of RAID is quite basic.
T
TightMrKI113r
11-16-2016, 01:56 PM #4

It might be a RAID configuration issue. Possible reasons include faulty RAID drivers (ensure you're using the newest versions) or the RAID controller not accepting your drives. Keep in mind my understanding of RAID is quite basic.