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

Hi there,

My system is facing problems with an intermittent machine_check_exception BSOD during the OS boot, after I recently replaced my motherboard and reinstalled Windows. The BSOD screen states it will restart for me, but never does. When normally booting up, my system disconnects all USB devices and reconnects them shortly after Win10 logo and spinning circle appear, but on an unsuccessful boot the BSOD appears right when the devices are due to reconnect (driver conflict?), leaving them disconnected. I am aware others have faced the same stop code for reasons of either hardware or driver failure/malfunction. Most examples of this BSOD happen either at random inside the OS or during games from what I have read elsewhere.

The crashes occur on roughly 2 out of every 3 attempts to boot/restart the system. When I finally make it into the OS and log in, everything seems to work perfectly fine, including CPU and GPU benchmarks. I have also run the Memtest USB bootable and it found no issues relating to memory, along with Intel's Processor Diagnostic Tool. No driver errors shown in device manager.

I heard on another post that overclocking utilities such as AI Suite can cause this issue. I uninstalled the program and disabled all overclocks, but the problem persisted. My CPU core temps at both idle and under load are perfectly fine (Noctua NH-D15 cooler, 30C idling). So after all my efforts to troubleshoot, I am beginning to suspect either a potential fault with new motherboard, or perhaps a driver conflict with one of my USB devices.

Can anyone tell me anything from crash dumps? Also, this is my first time using TenForums, so sorry for any noob errors!



:)

 

MACHINE_CHECK_EXCEPTION on bootup after install

Hello.

I sadly have a problem with Windows 10's installation.

Back in July I installed Windows 10 on a third partition to dual boot it alongside a Windows 7 installation, tried to boot it up, and it did everything it was supposed to, but after telling me that it wanted to reboot, the screen
went black and hard drive activity went zero. It then came up with a bluescreen - MACHINE_CHECK_EXCEPTION. After pressing the power button for 10 seconds and restarting, it went as far as the loading screen telling me to "Please wait....", but then the same
result. I decided to delete Windows 10 and go with Windows 8.1 then.

Fast forward to today, I decided to delete the Windows 8.1 partition and try it again with Windows 10. The exact same result. However, after the "Please wait", not even a BSoD decided to show up.

I tried to look into the partition of Windows 10 to search for any logs relating to that BSoD, but i couldn't find any.

Please help me, I really want to try some of the new Win10 features.

Thanks in advance.

UPDATE: After updating my BIOS, there's a new crash message: CLOCK_WATCHDOG_TIMEOUT, but otherwise everything's the same.

 

Windows 10 Feature Update 1709.

Update!

After a successful afternoon, during which I continued to install apps on my system, I started getting BSOD again! I had just installed a blue tooth enabling device into a USB slot and paired it with my Anker Soundcore speaker. I have since uninstalled
these, and the BSOD seem to have stopped again. The BSOD component was FLTMGR.SYS.

While I was reading up on this, it occurs to me that my Asus M2N-SLI deluxe motherboard might not fully support the x64 version of W10 that I have installed, although everything else seems to be working OK. Is there any way I can update this motherboard
- new BIOS, new drivers?

Alan

 

Hello Spoochung,

There is only one crash dump file in the logs and it is not a Machine Check exception so I suspect that these BSODs are not being written to a dump file when they occur, probably because they are happening at the bootup stage.

You could try turning off fast startup to see if it makes a difference.

 

Thanks for the suggestion, late last night I tried resetting BIOS to optimised default settings (despite no OC), and that seemed to fix the machine check exception BSODs at boot from what I can tell after about 5 successful cold boots and restarts.

