Bsod 124

[Albert2006]

I was sent to you from the support of Electronic Arts. Whenever I try to play a game Battlefield Bad Company 2 minutes after 2-5 comes out the blue screen with 124 code.

Is Windows 7 . . .
- x64
- the original installed OS on the system? Yes
- full retail version
- Less than one year
- 3-5 month

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Language Code: 1049

For more information about this issue:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80047E4028
BCP3: 00000000B2000040
BCP4: 0000000000000800
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files containing information about the problem:
C: \ Windows \ Minidump \ 012911-32931-01.dmp
C: \ Users \ Albert \ AppData \ Local \ Temp \ WER-99918-0.sysdata.xml

All of your requirements complied, an archive of information attached.
Can you help me? Thx

 

[zigzag3143]

I was sent to you from the support of Electronic Arts. Whenever I try to play a game Battlefield Bad Company 2 minutes after 2-5 comes out the blue screen with 124 code.

Is Windows 7 . . .
- x64
- the original installed OS on the system? Yes
- full retail version
- Less than one year
- 3-5 month

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Language Code: 1049

For more information about this issue:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80047E4028
BCP3: 00000000B2000040
BCP4: 0000000000000800
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files containing information about the problem:
C: \ Windows \ Minidump \ 012911-32931-01.dmp
C: \ Users \ Albert \ AppData \ Local \ Temp \ WER-99918-0.sysdata.xml

All of your requirements complied, an archive of information attached.
Can you help me? Thx

First a 124 BC is hardware related read here to see what that means and what to try
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... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Second where did you get your copy of win 7? there are some very unusual file sizes and dates that we cant support.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\012911-32931-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;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
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03c65000 PsLoadedModuleList = 0xfffff800`03e99eb0
Debug session time: Sat Jan 29 10:22:02.793 2011 (GMT-5)
System Uptime: 0 days 0:41:40.603
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80047e4028, b2000040, 800}

*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware

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

Thanks


Ken

 

[Albert2006]

Thanks, I'll try to reinstall Windows