Question Events in Event Viewer and Crashes

[Joe Doe]

Simple question: does the event right before a crash error in event viewer tell you the likely cause of the crash?

I would try to view the dump file, but it's giving me the "Dump file creation failed due to error during dump creation" thing.

 

[Ralston18]

What error codes are you seeing? Remember you can right click on any given event for additional information.

Also update your post to include full system hardware specs and OS.

If the event is consistent with crashes (either preceding or corresponding the crash) then Event Viewer is useful.

Where it becomes problematic is if the events vary - in which case would make the PSU suspect. Bad power can wreak havoc in any number of and varying ways.....

Also take a look at Reliability History. Reliability History is more user friendly and shows error codes, warnings, and information events along a timeline.

That can be handy because if the problem traces back in time to some known action on your part (e.g., new software, upgrade, new component) then the cause may be easier to pinpoint.

 

[Joe Doe]

Thanks so much for the response, Ralston. My build is below:


CPU = Intel Core i9-9820X Skylake 3.3 GHz LGA 2066
Motherboard = ASUS Prime X299-Deluxe II LGA 2066 ATX Intel
Memory = CORSAIR Vengeance RGB Pro 128GB (8 x 16GB) 288-Pin DDR4 SDRAM DDR4 2666 (PC4 21300)
GPU = NVIDIA Titan RTX Dual-Fan 24GB GDDR6 PCIe Video Card
PSU = Corsair AX1200i 1200 Watt ATX 12V Power Supply
OS Drive = Corsair Force Series 2TB SSD 3D TLC NAND MP600 M.2 2280 PCIe NVMe Internal Solid State
OS = Microsoft Windows 10 Pro 64-bit


There does seem to be a consistency in the event before certain crashes; for instance there are several crash instances of below:

____
EVENT BEFORE ERROR

A service was installed in the system.

Service Name: MSIO
Service File Name: C:\Program Files\Patriot\Aac_Patriot Viper RGB\msio64.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:
____

ERROR / CRASH

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8021f918930, 0xffffa6005dd7e130, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 24dd3cf2-9e28-4c8f-aff5-c8519c006043.
____


And several of these:

____

EVENT BEFORE ERROR

A service was installed in the system.

Service Name: MSIO
Service File Name: C:\Program Files\Galaxy\Aac_GALAX GAMER RGB\msio64.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:
____
ERROR / CRASH

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8075073f321, 0xffff9d8e210295f8, 0xfffff80753c7e930). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b91e9924-4ee0-4f8f-affb-c77c57a73b59.


____



I’ve done assorted memory tests, with all installed and each individually as a single and they always pass with no errors.

I built this system for a co-worker and he says it BSODs on him several times a day.

During the install I had several BSODs relating to a known motherboard wifi issue (see pic below).

I had the gentleman completely disable the wifi in the bios and he said it seemed to fix it, but came back days later and said the problems were back.

 

[Joe Doe]

bb code image hosting