BSoDs (Windows restarts itself)

[Arclight]

Think it might be the hard drive. Maybe bad sector or something, damaged filesystem, not sure.

Do you format the partition during setup? Might try doing a full format next time (Win7 setup only does quick format), and run the error-checking tool in Windows (right-click the drive > properties > 'tools' tab).

[Feuer Frei!]

If this is a new computer, you may simply have some bad memory. Try taking out a stick for a few days (if you have two) and if it still crashes, put the other stick back in and take out the first.

If this is a computer that worked fine with a previous OS, it still could be a bad component, but less likely. Have you downloaded and installed all the manufacturers drivers, or just used the built-in Windows ones?

Heat can be another issue, as well, as flaky power supplies.

When you installed 7, did you install it onto a newly created partition?
A common side effect of faulty memory is data corruption, so what I usually recommend in severe cases where there are a lot of memory errors, or memory is likely to have been faulty for some time is a clean install to clear any corruption.
Run MemTest:
http://www.memtest.org/

Let us know how you go.

[Arclight]

Iirc he just rebuild the thing after a faulty PSU. Afraid that thing may have damaged other components before going out.

[Crécy]

Originally Posted by Arclight

Iirc he just rebuild the thing after a faulty PSU.

Yes, the PSU was changed to a better one.

Originally Posted by Feuer Frei!

If this is a new computer, you may simply have some bad memory. Try taking out a stick for a few days (if you have two) and if it still crashes, put the other stick back in and take out the first.

Have you downloaded and installed all the manufacturers drivers, or just used the built-in Windows ones?

Heat can be another issue, as well, as flaky power supplies.

When you installed 7, did you install it onto a newly created partition?
A common side effect of faulty memory is data corruption, so what I usually recommend in severe cases where there are a lot of memory errors, or memory is likely to have been faulty for some time is a clean install to clear any corruption.
Run MemTest:
http://www.memtest.org/

Let us know how you go.

Yes, I have a fairly new computer (one-year-old). I installed chipset updates. I deleted both partitions and then created a 100gb partition for windows 7. I installed it there.

Ran CHKDSK as Arc suggested and at least it didn't find any bad sectors. I will try memtest now.

Which memtest file I should download?

Thank you both for your help so far!

[Feuer Frei!]

Originally Posted by Crécy

Which memtest file I should download?

http://hcidesign.com/memtest/download.html

[Syxx_Killer]

I would bet anything it is bad memory. I went through this for a long time before I finally broke down and got some different memory. I have Windows XP (SP2 on disc, SP3 after update). I would get random BSoDs all the time. It would happen when I am on the computer and when off. I disabled the automatic reboot so I could see what the messages were. MEMORY_MANAGEMENT and BAD_POOL_HEADER were two of my my frequent ones, too. I also had DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL_TO (or something to that effect). There were a couple others, but I don't remember what they were. I also would experience random crashes with just about any program I used. Firefox and Chrome were especially vulnerable. I had Crucial Ballistix at the time. I then switched out for some Patriot memory. Haven't had a single BSoD or random crash since (knock on wood ).

[Crécy]

I did the memtest. Had about one million and three-hundred thousand errors. Guess that indicates a faulty RAM then, huh?

[Castout]

How long have you been using the power supply?


Could be it.

Edit: Missed the conclusion.

[Feuer Frei!]

Originally Posted by Feuer Frei!

If this is a new computer, you may simply have some bad memory. Try taking out a stick for a few days (if you have two) and if it still crashes, put the other stick back in and take out the first.

A common side effect of faulty memory is data corruption, so what I usually recommend in severe cases where there are a lot of memory errors, or memory is likely to have been faulty for some time is a clean install to clear any corruption.

Originally Posted by Crécy

I did the memtest. Had about one million and three-hundred thousand errors. Guess that indicates a faulty RAM then, huh?

Quiet possible.
Use my suggestions that i quoted, see how you go