1. To check/confirm whether it's a hardware problem or not...
(a) Boot the PC using a bootable/live Linux CD.
(b) The one I know is Puppy_Linux.
It's small, and therefore easy and fast to download and to burn the CD.
It loads from the CD into RAM and runs totally in RAM.
Doesn't use [the boot arrangements, or load any software from] the internal HDD at all, so if that was the cause of the problem, the problem wouldn't be in effect.
Good idea to disconnect the internal HDD when testing with Puppy_Linux.
(c)
If the problem is there in Puppy_Linux, then it's probably a hardware problem that involves at least 1 item other than the internal HDD.
(d)
If the problem is not present in Puppy_Linux, then the main suspects would include...
The internal HDD...
And/or...
The Windows software.
But NOT any other items of hardware...
(e)
The Lupu-528 thread.
And...
lupu-528.iso
md5sum =
f04ec9ef3540be8e50d0a24c512e1309 lupu-528.iso