BSOD on sc2

[Webb26]

Okay guys i'm a fairly new custom pc builder so i consider myself a real big noob but i'll try and get out as much info as I can. Basically been getting the BSOD while playing sc2. Never had a problem till the past week.

Computer components:

motherboard: asus m4A87TD EVO
CPU: AMD phenom II x6 1090t 3.20 ghz
gpu: Sapphire radeon hd 5770 1gb, 128 bit
RAM: G skills ripjaws 8gb total(ddr3 1600)
Power supply: antec 500w

OS: Win 7 ultimate 64 bit full retail(clean install when pc was built)
Length of use: 1 month



I have a total of 5 .dmp files but I will only post the latest one. Lmk if the other dump files are needed. Also attached is the debug of the dump file.

Thank you for attempting/looking at this thread. I just hope that I can problem solve this situation.

 

[Webb26]

Sorry guys I didn't read the how to's so i will update with all the required information. I'll leave up the old info just in case.

Thanks again,
Giang

 

[yowanvista]

The dumps are blaming your CPU, please stop any overclocking
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

IF you still get the issue test your CPU

   Information

Go to your motherboard's website and check your version of your BIOS. See if there are any problems you are having that are solved by a a later version. I do not often recommend flashing the BIOS because there is a risk involved. If there is problem addressed by a BIOS that applies to your computer, consider flashing your BIOS to the latest version. If you choose to do this, flash you BIOS outside of Windows.

Run Prime 95 again to test your CPU and your ram. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007d59028, b640a000, e9000135}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007d59028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b640a000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000e9000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fddb08 fffff800`02ffc903 : 00000000`00000124 00000000`00000000 fffffa80`07d59028 00000000`b640a000 : nt!KeBugCheckEx
fffff880`02fddb10 fffff800`02b935a3 : 00000000`00000001 fffffa80`07b778f0 00000000`00000000 fffffa80`07b77940 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddb50 fffff800`02ffc5c8 : 00000000`00000728 fffffa80`07b778f0 fffff880`02fddeb0 00000000`060ae800 : nt!WheaReportHwError+0x263
fffff880`02fddbb0 fffff800`02ffbf1a : fffffa80`07b778f0 fffff880`02fddeb0 fffffa80`07b778f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddd00 fffff800`02fefe8f : 00000000`f6db5be8 00000000`00000001 fffff880`02fddf30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddd40 fffff800`02a7bfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddd70 fffff800`02a7be53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fddeb0 00000000`01028eef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`060ae74c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1028eef


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------

 

[Webb26]

^thank you for such a quick reply. I will get on the stress testing as soon as I get home. For overclocking, I didn't think I was. The only thing I can think of is in BIOS the amd turbo is set to enabled, sorry for such a noob question but could that be overclocking since I didn't manaully change the cpu settins in bios?

 

[yowanvista]

^thank you for such a quick reply. I will get on the stress testing as soon as I get home. For overclocking, I didn't think I was. The only thing I can think of is in BIOS the amd turbo is set to enabled, sorry for such a noob question but could that be overclocking since I didn't manaully change the cpu settins in bios?

Yes overclocking can cause BSODs

 

[Webb26]

So with all three tests my cpu could not last more than 1min before getting close to shutting down. I can't complete the tests. I updated to the latest bios when I first did the install of win7 so it's up to date. I don't know how to underclock, lol, from what its set to. I had never touched any setting to the cpu in bios so I don't know why its being oc'd now.

 

[yowanvista]

So with all three tests my cpu could not last more than 1min before getting close to shutting down. I can't complete the tests. I updated to the latest bios when I first did the install of win7 so it's up to date. I don't know how to underclock, lol, from what its set to. I had never touched any setting to the cpu in bios so I don't know why its being oc'd now.

Your CPU should be clocked at 3.2Ghz but its at 3.7Ghz atm. Try to reset your BIOS options to default values, this will clear any overclocks
IS your CPU properly cooled?

 

[Webb26]

^ i thought my cpu was properly cooled but after the stress testing I'm beginning to think otherwise. Would a .5 ghz overclock make that much of a difference? I'll go and reset bios to defaults and run another stress test and see how that goes.

 

[yowanvista]

^ i thought my cpu was properly cooled but after the stress testing I'm beginning to think otherwise. Would a .5 ghz overclock make that much of a difference? I'll go and reset bios to defaults and run another stress test and see how that goes.

It can make a difference if your CPU is badly overclocked

 

[SledgeDG]

I looked at your dumps and all blame the hardware error during the execution of SC2 (in fact they blame the AMD CPU cache)
I would say run a CPU Stress test to see what's behind that.
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Here is a BIOS update available for your board: ASUSTeK Computer Inc. -Support- Drivers and Download M4A87TD EVO

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\David\Desktop\Windows_NT6_BSOD_jcgriff2\050211-29234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Mon May  2 14:03:33.899 2011 (GMT-4)
System Uptime: 0 days 0:13:20.241
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007d59028, b640a000, e9000135}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007d59028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b640a000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000e9000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fddb08 fffff800`02ffc903 : 00000000`00000124 00000000`00000000 fffffa80`07d59028 00000000`b640a000 : nt!KeBugCheckEx
fffff880`02fddb10 fffff800`02b935a3 : 00000000`00000001 fffffa80`07b778f0 00000000`00000000 fffffa80`07b77940 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddb50 fffff800`02ffc5c8 : 00000000`00000728 fffffa80`07b778f0 fffff880`02fddeb0 00000000`060ae800 : nt!WheaReportHwError+0x263
fffff880`02fddbb0 fffff800`02ffbf1a : fffffa80`07b778f0 fffff880`02fddeb0 fffffa80`07b778f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddd00 fffff800`02fefe8f : 00000000`f6db5be8 00000000`00000001 fffff880`02fddf30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddd40 fffff800`02a7bfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddd70 fffff800`02a7be53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fddeb0 00000000`01028eef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`060ae74c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1028eef


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

