Lately, I have been experiencing multiple blue screens of deaths, game freezes, audio buzzing, complete blackouts of the screen. I have updated to the latest GPU drivers, audio drivers, latest BIOS version but still, I was still unable to resolve any issues.
More info on the specifications of the laptop available here.
I decided to run LatencyMon and try to find out what might be wrong. The output of it is:
There seems to be a problem with my HDAudBus.sys
and wdf01000.sys
. Has anyone encountered similar issues and how I can resolve those? Is this a hardware or software problem?
Multiple errors found in Event Viewer:
- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
- The server Microsoft.SkypeApp_15.64.80.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout.
- The previous system shutdown at 2:10:58 AM on 10/26/2020 was unexpected.
- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
- Dump file creation failed due to error during dump creation.
- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.
- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the sppsvc service.
- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000094, 0xfffff8057cd9764d, 0xfffff608a99f61f8, 0xffffa38098ceb930). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 805c74e4-3874-4499-8ffc-c036b8daf8ce.
- The Origin Web Helper Service service failed to start due to the following error: The system cannot find the file specified.
(26-11-2020) Brand new error:
Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.
The symptoms:
Conclusion: The disk is dead and needs to be replaced.
(I had this suspicion already, but full testing was required before giving
such an answer.)
User contributions licensed under CC BY-SA 3.0