All Forums
> RAM Disk
> Current topic
File spvve.sys crashes
Started by Robert J.
|
Robert J.
File spvve.sys crashes 12 January 2021, 22:00 |
|
|
Re: File spvve.sys crashes 12 January 2021, 23:09 |
Admin Registered: 19 years ago Posts: 3 598 |
If it crashes, it means the driver has run into a critical error. There can be a number of reasons, including faulty memory modules, conflict with other drivers, or a bug in our driver. There is unfortunately no easy fix or workaround for this.
To be able to help, we need to know the RAM Disk version you are using, and get a crash dump. Alternatively you can run this WhoCrashed utility and post its report here.
To be able to help, we need to know the RAM Disk version you are using, and get a crash dump. Alternatively you can run this WhoCrashed utility and post its report here.
|
Robert J.
Re: File spvve.sys crashes 13 January 2021, 00:31 |
Please find below the results from WhoCrashed. I have a new PC with X299-PRO and no RAM issues (tested with MEMTestPRO).
-------------------------
Crash Dump Analysis
-------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 12.01.2021 12:47:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011221-9406-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF8075E0056E5)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8075E0056E5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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: spvve.sys .
Google query: spvve.sys KMODE_EXCEPTION_NOT_HANDLED
On Tue 12.01.2021 11:12:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011221-10437-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF8015A0656E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8015A0656E5, 0xFFFFF389122E5D90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: spvve.sys .
Google query: spvve.sys SYSTEM_SERVICE_EXCEPTION
On Sun 10.01.2021 13:33:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011021-10250-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF8017D6E56E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8017D6E56E5, 0xFFFFC682D7EFDD90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: spvve.sys .
Google query: spvve.sys SYSTEM_SERVICE_EXCEPTION
On Sat 19.12.2020 11:01:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121920-10234-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF806208856E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF806208856E5, 0xFFFFA3892BE65D90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: spvve.sys .
Google query: spvve.sys SYSTEM_SERVICE_EXCEPTION
On Mon 14.12.2020 11:53:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121420-13906-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF803875C5DBD)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803875C5DBD, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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: spvve.sys .
Google query: spvve.sys KMODE_EXCEPTION_NOT_HANDLED
On Mon 14.12.2020 11:53:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F9CC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803875C5DBD, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
-------------------------
Conclusion
-------------------------
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
spvve.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
-------------------------
Crash Dump Analysis
-------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 12.01.2021 12:47:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011221-9406-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF8075E0056E5)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8075E0056E5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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: spvve.sys .
Google query: spvve.sys KMODE_EXCEPTION_NOT_HANDLED
On Tue 12.01.2021 11:12:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011221-10437-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF8015A0656E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8015A0656E5, 0xFFFFF389122E5D90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: spvve.sys .
Google query: spvve.sys SYSTEM_SERVICE_EXCEPTION
On Sun 10.01.2021 13:33:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011021-10250-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF8017D6E56E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8017D6E56E5, 0xFFFFC682D7EFDD90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: spvve.sys .
Google query: spvve.sys SYSTEM_SERVICE_EXCEPTION
On Sat 19.12.2020 11:01:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121920-10234-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF806208856E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF806208856E5, 0xFFFFA3892BE65D90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: spvve.sys .
Google query: spvve.sys SYSTEM_SERVICE_EXCEPTION
On Mon 14.12.2020 11:53:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121420-13906-01.dmp
This was probably caused by the following module: spvve.sys (0xFFFFF803875C5DBD)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803875C5DBD, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\spvve.sys
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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: spvve.sys .
Google query: spvve.sys KMODE_EXCEPTION_NOT_HANDLED
On Mon 14.12.2020 11:53:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F9CC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803875C5DBD, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
-------------------------
Conclusion
-------------------------
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
spvve.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
|
|
Re: File spvve.sys crashes 13 January 2021, 11:26 |
Admin Registered: 19 years ago Posts: 3 598 |
That indeed looks like an issue with our driver. For further investigation, could you please send us all dump files from C:\Windows\Minidump for analysis?
Please compress the files to a ZIP file and send it to us via our support centre. It will help further if you attach a screen shot of your RAM disk configuration and mention what version of the RAM Disk application you are using.
Thank you for your assistance.
Please compress the files to a ZIP file and send it to us via our support centre. It will help further if you attach a screen shot of your RAM disk configuration and mention what version of the RAM Disk application you are using.
Thank you for your assistance.
|
|
Re: File spvve.sys crashes 18 January 2021, 10:47 |
Admin Registered: 19 years ago Posts: 3 598 |
We have received the dumps, but unfortunately they suggest there is defective memory in your PC (or memory controller, or other components).
If you wish to test your memory, I recommend Prime95 tool, as the test you used before may not have found the issue. If you run Prime95 for a few hours and it reports no errors, then your PC is fine and the issue is somewhere else. You can also have a look at other memory testing tools, such as:
Please test the stability of your PC with Prime95 and/or other tools and let us know how it went.
If you wish to test your memory, I recommend Prime95 tool, as the test you used before may not have found the issue. If you run Prime95 for a few hours and it reports no errors, then your PC is fine and the issue is somewhere else. You can also have a look at other memory testing tools, such as:
- MemTest86 (one of the oldest tools for RAM stress-testing;the interface is quite old-fashioned, but the tests are comprehensive)
- MemTest64 (more modern tool, with GUI, but also with simplified testing abilities)
- AIDA64 Extreme (probably the simplest tool in the list)
Please test the stability of your PC with Prime95 and/or other tools and let us know how it went.
|
Re: File spvve.sys crashes 24 February 2021, 16:41 |
Registered: 3 years ago Posts: 2 |
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80217375672, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for spvve.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on UTHUWJUGHRYAEPV
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 14
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80217375672
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
READ_ADDRESS: fffff80219afb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80219a0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80219a0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff
EXCEPTION_PARAMETER2: ffffffffffffffff
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffff978dd15c5db0 -- (.trap 0xffff978dd15c5db0)
Unable to read trap frame at ffff978d`d15c5db0
STACK_TEXT:
ffff9202`66ae73c8 fffff802`192914d3 : 00000000`0000001e ffffffff`c0000005 fffff802`17375672 00000000`00000000 : nt!KeBugCheckEx
ffff9202`66ae73d0 fffff802`19207bac : 00000000`00000000 ffff978d`c2611060 ffff978d`d15c5db0 ffff978d`c26111b0 : nt!KiDispatchException+0x166ad3
ffff9202`66ae7a90 fffff802`192038e0 : ffff978d`c25a7a40 fffff802`1cf33ee0 00000000`00000000 00000000`00000103 : nt!KiExceptionDispatch+0x12c
ffff9202`66ae7c70 fffff802`17375672 : 00000000`00000000 ffff978d`c2681040 ffff978d`d04e8f08 fffff802`19052f55 : nt!KiGeneralProtectionFault+0x320
ffff9202`66ae7e00 00000000`00000000 : ffff978d`c2681040 ffff978d`d04e8f08 fffff802`19052f55 00000000`00000000 : spvve+0x5672
SYMBOL_NAME: spvve+5672
MODULE_NAME: spvve
IMAGE_NAME: spvve.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 5672
FAILURE_BUCKET_ID: 0x1E_c0000005_R_spvve!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c88d1460-fcc6-f1c6-07db-0ee28fd97dc4}
Followup: MachineOwner
---------
|
|
Re: File spvve.sys crashes 25 February 2021, 10:19 |
Admin Registered: 19 years ago Posts: 3 598 |
|
Re: File spvve.sys crashes 25 February 2021, 19:55 |
Registered: 3 years ago Posts: 2 |
|
|
Re: File spvve.sys crashes 04 March 2021, 14:52 |
Admin Registered: 19 years ago Posts: 3 598 |
Thank you, we were able to narrow down the crash dump to a specific source code location:
FAULTING_SOURCE_FILE: sys\volume\image.c
FAULTING_SOURCE_LINE_NUMBER: 922
FAULTING_SOURCE_CODE:
678: // Check for hit.
679: //
680:
681: if (u64CurrentOffset +
> 682: pRegion -> Size >
683: u64Offset)
684: {
685: //
686: // Validate iteration.
687: //
Unfortunately we can't tell why it crashed here. It may well be corrupted memory or a faulty memory module. I recommend that you test your PC's RAM to ensure it's stable.