应该是和360驱动发生冲突了,先卸载360再看看吧

他的办法不行的话，自己刷刷BIOS可能版本的问题
1.电脑中毒
2.不兼容
3.版本问题

谢谢,我先试试了

做技术的要严谨, 会就说, 不会就不说. 误导别人就没啥意思了. 如下dump, 请教你是怎么看出来跟360有关系的, 别说栈上有xxx, 如果用这个思路去分析dump. 那就真让人无语了...

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffdbc8aa, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: b7e0d64a, If non-zero, the instruction address which referenced the bad memory
         address.
Arg4: 00000000, (reserved)

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

Could not read faulting driver name
*** WARNING: Unable to verify timestamp for qutmdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for qutmdrv.sys
Unable to load image Hookport.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Hookport.sys
*** ERROR: Module load completed but symbols could not be loaded for Hookport.sys
Failed calling InternetOpenUrl, GLE=12007

READ_ADDRESS:  ffdbc8aa

FAULTING_IP:
Ntfs!NtfsFindNameLink+1e
b7e0d64a 668b10          mov     dx,word ptr [eax]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AliIM.exe

LAST_CONTROL_TRANSFER:  from b7e0d6f4 to b7e0d64a

STACK_TEXT:  
ab15e5b8 b7e0d6f4 e315db8c ab15e5fc e315da20 Ntfs!NtfsFindNameLink+0x1e
ab15e5e4 b7e0d822 88ef0c80 e315da20 ab15e724 Ntfs!NtfsFindPrefix+0x7c
ab15e748 b7e0af2d 88ef0c80 88e1f348 ab15e7a0 Ntfs!NtfsCommonCreate+0xbb6
ab15e82c 804ef139 89cc91a0 88e1f348 89d11f38 Ntfs!NtfsFsdCreate+0x1dc
ab15e83c b7e8e876 00000000 89d11f38 8901b008 nt!IopfCallDriver+0x31
ab15e888 804ef139 89cfae88 88e1f348 88e1f348 sr!SrCreate+0x150
ab15e898 b7e9ee9b 00000000 88e1f348 88e1f4fc nt!IopfCallDriver+0x31
ab15e8bc b7eab754 ab15e8dc 89ab7ee8 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
ab15e8f8 804ef139 89ab7ee8 88e1f348 88e1f4fc fltMgr!FltpCreate+0x26a
ab15e908 af770841 88e1f358 89ce8880 88dbcb78 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ab15e990 804ef139 89261790 88e1f348 88e1f348 qutmdrv+0xf841
ab15e9a0 80579722 89d21018 8903afd4 ab15eb48 nt!IopfCallDriver+0x31
ab15ea80 805b5dfa 89d21030 00000000 8903af30 nt!IopParseDevice+0xa12
ab15eb08 805b21a3 00000000 ab15eb48 00000040 nt!ObpLookupObjectName+0x56a
ab15eb5c 8056c315 00000000 00000000 15ec4401 nt!ObOpenObjectByName+0xeb
ab15ebd8 8056cc8c 029fde04 001200a9 029fdd00 nt!IopCreateFile+0x407
ab15ec34 805704b3 029fde04 001200a9 029fdd00 nt!IoCreateFile+0x8e
ab15ec74 b7f57871 029fde04 001200a9 029fdd00 nt!NtOpenFile+0x27
ab15ed44 8053e6f8 029fde04 001200a9 029fdd00 Hookport+0x2871
ab15ed44 7c92e4f4 029fde04 001200a9 029fdd00 nt!KiFastCallEntry+0xf8
029fdd20 00000000 00000000 00000000 00000000 0x7c92e4f4

STACK_COMMAND:  kb

FOLLOWUP_IP:
qutmdrv+f841
af770841 ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  qutmdrv+f841

FOLLOWUP_NAME:  wintriag

MODULE_NAME: qutmdrv

IMAGE_NAME:  qutmdrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50192f36

FAILURE_BUCKET_ID:  0x50_qutmdrv+f841

BUCKET_ID:  0x50_qutmdrv+f841

Followup: wintriag

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff7e6f6c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bd08d4f0, If non-zero, the instruction address which referenced the bad memory
         address.
Arg4: 00000000, (reserved)

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

Could not read faulting driver name
Failed calling InternetOpenUrl, GLE=12007

READ_ADDRESS:  ff7e6f6c

FAULTING_IP:
nv4_disp+7b4f0
bd08d4f0 8b7e08          mov     edi,dword ptr [esi+8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  main_new_server

LAST_CONTROL_TRANSFER:  from 00000000 to bd08d4f0

STACK_TEXT:  
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x7b4f0

STACK_COMMAND:  kb

FOLLOWUP_IP:
nv4_disp+7b4f0
bd08d4f0 8b7e08          mov     edi,dword ptr [esi+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+7b4f0

FOLLOWUP_NAME:  nvidia

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4fb206eb

FAILURE_BUCKET_ID:  0x50_nv4_disp+7b4f0

BUCKET_ID:  0x50_nv4_disp+7b4f0

Followup: nvidia
---------

我也没说肯定是,只是提出一个建议罢了,有必要较真吗?本来minidump就不一定看得出来

qutmdrv.sys既然能看到这个，百度或google下呗，也许有相同情况的网友提供的解决方案的

我的WIN7 64 最近也是睡眠蓝屏关机，经过大概的观察我认为可能是无线驱动的问题，升级最新驱动后正常了