Windows 10: Fall Creators Update random reboots WHEA_UNCORRECTABLE_ERROR (124)

As titled, I'm getting random, instant reboots after I've installed the Fall Creators Update.
I'm all backed up via Macrium & Syncbackpro, no illegal soft installed, win 10 pro, and have recently just finished setting up a fresh install from the GB x64 1709 FCU iso - fresh system install. I don't get any bsod as such, just one minute I'm copying a file/in chrome/anything, the next the pc is booting up again.

Minidumps linked - (forum upload says 'invalid file': Dropbox - Crash

Main readable info seems to be:
BUGCHECK_STR: 0x124_AuthenticAMD

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

and

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

DM Log collector: Dropbox - Crash

Specs:
AMD A10-8700) Radeon R6, 10 Compute Cores 4C+6G 1.8GHz8GB RAM64-bit Windows Pro 1709, 16299.19
Win & apps on C: 50gb, user data on E:

:)

 

Random disconnections are happening on my computer. Event 41, Kernel Power.

Same issue here with an HP 705 G2 running Windows 10 Creators Fall x64.

Drilling down into the crash dump I get

WHEA_UNCORRECTABLE_ERROR (124)

Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)

Status : 0xf2000010000b0c0f

I have run HP's extensive diagnostic test overnight (3 hours per test) without failure.

Updating the chipset driver, video driver (both AMD) and BIOS seems to have fixed it.

Looks like an AMD driver related issue with Creators Fall update, even though these bluescreens usually point towards a hardware problem.

*Edit*

2 days later and the PC was still crashing.

Had to reinstall Windows 10 fresh.

 

WHEA_UNCORRECTABLE_ERROR (124)

We disagree. Over 60 is too warm. Have you removed dust bunnies?

Please upload no more than three copies
of your dump files that were created during the last 14 days as shared files to your OneDrive with a link here.




Dump files are usually found at c:\windows\minidump. You may need to change your settings in Windows to be able to see the files. To show hidden files select the keyboard shortcut
Win+S, type File Explorer Options in the Search box and click Folder Options in the drop down menu. Select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and
"Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.



What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please, HTML files are less easy
to work with.

DriverView: Loaded Windows Drivers List



Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut
Win+R, type msinfo32 and press the ENTER
key. Select File, Export and give the file a name noting where it is located.
Files in the txt file format are preferred. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information
is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here.



Please upload to your OneDrive and share with everyone a copy of your
System log file from your Event Viewer and post a link here. Please remove any earlier copies of the logs from your OneDrive.



To access the System log select the keyboard shortcut Win+R, type
eventvwr.msc and press the ENTER key. From the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and
Save All Events as (the default evtx file type) and give the file a name. Do not provide filtered files.
Do not place the cursor in the list of reports before selecting Action from the menu. Do
not clear logs whilst you have a continuing problem.



For help with OneDrive see paragraph 9.3:

gerrys template

 

Hi dancedar,

Dumps cannot be directly uploaded, which is why the log collector is available *Smile

Any chance you have used disk cleanup or similar tools? There's only 1 dump present and this specific crash requires more dumps for a proper analysis.

 

Oh darn, I didn't think about that, I have, yes. Guess I'll have to wait for it to crash a few more times before re-running the log collector tool, thanks for the info!

 

I'm having the same problem - random instant reboots with no BSOD - and no entries in the Event Log other than when the system starts up it logs the critical event Code: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."[/quote] I have now enabled miniboots. I have a suspicion it has something to do with the display hardware (AMD Radeon HD 8570D) and/or hardware acceleration, however: I have the latest driver (15.201.1151.1008), I fully uninstalled and re-installed the driver, and I disabled hardware acceleration in Chrome and Thunderbird, none of which has helped.

 

Had my next one just now - same instant reboot while I was in Chrome with Lightroom running pretty hard in the background updating my image catalog. I did note that when it started up again it said 'Configuring Windows updates, don't turn off computer', and I think it did this last time, despite no updates installed since my last update check and this reboot.

Any help would be greatly appreciated, as I can't discern what's wrong using Instant Online Crash Analysis to analyse the logs.

If there are any other logs/tools I can upload/use I'm happy to be guided!
I've run sfc /scannow and dism /online /cleanup-image /restorehealth and both were fine, no errors.

Edit: log zip attached now

 

How to upload files

 

Uploaded in requested way *Smile

 

The CPU noticed, in both dumps, that there was no timeout between data A and data B.

Check Toshiba for BIOS updates and run driver verifier if there are no updates or if the update doesn't help.







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.

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.

 

I updated the BIOS last week, just in case.
Running the Driver Verifier tool now, it seemed to load the cpu up pretty well, but now my laptop is idling away doing nothing, should it be stressing the drivers constantly somehow or should I just wait for it to crash again ?In Verifier, all drivers are returning a 0 on testing so far and no fails. I'll leave my computer running and idling and see what happens - or would I be best to try and load up the stress by using heavy apps?

 

Driver verifier validates the selected actions on the selected drivers, if a driver performs an action that was selected driver verifier takes control and checks if everything goes properly. If it doesn't a crash occurs. This could slow down performance drastically.

Use your pc as you normally would while driver verifier is on.

 

Looks like it might be this:
https://answers.microsoft.com/en-us/...=1510227499530

 

@sowen, the problem you link is a different problem, the user in the thread you link doesn't get any BSOD.

 

The first post in this thread says s/he also doesn't get a BSOD, and neither do I.