However, not long after this I received the different stop code USB_driver_power_state_failure while on the desktop, which restarted the system. By instinct I checked device manager for any issues with my USB devices, and found "unknown USB device (device descriptor request failed)" in the Universal Serial Bus Controller tab (provided screenshot). I have identified that this appears to be a conflict with my USB audio interface (Focusrite Scarlett 2i4 1st gen) as the message goes away when I disconnect the device, which is connected to my rear USB ports via an external powered USB 3.0 hub. I tried to uninstall the driver, restart, plug it back in, and it worked fine until I booted up my system today. I also have a web cam plugged into the hub, so would this mean the audio interface box is faulty/incompatible with my setup? Or could it still be caused by the hub? (note I haven't had the BSOD relating to this since last night, it's just the driver error I am concerned about for now)

 

Upload another set of logs, we'll want to take a look at the crash dumps generated from the power state bugchecks.

Regarding the USB device, what error is shown in device manager?

 

The error can be seen in the last attachment image, stating " Unidentified USB Device (device descriptor request failed)". I have attached the details of the error and a new log file.

 

One crash dump from the 6th is corrupted (has 0 size on disk), so I was only able to look at one of the two new crashes.

It did show that your FocusRite USB driver was responsible for blocking the Power IRP, which then caused the power state failure.

Code: Irp is active with 25 stacks 24 is current (= 0xffffb3071865d758) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [Truncated for brevity] [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)] 0 0 ffffb307165ec060 00000000 fffff80b66146a70-ffffb307165bb5a0 \Driver\USBHUB3 UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion Args: 00000000 00000000 00000000 00000002 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)] 0 0 ffffb307165ec060 00000000 00000000-00000000 \Driver\USBHUB3 Args: 00000000 00000000 00000000 00000002 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffb307167ab040 00000000 fffff80130151ed0-ffffb30717d8c180 Success Error Cancel pending *** WARNING: Unable to verify timestamp for FocusriteUSB.sys *** ERROR: Module load completed but symbols could not be loaded for FocusriteUSB.sys \Driver\FocusriteUSB nt!PopRequestCompletion Args: 00051100 00000001 00000001 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffffb30717d8c180 Args: 00000000 00000000 00000000 00000000[/quote]
Have you checked on FocusRite's website for a newer driver? This looks to be their download page: Downloads | Focusrite

 

Thank you for looking into this for me. I have already tried updating to the driver from their site, and I made sure to get the 2i4 Gen1 driver rather than the one for the Gen2 model. Faulty box perhaps?

 

It could be a hardware issue for sure, it could also be that their driver is faulty and they do not want to spend money fixing/updating software for an older device.

 

I might see about trying to contact either Focusrite or the place where I got it from in that case (may be just out of the warranty period), and I'll also try plugging it directly into my PC with the hub taken out of the equation. The fact that it's an externally powered hub might cause issues with some but not all devices I suppose. If everything else remains stable for the next 48 hours I'll make sure to mark the thread as solved!

Thanks for all your help, wish I knew my stuff as well as you guys!

 

Update: I have plugged my audio interface into one of the rear ports and all appears to be fine and dandy now. But...
I have been setting up my BIOS settings since I had reset them to default while troubleshooting. I'm not doing any OCing at this stage as I want the system to be confirmed to be stable before I even think about that. The settings I am tweaking are purely to speed up boot time, as boot up times on the X99 platform can be quite a drag at stock settings.
So... I tweaked one setting at a time, no problems until disabling CSM, at which point the next reboot resulted in the same BSOD I created this thread to solve (MCE). Therefore it would seem that the root of the problem might have been caused by this setting in particular? Please let me know what you think. I have attached another log just in case the BSOD created a dump this time around.

 

For the focusriteusb there are 4 drivers on the computer that have that as a part of the name.

