我的系统崩溃了，但是卸载 utorrent 后，系统又恢复正常了。看看 Crash Dump。
http://dl.dropbox.com/u/32657135/Minidump.rar
我正在使用 Windows 7 64 位。
以下是第一次坠机事故的信息：
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Child-SP RetAddr Call Site
fffff880`033d55e8 fffff800`03180ef4 nt!memmove+0x1d1
fffff880`033d55f0 fffff800`03194a2f nt!EtwpLogKernelEvent+0x2a4
fffff880`033d5690 fffff880`011e9692 nt!EtwpTraceFileName+0x15f
fffff880`033d5720 fffff880`011ea43b fileinfo!FIStreamLog+0x1be
fffff880`033d57f0 fffff880`011e7563 fileinfo!FIEnumerate+0x117
fffff880`033d5870 fffff880`011e760b fileinfo!FIControlDispatchSystemControl+0x73
fffff880`033d58b0 fffff800`03332968 fileinfo!FIControlDispatch+0x4b
fffff880`033d58f0 fffff800`03465936 nt!WmipForwardWmiIrp+0x16c
fffff880`033d5970 fffff800`0346645b nt!WmipSendWmiIrpToTraceDeviceList+0xe6
fffff880`033d59d0 fffff800`03476e44 nt!WmiTraceRundownNotify+0x6b
fffff880`033d5a20 fffff800`034e2a7c nt!EtwpKernelTraceRundown+0xc4
fffff880`033d5a50 fffff800`034e2b7f nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`033d5b50 fffff800`032f1859 nt!EtwpStopLoggerInstance+0x4f
fffff880`033d5b90 fffff800`032f15d0 nt!EtwpStopTrace+0x129
fffff880`033d5c00 fffff800`03509f45 nt! ?? ::NNGAKEGL::`string'+0x58e5c
fffff880`033d5c70 fffff800`030a5471 nt!PerfDiagpProxyWorker+0x1c5
fffff880`033d5cb0 fffff800`03335f7a nt!ExpWorkerThread+0x111
fffff880`033d5d40 fffff800`0308c9c6 nt!PspSystemThreadStartup+0x5a
fffff880`033d5d80 00000000`00000000 nt!KiStartSystemThread+0x16
以下是第二次坠机的信息：
NTFS_FILE_SYSTEM (24)
Child-SP RetAddr Call Site
fffff880`036de1e8 fffff880`01437a88 nt!KeBugCheckEx
fffff880`036de1f0 fffff880`01526363 Ntfs! ?? ::FNODOBFM::`string'+0x2b49
fffff880`036de230 fffff800`024f6fec Ntfs! ?? ::NNGAKEGL::`string'+0x830e
fffff880`036de260 fffff800`024f6a6d nt!_C_specific_handler+0x8c
fffff880`036de2d0 fffff800`024f5845 nt!RtlpExecuteHandlerForException+0xd
fffff880`036de300 fffff800`025067c1 nt!RtlDispatchException+0x415
fffff880`036de9e0 fffff800`024cb3c2 nt!KiDispatchException+0x135
fffff880`036df080 fffff800`024c9cca nt!KiExceptionDispatch+0xc2
fffff880`036df260 fffff800`02478eb9 nt!KiGeneralProtectionFault+0x10a
fffff880`036df3f8 fffff800`0249b52d nt!RealSuccessor+0x39
fffff880`036df400 fffff880`014ad652 nt!RtlEnumerateGenericTableWithoutSplayingAvl+0x1d
fffff880`036df430 fffff880`014b5fad Ntfs!NtfsFlushVolume+0x436
fffff880`036df560 fffff880`014b66b4 Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`036df640 fffff880`00c02bcf Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`036df6b0 fffff880`00c016df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
*** WARNING: Unable to verify timestamp for AsDsm.sys
*** ERROR: Module load completed but symbols could not be loaded for AsDsm.sys
fffff880`036df740 fffff880`0123035a fltmgr!FltpDispatch+0xcf
fffff880`036df7a0 00000000`00000002 AsDsm+0x135a
fffff880`036df7a8 fffff880`036dfb10 0x2
fffff880`036df7b0 00000000`00000000 0xfffff880`036dfb10
查看异常记录时，这是第二次崩溃的信息：
Child-SP RetAddr Call Site
fffff880`036df3f8 fffff800`0249b52d nt!RealSuccessor+0x39
fffff880`036df400 fffff880`014ad652 nt!RtlEnumerateGenericTableWithoutSplayingAvl+0x1d
fffff880`036df430 fffff880`014b5fad Ntfs!NtfsFlushVolume+0x436
fffff880`036df560 fffff880`014b66b4 Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`036df640 fffff880`00c02bcf Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`036df6b0 fffff880`00c016df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`036df740 fffff880`0123035a fltmgr!FltpDispatch+0xcf
fffff880`036df7a0 00000000`00000002 AsDsm+0x135a
fffff880`036df7a8 fffff880`036dfb10 0x2
fffff880`036df7b0 00000000`00000000 0xfffff880`036dfb10
第三次撞机与第二次撞机类似。
第四次崩溃也类似，但没有提到 AsDsm：
Child-SP RetAddr Call Site
fffff880`039d8798 fffff880`0145fa88 nt!KeBugCheckEx
fffff880`039d87a0 fffff880`01463df3 Ntfs! ?? ::FNODOBFM::`string'+0x2b49
fffff880`039d87e0 fffff800`024b2fec Ntfs! ?? ::FNODOBFM::`string'+0xff8
fffff880`039d8810 fffff800`024b2a6d nt!_C_specific_handler+0x8c
fffff880`039d8880 fffff800`024b1845 nt!RtlpExecuteHandlerForException+0xd
fffff880`039d88b0 fffff800`024c27c1 nt!RtlDispatchException+0x415
fffff880`039d8f90 fffff800`024873c2 nt!KiDispatchException+0x135
fffff880`039d9630 fffff800`02485cca nt!KiExceptionDispatch+0xc2
fffff880`039d9810 fffff880`01468815 nt!KiGeneralProtectionFault+0x10a
fffff880`039d99a0 fffff880`01503777 Ntfs!NtfsAcquireFcbWithPaging+0x95
fffff880`039d9a00 fffff880`01501fd2 Ntfs!NtfsFindPrefixHashEntry+0x44e
fffff880`039d9b30 fffff880`014ff911 Ntfs!NtfsFindStartingNode+0x452
fffff880`039d9c00 fffff880`01468a3d Ntfs!NtfsCommonCreate+0x3e1
fffff880`039d9de0 fffff800`02493a88 Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`039d9e10 fffff880`014691bf nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`039d9ef0 fffff880`0150299c Ntfs!NtfsCommonCreateOnNewStack+0x4f
fffff880`039d9f50 00000000`00000000 Ntfs!NtfsFsdCreate+0x1ac
答案1
似乎有两次崩溃是AsDsm在通过 WinDBG（或 OSR Online）运行后发生的。
以下是有关该文件的更多信息：
Asdsm.sys
Data Security Manager Driver
Driver File
Windows (R) Codename Longhorn DDK
Digitally signed: ASUSTeK Computer Inc. (VeriSign Time Stamping - G2)
找了一下Data Security Manager，发现确实是Asus Data Security Management。
看起来这在某种程度上保护了正在访问的数据，尝试看看是否可以排除违规程序被拒绝访问。如果不行，您可以考虑删除安全程序/驱动程序，但这样您就不再拥有额外的安全优势了。虽然这只限于华硕，世界上很多人都不运行这个……
总结一下：
Asus Data Security Management由于无法访问数据而导致您的电脑崩溃。您可以通过排除有问题的程序或卸载 AsDsm 来缓解这种情况。