0x124 - possibly related to NVIDIA drivers?

Zudo · 30 Oct 2015

I've been having a crashing problem recently.

Zudo said:

Hi all, this problem has been pestering me for months, but after failed attempts to fix it myself, I felt I should ask for help.

I am running Windows 10 (64-bit), but this problem also occurred on 8.1 and 7 (both 64-bit) with clean installations. I am also dual booting Ubuntu Studio 15.04, but more on that later.

When I boot my PC into 10, I have up to ten minutes before my PC either resets forcefully by itself, or freezes and never recovers. When I check the Minidump folder afterwards nothing is there.

I have replaced both my CPU (amd fx-6300) and PSU (corsair cx500m), and tested my RAM (with both sticks or just one), but none of that has fixed the problem.

My BIOS settings are at their defaults, no over/underclocking or over/undervolting at all.

The odd thing is, Ubuntu Studio runs fine with no crashes as far as I can see *EDIT: NOT THE CASE* , but if there was a software problem surely there would be a dump file?

I'd like to see what the community here thinks.

So earlier today I finally got a dump file. It's a WHEA_UNCORRECTABLE_ERROR (0x124) but I have no idea how to interpret it. As you can see from my original post, I was having no trouble running Ubuntu Studio, but after I installed the NVIDIA official drivers, I started crashing. If anyone can help me here it would be greatly appreciated.

axe0 · 30 Oct 2015

Hi Zudo,

Do you have the dump file from yesterday?
Please check {windows partition}\windows\minidump\ for the dump file

The errors are 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, but this error is also caused by overclocking, faulty drivers or BIOS problems.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning

If you're overclocking your system, revert back to stock clocks now.

Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: MemTest86+ RAM Diagnostic
Part Two: Hard Drive Diagnostics
Part Three: GPU Stress Test

One

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking forzero errors here. Even a single error will indicate RAM failure.

Two

HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

Three

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

The problem:
A generic bus error, where the CPU observed the error as a 3rd party which means that the CPU found this error but it doesn't belong to the work of the CPU.

Code:

1: kd> !errrec ffffe001aa5638f8
===============================================================================
Common Platform Error Record @ ffffe001aa5638f8
-------------------------------------------------------------------------------
Record Id     : 01d11321caf487ff
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/30/2015 14:46:54 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe001aa563978
Section       @ ffffe001aa563a50
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   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 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  @ ffffe001aa563b10

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

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

Zudo · 31 Oct 2015

Thanks for the reply.

Running Memtest86+ showed no problems, it ran overnight for 16 passes and no errors were found.

SeaTools is happy with my hard drive. It didn't find any problems.

FurMark ran fine, with no crashes - this surprised me!

Is there anything else that I can do?

axe0 · 31 Oct 2015

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Zudo · 01 Nov 2015

I've been running Driver Verifier, and have received several crashes that looked no different to before. Here are all the dumps.

axe0 · 01 Nov 2015

Please run the DM Log Collector tool again.
Only dumps may not be enough.

Zudo · 01 Nov 2015

axe0 said:

Please run the DM Log Collector tool again.
Only dumps may not be enough.

OK, done. You might notice differences from the original file, as I performed a clean install.

axe0 · 01 Nov 2015

The northbridge is where the problem occurs, just noticed it.

Code:

Event[496]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2015-10-31T16:43:32.721
  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-PSF3GO2
  Description: 
A fatal hardware error has occurred.

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

Is there anything connected to your PC besides PSU, mouse and keyboard?
Is everything inside the case properly connected?

SmartEyeball · 01 Nov 2015

Zudo said:

, but after I installed the NVIDIA official drivers, I started crashing. .

I assume you've unistalled the drivers and tried an older version?

Typically if the crashes started after installing the drivers, then it's the drivers. Uninstall through Programs&Features and when you install another driverset, use custom and select the "Perform Clean Installation" check box.

http://www.nvidia.com/Download/Find.aspx?lang=en-us

Zudo · 01 Nov 2015

SmartEyeball said:

I assume you've unistalled the drivers and tried an older version?

Typically if the crashes started after installing the drivers, then it's the drivers. Uninstall through Programs&Features and when you install another driverset, use custom and select the "Perform Clean Installation" check box.

http://www.nvidia.com/Download/Find.aspx?lang=en-us

Thanks for the help, but I've done that several times.

axe0 said:

The northbridge is where the problem occurs, just noticed it.

Code:

Event[496]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2015-10-31T16:43:32.721
  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-PSF3GO2
  Description: 
A fatal hardware error has occurred.

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

Is there anything connected to your PC besides PSU, mouse and keyboard?
Is everything inside the case properly connected?

There's no other peripherals apart from my monitor, as I've unplugged anything that isn't necessary. I'll check all the connections.