cancel
Showing results for 
Search instead for 
Did you mean: 

Minor driver issue (possibly unrelated, some handholding required)

lightknightrr
Level 8
So, this happened:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 7

The details view of this entry contains further information.

More information:

- System

- Provider

[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}

EventID 18

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2017-12-16T05:00:47.604603700Z

EventRecordID 3825

- Correlation

[ ActivityID] {A30AB987-415F-45EF-9599-E934D5227624}

- Execution

[ ProcessID] 4528
[ ThreadID] 5768

Channel System

Computer HisArmor

- Security

[ UserID] S-1-5-19


- EventData

ErrorSource 3
ApicId 7
MCABank 5
MciStat 0xb6a0000000000108
MciAddr 0x7fff01b9b83e
MciMisc 0x0
ErrorType 9
TransactionType 2
Participation 256
RequestType 0
MemorIO 256
MemHierarchyLvl 0
Timeout 256
OperationType 256
Channel 256
Length 928
RawData 435045521002FFFFFFFF03000100000002000000A003000026000500100C11140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBE58801CF2A76D30102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000110F80000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000700000000000000110F8000000810070B32D87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F000206000000003EB8B901FF7F000000000000000000000000000000000000000000000000000001000000020000002E6ACBD02A76D301070000000000000000000000000000000000000005000000080100000000A0B63EB8B901FF7F000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2,879 Views
6 REPLIES 6

lightknightrr
Level 8
Immediately before it I got this:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffbb054abd58f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\121617-10265-01.dmp. Report Id: d84a4a67-ca6c-4e1e-bfbb-659bc3cc5528.

More information:

System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2017-12-16T05:00:47.152161300Z

EventRecordID 3819

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer HisArmor

Security


- EventData

param1 0x00000124 (0x0000000000000000, 0xffffbb054abd58f8, 0x0000000000000000, 0x0000000000000000)
param2 C:\Windows\Minidump\121617-10265-01.dmp
param3 d84a4a67-ca6c-4e1e-bfbb-659bc3cc5528

lightknightrr
Level 8
Speccy report: https://www.dropbox.com/s/bxvrgoohf77bdll/HISARMOR.txt?dl=0


Summary
Operating System
Windows 10 Pro 64-bit
CPU
AMD Ryzen 7 1800X 53 °C
Summit Ridge 14nm Technology
RAM
32.0GB Dual-Channel Unknown @ 1463MHz (16-16-16-39)
Motherboard
ASUSTeK COMPUTER INC. ROG CROSSHAIR VI HERO (WI-FI AC) (AM4) 32 °C
Graphics
SAMSUNG (3840x2160@59Hz)
8192MB ATI Radeon RX 480 Graphics (XFX Pine Group) 55 °C
Storage
931GB Crucial_CT1024MX200SSD1 (SSD) 32 °C
978GB Crucial_CT1050MX300SSD1 (SSD) 32 °C
7452GB Seagate ST8000NM0105-1VS112 (SATA) 39 °C
7452GB Seagate ST8000NM0105-1VS112 (SATA) 39 °C
953GB Samsung SSD 960 PRO 1TB (Unknown)
59GB Samsung Flash Drive USB Device (USB)
Optical Drives
HL-DT-ST BD-RE WH16NS40
DiscSoft Virtual SCSI CdRom Device
DiscSoft Virtual SCSI CdRom Device
HL-DT-ST BD-RE WH16NS40
Audio
AMD High Definition Audio Device

lightknightrr
Level 8
The question is whether this is a Crosshair bug, and in either case, does anyone want to walk me through reading a dump file to figure out which driver, exactly, is doing this?

lightknightrr wrote:
The question is whether this is a Crosshair bug, and in either case, does anyone want to walk me through reading a dump file to figure out which driver, exactly, is doing this?



There is a great ("free" and "Pro") utility out there for Windows called "whocrashed" that will read a Windows crash dump for you and output the likely driver culprit.

lightknightrr
Level 8
Ok, minor problem with that.

Dump file creation failed due to error during dump creation.

- System

- Provider

[ Name] volmgr

- EventID 161

[ Qualifiers] 49156

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2017-12-21T17:28:50.807206700Z

EventRecordID 5082

Channel System

Computer HisArmor

Security


- EventData

\Device\HarddiskVolume4
000000000100000000000000A10004C081000200010000C000000000000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00000000 00000001 00000000 C00400A1
0010: 00020081 C0000001 00000000 00000000
0020: 00000000 00000000


In Bytes

0000: 00 00 00 00 01 00 00 00 ........
0008: 00 00 00 00 A1 00 04 C0 ....¡..À
0010: 81 00 02 00 01 00 00 C0 �......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

lightknightrr
Level 8
Hmm. The mystery continues...video locks up, as well as the USB. Thermal issue? But I am using a Corsair 115 with some giant fans...


Running a render sequence on Adobe Premier seems to trigger it.