BSOD, bug check 0x124. Tested parts, completely lost.

xekushnr · 07 Feb 2019

Before I get going, here are the specs;

CPU: i7-7700k
MB: Asus Z270-AR
GPU: Asus GTX1070 OC 8GB
RAM: 2 x GSkill Trident Z 8GB
HDD: Samsung 850 EVO 500GB
PSU: Thermaltake Toughpower Grand RGB 650W
OS: Win10 Home

All parts were purchased new ~20 months ago. This started last Thursday. On Wednesday I updated my graphics driver, restarted, gamed for about three hours with no problems. Thursday I went to use the computer after work and within a few minutes in Windows it BSODs. This has continued till now and the computer is unusable. The code it gives me is WHEA_UNCORRECTABLE_ERROR (big help there) but when I view the crash logs it comes up with bug check 0x124 with hal.dll, ntoskrnl.dll and pshed.dll crashing.

It does run in safe mode. I have had it run in safe mode for hours with no issue.

The computer is not overclocked.

Here's what I have done;

GPU: Uninstalled drivers, removed from computer and plugged HDMI into motherboard. Issue persists. Observed fans running. Installed newest driver from Asus.

MB: Observed voltages in BIOS. All slightly over stated voltages. Upgraded BIOS to current version. Reset all settings to default. Verified no overclock. Visually checked board, looks fine. Reseated all connections.

RAM: Tested one stick at a time, issue persisted. Ran Memtest86 for 3-4 hours, no errors, passed fine. Tried sticks in slots 2 and 4 (was originally in 1 and 3)

HDD: Ran check disk, no errors. Swapped in another drive. Issue persisted. Formatted and reinstalled Win10. Issue persisted

OS: Tried Windows reset feature. Think it's supposed to reset OS to what it was like when first installed. Issue persisted. Formatted and did a fresh install.

CPU: Only part with a replacement plan, so I brought it to Micro Center. They loaded it up in Windows and ran Prime95 for ~45 minutes and said it worked flawlessly. I ran the Intel tool here and it passed that as well.

PSU: Unplugged every connection and replugged. Checked voltages in BIOS, all were a bit over the stated voltage.

Every part has been physically checked for damage. Every component has been reseated in the motherboard and every harness pulled and reinserted. The entire computer and every component has been blasted out with air.

When I checked the drivers in the verifier utility, I noticed rspndr.sys was marked as for an older version; I copied a new one from my Windows 10 CD and now I get no blue screen, just black and a restart.

I'm at wits end here, please help!

Ztruker · 07 Feb 2019

The zip file you uploaded is corrupted. Can you run the Beta log collector and upload that zip file please.

xekushnr · 07 Feb 2019

That was what the zip was from, but here's another one.

philc43 · 08 Feb 2019

Still can't open the zip file. Try the other DM Log Collector.

xekushnr · 08 Feb 2019

I think the problem is that I can barely keep the thing running in Windows long enough to get the reports. I ran both the DM and Beta logs again, both in regular Windows and in safe mode where the computer will actually keep running. One of these has got to work for you guys.

zbook · 08 Feb 2019

At some time the BETA log collector will replace the DM log collector.
There were two posts in this thread that had zips that were not able to be opened.
They displayed: compressed (zipped) folders error with the zip being invalid.
It was unclear what had happened.

The latest BETA zip was able to be opened.

The logs displayed that Windows driver verifier is still on.
1) Please turn off Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 | Tutorials

2) All of the BSOD in WER were WHEA 0x124 which is typically malfunctioning hardware.

3) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip the file > post a share link into the thread

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 02/07/2019 18:48:26
Size on disk: 537 MB

4) For any BSOD:
a) run the BETA log collector and post a new zip into the thread
b) open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into the thread

5) If you see any problems while running the BETA log collector or if the problems with the BETA log collector continue please use a camera or smartphone camera to take pictures and post images into the thread.

6) Open administrative command prompt and type or copy and paste:
7) sfc /scannow
8) dism /online /cleanup-image /restorehealth
9) chkdsk /scan
10) wmic RecoverOS set AutoReboot = False
11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

12) Make sure that there is no over clocking while troubleshooting.

13) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums | Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

14) To ensure that there are no improper bios settings please reset the bios.

15) Sometimes there can be failure to boot after resetting the bios.

16) Backup the computer files to another drive or to the cloud.

17) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

18) Create a brand new restore point:
Create System Restore Point in Windows 10 | Tutorials

How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how...bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

19) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

20) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.

Once the bios is reset and there is no overclocking:

21) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

22) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU | Tutorials
a) Record the maximum temperature and post the maximum temperature into the thread
b) Record test duration and post the uninterrupted test duration into the thread
c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 | Tutorials

23) Run memtest86 version 8.01 for four passes x 2.
MemTest86 - Official Site of the x86 Memory Testing Tool
MemTest86 - Official Site of the x86 Memory Testing Tool

The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.

Memtest86 version 8.0 was able to test for 8 or more passes.
In January 2019 Memtest86 version 8 was upgraded to 8.1
This new edition can only run four passes.

To be able to run 8 passes requires a pay version.

So the options now are to run two tests with each being four passes or to use the pay version.

Continuous testing is better than interrupted testing.

So at this time the best free testing appears to be two tests with four passes for each test.

There is 16 GB of RAM on the computer.
Memtest version 8.1 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 4 passes x two.
This should differentiate good from malfunctioning RAM.

b) For each Memtest version 8.1 run of four passes please use a camera or smartphone camera to take pictures and post images into the thread.
In addition to the image please post a text file into the thread using a share link (one drive, drop box, or google drive)

Memory problems. - Microsoft Community

MemTest86+ - Test RAM | Tutorials

24) Run HD Tune (free or trial edition)
https://www.hdtune.com/
Post images into the thread for results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

25) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test | Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 | Tutorials

26) All of these test should be done with the bios reset and no over clocking.

27) For each of the above tests please record maximum temperatures.

Code:

===============================================================================
Common Platform Error Record @ ffff9586ff74d028
-------------------------------------------------------------------------------
Record Id     : 01d4bf35e7697cd6
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/7/2019 22:40:32 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff9586ff74d0a8
Section       @ ffff9586ff74d180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000906e9
Processor ID  : 0x0000000000000003

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff9586ff74d0f0
Section       @ ffff9586ff74d240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000003
CPU Id        : e9 06 09 00 00 08 10 03 - bf fb fa 7f ff fb eb bf
                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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff9586ff74d138
Section       @ ffff9586ff74d280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 3 Bank 0)
  Status      : 0xf203f78000010005

philc43 · 09 Feb 2019

Looking at your report of all the tests you have done and zbook's analysis I have the following suggestions:

1. Turn off Driver Verifier as zbook requested - it is no longer needed.
2. The most important part of zbook's analysis is the code box at the end but he does not explain it. It indicates that the CPU is reporting a micro architectural error but that it is an unknown error. This tends to make me suspicious that the CPU could be faulty, every 0x124 error reports the same unknown error. Running Prime 95 on it in another PC suggests the CPU might be OK but this is not conclusive. If you have another CPU you can borrow to test in your PC do try it to rule in or out the CPU.
3. The black screen you now get suggests you should revert to the previous driver version for rspndr.sys. Do this in Device Manager in safe mode and roll-back the driver.
4. The fact that the on board graphics also gave the problem rules out the GPU card.
5. It is possible the motherboard is faulty but we can only conclude that once all the other components have been tested.

xekushnr · 10 Feb 2019

Code:

Microsoft Windows [Version 10.0.17134.556]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\twofo>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Users\twofo>cd\

C:\>cd
C:\

C:\>dir
 Volume in drive C has no label.
 Volume Serial Number is 668F-A91D

 Directory of C:\

02/06/2019  09:47 PM    <DIR>          NVIDIA
02/06/2019  09:11 PM    <DIR>          PerfLogs
02/07/2019  07:00 PM    <DIR>          Program Files
02/07/2019  05:59 PM    <DIR>          Program Files (x86)
02/07/2019  06:34 PM    <DIR>          symcache
02/06/2019  08:33 PM    <DIR>          Users
02/10/2019  07:41 PM    <DIR>          Windows
               0 File(s)              0 bytes
               7 Dir(s)  466,084,450,304 bytes free

