My first BSOD.. help needed :(

[WIGILOCO]

I was playing Battlefield Bad Company 2 for few hours without a problem, then suddenly my monitor goes black and I got bluescreen on my face. The event viewer raport says that it is my CPU which caused the error (code x124). I have overclocked my CPU from 3,4 to 3,8GHz and it has passed prime95 blend torture test for 16h without errors. Also intelburntest for few hours. I have had these overclocks for 8 months without any issue.

Here is the memory dump, if someone could take a look for me. I will appreciate any help given. Thank you.

PC specs

AMD Phenom II 965BE
ASUS M4A78T-E
AMD 6870 1GB
4GB DDR3 1333MHz
1TB HDD
Windows 7 64BIT

 

[zigzag3143]

I was playing Battlefield Bad Company 2 for few hours without a problem, then suddenly my monitor goes black and I got bluescreen on my face. The event viewer raport says that it is my CPU which caused the error (code x124). I have overclocked my CPU from 3,4 to 3,8GHz and it has passed prime95 blend torture test for 16h without errors. Also intelburntest for few hours. I have had these overclocks for 8 months without any issue.

Here is the memory dump, if someone could take a look for me. I will appreciate any help given. Thank you.

PC specs

AMD Phenom II 965BE
ASUS M4A78T-E
AMD 6870 1GB
4GB DDR3 1333MHz
1TB HDD
Windows 7 64BIT

Two things

1-sptd.sys a huge cause of BSOD's

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-Hardware. This may be being caused by the sptd.sys above but in case it isnt.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

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


Loading Dump File [C:\Users\K\Desktop\123010-20872-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Thu Dec 30 13:28:15.319 2010 (GMT-5)
System Uptime: 0 days 8:18:24.521
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004c42028, b20da000, 175}

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: fffffa8004c42028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b20da000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, 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:  BFBC2Game.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdba88 fffff800`031ef903 : 00000000`00000124 00000000`00000000 fffffa80`04c42028 00000000`b20da000 : nt!KeBugCheckEx
fffff880`02fdba90 fffff800`02d87593 : 00000000`00000001 fffffa80`04c43ea0 00000000`00000000 fffffa80`04c43ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdbad0 fffff800`031ef5c8 : 00000000`00000728 fffffa80`04c43ea0 fffff880`02fdbe30 00000000`0bf23f00 : nt!WheaReportHwError+0x263
fffff880`02fdbb30 fffff800`031eef1a : fffffa80`04c43ea0 fffff880`02fdbe30 fffffa80`04c43ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdbc80 fffff800`031e2e8f : 00000000`0bf24280 00000000`00000001 fffff880`02fdbeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdbcc0 fffff800`02c6ffec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fdbcf0 fffff800`02c6fe53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdbe30 00000000`00d12e23 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0306e240 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xd12e23


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
---------

 

[WIGILOCO]

I indeed had Daemon tools on my pc, now uninstalled and windows did the sound when you plug something out.. Could this really cause BSOD which says that CPU had a error? Thanks for help too. Is it needed to download that SPTD duplexsecure thing?

 

[zigzag3143]

I indeed had Daemon tools on my pc, now uninstalled and windows did the sound when you plug something out.. Could this really cause BSOD which says that CPU had a error? Thanks for help too. Is it needed to download that SPTD duplexsecure thing?

Yes the only way to remove the entire virtual HD is using duplexsecure (or something like it)

SPTD is one of the largest causes of BSOD's. It is a file we always look for and when found is usually the cause.


Ken J

 

[WIGILOCO]

I will bring my CPU overclock to stock speeds because I just heard that Bad Company 2 is very itchy about any OC and can cause BSOD because of that. =)

 

[zigzag3143]

I will bring my CPU overclock to stock speeds because I just heard that Bad Company 2 is very itchy about any OC and can cause BSOD because of that. =)

Overclocking is also a big cause of BSOD's. I can understand its need but it causes so many different instabilities I wonder if the boost is worth it.

Ken J

 

[WIGILOCO]

Yes, and in my case the gain was quite small. Though raising NB frequenzy made some little improvements. Now I'm at stock speeds and feel free Let's hope the problem went away