windows server 2008 R2系统，dell r320服务器，做了radi1+0，,4块硬盘。开机进入桌面后不定时（大概半小时至4小时之间）就会蓝屏。
重启对C盘进行过windows自带的自动修复文件系统错误后，又正常使用了14天，今天再次出现蓝屏，但再次自动修复文件错误后，进入桌面，1小时后就蓝屏了。
两次蓝屏的报错界面都是如下图。

windbg查看结果如下：
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\360data\重要数据\桌面\091418-25131-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 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: LanManNt, suite: Enterprise TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01e02000 PsLoadedModuleList = 0xfffff800`02041c90
Debug session time: Tue Sep 11 10:59:24.069 2018 (UTC + 8:00)
System Uptime: 0 days 0:08:07.647
*********************************************************************
* 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 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 19, {20, fffffa800ada4660, fffffa800ada4a80, 4420009}
Unable to load image gscfmgr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gscfmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for gscfmgr.sys
***** 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!PVOID ***
*** ***
*************************************************************************
*************************************************************************
Probably caused by : gscfmgr.sys ( gscfmgr+57e6 )
Followup: MachineOwner
---------