Jump to content

blue screen after install


Recommended Posts

FYI - Immediately after install (BETA) 0.9.17 I experienced the infamous BSD. After re-boot all seems well except a second re-boot was required since I needed to allow program through 3rd party firewall. FWIW - the faulting file spvve.sys is located in two places  "System 32/drivers" and "C:\Program Files\SoftPerfect RAM Disk". Both identical files installed on the same date. 
Nirsoft "BlueScreenView" results as follows:

093016-24835-01.dmp 09/30/16 07:25:32 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02e90665 fffff880`033cb0f8 fffff880`033ca950 spvve.sys spvve.sys+281f0     x64 ntoskrnl.exe+79665     C:\Windows\Minidump\093016-24835-01.dmp 4 15 7601 275,096 09/30/16 07:27:08 AM 


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: spvve.sys

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff80002e90665, 0xfffff880033cb0f8,
0xfffff880033ca950)

*** spvve.sys - Address 0xfffff88001af61f0 base at 0xfffff88001ace000 DateStamp
0x5631b5b0

Link to post
Share on other sites

Hello jopa66:

I will be requesting you post follow-up information that should provide developers/staffers with enough data to start.  Using only the native Windows built-in zip utility, please create the following .zip archive files for MBARW developer team analysis:

                              "%ProgramData%\Malwarebytes\Malwarebytes Anti-Ransomware\"
                              "%ProgramData%\Malwarebytes\MBAMService\logs\"
                              "%ProgramData%\MalwarebytesARW\"
                              "C:\Windows\Minidump\093016-24835-01.dmp"

Please attach the .zip archives to your next reply.

Does the system in question have any products installed from: https://www.softperfect.com/

Thank you for your beta testing contribution to the Malwarebytes Anti-Ransomware (MBARW Beta) project and your valued feedback.

Edited by 1PW
Link to post
Share on other sites

 

Attaching zips as requested. Unfortunately minidump file has been dumped. Ccleaner probably. I believe the info it contained is in the first post. The answer to your question about softperfect is YES. I have Networx v5.5.5 and RamDisk v3.4.7.0 both installed. As indicated in the first post, the faulting driver does seem to belong to RamDisk. There have been no further instances of conflict through many reboots. All seems fine working together.

Malwarebytes Anti-Ransomware.zip

MalwarebytesARW.zip

MBAMService.zip

Link to post
Share on other sites

Hello jopa66:

Thank you for the good news update.

If a similar BSoD does re-occur, please take accelerated steps to isolate and preserve the contents of the "%SystemRoot%\Minidump" directory for a later expert review.

Thank you again.

Edited by 1PW
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.