求助win7_x64旗舰版蓝屏debug检测结果

小卡小卡卡

*********************************************************************
* 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+88029 )

Followup: MachineOwner

812534593

symbol路径没有设置或者设置错误！

小卡小卡卡

812534593 发表于 2015-2-18 17:39
symbol路径没有设置或者设置错误！

可能会是什么原因啊,那得怎么解决呢

812534593

小卡小卡卡 发表于 2015-2-18 17:41
可能会是什么原因啊,那得怎么解决呢

把dump发上来，你dbg设置错误，看的没什么有用的信息，得从新看！

小卡小卡卡

812534593 发表于 2015-2-18 17:52
把dump发上来，你dbg设置错误，看的没什么有用的信息，得从新看！

c盘Minidump里面的

812534593

Probably caused by : memory_corruption ( nt!MiUpdateWsle+2b9 )

内存问题！看看谁会分析：

1. 
   
2. 
   
3. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
   
4. Copyright (c) Microsoft Corporation. All rights reserved.
   
5. 
   
6. 
   
7. Loading Dump File [D:\Tools\dump\021815-27034-01.dmp]
   
8. Mini Kernel Dump File: Only registers and stack trace are available
   
9. 
   
10. Symbol search path is: D:\Symbols;SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    
11. Executable search path is:
    
12. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    
13. Product: WinNt, suite: TerminalServer SingleUserTS
    
14. Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    
15. Machine Name:
    
16. Kernel base = 0xfffff800`04013000 PsLoadedModuleList = 0xfffff800`04257890
    
17. Debug session time: Wed Feb 18 17:08:21.895 2015 (UTC + 8:00)
    
18. System Uptime: 0 days 0:03:29.674
    
19. Loading Kernel Symbols
    
20. ...............................................................
    
21. ................................................................
    
22. ................................................
    
23. Loading User Symbols
    
24. Loading unloaded module list
    
25. ...
    
26. *******************************************************************************
    
27. *                                                                             *
    
28. *                        Bugcheck Analysis                                    *
    
29. *                                                                             *
    
30. *******************************************************************************
    
31. 
    
32. Use !analyze -v to get detailed debugging information.
    
33. 
    
34. BugCheck A, {fffff70640000e94, 0, 1, fffff8000409b029}
    
35. 
    
36. Probably caused by : memory_corruption ( nt!MiUpdateWsle+2b9 )
    
37. 
    
38. Followup: MachineOwner
    
39. ---------
    
40. 
    
41. 0: kd> !analyze -v
    
42. *******************************************************************************
    
43. *                                                                             *
    
44. *                        Bugcheck Analysis                                    *
    
45. *                                                                             *
    
46. *******************************************************************************
    
47. 
    
48. IRQL_NOT_LESS_OR_EQUAL (a)
    
49. An attempt was made to access a pageable (or completely invalid) address at an
    
50. interrupt request level (IRQL) that is too high.  This is usually
    
51. caused by drivers using improper addresses.
    
52. If a kernel debugger is available get the stack backtrace.
    
53. Arguments:
    
54. Arg1: fffff70640000e94, memory referenced
    
55. Arg2: 0000000000000000, IRQL
    
56. Arg3: 0000000000000001, bitfield :
    
57.         bit 0 : value 0 = read operation, 1 = write operation
    
58.         bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    
59. Arg4: fffff8000409b029, address which referenced memory
    
60. 
    
61. Debugging Details:
    
62. ------------------
    
63. 
    
64. 
    
65. WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800042c1100
    
66. fffff70640000e94
    
67. 
    
68. CURRENT_IRQL:  0
    
69. 
    
70. FAULTING_IP:
    
71. nt!MiUpdateWsle+2b9
    
