KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider

dencal, this is an eample of what I include to Microsoft if I get a BSOD/GSOD.

I just created one to show you by using an ustable OC and running a benchmark I knew would crash Windows

Code:

Crash Dump Analysis

Crash dump 
directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your 
computer.

On 
Fri 13-Apr-18 16:53:58 your computer crashed
crash dump file: 
C:\WINDOWS\Minidump\041318-9250-01.dmp
This was probably caused by the 
following module: Unknown 
() 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as 
the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Fri 13-Apr-18 16:49:10 your computer 
crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably 
caused by the following module: cinebench_windows_64_bit.sys 
(CINEBENCH_Windows_64_Bit+0x67EC21) 
Bugcheck code: 0x20001 (0x13, 0x0, 
0x29B92701, 0xFFFFE80000A5A258)
Error: HYPERVISOR_ERROR
Bug check description: The 
hypervisor has encountered a fatal error.
A third party driver was identified 
as the probable root cause of this system error. It is suggested you look for an 
update for the following driver: cinebench_windows_64_bit.sys . 
Google 
query: cinebench_windows_64_bit.sys 
HYPERVISOR_ERROR






Conclusion


2 crash dumps 
have been found and analyzed. A third party driver has been identified to be 
causing system crashes on your computer. It is strongly suggested that you check 
for updates for these drivers on their company websites. Click on the links 
below to search with Google for updates for these drivers: 

cinebench_windows_64_bit.sys 

If no updates for 
these drivers are available, try searching with Google on the names of these 
drivers in combination with the errors that have been reported for these 
drivers. Include the brand and model name of your computer as well in the query. 
This often yields interesting results from discussions on the web by users who 
have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for 
more information. 

Note that it's not always possible to state with 
certainty whether a reported driver is responsible for crashing your system or 
that the root cause is in another module. Nonetheless it's suggested you look 
for updates for the products that these drivers belong to and regularly visit 
Windows update or enable automatic updates for Windows. In case a piece of 
malfunctioning hardware is causing trouble, a search with Google on the bug 
check errors together with the model name and brand of your computer may help 
you investigate this further. 

dencal said:

The problem being from my point of view any suggestions made might have unfortunate effects repercussions on other parts of the O/S....an example look at the mess created by the last Release Preview Update.

When a BSOD or GSOD occurs MS is notified and will ask you what Happened. I have time and time again responded and when they wanted my email addy, I provided it. In 3 1/2 years in this program I have yet to get a reply. That to me is one hell of a way to run a railroad.

This is what I reported on Feedback Hub....I think M$ would have a better understanding of their own format for solving bugs than using software from an outside source.

Update:

Sorry but it doesn't look like we'll have another build for the Fast ring (not Skip Ahead) for a little while still.

Tweet

— Twitter API (@user) View on Twitter

Brink said:

Update:

Tweet

— Twitter API (@user) View on Twitter

Thanks Shawn so in effect he is acknowledging that Zab Bowden's comments were accurate.

kjlkjadfasdfasd said:

I can't help but think for them to take this step that the bug has something to do with data loss/corruption.

Or security.

kjlkjadfasdfasd said:

I can't help but think for them to take this step that the bug has something to do with data loss/corruption.

Who know as if you look in the Hub under Announcements, this build 17133.1 has no known issues

It's running without issue on my three AMD processor systems - Maybe it's an Intel Issue Just thought I throw my guess into the lottery

Delivery/installation blocking something. Software itself (the build) may have no known issues, but getting it out and installed may be breaking things. Release Preview getting 17133 hit a whole ton more machines of unknown ancestry!