[COLOR="Red"]BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/COLOR]

Followup: MachineOwner
---------

-DG

Sorry...when I started there was no answer yet.

 

[cluberti]

^ i thought my cpu was properly cooled but after the stress testing I'm beginning to think otherwise. Would a .5 ghz overclock make that much of a difference?

Remember, CPUs in the same "family" are sometimes produced in huge batches, and then tested for stability at different speeds to see where the part is stable, and then binned for sale at that speed. Overclocking a CPU that was potentially only stable at 3.2GHz means that 3.7GHz would be death to it. You have no way of knowing if you have a CPU that was running at 3.2GHz because it wouldn't pass faster speeds or was simply designed to run at 3.2GHz, but in general overclocking is something you must consider anytime that system becomes unstable afterwards. Also note that overclocking can cause permanent damage to the part, so you do take a real risk when you overclock something and create more heat.

 

[Webb26]

^ i thought my cpu was properly cooled but after the stress testing I'm beginning to think otherwise. Would a .5 ghz overclock make that much of a difference?

Remember, CPUs in the same "family" are sometimes produced in huge batches, and then tested for stability at different speeds to see where the part is stable, and then binned for sale at that speed. Overclocking a CPU that was potentially only stable at 3.2GHz means that 3.7GHz would be death to it. You have no way of knowing if you have a CPU that was running at 3.2GHz because it wouldn't pass faster speeds or was simply designed to run at 3.2GHz, but in general overclocking is something you must consider anytime that system becomes unstable afterwards. Also note that overclocking can cause permanent damage to the part, so you do take a real risk when you overclock something and create more heat.

Ahh i see, thanks for clearing this up guys. In all honesty I don't even remember every trying to overclock but i'll be more careful from here on out. I haven't been able to stress test since this afternoon, but hopefully I can give it a go when I get home. Also quick question, but if my cpu can not handle the stress test how can I get results to post up?

Currently on my setup i'm using the stock cpu fan and case fans. Again, thanks for all your help thus far.
-Giang

 

[SledgeDG]

You should start with loading and saving the BIOS Defaults!
That should take care of any overclocking accidentally or otherwise and sets your RAM timings to SPD values.

 

[Webb26]

You should start with loading and saving the BIOS Defaults!
That should take care of any overclocking accidentally or otherwise and sets your RAM timings to SPD values.

Thanks, so I set them to default values and set RAM to spd values and now I get random freezes every couple start ups. Then I reset the values of the RAM to auto and less freezes but still there. According to cpuz my cpu is always running at ~3.2ghz while in performance tab under task manager my cpu is very active. I have nothing running and my cpu is not under idle and is always running at 3.2ghz. IMHO that seems out of the normal since before the cpu would idle and be running at ~.08ghz

Edit: Is it necessary to run cool n' quiet? Would this cause any instability once going back to regular cpu speeds?

 

[SledgeDG]

Nope..Cool 'n Quiet is only active when nothing else uses the CPU. It runs on all my computers without problems.
that would also take care of CPU-Z always showing full speed.

Since RAM timing seems to make a difference you might play with that a little more (Check what the Manufacturer recommends)

-DG

 

[Webb26]

^So even with cool n quiet on or off my cpu speed always shows 3.2ghz. I set my RAM to manufacturer's specs so that should be squared off. My only problem is that I continually get freezes and have no idea what causes the system to do that.

 

[cluberti]

Is it a hard freeze, where you can't move the mouse cursor, numlock doesn't go on/off, etc? If so, that's hardware still.

 

[Webb26]

Is it a hard freeze, where you can't move the mouse cursor, numlock doesn't go on/off, etc? If so, that's hardware still.

Yes its exactly what you described.

 

[Webb26]

This is what my cpu usage is like with firefox open with three tabs open and chatting with AIM.

Doesn't that seem odd to you guys or is it normal?

 

[cluberti]

It's a bit much, but that could be normal depending on what apps are doing in the background.