Chiphell - 分享与交流用户体验

标题: 新买的雷神小主机每天蓝屏，怎么确定是硬件问题还是Win11 24H2的问题 [打印本页]

作者: 高子 时间: 2025-3-7 22:46
标题: 新买的雷神小主机每天蓝屏，怎么确定是硬件问题还是Win11 24H2的问题
本帖最后由高子于 2025-3-8 11:42 编辑

RT，每天都会蓝屏一到两次，如何确定是硬件问题还是软件问题？

售后要寄回去检查，工作用机，怎么能尽量不影响工作，排查问题？

插了USB网卡，之前重启不能进系统，后来设置USB设备延迟启动能进了，不知道是不是网卡有冲突引起的蓝屏。

这是蓝屏后系统生产的dump文件

DLOGFILE00010000DUMPj
Dump stack initialized at UTC: 2025/03/06 22:20:42, local time: 2025/03/07 06:20:42.
#BugCheckCode 0x000000000000000A
#BugCheckP1 0x00000000A2002109
#BugCheckP2 0x0000000000000002
#BugCheckP3 0x0000000000000001
#BugCheckP4 0xFFFFF801BBF6F104
Progress 0x00000042
Elapsed BugCheck duration 00001284ms
Starting get secondary dump callbacks size.
Progress 0x00000052
Finish get secondary dump callbacks size.
Dump Type: 4, Total Dump Size: 6249647, Secondary Dump Size: 6028463.
Starting write of dump header.
Finish write of dump header.
Starting write of minidump data.
Finish write of minidump data.
Progress 0x00000044
Elapsed BugCheck duration 00003167ms
Starting invoking secondary dump callbacks.
Calling igdkmdn64.sys secondary callback.
Return from igdkmdn64.sys secondary callback.
Writing igdkmdn64.sys secondary callback data.
Writing igdkmdn64.sys secondary callback data done.
Calling ibtdrv secondary callback.
Return from ibtdrv secondary callback.
Writing ibtdrv secondary callback data.
Writing ibtdrv secondary callback data done.
Calling Intel Wireless WiFi Link Adapter secondary callback.
Return from Intel Wireless WiFi Link Adapter secondary callback.
Writing Intel Wireless WiFi Link Adapter secondary callback data.
Writing Intel Wireless WiFi Link Adapter secondary callback data done.
Calling HbEvtpSystemDiagLogCrashdump secondary callback.
Return from HbEvtpSystemDiagLogCrashdump secondary callback.
Writing HbEvtpSystemDiagLogCrashdump secondary callback data.
Writing HbEvtpSystemDiagLogCrashdump secondary callback data done.
Calling rt25cx21 secondary callback.
Return from rt25cx21 secondary callback.
Writing rt25cx21 secondary callback data.
Writing rt25cx21 secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling IoBugCheckDriverData secondary callback.
Return from IoBugCheckDriverData secondary callback.
Writing IoBugCheckDriverData secondary callback data.
Writing IoBugCheckDriverData secondary callback data done.
Calling PortDriverStandard secondary callback.
Return from PortDriverStandard secondary callback.
Writing PortDriverStandard secondary callback data.
Writing PortDriverStandard secondary callback data done.
Calling \Device\DxgKrnl secondary callback.
Return from \Device\DxgKrnl secondary callback.
Writing \Device\DxgKrnl secondary callback data.
Writing \Device\DxgKrnl secondary callback data done.
Calling Wdf01000 secondary callback.
Return from Wdf01000 secondary callback.
Writing Wdf01000 secondary callback data.
Writing Wdf01000 secondary callback data done.
Calling blackbox - CI secondary callback.
Return from blackbox - CI secondary callback.
Writing blackbox - CI secondary callback data.
Writing blackbox - CI secondary callback data done.
Calling blackbox - Winlogon secondary callback.
Return from blackbox - Winlogon secondary callback.
Writing blackbox - Winlogon secondary callback data.
Writing blackbox - Winlogon secondary callback data done.
Calling blackbox - NTFS secondary callback.
Return from blackbox - NTFS secondary callback.
Writing blackbox - NTFS secondary callback data.
Writing blackbox - NTFS secondary callback data done.
Calling blackbox - PNP secondary callback.
Return from blackbox - PNP secondary callback.
Writing blackbox - PNP secondary callback data.
Writing blackbox - PNP secondary callback data done.
Calling blackbox - BSD secondary callback.
Return from blackbox - BSD secondary callback.
Writing blackbox - BSD secondary callback data.
Writing blackbox - BSD secondary callback data done.
Calling SecureKernelFailureLog secondary callback.
Return from SecureKernelFailureLog secondary callback.
Writing SecureKernelFailureLog secondary callback data.
Writing SecureKernelFailureLog secondary callback data done.
Calling SecureKernelCrashdumpArea secondary callback.
Return from SecureKernelCrashdumpArea secondary callback.
Writing SecureKernelCrashdumpArea secondary callback data.
Writing SecureKernelCrashdumpArea secondary callback data done.
Calling secondary multi-part dump callbacks.
Starting TRIAGEDUMPDATA multi-part secondary callback.
Finish TRIAGEDUMPDATA multi-part secondary callback.
Starting SMBiosData multi-part secondary callback.
Finish SMBiosData multi-part secondary callback.
Starting SMBiosRegistry multi-part secondary callback.
Finish SMBiosRegistry multi-part secondary callback.
Starting SMBiosRegisters multi-part secondary callback.
Finish SMBiosRegisters multi-part secondary callback.
Starting SMBiosDataACPI multi-part secondary callback.
Finish SMBiosDataACPI multi-part secondary callback.
Starting Etw multi-part secondary callback.
Finish Etw multi-part secondary callback.
Finish calling secondary multi-part dump callbacks.
Progress 0x00000045
Finish invoking secondary dump callbacks.
Starting invoking dump complete callbacks; Type: 0x04.
Finished invoking dump complete callbacks; Type: 0x04.
Progress 0x00000046
Dump ended at UTC: 2025/03/06 22:20:42, local time: 2025/03/07 06:20:42.
Elapsed BugCheck duration 00003922ms
Progress 0x00000053
Dump completed successfully.