The first one displayed below was the faulting driver
Code: focusriteusb Focusrite USB c:\windows\system32\drivers\focusriteusb.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] Code: focusriteusbaudio Focusrite USB Audio c:\windows\system32\drivers\focusriteusbaudio.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] Code: focusriteusbmidi Focusrite USB MIDI c:\windows\system32\drivers\focusriteusbmidi.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] Code: focusriteusbswroot USB Audio Root c:\windows\system32\drivers\focusriteusbswroot.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] 1) Open device manager and click view > show hidden devices > expand any category that displays a yellow triangle with a black exclamation mark.
Post an image into the thread.
2) for each triangle please click on the driver and the details tab and post an image of each into the thread.
3) update all bluetooth drivers as there were multiple entries displaying that the bluetooth adapter failed.
This may be the faulty driver:
Code: bthusb Bluetooth Radio USB Driver c:\windows\system32\drivers\bthusb.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] 4) open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /restorehealth
7) chkdsk /scan
8) 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
9) Update the Focusriteusb driver: Downloads | Focusrite
10) once the bsod have been fixed the fastest boot times can be achieve by clean boot.



Updating a driver: Updating a driver. - Microsoft Community



DeviceInst is "USB\VID_1235&PID_800A\7&309eb436&0&4"
ServiceName is "FocusriteUSB"



Code: 06/10/2017 02:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb307165ec060 P4: ffffa080d59f78f0 P5: ffffb3071865d010 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100617-20296-01.dmp \\?\C:\Windows\Temp\WER-21015-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61F7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61F8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6208.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_ff8caad46e72e5684c2c7c9795283c5ac7b525_00000000_cab_11cc65af Analysis symbol: Rechecking for solution: 0 Report ID: 651f6249-62e9-4b98-b19f-64a2cf26a1e5 Report Status: 2049 Hashed bucket:06/10/2017 02:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffb307165ec060 P4: ffffa080d59f78f0 P5: ffffb3071865d010 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100617-20296-01.dmp \\?\C:\Windows\Temp\WER-21015-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61F7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61F8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6208.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_ff8caad46e72e5684c2c7c9795283c5ac7b525_00000000_03c46205 Analysis symbol: Rechecking for solution: 0 Report ID: 651f6249-62e9-4b98-b19f-64a2cf26a1e5 Report Status: 4 Hashed bucket:05/10/2017 00:22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffc28cf8ef8080 P3: 0 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100517-13109-01.dmp \\?\C:\Windows\Temp\WER-13937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49AC.tmp.txt These files may be available here: Analysis symbol: Rechecking for solution: 1 Report ID: 30a6fd73-ec50-4db4-984b-2b59ec5b6c49 Report Status: 2049 Hashed bucket:04/10/2017 23:32 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffc28cf8ef8080 P3: 0 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100517-13109-01.dmp \\?\C:\Windows\Temp\WER-13937-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49AC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_6347a2c1d1f711de9131dc9e7cb1110b14e9da4_00000000_cab_14844c7a Analysis symbol: Rechecking for solution: 0 Report ID: 30a6fd73-ec50-4db4-984b-2b59ec5b6c49 Report Status: 2049 Hashed bucket:04/10/2017 23:32 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffc28cf8ef8080 P3: 0 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100517-13109-01.dmp \\?\C:\Windows\Temp\WER-13937-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49AC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_6347a2c1d1f711de9131dc9e7cb1110b14e9da4_00000000_038c49ab Analysis symbol: Rechecking for solution: 0 Report ID: 30a6fd73-ec50-4db4-984b-2b59ec5b6c49 Report Status: 4 Hashed bucket:[/quote]



Code: Event[3975]: Log Name: System Source: BTHUSB Date: 2017-10-06T22:21:53.028 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]

 

Sorry to have to present a further update here, but I just experienced another kind of crash. All system settings are on default with no OC still, even BIOS settings are default. I was playing Playerunknowns's Battlegrounds for about an hour without issue, when I ran to the top of a hill and someone started firing at me. The first half sniper sound was very loud and whistle-like (which is how it is meant to sound), but it transitioned into some sort of a screech, then everything froze, no blue screen, lights on all my USB devices remained on but it's safe to say the whole OS crashed. What on earth is going on? I've attached another log... *cry

 

And I only just saw your post, I will also try all of those steps while someone gets back to me on my previous message (thank you for the instructions and help).