win10系统蓝屏，dmp文件如下

Question

win10系统蓝屏，dmp文件如下

YZ L 1

Loading Dump File [C:\Windows\Minidump\053022-3921-01.dmp]
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 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff80682a00000 PsLoadedModuleList = 0xfffff8068362a2b0
Debug session time: Mon May 30 13:38:11.004 2022 (UTC + 8:00)
System Uptime: 0 days 0:11:34.713

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
......

*
Bugcheck Analysis *
*

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, fffff303ea7c6680, fffff303ea7c65d8, 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 31232 instance(s) of page corruption, target is likely to have memory corruption.

3: kd> !analyze -v

*
Bugcheck Analysis *
*

Unknown bugcheck code (139)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000003
Arg2: fffff303ea7c6680
Arg3: fffff303ea7c65d8
Arg4: 0000000000000000

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.

FAULTING_MODULE: fffff80682a00000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x139

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 7a00

LAST_CONTROL_TRANSFER: from fffff80682e09c69 to fffff80682df7d60

STACK_TEXT:
fffff303ea7c6358 fffff80682e09c69 : 0000000000000139 0000000000000003 fffff303ea7c6680 fffff303ea7c65d8 : nt+0x3f7d60
fffff303ea7c6360 0000000000000139 : 0000000000000003 fffff303ea7c6680 fffff303ea7c65d8 0000000000000000 : nt+0x409c69
fffff303ea7c6368 0000000000000003 : fffff303ea7c6680 fffff303ea7c65d8 0000000000000000 ffff9088a9482040 : 0x139
fffff303ea7c6370 fffff303ea7c6680 : fffff303ea7c65d8 0000000000000000 ffff9088a9482040 aaaaaaaaaaaaaaaa : 0x3
fffff303ea7c6378 fffff303ea7c65d8 : 0000000000000000 ffff9088a9482040 aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa : 0xfffff303ea7c6680 fffff303ea7c6380 0000000000000000 : ffff9088a9482040 aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa 0000000000000000 : 0xfffff303ea7c65d8

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 31232 instance(s) of page corruption, target is likely to have memory corruption.

0 comments

1 answer

Your answer

Answer 1

Hi YZL-3725,

Because this is an public forum, in order to protect your personal privacy information, it is not recommended to upload event logs such as dump information. You can look at the specific

bugcheck error code of event 1001 in the event log system log, and search the official website for information.

At the same time, you can see that no special information is recorded in the output of your dump information. There may be a problem with the configuration of your symbol file, resulting in a parsing error.

Mini dump usually contains less information. If you find a dump file with memory (C:\Windows\memory.dmp) after the blue screen appears, you can try to put it in a shared link that you think is safe, and put the shared link in In reply, I try to download it for you to check. But please delete the file in time.

Best Regards,

Carl

Share via

win10系统蓝屏，dmp文件如下

1 answer

Your answer