Windows 7 Forums
Join Forum | Login | Today's Posts | Tutorials | Vista Forum | Windows 8 Forum


Windows 7: BSOD BATTLEFIELD BC2, error 0x00000124 or 0x00000101

24 Sep 2011  
TorwaK

Windows 7 Ultimate x64
1 posts
 
 
BSOD BATTLEFIELD BC2, error 0x00000124 or 0x00000101
Hi folks,

I checked stability of my PC with Prime95 (CPU+RAM blended test) 3 hours and it's quite stable. However during playing BF BC2 game I recieve BSOD often.

I can't attached the dump file due compressed size is 85Mb in the letter. So I paste the dump screen print.



Could you please review it for me?

Thank you.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`0329b670
Debug session time: Sun Sep 25 00:53:38.048 2011 (UTC + 3:00)
System Uptime: 0 days 0:55:56.876
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007b9b028, be000000, 800400}

Probably caused by : hardware

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

0: 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: fffffa8007b9b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`0301fa3b : 00000000`00000124 00000000`00000000 fffffa80`07b9b028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`031e3513 : 00000000`00000001 fffffa80`0793d880 00000000`00000000 fffffa80`0793d8d0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`0301f700 : 00000000`00000728 fffffa80`0793d880 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`0301f052 : fffffa80`0793d880 fffff800`00ba8e70 fffffa80`0793d880 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`0301ef0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`03012e88 : 00000000`00080204 00000000`030961a8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`030d152c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`030d1393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`3f22dbd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0018df38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3f22dbd4


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------
My System SpecsSystem Spec

24 Sep 2011  
zigzag3143

Win 8 Release candidate 8400
2,141 posts
 
 
Quote   Quote: Originally Posted by TorwaK View Post
Hi folks,

I checked stability of my PC with Prime95 (CPU+RAM blended test) 3 hours and it's quite stable. However during playing BF BC2 game I recieve BSOD often.

I can't attached the dump file due compressed size is 85Mb in the letter. So I paste the dump screen print.

Could you please review it for me?

Thank you.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`0329b670
Debug session time: Sun Sep 25 00:53:38.048 2011 (UTC + 3:00)
System Uptime: 0 days 0:55:56.876
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007b9b028, be000000, 800400}

Probably caused by : hardware

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

0: 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: fffffa8007b9b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`0301fa3b : 00000000`00000124 00000000`00000000 fffffa80`07b9b028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`031e3513 : 00000000`00000001 fffffa80`0793d880 00000000`00000000 fffffa80`0793d8d0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`0301f700 : 00000000`00000728 fffffa80`0793d880 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`0301f052 : fffffa80`0793d880 fffff800`00ba8e70 fffffa80`0793d880 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`0301ef0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`03012e88 : 00000000`00080204 00000000`030961a8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`030d152c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`030d1393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`3f22dbd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0018df38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3f22dbd4


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------
You should configure your user control panel to small dmp

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 Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
Reply

 BSOD BATTLEFIELD BC2, error 0x00000124 or 0x00000101 problems?



« BSOD Not sure why, and now it just shuts off. | Windows 7 Opens and looks fine but doesn't function »
Thread Tools



Similar help and support threads for: BSOD BATTLEFIELD BC2, error 0x00000124 or 0x00000101
Thread Forum
BSOD playing battlefield 3, error 0x00000101 BSOD Help and Support
BSOD playing Battlefield 3, error 0x00000101 BSOD Help and Support
battlefield bad company 2 bsod error 0x00000124 BSOD Help and Support
BSOD while playing Battlefield 3, error 0x00000101 BSOD Help and Support
Always BSOD's in Battlefield:BC2, error 0x00000124 BSOD Help and Support


All times are GMT -5. The time now is 06:54 PM.

Contact Us - Windows 8 Support - Windows Vista Support - Legal - Privacy and cookies - Top


Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd