BSOD WHEA uncorrectable error W 8.1 even after reinstall

[JVD]

Dear all,

I keep getting Blue Screens on Windows 8.1 with "Whea Uncorrectable Error". I already reinstalled Windows so I'm assuming it's related to a Hardware issue (?) ...

Attached the BSOD report.

I would be happy if you could help me to resolve this issue!!!

Best,
Julian

 

[axe0]

Check Samsung for BIOS updates and (re)install all most recent drivers available.

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: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

CPU TEST

Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help 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 for zero errors here. Even a single error will indicate RAM failure.

THREE

HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

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

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

FOUR

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help 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.

 

[JVD]

axe0,

thank you for posting the guidelines.

Part One: CPU Stress Test: I ran IntelBurntest without any problems (see screenshot).
Part Two: MemTest86+ RAM Diagnostic: 8 passes & 0 errors (see screenshot).
Part Three: Hard Drive Diagnostics: Couldn't run SeaTools because it's a SSD. Disk Check (chkdsk) shows no errors. HD Tune results see screenshots.
Part Four: GPU Stress Test: I ran it for ~30min without any problems, the system got a little slow in response though. I couldn't locate the logs but the maximum temperature was ~94°C.

Would be great if you could help me narrow the issue down!

Thanks a lot in advance,
JulianView attachment 67366

 

[axe0]

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.​

How to fill in your system specs:

 

[cluberti]

This particular error code is coming from the CPU, and it's an undocumented error code by Intel:

Proc. Info 0  @ ffffe0010bf75240

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


Error         : Internal unclassified (Proc 0 Bank 4)
  Status      : 0xb200000000100402

The only way to know what happened is to ask Intel directly, but the CPU itself did indeed throw the error. Most all of the other issues, like RAM, disk, etc. will at least come up classified - an "Internal Unclassified" error means the error exists in the Intel MCi, but is not documented in the Intel x86/x64 documentation, and that would lean towards some sort of error thrown by the CPU itself, whether that be power-related, or something to do with access to memory regions. In any case, it would appear there's an actual hardware error here (either with the CPU or the board it's plugged into).

 

[JVD]

Dear all,

thanks for your answers.

@axe0: Updated the system info.
@cluberti: I talked to intel and they asked me to run the IntelProcessor Diagnostic Tool. The test failed (see results below). They advised me to talk to Samsung's support and troubleshoot the issue with them. I will do this and report back.

Best regards

--- IPDT64 - Revision: 3.0.0.23.W.MP
--- IPDT64 - Start Time: 10.02.2016 12:19:39


--------------------------------------------------------------------
Processor 1
--------------------------------------------------------------------
Intel(R) spbc Module Test
Module Version: 1.0.7.64b.W
Start Time: Wed Feb 10 12:19:39 2016
Test Result - PASS
..!!..Processor under test is verified as 'PRODUCTION'..!!..


Processor Manufacturer: GenuineIntel
Processor Brand String: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz


End Time: Wed Feb 10 12:19:40 2016
Total Time: seconds: 1
--------------------------------------------------------------------
Genuine Intel CPU Test
Module Version: 1.0.12.64b.W
Start Time: Wed Feb 10 12:19:40 2016
Test Result - PASS
Expected: GenuineIntel
Detected: GenuineIntel
End Time: Wed Feb 10 12:19:40 2016
Total Time: seconds: 0
--------------------------------------------------------------------
Temperature Test
Module Version: 1.0.12.64b.W
Start Time: Wed Feb 10 12:19:40 2016
Test Result - PASS
Expected: Greater than 1 degrees below max
Received: 35 degrees below max
End Time: Wed Feb 10 12:19:40 2016
Total Time: seconds: 0
--------------------------------------------------------------------
CPU Brand String Test
Module Version: 1.0.12.64b.W
Start Time: Wed Feb 10 12:19:40 2016
Test Result - PASS
Expected String Parts: As Defined in BrandString_LocalConfig.xml
Detected: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz
End Time: Wed Feb 10 12:19:40 2016
Total Time: seconds: 0
--------------------------------------------------------------------
Module - CPUFreq.exe did not create a results file.
--------------------------------------------------------------------
--- IPDT64 - Temperature Monitor Results
Temperature Monitor will begin when CPULoad Test starts
Temperature Monitor Stopped


--------------------------------------------------------------------


System Information
------------------
Processor Name: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz
Processor Information: Intel64 Family 6 Model 58 Stepping 9
Number of Physical Cores: 2
Number of Logical Cores: 4
Installed System Memory: 4 GB
Operating System: Microsoft Windows 8.1 64-Bit
Graphics Information: Intel(R) HD Graphics 4000
System Product: NP900X3F-K01DE
System BIOS: P03ACX
System Serial Number: JDMS91DD800008
--------------------------------------------------------------------


--- IPDT64 - End Time: 10.02.2016 12:19:40
--- IPDT64 - Result: Fail
--------------------------------------------------------------------
FAIL

 

[cluberti]

Seems like heat damage given the test failure. Good luck with the OEM, let us know what happens if you remember to do so.

 

[JVD]

Dear all,

Samsung's support told me to check for driver updates or reinstall the system. As I already reinstalled I checked for driver updates via Samsung's Update Tool, there was one Bluetooth Driver update available. After I updated this yesterday. I ran again the IntelProcessor Diagnostic Tool and it passed. I also didn't experience another BSOD (yet).

Do you think this may have caused the BSOD?

Attached the test results.

I'll report back if I get another BSOD.

Best Regards

 

[cluberti]

Hard to say, as there's no way to assume the test environment (physical) was exactly the same as the failing one. Bluetooth hardware in such a system is likely part of the WiFi chipset, which hang off of the PCI or USB bus (depending on motherboard design the OEM uses), so while anything is possible, it's not likely. However, a stable system is usually a good one, so hopefully the issue has not occurred in the last week.