Windows 7 Pro x64 BSOD

[Mr Bob]

Here are my computer specs

- [os] Windows 7 Professional x64
- [motherboard] Intel BOXD975XBX2KR LGA 775 Intel 975X ATX
- [cpu] Intel Core 2 Quad Q6600 Kentsfield 2.4GHz 2 x 4MB L2 Cache LGA 775
- [ram] Corsair XMS2 DHX 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
- [power supply] FSP FX700-GLN
- [fan controller/temp sensor] Thermaltake A2259 Hardcano
- [video card] BFG 8600 GTS
- [video card] BFG 6600 GT - secondary video card for Dell monitors
[hard drives]
- Raptor WD740GD 74GB
- [dvd drive] BenQ DW1640
- [sound card] XMYSTIQUE7.1 (7.1) 24bit 96KHz

Any ideas what's going on?

Minidump info:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122811-54406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03617000 PsLoadedModuleList = 0xfffff800`0385c670
Debug session time: Wed Dec 28 12:48:15.193 2011 (GMT-7)
System Uptime: 2 days 14:48:15.818
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000396bcf1, fffff88013ff17b8, fffff88013ff1010}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+354cf1 )

Followup: MachineOwner
---------

0: kd> .sympath srv*csymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*csymbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*csymbols*http://msdl.microsoft.com/download/symbols
0: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000396bcf1, The address that the exception occurred at
Arg3: fffff88013ff17b8, Exception Record Address
Arg4: fffff88013ff1010, Context Record Address

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\Drivers\stcvsm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for stcvsm.sys
*** ERROR: Module load completed but symbols could not be loaded for stcvsm.sys
Unable to load image \SystemRoot\system32\DRIVERS\tdrpm258.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tdrpm258.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm258.sys

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ObpQueryNameString+51
fffff800`0396bcf1 410fb64718 movzx eax,byte ptr [r15+18h]

EXCEPTION_RECORD: fffff88013ff17b8 -- (.exr 0xfffff88013ff17b8)
ExceptionAddress: fffff8000396bcf1 (nt!ObpQueryNameString+0x0000000000000051)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88013ff1010 -- (.cxr 0xfffff88013ff1010)
rax=fffff88013ff1ae8 rbx=5543204c4f502045 rcx=5543204c4f502045
rdx=fffff88013ff1b50 rsi=0000000000000001 rdi=0000000000000000
rip=fffff8000396bcf1 rsp=fffff88013ff19f0 rbp=0000000000000000
r8=0000000000000010 r9=fffff88013ff1b88 r10=00000000000028f4
r11=0000000000000000 r12=0000000000000001 r13=fffffa800d432760
r14=fffff88013ff1b50 r15=5543204c4f502015
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!ObpQueryNameString+0x51:
fffff800`0396bcf1 410fb64718 movzx eax,byte ptr [r15+18h] ds:002b:5543204c`4f50202d=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c6100
ffffffffffffffff

FOLLOWUP_IP:
stcvsm+168f5
fffff880`015518f5 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff8000397391e to fffff8000396bcf1

STACK_TEXT:
fffff880`13ff19f0 fffff800`0397391e : 5543204c`4f502045 fffff880`13ff1b50 00000000`00000010 fffff880`13ff1b88 : nt!ObpQueryNameString+0x51
fffff880`13ff1af0 fffff880`015518f5 : 00000000`00000001 fffffa80`0f51ae40 fffffa80`0d64e280 fffff880`017026ec : nt!ObQueryNameString+0xe
fffff880`13ff1b30 00000000`00000001 : fffffa80`0f51ae40 fffffa80`0d64e280 fffff880`017026ec fffffa80`0e6b6b60 : stcvsm+0x168f5
fffff880`13ff1b38 fffffa80`0f51ae40 : fffffa80`0d64e280 fffff880`017026ec fffffa80`0e6b6b60 fffff880`009f1180 : 0x1
fffff880`13ff1b40 fffffa80`0d64e280 : fffff880`017026ec fffffa80`0e6b6b60 fffff880`009f1180 fffff880`13ff1cb0 : 0xfffffa80`0f51ae40
fffff880`13ff1b48 fffff880`017026ec : fffffa80`0e6b6b60 fffff880`009f1180 fffff880`13ff1cb0 fffff880`0154d028 : 0xfffffa80`0d64e280
fffff880`13ff1b50 fffff880`01ee3160 : fffffa80`0decfcf0 fffff800`0392efee fffffa80`0e6b6b60 00000000`00000080 : Ntfs!NtfsCommonCreate+0x21b5
fffff880`13ff1d30 fffffa80`0decfcf0 : fffff800`0392efee fffffa80`0e6b6b60 00000000`00000080 fffffa80`06d16040 : tdrpm258+0x53160
fffff880`13ff1d38 fffff800`0392efee : fffffa80`0e6b6b60 00000000`00000080 fffffa80`06d16040 00000000`00000001 : 0xfffffa80`0decfcf0
fffff880`13ff1d40 fffff800`036855e6 : fffff880`009f1180 fffffa80`0e6b6b60 fffffa80`0d40a540 fffff880`01669cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`13ff1d80 00000000`00000000 : fffff880`13ff2000 fffff880`13fec000 fffff880`13ff1a10 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: stcvsm+168f5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: stcvsm

IMAGE_NAME: stcvsm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48c1919b

STACK_COMMAND: .cxr 0xfffff88013ff1010 ; kb

FAILURE_BUCKET_ID: X64_0x7E_stcvsm+168f5

BUCKET_ID: X64_0x7E_stcvsm+168f5

Followup: MachineOwner
---------

 

[Bubbaleone]

Can you boot into Safe mode? If you can, this might be worth a read.

http://forums.anandtech.com/showthread.php?t=2200335

If you can't boot Safe mode see this: Can't boot due to stcvsm.sys issue

 

[Mr Bob]

Safe mode works, this is the only BSOD i've had in awhile, and it doesn't keep happening. I just couldn't tell much about what the error was.

 

[Bubbaleone]

Generally, if you can boot safe mode, what you describe is an issue with a recent driver, service, or program change. If it continues, follow the tut in the forum link to zero-in on the culprit.

 

[Mr Bob]

I haven't installed anything new recently, programs, drivers, nor services.

I looked at some posts about stcvsm.sys and see it relating to a conflict with Acronis and ShadowProtect. I wonder if maybe that is what caused it.

ShadowProtect is set to run daily. Acronis is set to run manually, however, I did notice an Acronis service (the scheduler service) running "Automatic" with startup.

Since this BSOD has only happened once, modifying my services, and restarting to see if it happens again, won't really help me figure out what the root cause is, because it's only happened once.

If it keeps happening, I'll go through that tutorial and see if I have a better way of narrowing it down.

Thanks