BSOD error 0x00000124 WIN7_DRIVER_FAULT

[MrPointy]

Hi,

I've recently been working on a system that suffers a periodic BSOD.

There is a warning before the BSOD, with the system slowing down, the mouse becoming jerky, sound stuttering and then freezing.

I've been looking through the dump files and a WIN7_DRIVER_FAULT is mentioned. It also refers to process NBservice.exe, which I believe relates to Nero Back It Up. However, I thought a 0x124 error related to hardware? If removing Back It Up is all I need to do to fix these BSODs, then I will very

I would be very grateful if someone could review the attached dump files and advise if I'm in the right area?

Thanks

 

[Arc]

Hi MrPointy

Are you talking about it?

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

It is something default there. It appears everywhere, unless Driver Verifier is running behind. It is not anything to pay attention at.

What you are talking about a stop 0x124 is absolutely right. It is some sort of hardware error.

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

[B][COLOR=Red]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR][/B]
[COLOR=Red]A fatal hardware error has occurred.[/COLOR] 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, [COLOR=Red]Machine Check Exception[/COLOR]
Arg2: fffffa80083a6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

If you want to read:

• WHEA - Windows Hardware Error Architecture
• Machine-check exception - Wikipedia, the free encyclopedia
• Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR (Windows Debuggers)
• http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

If you follow the parameter 2, you get ....

1: kd> !errrec fffffa80083a6028
===============================================================================
Common Platform Error Record @ fffffa80083a6028
-------------------------------------------------------------------------------
Record Id     : 01cf1b4c8f9663c5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/30/2014 10:51:01 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000001

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

Local APIC Id : 0x0000000000000001
CPU Id        : 7a 06 01 00 00 08 04 01 - bd e3 08 0c ff fb eb bf
                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  @ fffffa80083a6240

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 1 Bank 0)
  Status      : 0xf200004000000800

So it indicates to some CPU BUS, as you can see. But if the first parameter is

Arg1: 0000000000000000, Machine Check Exception

.....then it is a stereotype output, because

A Machine Check Exception (MCE) is a type of computer hardware error that occurs when a computer's central processing unit detects a hardware problem.

• Source: Machine-check exception - Wikipedia, the free encyclopedia

Here the error is detected by the processor BUS, it is not necessary that it is detecting its own fault.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

It appears to be an old branded desktop Though the system spec says it is a custom build, I find it as an Acer Aspire M3802. Do you agree with me?

BiosMajorRelease = 8
BiosMinorRelease = 0
BiosVendor = American Megatrends Inc.
[COLOR=Red]BiosVersion = P01-A0
BiosReleaseDate = 08/18/2009[/COLOR]
[COLOR=Red]SystemManufacturer = Acer
SystemProductName = Aspire M3802
SystemFamily = Acer Desktop[/COLOR]
SystemVersion =         
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = Acer
[COLOR=Red]BaseBoardProduct = EG43M[/COLOR]
BaseBoardVersion =

Some primary suggestions in this case would be .....

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

If possible, update the BIOS.

Also, it would be better to take some regular hardware tests.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
__________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80083a6028, f2000040, 800}

Probably caused by : GenuineIntel

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

1: 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: fffffa80083a6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`009f8a58 fffff800`03a0ba3b : 00000000`00000124 00000000`00000000 fffffa80`083a6028 00000000`f2000040 : nt!KeBugCheckEx
fffff880`009f8a60 fffff800`0359f453 : 00000000`00000001 fffffa80`082b4ea0 00000000`00000000 fffffa80`082b4ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f8aa0 fffff800`03a0b700 : 00000000`00000728 fffffa80`082b4ea0 fffff880`009f8e30 fffff880`009f8e00 : nt!WheaReportHwError+0x263
fffff880`009f8b00 fffff800`03a0b052 : fffffa80`082b4ea0 fffff880`009f8e30 fffffa80`082b4ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f8c50 fffff800`03a0af0d : 00000000`00000004 00000000`00000001 fffff880`009f8eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f8c90 fffff800`039fee88 : 00000000`00000001 fffff880`009f0180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f8cc0 fffff800`0348746c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f8cf0 fffff800`034872d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f8e30 fffff800`03a03eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0331bc28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHpetQueryCount+0x1c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_bus

FAILURE_ID_HASH:  {38a83809-f559-ef4c-bd8b-993a0e589732}

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