硬盘550小时，通电117次
(, 下载次数: 20)

作者: effortbee 时间: 2025-3-7 23:28
正版的话当我没说~~
我用我这个的第四选项做了一个U盘从新安装恢复就没毛病了
你要是正版在看看别人回复排查排查~~

https://answers.microsoft.com/zh ... b-8d12-3cf104572f89

作者: 文泰来 时间: 2025-3-7 23:44
现在win11稳定得很，大概率硬件问题，你都知道网卡不正常了，换一个试试不简单嘛？

作者: 6jqo1d 时间: 2025-3-8 00:02
你这个问题重启解决不了，那就重装，要是还不行，重买。。。

抖个激灵。可以想尝试去掉所有外设，还不行的话内存对调一下（我之前也试过天天蓝屏，内存对调一下就好了），还不行试一下重装。再不行就是硬件问题了

作者: zerozerone 时间: 2025-3-8 00:22
24h2的电管、内置驱动、系统策略、芯片组驱动的兼容性造成的稳定性的问题还是相对比较明显的，
相当一部分驱动对于24系统的“安全”要求没那么高的适配性，嘿嘿，其内置驱动也是频繁的“超大规模”的持续更新。
复杂多元多层的安全设备环境下的安全总体可绝不是个简单问题。
可能有人觉得说的云里雾里的，大概率可能对“安全”这个概念过于正向正面理解了。
微软-安全，嘿嘿。

说人话，磨（刀）合期的东西，自用还是要自甘风险。

作者: zerozerone 时间: 2025-3-8 00:25
可以试试26100.3323。如现用的是.3000之前系统。

作者: yuechsh 时间: 2025-3-8 06:01
装22631.4169版本的23h2试一下

作者: YsHaNg 时间: 2025-3-8 06:22

zerozerone 发表于 2025-3-7 16:22
24h2的电管、内置驱动、系统策略、芯片组驱动的兼容性造成的稳定性的问题还是相对比较明显的，
相当一部分 ...

24h2要等25h2 rollout才能用

作者: 高子 时间: 2025-3-8 08:42

文泰来发表于 2025-3-7 23:44
现在win11稳定得很，大概率硬件问题，你都知道网卡不正常了，换一个试试不简单嘛？ ...

USB网卡换过，两个不同品牌都会蓝屏

作者: 高子 时间: 2025-3-8 08:43

6jqo1d 发表于 2025-3-8 00:02
你这个问题重启解决不了，那就重装，要是还不行，重买。。。
抖个激灵。可以想尝试去掉所有外设，还不行的 ...

