电脑蓝屏求各位大佬帮助分析一下原因

最新推荐文章于 2023-08-22 10:13:32 发布

LA徐凤年

最新推荐文章于 2023-08-22 10:13:32 发布

阅读量2.7k

点赞数 1

文章标签： microsoft windows

本文链接：https://blog.csdn.net/m0_64931011/article/details/127827755

版权

Loading Dump File [C:\Windows\Minidump\111322-11546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols
Executable search path is:
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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff806`50e00000 PsLoadedModuleList = 0xfffff806`51a13410
Debug session time: Sun Nov 13 00:37:13.972 2022 (UTC + 8:00)
System Uptime: 0 days 1:32:43.750
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
.......
Cannot read PEB32 from WOW64 TEB32 00018518 - Win32 error 0n30
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff80651b1c340, 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 : hardware_ram ( PAGE_NOT_ZERO )

Followup: MachineOwner
---------

*** Memory manager detected 99608 instance(s) of page corruption, target is likely to have memory corruption.

15: 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: fffff80651b1c340
Arg4: 0000000000000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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.

FAULTING_MODULE: fffff80650e00000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x133

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 18518

LAST_CONTROL_TRANSFER: from fffff8065102413f to fffff806512283c0

STACK_TEXT:
ffffc500`5a26bc68 fffff806`5102413f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`51b1c340 : nt+0x4283c0
ffffc500`5a26bc70 00000000`00000133 : 00000000`00000001 00000000`00001e00 fffff806`51b1c340 00000000`00000000 : nt+0x22413f
ffffc500`5a26bc78 00000000`00000001 : 00000000`00001e00 fffff806`51b1c340 00000000`00000000 00001388`5119218b : 0x133
ffffc500`5a26bc80 00000000`00001e00 : fffff806`51b1c340 00000000`00000000 00001388`5119218b ffffc500`5a251180 : 0x1
ffffc500`5a26bc88 fffff806`51b1c340 : 00000000`00000000 00001388`5119218b ffffc500`5a251180 00000000`00000202 : 0x1e00
ffffc500`5a26bc90 00000000`00000000 : 00001388`5119218b ffffc500`5a251180 00000000`00000202 00000000`00056ef0 : nt+0xd1c340

STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

*** Memory manager detected 99608 instance(s) of page corruption, target is likely to have memory corruption.

15: kd> lmvm nt
start end module name
fffff806`50e00000 fffff806`51e47000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Fri Apr 19 12:03:21 2002 (3CBF9709)
CheckSum: 00B7E513
ImageSize: 01047000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4