Windows 10: WATCHDOG_VIOLATION bug check has a value of 0x00000133.

Hi,

I have a fx6300300mhz OC,GTX650, 16GB DDR, 550W350w max load PC and I am getting BSOD from time to time with WATCHDOG_VIOLATION bug 0x00000133.


I updated my GPU and IDE ATA/ATAPI controllersAMD PCI IDE controller and АMD SATA controller. Did not help.


BlueScreenViewer says its caused by ntoskrnl.exe and hal.dll drivers.

Here are the minidump files

https://www.dropbox.com/s/bauph0jg6zjfcp2/032720-7062-01.dmp?dl=0

https://www.dropbox.com/s/wm07pm14s29nypg/032820-6093-01.dmp?dl=0

https://www.dropbox.com/s/l1hiv62glijkfcb/032920-6515-01.dmp?dl=0



This is from EventViewer


Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 29.3.2020 г. 17:53:01
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-U0DOL5T
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff8043e773358. A dump was saved in: C:\WINDOWS\Minidump\032920-5578-01.dmp. Report Id: fcda704c-df2f-4260-bc65-e64c6b3e05d4.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-03-29T14:53:01.443335800Z" />
<EventRecordID>63764</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DESKTOP-U0DOL5T</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000133 0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff8043e773358</Data>
<Data Name="param2">C:\WINDOWS\Minidump\032920-5578-01.dmp</Data>
<Data Name="param3">fcda704c-df2f-4260-bc65-e64c6b3e05d4</Data>
</EventData>
</Event>

:)

 

Bug check error: 0x00000133 on Windows 10

Hi,

Thank you for posting in Microsoft Community and being part of Windows 10.

I understand your concern about accessing your device after performing a bug check, we will help you with this issue.

Do let us know the following to assist you better with this issue:

• Are you able to boot the device to desktop?
• What is the complete error message along with error code of this issue?
• What is the make and model of your device?

If you are able to log-in to the desktop, try few of the below troubleshooting steps and check if it helps.

Step 1: Run Memory Diagnostic Tool.

Follow the below steps:

• Press Windows key and type
  Memory Diagnostic.
• Select Windows Memory Diagnostics
  and click on Restart now and check for problems.
• Follow the on-screen instructions.

Step 2: Run the Power Troubleshooter


Power troubleshooter find and fix problems with your computer's power settings to conserve power and extent battery life

• 
  Type Troubleshooting in the
  Search bar on the desktop and press Enter.
  
• 
  In the Troubleshooting window, click on
  View All on the left pane.
  
• 
  Click on Power.
  
• 
  Click Next and follow the on-screen instructions to complete the troubleshooting process.
  

Step 3: I suggest you to check for the pending updates on your device install them and check if it helps.

Steps:

• Connect to the internet.
• Press Windows key and type
  updates.
• Click on Check for updates.
• Under Windows Updates, click on
  Check for updates.
• Try to install the updates being shown.

Hope it helps. Kindly update the status of this issue, we will be happy to assist you further.

 

Bug Check Code: 0x00000133 - ntoskrnl.exe+149f90

More details here:

https://social.technet.microsoft.com/Forums/en-...

 

BSOD, Bug check code 0x00000133, caused by driver hal.dll

Lenovo ThinkPad with Intel i-7 processor, 8GB RAM, Windows 10 professional edition, suddenly crashed with BSOD, Bug check code 0x00000133, caused by driver hal.dll

Attached is the minidump file.

Any hints an to what might have caused the problem ?