Sign in with
Sign up | Sign in
Your question

BODS occours during the games

Last response: in Windows 7
Share
January 5, 2013 1:28:34 AM

Hi, awesome people (my English isn't that great... so beware lol)

I'm having a BODS problem and this started about 6 months ago.

This is what I have:
Windows 7 x64 bit
AMD Phenom(tm) II x6 1090 T processor
NVIDIA GeForce GTX 460
8 GB of RAM (not sure about the name of the product)
1TB of hard drive (currently using about 800GB)
ASUS M4A87TD EVO Motherboard
600W 80 Certified Power Supply
One extra Fan in a computer case


So, this BODS problem only occurs when I'm playing these two games: League of Legend and Dynasty Warrior 7.
Other games like Vindictus, Civilization V, Diablo 3, and Sims3 does not have BODS issue

It seems like BODS occurs when there are lots of graphics appears and moves around (like.. whole bunch of enemies show up or use lots of skills)

I looked some forms to fix the BODS issue and they stated to update all the drivers, check virus, and do a memory test.
So, i did all of that, but it did not fix the issue
I also format the computer and reinstall the Windows

I updated my Video card, sounds card, and motherboard to most current driver. That's all that i have to update, right?


To me, it looks like it is a problem with the video card.
So, i tried to test it by using Dynasty Warrior 7. I used the same Map (stage) with different graphic setting (High and Low)
If i set the graphic as High, i got BODS screen about 10 minutes later. Then i set it as low and got BODS about 40 minutes later...
(FYI: I can play games like Vindictus and Diablo3 with highest graphic setting and never have a problem)


Time to time, my apartment room electricity kind of shuts down all of sudden... could that damaged my video card, physically?
Any help would appreciated!
Thank you!


PS. I was able to play League of Legend with highest setting during summer time without any BODS error



This is the detail BODS error message:
-----------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007A13028
BCP3: 00000000B61A4000
BCP4: 0000000000000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010213-25396-01.dmp
C:\Users\James\AppData\Local\Temp\WER-37268-0.sysdata.xml

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

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

More about : bods occours games

a b $ Windows 7
January 5, 2013 1:44:57 AM

What are Power supply u are using... ?

It sound like overheating issue try check the temp.... while running stressing test

MSI kombustor furmark for gpu, prime95 for cpu....
msi afterburner or hwmonitor to check the temp.......
January 5, 2013 1:56:29 AM

rdc85 said:
What are Power supply u are using... ?

It sound like overheating issue try check the temp.... while running stressing test

MSI kombustor furmark for gpu, prime95 for cpu....
msi afterburner or hwmonitor to check the temp.......


Not sure the name of the product, but it is 600W and has 80 plus certificate

I don't think it is a temperature issue, CPU doesn't look hot and Video card does get hard either
During the summer time I played league of legend without any BODS and that time i didn't have that extra fan (updated this info in the main forum)
Thanks!
Related resources
Can't find your answer ? Ask !
a b $ Windows 7
January 5, 2013 3:19:46 AM

Well try those msi kombustor they are free....... :D 

at least we can rule out temp issue after the test...
a b $ Windows 7
January 5, 2013 3:27:05 AM

If you are getting a ton of power outtages it could have definitely be something going amiss with the card itself.

That video card appears to have a fan on it, unless its a 3rd party vendor card and it's been modified.

The next time you get a BSOD, take the side off of your computer and see if the fan on the video card is spinning at all. I know this sounds like something that would short out your system but as long as you keep a hand on the case itself, not plastic, it will keep you grounded and won't cause a short.

This will actually help you determine if the issue is truly your video card or something else.
January 5, 2013 4:59:47 AM

rdc85 said:
Well try those msi kombustor they are free....... :D 

at least we can rule out temp issue after the test...


This tool is pretty cool lol

I ran all the test and there was no BSOD and lowest temperature was 35C and highest was 53C

Thanks!
January 5, 2013 5:02:00 AM

hedwar2011 said:
If you are getting a ton of power outtages it could have definitely be something going amiss with the card itself.

That video card appears to have a fan on it, unless its a 3rd party vendor card and it's been modified.

The next time you get a BSOD, take the side off of your computer and see if the fan on the video card is spinning at all. I know this sounds like something that would short out your system but as long as you keep a hand on the case itself, not plastic, it will keep you grounded and won't cause a short.

This will actually help you determine if the issue is truly your video card or something else.



Luckly my Video Card has 2 fans lol and it spins just fine...
Could it be something else that is starting BSOD?
Thanks!
January 5, 2013 5:25:18 AM

That bugcheck code is WHEA_UNCORRECTABLE_ERROR. It means Windows detected a hardware failure. From the bugcheck parameters, it looks like a machine check exception from the CPU indicating some internal CPU failure. I got a similar one when I had OCed my CPU a bit too far. If you want to dig up Intel's CPU manuals, you can find what each bit in the MCi_STATUS register means and cross reference it with parameters 3 and 4 of the bugcheck.

EDIT: Actually you have an AMD CPU, so check out the BKDG for Family 10h CPUs - http://support.amd.com/us/Processor_TechDocs/31116.pdf

But you'll probably need to pull the WHEA error record to figure out which MCi_STATUS register you're seeing. I think the minidump contains that information. If you want, you can upload your minidump somewhere and post a link here so I can take a look. I've got nothing better to do right now.
January 5, 2013 6:29:47 AM

I would love to upload that file somewhere, but i cannot find any sites that i can upload this .dmp file....
Do you know any sites that i can upload this file?
Thanks
January 5, 2013 8:37:27 PM

aicom said:
That bugcheck code is WHEA_UNCORRECTABLE_ERROR. It means Windows detected a hardware failure. From the bugcheck parameters, it looks like a machine check exception from the CPU indicating some internal CPU failure. I got a similar one when I had OCed my CPU a bit too far. If you want to dig up Intel's CPU manuals, you can find what each bit in the MCi_STATUS register means and cross reference it with parameters 3 and 4 of the bugcheck.

EDIT: Actually you have an AMD CPU, so check out the BKDG for Family 10h CPUs - http://support.amd.com/us/Processor_TechDocs/31116.pdf

But you'll probably need to pull the WHEA error record to figure out which MCi_STATUS register you're seeing. I think the minidump contains that information. If you want, you can upload your minidump somewhere and post a link here so I can take a look. I've got nothing better to do right now.


I would love to upload that file somewhere, but i cannot find any sites that i can upload this .dmp file....
Do you know any sites that i can upload this file?
Thanks
January 6, 2013 3:28:42 AM

ljoo87 said:
I would love to upload that file somewhere, but i cannot find any sites that i can upload this .dmp file....
Do you know any sites that i can upload this file?
Thanks


You could share it via a service like Dropbox or SkyDrive. If you don't have accounts on either of those, you could just put it on mediafire.com
January 9, 2013 1:45:41 AM

aicom said:
You could share it via a service like Dropbox or SkyDrive. If you don't have accounts on either of those, you could just put it on mediafire.com


sweet! thanks!
Here is the link http://www.mediafire.com/?5ajm0jn5xobui2e

And found the workaround, but it is a sucky one
I have to play one stage and close the game and restart the game... lol
January 9, 2013 2:17:33 AM

Definitely a CPU-related problem. Looks like core 4 (the fifth core) threw a machine check exception when trying to read the L1 data cache.


4: kd> !errrec fffffa8007b59028
===============================================================================
Common Platform Error Record @ fffffa8007b59028
-------------------------------------------------------------------------------
Record Id : 01cdeb92a8781907
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 1/5/2013 22:30:05 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa8007b590a8
Section @ fffffa8007b59180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Data Read
Flags : 0x00
Level : 1
CPU Version : 0x0000000000100fa0
Processor ID : 0x0000000000000004

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa8007b590f0
Section @ fffffa8007b59240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000004
CPU Id : a0 0f 10 00 00 08 06 04 - 09 20 80 00 ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ fffffa8007b59240

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8007b59138
Section @ fffffa8007b592c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : DCACHEL1_DRD_ERR (Proc 4 Bank 0)
Status : 0xb6602000fc000135
Address : 0x00000001f8509280
Misc. : 0x0000000000000000
January 9, 2013 3:28:59 AM

hmm... is there a fix for this issue or is it just hardware failure?

Do you think i need to get a new CPU?
January 9, 2013 4:13:25 AM

It really looks like a hardware failure, unless there's something like overclocking or heat causing it. If you call AMD tech support and tell them that your CPU generated a machine check exception with an L1 data cache read error code, they'll probably replace it for you.

In any case, I'd be interested to see if you can replicate/induce the failure by using Prime95 with small FFTs. P95 might find a calculation error (on CPU 4) or it could cause another bugcheck. That should happen within 6 hours of running the test. If that does happen, it's another nail in the coffin of this CPU. The next time you won't be using it for many hours, start up Prime95 and give it a run on small FFTs.
February 9, 2013 10:42:10 PM

aicom said:
It really looks like a hardware failure, unless there's something like overclocking or heat causing it. If you call AMD tech support and tell them that your CPU generated a machine check exception with an L1 data cache read error code, they'll probably replace it for you.

In any case, I'd be interested to see if you can replicate/induce the failure by using Prime95 with small FFTs. P95 might find a calculation error (on CPU 4) or it could cause another bugcheck. That should happen within 6 hours of running the test. If that does happen, it's another nail in the coffin of this CPU. The next time you won't be using it for many hours, start up Prime95 and give it a run on small FFTs.



Sorry for the late response, but this Prime95 takes forever to complete... How long does it usually take to finish running?
!