Ecthellin
发表于 2015-7-27 15:44:28
包子侯爵 发表于 2015-7-27 15:26
http://diy.pconline.com.cn/674/6745146.html
感触良多啊
唉,俗话说的好:性能过剩战三年,仙六一出解放前{:5_160:}
包子侯爵
发表于 2015-7-27 15:45:18
Ecthellin 发表于 2015-7-27 15:44
唉,俗话说的好:性能过剩战三年,仙六一出解放前
优化太渣……
冶天
发表于 2015-7-27 15:52:19
包子侯爵 发表于 2015-7-27 15:45
优化太渣……
{:6_170:}{:6_170:}
冶天
发表于 2015-7-27 15:52:57
包子侯爵 发表于 2015-7-27 15:43
我问了电脑城那人,没理我……
自己京东解决 外面现在也没什么好货
该隐的复仇
发表于 2015-7-27 16:20:58
我的也花了http://radeonfury.com/forum.php?mod=viewthread&tid=397&highlight=%E8%8A%B1%E5%B1%8F
电源RM750
Ecthellin
发表于 2015-7-27 16:22:04
该隐的复仇 发表于 2015-7-27 16:20
我的也花了http://radeonfury.com/forum.php?mod=viewthread&tid=397&highlight=%E8%8A%B1%E5%B1%8F
电源RM ...
你这个还没搞定啊
冶天
发表于 2015-7-27 16:22:17
该隐的复仇 发表于 2015-7-27 16:20
我的也花了http://radeonfury.com/forum.php?mod=viewthread&tid=397&highlight=%E8%8A%B1%E5%B1%8F
电源RM ...
水王还蓝屏掉盘 你应该不掉不蓝
该隐的复仇
发表于 2015-7-27 16:25:23
冶天 发表于 2015-7-27 16:22
水王还蓝屏掉盘 你应该不掉不蓝
。。。前天一次蓝屏,用15.15驱动玩刺客信条4,一秒后卡住,然后蓝屏了,连续两次都这样。。。。换回15.20又没事了。
该隐的复仇
发表于 2015-7-27 16:27:11
Ecthellin 发表于 2015-7-27 16:22
你这个还没搞定啊
首先我要知道问题出哪里啊。。。显卡到手都是先跑个分,玩游戏等等,都没事。。。后面停下来看网页就出现这状况了。
包子侯爵
发表于 2015-7-27 16:27:35
冶天 发表于 2015-7-27 15:52
自己京东解决 外面现在也没什么好货
他直接在电脑城拿货,便宜,直接找他质保就行了
包子侯爵
发表于 2015-7-27 16:28:24
该隐的复仇 发表于 2015-7-27 16:20
我的也花了http://radeonfury.com/forum.php?mod=viewthread&tid=397&highlight=%E8%8A%B1%E5%B1%8F
电源RM ...
恩,之前就看过了
该隐的复仇
发表于 2015-7-27 16:32:16
我本月累计搜索3300次,看网页的频率蛮高的。。。。有高几率花屏,某种程度上也算是测试?{:5_138:}
冶天
发表于 2015-7-27 16:33:04
该隐的复仇 发表于 2015-7-27 16:25
。。。前天一次蓝屏,用15.15驱动玩刺客信条4,一秒后卡住,然后蓝屏了,连续两次都这样。。。。换回15.20 ...
水王游戏 倒是没事 就是浏览器
该隐的复仇
发表于 2015-7-27 16:34:58
冶天 发表于 2015-7-27 16:33
水王游戏 倒是没事 就是浏览器
我也是啊。。。。{:5_145:}关于15.15刺客信条4卡住蓝屏,但看门狗又不会卡住。。。{:5_151:}实在搞不懂
该隐的复仇
发表于 2015-7-27 16:35:33
冶天 发表于 2015-7-27 16:33
水王游戏 倒是没事 就是浏览器
浏览器问题是最明显的。。。游戏问题很少
Ecthellin
发表于 2015-7-27 16:37:37
该隐的复仇 发表于 2015-7-27 16:32
我本月累计搜索3300次,看网页的频率蛮高的。。。。有高几率花屏,某种程度上也算是测试? ...
浏览器压力测试...
z23wen
发表于 2015-7-27 16:39:11
这么牛X的显卡,怎么也得1080P啊,你弄个900P啥意思啊!
冶天
发表于 2015-7-27 16:39:48
z23wen 发表于 2015-7-27 16:39
这么牛X的显卡,怎么也得1080P啊,你弄个900P啥意思啊!
念旧{:6_170:}
Ecthellin
发表于 2015-7-27 16:49:31
z23wen 发表于 2015-7-27 16:39
这么牛X的显卡,怎么也得1080P啊,你弄个900P啥意思啊!
自己的显示器没敢搬到单位,怕挨打{:5_154:}
z23wen
发表于 2015-7-27 16:55:43
我去,你不会把你的FURY X插单位的办公电脑玩吧
Ecthellin
发表于 2015-7-27 16:56:27
z23wen 发表于 2015-7-27 16:55
我去,你不会把你的FURY X插单位的办公电脑玩吧
不是啊,我是把二奶搬到单位了{:5_157:}
冶天
发表于 2015-7-27 16:57:26
z23wen 发表于 2015-7-27 16:55
我去,你不会把你的FURY X插单位的办公电脑玩吧
估计除了显示器机箱没换 其它都暗渡陈仓
包子侯爵
发表于 2015-7-27 17:02:51
该隐的复仇 发表于 2015-7-27 16:20
我的也花了http://radeonfury.com/forum.php?mod=viewthread&tid=397&highlight=%E8%8A%B1%E5%B1%8F
电源RM ...
好像是DX问题dxgkrnl.sys,错误信号
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File
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: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`04e5c000 PsLoadedModuleList = 0xfffff800`050a1890
Debug session time: Thu Jul 23 11:23:29.907 2015 (UTC + 8:00)
System Uptime: 0 days 2:24:33.203
*********************************************************************
* 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
...........
Unable to load image dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {fffffa800612aa00, 0, 0, 0}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : dxgkrnl.sys ( dxgkrnl+6f63 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa800612aa00, Pointer to a stuck thread object.Do .thread then kb on it to find
the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times this error occurred.If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below.On the
blue screen, this will always equal 1.
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: dxgkrnl
FAULTING_MODULE: fffff80004e5c000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:539e411c
FAULTING_THREAD:fffffa800612aa00
DEFAULT_BUCKET_ID:GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT:1
BUGCHECK_STR:0xEA
CURRENT_IRQL:0
LAST_CONTROL_TRANSFER:from fffff88005ee6f63 to fffff80004ecea40
STACK_TEXT:
fffff880`020cef78 fffff880`05ee6f63 : 00000000`000000ea fffffa80`0612aa00 00000000`00000000 00000000`00000000 : nt+0x72a40
fffff880`020cef80 00000000`000000ea : fffffa80`0612aa00 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x6f63
fffff880`020cef88 fffffa80`0612aa00 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`05ee6e28 : 0xea
fffff880`020cef90 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`05ee6e28 fffff800`04e20028 : 0xfffffa80`0612aa00
STACK_COMMAND:.thread 0xfffffa800612aa00 ; kb
FOLLOWUP_IP:
dxgkrnl+6f63
fffff880`05ee6f63 ?? ???
SYMBOL_STACK_INDEX:1
SYMBOL_NAME:dxgkrnl+6f63
FOLLOWUP_NAME:MachineOwner
IMAGE_NAME:dxgkrnl.sys
BUCKET_ID:WRONG_SYMBOLS
Followup: MachineOwner
---------
z23wen
发表于 2015-7-27 17:03:51
单位的志强换到自己的电脑,24G内存换到自己的电脑,然后自己的奔腾换到单位,2G内存插单位电脑,1TB的机械硬盘跟单位的240G固态硬盘调了个
冶天
发表于 2015-7-27 17:06:08
z23wen 发表于 2015-7-27 17:03
单位的志强换到自己的电脑,24G内存换到自己的电脑,然后自己的奔腾换到单位,2G内存插单位电脑,1TB的机械 ...
你说反了 他是自己的换到单位{:6_170:} 有几个单位提供的够劲