[SOLVED] The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000034, 0x0000000000000002, 0x0000000000000000, 0xfffff8022af19d0

[Feinraf]

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000034, 0x0000000000000002, 0x0000000000000000, 0xfffff8022af19d05). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d5097ae5-7556-47a3-ab46-7d44d2c084bc.

MEMORY.DMP file - https://1drv.ms/u/s!Anb5U3btYEmrhb5-Z-erOsQgLB96og?e=p4kx9L

Mini Dumps ZIP - https://1drv.ms/u/s!Anb5U3btYEmrhb5_QbzBL5BXyMvyUQ?e=3JTGGE

Hi, I've been having issues with my PC for months now, a brief timeline below:

PC Built

BSOD's

Replaced GPU

Replaced SSD

Replaced MOBO

Replaced RAM

Replaced CPU

During most of these replacements, I've fully reinstalled Windows 10 including the latest time a few days ago when I replaced the RAM and then CPU.

Any help appreciated, thank you!

 

[kanewolf]

You have not mentioned the power supply in any of your troubleshooting...

 

[Colif]

Were you sure it was any of these parts before replacing them?

0x0000000a are IRQ errors, these can often be caused by drivers. I have asked a friend to look at the dump files.

 

[gardenman]

Hi, I ran the 5 minidump files through the debugger and got the following information: https://swishiermix.htmlpasta.com/

Spoiler

File information:	011420-9734-01.dmp (Jan 14 2020 - 14:25:37)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: Taskmgr.exe)
Uptime:	0 Day(s), 9 Hour(s), 56 Min(s), and 35 Sec(s)

File information:	011420-9296-01.dmp (Jan 13 2020 - 19:10:41)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	0 Day(s), 0 Hour(s), 04 Min(s), and 58 Sec(s)

File information:	011420-8937-01.dmp (Jan 13 2020 - 19:03:47)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: Discord.exe)
Uptime:	0 Day(s), 0 Hour(s), 25 Min(s), and 43 Sec(s)

File information:	011320-9281-01.dmp (Jan 13 2020 - 18:15:54)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	memory_corruption (Process: services.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 11 Sec(s)

File information:	011020-10687-01.dmp (Jan 10 2020 - 08:50:30)
Bugcheck:	UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 06 Sec(s)

I didn't have time to do the memory.dmp tonight but can do it later if needed.

BIOS info was not included in the 1st dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

well, any driver older than 2015 could be the reason so here's one

Sep 07 2011

V0700Vid.sys

Video Capture Device 64-bit driver (Creative Technology)

see if you can find a newer driver.

So I never seen this before - WppRecorder!WppAutoLogTrace+0x2b - and it seems its part of Windows software trace preprocessor which is used to trace the operation of a software component (trace provider).
https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/wpp-software-tracing so i guess my next question is how do you access the log - I don't expect you to know. Its tied into 2nd error (where Chrome crashed).

possible some caused by latest Nvidia drivers as well. DWM.exe is mentioned in some and that is the Windows desktop manager. That and I always suspect Nvidia drivers