New
#11
The DCOM error is not unusual, I see it a lot.
Look at Event Viewer as the one entry suggested, see if there is more info available:
The details view of this entry contains further information.
The DCOM error is not unusual, I see it a lot.
Look at Event Viewer as the one entry suggested, see if there is more info available:
The details view of this entry contains further information.
Memory changed, now at 12 GB. Will report back depending on what happens.
Here is the details view, I hope it means more to you than me :
- System
- Provider
[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM
- EventID 10016
[ Qualifiers] 0
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2017-01-18T02:49:56.079941300Z
EventRecordID 145759
Correlation
- Execution
[ ProcessID] 744
[ ThreadID] 3896
Channel System
Computer Dad-PC
- Security
[ UserID] S-1-5-18
- EventData
param1 application-specific
param2 Local
param3 Activation
param4 {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
param5 {F72671A9-012C-4725-9D2F-2A4D32D65169}
param6 NT AUTHORITY
param7 SYSTEM
param8 S-1-5-18
param9 LocalHost (Using LRPC)
param10 Unavailable
param11 Unavailable
I wanted the details view for the hardware error (WHEA Error)
not the COM/DCOM event.Code:Event[64018]: Log Name: System Source: Microsoft-Windows-WHEA-Logger
My Mistake, here you go:
- System
- Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
EventID 17
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2017-01-18T03:04:23.169287300Z
EventRecordID 145765
- Correlation
[ ActivityID] {72E55B95-E9FE-4EC0-A067-2F6BEE38C193}
- Execution
[ ProcessID] 1288
[ ThreadID] 5116
Channel System
Computer Dad-PC
- Security
[ UserID] S-1-5-19
- EventData
ErrorSource 4
FRUId {00000000-0000-0000-0000-000000000000}
FRUText
ValidBits 0xdf
PortType 4
Version 0x101
Command 0x10
Status 0x0
Bus 0x0
Device 0x0
Function 0x0
Segment 0x0
SecondaryBus 0x0
Slot 0x0
VendorID 0x8086
DeviceID 0x3405
ClassCode 0x30000
DeviceSerialNumber 0x0
BridgeControl 0x0
BridgeStatus 0x0
UncorrectableErrorStatus 0x0
CorrectableErrorStatus 0x0
HeaderLog 00000000000000000000000000000000
Length 672
RawData 435045521002FFFFFFFF02000200000002000000A00200001604030012011114000000000000000000000000000000000000 0000000000000000000000000000BDC407CF89B7184EB3C41F732CB571311FC093CF161AFC4DB8BC9C4DAF67C10424582C5D 3571D20100000000000000000000000000000000000000000000000010010000D0000000000300000100000054E995D9C1BB 0F43AD91B44DCB3C6F3500000000000000000000000000000000020000000000000000000000000000000000000000000000 E0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB000000000000000000000000000000000300 00000000000000000000000000000000000000000000DF000000000000000400000001010000100000000000000086800534 00000300000000000000000000000000000000000000000010E042002080000000000000413C3B000000413000000000C007 000100000000000000003E000000090000000000000000000000000000000000000001000115000000000000000010200600 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000043010000000000000002000000000000A5060100 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000
Looking at that info, the problem device is:
Chip Vendor Intel Corporation 8086 PCI\VEN_8086
Chip Device 5520/5500/X58 I/O Hub to ESI Port 3405 PCI\VEN_8086&DEV_3405
That may be covered by the Intel Chipset driver but I'm not sure as I can't find anything that tells me that.
Edit: The only driver I can find for this is here: Intel(R) 5520/5500/X58 I/O Hub to ESI Port - 3405 Drivers Download
Attachment 117754
Hi, done. Will monitor over the next couple of days, and will mark if no other BSODs or freezing. Will then mark as solved.
Thanks again for your help.
No BSODs over last couple of days..keeping fingers crossed... will mark as solved.
Many thanks for all the help