Question WATCHDOG_VIOLATION bug check has a value of 0x00000133.

Mar 29, 2020
2
0
10
Hi,

I have a fx6300(300mhz OC),GTX650, 16GB DDR, 550W(350w 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 controllers(AMD 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>
 
Last edited:
Mar 29, 2020
2
0
10
Update

Based on the analysis of the dump files, I see that the Blue Screens are caused by the file wisetdifw64.sys, and this is related to Wise Cleaner.

36 hours later the system is stable.

Solved