New Hp Laptop Someone have a look?

gpwill · 19 Feb 2016

Hello,
Brand new HP laptop less than a month old with literally nothing it. Got it from Costco at a good deal. Wife was playing solitaire and boom. Ran it thru WinDBG and got this.... Can a guru have a look? Time to take it back?

Thanks

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.17336 (debuggers(dbg).150226-1500) x86fre

STACK_TEXT:
ffffd000`f7b085b0 fffff802`9283476d : 00000000`00000000 ffffe000`557cc010 fffff802`927566a0 fffff802`92817340 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`f7b08ae0 fffff802`92694c98 : ffffe000`557cc010 00000000`00000000 fffff801`5f0630c0 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffd000`f7b08b10 fffff802`92695ddd : fffff802`92756640 fffff802`92756640 fffff802`927566a0 00000000`00000287 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`f7b08b50 fffff802`924d56a9 : fffff802`92817200 ffffe000`54baa040 fffff801`00000000 ffffe000`00170000 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`f7b08b80 fffff802`925675a5 : 00000204`b4bbbdff 00000000`00000080 ffffe000`532c2680 ffffe000`54baa040 : nt!ExpWorkerThread+0xe9
ffffd000`f7b08c10 fffff802`925cb626 : ffffd000`f74a4180 ffffe000`54baa040 fffff802`92567564 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd000`f7b08c60 00000000`00000000 : ffffd000`f7b09000 ffffd000`f7b03000 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}

whs · 19 Feb 2016

This is a fatal hardware error. Time to return the device.

gpwill · 19 Feb 2016

Pretty much what I thought..

axe0 · 20 Feb 2016

All 0x124 errors are fatal errors

This error is an observing error, the CPU reports the errors but does nothing with the actual data that caused the crash.
The crash occured on the northbridge bus, because there was no delay between data 1 and data b.

My recommendation is to at least check Dell for driver updates, if this error occurs again report back so we can analyse it and see if it is the same problem.

Code:

1: kd> !errrec ffffe000557cc038
===============================================================================
Common Platform Error Record @ ffffe000557cc038
-------------------------------------------------------------------------------
Record Id     : 01d16a455612c750
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/18/2016 12:10:27 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe000557cc0b8
Section       @ ffffe000557cc190
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    @ ffffe000557cc100
Section       @ ffffe000557cc250
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 3e 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  @ ffffe000557cc250

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

Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa000010000b0c0f

Code:

Event[3173]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2016-02-18T07:11:16.300
  Event ID: 20
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-QHUDK67
  Description: 
A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: 11
Processor APIC ID: 0

The details view of this entry contains further information.

gpwill · 20 Feb 2016

My recommendation is to at least check Dell for driver updates, if this error occurs again report back so we can analyse it and see if it is the same problem.

Too bad Dell doesnt have drivers for HP laptops...:)

axe0 · 20 Feb 2016

Mischecked it

I was too much focused on your 'My System Specs'

gpwill · 20 Feb 2016

No issue axe0. Figure'd typo. My concern with this thing is its my wifes computer and I REALLY dont want to be playing around with this since we can return so easy. Appreciate you looking into it.

axe0 · 20 Feb 2016

I'm only asking for a driver check, see how it goes and report back :)

It looks like a single crash, if that is the case and no other bluescreen occurs anytime soon than you have nothing to worry with the reason that Windows handles single crashes.

gpwill · 20 Feb 2016

Will check and see what happens. Windows can handle single crashes. Wife cannot. :)

axe0 · 20 Feb 2016

Crashes will always give a (small) shock to the user when a crash occurs, I remember mine when I had my first bluescreen which immediately turned out to be a bluescreen loop.