Computer freezes with buzzing sound on freshly installed Win 10 2004.

Happened again

Did you find something new in the dump file, guys? @cwsink @philc43
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

I was not able to find anything that really helps in the crash dump that was created on Nov 2.

The only processes that seemed to be occurring prior to you initiating the crash were USB related.

Code:

STACK_TEXT:  
fffff805`6aa6adf8 fffff805`74044170     : 00000000`000000e2 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff805`6aa6ae00 fffff805`74043a7f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kbdhid!KbdHidProcessCrashDump+0x1f0
fffff805`6aa6ae40 fffff805`73a04cac     : ffffb48c`3a81bc20 ffffb48c`394f327c 00000000`00000000 fffff805`73a08110 : kbdhid!KbdHid_InsertCodesIntoQueue+0xbf
fffff805`6aa6aea0 fffff805`73a04e0a     : ffff901e`000000c6 ffffb48c`3afc5000 00000000`00000000 00000000`00000001 : HIDPARSE!HidP_KbdPutKey+0x44
fffff805`6aa6aed0 fffff805`73a04f87     : ffffb48c`394f327c 00000000`0000000e ffffb48c`3c9e9480 00000000`00000000 : HIDPARSE!HidP_ModifierCode+0x9a
fffff805`6aa6af00 fffff805`73a05083     : ffffb48c`394f3348 ffffb48c`39cd4660 ffffb48c`39cd4660 fffff805`73a03dca : HIDPARSE!HidP_TranslateUsage+0x8b
fffff805`6aa6af50 fffff805`740437af     : 00000000`00000000 ffffb48c`39cd4660 ffffb48c`3a81bc20 fffff805`66c69e80 : HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes+0xb3
fffff805`6aa6afc0 fffff805`66ca1c16     : 00000000`00000000 ffffb48c`48ce9c02 ffffb48c`00000000 fffff805`6aa6b001 : kbdhid!KbdHid_ReadComplete+0x43f
fffff805`6aa6b050 fffff805`66cc310e     : ffffb48c`39cd4660 fffff805`6aa6b109 00000000`00000000 ffffb48c`39cd4bfb : nt!IopUnloadSafeCompletion+0x56
fffff805`6aa6b080 fffff805`66cc2fd7     : 00000000`00000000 ffffb48c`393c5906 ffffb48c`390a5a90 00000000`00000000 : nt!IopfCompleteRequest+0x11e
fffff805`6aa6b170 fffff805`739caef5     : ffffb48c`3c633f28 ffffb48c`39c92102 00000000`00000000 00000000`00000009 : nt!IofCompleteRequest+0x17
fffff805`6aa6b1a0 fffff805`739ca7ed     : ffffb48c`39c921d0 ffffb48c`39c92102 ffffb48c`39c921d0 00000000`00000009 : HIDCLASS!HidpDistributeInterruptReport+0x3f5
fffff805`6aa6b2a0 fffff805`66cc310e     : ffffb48c`39c8c9a0 ffffb48c`39c8c9a0 fffff805`6aa6b301 ffffb48c`39c8ce1b : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff805`6aa6b340 fffff805`66cc2fd7     : 00000000`00000001 00000000`00000000 ffffb48c`39c8ea00 00000000`00000002 : nt!IopfCompleteRequest+0x11e
fffff805`6aa6b430 fffff805`691b811a     : 00000000`00000000 ffffb48c`391a1a30 ffffb48c`39c8c9a0 fffff805`6aa6b510 : nt!IofCompleteRequest+0x17
fffff805`6aa6b460 fffff805`691b5bbf     : ffffb48c`39c4e102 ffffb48c`39c91010 ffffb48c`39c8c9a0 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] 
fffff805`6aa6b4f0 fffff805`7377b91c     : 00000000`ffffff02 ffffb48c`39c4e020 ffffb48c`39c8ede0 ffffb48c`39c8ede0 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 
fffff805`6aa6b550 fffff805`7377b7e1     : ffffb48c`39c4e1c0 00000000`00000008 ffffb48c`39c4e250 fffff805`6aa6b768 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc8
fffff805`6aa6b5b0 fffff805`7377b5d0     : 00000000`00000004 fffff805`6aa6b720 00000000`00000000 ffffb48c`39c8e460 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
fffff805`6aa6b660 fffff805`73776570     : 00000000`00000004 fffff805`6aa6b738 00000000`00000008 fffff805`6aa6b740 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff805`6aa6b690 fffff805`737760a5     : 00000000`00000780 00004b73`c4c37f00 ffffb48c`393d0f60 ffffb48c`39bf8bb0 : USBXHCI!Endpoint_TransferEventHandler+0xb0
fffff805`6aa6b6f0 fffff805`73775d7c     : 00000000`00000002 00000000`00000000 00004b73`c6cd2fd8 00000000`00000001 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff805`6aa6b7f0 fffff805`691b38f5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff805`6aa6b820 fffff805`66ce549e     : fffff805`62792240 00000000`00000000 fffff805`6aa6bb20 fffff805`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa5 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404] 
fffff805`6aa6b860 fffff805`66ce4784     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff805`6aa6b9d0 fffff805`66df810e     : 00000000`00000000 fffff805`6278f180 fffff805`67727600 ffffb48c`3dfd9580 : nt!KiRetireDpcList+0x1f4 
fffff805`6aa6bc60 00000000`00000000     : fffff805`6aa6c000 fffff805`6aa66000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

