machine_check_exception BSOD on boot up after new motherboard install

zbook · 06 Oct 2017

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

Code:

focusriteusbaudio    Focusrite USB Audio    c:\windows\system32\drivers\focusriteusbaudio.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes

Code:

focusriteusbmidi    Focusrite USB MIDI    c:\windows\system32\drivers\focusriteusbmidi.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes

Code:

focusriteusbswroot    USB Audio Root    c:\windows\system32\drivers\focusriteusbswroot.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes

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

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:

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.

Spoochung · 06 Oct 2017

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

Spoochung · 06 Oct 2017

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

Spoochung · 06 Oct 2017

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 347136 file records processed.File verification completed. 17697 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 420736 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 36801 data files processed.CHKDSK is verifying Usn Journal... 41880168 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 232964852 KB total disk space. 70462260 KB in 147498 files. 114160 KB in 36802 indexes. 0 KB in bad sectors. 468160 KB in use by the system. 65536 KB occupied by the log file. 161920272 KB available on disk. 4096 bytes in each allocation unit. 58241213 total allocation units on disk. 40480068 allocation units available on disk.C:\WINDOWS\system32>

Spoochung · 06 Oct 2017

I've reinstalled the focusrite and bluetooth drivers succesfully, and it looks like they're working fine for now. I checked event viewer and at the moment there are no more error reports for the bluetooth adapter. There were no exclamation mark triangles to show you in device manager even with show hidden devices enabled. Thank you for your patience and assistance once again.

Now I just need to work out what the in-game crash was all about... I've had crashes like that previous to my motherboard replacement, and I even replaced my PSU at one point relating to that same crash scenario. So the only things in my system that have not been replaced are the CPU, RAM modules, GPU and SSD+HDD. Obviously replacing some of those could get expensive beyond worth and I don't have parts I can substitute them with, so what are my next steps? I don't think throwing it out of the window will work, even if they do call it Windows...

zbook · 06 Oct 2017

There were some mini dumps that were not created from the dump file.

Code:

Unable to produce a minidump file from the full dump file.

Please post a share link with the memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMPUse file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

Spoochung · 06 Oct 2017

Got the memory dump file, but I think the file attachment system didn't like the file size so I zipped it and uploaded to my Google drive: MEMORY.rar - Google Drive

zbook · 06 Oct 2017

The memory dump dubugging displayed another misbehaving driver.

Please uninstall Avast.
Avast Uninstall Utility | Download aswClear for Avast Removal
Turn on Windows defender.

aswStm.sys

avast! Antivirus Stream Filter driver

http://support.avast.com/

Spoochung · 06 Oct 2017

Okay, Avast cleaned up and Win Defender turned back on. Do you consider it possible that Avast could have been the cause a crash in-game? It would certainly make sense to me from a timeline perspective, as I have been using Avast for well over 2 years now and all the while putting up with the annoyance of these crashes.

zbook · 06 Oct 2017

With the recent fixes time is needed now to evaluate the computer environment.