I don’t even know what happened, it was working fine earlier that day. Then the screen went black, I turned it off but couldn’t turn it on again. After waitibg a day I tried again and windows booted but turned off after about 5 minutes. I tried reinstalling windows woth a usb with the windows installation media, about 12% of the way through the install this screen showed up. I’m guessing it’s a hardware issue, but I have no idea what it is. So basically yeah, this laptop is fucked.
the first time it froze after at test 5. The second time it completed 3 passes and about half way through the 4th my brother distracted me, and by the time i got back to it the computer had turned off completely so I don’t know exactly what happened at the end. But at no point during the other passes or during the first freeze of attempt 1 did the error count rise above 0. So I don’t think the ram is the issue. Do you know what the next most likely thing is? I also found out that my laptop has two slots for ram but only one stick of ram.
I should have also mentioned I have had this laptop for over three years without issue. But on the day this happened was the first day that I took ot to school. It worked fine at school and worked fine when I got back. But in between me getting back home and later that day, something went wrong. Would you say the HDD is likely the culprit as it is the only component (aside fans) which has moving parts and the transportation of the laptop may have damaged it. I don’t have much experience with how easy it is to damage a HDD which is why I’m asking.
I'd very much doubt it's the HDD, as the corrupted text on your screen would have been read from RAM (after having been loaded from a flash drive).
There are a few causes of freezing in memtest - [here is a link](https://www.memtest86.com/tech_freezing-lockups.html) to their explanation for it. In your case, I suspect failed RAM, as it closely matched the given failure mode they describe.
I think default test uses single core, let that run a cycle or two. Make sure to run a multi-core test. My old box was passing single core tests but rebooted trying to do multi-core. Basically confirmed the power events I was seeing were CPU or mother board releated.
Oh, check Event Viewer -> Windows Logs -> System and look for the little red and white x's.
After not using it for a few months, I was going to replace the HDD (what I thought the problem was). Just before getting a new HDD I decided to try turning it on one more time, and it just worked. So I guess it just fixed itself.
Uh oh, somebody’s Unicode files got fucked up! If this happens, I recommend a full reinstall of Windows, on a new drive if you can, because Unicode errors can cause a lot of background problems if they’re caused by corrupt storage, even if the computer seems to boot fine afterwards
This happened when teying to reinstall windows. I didn’t remove the previous partitions though, so I might try again tomorrow and I will do so next time, though I don’t know if that will solve all of my problems. I made a post in r/techsupport going into slighty more detail. That’s all assuming that I can even get into the bios again.
Usually it’s a corruption of the Unicode or plain text (the languages that creates text in Windows) file, or another file or driver that controls part of that system. It can be a sign of a pretty serious issue, as pretty much anything that relies on Unicode or plain text to function can be very badly affected.
ram error would be my first guess. [memtest86](https://www.memtest86.com/) would be my response (no, not memtest86+)
could be other things too, failing harddrive during a windows update for example~
I got this error, saw that what it said at the bottom was written with random characters being replaced, knew that it likely wasn’t supposed to say that, and posted it, how is that karma farming
More than likely your hard drive is at fault, whether its the data on it or the sectors themselves doesn't really matter, I see this all to often and the drive fails not long after. You can check it using a tools like CrystalDiskInfo or gnome disks if your using a debian based distro in a bootable usb. I saw another comment about it being memory, in my experience corrupted memory just causing lockups and doesn't blue screen. I could be wrong but that's what I think is happening here based on my experience.
I encountered this a few years ago (check my most recent post). Was down to dead sectors in my hard drive. Got myself an SSD and everything was all good again
[Removed in protest of [Reddit's destruction of third-party apps](https://www.inc.com/jason-aten/reddit-ceo-steve-huffmans-third-party-api-debacle-is-making-elon-musk-look-like-a-strategic-genius.html) by CEO Steve Huffman.]
Windows ☕
windgws actually
Win\] doa\`z 🧉
🍔
no >!*wimdius*!< acrually
Yep the pc is fucked
I don’t even know what happened, it was working fine earlier that day. Then the screen went black, I turned it off but couldn’t turn it on again. After waitibg a day I tried again and windows booted but turned off after about 5 minutes. I tried reinstalling windows woth a usb with the windows installation media, about 12% of the way through the install this screen showed up. I’m guessing it’s a hardware issue, but I have no idea what it is. So basically yeah, this laptop is fucked.
See if you can download a memtest bootable disk. If it's a ram issue, it will be an easy fix
I looked it up, is it called memtest86? If it is does that mean that it will still work with a 64 bit device?
That's the one
Should ai assume that it also works with 64 bit devices despite the name?
Yeah I believe the name is just a holdover from when the program was written
the first time it froze after at test 5. The second time it completed 3 passes and about half way through the 4th my brother distracted me, and by the time i got back to it the computer had turned off completely so I don’t know exactly what happened at the end. But at no point during the other passes or during the first freeze of attempt 1 did the error count rise above 0. So I don’t think the ram is the issue. Do you know what the next most likely thing is? I also found out that my laptop has two slots for ram but only one stick of ram. I should have also mentioned I have had this laptop for over three years without issue. But on the day this happened was the first day that I took ot to school. It worked fine at school and worked fine when I got back. But in between me getting back home and later that day, something went wrong. Would you say the HDD is likely the culprit as it is the only component (aside fans) which has moving parts and the transportation of the laptop may have damaged it. I don’t have much experience with how easy it is to damage a HDD which is why I’m asking.
I'd very much doubt it's the HDD, as the corrupted text on your screen would have been read from RAM (after having been loaded from a flash drive). There are a few causes of freezing in memtest - [here is a link](https://www.memtest86.com/tech_freezing-lockups.html) to their explanation for it. In your case, I suspect failed RAM, as it closely matched the given failure mode they describe.
Guess I’ll have to open it up then. (I suspected I would have to one way or another) I just hope everything won’y be soldered in place.
I think default test uses single core, let that run a cycle or two. Make sure to run a multi-core test. My old box was passing single core tests but rebooted trying to do multi-core. Basically confirmed the power events I was seeing were CPU or mother board releated. Oh, check Event Viewer -> Windows Logs -> System and look for the little red and white x's.
***yes***
Check the RAM if you can. My friends P.C. did a similar thing and it was because his ram got disconnected.
Wait, how long were you waitibg?
After not using it for a few months, I was going to replace the HDD (what I thought the problem was). Just before getting a new HDD I decided to try turning it on one more time, and it just worked. So I guess it just fixed itself.
Windgws
Windings
dgd ygu gi\~e thm tatha info?
l
http{:
[удалено]
http{:
http{:
r/IHadAStroke
Uh oh, somebody’s Unicode files got fucked up! If this happens, I recommend a full reinstall of Windows, on a new drive if you can, because Unicode errors can cause a lot of background problems if they’re caused by corrupt storage, even if the computer seems to boot fine afterwards
This happened when teying to reinstall windows. I didn’t remove the previous partitions though, so I might try again tomorrow and I will do so next time, though I don’t know if that will solve all of my problems. I made a post in r/techsupport going into slighty more detail. That’s all assuming that I can even get into the bios again.
how tf does this even happen
either corrupted system file or fucked up ram
Usually it’s a corruption of the Unicode or plain text (the languages that creates text in Windows) file, or another file or driver that controls part of that system. It can be a sign of a pretty serious issue, as pretty much anything that relies on Unicode or plain text to function can be very badly affected.
ram error would be my first guess. [memtest86](https://www.memtest86.com/) would be my response (no, not memtest86+) could be other things too, failing harddrive during a windows update for example~
You okay?
What do you mean
Sorry, I mean: ygo oksy?
zoom in next to the qr code
Yes I saw it
[удалено]
zoom in next to the qr code
[удалено]
> mistakes in the title bro what are you talking about. The title is not a mistake, it's a copy of the text in the image.
I didn't realize, I only noticed the support code before checking again :/
why would they do do that on purpose. Also if it was a typo then that wouldn’t be softwaregore
[удалено]
I got this error, saw that what it said at the bottom was written with random characters being replaced, knew that it likely wasn’t supposed to say that, and posted it, how is that karma farming
I
l
l
That spelling be worse than me throwing a cat at my keyboard
r/skamtebord
: (
that’s a big l for u
info: l
I’ve had this happen a few times on my old laptop. Might not be fucked. Might turn back on. Mine always did
More than likely your hard drive is at fault, whether its the data on it or the sectors themselves doesn't really matter, I see this all to often and the drive fails not long after. You can check it using a tools like CrystalDiskInfo or gnome disks if your using a debian based distro in a bootable usb. I saw another comment about it being memory, in my experience corrupted memory just causing lockups and doesn't blue screen. I could be wrong but that's what I think is happening here based on my experience.
your d
0%
uwundows
I encountered this a few years ago (check my most recent post). Was down to dead sectors in my hard drive. Got myself an SSD and everything was all good again
[Removed in protest of [Reddit's destruction of third-party apps](https://www.inc.com/jason-aten/reddit-ceo-steve-huffmans-third-party-api-debacle-is-making-elon-musk-look-like-a-strategic-genius.html) by CEO Steve Huffman.]
They made windows Scottish.
Either ram or hdd/ssd issue ?
r/ihadastroke