Thread replies: 8
Thread images: 3
Thread images: 3
File: tRL5v64.jpg (70KB, 600x800px) Image search:
[Google]
70KB, 600x800px
I think I just broke my laptop. I punched it while playing CoD 4.
I turn it on, shows windows logo and it blue screens for a second or so. Its an old 32-bit Xp so Im not putting any more money into it.
Something wrong with the hardware. What can I do without buying new crap?
>>
>>83223
>I punched it while playing CoD 4
>What can I do without buying new crap?
You could grow up for starters.
>>
>>83226
Thank you for contribootin
>>
>>83233
No problem.
>>
File: 30d00b1ac97748dd0d1e6d8bf91297308f4b45c7788300bded011e60dd92861a[1].jpg (59KB, 551x549px) Image search:
[Google]
![30d00b1ac97748dd0d1e6d8bf91297308f4b45c7788300bded011e60dd92861a[1].jpg](https://i.imgur.com/nUbeGXB.jpg "30d00b1ac97748dd0d1e6d8bf91297308f4b45c7788300bded011e60dd92861a[1]")
59KB, 551x549px
>>83223
>Something wrong with the hardware. What can I do without buying new hardware?
>>
if something was wrong with the hardware, it wouldn't turn on and you won't see anything...
and how were you playing that on XP in the first place?
>>
File: maxresdefault[1].jpg (91KB, 1280x720px) Image search:
[Google]
![maxresdefault[1].jpg](https://i.imgur.com/iBvFKso.jpg "maxresdefault[1]")
91KB, 1280x720px
>>83252
>if something was wrong with the hardware that makes it turn on, it wouldn't turn on and you won't see anything...
FTFY
OP's head-crashed his hard disk. OP should really go buy a new one, ghost his old one onto it, and then repair whatever files got damaged by his juvenile behaviour, which he can do by noting the offset of every badsector reported during copy, and then looking them up against the NTFS inodes.
But he's not going to do that, because OP's the kinda guy that plays CoD and punches laptops.
>>
>>83223
Serves you right fagit
Thread posts: 8
Thread images: 3
Thread images: 3