Root Cause of BSOD Troubleshooting using Event Viewer ID

Orlando Thompson 0 Reputation points
2024-02-06T20:31:06.1933333+00:00

We have "Blue screening" since December 2023. Initial investigation shows "bug check" It is unique to only this server in our stack currently "Windows Server 2016". We looked in the event viewer under Windows Logs, System and created a customer view filtering on Critical, Warning, Error and are finding thousands of Warnings with Event ID 196 See screenshot for details of these events.

User's image

Under Details Tab
User's image

Can you help me identify root cause and possible resolution for this issue. I believe it is causing us BSOD issues.

Thanks for all your help and support in this matter, Orlando

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Michael Taylor 60,331 Reputation points
    2024-02-06T21:07:39.9366667+00:00

    It appears you have a USB device that is not going into the power down state when idle which is causing a drain. Whether this is causing your BSOD or not is difficult to say without looking at the crash dump.

    It is possible you have a bad USB device that just needs to be replaced but start by checking your power options first. Some suggestions online recommend the following. Since we don't know what you might or might not have changed you should reset to default settings first.

    • powercfg -restoredefaultschemes and then reboot.
    • Run the Power Troubleshooter to see if it fixes anything and then reboot.
    • Go to the Power Options and, at least for a server, don't allow sleep or hibernation.
    • Personally I also had issues with slow (or hung) restarts so I disabled Fast Startup as well.
    • Remove the USB device in question and see if the BSOD issues go away.
    0 comments No comments

  2. Anonymous
    2024-02-08T06:23:57.19+00:00

    Hello, Few steps you could check in the link below: Event ID 196: How to Fix This USB3 Power Draining Error (windowsreport.com) Meanwhile, you could check the system event log about event id 41,6008. It always records the BSOD bugcheck code. Best Regards, Hania Lian

    If the Answer is helpful, please click "Accept Answer" and upvote it.


    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.