C:\>cd Windows

C:\Windows>dir
 Volume in drive C has no label.
 Volume Serial Number is 668F-A91D

 Directory of C:\Windows

02/10/2019  07:41 PM    <DIR>          .
02/10/2019  07:41 PM    <DIR>          ..
02/06/2019  09:11 PM    <DIR>          addins
02/06/2019  09:11 PM    <DIR>          appcompat
02/06/2019  09:14 PM    <DIR>          apppatch
02/06/2019  09:17 PM    <DIR>          AppReadiness
02/10/2019  07:12 PM    <DIR>          assembly
02/06/2019  09:14 PM    <DIR>          bcastdvr
04/11/2018  06:34 PM            67,072 bfsvc.exe
02/06/2019  09:11 PM    <DIR>          Boot
02/06/2019  09:11 PM    <DIR>          Branding
02/06/2019  09:14 PM    <DIR>          CbsTemp
02/06/2019  09:11 PM    <DIR>          Cursors
02/06/2019  09:53 PM    <DIR>          debug
02/06/2019  09:11 PM    <DIR>          diagnostics
02/06/2019  09:13 PM    <DIR>          DigitalLocker
02/06/2019  09:54 PM             1,947 DtcInstall.log
02/06/2019  09:13 PM    <DIR>          en-US
07/06/2018  09:17 AM         3,932,672 explorer.exe
02/06/2019  09:11 PM    <DIR>          GameBarPresenceWriter
02/06/2019  09:11 PM    <DIR>          Globalization
02/06/2019  09:53 PM    <DIR>          Help
01/09/2019  12:36 PM         1,054,720 HelpPane.exe
04/11/2018  06:34 PM            17,920 hh.exe
02/06/2019  09:11 PM    <DIR>          IdentityCRL
02/06/2019  09:13 PM    <DIR>          IME
02/06/2019  09:53 PM    <DIR>          ImmersiveControlPanel
02/07/2019  07:25 PM    <DIR>          INF
02/06/2019  09:15 PM    <DIR>          InfusedApps
02/06/2019  09:11 PM    <DIR>          InputMethod
02/06/2019  09:11 PM    <DIR>          L2Schemas
02/06/2019  10:11 PM    <DIR>          LastGood
02/06/2019  09:43 PM    <DIR>          LastGood.Tmp
02/06/2019  09:11 PM    <DIR>          LiveKernelReports
02/08/2019  02:06 AM    <DIR>          Logs
02/06/2019  09:53 PM             1,378 lsasetup.log
02/07/2019  06:48 PM       563,076,971 MEMORY.DMP
04/11/2018  06:34 PM            43,131 mib.bin
02/10/2019  07:13 PM    <DIR>          Microsoft.NET
02/06/2019  09:11 PM    <DIR>          Migration
02/07/2019  06:48 PM    <DIR>          Minidump
02/06/2019  09:11 PM    <DIR>          ModemLogs
04/11/2018  06:34 PM           245,760 notepad.exe
02/10/2019  07:41 PM         3,132,848 ntbtlog.txt
01/10/2019  12:51 AM             1,951 NvContainerRecovery.bat
01/11/2019  06:06 AM             1,951 NvTelemetryContainerRecovery.bat
02/06/2019  09:13 PM    <DIR>          OCR
02/06/2019  09:11 PM    <DIR>          Offline Web Pages
02/06/2019  08:26 PM    <DIR>          Panther
02/06/2019  09:11 PM    <DIR>          Performance
02/06/2019  10:07 PM               566 PFRO.log
02/06/2019  09:11 PM    <DIR>          PLA
02/06/2019  09:13 PM    <DIR>          PolicyDefinitions
02/10/2019  07:13 PM    <DIR>          prefetch
02/06/2019  09:53 PM    <DIR>          PrintDialog
02/06/2019  09:14 PM    <DIR>          Provisioning
04/11/2018  06:34 PM           336,384 regedit.exe
02/06/2019  09:11 PM    <DIR>          Registration
02/06/2019  09:11 PM    <DIR>          rescache
02/06/2019  09:11 PM    <DIR>          Resources
02/06/2019  09:11 PM    <DIR>          SchCache
02/06/2019  09:11 PM    <DIR>          schemas
02/06/2019  09:11 PM    <DIR>          security
02/06/2019  09:53 PM    <DIR>          ServiceProfiles
02/06/2019  09:11 PM    <DIR>          ServiceState
02/06/2019  09:13 PM    <DIR>          servicing
02/06/2019  09:14 PM    <DIR>          Setup
02/06/2019  10:07 PM            19,148 setupact.log
02/06/2019  09:43 PM                 0 setuperr.log
02/06/2019  09:14 PM    <DIR>          ShellComponents
02/06/2019  09:14 PM    <DIR>          ShellExperiences
02/06/2019  09:11 PM    <DIR>          SKB
02/06/2019  08:26 PM    <DIR>          SoftwareDistribution
02/06/2019  09:11 PM    <DIR>          Speech
02/06/2019  09:11 PM    <DIR>          Speech_OneCore
04/11/2018  06:34 PM           130,560 splwow64.exe
02/06/2019  09:11 PM    <DIR>          System
02/06/2019  09:10 PM               219 system.ini
02/06/2019  11:05 PM    <DIR>          System32
02/06/2019  09:11 PM    <DIR>          SystemApps
02/06/2019  09:11 PM    <DIR>          SystemResources
02/06/2019  11:05 PM    <DIR>          SysWOW64
02/06/2019  09:11 PM    <DIR>          TAPI
02/10/2019  07:16 PM    <DIR>          Tasks
02/10/2019  07:16 PM    <DIR>          Temp
02/06/2019  09:14 PM    <DIR>          TextInput
02/06/2019  09:11 PM    <DIR>          tracing
02/06/2019  09:11 PM    <DIR>          twain_32
04/11/2018  06:34 PM            65,536 twain_32.dll
02/06/2019  09:11 PM    <DIR>          Vss
02/06/2019  09:11 PM    <DIR>          WaaS
02/06/2019  09:11 PM    <DIR>          Web
02/06/2019  09:10 PM                92 win.ini
02/07/2019  07:10 PM               276 WindowsUpdate.log
04/11/2018  06:34 PM            11,776 winhlp32.exe
02/06/2019  09:54 PM    <DIR>          WinSxS
04/11/2018  06:33 PM           316,640 WMSysPr9.prx
04/11/2018  06:34 PM            11,264 write.exe
              24 File(s)    572,470,782 bytes
              74 Dir(s)  466,084,450,304 bytes free

