最新主题

mxqwe · ‎2021-07-25

这么久了还是来反馈下情况吧。真正的原因应该是装系统的固态硬盘掉盘或者接触不良。导致只能识别到机械硬盘，这也是为什么硬盘诊断没有出现问题的原因。我重新拔插后，目前还没有出现3F0现象。

mxqwe · ‎2021-07-08

我最近更新过最新版本的BIOS，现在想想好像就是更新之后才出的问题。

mxqwe · ‎2021-07-07

最近一周出现两次开机出现3F0，硬盘没有找到。但是内存检查和硬盘检查都没问题啊。多重启几次就可以进入系统了。我想问这种问题出现的原因是什么，怎么修复？是系统软件问题还是电脑驱动问题？重装系统能解决吗？重装系统太麻烦，很多软件资料要重新设置。

mxqwe · ‎2018-09-19

电脑原本8G内存。之前了解到内存组双通道能提高内存性能，便想买一块8G内存条。但是价格一直不降，又想到这电脑的配置没必要16G内存，12G也行。就想问下8+4与8+8这两种方案，除了内存大小差异外，性能有没有差异？谢谢指教。双十一快到了，8G内存也勉强能接受，主要是值不值得的问题。

mxqwe · ‎2018-09-08

最近电脑出了点顽疾，想重装系统。这个本子好像不提供原厂oem系统下载。recovery不小心格式化了。可以装原版win10补上惠普的驱动和各种组件吗？还能正常用HP support assistant，HP coolsense,Bang Olufsen音频控制这些吗？可以使用驱动精灵这类软件吗？

mxqwe · ‎2018-09-07

测试了两小时也没出现问题

mxqwe · ‎2018-09-07

测试了两个小时也没有出现错误

mxqwe · ‎2018-09-07

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\cydzo\Desktop\090718-20578-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 17134 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 17134.1.amd64fre.rs4_release.180410-1804 Machine Name: Kernel base = 0xfffff800`6060a000 PsLoadedModuleList = 0xfffff800`609b8170 Debug session time: Fri Sep 7 03:44:06.459 2018 (UTC + 8:00) System Uptime: 0 days 1:44:29.453 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............ Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 133, {1, 1e00, fffff80060a57378, 0} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff80060a57378 Arg4: 0000000000000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x133 PROCESS_NAME: System CURRENT_IRQL: d LAST_CONTROL_TRANSFER: from fffff800607e0ec5 to fffff800607b2ca0 STACK_TEXT: fffff800`63151b78 fffff800`607e0ec5 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`60a57378 : nt!KeBugCheckEx fffff800`63151b80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x182625 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff800607493ef - nt!MiQueryLeafPte+1f [ f6:ef ] 1 error : !nt (fffff800607493ef) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BYTE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BYTE BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BYTE Followup: memory_corruption --------- 这是第二个，基本相同。

mxqwe · ‎2018-09-07

Loading Dump File [C:\Users\cydzo\Desktop\090718-20359-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/dow...

Loading Dump File [C:\Users\cydzo\Desktop\090718-20359-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 17134 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 17134.1.amd64fre.rs4_release.180410-1804 Machine Name: Kernel base = 0xfffff800`38492000 PsLoadedModuleList = 0xfffff800`38840170 Debug session time: Fri Sep 7 01:59:02.916 2018 (UTC + 8:00) System Uptime: 0 days 0:22:47.907 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 133, {0, 501, 500, fffff800388df378} Probably caused by : memory_corruption Followup: memory_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff800388df378 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x133 PROCESS_NAME: dllhost.exe CURRENT_IRQL: d LAST_CONTROL_TRANSFER: from fffff80038668e35 to fffff8003863aca0 STACK_TEXT: fffff800`3af51b78 fffff800`38668e35 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx fffff800`3af51b80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x182595 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff800385d13ee-fffff800385d13ef 2 bytes - nt!MiQueryLeafPte+1e [ 80 f6:00 82 ] 2 errors : !nt (fffff800385d13ee-fffff800385d13ef) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: LARGE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE Followup: memory_corruption --------- 0: kd> lmvm memory_corruption start end module name 0: kd> lmvm memory_corruption start end module name 我看不怎么懂，求大神帮助

mxqwe · ‎2018-09-06

没用，还是一样。和win10的版本有关系吗？

mxqwe · ‎2018-09-05

重装也没用，是nvidia的原因吗？最新版。

mxqwe · ‎2017-09-05

校园网开无线热点需要虚拟无线网卡，求教如何安装

最新主题

回复： 3F0错误频繁出现

回复： 3F0错误频繁出现

3F0错误频繁出现

内存8+4双通道与8+8双通道，性能上有什么差异吗？

暗影精灵2pro,重装系统可以装MSDN原版WIN10+惠普的驱动吗？

回复：使用onedrive上传文件大概率蓝屏，附dump分析，谢谢大神帮助

回复：使用onedrive上传文件大概率蓝屏，附dump分析，谢谢大神帮助

回复：使用onedrive上传文件大概率蓝屏，附dump分析，谢谢大神帮助

使用onedrive上传文件大概率蓝屏，附dump分析，谢谢大神帮助

回复： nvidia geforce experience打不开？

nvidia geforce experience打不开？

win10如何安装虚拟无线网卡？