Windows 10: machine_check_exception BSOD on boot up after new motherboard install

In device manager there appears to be a yellow triangle with black exclamation mark for an unknown USB device.
For this listing please click on properties then device and post an image into the thread.

How to easily find drivers for Unknown Devices in Windows | PCWorld
How to Find Drivers for Unknown Devices in the Device Manager

 

@zbook look back at post #3, the OP already knows what that is.

 

In follow up to post #3 it appears that the unknown USB device is a problem device.

This is the information from msinfo32:

Unknown USB Device (Device Descriptor Request Failed) USB\VID_0000&PID_0002\6&1E95266D&0&4 43

The problem device and bsod both appear to be related to Focusrite:

Code: Event[4760]: Log Name: System Source: Microsoft-Windows-UserPnp Date: 2017-10-07T01:43:54.372 Event ID: 20001 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-OFB6ESI Description: Driver Management concluded the process to install driver focusriteusbcustom.inf_amd64_43a2a7a65d33f9e8\focusriteusbcustom.inf for Device Instance ID USB\VID_1235&PID_800A\6&1E95266D&0&4 with the following status: 0x0.[/quote]

 

Yes I'm aware of this. I did a clean install of the drivers for the Focusrite box, it seemed to fix everything in device manager as Focusrite entries were where they should be under the audio and sound tabs. A few reboots later (maybe 3 or 4) I received the BSOD again, and on the next boot the Unknown USB Device appeared. All of this, alongside the returning event viewer errors relating to the bluetooth adapter.

I have contacted Focusrite earlier on, and am waiting on their response. In the meantime I thought I would unplug and clean off all the drivers for it again, and test to see if I still get the in-game crashes from before without the device connected. This will help tell us whether or not we're dealing with one problem (Focusrite causing BSOD and non-BSOD crashing) or many (Focusrite box causing BSOD and something entirely unrelated causing non-BSOD crash).

 

As I suspected, my system just experienced another crash while in-game, no BSOD. The only difference being that my keyboard and mouse disconnected, whereas the light on my HyperX Cloud II soundcard remained lit up.

 

Attached a log file, and the memory dump is available here if needed: MEMORY2.rar - Google Drive

 

The misbehaving driver was again Focusrite.
Now the drivers list no longer display Focusrite.
The event log has continued to display a problem with a bluetooth adapter:

Code: Event[5858]: Log Name: System Source: BTHUSB Date: 2017-10-07T21:22:41.923 Event ID: 17 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-OFB6ESI Description: The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.[/quote]

 

The Bluetooth adapter is located ON the motherboard, or else I would just disconnect it since I don't care much for Bluetooth connectivity on desktop computers.
As for the crash being caused by Focusrite, how is that possible when I'm fairly certain I blitzed all of the drivers? Where should I look if there may still be some residual driver files? The box was disconnected at the time of the crash.

 

[/quote] @zbook you are incorrect - the focusrite driver was not the cause of the crash described in post #33. It was stated that this was not a BSOD so there is no new crash dump file associated with it and as you also noted the focusrite drivers are not listed in the drivers.txt file so it could not have been the cause of the crash. We are dealing with something else that does not trigger a BSOD.

@spoochung The memory dump you posted refers to the previous crash so it does not help in this latest case. Can you tell us any more about what happened - did the system just freeze or did it reboot?

 

It literally just froze. I had to hold down the power button on the case.

 

There are some other sections in this forum that deal with freezes - it would be worth doing a search on these to see if any can help. I'm off to bed now so will let others carry on, may not get back to you until Monday. Hope you can make some progress *Smile

 

Alrighty, thanks man. I'll see what I can dig up.

 

See if there is any performance problems (hangs/freezing/crashes etc.) with hardware stress testing:

1) download and install the Intel Processor Diagnostic Tool

It should take less than 20 minutes to complete.
It has a feature to automatically abort should there be any temperature problems.
It will display pass or fail when it has completed testing.


When the test completes please use the Microsoft snipping tool to post an image into the thread.


Download Intel® Processor Diagnostic Tool:
Download Intel® Processor Diagnostic Tool
The Intel® Processor Diagnostic Tool:
The Intel® Processor Diagnostic Tool

2) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials

Please make note of the importance of temperature monitoring and aborting the test in the GPU link.


FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Performance Maintenance Tutorials


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


For Furmark testing please record maximum temperatures and testing duration.

Aim for 45 - 60 minutes of testing and abort as needed for problems with temperature, freezing, display artifacts, etc.


And please make sure that you use the Microsoft snipping tool to post images of each into the thread.


Take Screenshot in Windows 10 General Tips Tutorials

 

I'll do this tomorrow, it's too late here now do be running benchmarks. Thanks for the suggestions.

 

Okay, I've run both the IPDT and FurMark. No crashes at all, IPDT passed with no issues and stayed 63°C away from max. GPU temperature peaked at 71°C but remained at 70°C for almost the whole test (which I ran for over an hour). Does this pretty much eliminate both CPU and GPU from the troubleshooting or is it still possible that there's an underlying fault with either pieces of hardware?

To give a bit of background, I returned my old revision Corsair model CX750M PSU because I suspected it was potentially causing the issue, but after having the newer revision of the same model installed in my system for a few months now, it's apparent that this did nothing to solve the problem. Likewise, a couple of days before starting this thread I replaced my motherboard from an ASUS X99-S to a more up to date ASUS Strix X99 Gaming mobo and the problem persists.

As for the crashes in question, am I right in thinking that they seem to occur when the system is using a lot of power (games that utilise both CPU and GPU resources heavily)? And should I consider looking more closely at the way I power the system (currently using a surge protected 6 gang power bar plugged into the wall)? Surely a 750W PSU is providing more than sufficient headroom for my system specs...