Fall Creators Update random reboots WHEA_UNCORRECTABLE_ERROR (124)

dancedar · 01 Nov 2017

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:

axe0 · 01 Nov 2017

Hi dancedar,

Dumps cannot be directly uploaded, which is why the log collector is available :)

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.

dancedar · 01 Nov 2017

axe0 said:

Hi dancedar,

Dumps cannot be directly uploaded, which is why the log collector is available :)

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!

sowen · 08 Nov 2017

dancedar said:

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.

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."

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.

dancedar · 08 Nov 2017

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 http://www.osronline.com/page.cfm?name=Analyze 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

axe0 · 08 Nov 2017

BSOD Posting Instructions & How to upload files

dancedar · 08 Nov 2017

Uploaded in requested way :)

axe0 · 08 Nov 2017

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.

dancedar · 08 Nov 2017

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?

axe0 · 08 Nov 2017

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.