Alright, I think there is no point in dragging this thread then. I will stop using Google Chrome until they fix the issue. Thanks for everything.

I just want to say that it just happened while using Firefox so I was wrong that it only happens on Chrome. I'm going to get rid of Creative driver/sound card and test On-Board Realtek one... If that doesn't work I'm going to test with different keyboard/mouse.

Ok, so I stopped using the Sound Blaster X-Fi Surround 5.1 Pro and started using the On-Board Realtek for a week now. There are no issues so far.

I just remembered that I spilled some water near the Creative sound card by accident few months ago. I decided to see inside and this is what I can see: https://i.imgur.com/aBI4rBY.jpg

This is a photo that I found on the Internet for comparison: https://i.imgur.com/jdZTIfM.jpg

Do you think this could have anything to do with the issue? @philc43 @cwsink

Can you try cleaning up those components with rubbing alcohol? I'm no expert but that's not what I've typically seen when a component has burned up. Perhaps it's just residue from what got spilled that might be causing a short?

cwsink said:

Can you try cleaning up those components with rubbing alcohol? I'm no expert but that's not what I've typically seen when a component has burned up. Perhaps it's just residue from what got spilled that might be causing a short?

I agree and of course if the board was live when the spillage occurred it might have shorted a component and the damage could all be internal.

cwsink said:

Can you try cleaning up those components with rubbing alcohol? I'm no expert but that's not what I've typically seen when a component has burned up. Perhaps it's just residue from what got spilled that might be causing a short?

I cleaned it up the best I could: https://i.imgur.com/wcNzO9e.jpg

Should I try to use it now or wait some more time to make sure that the problem was caused by the Creative sound card?

philc43 said:

I agree and of course if the board was live when the spillage occurred it might have shorted a component and the damage could all be internal.

Yeah, it was live. I immediately disconnected the usb cable. There was a few drops of water near the volume knob so it's possible that it went down to the board.

I am pretty sure the board was the culprit - it fits with the USB related errors that I saw.

After cleaning it there is a possibility it may work but I would not hold out too much hope. I would wait a while before testing to make sure it is fully dried out after the cleaning.

BTW nice job on the cleaning!

philc43 said:

I am pretty sure the board was the culprit - it fits with the USB related errors that I saw.

After cleaning it there is a possibility it may work but I would not hold out too much hope. I would wait a while before testing to make sure it is fully dried out after the cleaning.

BTW nice job on the cleaning!

Thank you.

It feels good to know what was most likely causing the problem. I will wait for a few days and try to use it again. I'm curious what will happen. Worst case scenario, I will buy a new sound card.