BSOD ATTEMPTED_ SWITCH_FROM_DPC while using AOMEI Backupper

Just to let you know what happened next...

I did a few disk tests that I could, all involving full-surface scans. The disk seems fine according to those. I did not find a test that is as comprehensive as SpinRite that I could use, so I'm keeping my fingers (figuratively) crossed.

Meanwhile, I was surprised to get a couple new BSODs:






To me these seemed to indicate RAM problems, so I followed the advice on the memtest page. almost immediately, it reported a bunch of errors:



Repeating the test repeatedly showed memory problems of various magnitude.

Aha! I thought. So I took out half the memory and ran it again. No problems, so I figured it must be the removed half of the memory (or the slots they were in). So I ran the tests again with just the removed memory reinstalled ... no problems! So I put the other half of the memory in the original slots and ran again... no problems! In short, every which way I tested showed no problems. The last thing I did was to leave the memory with the sticks swapped from the original configuration and ran a very long test - after 15 passes, still no errors detected:



For good measure, I also ran 4 passes of the Passmark free version of memtest86 - also detected no errors.

So.... I don't know why I was getting those memory errors - maybe reseating the sticks cleaned the contacts or just gave a better connection. At any rate, I'm moving on and hoping that all is now well. We'll see if it blue-screens again...

Thanks,
Yosh

Let me know if you need any further help while @axe0 is away :)

Thanks. Well, my system is continuing to have a variety of BSODs. I am not sure if I should start a new thread or continue in this one. At this point, since replacing the hard drive & reinstalling Windows form scratch, I've had about 8 BSODs, with a variety of stopcodes. Here's the report from Nirsoft's BlueScreenView:
Crash List

Created by using BlueScreenView

Dump File	Crash Time	Bug Check String	Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Caused By Driver	Caused By Address	File Description	Product Name	Company	File Version	Processor	Crash Address	Stack Address 1	Stack Address 2	Stack Address 3	Computer Name	Full Path	Processors Count	Major Version	Minor Version	Dump File Size
051017-8515-01.dmp	5/10/2017 9:21:19 AM	KMODE_EXCEPTION_NOT_HANDLED	0x0000001e	ffffffff`c0000096	fffff806`88e444bc	00000000`00000000	00000000`00000000	dxgkrnl.sys	dxgkrnl.sys+1b44bc					x64	ntoskrnl.exe+14e7c0					C:\Windows\Minidump\051017-8515-01.dmp	8	15	14393	545,956
050417-9484-01.dmp	5/4/2017 3:54:14 PM	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED	0x1000007e	ffffffff`c0000005	fffff800`e0c6b958	ffff9501`acd88368	ffff9501`acd87b90	ntoskrnl.exe	ntoskrnl.exe+1f1958					x64	ntoskrnl.exe+1f1958					C:\Windows\Minidump\050417-9484-01.dmp	8	15	14393	513,508
042617-8078-01.dmp	4/26/2017 2:12:46 PM		0x00000154	ffff9b89`93a0c000	ffff8901`3ddcc050	00000000`00000002	00000000`00000000	ntoskrnl.exe	ntoskrnl.exe+14e7c0					x64	ntoskrnl.exe+14e7c0					C:\Windows\Minidump\042617-8078-01.dmp	8	15	14393	546,348
042317-8906-01.dmp	4/23/2017 9:58:13 AM	MEMORY_MANAGEMENT	0x0000001a	00000000`00041284	00007ff8`57a90000	00000000`00000000	fffff500`10804310	ntoskrnl.exe	ntoskrnl.exe+14e7c0					x64	ntoskrnl.exe+14e7c0					C:\Windows\Minidump\042317-8906-01.dmp	8	15	14393	537,484
042017-8453-01.dmp	4/20/2017 9:57:17 AM	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED	0x1000007e	ffffffff`c0000005	fffff802`f487b958	ffff8300`b3b88368	ffff8300`b3b87b90	ntoskrnl.exe	ntoskrnl.exe+1f1958					x64	ntoskrnl.exe+1f1958					C:\Windows\Minidump\042017-8453-01.dmp	8	15	14393	538,908
041317-8109-01.dmp	4/13/2017 11:37:38 PM		0x0000012b	ffffffff`c00002c4	00000000`000003ef	00000000`2da79e10	ffffc601`02ff7000	ntoskrnl.exe	ntoskrnl.exe+14e7c0					x64	ntoskrnl.exe+14e7c0					C:\Windows\Minidump\041317-8109-01.dmp	8	15	14393	677,244
040617-9156-01.dmp	4/6/2017 10:14:22 PM	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED	0x1000007e	ffffffff`c0000005	fffff802`14882958	ffffa280`d2353368	ffffa280`d2352b90	ntoskrnl.exe	ntoskrnl.exe+1f1958					x64	ntoskrnl.exe+1f1958					C:\Windows\Minidump\040617-9156-01.dmp	8	15	14393	530,412
033017-8187-01.dmp	3/30/2017 4:54:21 PM	BAD_POOL_HEADER	0x00000019	00000000`00000020	ffffba8c`d2e2b450	ffffba8c`d2e2b490	00000000`04040012	FLTMGR.SYS	FLTMGR.SYS+345e8					x64	ntoskrnl.exe+14a510					C:\Windows\Minidump\033017-8187-01.dmp	8	15	14393	546,140

