Windows 10: Multiple crashes with multiple error codes & modules

Hi there,

For the past few months I've had fairly regular (usually at least one a day) BSOD on W10. Using WhoCrashed, it's shown that there's multiple modules causing a variety of different errors. I've uploaded my zip from the log collector but I'll also add the log from WhoCrashed.

These crashes are completely random. I can leave my PC on with maybe Twitch open and I'll come back 5 minutes later and it'll have crashed. I can also be gaming and have the PC crash, likewise with simply just browsing the internet.
I've checked all my RAM sticks and all RAM slots - I've booted the PC with just 1 RAM stick by itself (I tried every stick), and tried booting with a single RAM stick in every slot. I also ran the W10 Memory Diagnostic tool and it returned no errors.

I've tried updating the drivers that WhoCrashed has identified - namely Nvidia Drivers using DDU and Realtek drivers. I've used not only DriverBooster to identify any outdated Drivers but also MSI's LiveUpdate 6. I've also reseated my GPU and refitted the power cables from my PSU. I've also done a completely fresh reinstall of Windows10 yet the crashes have persisted.

I'm at my wits end here, hopefully somebody can help me. Thank you

:)

 

Fault Module Name:_wcescommproxy.dll

My WMDC continually crashes after initial start up. The error report lists
Fault Module Name: wcescommproxy.dll as the problem. I have done multiple uninstalls and reinstalls. I can initially set up my phone and sync and then the next attempt restarts the crash process.

 

BSOD problem

38 errors after 8 passes. You need to replace the faulty RAM. Is there a single module or multiple modules of RAM?

If multiple, we might have to dig in which RAM is failing by running tests on them one by one.

 

Just had another crash -

crash dump file: C:\Windows\Minidump\032617-6312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x50 (0xFFFF80826175E698, 0x0, 0xFFFFF801230B419F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Remove DB4 and check MSI for LAN driver updates.

 

I've uninstalled DB and I downloaded the new Realtek LAN driver from MSI. I uninstalled the older driver and reinstalled the new one.

I'm about to run the W10 Driver Verifier and see if it identifies any issues.

 

I enabled the Driver Verifier but it put my PC into an endless BSOD loop. I was able to boot into safe mode and disable it. In WhoCrashed the error reads -

On Sun 26/03/2017 16:27:45 your computer crashed
crash dump file: C:\Windows\Minidump\032617-4375-01.dmp
This was probably caused by the following module: scpvbus.sys (ScpVBus+0xB174)
Bugcheck code: 0xC9 (0x21F, 0xFFFFF80E73CFB174, 0xFFFFF6868E06EDC0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\scpvbus.sys
product: Scp Virtual Bus Driver
company: Scarlet.Crush Productions
description: Scp Virtual Bus Driver
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions).
Google query: Scarlet.Crush Productions DRIVER_VERIFIER_IOMANAGER_VIOLATION

 

Post a new zip by the DM Log Collector, more useful than those 'reports'.

 

I've attached the new DM Log Collector results.

 

Follow the instructions on Malwarebytes |

Malwarebytes MB-clean tool to uninstall Malwarebytes, instructions are at the bottom of the page.

 

I've uninstalled MB using the tool provided and rebooted. Was MB causing the BSODs?

 

Many of them yes, we'll find out about the few others *Smile

 

Well so far so good - I've yet to crash again. If I get another crash I'll post an update in here with an updated DM Log zip file.

Thank you for your help Axe!

 

Unfortunately it didn't last too long. Had another crash this afternoon, I've attached the log zip.

 

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.