It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
If your motherboard has an integrated graphics card, you could plug your monitor into it and unplug your graphic card, to check if it is a problem of this card.
BSOD (Blue Screen of Death) crashes are commonly caused by 3 things;

1: Bad drivers (manufacturer's code) and usually incorrectly blames on the operating system.

2: Faulty OS/HDD (i.e. corrupted)

3: Faulty CPU/Memory/Mama board/PSU (Power Supply)

(Usually in that order)

As the second post above mentions about rootkit/malware/adware/viruses/worms - usually it is not enough to do a system cleaning. But since your HDD are a "tad old", I suggest getting a new one, reinstall, and copy over personal files / games you might bring over. You should always have an external backup disk.

Going through event viewer usually gives more headache then solutions, that`s my experience anyway.

If that doesn`t work, then you have to to go trough a separate check list, just to eliminate what hardware that work / doesn`t work
Post edited August 10, 2013 by sanscript
avatar
klaattu: If your motherboard has an integrated graphics card, you could plug your monitor into it and unplug your graphic card, to check if it is a problem of this card.
The thing is, it's random, and doesn't appear to be related to the stress of the graphics card, as the comp can freeze while playing, while loading or while idling. It's so god damn weird.

Also did a rootkit scan, showed up nothing.

Maybe I need to run that memtest or something.
Win 7 has integrated a RAM test.

You should find it in the search menu looking for mem. It should be called something like Diagnose your computer's memory problems.

It will reboot and test your RAM
Btw, the error message thingie does a "minidump" file (hilarious name). Is there a way I can read it? Would it even tell more about the error?
avatar
KneeTheCap: Btw, the error message thingie does a "minidump" file (hilarious name). Is there a way I can read it? Would it even tell more about the error?
It is a dump of the memory of the system to know the exact state. You can load it in windbg but I think most of us couldn't understand a thing.
avatar
KneeTheCap: Btw, the error message thingie does a "minidump" file (hilarious name). Is there a way I can read it? Would it even tell more about the error?
Well, If you really want to; http://support.microsoft.com/kb/315263#method3

https://en.wikipedia.org/wiki/Memory_dump

http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx


It might, but it usually helps if you are an MS engineer when reading it...
Post edited August 10, 2013 by sanscript
Ah, computers. They get mugged and when they describe the culprit, instead of a detailed description they say "'twas a man"

Maybe I should revert back to consoles...
avatar
KneeTheCap: Ah, computers. They get mugged and when they describe the culprit, instead of a detailed description they say "'twas a man"

Maybe I should revert back to consoles...
Since Time is Money, as they say, "No one" reads those dumps or the event viewer, they are heavenly cryptic about information. Well, event viewer CAN give some direction on where the error repeats itself.

Blame it on MS for shitty coding - everyone else does :p
interesting.
avatar
sanscript: BSOD (Blue Screen of Death) crashes are commonly caused by 3 things;

1: Bad drivers (manufacturer's code) and usually incorrectly blames on the operating system.

2: Faulty OS/HDD (i.e. corrupted)

3: Faulty CPU/Memory/Mama board/PSU (Power Supply)

(Usually in that order)

As the second post above mentions about rootkit/malware/adware/viruses/worms - usually it is not enough to do a system cleaning. But since your HDD are a "tad old", I suggest getting a new one, reinstall, and copy over personal files / games you might bring over. You should always have an external backup disk.

Going through event viewer usually gives more headache then solutions, that`s my experience anyway.

If that doesn`t work, then you have to to go trough a separate check list, just to eliminate what hardware that work / doesn`t work
"tad old" means it's what, 5-6 years now? Something like that, so maybe it's time to replace that anyway. I have two, and windows is installed on the older and smaller one. The other HDD is much newer, maybe 3 years.

About that power supply, if its faulty, wouldn't that mean the crashes would be more frequent while playing? So far the most common place for the comp to crash is while its loading something (Windows desktop, a game and stuff like that).
Do you get a kernel inpage error too?
avatar
Tiefood: Do you get a kernel inpage error too?
the what?
Try this out:
http://www.tomshardware.com/answers/id-1627817/bsod-bccode-124.html
avatar
sanscript: Snip 8<
lol @ "Mama Board"

avatar
sanscript: [i] BSOD (Blue Screen of Death) crashes are commonly caused by 3 things;

1: Bad drivers (manufacturer's code) and usually incorrectly blames on the operating system.

2: Faulty OS/HDD (i.e. corrupted)

3: Faulty CPU/Memory/Mama board/PSU (Power Supply)

(Usually in that order)

As the second post above mentions about rootkit/malware/adware/viruses/worms - usually it is not enough to do a system cleaning. But since your HDD are a "tad old", I suggest getting a new one, reinstall, and copy over personal files / games you might bring over. You should always have an external backup disk.

Going through event viewer usually gives more headache then solutions, that`s my experience anyway.

If that doesn`t work, then you have to to go trough a separate check list, just to eliminate what hardware that work / doesn`t work[/i]
avatar
KneeTheCap: [i] "tad old" means it's what, 5-6 years now? Something like that, so maybe it's time to replace that anyway. I have two, and windows is installed on the older and smaller one. The other HDD is much newer, maybe 3 years.

About that power supply, if its faulty, wouldn't that mean the crashes would be more frequent while playing? So far the most common place for the comp to crash is while its loading something (Windows desktop, a game and stuff like that).[/i]
Loading something MAY be a RAM / Memory problem
Try using 1 stick of RAM if you have more than 1 and see if it stops the error(s). If you DO have more than 1 and you DO take them all out except for one like I just said, and you STILL get an error(s), try switching to another RAM stick and repeat this process until either the problem stops or you try all the RAM sticks you have and the problem doesn't cease.

Atleast this way you can rule out the RAM being faulty.
Post edited August 10, 2013 by YellowAries