Most (but not all) have happened while resuming Windows 10 from hibernation. The most recent (KMODE_EXCEPTION_NOT_HANDLED) happened this morning.

I'm not an expert in analyzing dump files, but I used BlueScreenView to see the stack & they all mention the VGA boot driver (but not only that - in fact, the list is very similar in all the files). Here's the beginning of today's dump (see rows I marked red):

Filename	Address In Stack	From Address	To Address	Size	Time Stamp	Time String	Product Name	File Description	File Version	Company	Full Path
dxgkrnl.sys	dxgkrnl.sys+1b44bc	fffff806`88c90000	fffff806`88eaf000	0x0021f000	0x58d9f03f	3/28/2017 8:10:23 AM
ntoskrnl.exe	ntoskrnl.exe+183990	fffff802`c1e8b000	fffff802`c26a3000	0x00818000	0x58d9f097	3/28/2017 8:11:51 AM
hal.dll		fffff802`c1e16000	fffff802`c1e8b000	0x00075000	0x57dac91a	9/15/2016 7:15:22 PM
kd.dll		fffff802`c0419000	fffff802`c0424000	0x0000b000	0x57899bfc	7/16/2016 5:29:16 AM
mcupdate_GenuineIntel.dll		fffff806`86150000	fffff806`861de000	0x0008e000	0x57899bb5	7/16/2016 5:28:05 AM
werkernel.sys		fffff806`861e0000	fffff806`861f0000	0x00010000	0x57899be3	7/16/2016 5:28:51 AM
CLFS.SYS		fffff806`85e00000	fffff806`85e63000	0x00063000	0x584a76cf	12/9/2016 12:18:07 PM
tm.sys		fffff806`85e70000	fffff806`85e95000	0x00025000	0x57f4c3a4	10/5/2016 12:11:00 PM
PSHED.dll		fffff806`85ea0000	fffff806`85eb7000	0x00017000	0x578997a4	7/16/2016 5:10:44 AM	Microsoft® Windows® Operating System	Platform Specific Hardware Error Driver	10.0.14393.0 (rs1_release.160715-1616)	Microsoft Corporation	C:\Windows\system32\PSHED.dll
BOOTVID.dll		fffff806`85ec0000	fffff806`85ecc000	0x0000c000	0x5789979d	7/16/2016 5:10:37 AM	Microsoft® Windows® Operating System	VGA Boot Driver	10.0.14393.0 (rs1_release.160715-1616)	Microsoft Corporation	C:\Windows\system32\BOOTVID.dll
FLTMGR.SYS		fffff806`85ed0000	fffff806`85f32000	0x00062000	0x578997a5	7/16/2016 5:10:45 AM
msrpc.sys		fffff806`85f40000	fffff806`85f9d000	0x0005d000	0x57899a8a	7/16/2016 5:23:06 AM

...

I have no idea if my surmise is correct...

What would you advise? Should I start a new thread? Attach a collection of minidump files? Do the whole BSOD posting procedure over again to collect all system info (with DM Log Collector)? Should I focus on my VGA hardware & driver?

Any advice will be much appreciated.

Thanks,
Yosh

Please post a new set of files using the DM_log_collector and we can take a fresh look at what is happening.