I know this is probably not the place for this kind of question, but maybe someone already had this bullshit going on with their PC.

Anyway, I have Windows 7 ultimate 64bit, I have reinstalled it twice now. At first (for a month or so) it works perfectly, no problems. Then it stars throwing blue screens of death daily. And I mean, just once a day and then it has no problems, but every single day I boot up my pc, it blue screens of death in the space of 1 hour randomly.

It doesn't help that the errors displayed by the BSOD keep shuffling and changing every day. I have tried checking the disk and repairing bad sectors, and it fixes the issue for around two days, but then it starts it's tune again.

What the fuck? Has anyone had anything similar going around?

Hardware issue would be my guess. It could be anything tho. My guess goes to CPU, graphics card or any other component which severely heats up during runtime.

edit: Just try to diassemble your computer and assemble it again, it might just be a wrong connection or other triviality like that. And yeah, I've had random BSODs, for whatever reason when I've had a weak power supply.

I'd point the finger squarly at bad RAM. I had this when I was trying to run two pairs of RAM that was recommended at 2 different voltages. Make sure you're running at the right voltage, and run a memtest..

That would lead to completely random BSODs instead of 'within one hour' tho, wouldn't it? RAM sticks were my first guess as well, but the one hour rule kind of confuses me...

I suggest you go to Tech Support Forum. They've got instructions and everything. It might take a few days and probably a few bumps for them to get back to you, but they probably will.

My guess is that it's a hardware failure, but I'm no expert.

Me too, but I got the same thing. I wonder if once it's warmed up it's able to handle the voltage, but getting it going is the problem.

Well they do get connected right next to the CPU, so it would make sense. Kind of.

Regarding it being the hardware problem, the last time I had this error, in around a month or two, bent my PC over and it just wasn't starting at all, bluescreening every time on the welcome screen. So I took it to the company that assembled my PC and they told me that there's nothing wrong with the hardware, only the windows, which I need to reinstall. And I did, and it worked perfectly for a month. But now, for some reason, it has started again.

I really don't feel like waiting for it to screw up my PC again, losing 400GB worth of data with my internet would suck admiral balls.

Well there might be, and keep in mind that there's an incredibly small probability of this (and I don't know whether something like that can even happen with win 7,) that there is something wrong with your Win 7 installation itself. Scratched install DVD, whatever, that installs a corrupted file. But I would not bet on it, more likely the guys who assembled it missed something / screwed up.

1. As already has been suggested, run a test on your RAM. This is easy to do and might eliminate one possible culprit. Or it might not, but it's not hard to do and therefore worth a shot.

2. Remove your hard drive, and connect it to a different computer as a data drive. Run an HD test from that computer.

For testing, I found Aida64 pretty useful, but there are several options.

Shouldn't it be possible to do this fairly reliably via a live Linux distro? It would eliminate the need of finding another computer... And if the Linux distro screws up itself, it's probably not a HDD issue :D

I'll try it out, sure. Fair enough, but why the extended periods of working perfectly? I'm thinking I always install something that butts heads with the drivers or windows 7 or whatever it could rival with.

Yep. That occured to me only after I wrote my reply. I was just going to edit it in, but now see that you've beaten me to it. :)

Using a live Linux distro is actually the better option, since there also is a (however small) chance that the problem is caused by a malware infection. Which would make it inadvisable to connect the HD to a different computer.

The Linux distro might not be able to distinguish completely between problems in the HD, mainboard, CPU, and RAM (a clean analysis would need switching parts with a different computer), but it's the best start.

You could also try scanning instalation for corupted files. sfc /scannow

But, I also point finger at faulty RAM stick.

Cannot find a memtest in Aida64! D:

And should I write that sfc /scannow into the Run window?