Disconnect/connect sounds play and then BSOD

[MakSM]

I'm using windows 10 atm and my computer has been recently making connect/disconnect sounds and then just a BSOD. I really want to know how to fix it; I've updated my graphics drivers and there doesn't seem to be any buggy drivers so i'm really not sure whats causing it?

Graphics Card: AMD r9 380
Processor: intel i5 4440 (i think)
Ram: 8gb

if more info needed i'll be sure to look for it just dont really think it's that important atm

 

[Colif]

Can you download and run who crashed: http://www.resplendence.com/whocrashed
it will produce a summary of the BSOD and maybe show us the cause

Copy/paste results here.

That sound makes me think its likely to be your motherboard or USB drivers, though it could also be a USB device itself.

 

[MakSM]

Can you download and run who crashed: http://www.resplendence.com/whocrashed
it will produce a summary of the BSOD and maybe show us the cause

Copy/paste results here.

That sound makes me think its likely to be your motherboard or USB drivers, though it could also be a USB device itself.

On Sun 16/10/2016 13:34:34 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101616-29859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

this has been known to fix that: http://www.thewindowsclub.com/dpc_watchdog_violation-blue-screen-in-windows-10

 

[MakSM]

this has been known to fix that: http://www.thewindowsclub.com/dpc_watchdog_violation-blue-screen-in-windows-10

I haven't had an issue yet so I'll label it as solved then. Thanks so much man!