72. fffff800`0409b029 44893498        mov     dword ptr [rax+rbx*4],r14d
    
73. 
    
74. CUSTOMER_CRASH_COUNT:  1
    
75. 
    
76. DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
77. 
    
78. BUGCHECK_STR:  0xA
    
79. 
    
80. PROCESS_NAME:  taskhost.exe
    
81. 
    
82. TRAP_FRAME:  fffff88003eba670 -- (.trap 0xfffff88003eba670)
    
83. NOTE: The trap frame does not contain all registers.
    
84. Some register values may be zeroed or incorrect.
    
85. rax=fffff70440001000 rbx=0000000000000000 rcx=fffff70001080488
    
86. rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    
87. rip=fffff8000409b029 rsp=fffff88003eba800 rbp=000000000000000f
    
88. r8=fffff683fffffd28  r9=fffffa8000000000 r10=fffff68000005da8
    
89. r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    
90. r14=0000000000000000 r15=0000000000000000
    
91. iopl=0         nv up ei pl nz na po nc
    
92. nt!MiUpdateWsle+0x2b9:
    
93. fffff800`0409b029 44893498        mov     dword ptr [rax+rbx*4],r14d ds:fffff704`40001000=????????
    
94. Resetting default scope
    
95. 
    
96. LAST_CONTROL_TRANSFER:  from fffff80004087469 to fffff80004087ec0
    
97. 
    
98. STACK_TEXT:  
    
99. fffff880`03eba528 fffff800`04087469 : 00000000`0000000a fffff706`40000e94 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
    
100. fffff880`03eba530 fffff800`040860e0 : 00000000`00000001 fffff706`40000e94 00000000`00000000 00000000`7fffffa5 : nt!KiBugCheckDispatch+0x69
     
101. fffff880`03eba670 fffff800`0409b029 : fffffa80`00000028 00000000`00000000 00000000`00000000 fffff800`00000000 : nt!KiPageFault+0x260
     
102. fffff880`03eba800 fffff800`040a5987 : 80000000`2758a825 fffff800`0439b068 fffff700`01080000 fffff8a0`0a5fb360 : nt!MiUpdateWsle+0x2b9
     
103. fffff880`03eba870 fffff800`040950b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x6e7
     
104. fffff880`03eba980 fffff800`04085fee : 00000000`00000000 00000000`00bb0000 00000000`00000201 00000000`00000004 : nt!MmAccessFault+0x359
     
105. fffff880`03ebaae0 000007fe`ff92e518 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
     
106. 00000000`010de800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff92e518
     
107. 
     
108. 
     
109. STACK_COMMAND:  kb
     
110. 
     
111. FOLLOWUP_IP:
     
112. nt!MiUpdateWsle+2b9
     
113. fffff800`0409b029 44893498        mov     dword ptr [rax+rbx*4],r14d
     
114. 
     
115. SYMBOL_STACK_INDEX:  3
     
116. 
     
117. SYMBOL_NAME:  nt!MiUpdateWsle+2b9
     
118. 
     
119. FOLLOWUP_NAME:  MachineOwner
     
120. 
     
121. MODULE_NAME: nt
     
122. 
     
123. DEBUG_FLR_IMAGE_TIMESTAMP:  54b5f6ff
     
124. 
     
125. IMAGE_NAME:  memory_corruption
     
126. 
     
127. FAILURE_BUCKET_ID:  X64_0xA_nt!MiUpdateWsle+2b9
     
128. 
     
129. BUCKET_ID:  X64_0xA_nt!MiUpdateWsle+2b9
     
130. 
     
131. Followup: MachineOwner
     
132. ---------
     
133. 
     
134. 
     

复制代码

小卡小卡卡

812534593 发表于 2015-2-18 18:16
Probably caused by : memory_corruption ( nt!MiUpdateWsle+2b9 )

内存问题！看看谁会分析：

应该是安装了VMware11的问题,有冲突.本人正版win7_x64旗舰版...不知道有没有类似情况的

812534593

小卡小卡卡 发表于 2015-2-20 15:55
应该是安装了VMware11的问题,有冲突.本人正版win7_x64旗舰版...不知道有没有类似情况的

我的也是win7 x64旗舰版，用vmware从来没出现过问题！

小卡小卡卡

812534593 发表于 2015-2-20 18:54
我的也是win7 x64旗舰版，用vmware从来没出现过问题！

我现在换回了VMware10目前还没有出现过蓝屏,可能是版本问题吧

小卡小卡卡

已解决...win7内存检测工具显示有硬件损坏,内存条坏了...