Windows 10: BSOD Error with 5010 , 6155 , 10016 logs attached here windows 11

Source: Netwtw08Date: 09-08-2024 22:44:52Event ID: 5010Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: LAPTOP-4HHELD19Description:IntelR Wireless-AC 9560 : The network adapter has returned an invalid value to the driver.Event Xml:<Event xmlns="http://schema

:)

 

BSOD: 10016, 6062, and 6155 Errors

Hi,

My computer has been freezing and then progressing to BSOD for the past three weeks since I updated Windows 11. I noticed Event IDs 10016, 6062, and 6155 warnings all around the time of the issues. After reading several posts, updating network adapter drivers, and running a clean install, I still have the issue.

I can't seem to attach the minidump file from today's crash so please use the following link.

Below are the specs:

Device name Legion

Processor Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz

Installed RAM 80.0 GB (79.7 GB usable)

Device ID 25C22060-5BF3-48C2-8AD9-B14127ADDD49

Product ID 00325-81920-75181-AAOEM

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Below is the Window specifications:

Edition Windows 11 Home

Version 22H2

Installed on ‎10/‎14/‎2023

OS build 22621.2428

Experience Windows Feature Experience Pack 1000.22674.1000.0

Any help would be greatly appreciated.

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

DCOM error 10016

Hello one of your suggestions seems to have worked for a bit then i got a bluescreen think it was watchdog clock timeout the BSOD was labled as a dcom error 10016

then the problems started again