C:\Windows>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.556

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows>chkdsk /scan
The type of the file system is NTFS.
This service cannot be started in Safe Mode

A snapshot error occured while scanning this drive. Run an offline scan and fix.

C:\Windows> wmic RecoverOS set AutoReboot = False
Updating property(s) of '\\DESKTOP-O0Q329Q\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\Windows>

Will have to start the chkdsk process in regular Windows. I'm having trouble uploading my zip of the memory.dmp. I'll work on getting that to you, as for the rest, it will take a bit of time (obviously) to run through. For the record the sfc scan found that rspndr.sys file I replaced and that was it.

xekushnr · 10 Feb 2019

Code:

Microsoft Windows [Version 10.0.17134.556]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  581632 file records processed.
File verification completed.
  40476 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  149 reparse records processed.
  642366 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  149 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  30368 data files processed.
CHKDSK is verifying Usn Journal...
  38471208 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 487391341 KB total disk space.
  31847476 KB in 106777 files.
     80756 KB in 30369 indexes.
         0 KB in bad sectors.
    722817 KB in use by the system.
     65536 KB occupied by the log file.
 454740292 KB available on disk.

      4096 bytes in each allocation unit.
 121847835 total allocation units on disk.
 113685073 allocation units available on disk.

C:\WINDOWS\system32>

zbook · 10 Feb 2019

The scannow command result displayed corruption of the operating system that was repaired:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

By default Windows will overwrite the memory dump.
So immediately after a BSOD save the memory.dmp so it does not disappear with the next crash.

Open administrative command prompt and type or copy and paste:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

Find the new file on the desktop > zip > post a share link into the thread