"ntkrnlmp.exe" related BSOD

[franzela]

View attachment 252328
I bought recently this PC and it had this problem from the beginning. I tested the hardware (except power supply) and everything is working, yet i'm still getting BSOD from time to time. If you have any idea what's happening please tell me! sorry for my english
View attachment 252328

 

[Arc]

Hello

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 50[/COLOR], {fffff80003225240, 8, fffff80003225240, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+437f6 )

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

According to Carrona.org, STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Let us check them one by one.

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.

Run SFC /SCANNOW Command - System File Checker

Uninstall AVG using AVG Remover. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Do some disc checks.

1. Update your SSD's Firmware (Skip it, if it is not a SSD)
2. Re-seat the sata and power.
   
   
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Uninstall Magic Disc. Those Disc image mounting programs are often problematic; specially in case when they are set to be auto start with windows.

Let us know the results.

 

[franzela]

Report

I did what you told me....
In my first report i set CPU to use only 2.4 ghz out of 3.2 ghz because the BSOD was to frequently and i could't use the PC at all.
RAM is ok.
System File Checker :"windows resource protection did not find any integrity violations".
I removed AVG (and magicdisc) and replaced it with Microsoft security essentials and MBAM. Their scan found nothing.
Disk Check : ok, no bads or anything.
Then i enabled Driver Verifier and used PC as usual. Then i set the CPU to use 3.2 ghz (to see what happens), and 5 minutes after the windows' startup a BSOD occured. I guess the CPU is the problem but you know better...
Anyway here's the report after the BSOD View attachment 252369

 

[Arc]

Disable driver verifier. When a DV enabled crash dump shows a Atop 0x124, DV is no more necessary.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 124[/COLOR], {0, fffffa80072181d8, f673a000, 6d000136}

Probably caused by : AuthenticAMD

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=Red]
WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
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: fffffa80072181d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f673a000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000006d000136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

[COLOR=Red]DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f1a08 fffff800`02e1aa3b : 00000000`00000124 00000000`00000000 fffffa80`072181d8 00000000`f673a000 : nt!KeBugCheckEx
fffff880`009f1a10 fffff800`02fddb13 : 00000000`00000001 fffffa80`0519fd60 00000000`00000000 fffffa80`0519fdb0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f1a50 fffff800`02e1a700 : 00000000`00000728 fffffa80`0519fd60 fffff880`009f1db0 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`009f1ab0 fffff800`02e1a052 : fffffa80`0519fd60 fffff880`009f1db0 fffffa80`0519fd60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f1c00 fffff800`02e0de8f : 00000000`00000000 00000000`00000001 fffff880`009f1e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f1c40 fffff800`02ece8ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f1c70 fffff800`02ece713 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f1db0 fffff800`02f89de1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031d39d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x41


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_VRF_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_VRF_PROCESSOR_CACHE

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

Follow the Guide: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

 

[franzela]

Still usolved

i noticed that if i deactivate a core the problem disappear. apparently BSOD appears only when the CPU works at its full processing speed....I left the CPU in a service and they told it works fine. I searched for 124 error and it's usualy appears when the system is overclocked but i never overclocked it, in fact i used less then it's power so the pc could work. What should i do?View attachment 252761

 

[Arc]

Stress test the CPU.
Hardware - Stress Test With Prime95

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.

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

Check all the other hardware like PCI and PCIe devices, USB devices and PSU.

Finally, The step #9 of http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Edit: Unistall these programs. If it says to set anything to default at first to uninstall, do it.

Start Menu\Programs\ASUS
Start Menu\Programs\ASUS\EPU-4 Engine
Start Menu\Programs\ASUS\PC Probe II

Uninstall these programs, too.

Start Menu\Programs\DAEMON Tools Lite
Start Menu\Programs\MagicDisc

All the disk image mounting programs are problematic, as they virtualize hardware. Among them, Daemon tools is the most frequent BSOD causer.

 

[franzela]

!

I don't have access to equivalent components,but as i ran prime95 the 124 BSOD appeared...

 

[Arc]

Try to replace the CPU.