My Setup:
- Windows 2012 Server
- latest RAM Disk software available on the website
- 4gb RAM as R:
- has a default admin share of \\server\R$, and a public one of \\server\RAM
Often (not always) when I access either one from another computer in the network the server bluescreens. I have programming/debugging experience if you need more details. But I'd rather not crash the server again
I also tried running the verifier tool from the WDK. Unfortunately then the install of the RAM disk software bluescreens already (I probably have a dump for that as well).
Here is the analyzed dump:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010614-8953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`16876000 PsLoadedModuleList = 0xfffff802`16b42a20
Debug session time: Mon Jan 6 22:51:53.199 2014 (UTC - 5:00)
System Uptime: 0 days 0:03:16.955
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2001f, fffff88001107950, 0, 0}
*** WARNING: Unable to verify timestamp for spvve.sys
*** ERROR: Module load completed but symbols could not be loaded for spvve.sys
Probably caused by : spvve.sys ( spvve+280df )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000000002001f, ID of the 'IrqlZwPassive' rule that was violated.
Arg2: fffff88001107950, A pointer to the string describing the violated rule condition.
Arg3: 0000000000000000, An optional pointer to the rule state variable(s).
Arg4: 0000000000000000, Reserved (unused)
Debugging Details:
------------------
DV_VIOLATED_CONDITION: ZwEnumerateKey should only be called at IRQL = PASSIVE_LEVEL.
DV_MSDN_LINK: !url http://go.microsoft.com/fwlink/?LinkId=216048
DV_RULE_INFO: !ruleinfo 0x2001f
BUGCHECK_STR: 0xc4_IrqlZwPassive_XDV
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff8800110521f to fffff802168d0440
STACK_TEXT:
fffff880`02d084a8 fffff880`0110521f : 00000000`000000c4 00000000`0002001f fffff880`01107950 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d084b0 fffff880`010fc395 : fffff980`39d84ee0 00000000`00000118 fffff880`02d08740 fffff880`16a8a900 : VerifierExt!SLIC_abort+0x47
fffff880`02d084f0 fffff880`010fc3d0 : 00000000`20202058 fffff880`01100665 00000000`00000081 00000000`00000118 : VerifierExt!ZwEnumerateValueKey_wrapper+0x8d
fffff880`02d08520 fffff802`16ed5278 : fffff880`16aa80df 00000000`00000000 fffff880`02d08628 ffffffff`80000db4 : VerifierExt!ZwEnumerateKey_wrapper+0x30
fffff880`02d08560 fffff880`16aa80df : ffffffff`80000db4 ffffffff`80000db4 00000000`00000000 fffff802`16ed87db : nt!VfZwEnumerateKey+0x6c
fffff880`02d085b0 ffffffff`80000db4 : ffffffff`80000db4 00000000`00000000 fffff802`16ed87db fffff880`00000118 : spvve+0x280df
fffff880`02d085b8 ffffffff`80000db4 : 00000000`00000000 fffff802`16ed87db fffff880`00000118 fffff880`02d08628 : 0xffffffff`80000db4
fffff880`02d085c0 00000000`00000000 : fffff802`16ed87db fffff880`00000118 fffff880`02d08628 fffff980`39d84ee0 : 0xffffffff`80000db4
STACK_COMMAND: kb
FOLLOWUP_IP:
spvve+280df
fffff880`16aa80df ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: spvve+280df
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: spvve
IMAGE_NAME: spvve.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52859da1
FAILURE_BUCKET_ID: 0xc4_IrqlZwPassive_XDV_VRF_spvve+280df
BUCKET_ID: 0xc4_IrqlZwPassive_XDV_VRF_spvve+280df
Followup: MachineOwner
---------