New
#1
Watchdog violation assume this is a bsod
Hi,
Okay besides stop oc'ing to all core 48 is there anything meaningful in this ?
Attachment 163071
Code:Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 11/9/2017 8:07:33 PM Event ID: 1001 Task Category: None Level: Error Keywords: Classic User: N/A Computer: masqww-win-10-x299 Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8013b400370, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d7dab68b-f98a-4ecf-b1c0-a2403509d90e. 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="2017-11-10T02:07:33.759286500Z" /> <EventRecordID>8488</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>masqww-win-10-x299</Computer> <Security /> </System> <EventData> <Data Name="param1">0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8013b400370, 0x0000000000000000)</Data> <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data> <Data Name="param3">d7dab68b-f98a-4ecf-b1c0-a2403509d90e</Data> </EventData> </Event>