好的，只能死马当作活马医了~

作者: hwqdyx 时间: 2025-3-8 09:24
The log you provided appears to be a Windows Bug Check (Blue Screen of Death - BSOD) dump file log. This log is generated when the system encounters a critical error and crashes. Below is a breakdown of the key information in the log:
Key Details from the Log

Bug Check Code (Stop Code):

      0x0000000A (IRQL_NOT_LESS_OR_EQUAL)

         This indicates that a kernel-mode process or driver attempted to access a memory address it did not have permission to access, or at an Interrupt Request Level (IRQL) that was too high.

Bug Check Parameters:

      P1: 0x00000000A2002109 - Memory address that was referenced.

      P2: 0x0000000000000002 - IRQL at the time of the crash.

      P3: 0x0000000000000001 - Type of access (0 = read, 1 = write).

      P4: 0xFFFFF801BBF6F104 - Address of the instruction that attempted the memory access.

Dump Type:

      Type: 4 - This is a Complete Memory Dump, which includes all the contents of system memory at the time of the crash.

Dump Size:

      Total Dump Size: 6,249,647 bytes (~6 MB).

      Secondary Dump Size: 6,028,463 bytes (~6 MB).

Drivers/Modules Involved:

      Several drivers and components were called during the crash dump process, including:

         igdkmdn64.sys (Intel Graphics Driver).

         ibtdrv (Intel Bluetooth Driver).

         Intel Wireless WiFi Link Adapter.

         wdiwifi.sys (Windows Driver for WiFi).

         DxgKrnl (DirectX Graphics Kernel).

         Wdf01000.sys (Windows Driver Framework).

         NTFS (File System Driver).

         SecureKernel (Windows Secure Kernel).

Timestamps:

      Crash occurred at UTC: 2025/03/06 22:20:42 (Local Time: 2025/03/07 06:20:42).

      The entire dump process took 39,222 milliseconds (~39 seconds).

Progress Codes:

      The log shows various progress codes (e.g., 0x00000042, 0x00000052, etc.), which indicate the stages of the crash dump process.

Analysis of the Crash

The IRQL_NOT_LESS_OR_EQUAL error is often caused by:

      Faulty or Incompatible Drivers:

         The log mentions several drivers (igdkmdn64.sys, ibtdrv, wdiwifi.sys, etc.), which could be potential culprits.

      Hardware Issues:

         Faulty RAM, overheating, or other hardware problems can also trigger this error.

      Corrupted System Files:

         Issues with Windows system files or the file system (e.g., NTFS) can cause crashes.

      Software Conflicts:

         Third-party software or drivers conflicting with the operating system.

Next Steps for Troubleshooting

Check for Driver Updates:

      Update the drivers mentioned in the log, especially:

         Intel Graphics Driver (igdkmdn64.sys).

         Intel Bluetooth Driver (ibtdrv).

         WiFi Driver (wdiwifi.sys).

Run Hardware Diagnostics:

      Test your RAM using tools like Windows Memory Diagnostic or MemTest86.

      Check for overheating issues and ensure proper cooling.

Scan for Corrupted System Files:

      Open Command Prompt as Administrator and run:
      复制

      sfc /scannow

      Follow up with:
      复制

      DISM /Online /Cleanup-Image /RestoreHealth

Analyze the Dump File:

      Use tools like WinDbg or BlueScreenView to analyze the dump file (DLOGFILE00010000DUMP) for more details about the crash.

Check for Windows Updates:

      Ensure your system is up to date with the latest Windows updates and patches.

Review Installed Software:

      Uninstall any recently installed software or drivers that might be causing conflicts.

Conclusion

The crash was caused by an IRQL_NOT_LESS_OR_EQUAL error, likely due to a driver or hardware issue. Focus on updating drivers, checking hardware, and analyzing the dump file for more specific insights. If the issue persists, consider seeking further assistance from Microsoft Support or a professional technician.

作者: 文泰来 时间: 2025-3-8 23:55

高子发表于 2025-3-8 08:42
USB网卡换过，两个不同品牌都会蓝屏

换个口或者都不插试试呗，usb口或者主板usb控制器的问题也有可能

欢迎光临 Chiphell - 分享与交流用户体验 (https://www.chiphell.com/)