Windows 7 - Blue Screen Of Death (BSOD) help?

[sneekypeet]

http://img260.imageshack.us/img260/8445/p1160107.jpg

HELLO - haha it was just a matter of time... the only reason i installed this windows is to play DX10 games.

I need your help, please!

This bscreen keeps appearing randomly - 30 minutes after start, 15 minutes after start, 4 hours
after start. When my pc is idle, when im playing games - same... I just noticed that when playing CODMWF2 it shows up apparently 5 minutes in the game - it happened 3-4 times now.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80029A0038
BCP3: 00000000B66F0000
BCP4: 0000000000010016
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
D:\Windows\Minidump\112109-18314-01.dmp
D:\Users\Kralq\AppData\Local\Temp\WER-30342-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
D:\Windows\system32\en-US\erofflps.txt


Here's my info:

Athlon x2 5000+ @ 3 ghz, corsair xms2 800mhz ddr2, gigabyte MA690V mb, 9600GT, 400W PSU

http://img502.imageshack.us/img502/3815/thumbsmoher.jpg


If u have an answer to this problem, or you need more info (specify what) post here!

I'm running a Intel i7 960 3.2 mhz, not overclocked. I think you're confusing me with another person.

Another thing I just noticed is, After I select "log in" I see a pop-up for a split second that relates to allowing the connection, or allowing it through my firewall. I cant get to it fast enough to select yes, because I get the Black Screen almost instantly.
I have Xfire allowed in my Firewall, I added each .exe manually. Does anyone know how I can get this selected before my Black Screen? I know this must be the issue, but I dont know how to fix it or find the process to allow it. According to my Firewall, its allowed. if so, why am I still getting that pop up?

Thanks again.

I think you were the one doing the confusing, as you can see I bolded where I got my information from. Thanks for clearing up the fact that the specs you listed for us to fix arent the specs, maybe you should edit the OP a bit

I assume you havent even been in bios and set the ram voltage to spec or the timings?
Also depending on the ram it may need some voltage in other areas to get stable at stock. Bios defaults are a guess to get you booted, sometimes you have to finesse it into compliance.

 

[Steevo]

I think Sneeky means, GTFO this isn't your thread.

I was directing the question to the OP, not you. And for all of you on Win 7 X64, or Vista X64. The 64 bit instructions reveal a little more weakness in your overclock. The extra instruction sets, decimal places and register width makes a naormally acceptable overclock fail when the rounding that EVERY processor does stand out.

For example when rounding a incomplete number at a lower accuracy or lower bit set, the margin of error created by a microscopicly unstable overclock will be within the acceptable range. When you perform the same calculation in a native 64 bit enviroment the margin of error becomes unacceptable. Thus the reason your "stable" overclock fails in a 64bit enviroment.


Lets calculate something so we have a idea.



We want to send Sneeky to the other side of the galaxy to a planet inhabited by beer serving fair maidens. The exact earth to planet X trajectory is a decimal degree and speed calculation. If the calculation if off by one 128th of a percent (complex) then he hits the planet behind it. That is a planet of sexy men, who sodomize one another forcefully. So how important is it to Sneeky that we have exact coordinates and speed? If our calculations of either the initial trajectory, or speed are off by
.000000000000000000000000000000000000000000000000000000000000001 then he is either sailing past the planet into oblivion, or has just been forceably entered from the rear.

Only due to a extra instruction set that a X86 (32 bit) doesn't calculate unless it is forced, or in a native X64 (64 bit) system it does the extra calculations anyway.

 

[BLuDKLoT]

Gawd damn man, you guys are fools. Forget I asked.

 

[Steevo]

Thats amazing, you hijack a thread, then get confused, then get joked around with, and your response is to call names?




You are awsome.


Go make your own thread, you might get helped, but with that attitude I doubt it.

You just need to press alt+tab back to your desktop and allow it. If you made your own thread you would have this super hard "fix" that everybody and their mother knows about already.

 

[Deleted member 67555]

@ BluDKlot ur answer is already listed in this post....Read it over it's actually a simple fix..
and yes please get ur own thread

@ Bulgarianboy92 did you remove ur OC as Sneekypeet suggested and did that work?

 

[Wile E]

I think you were the one doing the confusing, as you can see I bolded where I got my information from. Thanks for clearing up the fact that the specs you listed for us to fix arent the specs, maybe you should edit the OP a bit

I assume you havent even been in bios and set the ram voltage to spec or the timings?
Also depending on the ram it may need some voltage in other areas to get stable at stock. Bios defaults are a guess to get you booted, sometimes you have to finesse it into compliance.

Ummm, 2 different people?

 

[freepizza]

Blue screen - Meee tooo

Hi BulgarianBoy92

I have the same problem exactly. With slightly differing HW.

Gigabyte EP45-Extreme with ASUS 4890 Grafix card, Nothing is overclocked. I think what is common with us is the Motherboard. Board was flashed with newer Firmware but it still happens albeit less. and the latest 4890 driver installed All on windows 7 64bit. Vista 64Bit did the same. I have emailed Gigabyte 2 days ago and still waiting for response. But I have no answers. Other than to go back to my older Grafix card - as the old one was ok.

The link previously mentions a hotfix. But the only/closest one is vista x64. applying it on Win7 gave the message that "The update is not applicable on your computer". Can I disable the "hot plugging" feature ? Cos the KB seems to be blaming that. How do I do that, would it cause other problems?

Thanks people

 

[Steevo]

Start your own thread. You will be better served by the community.


I will respond.

 

[Solaris17]

Ummm, 2 different people?

lol ya i was confised for a sec i read amd in the op then i7 960's i was like wait WTF? you just cant change your system specs halfway throuh a poblem...o wait someone hijacked