How is this possible?

>>61454670
Install Gentoo

>>61454678
You have to be some mad nigger to start wandows

>>61454670
Shit happens, you could edit that manually with cheatengine if you tried and the result would be the same, it's really just a message box, the variables are untouched ("minutes" and the number "2"). I don't know what they did to get this but they'd better undo whatever it was that they did because they're really lucky that only the message box was affected.

>>61454678

>problem$
>Ngrmadly

Is this Windows HipHop Edition?

faulty ram

bit flippin mad yo

>>61454735
That's exactly the question though. How can only the message box be affected? It just seems really unlikely if you have faulty RAM.

>>61454881
>How can only the message box be affected?
Damn sure all these systems froze at some point

>>61454881
corrupted bits

>>61454750
>>61454750
>>61454750
This, your memory is fucked anon, simple

>>61454735
>>61454750
>>61455218
I think knows that. The question was why only the message box gets corrupted while everything else still works.

>>61455241
Because when ram goes bad it's not the whole thing that goes bad, usually it's just a single chip (on a stick where you can have up to 16 chips)

I'd guess the text in the message box is being stored on the faulty chip, while the rest of the OS is occupying the other chips instead.

>>61455241
Maybe it's a virus, like one of thoose oldschool ones that instead of stealing passwords or asking for ransom just did random shit for lulz like corrupting messages or wiping your hard drive.

>>61454670
Memory corruption. Either faulty memory or timing is faulty through OC or something.

>>61454670
you should probatly install gentoo anon

Let's organize this.
1. Fucked up ram, run a diagnostics program in the bios.
2. Overclocking messed the timing, underclock to stock.
3. Pirate windows, install gentoo.

>>61455293
Isn't that really unlikely though? Especially after running the system for some time?

>>61455541
Does saging even work any more?

>>61455688
aye

File: 1422572753725.png (23KB, 382x276px) Image search: [Google]

23KB, 382x276px

>>61454678

>>61454670
>Windows
Found your problem

File: sumtin habben.jpg (41KB, 474x267px) Image search: [Google]

41KB, 474x267px

>>61454670
>Winshit
Literally made by Pajeets, that's how.

>>61454881
because that was the location in memory that was corrupted

>>61454670
Your ram is fucked boi.
Run MemTest86

>>61455241
You were lucky I guess.

>>61457800
lmao

>>61455541
announcing sage isn't allowed here

>>61454670

Needs more dedotated wam.

>>61454670
If I remember correct, a considerable number of Windows text segments are stored all in roughly the same place.
Makes it easier to translate to other languages.
Language files might be fucked.