Crashing daily (The computer has rebooted from a bugcheck)

Microsoft's hotfix solved the problem for me.

Which hotfix or are you just selling something?

KB Article Number(s): 2495523
Language: All (Global) Platform: x64 Location: (http://hotfixv4.microsoft.com/Window...tl_x64_zip.exe) Password: jskWFu%

Thank you Jarome - I am not quite sure what to do as each crash is giving me a different bugcheck STOP # i.e. 0x0000003b and 0x0000007e and 0x0000000a and 0x00000024 and 0x00000050..... There seems to be separate Hotfixes for most. Cannot believe I should install each nor any given one. Sure would appreciate any insite re my BSOD almost daily.

Hey, this same problem has been annoying me for months now. I do a lot of production 3D renders and it has made the render pipeline very unstable as my PC is the manager of all this.... it normally crashes once a day on high memory load. Had the i7 rig overclocked to 3.8ghz for almost a year now and was running rock solid but only recently the project I have been working on demands a very high memory load constantly and since had this problem...

Applied TheUSMarshall's trick yesterday morning and no crash yet.. I pray it doesnt! If not I shall try giving the memory a bit more juice!

Cheers for the help guys!

PROBLEM SOLVED:
After a crash/blue screen on occasion my system would report 2 of my 6 memory sticks as not installed and reflected 8GB installed rather than 12GB. (I set something in boot setup to see the slots as the system boots but cannot remember now what I did. If you need this info let me know and I will try to go back through the process but I could also see the missing memory after boot using tools HP (Support Assistant) supplied on the system and under control panel/system security/system) I have run extensive tests on the memory multiply times using various programs including MEMTEST86 to do so with no bad results ever being reported. Note that crashes always seem to report a different bug check code and varying suspect files as the cause. H.P. wanted me to send them the machine to bench test in case the problem was motherboard but I could not afford to do so. Finally when the system crashed and reported missing memory sticks slots 1 and 2 I swapped one and two with 5 and 6 and waited days/weeks for the next crash which also reflected the missing sticks. Finally and sure enough 5 and 6 came up empty. To be sure I moved 5 and 6 to 3 and 4 and waited again. Sure enough in a few days 3 and 4 came up empty after a crash. I called H.P. and finally convinced them it was a faulty stick. They sent two new sticks and things have been working great now for two weeks. I am convinced it was a memory module even after running multiple tests that indicated no problems. Good Luck you all. P.S. My bad sticks were “MICRON TECHNOLOGY” 2.00 GB DDR3-SDRAM (1333MHz). Now replaced with KINGSTON.

You can also go to START and type "memory" and select "Show how much RAM is on this computer" from the list.

Hello everyone.

When someone googles for the GUID code of this error, this is the first topic that comes up.
I've found my solution and thought this is a good place to share it, since this topic is the first source of solutions to hundreds of future searchers. Even if the last post is 160 days ago.

I've tried most of the tips here to no avail. Then I did two things at once; disabled overdrive in ATI control center, and changed my RAM settings to from "Turbo" to "Standard" in my Gigabyte BIOS. (there is standard, turbo and extreme).

I have no idea why it was set as Turbo. Maybe they just didn't want it to look like "slow-standard-turbo", so they changed it to "standard-turbo-extreme".

My specs:

Intel i7 860
Gigabyte GA-P55M-UD2 P55
Transcend 2GB DDR3 1333Mhz
Radeon 5770 1GB


Anyway I knew that the crash occurred whenever I set uTorrent to download a big file over night. Not once did it survive the 24h mark, always crashed before that.

So after these last 2 changes, I set it to download 80 gigs - so it would download for about 18 hours straight at full speed - and it's been running for 28 hours so far.