New Laptop and Getting 0x124 BSOD - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Hardware > Hardware Repairs and Troubleshooting
Click Here to Login
Reply
 
Thread Tools Display Modes
 
Old 06-05-2016, 04:26 AM   #1 (permalink)
Newb Techie
 
Join Date: Jun 2016
Location: UK
Posts: 7
Question New Laptop and Getting 0x124 BSOD

Hi All,

So I got the "HP Envy 15-ah150sa" (Specification) And after a while I was using it (Nothing too intensive) it hard reset itself quickly showing a BSOD.
After the reset the booting sequence animation runs twice with the second one at a lower framerate. The boot now takes like 3 times as long and the laptop is generally really slow.
I contacted HP support and they ran it with all non-Microsoft services disabled, and it still ran slow. They then suggested a factory reset which I did. It ran perfectly for a while like it was but the event happened again, now running slow again.
Wondering anyone could help figure it out. I also used the HP system check which showed nothing.

Here is the mini-dump summary:
Bug check code: 0x124
Parameter 2: ffffe001`ef37b8f8
Caused by driver: ntoskrnl.exe

Thanks in advance.
Tom
Ho0ty
__________________

ho0ty is offline   Reply With Quote
Old 06-05-2016, 12:36 PM   #2 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,507
Default Re: New Laptop and Getting 0x124 BSOD

Is this laptop brand new and still under warranty?

Please upload your latest minidump file from C:\Windows\Minidump

Add it to a zip file and attach it to a post.

Things I'd first suggest:
Run a chkdsk on your drive:
Start -> type 'cmd' (without quotes) -> right click -> run as admin -> in the console window that pops up type:
chkdsk C: /f /r
Press Enter and it will say it cannot lock the current drive and to run on next reboot. Type Y and hit Enter -> Reboot your computer and let it run through the check (it may take some time, depending on how big your HDD is).

Would also suggest running a Memtest with Memtest86+: Memtest86+ - Advanced Memory Diagnostic Tool
Burn the ISO to a CD or create a bootable flash drive with something like Rufus, and reboot the system and boot off of the media you just created. Let it run for several passes (the longer the better, a minimum of 4 hours or even overnight is best). If there's any errors at all, then you have bad memory and need to test each memory stick one at a time.
__________________

__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is online now   Reply With Quote
Old 06-06-2016, 08:58 AM   #3 (permalink)
Newb Techie
 
Join Date: Jun 2016
Location: UK
Posts: 7
Default Re: New Laptop and Getting 0x124 BSOD

Yes it is brand new and under warranty.
I did dskchk and it finished with nothing wrong looking at the log.
I'll try doing memtest, if I can find a flash drive to boot off, and see what comes up.
Minidump attached.

Thanks,
Tom
ho0ty is offline   Reply With Quote
Old 06-06-2016, 09:42 AM   #4 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,507
Default Re: New Laptop and Getting 0x124 BSOD

Looks like your attachment must not have gone through? Can try uploading it to somewhere like Mega, Dropbox, OneDrive, etc. if it's too big to be attached to a post.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is online now   Reply With Quote
Old 06-06-2016, 12:03 PM   #5 (permalink)
Newb Techie
 
Join Date: Jun 2016
Location: UK
Posts: 7
Default Re: New Laptop and Getting 0x124 BSOD

Running memtest at the moment, I'll put it in Dropbox once it's finished.
ho0ty is offline   Reply With Quote
Old 06-06-2016, 01:00 PM   #6 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,507
Default Re: New Laptop and Getting 0x124 BSOD

Sounds good - let us know what happens with the Memtest.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is online now   Reply With Quote
Old 06-06-2016, 02:51 PM   #7 (permalink)
Newb Techie
 
Join Date: Jun 2016
Location: UK
Posts: 7
Default Re: New Laptop and Getting 0x124 BSOD

Ok so memtest running for over 5 hours came back clean with no errors, so its probably not the memory. Here is the minidump on dropbox.
MiniDump DB
ho0ty is offline   Reply With Quote
Old 06-06-2016, 03:41 PM   #8 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,507
Default Re: New Laptop and Getting 0x124 BSOD

Related: blue screen error - Microsoft Community

Here's your raw dump file:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe001ef37b8f8, 0, 0}

Probably caused by : AuthenticAMD

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: ffffe001ef37b8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
ffffd001`205535b0 fffff801`c17cb7b1 : 00000000`00000000 ffffe001`ef37b8d0 fffff801`c16ed6a0 fffff801`c17ae340 : nt!WheapCreateLiveTriageDump+0x81
ffffd001`20553ae0 fffff801`c162bca8 : ffffe001`ef37b8d0 ffffe001`ed3b1b10 00000000`00000000 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffd001`20553b10 fffff801`c162cded : fffff801`c16ed640 fffff801`c16ed640 fffff801`c16ed6a0 fffff801`c14fdac0 : nt!WheapProcessWorkQueueItem+0x48
ffffd001`20553b50 fffff801`c145dc59 : fffff801`c17ae200 ffffe001`ed195040 fffff801`00000000 ffffe001`ef23ab58 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd001`20553b80 fffff801`c1508b65 : 00000205`b4bbbdff 00000000`00000080 ffffe001`eb8a1680 ffffe001`ed195040 : nt!ExpWorkerThread+0xe9
ffffd001`20553c10 fffff801`c1562926 : ffffd001`1fe40180 ffffe001`ed195040 fffff801`c1508b24 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd001`20553c60 00000000`00000000 : ffffd001`20554000 ffffd001`2054e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

Followup: MachineOwner
---------
Running an additional command on the error address we get this:
Code:
1: kd> !errrec ffffe001ef37b8f8
===============================================================================
Common Platform Error Record @ ffffe001ef37b8f8
-------------------------------------------------------------------------------
Record Id     : 01d1bda54ea4f1c6
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/3/2016 14:36:40 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe001ef37b978
Section       @ ffffe001ef37ba50
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         : 3
CPU Version   : 0x0000000000660f01
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 01 0f 66 00 00 08 04 00 - 0b 32 d8 7e ff fb 8b 17
                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  @ ffffe001ef37bb10

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

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000f0564024
  Misc.       : 0xd00a0fff01000000
So, could be RAM still; could also be chipset/graphics drivers, or a hardware issue with the CPU/GPU.

I would recommend updating your graphics/chipset drivers from AMD's website directly and see if you still have issues.

Also, what are you CPU/GPU temps? Use something like HWMonitor to monitor them and try and cause a BSOD and see what the temps were around when it happened.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is online now   Reply With Quote
Old 06-06-2016, 04:07 PM   #9 (permalink)
Newb Techie
 
Join Date: Jun 2016
Location: UK
Posts: 7
Default Re: New Laptop and Getting 0x124 BSOD

Thanks for that.
So through light use though it has been running a while, these are the temperatures:

Hardware monitor ACPI
Temperature 0 46C (114F) [0xC78] (TSZ0)
Temperature 1 20C (68F) [0xB74] (TSZ2)
Temperature 2 0C (32F) [0x0] (PCH)

Hardware monitor Battery
Voltage 0 12.95 Volts [0x3293] (Current Voltage)
Capacity 0 48017 mWh [0xBB91] (Designed Capacity)
Capacity 1 46706 mWh [0xB672] (Full Charge Capacity)
Capacity 2 46706 mWh [0xB672] (Current Capacity)
Level 0 3 pc [0x61] (Wear Level)
Level 1 100 pc [0x64] (Charge Level)

Hardware monitor AMD ADL
Temperature 0 46C (114F) [0x2E] (TMPIN0)
Clock Speed 0 336.28 MHz [0x150] (Graphics)
Clock Speed 1 435.08 MHz [0x150] (Memory)

I haven't had a BSOD since the last one, it only seems to happen once after a factory reset, so I doubt I will be able to re-create it. Plus it happened during only light/moderate use which seems quite random as it didn't happen while I was quite heavily gaming on the notebook where I would expect it to if it was temperature based.
ho0ty is offline   Reply With Quote
Old 06-06-2016, 04:19 PM   #10 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,507
Default Re: New Laptop and Getting 0x124 BSOD

Hmm, so it only happened after doing a fresh install (factory reset) then? I'd probably say it was driver related then.
__________________

__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD DRIVER_IRQL_NOT_EQUAL, BSOD help please? happyh1ppo Hardware Repairs and Troubleshooting 1 01-05-2012 03:52 PM
BSOD Stop Error 0x124 MindoverMaster Microsoft Windows and Software 18 06-02-2011 06:31 PM
Getting BSOD 0x000000F4 naRIPSTA Hardware Repairs and Troubleshooting 3 09-08-2008 05:11 PM
Why am i getting DRIVER_IRQL_NOT_LESS_THAN_EQUAL_TO BSOD's??? diabloII Monitors, Printers and Peripherals 13 07-18-2005 12:28 PM
BSOD - Multiple times! Getting very bad stevo119 Microsoft Windows and Software 10 06-02-2005 04:25 PM



Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 04:19 PM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.